Search Results gem5_oprnline_id_s

Overview

GMD_OPERATION_ACTIVITIES_PUB is the public (PUB) application programming interface for managing operation activities within the Oracle E-Business Suite Process Manufacturing (OPM) module. In the EBS 12.1.1 and 12.2.2 releases, this package body serves as the externally callable business API that encapsulates the logic needed to create, maintain, and remove activity assignments tied to process operations. Operation activities represent the discrete tasks or activities performed within a manufacturing operation and are a foundational element of routing and recipe definitions used by Process Execution and Process Planning.

The PUB layer follows the standard Oracle EBS API architecture in which the public package validates inputs using the FND_API and FND_MSG_PUB message-handling framework, then delegates the actual transactional work to a corresponding private package, GMD_OPERATION_ACTIVITIES_PVT. This separation keeps the public interface stable while allowing internal validation and DML logic to evolve. The package is classified as a PUB API, confirming it is intended for external consumption by forms, concurrent programs, and custom extensions rather than internal-only use.

Key Procedures and Functions

The documented interface exposes three procedures, each aligned to a standard DML operation against the operation activity entity:

• INSERT_OPERATION_ACTIVITY — Creates a new operation activity record, validating the supplied attributes and persisting the row through the underlying private package.
• UPDATE_OPERATION_ACTIVITY — Modifies an existing operation activity, applying validation rules and performing the update through the private layer.
• DELETE_OPERATION_ACTIVITY — Removes an operation activity, typically enforcing referential and business-rule checks before deletion.

Each procedure participates in the FND_API error and message stack, so callers should inspect the returned message list for validation failures. Parameter lists are not reproduced here; callers should consult the package specification for exact signatures.

Tables Accessed

Based on the documented dependency metadata, the package body references several tables via APPS synonyms:

• GMD_OPERATION_ACTIVITIES — the primary transactional table holding operation activity rows that the three procedures insert, update, and delete.
• GMD_ACTIVITIES — the activity master, used to validate that a referenced activity exists and is valid.
• GMD_OPERATIONS and GMD_OPERATIONS_B — the operation definition and its base (multilingual) table, used to associate activities with a valid operation.
• GEM5_OPRNLINE_ID_S — a sequence used to generate surrogate keys, notably the identifier associated with the user's search term gem5_oprnline_id_s, which supplies operation line identifiers during inserts.
• FND_DUAL — a utility dual table used for lightweight lookups and single-row validations.
• PLITBLM — the standard PL/SQL integer table type used for bulk message handling within the API stack.

Usage Notes

This package is typically invoked from Oracle Process Manufacturing setup and execution forms, from concurrent programs that bulk-load or migrate operation activity data, and from custom PL/SQL extensions that need to manipulate activities without bypassing validation. Because it is a PUB API, it is safe to call from custom code, but callers must supply the standard API parameters (such as p_init_msg_list and p_commit) and handle the returned message list. The dependency on GEM5_OPRNLINE_ID_S confirms that the package obtains operation-line identifiers from that sequence during insert processing, which is relevant when troubleshooting key-generation or duplicate-key issues in customer implementations across both 12.1.1 and 12.2.2.