Results for “mrp_ad_si_capa”

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

Overview

MRP_AD_SI_CAPA is a table in the MRP schema (Master Scheduling/MRP product family) in Oracle EBS 12.1.1 and 12.2.2. The name follows the Oracle Applications convention of a repository table created during a supply-chain planning data collection or pre-processing operation, where the MRP_AD_SI_ prefix denotes a staging or work area used by the MRP planning engine before permanent data is merged into the core planning tables.

The table is documented as VALID in the ETRM 12.2.2 physical schema with 13 columns and carries a single foreign key to PO_APPROVED_SUPPLIER_LIST via ASL_ID, indicating that its rows describe approved-supplier-list (ASL) related planning data scoped to a specific organization and date range. The MINED Data Vault classification is standalone, meaning no dependent child tables or composite FK chains were detected. From a modeling standpoint, this suggests treating MRP_AD_SI_CAPA as a satellite-like object keyed by ASL_ID plus organization and date, rather than as a hub or a link table, though the standalone classification should be validated against actual usage before designing a warehouse layer.

Key Information Stored

The table's business identity centres on the approved supplier list reference and the planning organization:

• ASL_ID — surrogate reference to the approved supplier list entry in PO_APPROVED_SUPPLIER_LIST. This is the primary business-key candidate and the only documented foreign key.
• USING_ORGANIZATION_ID — the inventory organization in whose planning context the ASL record is being staged or evaluated. Combined with ASL_ID and FROM_DATE, this forms the natural composite unique key.
• FROM_DATE — the effective start date of the staging record, defining the planning horizon covered.
• RN — a row-number or sequence column used by the MRP engine for internal ordering and de-duplication during set processing.

Standard EBS WHO columns complete the structure: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN record auditing, while REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE identify the concurrent request and concurrent program that generated each row. There is no separately documented surrogate primary key column, so the ASL_ID / USING_ORGANIZATION_ID / FROM_DATE triad is the practical logical key, and ASL_ID is the documented FK.

Common Use Cases and Queries

Typical usage centres on diagnosing MRP planning results and auditing sourcing decisions. A common pattern joins the staging rows back to the supplier list to verify which approved sources were considered during a planning run:

• Reconcile a planning run to its inputs by filtering REQUEST_ID or PROGRAM_ID.
• List ASL records evaluated for an organization: SELECT asl_id, using_organization_id, from_date FROM mrp_ad_si_capa WHERE using_organization_id = :org_id.
• Trace which concurrent program produced stale or duplicate staging rows using PROGRAM_UPDATE_DATE and RN.
• Verify effective dating by comparing FROM_DATE against the ASL start date in PO_APPROVED_SUPPLIER_LIST.
• Support purging/archival scripts that delete rows older than a retained RUN_DATE.

Because the table is a staging structure, reporting should generally target the permanent MRP and PO tables after the concurrent program completes.

Related Objects

The documented foreign key drives the primary relationship, with several surrounding objects referenced by the WHO and concurrent-program columns:

• PO_APPROVED_SUPPLIER_LIST — joined on ASL_ID; the authoritative source of approved supplier definitions.
• MRP_SYSTEM_ITEMS / MRP_ITEM_SOURCING — sourcing rules that consume ASL data during the same planning flow.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the originating planning run.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_APPLICATION_ID and PROGRAM_ID.
• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for audit attribution.

No child tables or dependent views were detected, consistent with the standalone classification. Validation of any custom report or interface that reads MRP_AD_SI_CAPA should confirm the concurrent program lifecycle before relying on row persistence.