Search Results update_activity

Overview

GMD_ACTIVITIES_PVT is the private implementation layer of the Oracle Process Manufacturing (OPM) Activity API. It sits beneath the public package GMD_ACTIVITIES_PUB and provides the actual database logic for creating and maintaining activity records used throughout OPM shop floor and costing operations. Activities in OPM represent discrete production steps or operations that can be associated with routings, resources, and process instructions. The package header carries the revision identifier $Header: GMDVACTB.pls 115.4 2004/02/25, and the source notes authorship by Sandra Dulyk of OPM Development.

Because the package is classified as PVT (private), it is not intended for direct invocation by external callers. All access is expected to flow through the public wrapper package, which enforces the standard EBS API contract of p_api_version, p_init_msg_list, p_commit, and message/return status output parameters. This separation allows Oracle to evolve internal validation and persistence logic without disturbing the supported public interface.

Key Procedures and Functions

The documented package metadata identifies two public procedures within the body:

• INSERT_ACTIVITY — Creates a new activity record. The procedure accepts a version identifier, initialization and commit flags, and a activity table type (gmd_activities_pub.gmd_activities_tbl_type) carrying the rows to be inserted. It returns a message count, message list, and return status. Internally it declares a cursor (Cur_check_activity) that queries GMD_ACTIVITIES_B to detect an existing activity name, and declares exceptions for setup failure and duplicate activity, enforcing uniqueness before insertion.
• UPDATE_ACTIVITY — Modifies an existing activity record. It follows the same API contract pattern, validating the target row and applying changes to the underlying base and translation tables.

The body also contains an internal helper, set_debug_flag, which returns 'Y' when the FND_LOG runtime level is at or above LEVEL_PROCEDURE. A package-level variable initializes this flag, and debug output is emitted through gmd_debug.put_line. This replaced an earlier call to FND_PROFILE.VALUE('AFLOG_ENABLED') under Bug 3222090 (February 2004), aligning the package with the standard EBS logging framework.

Tables Accessed

• GMD_ACTIVITIES — The primary activity entity table, referenced through the APPS synonym. It holds the activity definition records maintained by this package.
• GMD_ACTIVITIES_B — The base (non-translated) table for activity data. The duplicate-check cursor in INSERT_ACTIVITY selects from this table by activity name.
• PLITBLM — The PL/SQL integer table type used for message handling in the EBS API message stack, supporting the x_message_list output.

Usage Notes

GMD_ACTIVITIES_PVT is referenced by one other package, consistent with its role as a subordinate implementation unit. It is typically invoked indirectly through the public API wrapper from OPM setup forms, from concurrent programs that load or maintain activity master data, and from custom extensions that need to create activities programmatically. Callers should supply a valid API version, pass p_commit = TRUE only when they control the surrounding transaction, and always inspect x_return_status and the message list rather than relying on exceptions. Direct calls to the PVT layer are not supported and may change without notice across releases such as 12.1.1 and 12.2.2.