Search Results migrate_rgpv
Overview
OKL_OKC_MIGRATION_A_PVT is a private PL/SQL package body in the Oracle EBS Applications (APPS) schema that belongs to the Oracle Lease and Finance Management (OLFM/OKL) product family. Its header comment identifies it as an internal, non-shipped object (the noship marker in the RCS revision string), confirming that it is a helper package rather than a public API. The package supports migration and staging of article, rule group, and assertion data into the Oracle Contracts (OKC) repository. It is not a standalone conversion program; instead, it exposes private row-level and validation procedures that a larger migration driver package invokes to move legacy or staged records into the OKC contract structure. The presence of the local migrate_catv procedure — which maps a locally declared CATV record type into the OKC_K_ARTICLE_PUB record type — illustrates the package's core role: reconciling data structures between the OKL and OKC data models during migration. The user search term "migrate_rgpv" points to this migration theme, specifically the movement of rule group and article-version data, which this package facilitates through its insert, update, and delete primitives.
Key Procedures and Functions
The ETRM documentation lists eight procedures and functions in this package. The primary data manipulation routines are:
- INSERT_ROW — Inserts a migrated article or rule-group record into the OKC base tables. It applies the standard API pattern of error capture via the
G_SQLERRM_TOKENandG_SQLCODE_TOKENtokens declared at the top of the body. - UPDATE_ROW — Updates existing OKC records with migrated attribute values, used when a target row already exists and must be synchronized rather than created.
- DELETE_ROW — Removes staged or obsolete OKC records, supporting cleanup and re-run scenarios in a migration cycle.
- EXECUTE_QA_CHECK_LIST — Runs the quality-assurance checklist against migrated data, validating that articles and rule groups meet contract quality rules before the migration is committed.
- UPDATE_ALLOWED — Determines or records whether an update is permitted for a given migration record, enforcing the allowed-operation rules of the underlying OKC API.
The remaining three documented procedures serve supporting roles, including the local migrate_catv record-mapping routine. All routines are private to the package and are not intended for direct customer invocation.
Tables Accessed
The package operates against the following documented tables, accessed through APPS synonyms:
- OKC_K_ARTICLES_B — the base table for contract articles, the primary target of insert and update operations.
- OKC_K_ARTICLES_TL — the translation table for article names and descriptions, populated alongside the base row.
- OKC_RULE_GROUPS_B — the base table for rule groups, which is the likely focus of the "rgpv" migration path.
- OKC_RULE_GROUPS_TL — the translation table for rule-group text.
- OKC_ASSENTS — the assertions/assent records associated with contract terms.
- OKC_K_HEADERS_B — the contract header table, used to validate and link migrated articles and rule groups to their parent contract.
- PLITBLM — the Oracle Forms/PL/SQL character-table structure, used for array-style operations and list handling during bulk migration.
Usage Notes
Because this is a PVT-class (private) package, it is never called directly from Oracle Forms or a concurrent program definition. It is invoked by other migration and conversion packages; the ETRM metadata records that it is referenced by 13 other packages. Typical invocation is therefore from a parent migration driver, either during an upgrade to Release 12.1.1 or 12.2.2 or as part of a one-time data conversion from legacy lease or contract data into the OKC model. The QA checklist procedure implies the package is executed in staged, repeatable cycles where data is loaded, validated, and only then committed. Custom code should not call this package; instead, use the public OKC contract APIs and let the migration driver orchestrate OKL_OKC_MIGRATION_A_PVT internally.
-
PACKAGE BODY: APPS.OKL_OKC_MIGRATION_A_PVT
12.2.2
-
PACKAGE BODY: APPS.OKL_VP_RULE_PUB
12.1.1
-
PACKAGE BODY: APPS.OKL_VP_RULE_PUB
12.2.2
-
PACKAGE BODY: APPS.OKL_OKC_MIGRATION_A_PVT
12.1.1
-
PACKAGE BODY: APPS.OKL_OKC_MIGRATION_PVT
12.2.2
-
PACKAGE BODY: APPS.OKL_OKC_MIGRATION_PVT
12.1.1
-
APPS.OKL_OKC_MIGRATION_A_PVT dependencies on OKC_RULE_PUB
12.1.1
-
APPS.OKL_OKC_MIGRATION_A_PVT dependencies on OKC_RULE_PUB
12.2.2
-
PACKAGE BODY: APPS.OKC_RULE_PUB
12.2.2
-
APPS.OKL_VP_RULE_PUB dependencies on OKL_VP_RULE_PVT
12.2.2
-
APPS.OKL_VP_RULE_PUB dependencies on OKL_VP_RULE_PVT
12.1.1
-
APPS.OKL_OKC_MIGRATION_PVT dependencies on OKC_RULE_PUB
12.1.1
-
APPS.OKL_OKC_MIGRATION_PVT dependencies on OKC_RULE_PUB
12.2.2
-
PACKAGE BODY: APPS.OKC_RULE_PUB
12.1.1
-
PACKAGE BODY: APPS.OKL_RULE_PUB
12.1.1
-
APPS.OKL_OKC_MIGRATION_A_PVT dependencies on OKC_QA_CHECK_PUB
12.1.1
-
PACKAGE BODY: APPS.OKL_RULE_PUB
12.2.2
-
APPS.OKL_RULE_PUB dependencies on OKL_OKC_MIGRATION_PVT
12.1.1
-
APPS.OKL_RULE_PUB dependencies on OKL_OKC_MIGRATION_PVT
12.2.2
-
APPS.OKL_OKC_MIGRATION_A_PVT dependencies on OKC_QA_CHECK_PUB
12.2.2
-
APPS.OKC_RULE_PUB dependencies on OKC_RULE_PVT
12.2.2
-
APPS.OKC_RULE_PUB dependencies on OKC_RULE_PVT
12.1.1
-
APPS.OKL_VP_RULE_PUB dependencies on OKC_API
12.1.1
-
APPS.OKL_VP_RULE_PUB dependencies on OKC_API
12.2.2
-
APPS.OKL_OKC_MIGRATION_A_PVT dependencies on OKC_API
12.1.1
-
APPS.OKL_OKC_MIGRATION_A_PVT dependencies on OKC_API
12.2.2
-
APPS.OKL_OKC_MIGRATION_PVT dependencies on OKC_API
12.1.1
-
APPS.OKL_OKC_MIGRATION_PVT dependencies on OKC_API
12.2.2
-
APPS.OKC_RULE_PUB dependencies on OKC_API
12.1.1
-
APPS.OKC_RULE_PUB dependencies on OKC_API
12.2.2
-
APPS.OKL_RULE_PUB dependencies on OKC_API
12.1.1
-
APPS.OKL_RULE_PUB dependencies on OKC_API
12.2.2