Results for “zx_condition_groups_b_s”

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

Overview

ZX_MIGRATE_TAX_DEFAULT_HIER is an APPS-owned PL/SQL package body in the Oracle E-Business Suite ETRM (E-Business Tax) module. Its purpose is to migrate legacy tax defaulting hierarchies — the ordered sets of determining factors, conditions, rules, and rates that govern how tax is calculated on a transaction — into the ZX (E-Business Tax) repository. Prior to the consolidation of tax setup into E-Business Tax, defaulting logic resided in multiple legacy tables across Payables (AP) and Receivables (AR), such as AR_VAT_TAX_ALL, AR_TAX_CONDITIONS_ALL, and AP_TAX_CODES_ALL. This package reads those legacy definitions and transforms them into the normalized ZX model, encompassing condition groups, conditions, rules, determining factors, and process results. It functions as a migration utility rather than a runtime calculation API, and its execution is part of the broader upgrade and data-conversion effort that populates the E-Business Tax configuration when an environment moves to 12.1.1 or 12.2.2. The package is classified as OTHER, indicating it is not a public, supported integration API but rather an internal migration routine.

Key Procedures and Functions

The package body exposes four documented procedures, each responsible for one stage of the hierarchy migration:

• MIGRATE_DEFAULT_HIERARCHY — The primary driver. It orchestrates the migration of the legacy defaulting hierarchy into the ZX structures, coordinating the invocation of the subordinate routines described below.
• CREATE_CONDITION_GROUPS — Populates condition group definitions in the ZX layer, derived from the legacy tax condition and tax code setup. Condition groups provide the logical grouping under which determining factors and conditions are evaluated.
• CREATE_RULES — Builds the tax rules that express the migrated defaulting logic, establishing the relationship between determining factors and the tax outcomes they drive.
• CREATE_PROCESS_RESULTS — Inserts and maintains entries in the process results tables, recording the outcomes produced by the migration and the applicability results generated by the ZX engine for later use and auditability.

The documented metadata does not expose parameter signatures; the descriptions above reflect the naming and dependency evidence rather than a published interface.

Tables Accessed

The package references a substantial set of APPS synonyms. Legacy source tables include AP_TAX_CODES_ALL, AP_TAX_CODES_S, AR_SYSTEM_PARAMETERS_ALL, AR_TAX_CONDITIONS_ALL, AR_TAX_GROUP_CODES_ALL, AR_VAT_TAX_ALL, AR_VAT_TAX_ALL_B, and AR_VAT_TAX_S, which hold the pre-12 tax setup. Target ZX tables include ZX_CONDITIONS and ZX_CONDITIONS_S, ZX_CONDITION_GROUPS_B / _B_S / _TL, ZX_DETERMINING_FACTORS_B, ZX_DET_FACTORS_TL, ZX_DET_FACTOR_TEMPL_B and its detail tables, ZX_RULES_B, ZX_RULES_B_S, ZX_RULES_B_TMP, ZX_RULES_TL, ZX_TAXES_B, ZX_TAXES_B_S, ZX_TAXES_B_TMP, ZX_RATES_B, ZX_ID_TCC_MAPPING_ALL, ZX_PARTY_TAX_PROFILE, ZX_PROCESS_RESULTS, and ZX_PROCESS_RESULTS_S. Supporting framework objects include FND_LANGUAGES, FND_PRODUCT_GROUPS, FND_GLOBAL, FND_LOG, and FND_PROFILE, used for language handling, instance identification, logging, and profile-driven behavior. The temporary (_TMP) and _S (sequence or shadow) tables suggest bulk staging during conversion.

Usage Notes

Because ZX_MIGRATE_TAX_DEFAULT_HIER is an internal migration package, it is not intended to be invoked from standard application forms. It is typically executed during upgrade or conversion, driven by the E-Business Tax migration framework and related utilities such as ZX_MIGRATE_UTIL. The presence of FND_LOG and FND_GLOBAL dependencies indicates that execution is logged through the standard EBS logging framework, allowing administrators to review migration progress and errors. The package is not referenced by any other database object, confirming its role as a terminal migration step, though it is reported to be called by one related package. Customers moving to 12.1.1 or 12.2.2 should rely on Oracle-supplied migration flows rather than invoking these procedures directly; custom code should treat the package as read-only internal logic. The user's search term, "zx_process_results_s," corresponds to the sequence or shadow table maintained by CREATE_PROCESS_RESULTS, which acts as the primary key source for ZX_PROCESS_RESULTS records generated during migration.