Search Results gme_batch_step_charge_dbl




Overview
Explore in AI Chat

Overview

GME_BATCH_STEP_CHARGE_DBL is a PL/SQL database package owned by the APPS schema and declared with AUTHID CURRENT_USER. It serves as the data-access layer (the "_DBL" suffix denotes a Database Layer wrapper) for the GME_BATCH_STEP_CHARGES entity within the Oracle Process Manufacturing (OPM/GME) application family. The package encapsulates the standard create, retrieve, update, and delete operations performed against batch step charge records, which represent the charges or cost-related values attached to individual steps of a production batch.

The package was created on 04-MAY-2004 by Rishi Varma under bug 3307549, with the source header GMEVGSCS.pls at version 120.1. Its header comment explicitly declares that it is the specification of package gme_batch_step_charges_dbl and lists the four operations it exposes: insert_row, fetch_row, delete_row, and update_row. This structure isolates the physical table access from higher-level business logic, allowing callers to manipulate batch step charge records without embedding direct DML against the base table.

Key Procedures and Functions

The package exposes four documented functions, each returning a BOOLEAN status to signal success or failure of the operation. All are declared in the package specification.

  • INSERT_ROW — Creates a new row in the GME_BATCH_STEP_CHARGES table. It accepts an input row of type gme_batch_step_charges%ROWTYPE and returns the inserted row, propagating any server-assigned or defaulted attribute values back to the caller.
  • FETCH_ROW — Retrieves a single batch step charge record matching the supplied key values. This is the operation referenced by the search term "fetch_row." It accepts an input row whose key columns identify the desired record, and returns the fully populated row through the IN OUT NOCOPY parameter.
  • DELETE_ROW — Removes the batch step charge row identified by the passed key values from the underlying table.
  • UPDATE_ROW — Modifies an existing batch step charge record with the values supplied in the input row.

Tables Accessed

The single documented table referenced by this package is GME_BATCH_STEP_CHARGES, accessed through an APPS synonym. The four functions correspond directly to the four DML operations against this table: INSERT_ROW inserts, FETCH_ROW queries, DELETE_ROW deletes, and UPDATE_ROW updates. Because the package parameters are declared using the table's %ROWTYPE, the record structure of GME_BATCH_STEP_CHARGES defines the interface contract for every call.

Usage Notes

As a database-layer package, GME_BATCH_STEP_CHARGE_DBL is not typically invoked directly by end users. Instead it is called by higher-level OPM business logic, forms, and concurrent programs that manage batch step charges. The ETRM metadata records that the package is referenced by one other package, confirming that it sits beneath a caller in the dependency chain rather than at the top of it.

The FETCH_ROW function is commonly used by callers that must first validate the existence of a charge record before performing an update or delete, or that must present the current values to a user interface. Custom extensions that need to read or maintain batch step charge data should call these functions rather than issuing direct SQL against GME_BATCH_STEP_CHARGES, thereby preserving the encapsulation and validation behavior implemented in the database layer.