Search Results source_org

Overview

POS_RECEIPT_HEADERS_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It exposes a consolidated, denormalized projection of receipt header information drawn primarily from the receiving transaction table RCV_SHIPMENT_HEADERS, augmented with descriptive attributes resolved through joins to supplier, organization, location, and employee reference objects. The view does not store data; it is a query-only construct that presents receipt activity in a form suitable for reporting, inquiry screens, and integration extracts.

Because Oracle EBS stores receipt headers using surrogate identifiers (numeric foreign keys, coded lookup values), raw table queries return codes rather than business-meaningful text. POS_RECEIPT_HEADERS_V resolves those identifiers into human-readable values such as vendor name, supplier site code, ship-to location code, and receiver name, and it derives the SOURCE_ORG and SOURCE_TYPE attributes that describe the origin of the receipt. The view filters out rows where RECEIPT_NUM is null, so only fully identified receipt headers are surfaced. This makes it a reliable foundation for receipts-by-source and receipts-by-supplier analysis in a 12.1.1 or 12.2.2 environment.

Underlying Base Objects

The view is defined over the following documented objects in the APPS schema:

• RCV_SHIPMENT_HEADERS (synonym) — the primary driving table, supplying receipt number, receipt date, source code, shipment information, and foreign keys.
• PO_VENDORS (view) — outer-joined on VENDOR_ID to supply vendor name and the ATTRIBUTE14 supplier URL.
• PO_VENDOR_SITES_ALL (view) — outer-joined on VENDOR_SITE_ID to supply the supplier site code.
• ORG_ORGANIZATION_DEFINITIONS (view) — outer-joined on ORGANIZATION_ID to supply the source organization name.
• HR_LOCATIONS_ALL (synonym) — outer-joined on SHIP_TO_LOCATION_ID to supply the ship-to location code.
• PER_ALL_PEOPLE_F (synonym) — outer-joined on EMPLOYEE_ID to supply the receiver's full name.

Referenced package-level dependencies include FND_GLOBAL, HR_GENERAL, and HR_SECURITY; these typically support organization and security context resolution. All non-driving joins are outer joins, ensuring receipt headers are returned even when a referenced vendor, site, location, or employee record is absent.

Key Columns

• RECEIPT_NUM / RECEIPT_DATE — the receipt identifier and the creation date used as the receipt date.
• SOURCE_TYPE — the RECEIPT_SOURCE_CODE, decoded to indicate INTERNAL ORDER, INVENTORY, or VENDOR.
• SUPPLIER_ID / SUPPLIER — a decoded combination: for vendor-sourced receipts the vendor ID and name are returned; otherwise the organization ID and organization name are used.
• VENDOR_ID / VENDOR / SUPPLIER_SITE_ID / SUPPLIER_SITE — the raw vendor and site identifiers alongside their descriptive names and codes.
• ORGANIZATION_ID / SOURCE_ORG — the owning inventory organization identifier and its decoded organization name. SOURCE_ORG is the attribute most relevant to the "source_org" search, identifying the organization from which a receipt originated.
• SHIPMENT_NUM, SHIP_TO_LOCATION, SHIPPED_DATE, EXPECTED_RECEIPT_DATE — shipping and logistics detail.
• RECEIVER, NUM_OF_CONTAINERS, WAYBILL_AIRBILL_NUM, BILL_OF_LADING, PACKING_SLIP, FREIGHT_CARRIER_CODE, COMMENTS — operational receipt attributes.
• SHIPMENT_HEADER_ID — the underlying primary key, useful for joining back to base receiving tables.

Common Use Cases and Queries

Typical uses include receipts reporting by source organization, supplier performance analysis, and inbound shipment tracking. A representative query listing receipts with their source organization is:

• SELECT RECEIPT_NUM, RECEIPT_DATE, SOURCE_TYPE, SUPPLIER, SOURCE_ORG, SHIP_TO_LOCATION FROM APPS.POS_RECEIPT_HEADERS_V WHERE SOURCE_ORG = :org_name ORDER BY RECEIPT_DATE DESC;

Filtering by supplier and date range supports vendor receipt history extracts:

• SELECT RECEIPT_NUM, RECEIPT_DATE, VENDOR, SUPPLIER_SITE, SOURCE_ORG FROM APPS.POS_RECEIPT_HEADERS_V WHERE VENDOR = :vendor AND RECEIPT_DATE BETWEEN :from_date AND :to_date;

Because SOURCE_ORG resolves the organization name rather than its ID, users should apply ORG_ORGANIZATION_DEFINITIONS to obtain the ORGANIZATION_ID when integration targets require numeric keys. Note that the view enforces no organization security by itself; callers in a multi-org context should restrict results using session-appropriate organization filters.