Results for “order_type_id”

50+ results




Overview
Explore in AI Chat

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

Overview

GML_OM_MIG_VALIDATE_PKG is an Oracle EBS Application Object Library (APPS) package body that belongs to the Oracle Process Manufacturing (OPM/GML) migration framework. Its documented purpose is to provide the validation and lookup logic required when migrating sales order data from legacy or external systems into the Oracle Order Management (OM) and OPM order structures. The package supplies a suite of Boolean-returning validation functions and OUT-parameter lookup procedures whose task is to confirm that incoming order attributes — order numbers, customers, sales representatives, shippers, payment terms, currencies, price lists, organizations, and freight attributes — are valid and reconcilable between the OPM and OM schemas before a migration program accepts or converts the record.

Key Procedures and Functions

The package exposes twenty-one documented callable units. The most prominent, and the one returned for the query "validate_order_no", is VALIDATE_ORDER_NO, which the header comment states must be numeric or the value will not be converted. Related validation members include VALIDATE_CUSTOMER, VALIDATE_SALESREP, VALIDATE_SHIPPER, VALIDATE_PAYMENT_TERM, and VALIDATE_CURR_CODE, each confirming that a reference value exists in both OPM and OM. Lookup or resolver functions return identifiers and derived attributes: ORDER_TYPE_ID, ORIG_SYS_DOCUMENT_REF, PRICE_LIST_ID, SHIP_TO_CONTACT_ID, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, DELIVER_TO_ORG_ID, FOB_POINT_CODE, HOLD_REASON_CODE, FETCH_FREIGHT_TERMS_CODE, GET_RATE_TYPE_CODE, and MIGRATE_SHIP_METHODS. ERROR_LOG provides the diagnostic sink for validation failures encountered during a migration run. Each validation routine conventionally accepts an input value plus an order identifier and returns a success/failure indicator or an OUT parameter carrying the resolved internal identifier.

Tables Accessed

The ETRM metadata for this package lists no directly referenced base tables; the package accesses data through APPS synonyms. Given its stated function, it reads the OPM and OM master and reference tables that hold customers, sales representatives, shippers, payment terms, currencies, price lists, organizations, freight terms, rate types, and ship methods, and it writes migration results or error information to the error log structures used by the migration framework. The absence of documented table references indicates that the package relies on the APPS synonym layer rather than hard-coded schema-qualified names.

Usage Notes

This is a migration-support package rather than a public business API. It is invoked by GML order-migration concurrent programs and custom conversion routines that stage legacy sales orders and must certify each attribute before inserting into the OM interface tables. It is referenced by zero other packages, confirming that it sits at the outer edge of the migration flow, called directly by migration executable code. Because the validation functions return Boolean values, they are typically consumed by PL/SQL migration drivers rather than by Oracle Forms directly. The header revision (120.1, dated 2006) and the embedded GSCC NCOPY change reference indicate the package predates and is carried forward through EBS 12.1.1 and 12.2.2 largely unchanged, so implementers using it on 12.2.x should treat it as legacy migration infrastructure and validate behavior against their specific OPM/OM release.