Results for “qc_text_tbl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.GMD_QC_MIG12 is a migration utility package that forms part of the Oracle Process Manufacturing (OPM) Quality module upgrade path into Release 12. Its stated purpose, per the embedded header block (gmdmg12s.pls, version 120.1), is to provide "migration procedures for Quality for 12 migration." The package therefore serves as a one-time data-conversion engine that carries forward pre-R12 Quality setup and transactional entities into the structures introduced by the 12.1.1 and 12.2.2 data models.
The package is classified as OTHER under the ETRM API classification scheme, meaning it is not a public, supported business API. It exists to be driven by the OPM migration tooling during an upgrade, not to be called as part of normal production processing. It is referenced by zero other packages, confirming its position as a leaf-level, upgrade-only utility rather than a reusable library component.
The body opens with an extensive block of global database log counters, one triplet per migrated entity (typically a "pro" processed, "upd" updated, and "err" error counter). Counters exist for test methods, quality configuration, sampling plans, samples, results, sample events, store plans, store packs, stability studies, material sources, and specification variants. These counters indicate that the package reports row-level reconciliation statistics for each migration phase, which is characteristic of OPM/ETRM data-conversion code.
Key Procedures and Functions
Five procedures are documented for this package. Parameter lists are not published in the ETRM metadata and are therefore not reproduced here; only purpose is described.
- GMD_QC_MIGRATE_SETUP — Migrates Quality module configuration and setup data. It is the logical entry point for converting reference and control data, consistent with the spec, sampling plan, and store-related counters declared in the specification.
- GMD_QC_MIGRATE_SAMPLES — Migrates sample records into the Release 12 sample structures.
- GMD_QC_MIGRATE_RESULTS — Migrates Quality results data, converting historical result rows to the new result model.
- GMD_QC_MIGRATE_SPECS — Migrates specification and specification-version data, including the inventory, customer, and monitoring specification variants referenced by the package's table list.
- GMD_QC_MIGRATE_STABS — Migrates stability study data, corresponding to the stability counters declared in the package specification.
The five procedures align directly with the counter groupings, such that each procedure can be executed, monitored, and re-run independently during the upgrade window.
Tables Accessed
The package reads and writes the following documented tables through APPS synonyms:
- GMD_SAMPLES, GMD_RESULTS, GMD_SAMPLING_EVENTS — the core Quality transactional tables populated by the sample, result, and event migration procedures.
- GMD_SAMPLING_PLANS_B, GMD_QUALITY_CONFIG — setup tables loaded during the setup migration phase.
- GMD_INVENTORY_SPEC_VRS, GMD_CUSTOMER_SPEC_VRS, GMD_MONITORING_SPEC_VRS — the specification-version tables handled by GMD_QC_MIGRATE_SPECS.
- GMD_QC_SPEC_VR_ID_S, GMD_QC_SS_STOR_PACK_ID_S, GEM5_TEXT_CODE_S, GMD_EVENT_SPEC_DISP — sequence, text-code, and display support objects used to generate new identifiers and resolve coded values during conversion.
- GMD_MIGRATE_PARMS — the migration parameter table that governs run behaviour and scope.
- FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES — read to resolve profile settings that influence migration defaults, such as operating unit and quality parameters.
Usage Notes
GMD_QC_MIG12 is invoked during an OPM-to-Release 12 upgrade, not during ordinary application use. It is not exposed through Oracle Forms or as a standalone concurrent program in the standard OPM Quality responsibility; instead it is driven by the migration framework that orchestrates the Quality conversion steps. In practice it is called from the upgrade driver after the target Release 12 tables have been created and before Quality data is validated and made available to users.
Because the package maintains its own progress and error counters, DBAs and upgrade teams typically inspect the session output or the migration log tables to confirm that processed, updated, and error counts reconcile. The presence of separate error counters for every entity implies that individual row failures are tolerated and logged rather than aborting the entire migration, allowing remediation and re-execution of specific procedures.
Custom code should not call this package outside an upgrade context. Post-upgrade, the supported interfaces for loading Quality data are the standard OPM Quality APIs and open interfaces. The search phrase "mx12gu drive" does not correspond to a documented component of this package; it is most likely a transcription artefact of the source file name gmdmg12s.pls or of the 12.x migration driver naming convention, and has no bearing on the package's documented interface.
-
SYNONYM: APPS.QC_TEXT_TBL 12.2.2
-
SYNONYM: APPS.QC_TEXT_TBL 12.1.1
-
PACKAGE: APPS.GMD_QC_MIG12 12.1.1
-
PACKAGE: APPS.GMD_QC_MIG12 12.2.2
-
VIEW: APPS.QC_TEXT_TBL_VL 12.2.2
-
VIEW: APPS.QC_TEXT_TBL_VL 12.1.1