Search Results arrival_seq

Overview

The GL_BC_PACKET_ARRIVAL_ORDER table is an Oracle General Ledger (GL) budgetary control object that governs the processing sequence of budgetary control packets. Budgetary control in Oracle EBS validates transactions against a control budget and performs funds reservation or funds checking when a source transaction (for example, a requisition, purchase order, or payable invoice) is submitted. Packets represent units of budgetary control work; this table determines the order in which packets are consumed by the budgetary control engine, and additionally records whether funds checking is to be performed.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This suggests the object behaves as a descriptive, contextual store attached to a parent business key rather than as a pure hub or link. Modelers should treat the ledger identifier as the principal business anchor and view the remaining attributes as satellite context describing packet processing characteristics for that ledger.

Key Information Stored

The documented physical schema contains six columns. The most significant are:

• ARRIVAL_SEQ — The arrival sequence of a budgetary control packet. This column is documented as the surrogate primary key, GL_BC_PACKET_ARRIVAL_ORDER_PK, and therefore uniquely identifies each row.
• PACKET_ID — The identifier of the budgetary control packet. It is documented as a business-key candidate via unique index GL_BC_PACKET_ARRIVAL_ORDER_U1.
• LEDGER_ID — The ledger for which packet processing is ordered. This is a foreign key to GL_LEDGERS, anchoring the row to a specific ledger.
• AFFECT_FUNDS_FLAG — The flag controlling whether the packet affects funds. In Oracle EBS terms, this determines whether the associated transaction performs funds checking or funds reservation. Its importance explains why the user searched for this term. It is documented as a high-cardinality business-key component in unique index GL_BC_PACKET_ARRIVAL_ORDER_U3.
• LAST_UPDATE_DATE and LAST_UPDATED_BY — Standard Oracle who-columns recording the date and user of the last modification.

Unique indexes U2 (ARRIVAL_SEQ) and U3 (LEDGER_ID, AFFECT_FUNDS_FLAG, ARRIVAL_SEQ, PACKET_ID) further reinforce the ordering and funds-affecting semantics of the table.

Common Use Cases and Queries

Typical scenarios include diagnosing funds-check ordering, verifying whether a packet affects funds, and reporting the arrival sequence per ledger.

• Identify funds-affecting packets for a ledger: SELECT packet_id, arrival_seq FROM gl_bc_packet_arrival_order WHERE ledger_id = :p_ledger AND affect_funds_flag = 'Y';
• Inspect processing order: SELECT packet_id, affect_funds_flag FROM gl_bc_packet_arrival_order WHERE ledger_id = :p_ledger ORDER BY arrival_seq;
• Audit recent changes: SELECT * FROM gl_bc_packet_arrival_order WHERE last_update_date >= SYSDATE - 1;

Reporting use cases include reconciliations between packed budgetary control transactions and ledger definitions, and troubleshooting when funds checking appears to skip or reorder transactions.

Related Objects

• GL_LEDGERS — Referenced via the documented foreign key GL_BC_PACKET_ARRIVAL_ORDER.LEDGER_ID; the principal join for resolving ledger names.
• GL_BC_PACKETS and other GL_BC_* budgetary control tables — Companion objects keyed by PACKET_ID that hold packet content and status.
• Budgetary control concurrent programs and APIs — Processing that consumes this ordering information when checking or reserving funds.
• GL_BC_PACKET_ARRIVAL_ORDER indexes — _PK, _U1, _U2, _U3, which enforce ordering and funds-affecting uniqueness.