Search Results check_extension_rule

Overview

OKC_XPRT_IMPORT_RULES_PVT is a private PL/SQL package in the APPS schema that supports the import of export-compliance rules into Oracle E-Business Suite. The suffix _PVT indicates that the package is an internal implementation layer: it is not exposed directly to end users or external integrations, but is instead invoked by the public packages that make up the OKC Export Compliance (XPRT) module. Its principal role is to translate source rule definitions—typically originating from Oracle's centralized content repository and staged in the CZ interface tables—into the runtime structures used by the EBS export compliance engine, namely the OKC_XPRT_RULE_* tables.

The metadata further identifies the package as VALID in both EBS 12.1.1 and 12.2.2, and notes that it references only SYS.STANDARD directly, with the bulk of its real work performed against APPS synonyms. This pattern is consistent with an internal worker package that is called from OKC_XPRT_IMPORT_PVT, which is its only documented referencer.

Key Procedures and Functions

Eight documented entry points are associated with the package. Their names describe their functional intent:

• IMPORT_RULES_PUBLISH — Publishes imported rule definitions, making them available to the runtime compliance engine.
• IMPORT_RULES_DISABLE — Disables previously imported rules, removing them from active enforcement without deleting historical definitions.
• IMPORT_RULE_TEMP_APPROVAL — Handles the temporary-approval state applied to imported rules pending full review.
• BUILD_AND_INSERT_RULE — Constructs a rule record from staged import data and inserts it into the OKC export rule tables.
• BUILD_STATEMENT_RULE — Builds a rule statement, i.e., the logical expression evaluated at runtime.
• CHECK_EXTENSION_RULE — Validates an extension rule supplied during import.
• ATTACH_EXTENSION_RULE — Attaches an approved extension rule to the appropriate rule header or template.
• ATTACH_EXTENSION_RULE_TMPL — Attaches an extension rule to a terms template.

Parameter lists are intentionally not documented here; callers should treat the package as private and invoke it only through OKC_XPRT_IMPORT_PVT.

Tables Accessed

The package reads and writes several groups of tables. Source data is drawn from the CZ staging tables (CZ_IMP_RULES, CZ_RULES, CZ_DEVL_PROJECTS, CZ_IMP_LOCALIZED_TEXTS, CZ_XFR_RUN_INFOS_S), which hold downloaded compliance content and its transfer metadata. Target definitions are written to OKC_XPRT_RULE_HDRS_ALL, OKC_XPRT_RULE_CONDITIONS, OKC_XPRT_RULE_COND_VALS, and OKC_XPRT_RULE_OUTCOMES, forming the header, condition, condition-value, and outcome layers of a rule. Template linkage is recorded in OKC_XPRT_TEMPLATE_RULES and OKC_TERMS_TEMPLATES_ALL. FND_LANGUAGES supplies the installed-language list for localized text, while DBMS_LOB and DUAL are used for large-object handling and single-row queries respectively.

Usage Notes

OKC_XPRT_IMPORT_RULES_PVT is not intended for direct invocation. It is called exclusively by OKC_XPRT_IMPORT_PVT, which is itself driven by the export-compliance import process—typically a concurrent program or an administrative form within the OKC module. Custom code should not call this package; instead, integrators should target the import orchestration layer exposed by OKC_XPRT_IMPORT_PVT. Because the package manipulates rule headers, conditions, and outcomes across multiple tables, any direct manipulation would bypass validation and audit logic embedded in the private layer. In 12.2.2 the package remains VALID and is referenced by exactly one other package, confirming its role as a non-public implementation detail of the ETRM export-compliance import feature.