Results for “mul_div_sign”

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

Overview

GL_SUBR_TST is a transient work table owned by the GMF schema, the Process Manufacturing Financials module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its function is tightly scoped: it holds the projected accounting entries generated when the Subledger Update process is executed in test mode. Running Update in test mode allows financial users to inspect the bookings that would be created in the General Ledger interface without committing them to the live subledger tables. Once the test run is reviewed and verified, the same population can be re-driven through a live Update. Because of this staging role, GL_SUBR_TST is a short-lived table — rows are typically purged or overwritten between test iterations and are not part of the permanent accounting audit trail.

From a data-modeling perspective, the documented foreign-key structure suggests a link classification under a Data Vault heuristic. The table sits at the intersection of master references (account, accounting unit, currency, ledger, policy/company, source, UOM, tax authority) and the operative subledger stream, so it functions as a relationship record rather than a pure descriptive satellite or a business hub.

Key Information Stored

The table carries 44 documented columns and is uniquely identified by the surrogate primary key SUBLEDGER_ID, enforced through the unique index GL_SUBR_TST_PK. No separate composite unique index is documented, so SUBLEDGER_ID is the sole business-key candidate on record.

• SUBLEDGER_ID — surrogate primary key for each test-run subledger line.
• DOC_TYPE, DOC_ID, LINE_ID — identify the source document and line that produced the booking.
• SUB_EVENT_TYPE, TRANS_SOURCE_TYPE — classify the accounting event and its originating transaction source.
• CO_CODE, LEDGER_CODE, ACCTG_UNIT_ID, ACCT_ID — the accounting context: company/policy, ledger, accounting unit, and natural account.
• CURRENCY_BASE, CURRENCY_TRANS, AMOUNT_BASE, AMOUNT_TRANS, EXCHANGE_RATE, MUL_DIV_SIGN — the dual-currency amounts and conversion controls for the booking.
• DEBIT_CREDIT_SIGN, GL_TRANS_DATE, GL_DOC_DATE, FISCAL_YEAR, PERIOD — the debit/credit indicator and GL dating/period placement.
• QUANTITY, QUANTITY_UM, PROJECT_NO — quantity captured with its unit of measure, plus any project association.
• TAXAUTH_ID, TAXABLE_BASE, TAXABLE_TRANS, REVERSAL_FLAG, FRONT_CURR_IND — tax authority and taxable amounts, reversal indicator, and front-currency flag.
• BATCH_NAME, TRANS_CNT, EXPORTED_DATE — grouping, count, and export status for the test population.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — the concurrent request and program that generated the test run, enabling traceability.

Common Use Cases and Queries

The primary scenario is pre-Update verification: a finance user runs the Subledger Update in test mode, then queries GL_SUBR_TST to confirm that debits and credits balance, that amounts land in the correct period, and that account/ledger assignments resolve as expected before committing a live run.

• Review all entries for a specific concurrent request: SELECT * FROM GMF.GL_SUBR_TST WHERE REQUEST_ID = :req;
• Check debit/credit balance by account: SELECT ACCT_ID, DEBIT_CREDIT_SIGN, SUM(AMOUNT_BASE) FROM GMF.GL_SUBR_TST GROUP BY ACCT_ID, DEBIT_CREDIT_SIGN;
• Trace a source document's projected entries: SELECT SUBLEDGER_ID, VOUCHER_ID, AMOUNT_BASE FROM GMF.GL_SUBR_TST WHERE DOC_TYPE = :dt AND DOC_ID = :id;
• Validate conversion arithmetic against EXCHANGE_RATE and MUL_DIV_SIGN, and confirm taxable amounts via TAXABLE_BASE and TAXAUTH_ID.

Reporting should treat results as provisional, since rows reflect a simulated, not posted, run.

Related Objects

• GL_ACCT_MST via ACCT_ID — natural account master.
• GL_ACCU_MST via ACCTG_UNIT_ID — accounting unit definition.
• GL_CURR_MST via CURRENCY_BASE and CURRENCY_TRANS — base and transaction currencies.
• GL_LDGR_MST via LEDGER_CODE — ledger definition.
• GL_PLCY_MST via CO_CODE — company/policy mapping.
• GL_SRCE_MST via TRANS_SOURCE_TYPE — transaction source definition.
• GL_SUBR_STA via GL_SUBR_TST_REFERENCE_NO — reference status linkage.
• SY_UOMS_MST via QUANTITY_UM — unit of measure master.
• TX_TAXA_MST via TAXAUTH_ID — tax authority master.