Search Results copy_process_instructions

Overview

GMD_PROCESS_INSTR_UTILS is an Oracle EBS Process Manufacturing (OPM) utility package in the APPS schema. It centralizes low-level logic for managing process instructions, the operation-level directives attached to recipes and routings. Process instructions describe what a shop-floor operator must do at a given operation, which resources and activities apply, and in what sequence. This package handles copying, array-building, and acknowledgement propagation of that data so the higher-level Recipe Designer, Routing Designer, Version Control and Search/Replace modules do not each reimplement it. In EBS 12.1.1 and 12.2.2, the package is delivered as VALID and depends only on the standard SYS.STANDARD package and the APPS.GMO_DATATYPES_GRP collection type, indicating it is a foundational element of the OPM process instruction tier rather than a standalone business API.

Key Procedures and Functions

The documented entry points fall into three functional groups:

• Copy routines — COPY_PROCESS_INSTRUCTIONS, COPY_PROCESS_INSTR, and COPY_PROCESS_INSTR_ROW replicate process instruction definitions. They support the copy/versioning workflows used when a recipe or routing is duplicated, letting calling packages clone instruction headers, individual instructions, and single instruction rows without external orchestration.
• Array construction — BUILD_ARRAY assembles a PL/SQL collection (using GMO_DATATYPES_GRP types) from process instruction data, enabling bulk processing and in-memory manipulation before persistence.
• Acknowledgement routines — SEND_PI_ACKN, DESG_SEND_PI_ACKN, and DESG_SEND_VER_PI_ACKN emit process instruction acknowledgement events, likely for upstream/downstream integration and version-aware messaging. GET_DESG_INVOKE_PI_ID and SET_DESG_INVOKE_PI_ID act as accessor/mutator pairs maintaining a package-level designation of the invoking process instruction identifier, used to correlate acknowledgements with their originating transaction.

Ten documented procedures/functions are catalogued in ETRM, with the package classified as OTHER (not a public Open Interface API).

Tables Accessed

The package references these tables through APPS synonyms:

• GMD_RECIPES, GMD_RECIPES_B — recipe headers and base rows that own the process instructions.
• GMD_OPERATIONS_B, GMD_OPERATION_ACTIVITIES, GMD_OPERATION_RESOURCES — operation definitions, activities performed at each operation, and resources consumed or produced, which form the context of an instruction.
• FM_ROUT_HDR, FM_ROUT_DTL — routing headers and details for process instruction attachment at the routing level.
• FM_FORM_MST, FM_MATL_DTL — formula master and material detail records linked to instruction-driven execution.
• MTL_SYSTEM_ITEMS_KFV — item flexfield view for validating and resolving instruction item references.
• PLITBLM — the standard PL/SQL integer table used for bulk array operations.

These tables are read for validation/context and written when copying or acknowledging instruction data.

Usage Notes

GMD_PROCESS_INSTR_UTILS is not intended for direct customer invocation. It is referenced by GMD_RECIPE_DESIGNER_PKG, GMD_ROUTING_DESIGNER_PKG, GMD_RECIPE_GENERATE, GMD_VERSION_CONTROL, GMD_SEARCH_REPLACE_VERS and by itself — five dependent packages per ETRM. It therefore executes indirectly whenever a user saves or versions a recipe/routing in the OPM Recipe Designer or Routing Designer forms, or runs recipe generation and version-control concurrent programs. Custom extensions that manipulate OPM recipes should call the owning application APIs (Recipe Designer, Version Control) rather than this utility, because its interface and behaviour are internal and may change. Because it depends only on SYS.STANDARD and GMO_DATATYPES_GRP, it can be relied upon to remain stable across 12.1.1 and 12.2.2 at the schema level, but its ten documented procedures are not a supported public contract.