Search Results gms_burden_adjustments_log




Overview
Explore in AI Chat

Overview

GMS_BURDEN_ADJUSTMENTS_LOG is a table in the GMS (Grants Accounting) product of Oracle E-Business Suite, documented in both releases 12.1.1 and 12.2.2 with VALID status. The table functions as a journal of burdenable raw cost adjustments. When burdenable raw costs recorded against an award must be corrected, reclassified, or otherwise adjusted after the fact, this table preserves the detail of each adjustment line so that downstream burdening and costing processes can account for the change. It is therefore an audit and reconciliation object rather than a master or transaction-entry object: it records what was adjusted, at what amount, and in which processing context.

The ETRM metadata classifies the table as standalone under a heuristic Data Vault assessment mined from its foreign-key structure. As a modeling suggestion, this indicates that the object is not a natural hub or link participant within the modeled relationship graph, but instead behaves as a satellite-like fact collection whose grain is defined by its own unique index rather than by conformance to shared business keys. Its only documented foreign key, AWARD_ID, points to IGF_AW_AWARD_ALL, so the adjustment journal is anchored to the award rather than to a project or expenditure item dimension.

Key Information Stored

The documented physical schema contains 20 columns. The most significant are listed below.

  • ADJUSTMENT_ID — the adjustment document identifier and part of the composite unique index GMS_ADJ_PK_U1.
  • LINE_NUM — the adjustment line number and the second component of GMS_ADJ_PK_U1, establishing the business-key grain of one row per adjustment line.
  • AWARD_ID — the foreign key to IGF_AW_AWARD_ALL, identifying the award whose raw costs are being adjusted.
  • AMOUNT — the adjustment amount recorded for the line.
  • ADJ_BURDENABLE_AMOUNT — the portion of the adjustment that is burdenable, used by burdening processes to recompute applied burden.
  • SOURCE_FLAG — indicates the origin or classification of the adjustment source.
  • DOCUMENT_HEADER_ID and DOCUMENT_DISTRIBUTION_ID — references to the document header and distribution being adjusted.
  • DOCUMENT_TYPE — the type of document subject to adjustment.
  • ADL_LINE_NUM — the corresponding line number on the adjusted source detail.
  • EXPENDITURE_TYPE — the expenditure type under which the adjusted cost is classified.
  • AWARD_SET_ID — the award set context associated with the adjustment.
  • POSTED_FLAG — indicates whether the adjustment line has been posted.
  • PACKET_ID and BC_PACKET_ID — packet identifiers used by the burdening and cost-collection concurrent processes.

The documented surrogate-side columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN are standard EBS audit columns. Note that the documented unique index is a business-key candidate rather than a declared single-column surrogate primary key.

Common Use Cases and Queries

Typical scenarios include reconciling burden adjustments back to awards, reporting unposted adjustment lines pending burden recalculation, and auditing who created or updated a given adjustment. A common query pattern joins the log to the award table on the documented foreign key:

  • SELECT l.ADJUSTMENT_ID, l.LINE_NUM, l.AWARD_ID, l.AMOUNT, l.ADJ_BURDENABLE_AMOUNT FROM GMS.GMS_BURDEN_ADJUSTMENTS_LOG l WHERE l.AWARD_ID = :award_id ORDER BY l.ADJUSTMENT_ID, l.LINE_NUM;
  • Filtering by POSTED_FLAG to isolate adjustment lines awaiting processing, or by PACKET_ID / BC_PACKET_ID to trace a specific burdening run.
  • Aggregating ADJ_BURDENABLE_AMOUNT by EXPENDITURE_TYPE to compare burdenable adjustments against the original raw cost recorded on the award.

Related Objects

  • IGF_AW_AWARD_ALL — joined on AWARD_ID to retrieve award attributes for the adjusted costs.
  • GMS_BURDEN_ADJUSTMENTS (and its header/distribution tables) — the adjustment document structure whose header and distribution IDs are referenced by this log.
  • GMS_AWARD_SET / award set structures — referenced through AWARD_SET_ID.
  • Burdening and cost-collection programs and their interface tables — consume PACKET_ID and BC_PACKET_ID to process adjustments.
  • Expenditure type reference data (e.g., FND lookup or PA_EXPENDITURE_TYPES) — resolved through EXPENDITURE_TYPE for reporting.

Because AWARD_ID is the only documented foreign key, any integration or report design should treat the award relationship as the confirmed join path and validate all other joins against the actual instance before relying on them.