Results for “replenishment_destination_id”

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

Overview

The APPS.MRPBV_REPLENISHMENT_DSTNS view is a Master Scheduling/MRP (MRP) dictionary object that exposes replenishment destination information used by Oracle's sourcing-rule and bill-of-distribution logic. In Oracle EBS 12.1.1 and 12.2.2, this view functions as a reporting and integration layer over the underlying sourcing-rule and receipt-organization configuration, resolving the customer, address, and organization identifiers required to route replenishment supply to a destination. Because it is a read-only view (defined WITH READ ONLY), it is intended strictly for query and extraction purposes rather than transactional DML.

The view is registered as a valid synonym under the APPS schema and is owned by APPS, with referenced base objects documented against HZ_ and MRP_ synonyms in the 12.2.2 metadata. The presence of the hidden predicate '_SEC:SO.ORGANIZATION_ID' IS NOT NULL reflects the multi-tenant/multi-org security enforcement (VPD/OLS policy) applied to sourcing rules, ensuring that only destinations belonging to the operating context of the querying organization are returned.

Underlying Base Objects

The documented base objects are the HZ customer-model tables together with the MRP sourcing tables and HR organization information:

• MRP_SR_RECEIPT_ORG — the primary receipt-organization record tying a sourcing rule to a receiving organization.
• MRP_SOURCING_RULES — defines the sourcing rule type (1 for global/blanket, 2 for specific assignment) and identifier.
• HR_ORGANIZATION_INFORMATION — supplies the customer/supplier association context, with ORG_INFORMATION1 mapping to the customer and ORG_INFORMATION2 mapping to the site use.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_PARTIES — the Trading Community Architecture (TCA) hierarchy resolving customer, site, and address identifiers.

The 12.1.1-era view text references legacy RA_ tables (RA_ADDRESSES, RA_SITE_USES_ALL, RA_CUSTOMERS); in 12.2.2 these are mapped to their TCA HZ_ counterparts, reflecting the migration of customer data into the TCA model.

Key Columns

The view exposes the following columns, which correlate directly to the underlying sourcing and TCA structures:

• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — validity window of the replenishment destination.
• REPLENISHMENT_DESTINATION_ID — the sourcing rule identifier when the rule type qualifies as a destination.
• SOURCING_RULE_ID / BILL_OF_DISTRIBUTION_ID — decoded from SOURCING_RULE_TYPE, distinguishing sourcing-rule destinations from bill-of-distribution destinations.
• DESTINATION_ORGANIZATION_ID — the receiving organization for the replenishment.
• CUSTOMER_ID / CUSTOMER_SITE_ID / CUSTOMER_ADDRESS_ID — the TCA identifiers resolving the customer, site use, and address. The CUSTOMER_ADDRESS_ID column is the most commonly searched attribute, as it links the destination to a physical ship-to address.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY — standard audit columns supporting change tracking.

Common Use Cases and Queries

Typical scenarios include identifying which customer addresses serve as replenishment destinations, reconciling sourcing rules against ship-to site uses, and extracting address data for downstream distribution planning. A representative query to retrieve destinations by customer address is:

SELECT REPLENISHMENT_DESTINATION_ID, SOURCING_RULE_ID, DESTINATION_ORGANIZATION_ID, CUSTOMER_ID, CUSTOMER_SITE_ID, CUSTOMER_ADDRESS_ID FROM APPS.MRPBV_REPLENISHMENT_DSTNS WHERE CUSTOMER_ADDRESS_ID = :address_id;

Analysts also join the view to HZ_LOCATIONS or HZ_PARTY_SITES on CUSTOMER_ADDRESS_ID to obtain formatted address text, and filter on START_EFFECTIVE_DATE and END_EFFECTIVE_DATE to isolate currently active destinations. Because of the read-only and security predicates, queries should always be executed within the appropriate operating-unit context to avoid policy-driven truncation of results.