Results for “mrpfv_replenishment_dstns”

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

Overview

The MRPFV_REPLENISHMENT_DSTNS view is a read-only Oracle E-Business Suite dictionary object owned by the APPS schema and defined in the MRP (Master Scheduling/MRP) product. Its name reflects its purpose: it exposes replenishment destinations — the organizational or customer-facing endpoints toward which a sourcing rule directs supply. In MRP and its downstream planning flows, sourcing rules and bills of distribution determine where material is replenished, and receipt organization assignments (`MRP_SR_RECEIPT_ORG`) tie a sourcing rule to a specific receiving organization. This view denormalizes those relationships together with the destination organization details. It also surfaces customer and address information through the customer/supplier association captured in HR organization information, which is why the view is frequently surfaced when users search for concepts such as customer_address. The view carries the WITH READ ONLY clause and is marked VALID, indicating it is intended strictly for query, reporting, and integration consumption.

Underlying Base Objects

The view is defined over several base objects via APPS synonyms. Organization and destination data come from MTL_PARAMETERS (joined on ORGANIZATION_ID), HR_ALL_ORGANIZATION_UNITS (aliased AL, providing the organization name), and HR_ORGANIZATION_INFORMATION (aliased HR, with context CUSTOMER/SUPPLIER ASSOCIATION). Sourcing metadata is drawn from MRP_SOURCING_RULES and MRP_SR_RECEIPT_ORG. Customer and address attributes are resolved through the HR organization information columns ORG_INFORMATION1 (customer) and ORG_INFORMATION2 (site use), which link outward to customer master objects. In the documented 12.2.2 metadata, the referenced customer model uses the HZ schema: HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS. Older view text (as shipped in 12.1.1) references the legacy RA_CUSTOMERS, RA_ADDRESSES, and RA_SITE_USES_ALL tables, reflecting the transition to the Trading Community Architecture (TCA) customer model.

Key Columns

The view exposes sourcing-rule identity and type-decoded names, destination organization code and name, customer and address details, and effective dating. Notable columns include:

• SOURCING_RULE_NAME / SOURCING_RULE_ID — populated conditionally by DECODE on SOURCING_RULE_TYPE (type 1 vs. type 2), distinguishing the two sourcing rule classes.
• DESTINATION_ORGANIZATION_CODE / DESTINATION_ORGANIZATION_NAME — the receiving organization, from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS.
• CUSTOMER_NAME, CUSTOMER_ADDRESS, CUSTOMER_ID, CUSTOMER_SITE_ID, CUSTOMER_ADDRESS_ID — the customer and address/party-site data resolved through the customer/supplier association, directly relevant to customer_address lookups.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — the EFFECTIVE_DATE and DISABLE_DATE of the receipt organization assignment.
• REPLENISHMENT_DESTINATION_ID — mapped to SR.SR_RECEIPT_ID, the primary identifier of the destination row.
• "_DF" — the descriptive flexfield reference token _DF:MRP:MRP_SR_RECEIPT_ORG:SR.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

Typical uses include reporting on sourcing rule destinations, verifying which organizations replenish to which customers or addresses, and joining the view into custom planning extracts. The following query lists replenishment destinations with their customer address:

• SELECT sourcing_rule_name, destination_organization_code, customer_name, customer_address, start_effective_date FROM apps.mrpfv_replenishment_dstns;
• SELECT customer_name, customer_address_id FROM apps.mrpfv_replenishment_dstns WHERE customer_address_id IS NOT NULL;
• SELECT destination_organization_code, replenishment_destination_id FROM apps.mrpfv_replenishment_dstns ORDER BY destination_organization_code;

Because the view is read-only and governed by the _SEC:RECEIPT_ORGANIZATION_ID security predicate, query results are filtered by the caller's organization access, ensuring users see only the replenishment destinations permitted by their security profile.