Results for “gme_transform_batch”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GME_TRANSFORM_BATCH is a PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite process manufacturing (GME/GMA) product family. Its central purpose is to support batch transformation and migration logic for process manufacturing batch records. In EBS 12.1.1 and 12.2.2, the package is documented as VALID and is classified under the API classification of OTHER, indicating it is primarily an internal utility package rather than a published public API. The package carries out transformation, migration, and enrichment of batch header data, WIP entity linkage, resource transaction migration, and reason/documented reference resolution. It operates largely against process manufacturing tables (GME, GMD) and manufacturing execution tables (WIP_ENTITIES), with logging delivered through the common logging infrastructure.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions within this package body:

• GET_PROFILE_VALUE — Retrieves a value from an Oracle profile option, supporting the package's dependency on FND_PROFILE and the FND_PROFILE_OPTIONS/FND_PROFILE_OPTION_VALUES tables.
• GME_MIGRATION — The principal migration routine, orchestrating the movement and transformation of batch-related data, including resource transaction migration between GME_RESOURCE_TXNS and GME_RESOURCE_TXNS_MIG.
• CREATE_GME_PARAMETERS — Creates parameter records, likely populating GME_PARAMETERS to support batch transformations.
• UPDATE_BATCH_HEADER — Updates batch header records in GME_BATCH_HEADER as part of transformation or migration processing.
• UPDATE_WIP_ENTITIES — Updates or reconciles WIP entity records (WIP_ENTITIES/WIP_ENTITIES_S) to align manufacturing work-in-process data with batch transformations.
• UPDATE_FROM_DOC_NO — Updates records based on a document number, drawing on SY_DOCS_SEQ to resolve or generate document sequence references.
• UPDATE_REASON_ID — Updates reason identifiers, referencing SY_REAS_CDS_B for reason code resolution.

Parameter lists are not published in the metadata and should be confirmed against the package specification before use.

Tables Accessed

The package reads and writes several documented tables through APPS synonyms. FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES supply profile option lookups. GMD_RECIPE_VALIDITY_RULES and GME_GANTT_DOCUMENT_FILTER provide recipe validity and document filtering context. GME_BATCH_HEADER and GME_PARAMETERS hold the primary batch and parameter data being transformed. GME_RESOURCE_TXNS and GME_RESOURCE_TXNS_MIG support resource transaction migration. MTL_GEN_OBJECT_ID_S, SY_DOCS_SEQ, SY_ORGN_MST, and SY_REAS_CDS_B resolve object identifiers, document sequences, organization master data, and reason codes. WIP_ENTITIES and WIP_ENTITIES_S link batch transformation to WIP entities. DUAL supports standalone queries.

Usage Notes

As an OTHER-classified, APPS-owned package not referenced by any other database object, GME_TRANSFORM_BATCH is typically invoked from concurrent programs, migration scripts, or custom code rather than from standard Oracle Forms. It is commonly executed during process manufacturing data migration or batch remediation projects. Because GME_RESOURCE_TXNS_MIG is involved, it is likely paired with migration initiatives. The dependency on GMA_COMMON_LOGGING and FND_LOG indicates logging is integrated for diagnosability. Developers should treat the package as internal and verify the package specification before calling procedures directly.