Search Results set_sequence_dependent_id

Overview

GME_BATCH_STEP_CHG_PVT is a private PL/SQL package in the APPS schema that supports Oracle Process Manufacturing (OPM) batch charging functionality within Oracle E-Business Suite. The package is classified as a PVT (private) API, indicating that it is intended for internal consumption by other Oracle EBS modules rather than for direct customer invocation. Its central responsibility is to manage the sequencing and persistence of batch step charges — the records that tie resources, activities, and consumed quantities to specific batch steps in the GME_BATCH_STEP_CHARGES table. The package also provides utilities for recalculating activity sequence numbers, clearing charge and charge-date data, and populating the charges table from caller-supplied rows. Tracing its header history, the package was created in May 2004 (bug 3307549) and extended in July 2004 to add automatic activity sequence-number calculation (bug 3718176).

Key Procedures and Functions

The package exposes eight documented procedures:

• SET_ACTIVITY_SEQUENCE_NUM — Recalculates and sets the activity sequence number for all charges belonging to a given batch, identified by the batch ID parameter. This is the procedure most closely associated with the user's search term; it operates at batch scope rather than at individual charge scope.
• SET_ALL_BATCH_ACTIVITIES — Performs the activity-sequencing operation across all batches, typically as part of a bulk maintenance or upgrade routine.
• SET_SEQUENCE_DEPENDENT_ID — Establishes the sequence-dependent identifier for a specified batch, linking charge records to the appropriate sequence definition.
• SET_ALL_BATCH_SEQUENCES — Applies the sequence-dependent identifier logic across all batches in a bulk operation.
• CLEAR_CHARGE_DATES — Removes charge-date values for a batch, optionally narrowed to a single batch step, and returns a status indicator.
• CLEAR_CHARGES — Deletes or resets charge records for a batch (optionally a single batch step) and returns a status indicator.
• CALC_ACTIVITY_SEQUENCE_NUMBER — A targeted calculation routine added under bug 3718176 that derives the activity sequence number for a specific batch step and resource combination, returning the computed number and a status.
• POPULATE_CHARGES_TABLE — Inserts charge rows into GME_BATCH_STEP_CHARGES based on an inbound row structure, a charge count, and a remaining quantity, returning a status indicator.

The package also declares two PL/SQL collection types (GME_BATCH_IDS_TAB and GME_BATCHSTEP_IDS_TAB) for passing arrays of batch and batch-step identifiers.

Tables Accessed

The package reads and writes several core OPM batch tables: GME_BATCH_HEADER (batch context), GME_BATCH_STEPS (parent step records), GME_BATCH_STEP_CHARGES (the charges being sequenced and populated), GME_BATCH_STEP_RESOURCES (resource assignments used in sequence calculation), and GME_BATCH_STEP_ACTIVITIES (activity definitions). Reference data is drawn from CR_RSRC_DTL (resource details), GMD_RECIPE_VALIDITY_RULES (recipe validity), GMP_SEQUENCE_TYPES (sequence definitions), and the inventory category structures MTL_DEFAULT_CATEGORY_SETS, MTL_ITEM_CATEGORIES, and MTL_SYSTEM_ITEMS. PLITBLM is used as a PL/SQL-indexed table for bulk operations.

Usage Notes

Because GME_BATCH_STEP_CHG_PVT is a PVT-classified API, it is not documented for direct customer calls; it is invoked by other Oracle packages — the metadata records nine dependent packages — and indirectly by OPM batch and charge-related forms and concurrent programs. Developers extending OPM charge logic should call the public wrapper APIs rather than this private package. When troubleshooting activity sequence numbering issues on GME_BATCH_STEP_CHARGES in Release 12.1.1 or 12.2.2, SET_ACTIVITY_SEQUENCE_NUM and CALC_ACTIVITY_SEQUENCE_NUMBER are the relevant entry points for recalculating values, while CLEAR_CHARGES and CLEAR_CHARGE_DATES are used to reset charge data before regeneration.