Search Results process_staging

Overview

M4R_7B1_WSM_IN is an APPS-owned PL/SQL package that forms part of the Oracle E-Business Suite discrete manufacturing solution delivered through Oracle's legacy 7B1 / OSFM (Orderless Shop Floor Management) vertical, hosted within the M4R product schema. Its stated purpose is to provide the specification of the package M4R_7B1_WSM_IN, which is called from the Workflow process designated "M4R 7B1 OSFM Distribute WIP." The package therefore acts as the server-side engine for a workflow-driven WIP distribution activity: it evaluates staging records produced during the distribution of work-in-process information, validates them against bills of material routing structures and master item definitions, and drives collection-history updates and outbound notifications to trading partners. All procedures use the standard Oracle Workflow PL/SQL callback signature (item type, item key, activity ID, function mode, and result out), confirming that the package is invoked as one or more workflow function activities rather than as a standalone API.

Key Procedures and Functions

• PROCESS_NOTIFICATION — The workflow activity responsible for generating notification output from the WIP distribution process. As a Workflow-standard entry point it accepts the item type, item key, activity ID, function mode, and an IN OUT result value that returns the workflow result code. This is the procedure most likely to be examined when troubleshooting notification behavior in the OSFM distribute-WIP flow.
• PROCESS_STAGING — Reads and processes staging rows populated by the WIP distribution load, applying the business rules required before records are promoted or rejected.
• CHECK_VALID_RECORDS — Validates staged records for completeness and correctness prior to further processing.
• CHECK_CP_IMPORT_STATUS — Evaluates the import status of collection-plan/interface data, allowing the workflow to branch or fail when the inbound interface has not completed successfully.
• UPDATE_COLL_HIST — Updates collection history for a given internal control number with a supplied message, returning a workflow result.
• ADD_MSG_COLL_HIST — Inserts a collection-history message record, carrying an error string plus reference identifiers and header/message IDs for traceability.
• GET_TP_DETAILS — Resolves trading-partner header information into the party identifier and party site identifier used by downstream notification processing.

Package-level globals (g_debug_level, g_error_code, g_errmsg, g_exception_tracking_msg, g_intrl_cntrl_num, g_tp_frm_code) provide debug control, error capture, and context sharing across the procedures during a single workflow invocation.

Tables Accessed

The package reads and writes a defined set of APPS-synonymed tables. Routing and configuration data come from BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_NETWORKS, BOM_OPERATION_SEQUENCES, and MTL_PARAMETERS. Item context is drawn from MTL_SYSTEM_ITEMS_KFV. Work-in-process and transaction data are handled through WIP_DISCRETE_JOBS, MTL_MATERIAL_TRANSACTIONS_S, MTL_TRANSACTIONS_INTERFACE, and MTL_TRANSACTION_LOTS_INTERFACE. Staging and message data reside in M4R_7B1_OSFM_S1, M4R_WSM_DWIP_HDR_STAGING, M4R_WSM_DWIP_LOT_QTY_STAGING, and M4R_WSM_DWIP_MSG_STAGING. Trading-partner lookup uses ECX_TP_HEADERS, and workflow parameter passing uses WF_PARAMETER_LIST_T.

Usage Notes

M4R_7B1_WSM_IN is invoked exclusively from the "M4R 7B1 OSFM Distribute WIP" Oracle Workflow, with each procedure exposed as a function activity. It is not referenced by any other package (referenced by 0 packages), so callers outside this workflow must invoke it directly and supply a valid workflow item type, item key, and activity ID. Because processing depends on pre-populated staging tables, the workflow must run after the WIP distribution load has completed. Debug tracing can be enabled through g_debug_level, and failures surface through g_error_code and g_errmsg, with details written to the collection-history message tables.