Search Results get_routing_no

Overview

GMF_MIGRATION is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It supports the migration of legacy process manufacturing (OPM) cost and fiscal configuration data into the EBS data model used by Oracle Process Manufacturing. The package name, its header version stamp, and its function names indicate that it is a data-conversion utility tied to the GMF (Process Manufacturing) costing and accounting schema. Its primary purpose is to resolve legacy coded values into EBS surrogate identifiers and to migrate fiscal policy, cost method, and lot cost method setups. Internally the package holds a substantial set of global constants mapping legacy attribute names (for example ORGANIZATION_ID, SUBINVENTORY_CODE, INVENTORY_ITEM_ID, ORDER_TYPE, REASON_ID, and CURRENCY_CODE) to identifiers used within the migration run. A set of single-character globals (G_Constant, G_And, G_Or, G_Equal) indicates the package constructs dynamic SQL predicates during migration, and Application_id is fixed at 555, the Process Manufacturing application.

Key Procedures and Functions

ETRM documents 48 procedures and functions in this package. The retrieval functions form a lookup layer used by the migration logic:

• GET_ACCOUNT_ID, GET_CO_CODE – resolve account codes and company (cost organization) codes to their internal identifiers.
• GET_INVENTORY_ITEM_ID, GET_ITEM_NUMBER – convert between item numbers and inventory item identifiers.
• GET_LEGAL_ENTITY_ID – returns the legal entity identifier for a given migration context.
• GET_CUSTOMER_NO, GET_VENDOR_NO – resolve customer and supplier numbers to internal party identifiers.
• GET_REASON_ID, GET_ROUTING_NO, GET_PRICE_ELEMENT_TYPE_ID – look up reason codes, routings, and price element types.
• GET_COST_CMPNTCLS_CODE – resolves the cost component class code.
• GET_ORDER_TYPE_CODE – returns the order type code used to classify migration records by order category.
• GET_LINE_TYPE_CODE, GET_AR_TRX_TYPE_CODE – resolve line type and receivables transaction type codes.
• GET_GL_BUSINESS_CLASS_CAT, GET_GL_PRODUCT_LINE_CAT – resolve GL business class and product line category mappings.
• MIGRATE_FISCAL_POLICIES_LE, MIGRATE_FISCAL_POLICIES_OTHERS – migrate fiscal policy definitions for legal entities and for other organizations respectively.
• MIGRATE_COST_METHODS, MIGRATE_LOT_COST_METHODS – migrate cost method and lot-level cost method setups into the target cost tables.

Tables Accessed

All tables referenced by the package are accessed through APPS synonyms and belong to the CM (Cost Management) schema family. CM_MTHD_MST holds cost method master definitions consumed by MIGRATE_COST_METHODS. CM_CMPT_MST, CM_CMPT_DTL, and CM_CMPT_MTL store cost component master, detail, and material-level data. CM_CLDR_HDR_B and CM_CLDR_DTL hold calendar header and detail records used in fiscal policy migration. CM_ACST_LED, CM_SCST_LED, and CM_CUPD_CTL are actual cost, standard cost, and cost update control ledgers. CM_RLUP_CTL and CM_RLUP_ITM support cost rollup control and item-level rollup results. CM_RSRC_DTL, CM_ADJS_DTL, CM_BRDN_DTL, and CM_ACPR_CTL hold resource detail, adjustment detail, burden detail, and actual cost processing control records. These tables are read for legacy values and written with converted EBS identifiers during migration.

Usage Notes

GMF_MIGRATION is not an operational runtime API. It is invoked during implementation and upgrade projects when legacy process manufacturing costing data must be converted into an EBS 12.1.1 or 12.2.2 instance. Typical invocation paths include concurrent programs supplied by Oracle for OPM migration, and custom conversion scripts that call the individual GET_* and MIGRATE_* routines in a controlled sequence. The GET_ORDER_TYPE_CODE function in particular is called by the user's search because it is a frequently referenced lookup when mapping legacy order classifications to EBS order type codes before records are inserted into the cost tables. Because the package writes directly to CM cost tables, it should only be run under a controlled migration plan with backups in place; it is referenced by one other package in the ETRM metadata, confirming its role as a supporting utility rather than a top-level entry point.