Results for “test_posting”

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

Overview

GL_SUBR_STA is the OPM Subsidiary Ledger Update process control table owned by the GMF schema in Oracle Process Manufacturing Financials. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the runtime status and parameter repository for the subsidiary ledger update (subledger posting) concurrent process that transfers OPM cost and accounting transactions into the General Ledger. Each row in GL_SUBR_STA represents a discrete run or control record of the subsidiary ledger update, capturing the process state, the accounting period and ledger context, the transaction categories eligible for posting, and the cumulative error and posting statistics generated during execution.

Because it stores process state, timing, counters, and control flags rather than descriptive master data, the table functions as transactional control metadata for the OPM-to-GL posting flow. Mined from its foreign key structure, the heuristic Data Vault classification for GL_SUBR_STA is hub-leaning. As a modeling suggestion, the table primarily acts as a hub of process identity anchored on REFERENCE_NO, with satellite-style attributes (state, counters, dates, flags) and link-style relationships to cost types, legal entities, and the subsidiary ledger detail tables.

Key Information Stored

The physical schema documents 79 columns. The surrogate primary key is GL_SUBR_STA_PK, defined on REFERENCE_NO, which uniquely identifies each subsidiary ledger update control record and is the single documented unique index (business-key candidate). The most significant columns include:

• REFERENCE_NO — Primary key and hub key identifying the process run.
• CURRENT_STATE, COMPLETION_IND, STARTED_BY, ABORTED_BY, ABORT_REASON — Process status and lifecycle attributes.
• START_TIME, END_TIME, SCHEDULED_ON — Execution timing for the run.
• GL_DATE, GL_PERIOD, GL_FISCAL_YEAR, PERIOD, FISCAL_YEAR, PERIOD_START_DATE, PERIOD_END_DATE, PERIOD_ID — Accounting period and GL date context.
• LEDGER_ID, LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME, CO_CODE — Ledger and legal entity scope for the posting.
• COST_TYPE, COST_TYPE_ID, COST_BASIS, COST_MTHD_CODE, PROCESS_CATEGORY — Costing context used to select transactions.
• UPDATE_STAGE, ERRORS_FOUND, ERRORS_POSTED, ERRORS_LIMIT, ROWS_POSTED — Runtime progress and error statistics.
• TEST_POSTING, POST_IC, POST_OP, POST_PM, POST_PO, POST_CM — Posting control flags by transaction category.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — Concurrent program and request linkage for auditability.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, DELETE_MARK, IN_USE — Standard audit and concurrency columns.

Common Use Cases and Queries

Typical use cases include monitoring subsidiary ledger update runs, diagnosing aborted or error-heavy postings, and auditing which periods and ledgers have been processed. The concurrent REQUEST_ID is the most common lookup key, since administrators trace a specific posting request back to its control record.

• Identify runs still in progress: SELECT REFERENCE_NO, CURRENT_STATE, START_TIME FROM GMF.GL_SUBR_STA WHERE COMPLETION_IND = 'N' AND IN_USE = 'Y';
• Review posting statistics for a request: SELECT REFERENCE_NO, ROWS_POSTED, ERRORS_FOUND, ERRORS_POSTED, ABORT_REASON FROM GMF.GL_SUBR_STA WHERE REQUEST_ID = :req_id;
• Audit by ledger and period: SELECT REFERENCE_NO, GL_PERIOD, GL_FISCAL_YEAR, LEDGER_ID, LEGAL_ENTITY_NAME FROM GMF.GL_SUBR_STA WHERE LEDGER_ID = :ledger AND GL_FISCAL_YEAR = :yr;

These patterns support reconciliation reporting and operational troubleshooting of the OPM-to-GL transfer.

Related Objects

GL_SUBR_STA participates in documented foreign key relationships. It references CST_COST_TYPES via COST_TYPE_ID and FV_LEGAL_ENTITIES via LEGAL_ENTITY_ID. Three child tables reference it through REFERENCE_NO: GL_SUBR_LED (GL_SUBR_LED.REFERENCE_NO), GL_MESG_TBL (GL_MESG_TBL.REFERENCE_NO), and GL_SUBR_TST (GL_SUBR_TST.GL_SUBR_TST_REFERENCE_NO). GL_SUBR_LED holds the subsidiary ledger detail lines, GL_MESG_TBL stores message and error text for the process, and GL_SUBR_TST carries test-mode data. Standard WHO and concurrent program columns (CREATED_BY, PROGRAM_ID, REQUEST_ID) link the table to FND_USER and FND_CONCURRENT_REQUESTS for audit and run details.