Search Results gl_bc_packet_arrival_order_u2

Overview

GL.GL_BC_PACKET_ARRIVAL_ORDER is a budgetary control infrastructure table in the General Ledger schema of Oracle E-Business Suite. It maintains the processing sequence for budgetary control packets, ensuring that packets are evaluated by the Funds Checker in deterministic arrival order. Each row carries a sequence number, and lower arrival sequence values receive higher processing priority. The table also records whether a given packet alters funds availability for later packets, which allows the Funds Checker to correctly cascade or isolate funds impact across a batch of transactions.

In Oracle EBS 12.1.1 and 12.2.2, this table is populated and consumed internally by the budgetary control engine rather than by end-user forms. It is a transactional queue-ordering structure whose rows are short-lived and tied to the lifecycle of a budgetary control packet. Based on the foreign-key and uniqueness structure, its heuristic Data Vault classification is satellite-leaning: it hangs off the packet and ledger business keys and stores descriptive, context-dependent attributes (arrival sequence and funds-affect flag) rather than serving as an independent hub. Teams modeling this table in a warehouse should treat it as a satellite subordinate to a packet/ledger hub-and-link structure.

Key Information Stored

• ARRIVAL_SEQ — Numeric sequence defining packet processing order; lower values are processed first. This column is both the declared primary key (GL_BC_PACKET_ARRIVAL_ORDER_PK) and a unique business-key candidate via GL_BC_PACKET_ARRIVAL_ORDER_U2.
• PACKET_ID — Budgetary control packet defining column and the surrogate identifier linking each row to its packet. It is a unique business-key candidate via GL_BC_PACKET_ARRIVAL_ORDER_U1.
• LEDGER_ID — Ledger defining column; scopes each packet's arrival ordering to a specific ledger. Documented as participating in a foreign-key relationship (LEDGER_ID) and as the leading column of unique index GL_BC_PACKET_ARRIVAL_ORDER_U3.
• AFFECT_FUNDS_FLAG — Indicates whether an already-processed packet affects available funds for later-arriving packets; read by the Funds Checker to determine inter-packet impact.
• LAST_UPDATE_DATE — Standard Who audit column recording the last modification timestamp.
• LAST_UPDATED_BY — Standard Who audit column capturing the user or process that last updated the row.

The composite unique index GL_BC_PACKET_ARRIVAL_ORDER_U3 spans LEDGER_ID, AFFECT_FUNDS_FLAG, ARRIVAL_SEQ, and PACKET_ID, providing an efficient access path for the Funds Checker's ledger-scoped, flag-aware, sequence-ordered reads. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, while its three unique indexes reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

Primary consumers are the budgetary control and Funds Checker processes, which read packets in ARRIVAL_SEQ order for a given ledger and evaluate AFFECT_FUNDS_FLAG to decide whether prior packets alter availability. Support and diagnostic scenarios include identifying stuck or misordered packets, confirming processing order for a ledger, and auditing funds-impact behavior. A representative query follows:

• Retrieve ordered packets for a ledger: SELECT PACKET_ID, ARRIVAL_SEQ, AFFECT_FUNDS_FLAG FROM GL.GL_BC_PACKET_ARRIVAL_ORDER WHERE LEDGER_ID = :ledger ORDER BY ARRIVAL_SEQ;
• Find funds-affecting packets: filter by AFFECT_FUNDS_FLAG = 'Y' to isolate packets that change availability for successors.
• Audit recent activity using LAST_UPDATE_DATE and LAST_UPDATED_BY to trace the process that last touched a row.
• Use the documented base query selecting PACKET_ID, LEDGER_ID, ARRIVAL_SEQ, AFFECT_FUNDS_FLAG, LAST_UPDATE_DATE, and LAST_UPDATED_BY for reconciliation extracts.

Related Objects

• GL.GL_BC_PACKETS — Parent packet definition joined on PACKET_ID = PACKET_ID; supplies packet header context for each arrival-order row.
• GL.GL_LEDGERS — Ledger master joined on LEDGER_ID = LEDGER_ID for ledger name and currency context.
• GL_BC_PACKET_ARRIVAL_ORDER# — The underlying base object referenced by this synonym/view, per the dependency section.
• Funds Checker / Budgetary Control engine routines — Internal PL/SQL consumers that read rows in ARRIVAL_SEQ order and interpret AFFECT_FUNDS_FLAG.
• Standard Who audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY) tie rows to FND audit conventions for tracing.