Results for “sy_docs_mst”

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

Overview

MR_ACTN_TBL is a table in the GMP schema (Process Manufacturing Process Planning) within Oracle EBS 12.1.1 and 12.2.2. It stores MRP (Material Requirements Planning) action messages generated by the process manufacturing planning engine. These messages represent the actionable output of a planning run—recommendations such as reschedule, release, expedite, cancel, or adjust quantity for planned orders, process batches, and related supply/demand elements. In practice, the table serves as the persistent store behind the planner workbench action message display, enabling planners to review and act on net change recommendations produced by the MRP calculation.

From a modeling perspective, the relationship metadata suggests a satellite-leaning classification. The table carries descriptive attributes (quantities, dates, status flags, message codes) attached to a business key formed by planning run, item, warehouse, and action identity, rather than acting purely as a hub or a link between independent business entities. However, the presence of several foreign keys to master and parameter tables gives it additional link-like characteristics.

Key Information Stored

The table contains 27 documented columns. The most significant are:

• MRP_ID — Identifier of the planning run/parameter set that generated the message; joins to MR_PARM_DTL.
• ACTION_NO — Sequence number uniquely identifying the action message within a planning run.
• ITEM_ID — The planned item, referencing IC_ITEM_MST and IC_ITEM_MST_B.
• WHSE_CODE / WHSE_CODE_2 — Source and destination warehouses (transfer context), referencing IC_WHSE_MST.
• EVENT_DATE — The date the action message pertains to (e.g., suggested order date).
• INVENTORY_DATE — Relevant inventory/supply date.
• MESSAGE_CODE — Code classifying the recommendation (reschedule in/out, release, cancel, expedite, etc.).
• FORMULA_ID — Linked formula for process batches, referencing FM_FORM_MST.
• ACTION_QTY — Quantity associated with the recommended action.
• PROJ_BALANCE_QTY — Projected balance quantity driving the recommendation.
• DOC_TYPE / DOC_ID — Document reference (DOC_TYPE joins SY_DOCS_MST) identifying the underlying source document.
• ORGN_CODE — Organization context, referencing SY_ORGN_MST and SY_ORGN_MST_B.
• STATUS_IND — Status indicator for the message (e.g., new, processed).
• FMEFF_ID — Formula effectivity reference.

Two unique indexes define business-key candidates. The primary key MR_ACTN_TBL_PK is (MRP_ID, ACTION_NO). A second unique index, MR_ACTN_TBLI1, is (MRP_ID, ITEM_ID, WHSE_CODE, EVENT_DATE, ACTION_NO). No separate surrogate single-column key is documented; the composite keys serve as the identifiers.

Common Use Cases and Queries

The dominant use case is reporting and reviewing planning recommendations. Planners and reporting tools query by planning run (MRP_ID) and filter on MESSAGE_CODE or STATUS_IND to isolate actionable messages.

• Listing open reschedule messages for an item and warehouse:

SELECT a.ACTION_NO, a.ITEM_ID, a.WHSE_CODE, a.EVENT_DATE,
       a.MESSAGE_CODE, a.ACTION_QTY, a.PROJ_BALANCE_QTY
FROM   GMP.MR_ACTN_TBL a
WHERE  a.MRP_ID = :mrp_id
AND    a.MESSAGE_CODE IN ('RESCHEDULE_IN','RESCHEDULE_OUT')
AND    a.STATUS_IND = 'N';

• Aggregating recommended action quantities by item for a run:

SELECT ITEM_ID, WHSE_CODE, SUM(ACTION_QTY) total_action_qty
FROM   GMP.MR_ACTN_TBL
WHERE  MRP_ID = :mrp_id
GROUP BY ITEM_ID, WHSE_CODE;

• Joining to item master for descriptions when building a planner workbench-style report:

SELECT a.ACTION_NO, i.ITEM_DESC, a.EVENT_DATE, a.MESSAGE_CODE
FROM   GMP.MR_ACTN_TBL a, GMP.IC_ITEM_MST i
WHERE  a.ITEM_ID = i.ITEM_ID AND a.MRP_ID = :mrp_id;

Typical scenarios include net change analysis between planning runs, expedite/cancel exception reports, and feeding downstream execution or dashboard reporting.

Related Objects

The following objects are most significant based on the documented foreign key relationships:

• MR_PARM_DTL — Planning parameters; MR_ACTN_TBL.MRP_ID references this, tying messages to a run.
• MR_PEGG_TBL — Pegging detail; references MR_ACTN_TBL via MR_ID and ACTION_NO, linking each action to its pegging chain. This is the principal dependent child.
• IC_ITEM_MST / IC_ITEM_MST_B — Item master references via ITEM_ID.
• IC_WHSE_MST — Warehouse master, referenced twice via WHSE_CODE and WHSE_CODE_2.
• FM_FORM_MST — Formula master, referenced via FORMULA_ID.
• SY_DOCS_MST — Document type reference via DOC_TYPE.
• SY_ORGN_MST / SY_ORGN_MST_B — Organization references via ORGN_CODE.

These relationships confirm MR_ACTN_TBL as a central planning-output table, anchored to parameters, pegged to supply/demand, and enriched by item, warehouse, formula, and organization master data.