Results for “msc_pdr_parameters”

50+ results




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

Overview

MSC_PDR_PARAMETERS is a transactional configuration table in the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. Its stated purpose, per the ETRM dictionary, is to store the parameters that a user enters when running the Planning Detailed Reports. In practice, the table functions as a persisted record of report execution criteria: rather than discarding user selections after a report completes, ASCP retains them so that a planning report can be re-run with identical scope, audited, or shared between planners.

From a dimensional modeling perspective, the ETRM metadata classifies this object as standalone based on its mined foreign-key structure. In Data Vault terms, this suggests modeling MSC_PDR_PARAMETERS as a hub-like entity capturing a discrete report request event, with the extensive set of dimension identifiers (plan, organization, item, supplier, resource) acting as descriptive links to their respective reference tables rather than as parent-child relationships enforced within the table itself. This classification is a heuristic and should be validated against actual usage patterns before implementing a warehouse or reporting layer on top of it.

Key Information Stored

The table contains 25 documented columns. The most consequential are the scope-defining parameters and the audit columns:

No separate surrogate primary key column is documented in the ETRM column list; the row identity is therefore formed by the combination of the scoping columns (typically USER_ID, PLAN_ID, and the dimensional filters) in conjunction with the audit columns.

Common Use Cases and Queries

The principal use case is re-execution and audit of Planning Detailed Reports. A planner wishing to reproduce a report can read the stored parameter row and re-submit the concurrent request with identical scope. A second use case is security and access review: administrators can query which users have requested reports against which plans and organizations.

SELECT user_id, plan_name, organization_id, inventory_item_id,
       report_period_from, report_period_to, creation_date
FROM   msc.msc_pdr_parameters
WHERE  plan_id = :plan_id
ORDER  BY creation_date DESC;

A typical join enriches the report parameters with item and organization descriptions:

SELECT p.user_id, p.plan_name, msi.segment1 item, mp.organization_code
FROM   msc.msc_pdr_parameters p,
       mtl_system_items_b msi,
       mtl_parameters mp
WHERE  p.inventory_item_id = msi.inventory_item_id
AND    p.organization_id  = msi.organization_id
AND    p.organization_id  = mp.organization_id;

Reporting use cases include measuring report usage frequency by plan, identifying stale parameter sets that reference obsolete plans, and analyzing which ABC classes or planners drive the largest reporting volume.

Related Objects

The following objects are most significant in relation to MSC_PDR_PARAMETERS:

  • MTL_ABC_CLASSES — the sole documented foreign key, joined via ABC_CLASS_ID.
  • MSC_PLANS — the plan definition referenced by PLAN_ID and PLAN_NAME.
  • MTL_SYSTEM_ITEMS_B — item master, joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • MTL_PARAMETERS — inventory organization definition, joined on ORGANIZATION_ID.
  • FND_USER — identifies the requesting user via USER_ID.
  • MTL_CATEGORY_SETS_B / MTL_CATEGORIES_B — category set and product category resolution via CATEGORY_SET_ID and PRODUCT_CATEGORY_ID.
  • PO_VENDORS / AP_SUPPLIERS — supplier resolution via SUPPLIER_ID.
  • BOM_RESOURCES / BOM_DEPARTMENTS — resource and department resolution via RESOURCE_ID and DEPT_LINE_ID.
  • MSC_PDR_REPORTS (ASCP reporting layer) — the report execution and output structures that consume these parameters.

Because the table is standalone in the mined FK graph, most relationships are logical rather than enforced, and joins should be validated against the specific ASCP patch level in use on 12.1.1 or 12.2.2.