Search Results gmd_activities_pvt




Overview
Explore in AI Chat

Overview

GMD_ACTIVITIES_PUB is the public API package for Oracle Process Manufacturing (OPM) activity records, belonging to the discretely-named GMD (Process Manufacturing) module family that is embedded within Oracle E-Business Suite 12.1.1 and 12.2.2. Activities in OPM represent the discrete production steps performed within a batch — such as charging, mixing, heating, reacting, or packaging — and they form the operational backbone of a process manufacturing recipe or batch instruction set. The activities API therefore provides a supported, stable interface through which external programs and internal OPM components can create, amend, and remove activity definitions without directly manipulating the underlying base tables.

Key Procedures and Functions

The package exposes three documented public procedures, following the standard OPM insert/update/delete design pattern used across the GMD schema:

  • INSERT_ACTIVITY — Creates a new OPM activity record. It validates the incoming activity attributes and writes a corresponding row to the activity base tables. This procedure is the sanctioned route for introducing new activities into a recipe or batch.
  • UPDATE_ACTIVITY — Modifies an existing activity record, allowing attributes such as description, sequencing, or associated resource information to be changed after initial creation. It enforces the same validation rules applied at insert time.
  • DELETE_ACTIVITY — Removes an activity record, typically subject to referential integrity and business-rule checks that prevent deletion of an activity already consumed by downstream batch or recipe processing.

Because the procedures are the documented public surface, no parameter lists are reproduced here; callers should reference the package specification for exact signatures.

Tables Accessed

The package operates against the core OPM activity tables and supporting structures:

  • GMD_ACTIVITIES_B — The base (language-independent) activity table holding the primary activity definition and its identifying key.
  • GMD_ACTIVITIES — The translated activity table that stores language-dependent descriptive text associated with each activity. The _B/_T pair follows the standard Oracle multi-language support pattern.
  • PLITBLM — A generic OPM API infrastructure table used for message and error handling, providing the mechanism by which the three procedures return status information to callers.

All access is performed through APPS synonyms, so the package executes under the APPS schema rather than a GMD-specific schema.

Usage Notes

GMD_ACTIVITIES_PUB is invoked indirectly by OPM batch and recipe maintenance forms, and by other program units within the GMD stack. The ETRM metadata confirms it is referenced by the private companion package GMD_ACTIVITIES_PVT, which typically contains the validation and DML implementation logic that the public procedures wrap. The - show dependent code entries in the dependency listing indicate that both the package and its body are present and VALID in this ETRM snapshot.

Because the name carries the _PUB suffix, the package is the intended entry point for custom development and interface programs that need to maintain OPM activity data programmatically. Standard practice is to call the public procedures rather than writing directly to GMD_ACTIVITIES or GMD_ACTIVITIES_B, ensuring that validation, language handling, and error propagation through PLITBLM remain consistent. Callers should inspect the package specification for exact argument lists and expected return status values before coding, and should not assume the documented three procedures represent the only members of the package body.