Results for “hold_reason_code”

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

Overview

GML_OM_MIG_VALIDATE_PKG is an Oracle EBS PL/SQL package owned by APPS within the Process Manufacturing (GML) module set. Its name — GML Order Management Migration Validate — describes its role precisely: it validates and derives reference values needed to migrate legacy order data into Oracle Order Management (OM). In Oracle EBS 12.1.1 and 12.2.2, legacy conversion routines cannot insert directly into OM base tables without first resolving foreign keys and validating lookup codes. This package supplies that resolution layer, converting the loosely typed values found in staging tables (order numbers, terms codes, customer identifiers, warehouse codes) into the internal identifiers OM requires, and returning a boolean or an OUT parameter as appropriate.

The package is declared AUTHID CURRENT_USER, so it executes under the privileges of the calling session rather than the definer — an important consideration when it is called from SQL*Loader control scripts, custom PL/SQL migration programs, or concurrent request code. The source header records a development revision from 2007 and references Bug 5840624, indicating the package has been stable across the 11i-to-R12 lifecycle.

Key Procedures and Functions

The documented interface comprises 21 programs, separable into validators (which return a boolean or a resolved value) and derivation procedures (which populate OUT parameters for OM header columns).

• VALIDATE_ORDER_NO — confirms that an incoming order number is acceptable for the migration load, avoiding duplicate or malformed order keys.
• VALIDATE_PAYMENT_TERM — checks a payment terms code and returns the corresponding term identifier.
• VALIDATE_CURR_CODE — verifies that a currency code is defined and active.
• ORDER_TYPE_ID — resolves the order type identifier and a related price list from order type and operating unit context.
• ORIG_SYS_DOCUMENT_REF — constructs or validates the original system document reference used to trace migrated orders back to their source system.
• PRICE_LIST_ID — derives the price list applicable to the billing currency.
• SHIP_TO_CONTACT_ID, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, DELIVER_TO_ORG_ID — resolve the party, contact, and inventory organization identifiers required for OM header and line shipping, billing, and delivery fields.
• FOB_POINT_CODE — validates and normalizes the FOB point code for shipping terms.
• VALIDATE_CUSTOMER, VALIDATE_SALESREP, VALIDATE_SHIPPER — validate the customer account, sales representative, and shipper reference data used on migrated orders.
• FETCH_FREIGHT_TERMS_CODE — retrieves the freight terms code associated with the shipment context.
• HOLD_REASON_CODE — validates the hold reason applied to orders placed on hold during migration.
• MIGRATE_SHIP_METHODS — migrates or converts ship method reference data as part of the load.
• GET_RATE_TYPE_CODE — returns the rate type code used for currency conversion on the order.
• ERROR_LOG — records validation failures for operator review and reprocessing, with a package global g_order_id and g_line_id providing row context across calls.

Tables Accessed

The ETRM metadata for this package does not enumerate the tables it references; it lists no APPS synonyms or base tables explicitly. Functionally, however, validation and derivation of order type, price list, customer, terms, currency, organizations, and sales representatives necessarily reads the corresponding OM and reference setup entities — order types, price lists, customers, payment terms, currencies, inventory organizations, and sales rep definitions — through APPS synonyms. The package is documented as referenced by zero other packages, confirming it is a leaf-level utility consumed directly by migration code rather than an internal dependency of other PL/SQL APIs.

Usage Notes

GML_OM_MIG_VALIDATE_PKG is not invoked by standard EBS forms or seeded concurrent programs. It is a migration-support package called from custom conversion scripts, SQL*Loader post-load validation routines, and bespoke PL/SQL programs that stage legacy orders into OM interface tables or base tables. Because it is AUTHID CURRENT_USER, the calling schema must hold the necessary privileges on the underlying APPS objects. The user search term "order_id" reflects the package's pervasive use of an order identifier as a context parameter on nearly every program, alongside the package globals g_order_id and g_line_id, which allow the ERROR_LOG utility to attribute failures to the specific order or line being processed. Callers should expect boolean-return validators to be checked before the DERIVE-style procedures are called, so that only validated orders proceed to insertion.