Search Results gme_batchstep_act_pvt




Overview
Explore in AI Chat

Overview

APPS.GME_BATCHSTEP_ACT_PVT is a private PL/SQL package in the Oracle EBS Process Manufacturing (OPM/GME) product family. It encapsulates the core validation and maintenance logic for batch step activities — the individual production activities recorded against a batch step within a process manufacturing batch. The package belongs to the API classification PVT, indicating it is an internal, private implementation unit rather than a public, customer-facing API. It is not intended to be called directly by external integrations; instead, it supports the higher-level public APIs that manage batch creation and execution, notably GME_CREATE_STEP_PVT, which is referenced in the signature of INSERT_BATCHSTEP_ACTIVITY.

The package was authored under revision "$Header: GMEVACTS.pls 120.1 2005/06/06" and remains present in both EBS 12.1.1 and 12.2.2. Its responsibility is to resolve and validate the identifiers implied by a user's search input — organization code, batch number, and step number — and to persist, amend, or remove activity records on the underlying GME_BATCH_STEP_ACTIVITIES entity.

Key Procedures and Functions

  • validate_param — Resolves and validates the composite key supplied as organization code (p_org_code), batch number, batch step number, and activity. On success it returns the resolved batch, batch step, and activity identifiers along with the batch status, step status, and a return status flag. This procedure is the primary entry point corresponding to searches on p_org_code.
  • validate_activity_param — Validates an activity record supplied as a GME_BATCH_STEP_ACTIVITIES row type, along with a step identifier, a flexfield validation flag (defaulting to FND_API.G_FALSE), and an action code. It returns the validated activity record, the resulting step status, and a return status.
  • insert_batchstep_activity — Inserts a new batch step activity. It accepts the activity row type, a resource table (of type GME_CREATE_STEP_PVT.RESOURCES_TAB), optional organization code, batch number, and step number, plus flags controlling quantity-below-capacity tolerance and flexfield validation. It returns the persisted activity record and a return status.
  • update_batchstep_activity — Updates an existing activity record identified by the activity row type and optional organization, batch, and step identifiers, with optional flexfield validation. Returns the updated record and return status.
  • delete_batchstep_activity — Removes an activity, identified by activity identifier and/or the organization code, batch number, and step number context, with a return status indicating outcome.

Tables Accessed

  • GME_BATCH_STEP_ACTIVITIES — The primary transactional table holding activity records for batch steps; the target of insert, update, and delete operations.
  • GME_BATCH_HEADER — Provides batch-level context and status used during validation.
  • GME_BATCH_STEPS — Supplies step-level context and status for the batch.
  • GME_BATCH_STEP_RESOURCES — Links resources associated with a step activity.
  • FM_ACTV_MST — The activity master table, used to validate that the supplied activity is a defined activity.
  • PLITBLM — A PL/SQL index-by table utility used internally for bulk processing.

Usage Notes

Because the package is classified PVT, it is not called directly by end users or external systems. It is invoked indirectly through the Process Manufacturing batch and step forms, through the public OPM batch APIs (for example GME_CREATE_STEP_PVT), and through any custom code that manipulates batch step activities with proper setup. The p_org_code parameter accepted by validate_param, insert_batchstep_activity, update_batchstep_activity, and delete_batchstep_activity is the organization code used to scope operations within a specific process organization. Callers are expected to pass consistent organization, batch, and step identifiers so the package can resolve internal IDs. The return status follows FND_API conventions, so callers should check x_return_status against FND_API.G_RET_STS_SUCCESS and handle G_RET_STS_ERROR and G_RET_STS_UNEXP_ERROR accordingly. The package is referenced by one other package in the environment, confirming its supporting role beneath the public API layer.