Results for “contract_amount”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The table POA_BIS_SAVINGS_EFC is a Purchasing (PO) module object owned by the PO schema. According to its ETRM description, it serves as an archive for the Euro functional currency project. In practical Oracle EBS 12.1.1 and 12.2.2 terms, this identifies it as a legacy migration and archival table rather than a transactional or runtime-driven object. It was created to preserve procurement savings and amount data as part of the historical conversion exercises associated with the Euro functional currency initiative, where purchasing contracts, potential savings, and purchase amounts needed to be retained outside the live transactional model during currency transition activities.

The Data Vault classification for this table is standalone, derived heuristically from its foreign key structure. As a modeling suggestion, this indicates the table functions as an independent entity within the source model, holding a discrete set of descriptive and numeric facts without participating in a broader hub-and-satellite or link topology driven by multiple parent hubs. Its single documented foreign key relationship confirms it is largely self-contained, with limited lineage into the surrounding schema.

Key Information Stored

The documented physical schema for version 12.1.1 records nine columns. The most significant of these, and the ones that should drive any query against this archive, are:

  • SET_OF_BOOKS_ID — The ledger identifier under which the archived savings data was recorded. This is a primary business-key candidate for separating records by accounting context.
  • SECURITY_GROUP_ID — References FND_SECURITY_GROUPS and enforces access control and data segregation, a common requirement for archived financial records.
  • CURRENCY_CODE — The functional currency of the stored amounts; given the table's purpose, this is typically the Euro or the pre-conversion functional currency.
  • CONTRACT_AMOUNT — Contracted procurement value at the time of archival.
  • NON_CONTRACT_AMOUNT — Spend associated with purchases not governed by a formal contract.
  • POT_CONTRACT_AMOUNT — Potential contract amount, capturing prospective or pipeline value.
  • PURCHASE_AMOUNT — The actual purchased value recorded for the archived record.
  • POTENTIAL_SAVING — The calculated procurement savings, central to the "savings" emphasis in the table name.
  • SHIP_TO_ORGANIZATION_ID — The ship-to organization, providing organizational context for the savings figures.

The metadata does not document an explicit surrogate primary key column, so the table appears to rely on business columns (such as SET_OF_BOOKS_ID combined with organizational and currency context) to distinguish rows. No unique indexes are listed in the provided ETRM extract.

Common Use Cases and Queries

Because this is an archival object, the principal use cases are historical reporting, audit, and reconciliation of the Euro functional currency conversion. Analysts and DBAs use it to compare pre-conversion savings figures against post-conversion transactional tables. A representative query pattern isolates records by ledger and currency:

  • SELECT SET_OF_BOOKS_ID, CURRENCY_CODE, SUM(PURCHASE_AMOUNT), SUM(POTENTIAL_SAVING) FROM POA_BIS_SAVINGS_EFC GROUP BY SET_OF_BOOKS_ID, CURRENCY_CODE;
  • Patterns joining back to purchasing contract and supplier source tables to reconstruct the original savings context during a specific conversion period.
  • Audit extractions filtered by SHIP_TO_ORGANIZATION_ID to verify organization-level savings totals.

The table is not recommended as a live reporting source; it should be treated as read-only historical evidence.

Related Objects

The documented foreign key establishes the most concrete dependency:

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID, controlling row-level access to archived records.
  • GL_SETS_OF_BOOKS / GL_LEDGERS — joined via SET_OF_BOOKS_ID to resolve the ledger name and accounting context.
  • PO_HEADERS_ALL / PO_LINES_ALL — the live purchasing tables against which archived savings and amounts are typically reconciled.
  • POA_BIS_SAVINGS — the presumed active counterpart whose rows this table archives.
  • HR_ORGANIZATION_UNITS — joined via SHIP_TO_ORGANIZATION_ID to resolve organization names for inventory and ship-to reporting.
  • FND_CURRENCIES — joined via CURRENCY_CODE for currency descriptions.

These relationships, together with the SET_OF_BOOKS_ID and SECURITY_GROUP_ID filters, form the standard join topology for any historical analysis of this Purchasing archive table.