Search Results gms_packet_ind_n2




Overview
Explore in AI Chat

Overview

GMS.GMS_BURDEN_ADJUSTMENTS_LOG is an Oracle EBS table in the GMS (Grants Management) schema that maintains the journal of burdenable raw cost adjustments performed across expenditure items, invoice distributions, manual encumbrances, purchase order distributions, and purchase requisition distributions. Its purpose is to maximize the burdenable raw cost by award and expenditure type, capturing each adjustment transaction together with the raw cost amount and the corresponding burdenable amount. The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10 and carries three documented indexes stored in APPS_TS_TX_IDX.

Heuristic Data Vault classification mined from the foreign key structure identifies this object as standalone. As a modeling suggestion, this indicates the table functions predominantly as a transactional journal rather than a pure hub, link, or satellite. Its grain is defined by the pair ADJUSTMENT_ID and LINE_NUM, where ADJUSTMENT_ID groups a set of adjustments and LINE_NUM sequences the individual entries within that set. Because the table records the outcome of adjustment processing rather than master reference data, it behaves like an append-oriented transaction journal whose lifecycle is tied to the expenditure and award configurations that drive burdening.

Key Information Stored

The surrogate primary key is ADJUSTMENT_ID, a NUMBER(15) column holding the unique identifier for a set of adjustments. The business-key candidate is the unique index GMS_ADJ_PK_U1, defined over ADJUSTMENT_ID and LINE_NUM, which together guarantee uniqueness of each adjustment line within a set.

Common Use Cases and Queries

Typical reporting scenarios reconcile the raw cost adjustment against its burdenable amount for a given award, expenditure type, or source document. Analysts querying the table frequently filter on DOCUMENT_HEADER_ID, DOCUMENT_DISTRIBUTION_ID, and DOCUMENT_TYPE to trace adjustments back to the originating expenditure item, invoice distribution, encumbrance, or requisition distribution. The unique index GMS_ADJ_PK_U1 is the access path most often used when retrieving a specific adjustment set in line order.

  • Reconciling adjustments for an award: select ADJUSTMENT_ID, LINE_NUM, AMOUNT, ADJ_BURDENABLE_AMOUNT where AWARD_ID equals the award of interest.
  • Tracing a source transaction: join on DOCUMENT_HEADER_ID and DOCUMENT_DISTRIBUTION_ID to identify all adjustments applied to a document.
  • Reviewing pending postings: filter on POSTED_FLAG and SOURCE_FLAG to isolate unposted or system-generated adjustments.
  • Analyzing burdenable recovery by expenditure type: aggregate AMOUNT and ADJ_BURDENABLE_AMOUNT grouped by EXPENDITURE_TYPE and AWARD_ID.
  • Packet-level processing checks: use PACKET_ID and BC_PACKET_ID with index GMS_PACKET_IND_N2 to audit adjustment packets.

Related Objects

The most significant referenced object is the award master table reached through the documented foreign key AWARD_ID.

  • IGF_AW_AWARD_ALL — referenced by GMS_BURDEN_ADJUSTMENTS_LOG.AWARD_ID; provides award attributes used to validate and report adjustment activity.
  • GMS_BURDEN_ADJUSTMENTS — the primary adjustment table sharing the ADJUSTMENT_ID and LINE_NUM key structure, against which this log records historical or processed entries.
  • GMS_AWARD_DISTRIBUTIONS — the award distribution entity aligned with AWARD_SET_ID and ADL_LINE_NUM.
  • PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURE_TYPES — source expenditure items and the expenditure type definitions referenced by EXPENDITURE_TYPE.
  • AP_INVOICE_DISTRIBUTIONS_ALL and PO_DISTRIBUTIONS_ALL — source documents for invoice and purchase order adjustments identified by DOCUMENT_HEADER_ID and DOCUMENT_DISTRIBUTION_ID.
  • PO_REQUISITION_DISTRIBUTIONS_ALL — source document for requisition distribution adjustments.