Search Results from_organization_name

Overview

RCV_MSH_V is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM description identifies it plainly as "10SC ONLY - Retrofitted," meaning it is not part of the standard Oracle Receiving flow delivered to conventional implementations but rather a retrofitted object introduced for the 10SC (Government/Public Sector) configuration. Its name derives from the base table RCV_SHIPMENT_HEADERS, and the view is designed to present shipment header information in a denormalized, report-friendly form.

The view consolidates shipment header attributes with descriptive lookup values pulled from organization and HR location definitions, so that a consumer does not need to re-join those reference tables. It acts as a reporting and integration surface over the receiving shipment headers, particularly for the receipt sources "INVENTORY" and "INTERNAL ORDER," for which the ship-to location and ship-to organization naming must be resolved for human-readable output.

Underlying Base Objects

The documented base objects for RCV_MSH_V are RCV_SHIPMENT_HEADERS (synonym, the primary driving table), HR_LOCATIONS_ALL_TL (synonym, joined on SHIP_TO_LOCATION_ID with language equal to the user's session language), ORG_ORGANIZATION_DEFINITIONS (view, outer-joined on ORGANIZATION_ID), PO_VENDORS (view), PO_VENDOR_SITES (view), and RCV_SHIPMENT_LINES (synonym), together with the packages FND_GLOBAL, HR_GENERAL, HR_SECURITY, and the synonym RCV_TRANSACTIONS_INTERFACE. The view text shown is a UNION ALL: the first block selects shipments with RECEIPT_SOURCE_CODE in ('INVENTORY', 'INTERNAL ORDER') and returns organization names and HR location codes; the second block supplies vendor name and vendor site code from PO_VENDORS and PO_VENDOR_SITES for the remaining source types. This UNION structure is the defining architectural characteristic of the view. Note that the ETRM listing places RCV_TRANSACTIONS_INTERFACE among referenced objects, which is typically required for the location validation or security sub-routines implicit in HR_SECURITY and FND_GLOBAL.

Key Columns

• ROW_ID – the ROWID of the underlying RCV_SHIPMENT_HEADERS row.
• SHIPMENT_HEADER_ID – primary key linking back to the shipment header.
• RECEIPT_NUM, SHIPMENT_NUM, RECEIPT_SOURCE_CODE – the receipt identity and the source classification that drives the UNION branches.
• SHIP_TO_LOCATION – the human-readable location code sourced from HR.LOCATION_CODE; this is the column users identify when searching on "ship_to_location."
• SHIP_TO_LOCATION_ID, SHIP_TO_ORG_ID – the numeric identifiers behind the descriptive values.
• FROM_ORGANIZATION_NAME, FROM_ORGANIZATION_ID – the shipping organization, resolved via ORG_ORGANIZATION_DEFINITIONS.
• VENDOR_NAME, VENDOR_SITE_CODE – supplier descriptors populated in the vendor-source branch of the UNION.
• Waybill, ASN, carrier, packing and date columns – BILL_OF_LADING, WAYBILL_AIRBILL_NUM, ASN_TYPE, FREIGHT_CARRIER_CODE, EXPECTED_RECEIPT_DATE, SHIPPED_DATE, NUM_OF_CONTAINERS, PACKING_SLIP.
• Attributes 1–15 and the WHO columns – standard DFF and audit columns carried through unchanged.

Common Use Cases and Queries

The primary use case is resolving a shipment header to its ship-to location code and ship-to organization for reporting. A typical query joins the view to receipt lines or filters by receipt number:

• Locating receipts by destination: SELECT receipt_num, shipment_num, ship_to_location, from_organization_name FROM apps.rcv_msh_v WHERE ship_to_location = :p_location;
• Internal/inventory shipments: SELECT shipment_header_id, receipt_num, from_organization_name FROM apps.rcv_msh_v WHERE receipt_source_code IN ('INVENTORY','INTERNAL ORDER');
• Vendor receipts: SELECT receipt_num, vendor_name, vendor_site_code, bill_of_lading FROM apps.rcv_msh_v WHERE receipt_source_code NOT IN ('INVENTORY','INTERNAL ORDER');

Because the view already joins the location and organization references, it is convenient for ad-hoc inquiry and for feeding downstream interfaces. Queries must nevertheless account for the UNION semantics: organization and vendor columns are not populated simultaneously, so predicates on those columns should be aligned with the appropriate receipt source to avoid filtering out rows unexpectedly.