Search Results presales_ordline_no

Overview

The OP_PRSL_DTL table is a core transactional entity within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. It stores detailed line-level information for two key pre-sales order types: order profiles and blanket sales agreements. This table functions as the child record to the header table OP_PRSL_HDR, capturing all item-specific details, pricing, shipping, and customer information for each line on a pre-sales document. Its role is central to managing the lifecycle of negotiated sales agreements before they are converted into standard sales orders, ensuring that all contractual line-item terms are persistently stored and can be referenced for order generation and fulfillment.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which reveal the critical data elements it manages. The primary key is a composite of PRESALES_ORD_ID and PRESALES_ORDLINE_NO, linking the line directly to its parent header and establishing its sequence. A unique alternate key on PRESALES_ORDLINE_ID also exists. Essential columns, as indicated by the extensive foreign key relationships, include ITEM_ID (linking to IC_ITEM_MST_B), various customer identifiers (SOLDTOCUST_ID, SHIPCUST_ID, BILLCUST_ID), and pricing terms like COMMISSION_CODE and TERMS_CODE. It also holds logistical data such as SHIP_MTHD, FROM_WHSE, SHIPPER_CODE, and port details (EMBARKATION_PORT, DEBARKATION_PORT). Quality and packaging specifications are tracked via QC_GRADE_WANTED and SALESPKG_ID.

Common Use Cases and Queries

Primary use cases involve querying and reporting on blanket agreement or order profile lines for analysis, conversion to sales orders, and auditing. Common SQL patterns include joining to the header and related master tables to get a complete view of a profile's lines. For instance, to list all active lines for a specific customer, a query might join OP_PRSL_DTL to OP_PRSL_HDR on PRESALES_ORD_ID and filter by the customer and header status. Another critical operation is validating lines before order generation, checking for holds (HOLDREAS_CODE), item validity, and completeness of shipping instructions. Reporting often aggregates data by item, sales representative (SLSREP_CODE), or customer to analyze pre-sales pipeline activity and agreement coverage.

Related Objects

OP_PRSL_DTL has a dense network of relationships, as shown in the metadata. Its most direct parent is the OP_PRSL_HDR table, linked via PRESALES_ORD_ID. It references numerous master data tables, including:

• Customer Data: OP_CUST_MST (for multiple customer roles).
• Item Data: IC_ITEM_MST_B, OP_GNRC_ITM, OP_PKGD_ITM.
• Logistics: IC_WHSE_MST, OP_SHIP_MTH, OP_SHIP_MST, OP_PORT_MST.
• Financial Terms: OP_TERM_MST, GL_CURR_MST, OP_COMMISSION.
• Quality: GMD_GRADES_B, QC_GRAD_MST.
• System Data: SY_ADDR_MST (for addresses), SY_UO (for units of measure), OP_TEXT_HDR.

These relationships enforce data integrity and ensure that line details align with established enterprise master data.