Results for “subledger_doc_sequence_value”

4 results




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

Overview

AP_ENCUMBRANCE_LINES_ALL is a Payables (AP) module table in the Oracle E-Business Suite 12.1.1 / 12.2.2 data model, owned by the AP schema. As its documentation states, it is the Encumbrance lines table, storing the individual encumbrance accounting lines generated when invoices and their distributions create, adjust, or reverse commitments against budgetary funds. Encumbrance accounting is the mechanism by which Oracle Purchasing and Payables reserve budget for commitments — requisitions, purchase orders, and unpaid invoices — and this table persists each resulting encumbrance entry at the line level, tagged with its General Ledger accounting distribution.

Functionally, AP_ENCUMBRANCE_LINES_ALL acts as the AP-side repository that feeds GL interface processing: lines written here are picked up by the Subledger Accounting (SLA) engine and transferred to General Ledger as encumbrance journal entries. The heuristic Data Vault classification mined from the foreign-key structure is link, suggesting the table is best modeled as a relationship/associative construct that connects an encumbrance event (via AE_HEADER_ID to AP_AE_HEADERS_ALL) to a chart-of-accounts distribution (CODE_COMBINATION_ID to GL_CODE_COMBINATIONS) and an encumbrance category (ENCUMBRANCE_TYPE_ID to GL_ENCUMBRANCE_TYPES).

Key Information Stored

The documented physical schema comprises 35 columns. The most significant of these are:

Common Use Cases and Queries

The table is queried principally for encumbrance reconciliation, budget-versus-commitment reporting, and GL interface troubleshooting. A typical join reconciles encumbrance lines to their accounting flexfield and encumbrance type:

  • Reporting total encumbered amounts by code combination and period: join AP_ENCUMBRANCE_LINES_ALL.CODE_COMBINATION_ID to GL_CODE_COMBINATIONS and filter on PERIOD_NAME.
  • Auditing a specific encumbrance document via SUBLEDGER_DOC_SEQUENCE_VALUE.
  • Tracing encumbrance entries back to their parent accounting event through AE_HEADER_ID to AP_AE_HEADERS_ALL.
  • Investigating reversals by filtering on REVERSAL_FLAG and ENCUMBRANCE_LINE_TYPE.
  • Operating-unit–scoped reporting via ORG_ID.

Related Objects

  • AP_AE_HEADERS_ALL — joined on AE_HEADER_ID; the parent accounting header.
  • GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID; the accounting flexfield.
  • GL_ENCUMBRANCE_TYPES — joined on ENCUMBRANCE_TYPE_ID; the commitment classification.
  • FND_DOCUMENT_SEQUENCES — joined on SUBLEDGER_DOC_SEQUENCE_ID; the document numbering source.
  • CST_ENCUMBRANCE_LINES — references this table via ENCUMBRANCE_LINE_ID; Cost Management encumbrance detail.
  • AP_ENCUMBRANCE_LINES_ALL_EFC — the EFC (multinational/archival) companion referencing ENCUMBRANCE_LINE_ID.

Together these relationships confirm the table's role as the central AP encumbrance line repository feeding General Ledger and cost accounting processes.