Search Results financials_system_parameters

Overview

The APPS.SO_DROP_SHIP_LINKS_V view is a reporting and integration construct within the Oracle E-Business Suite Order Entry (OE) module. It exposes the linkage between order management sales order lines and their associated drop-ship procurement documents, presenting a unified record set of purchase orders and purchase requisitions generated to fulfill drop-shipped sales order demand. The view combines data across the Order Management and Purchasing schemas, allowing downstream reporting, workflow, and custom integration components to retrieve the procurement artifacts tied to a given sales order line without joining the underlying base tables directly.

The view is defined as a UNION of two queries, producing a TYPE indicator of 1 for purchase orders and 2 for requisitions. This design supports reporting that must accommodate both fully approved purchasing documents and their requisition-stage predecessors. In the 12.1.1 and 12.2.2 releases, the view remained valid and is commonly referenced by drop-shipment tracking reports and order-line inquiry screens.

Underlying Base Objects

The documented base objects include FINANCIALS_SYSTEM_PARAMETERS, GL_SETS_OF_BOOKS, HR_LOCATIONS, PER_PEOPLE_F, PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_VENDORS, SO_DROP_SHIP_SOURCES, SO_LINES, and SO_LOOKUPS. Several packaged objects are also referenced: FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and OE_DROP_SHIP_PVT.

The central linking table is SO_DROP_SHIP_SOURCES, which maps a sales order LINE_ID to the PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID generated through the drop-ship sourcing process. PO_HEADERS and PO_LINES supply the purchasing header and line details for the TYPE = 1 branch, while PO_REQUISITION_HEADERS and PO_REQUISITION_LINES serve the TYPE = 2 branch. PER_PEOPLE_F supplies the buyer, constrained via BUSINESS_GROUP_ID matched to the operating unit's financials system parameters. The OE_DROP_SHIP_PVT package provides the GET_PO_STATUS function used to derive document status. HR_LOCATIONS and PO_VENDORS are outer-joined for ship-to and supplier detail, and SO_LOOKUPS supplies the DOCUMENT_TYPE meaning decoded from the 'DOCUMENT TYPE' lookup type.

Key Columns

• LINE_ID — Sales order line identifier; the primary join key to SO_LINES and the entry point for queries.
• TYPE — Discriminator. A value of 1 indicates a purchase order; 2 indicates a requisition.
• TYPE_LOOKUP_CODE / DOCUMENT_TYPE — Purchasing document type code and its decoded meaning derived from SO_LOOKUPS.
• PO_REQ_HEADER_ID / PO_REQ_NUMBER — The purchase order or requisition header identifier and number (SEGMENT1).
• BUYER_NAME — The full name of the buyer, sourced from PER_PEOPLE_F.FULL_NAME via the AGENT_ID on the purchasing header and filtered to active, employee-numbered records. This is the column most frequently cited in searches for "buyer_name."
• VENDOR_NAME — Supplier name, from PO_VENDORS for purchase orders or SUGGESTED_VENDOR_NAME for requisitions.
• STATUS — Document status; PO status via OE_DROP_SHIP_PVT for TYPE 1, or AUTHORIZATION_STATUS for requisitions.
• LINE_NUM, SUPPLIER_ITEM, ORDERED_UOM, QUANTITY, UNIT_PRICE, CURRENCY_CODE — Purchasing document line detail used for quantity and pricing reconciliation.
• NEED_BY_DATE, QUANTITY_RECEIVED, RECEIVED_UOM — Scheduling and receipt information from PO_LINE_LOCATIONS.

Common Use Cases and Queries

A typical use is identifying the buyer responsible for fulfilling a specific drop-shipped sales order line, or summarizing all drop-ship procurement activity by buyer. The following query lists procurement documents for a sales order line:

• SELECT line_id, type, document_type, po_req_number, buyer_name, vendor_name, status, quantity, unit_price FROM apps.so_drop_ship_links_v WHERE line_id = :p_line_id ORDER BY type, line_num;
• SELECT buyer_name, COUNT(*) FROM apps.so_drop_ship_links_v WHERE type = 1 GROUP BY buyer_name ORDER BY 2 DESC;
• SELECT po_req_number, document_type, status, supplier_item, quantity_received FROM apps.so_drop_ship_links_v WHERE vendor_name = :p_vendor;

Because the view references FND_GLOBAL and HR_SECURITY indirectly through its base objects, query results are subject to the security context of the session. Reporting or integration layers should therefore run under an appropriately configured user or a designated APPS connection. The UNION structure means callers should filter on TYPE when only approved purchase orders are required, avoiding dilution of results with requisition-stage records.