Search Results gms_bc_packets_n4

Overview

GMS.GMS_BC_PACKETS is the central transaction table for the budgetary control feature in Oracle Grants Accounting. It stores budgetary control packets — discrete sets of grant-related transactions that must be validated by the funds check engine before journal entries may be created. Each row represents a candidate transaction (or a rollup of transactions) awaiting evaluation against an award, project, task, resource, and funding pattern. The funds check program evaluates the packet, performs funds availability logic, and updates the RESULT_CODE column with a lookup value that records the outcome. When a packet passes its funds check and the corresponding balances are updated in GMS_BALANCES, the row is physically removed from GMS_BC_PACKETS. This design keeps the table relatively small and focused on in-flight activity rather than historical audit trails.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10, and all of its indexes are stored in APPS_TS_TX_IDX. The documented physical schema in Release 12.2.2 contains 138 columns. From a Data Vault modeling perspective, the mined metadata classification is link. This is a reasonable heuristic: the table's grain is the intersection of transaction, project, award, task, expenditure type, and funding pattern, so it naturally functions as a many-to-many association between business entities rather than as a standalone hub or a descriptive satellite.

Key Information Stored

The surrogate primary key is BC_PACKET_ID, enforced by the unique index GMS_BC_PACKETS_U1. The business-key context — that is, the columns that identify and characterize the packet — is carried by PACKET_ID together with PROJECT_ID, AWARD_ID, and TASK_ID, which appear in several non-unique indexes (GMS_BC_PACKETS_N1 and related). The most operationally significant columns include:

• PACKET_ID — the logical grouping identifier shared by all rows in a single budgetary control packet.
• PROJECT_ID, AWARD_ID, TASK_ID, TOP_TASK_ID — the grant structure the packet affects.
• EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE, ACTUAL_FLAG — the nature and timing of the underlying transaction.
• DOCUMENT_TYPE, DOCUMENT_HEADER_ID, DOCUMENT_DISTRIBUTION_ID, ADJUSTED_DOCUMENT_HEADER_ID — the source document lineage, indexed through GMS_BC_PACKETS_N4, N10, and N11.
• STATUS_CODE and RESULT_CODE — the processing state and the funds check outcome.
• EFFECT_ON_FUNDS_CODE — whether the packet consumes or releases funds.
• ENTERED_DR, ENTERED_CR, BURDENED_COST, BURDENABLE_RAW_COST — the monetary amounts carried into the check.
• FUNDING_PATTERN_ID, FUNDING_SEQUENCE, FP_STATUS — the funding rule applied to the packet.
• BUDGET_VERSION_ID, SET_OF_BOOKS_ID, PERIOD_NAME — the budgetary and accounting context.
• PARENT_BC_PACKET_ID, BURDEN_ADJ_BC_PACKET_ID — hierarchy for rollup and burden adjustment packets.
• AWARD_BUDGET_BAL, TASK_BUDGET_BAL, RES_BUDGET_BAL — snapshots of available balances at check time.
• REQUEST_ID, SESSION_ID, SOURCE_EVENT_ID — integration and concurrency control.

Common Use Cases and Queries

The most common reporting need is to inspect all rows belonging to a single packet and determine its funds check status:

SELECT PACKET_ID, PROJECT_ID, AWARD_ID, TASK_ID,
       EXPENDITURE_TYPE, ENTERED_DR, ENTERED_CR,
       STATUS_CODE, RESULT_CODE
FROM   GMS.GMS_BC_PACKETS
WHERE  PACKET_ID = :p_packet_id;

A related diagnostic query identifies packets that failed their check, using the RESULT_CODE or the FC_ERROR_MESSAGE column:

SELECT BC_PACKET_ID, PACKET_ID, RESULT_CODE, FC_ERROR_MESSAGE
FROM   GMS.GMS_BC_PACKETS
WHERE  RESULT_CODE <> 'P'      -- not passed
AND    TRUNC(LAST_UPDATE_DATE) >= TRUNC(SYSDATE)-7;

Reporting on funding pattern consumption typically joins through FUNDING_PATTERN_ID and FUNDING_SEQUENCE, while reconciliation with subledger activity joins on DOCUMENT_TYPE and DOCUMENT_HEADER_ID (index GMS_BC_PACKETS_N11). Users also query by SOURCE_EVENT_ID (GMS_BC_PACKETS_N13) when tracing activity originating from Grants integration events.

Related Objects

Foreign key relationships tie GMS_BC_PACKETS to the principal Grants and Projects master data:

• PA_PROJECTS_ALL via PROJECT_ID.
• PA_TASKS via TASK_ID and TOP_TASK_ID.
• PA_EXPENDITURE_TYPES via EXPENDITURE_TYPE.
• IGF_AW_AWARD_ALL via AWARD_ID.
• GMS_FUNDING_PATTERNS_ALL via FUNDING_PATTERN_ID.
• GL_SETS_OF_BOOKS_11I via SET_OF_BOOKS_ID.
• GMS_BALANCES receives the updated balances once a packet passes its check.

Related Grants Accounting objects include GMS_BC_PACKETS (parent/child rows via PARENT_BC_PACKET_ID and BURDEN_ADJ_BC_PACKET_ID) and the funds check concurrent program that reads from this table. Because the table is thin and transient, most historical reporting should be sourced from the balances and accounting tables rather than from GMS_BC_PACKETS itself.