Search Results pos_id

Overview

The PO_COST_DTL table is a core data object within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. It functions as the detailed repository for acquisition cost information associated with purchase orders and stock receipts. This table is critical for capturing and storing the granular cost components that constitute the total landed cost of procured items, enabling precise inventory valuation and cost accounting. Its existence is fundamental to the financial integration between procurement and inventory management processes, ensuring costs are accurately recorded and traceable back to specific transactional documents.

Key Information Stored

The table's structure is designed to link detailed cost elements to a parent cost header and the originating document. Its primary key is a composite of DOC_TYPE, POS_ID, LINE_ID, and AQUI_COST_ID, which uniquely identifies each cost detail record. The AQUI_COST_ID column is a foreign key linking to the PO_COST_MST table, establishing the relationship between the cost header and its detail lines. The DOC_TYPE indicates the source document type (e.g., purchase order, receipt), while POS_ID and LINE_ID typically reference the specific line from that document. Additional columns, such as TEXT_CODE (linked to PO_TEXT_HDR), allow for descriptive notes or references associated with the cost detail, providing necessary context for financial analysis and audits.

Common Use Cases and Queries

A primary use case is the generation of detailed cost analysis reports for procured materials, which is essential for understanding cost breakdowns and profitability. Finance and supply chain analysts frequently query this table to reconcile invoice amounts against received goods and their associated costs. A common SQL pattern involves joining PO_COST_DTL to its master table and document tables to retrieve a complete cost picture. For example:

• Identifying all cost details for a specific purchase order line to validate total landed cost.
• Aggregating cost details by item or receipt to support period-end inventory valuation adjustments.
• Troubleshooting discrepancies between expected and actual procurement costs posted to the general ledger.

Sample queries often filter on DOC_TYPE and POS_ID to isolate transactions and join with PO_COST_MST on AQUI_COST_ID.

Related Objects

PO_COST_DTL maintains integral relationships with several other EBS objects, as indicated by its foreign keys. Its most direct relationship is with the PO_COST_MST table via the AQUI_COST_ID column, where PO_COST_MST serves as the cost header. It also references PO_TEXT_HDR via TEXT_CODE for storing descriptive text. Furthermore, it links to SY_DOCS_MST on DOC_TYPE to validate the document type. These relationships ensure data integrity and enable comprehensive cost tracing from the detail line through the cost header to the original business document within the Process Manufacturing ecosystem.