Search Results gl_transfer_submit_journal_imp

Overview

AP_SYSTEM_PARAMS_ALL_MRC_V is a multi-reporting-currency (MRC) view within the Oracle Payables (AP) module. Its documented product association is AP - Payables, and its description within the ETRM metadata is simply "MULTI-ORG MRC view." As an MRC construct, the view is intended to expose Payables system-level parameter (option) values across multiple reporting sets of books, allowing reporting and integration processes to read configuration settings that are otherwise maintained at a single functional level but must be presented in a multi-currency, multi-set-of-books context.

In Oracle EBS 12.1.1 and 12.2.2, MRC views such as this one are typically created to support environments that maintain more than one set of books (or, in later releases, primary and secondary ledgers). The view surfaces Payables system parameters — the option flags and accounting code combinations that drive invoice entry, payment processing, tax handling, and posting behavior — and lets a query obtain these values associated with a specific reporting set of books and reporting currency, rather than only the primary functional currency view.

It is important to note that the ETRM metadata records this object as "Not implemented in this database." This indicates that, within the specific environment being documented, the view does not physically exist, which is consistent with MRC views that are only deployed when multi-org or MRC functionality is enabled. Its role is nonetheless significant in reporting and integration contexts where cross-set-of-books Payables configuration must be reconciled or audited.

Underlying Base Objects

The documented view text selects from a set of Payables system parameters combined with an MRC source (aliased as MC) that supplies the reporting set of books and reporting currency values. The presence of the alias MC on columns such as MC.REPORTING_SET_OF_BOOKS_ID, MC.REPORTING_CURRENCY_CODE, and MC.AP_SECONDARY_SET_OF_BOOKS_ID indicates the view joins the base Payables system parameters record to its MRC equivalent, enriching the primary parameter row with the reporting set of books context.

The ETRM metadata lists no explicitly documented base objects ("Referenced base objects: none documented"). In typical Oracle EBS implementations, the underlying base table is AP_SYSTEM_PARAMETERS_ALL, with the MRC companion providing the multi-reporting-currency linkage. Because the documentation does not enumerate the base objects, consumers should treat the join target as environment-dependent and verify object definitions against the actual database dictionary before relying on relationships.

Key Columns

The view exposes a broad set of Payables configuration attributes alongside MRC context columns. Notable columns include:

• REPORTING_SET_OF_BOOKS_ID and REPORTING_CURRENCY_CODE — the MRC reporting set of books and its currency, the defining columns of this view.
• AP_SECONDARY_SET_OF_BOOKS_ID — the secondary set of books used for secondary accounting within the MRC model.
• SALES_TAX_CODE_COMBINATION_ID — the accounting code combination used for sales tax, relevant to tax configuration and reporting.
• ACCTS_PAY_CODE_COMBINATION_ID, DISC_LOST_CODE_COMBINATION_ID, DISC_TAKEN_CODE_COMBINATION_ID, PREPAY_CODE_COMBINATION_ID, INTEREST_CODE_COMBINATION_ID — the various liability, discount, prepayment, and interest accounting flexfield combinations.
• Gain/loss and rate variance combinations such as HOLD_GAIN_CODE_COMBINATION_ID, TRANS_GAIN_CODE_COMBINATION_ID, GAIN_CODE_COMBINATION_ID, LOSS_CODE_COMBINATION_ID, and RATE_VAR_CODE_COMBINATION_ID.
• Processing and posting options including RECALC_PAY_SCHEDULE_FLAG, AUTO_CALCULATE_INTEREST_FLAG, AUTO_TAX_CALC_FLAG, MATCH_ON_TAX_FLAG, REQUIRE_TAX_ENTRY_FLAG, and the various post-option columns (expense, discount, gain/loss, cash, future pay).

Common Use Cases and Queries

Typical use cases include auditing tax and accounting configuration across sets of books, validating that the sales tax code combination and related accounting combinations are consistently defined, and feeding downstream reporting that must reflect the reporting currency rather than the functional currency. A representative query is:

• SELECT REPORTING_SET_OF_BOOKS_ID, REPORTING_CURRENCY_CODE, SALES_TAX_CODE_COMBINATION_ID, ACCTS_PAY_CODE_COMBINATION_ID FROM AP_SYSTEM_PARAMS_ALL_MRC_V;
• To compare configurations across reporting books: SELECT REPORTING_SET_OF_BOOKS_ID, REPORTING_CURRENCY_CODE, AUTO_TAX_CALC_FLAG, REQUIRE_TAX_ENTRY_FLAG FROM AP_SYSTEM_PARAMS_ALL_MRC_V ORDER BY REPORTING_SET_OF_BOOKS_ID;
• To isolate the secondary set of books linkage: SELECT AP_SECONDARY_SET_OF_BOOKS_ID, SALES_TAX_CODE_COMBINATION_ID FROM AP_SYSTEM_PARAMS_ALL_MRC_V;

Because the view is documented as not implemented in this database and no base objects are enumerated, queries should be preceded by dictionary verification of the view and its dependencies in the target environment.