Results for “gl_setu_err”

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

Overview

GL_SETU_ERR is a table owned by the GMF schema (Process Manufacturing Financials) in Oracle EBS 12.1.1 and 12.2.2. Per the ETRM metadata, it stores "GL mapping setup errors found during Subsidiary Ledger Update process," and is explicitly documented as "Not currently used." This status is significant: while the object remains VALID in the data dictionary, Oracle's own documentation states it is dormant, meaning it is not populated or consumed by active application logic in supported releases. It should therefore be treated as a legacy or reserve structure rather than a functioning part of the Subsidiary Ledger Update or GL mapping configuration flow.

From a modeling perspective, the heuristic Data Vault classification derived from the foreign-key structure is link. The table's foreign keys reference GL_ACCT_TTL (via ACCT_TTL_TYPE) and SY_ORGN_MST / SY_ORGN_MST_B (via CO_CODE), placing GL_SETU_ERR at the intersection of account-title-type and operating-unit relationships. A link classification suggests the object was intended to associate setup-error records with the account and organization dimensions rather than serve as a standalone hub or as a satellite carrying descriptive attributes.

Key Information Stored

The documented physical schema for GMF.GL_SETU_ERR in 12.2.2 comprises 11 columns. The most operationally meaningful are:

• CO_CODE — operating unit / company code; a business-key component and a foreign key to both SY_ORGN_MST and SY_ORGN_MST_B.
• MESSAGE_CODE — the error or message identifier associated with the setup failure; a business-key component.
• ACCT_TTL_TYPE — the account title type involved in the mapping error; a business-key component and a foreign key to GL_ACCT_TTL.
• TRANS_CNT — a transaction counter, presumably recording the number of affected transactions at the time of error capture.
• TEXT_CODE — a code likely mapped to descriptive error or message text.
• DELETE_MARK — the standard EBS soft-delete flag.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking row provenance and last modification.

The surrogate primary key is defined by the unique index GL_SETU_ERR_PK (CO_CODE, MESSAGE_CODE, ACCT_TTL_TYPE). Notably, this composite is both the surrogate primary key and the source of business-key candidates, since each of the three columns participates in the unique constraint.

Common Use Cases and Queries

Because the table is documented as not currently used, practical use cases are largely diagnostic and historical. A consultant investigating why a Subsidiary Ledger Update failed in an older or customized environment might query the table to confirm whether error rows were ever captured:

• Listing all captured setup errors by operating unit: SELECT CO_CODE, MESSAGE_CODE, ACCT_TTL_TYPE, TRANS_CNT FROM GMF.GL_SETU_ERR WHERE DELETE_MARK = 0;
• Joining to the organization master to resolve company names: SELECT e.CO_CODE, o.NAME, e.MESSAGE_CODE FROM GMF.GL_SETU_ERR e, GMF.SY_ORGN_MST o WHERE e.CO_CODE = o.CO_CODE;
• Joining to GL_ACCT_TTL for the account title description associated with ACCT_TTL_TYPE.

Reporting against this object should be limited to migration audits, upgrade assessments (such as verifying whether any residual rows exist before an upgrade), and data-cleansing exercises. Any query that assumes live error capture during Subsidiary Ledger Update is likely to return no rows.

Related Objects

The documented foreign keys and primary key relationships identify the following significant related objects:

• SY_ORGN_MST — joined via CO_CODE; the primary organization master.
• SY_ORGN_MST_B — joined via CO_CODE; the organization master's base or secondary table.
• GL_ACCT_TTL — joined via ACCT_TTL_TYPE; defines account title types referenced by the error rows.
• GL_SETU_ERR_PK — the unique index enforcing the composite primary key (CO_CODE, MESSAGE_CODE, ACCT_TTL_TYPE).

Downstream tables, views, or APIs that consume GL_SETU_ERR are not documented in the ETRM metadata excerpt, consistent with the object's dormant status.