Results for “gl_transfer_error_code”

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

Overview

CST_ENCUMBRANCE_LINES is an Oracle E-Business Suite table owned by the BOM schema (Bills of Material) that stores encumbrance account distributions generated during periodic costing. In Oracle EBS 12.1.1 and 12.2.2, it acts as the costing-side staging and reference table for encumbrance entries that are subsequently transferred to the General Ledger via the Subledger Accounting (SLA) architecture. Each row represents a single encumbrance distribution line tied to a cost element, resource, activity, or repetitive schedule, expressed in both entered and accounted amounts.

From a Data Vault modeling perspective, the metadata mines this table as standalone (no dependent children). Given its 52 columns, surrogate key, and multiple foreign keys (to AP_ENCUMBRANCE_LINES_ALL, WIP_REPETITIVE_SCHEDULES, and GL_ENCUMBRANCE_TYPES), it is best modeled as a satellite attached to a costing encumbrance transaction hub, with the FK columns serving as links to the upstream source entities. This is a heuristic suggestion only; Oracle does not enforce Data Vault semantics.

Key Information Stored

The table is keyed by the surrogate primary key ENCUMBRANCE_LINE_ID, a system-generated identifier. Business-key candidates include the combination of AE_HEADER_ID and AE_LINE_NUMBER, which together identify the encumbrance line within its accounting header, and GL_SL_LINK_ID, which links the distribution back to the SLA journal.

• AE_HEADER_ID / AE_LINE_NUMBER / AE_LINE_TYPE_CODE — identify the parent accounting entry and its line classification.
• CODE_COMBINATION_ID — the accounting flexfield to which the encumbrance is posted.
• ENTERED_DR / ENTERED_CR / ACCOUNTED_DR / ACCOUNTED_CR — entered and accounted debit/credit amounts.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE — currency and conversion attributes.
• SOURCE_TABLE / SOURCE_ID — the originating transaction that created the encumbrance.
• COST_ELEMENT_ID / RESOURCE_ID / ACTIVITY_ID — the costing dimensions of the distribution.
• REPETITIVE_SCHEDULE_ID — links to the WIP repetitive schedule when applicable.
• PO_DISTRIBUTION_ID — links the encumbrance to its purchase order distribution.
• ENCUMBRANCE_TYPE_ID — references the GL encumbrance type definition.
• GL_SL_LINK_ID — the SLA subledger link for the resulting GL journal.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID.

Common Use Cases and Queries

Typical scenarios include reconciling periodic costing encumbrances to the GL, auditing purchase order encumbrances generated by Bills of Material, and reporting encumbrance balances by cost element or accounting flexfield.

• Reconcile a costing encumbrance to its GL journal via GL_SL_LINK_ID.
• Report encumbrances by CODE_COMBINATION_ID and COST_ELEMENT_ID.
• Trace encumbrances back to purchase order distributions using PO_DISTRIBUTION_ID.
• Investigate unaccounted or errored lines via ACCOUNTING_ERROR_CODE and GL_TRANSFER_ERROR_CODE.

A representative query joining to GL encumbrance types:

SELECT c.ENCUMBRANCE_LINE_ID, c.SOURCE_ID, c.ENTERED_DR, c.ENTERED_CR, g.ENCUMBRANCE_TYPE
FROM BOM.CST_ENCUMBRANCE_LINES c, GL_ENCUMBRANCE_TYPES g
WHERE c.ENCUMBRANCE_TYPE_ID = g.ENCUMBRANCE_TYPE_ID AND c.CREATION_DATE >= :p_start_date;

Related Objects

• AP_ENCUMBRANCE_LINES_ALL — referenced via ENCUMBRANCE_LINE_ID.
• WIP_REPETITIVE_SCHEDULES — referenced via REPETITIVE_SCHEDULE_ID.
• GL_ENCUMBRANCE_TYPES — referenced via ENCUMBRANCE_TYPE_ID.
• GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to resolve accounts.
• PO_DISTRIBUTIONS_ALL — joined on PO_DISTRIBUTION_ID.
• GL_IMPORT_REFERENCES / SLA journal tables — joined on GL_SL_LINK_ID to trace postings.