Results for “fin_system_params_all_mrc_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view FIN_SYSTEM_PARAMS_ALL_MRC_V is an Oracle E-Business Suite reporting object belonging to the Payables (AP) module. Its name and internal structure identify it as a Multiple Reporting Currencies (MRC) variant of the Financials System Parameters view, exposed through the Application Programming Interface layer (the "AP." qualifier on every projected column). In Oracle EBS 12.1.1 and 12.2.2, MRC views of this type present system-level Payables setup options — currencies, payment terms, encumbrance accounts, tax defaults, and global descriptive flexfield segments — for each reporting currency set defined for the operating unit. The single non-column expression in the select list, NVL(TO_NUMBER(SUBSTRB(USERENV('CLIENT_INFO'), 45, 10)), -99), is the standard "org context" extraction pattern used throughout EBS MRC and multi-org views; it reads the operating unit identifier from the client information string and defaults to -99 when no context has been set. The ETRM entry carries the annotation "Retrofitted," indicating the object was inherited from a prior release and exists primarily for backward compatibility within the MRC architecture rather than as a primary setup interface. The same metadata records that the view is "Not implemented in this database" in the sampled environment, which is typical for MRC views in installations where MRC is either not licensed or not configured, or where the documented environment does not reflect the production instance.

Underlying Base Objects

The ETRM metadata does not enumerate referenced base objects. From the column list and product context, the view is a wrapper over the Payables system parameters entity — logically, the MRC companion of FIN_SYSTEM_PARAMS_ALL — sourced from the AP system parameters table family within the AP schema. Every column is qualified with the AP schema prefix, consistent with a view defined in the AP (or APPS) schema over an AP base table. In the MRC model, a separate parameters record is maintained per reporting currency set, and the view exposes those records for the operating unit resolved from CLIENT_INFO. The absence of documented base objects in the ETRM record means dependency analysis should be confirmed against ALL_DEPENDENCIES and ALL_VIEWS in the target instance before relying on the view for integration.

Key Columns

• Currency and payment defaults: INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE, PAYMENT_METHOD_LOOKUP_CODE, BANK_CHARGE_BEARER.
• Accounting flexfield references (CCIDs): ACCTS_PAY_CODE_COMBINATION_ID, PREPAY_CODE_COMBINATION_ID, DISC_TAKEN_CODE_COMBINATION_ID, RES_ENCUMB_CODE_COMBINATION_ID, RATE_VAR_CODE_COMBINATION_ID, RATE_VAR_GAIN_CCID, RATE_VAR_LOSS_CCID, FUTURE_DATED_PAYMENT_CCID, EXPENSE_CLEARING_CCID, MISC_CHARGE_CCID.
• Encumbrance and reservation controls: RESERVE_AT_COMPLETION_FLAG and RES_ENCUMB_CODE_COMBINATION_ID govern reservation accounting. The user's search term, purch_encumbrance_type_id, is related in function rather than name: Purchasing encumbrance type identifiers are held on the Purchasing side (PO_ENCUMBRANCE_TYPES / purchasing options), while Payables records the corresponding reserve account and flag here. When troubleshooting encumbrance mismatches between PO and AP, both the Purchasing encumbrance type and this view's RES_ENCUMB_CODE_COMBINATION_ID should be inspected together.
• Tax configuration: VAT_REGISTRATION_NUM, VAT_COUNTRY_CODE, VAT_CODE, NON_RECOVERABLE_TAX_FLAG, TAX_ROUNDING_RULE, DEFAULT_RECOVERY_RATE, CASH_BASIS_ENC_NR_TAX.
• Control flags and numbering: HOLD_UNMATCHED_INVOICES_FLAG, EXCLUSIVE_PAYMENT_FLAG, MATCH_OPTION, USE_POSITIONS_FLAG, MANUAL_VENDOR_NUM_TYPE, VENDOR_NUM_START_NUM, RECEIPT_ACCEPTANCE_DAYS, FUTURE_PERIOD_LIMIT.
• Audit and context: ORG_ID, BUSINESS_GROUP_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1–15.

Common Use Cases and Queries

Typical uses include verifying Payables setup per reporting currency set, comparing encumbrance and reservable account configuration against Purchasing options, auditing tax and payment defaults, and driving AP integrations that must respect operating unit context. Note the columns projected as NULL — these are placeholders retained for column-order compatibility.

SELECT org_id,
       invoice_currency_code,
       payment_currency_code,
       res_encumb_code_combination_id,
       reserve_at_completion_flag,
       hold_unmatched_invoices_flag,
       match_option
FROM   fin_system_params_all_mrc_v
WHERE  org_id = :p_org_id;

Because MRC views depend on the CLIENT_INFO operating unit context, callers should initialize the org context (via FND_CLIENT_INFO or the standard APPS initialization) before querying, and should confirm the view exists in the target instance, since the ETRM metadata marks it as not implemented in the documented database.