Results for “gmd_status_pub”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.GMD_STATUS_PUB is a public PL/SQL package body that belongs to the Oracle Process Manufacturing (OPM) product family within Oracle E-Business Suite. Its principal business function is to manage status transition logic for process manufacturing entities such as recipes, routings, operations, and items. In OPM, each of these entities carries a controlled lifecycle status (for example, draft, approved, or obsolete) defined in the GMD_STATUS tables. The GMD_STATUS_PUB package encapsulates the rules that validate and apply a change from one status to the next, so that calling programs do not need to manipulate the underlying status tables directly. The package is classified as a PUB (public) API, meaning it is intended for invocation by other Oracle applications and by customer extensions rather than being restricted to internal use.
Key Procedures and Functions
The ETRM metadata documents a single public procedure for this package:
- MODIFY_STATUS — This procedure performs the status transition for an OPM entity. It verifies that the requested change is permissible under the defined status workflow and then updates the entity's status. The package body also contains internal helper logic, such as the private validate_operation procedure, which checks whether resources have been attached to every activity of an operation before the operation is allowed to advance in status. The header comment for modify_status indicates that the API returns a return code to the caller, consistent with the standard FND_API error-handling convention used elsewhere in the package, where x_return_status is set to values such as FND_API.G_RET_STS_SUCCESS or FND_API.G_RET_STS_ERROR. The package also includes a debug-flag function used to control diagnostic logging through FND_LOG.
Tables Accessed
The package reads and writes the OPM status model and validates the entities being transitioned. Documented tables include:
- GMD_STATUS, GMD_STATUS_B, and GMD_STATUS_NEXT — the definition of valid statuses and the permitted next-status transitions.
- GMD_RECIPES, GMD_RECIPES_B, GMD_RECIPE_VALIDITY_RULES — recipe headers and their validity constraints.
- GMD_ROUTINGS_B, GMD_OPERATIONS_B, GMD_OPERATION_ACTIVITIES, GMD_OPERATION_RESOURCES — routings, operations, activities, and the resources attached to them.
- GMD_ITEM_SUBSTITUTION_HDR_B — item substitution headers linked to status control.
- FM_FORM_MST_B and FM_MATL_DTL — formula master and material detail records.
- MTL_SYSTEM_ITEMS — the inventory item master, used to validate the items associated with the entities.
Usage Notes
GMD_STATUS_PUB is invoked whenever an OPM entity must move to a new status. Typical callers include Oracle Forms-based maintenance screens for recipes, routings, and operations, concurrent programs that perform bulk status changes, and custom PL/SQL extensions. The ETRM metadata records that the package is referenced by ten other packages, confirming its role as a shared service within the OPM schema. Because the status tables form the foundation of OPM lifecycle control, customizations should call MODIFY_STATUS rather than updating the GMD_STATUS tables directly, thereby preserving transition validation and consistent error reporting.
-
PACKAGE: APPS.GMD_STATUS_PUB 12.1.1
-
PACKAGE: APPS.GMD_STATUS_PUB 12.2.2
-
SYNONYM: APPS.GMD_STATUS_B 12.1.1
-
SYNONYM: APPS.GMD_STATUS_B 12.2.2
-
SYNONYM: APPS.GMD_STATUS 12.2.2
-
SYNONYM: APPS.GMD_STATUS 12.1.1
-
SYNONYM: APPS.GMD_ROUTINGS_B 12.1.1
-
SYNONYM: APPS.GMD_ROUTINGS_B 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.FM_FORM_MST_B 12.1.1
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.GMD_RECIPES 12.1.1
-
SYNONYM: APPS.GMD_RECIPES 12.2.2