Search Results get_max_step_date

Overview

GME_CREATE_STEP_PVT is a private PL/SQL package in the APPS schema that supports Oracle Process Manufacturing (OPM) batch step creation within Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified as a PVT (private) API, meaning it is intended for internal consumption by other OPM packages rather than as a public integration interface. Its principal business function is to construct and persist batch step records — including step activities, dependencies, items, resources, charges, and process parameters — when a batch is created, copied, rerouted, rescheduled, or updated. The package also performs date and duration calculations for batch steps, such as deriving step quantities, computing longest-path timings, and resolving working start times. It is the computational and transactional engine that sits between higher-level public APIs, notably GME_API_PUB, and the underlying GME batch tables.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions:

• CREATE_BATCH_STEPS — the primary driver that creates batch step records and their related child rows.
• CALC_DATES — computes start and end dates for batch steps based on dependencies and durations.
• UPDATE_CHARGES — recalculates or applies step charge information.
• CALC_STEP_QTY — derives the quantity associated with a batch step.
• COPY_AND_CREATE_TEXT — copies and instantiates text records associated with steps.
• CALC_LONGEST_TIME_ORIG — determines the longest duration path originating from a step.
• GET_USAGE_IN_HOURS — returns resource usage expressed in hours.
• GET_MAX_DURATION — returns the maximum duration across relevant steps.
• INSERT_RESOURCE_TXNS — inserts resource transaction records for steps.
• GET_MAX_STEP_DATE — returns the latest date associated with a batch step.
• GET_WORKING_START_TIME — resolves the working-calendar start time for scheduling.
• CALC_LONGEST_TIME — computes the longest duration path for scheduling purposes.
• GET_LONGEST_IN_BRANCH — returns the longest duration within a dependency branch.

Tables Accessed

The package reads and writes the core OPM batch tables through APPS synonyms:

• GME_BATCH_HEADER — parent batch record providing context for step creation.
• GME_BATCH_STEPS — the primary step records created and maintained.
• GME_BATCH_STEP_ACTIVITIES — activities performed at each step.
• GME_BATCH_STEP_DEPENDENCIES — predecessor/successor relationships used for date calculation.
• GME_BATCH_STEP_ITEMS — materials consumed or produced at steps.
• GME_BATCH_STEP_RESOURCES — resources assigned to steps.
• GME_BATCH_STEP_CHARGES — charge details applied to steps.
• GME_PROCESS_PARAMETERS — process parameter values for steps.
• GME_RESOURCE_TXNS — resource transaction records inserted during step creation.
• GME_TEXT_TABLE — text associated with steps.
• GME_MATERIAL_DETAILS — material detail information.
• GMD_RECIPE_STEP_MATERIALS and GMD_RECIPE_VALIDITY_RULES — recipe source data governing step materials and validity.
• FM_ROUT_DEP and FM_TEXT_TBL — routing dependency and text tables.

Usage Notes

Because GME_CREATE_STEP_PVT is a private package, it should not be called directly from custom code; the supported entry point is the public API GME_API_PUB, which references it. It is also invoked by numerous internal OPM packages, including GME_CREATE_BATCH_PVT, GME_BATCHSTEP_ACT_PVT, GME_INSERT_STEP_PVT, GME_REROUTE_BATCH_PVT, GME_RESCHEDULE_BATCH_PVT, GME_RESCHEDULE_STEP_PVT, GME_UPDATE_STEP_QTY_PVT, and GMP_APS_WRITER. It depends on utility packages such as FND_API, GMD_AUTO_STEP_CALC, and GMD_RECIPE_FETCH_PUB. Typical invocations occur during batch creation, batch step insertion, reroute and reschedule processing, and Advanced Planning System writes. Customizations requiring batch step logic should route through GME_API_PUB or the documented public OPM APIs to preserve supported behavior across upgrades.