Search Results project_reference_enabled

Overview

MRP_AP_ORGANIZATIONS_V is a Master Scheduling/MRP (MRP) view that exposes the organizational and partner-modeling attributes used by Oracle Advanced Planning and scheduling processes. It is not a base object maintained by the Application Object Library; the ETRM metadata records it as "Not implemented in this database," indicating that the view is referenced by code paths or documented configurations but is not instantiated as a physical database object in the registered schema depicted in that metadata capture. In practice the view serves as a reporting and integration surface over planning organizations and their associated modeled trading partners.

The view is closely associated with the supplier and customer modeling feature that allows a planning organization to designate a specific supplier or customer, and site, as the "modeled" party for planning purposes. Because the view's predicate includes the ORG_INFORMATION_CONTEXT value 'CUSTOMER/SUPPLIER ASSOCIATION', it is a natural access point for queries that must resolve which modeled supplier or customer has been attached to an inventory or planning organization.

Underlying Base Objects

The ETRM metadata documents no base objects for this view ("Referenced base objects: none documented"), but the embedded view text reveals the underlying sources. These include HR_ORGANIZATION_INFORMATION, which supplies the modeled customer and supplier identifiers from ORG_INFORMATION1 through ORG_INFORMATION4 under the context 'CUSTOMER/SUPPLIER ASSOCIATION'; HR_ALL_ORGANIZATION_UNITS_TL, which supplies the translated partner name and language; MRP_AP_ORG_UNITS_SN, which supplies the business group identifier used as the operating unit; MRP_AP_MTL_PARAS_SN, which supplies organization code, calendar, weight and volume parameters, and project control attributes; and MRP_AP_MRP_PARAS_SN, which supplies the master organization identifier and organization identifier used as the row's primary planning key.

The joins are defined with outer joins directed from the planning organization parameters to the organization units, the translated names, and the customer/supplier association subquery, so an organization without a modeled partner still returns a row with null modeled identifiers.

Key Columns

• ORGANIZATION_CODE — The short code of the planning organization, taken from MP.ORGANIZATION_CODE.
• SR_TP_ID — The organization identifier presented as the source trading partner identifier.
• MASTER_ORGANIZATION — The master organization for the planning organization.
• PARTNER_TYPE — A literal value of 3, identifying the partner classification used by this view.
• PARTNER_NAME — The translated name of the partner organization.
• CALENDAR_CODE, CALENDAR_EXCEPTION_SET_ID — The calendar and exception set associated with the organization.
• OPERATING_UNIT — The business group identifier representing the operating unit.
• MAXIMUM_WEIGHT, MAXIMUM_VOLUME, WEIGHT_UOM, VOLUME_UOM — Capacity and unit-of-measure attributes.
• PROJECT_REFERENCE_ENABLED, PROJECT_CONTROL_LEVEL — Project manufacturing control flags.
• MODELED_CUSTOMER_ID, MODELED_CUSTOMER_SITE_ID — The modeled customer and site, derived from ORG_INFORMATION1 and ORG_INFORMATION2.
• MODELED_SUPPLIER_ID, MODELED_SUPPLIER_SITE_ID — The modeled supplier and site, derived from ORG_INFORMATION3 and ORG_INFORMATION4.
• RN1, RN2, RN3 — Sequence columns originating in the base snapshots, used to preserve source ordering.

Common Use Cases and Queries

A frequent requirement is to determine which organization has a given supplier defined as its modeled supplier. The MODELED_SUPPLIER_ID column supports that lookup directly:

SELECT organization_code, sr_tp_id, partner_name, modeled_supplier_id, modeled_supplier_site_id FROM mrp_ap_organizations_v WHERE modeled_supplier_id = :supplier_id;

The view is also used in integration extracts that publish planning organization attributes, calendars, and capacity parameters to external planning or analytics systems, and in reconciliation reports that compare modeled partner assignments across organizations. Because the modeled identifiers are stored as character data in HR_ORGANIZATION_INFORMATION and converted with TO_NUMBER, queries should filter on numeric values and account for rows where no association exists and the columns are null.