Results for “total_cost”

2 results




Overview
Explore in AI Chat

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

Overview

PO_COST_DTL is a table owned by the GML schema (Process Manufacturing Logistics) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores acquisition cost detail records associated with a purchase order or a stock receipt. Each row captures a discrete cost component — such as freight, duty, or handling — applied to a specific purchase order document, line, and acquisition cost definition. The table therefore acts as the transactional intersection between purchasing documents and the cost master, providing the granular detail that rolls up into landed or acquisition cost calculations.

Based on heuristic Data Vault classification mined from its foreign key structure, PO_COST_DTL is best modeled as a link table. It resolves a many-to-many relationship between purchasing document lines and acquisition cost definitions stored in the cost master. No hub or satellite classification is asserted in the metadata; the link designation is a modeling suggestion derived from the pattern of foreign key references surrounding the primary key.

Key Information Stored

The table contains 21 documented columns. The most significant are outlined below.

  • Primary key composite — PO_COST_DTL_PK is defined on (DOC_TYPE, POS_ID, LINE_ID, AQUI_COST_ID). This composite is both the surrogate unique identifier and the business-key candidate for the row.
  • DOC_TYPE — Document type discriminator; also a foreign key to SY_DOCS_MST. Distinguishes purchase order documents from stock receipt documents.
  • POS_ID — Identifier of the purchase order or receipt document to which the cost applies.
  • LINE_ID — Line-level identifier within the referenced document.
  • AQUI_COST_ID — Foreign key to PO_COST_MST, identifying the acquisition cost definition being applied.
  • COST_AMOUNT — The monetary value of the individual cost component for the referenced line.
  • INCL_IND — Inclusion indicator controlling whether the cost is included in the acquisition cost total.
  • TEXT_CODE — Foreign key to PO_TEXT_HDR, linking optional descriptive text to the cost line.
  • TOTAL_COST — Aggregated total cost amount associated with the record.
  • TOTAL_COST_FLAG — Flag indicating whether the record participates in a total cost computation.
  • TOTAL_COST_BASIS — Basis on which the total cost is calculated and apportioned.
  • PO_HEADER_ID / PO_LINE_ID and LINE_LOCATION_ID — Core purchasing identifiers tying the cost detail to the Oracle Purchasing header, line, and shipment structures.
  • TRANS_CNT, DELETE_MARK, and MIGRATION_IND — Standard concurrency control, logical deletion, and data-migration indicator columns.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The table is most commonly queried in landed cost and acquisition cost analysis, where costs must be attributed to specific PO lines and reconciled against the cost master. Typical reporting includes per-line cost breakdowns, unmapped or unreferenced cost codes, and validation of inclusion flags prior to cost roll-up.

A representative query joining the cost definition master and document type reference is structured as follows:

  • SELECT d.POS_ID, d.LINE_ID, m.COST_CODE, d.COST_AMOUNT, d.INCL_IND
  • FROM GML.PO_COST_DTL d, GML.PO_COST_MST m, GML.SY_DOCS_MST s
  • WHERE d.AQUI_COST_ID = m.AQUI_COST_ID
  • AND d.DOC_TYPE = s.DOC_TYPE;

Because DOC_TYPE is part of both the primary key and the foreign key to SY_DOCS_MST, it must be included in most join predicates to preserve uniqueness. Filtering on DELETE_MARK ensures logically deleted cost rows are excluded from reporting totals, and summing COST_AMOUNT grouped by POS_ID and LINE_ID produces the acquisition cost detail suitable for landed cost reconciliation.

Related Objects

  • PO_COST_MST — join on PO_COST_DTL.AQUI_COST_ID = PO_COST_MST.AQUI_COST_ID; supplies the cost definition.
  • SY_DOCS_MST — join on PO_COST_DTL.DOC_TYPE = SY_DOCS_MST.DOC_TYPE; identifies document type.
  • PO_TEXT_HDR — join on PO_COST_DTL.TEXT_CODE = PO_TEXT_HDR.TEXT_CODE; provides descriptive text.

These three foreign key relationships, documented in the ETRM metadata, are the principal structural dependencies that any query, form, or concurrent program referencing PO_COST_DTL must respect.