Results for “sr_receipt_id”

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

Overview

APPS.MRP_SR_VIEW_MAKE_AT_V is a reporting view in the Oracle E-Business Suite Master Scheduling/MRP module. Its documented description is "Sourcing rule make at view," and it exposes the assignment of sourcing rules to receipt organizations together with the source details that determine where a supply is sourced from. The name and structure indicate that the view is intended for sourcing rules of the "Make At" type — that is, sourcing relationships resolved at a specific organization.

The view is useful wherever sourcing rule assignments must be reported across organizations in a supply chain. Because it joins receipt organization records to source organization records and decodes the source type through MFG_LOOKUPS, it provides a denormalized, human-readable picture of which source organization supplies a given receipt organization under a given sourcing rule. It is commonly consumed by sourcing analysis reports, planning data extracts, and integration interfaces that need to publish sourcing rule content outside of the standard planning engine. The view is owned by APPS and is recorded as VALID in the ETRM repository.

Underlying Base Objects

The documented base objects referenced by the view are MRP_SR_SOURCE_ORG_V (view), MRP_SR_RECEIPT_ORG (synonym), MFG_LOOKUPS (view), and FND_GLOBAL (package).

• MRP_SR_RECEIPT_ORG supplies the receipt side of the sourcing rule, contributing SOURCING_RULE_ID, SR_RECEIPT_ID, and RECEIPT_ORGANIZATION_ID.
• MRP_SR_SOURCE_ORG_V supplies the source side, contributing the source identifier, source organization identifier and code, vendor name, vendor site, allocation percentage, and rank, as well as the SOURCE_TYPE code.
• MFG_LOOKUPS resolves the SOURCE_TYPE code against LOOKUP_TYPE = 'MRP_SOURCE_TYPE' to produce the SOURCE_TYPE meaning exposed as SOURCE_TYPE in the view.
• FND_GLOBAL is an environment package referenced by the underlying objects; it typically supplies session context such as organization or user identifiers used by the source organization view.

The view's own definition restricts output to source types where SOUR.SOURCE_TYPE = 2, which corresponds to an organization-based source (as opposed to supplier-based sourcing) under the MRP_SOURCE_TYPE lookup.

Key Columns

• SOURCING_RULE_ID — Identifier of the sourcing rule to which the assignment belongs.
• SR_RECEIPT_ID — Identifier of the receipt-side assignment record; the join key linking the receipt organization to the source organization view.
• RECEIPT_ORGANIZATION_ID — The organization that receives the sourced supply.
• SR_SOURCE_ID — Identifier of the source assignment line.
• SOURCE_TYPE — Decoded meaning of the source type from MRP_SOURCE_TYPE.
• SOURCE_ORGANIZATION_ID and SOURCE_ORGANIZATION_CODE — The supplying organization's identifier and code.
• VENDOR_NAME and VENDOR_SITE — Supplier name and supplier site associated with the source. Although the view filters to organization-based sources, these columns are carried through from the source organization view to preserve supplier context where a source organization also carries a vendor definition. This is the column most relevant to a vendor_site search: it exposes the supplier site name for sourcing rows that include a vendor reference.
• ALLOCATION_PERCENT — Percentage of the receipt requirement allocated to this source when a sourcing rule contains multiple sources.
• RANK — Priority ranking of the source within the sourcing rule, used by the planning engine to sequence sources when allocation is applied.

Common Use Cases and Queries

Typical scenarios include listing all source organizations that supply a receipt organization, validating allocation percentages across source lines within a sourcing rule, and extracting vendor site references where the source carries a supplier definition.

Sample query listing sourcing assignments with source and vendor detail:

• SELECT sourcing_rule_id, receipt_organization_id, source_organization_code, vendor_name, vendor_site, allocation_percent, rank FROM apps.mrp_sr_view_make_at_v ORDER BY sourcing_rule_id, rank;
• SELECT source_organization_code, vendor_site, allocation_percent FROM apps.mrp_sr_view_make_at_v WHERE receipt_organization_id = :org_id AND sourcing_rule_id = :rule_id ORDER BY rank;
• SELECT vendor_site, COUNT(*) FROM apps.mrp_sr_view_make_at_v GROUP BY vendor_site ORDER BY 2 DESC;

Because the view is defined over the sourcing rule views, it should be treated as read-only. Queries should be filtered by organization or sourcing rule wherever possible, since unfiltered access across a large multi-organization installation returns a substantial row set.