Results for “tp_site_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MRP_AP_VENDOR_SITES_V is a reporting view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) module that consolidates supplier header and supplier site (address) information. Its principal function is to present vendor names and site details in a denormalized, partner-oriented format so that downstream planning, sourcing, and integration processes can consume supplier site data without directly joining the underlying staging tables.

The view is significant in the context of the user search term "partner_address." It exposes a dedicated PARTNER_ADDRESS column that concatenates the individual address components of a supplier site (address lines, city, state, zip, province, and country) into a single delimited string. This makes the view convenient for supply chain partner address reporting, where a single composite address value is required rather than many discrete columns. The PARTNER_TYPE column, hard-coded to the literal 1, identifies the partner as a supplier under the SR/TP (Source/Third Party) partner data model used within Oracle Advanced Supply Chain Planning (ASCP) and related MRP flows.

Underlying Base Objects

According to the documented view text, MRP_AP_VENDOR_SITES_V is defined over two objects:

• MRP_AP_VNDR_SITES_SN — the supplier site snapshot source, aliased as PVSA, supplying vendor site code, vendor site ID, and the address component columns.
• MRP_AP_VENDORS_SN — the supplier header snapshot source, aliased as PVV, supplying the vendor name and vendor ID.

The two are joined on VENDOR_ID (PVSA.VENDOR_ID = PVV.VENDOR_ID). Both base objects carry the "_SN" suffix, indicating they are snapshot tables maintained by the MRP/ASCP collections process, which periodically extracts supplier data from the Oracle Payables (AP) supplier model into staging tables used by the planning engine. The documented ETRM metadata records no separately catalogued base tables beyond these two, and the view is noted as "Not implemented in this database" in the excerpt, meaning it exists as a defined repository object but may not be deployed in every instance. The view also carries the Oracle Proprietary, Confidential Information designation.

Key Columns

• TP_NAME — Trading partner name, derived from the supplier/vendor name (PVV.VENDOR_NAME) in the vendor snapshot.
• TP_SITE_CODE — Trading partner site code, taken from the supplier site code (PVSA.VENDOR_SITE_CODE).
• SR_TP_ID — Source trading partner identifier, mapped from VENDOR_ID.
• SR_TP_SITE_ID — Source trading partner site identifier, mapped from VENDOR_SITE_ID.
• PARTNER_ADDRESS — The concatenation of ADDRESS_LINE1 through ADDRESS_LINE4, CITY, STATE, ZIP, PROVINCE, and COUNTRY, each separated by a comma and space. This is the column most relevant to the "partner_address" search.
• PARTNER_TYPE — A constant value of 1, classifying the record as a supplier-type partner.

Two internal columns, RN1 (from PVV) and RN2 (from PVSA), are also selected but are not exposed as named keys in the documented column list; they typically represent collection or sequence references from the snapshot process.

Common Use Cases and Queries

Typical uses include supplier site address lookups for planning reports, partner resolution within ASCP or MRP data extracts, and integration feeds requiring a single formatted partner address. A representative query retrieving supplier site addresses by vendor name is:

SELECT vendor_name, vendor_site_code, partner_address, partner_type
FROM mrp_ap_vendor_sites_v
WHERE vendor_name = :p_vendor_name;

To filter by a specific site address, the composite column can be searched conditionally:

SELECT vendor_name, vendor_site_code, partner_address
FROM mrp_ap_vendor_sites_v
WHERE partner_address LIKE '%&city%';

Because PARTNER_ADDRESS is a concatenated string and PARTNER_TYPE is a literal constant, queries that need structured address fields or partner type filtering beyond supplier identification should join to the underlying AP supplier tables instead. The view is best suited to read-only reporting and integration extraction rather than transactional processing.