Search Results p_tax_id

Overview

ZX_MIGRATE_TAX_DEF is an Oracle E-Business Tax migration package owned by APPS and classified under ETRM as OTHER. Its central business purpose is to migrate legacy Oracle Payables tax configuration data into the Oracle E-Business Tax (ZX) data model during implementation or upgrade. Prior to the introduction of E-Business Tax, tax setup for Payables was maintained through Oracle Payables structures such as AP_TAX_CODES_ALL, recovery rates, and recovery rules. ZX_MIGRATE_TAX_DEF performs the transformation of that legacy configuration into native ZX entities, including tax classifications, statuses, taxes, condition groups, rules, accounts, and offset codes.

The package is declared AUTHID CURRENT_USER, meaning all database object resolution and privilege checks are performed against the invoking user's schema rather than the owner's. The package header carries a header string indicating version 120.7, and two documented bug fixes (3557681 and 3700674) introduced several of the procedures described below. Because it writes directly to configuration tables, this package is not intended for routine day-to-day use; it is a controlled, one-time or phased migration utility.

Key Procedures and Functions

The package exposes thirteen documented procedures, several of which accept an optional p_tax_id parameter that restricts processing to a single legacy tax code.

• MIGRATE_AP_TAX_CODES_SETUP — Migrates Payables-level tax code setup data.
• MIGRATE_FND_LOOKUPS — Migrates values related to Oracle Application Object Library lookups into the ZX lookup framework.
• CREATE_TAX_CLASSIFICATIONS — Creates tax classification records; accepts p_tax_id (DEFAULT NULL).
• MIGRATE_NORMAL_TAX_CODES — Migrates normal (non-offset) tax codes into ZX taxes; accepts p_tax_id.
• MIGRATE_ASSIGN_OFFSET_CODES — Assigns offset tax codes during migration; accepts p_tax_id.
• MIGRATE_UNASSIGN_OFFSET_CODES — Removes/unassigns offset code associations; accepts p_tax_id.
• MIGRATE_RECOVERY_RATES — Migrates Payables recovery rates to corresponding ZX recovery configuration; accepts p_tax_id.
• CREATE_ZX_STATUSES — Creates the statuses required by migrated ZX taxes; accepts p_tax_id.
• CREATE_ZX_TAXES — Creates the ZX tax records themselves; accepts p_tax_id.
• CREATE_TEMPLATES — Creates tax configuration templates.
• CREATE_CONDITION_GROUPS — Creates condition groups; accepts p_rate_id (DEFAULT NULL).
• CREATE_RULES — Creates tax rules; accepts p_tax_id.
• CREATE_TAX_ACCOUNTS — Creates tax accounts (introduced by BugFix 3700674).

Tables Accessed

The package reads legacy Payables and system configuration tables and writes into E-Business Tax tables. Documented legacy/source tables include AP_TAX_CODES_ALL (Payables tax codes), AP_TAX_RECVRY_RATES_ALL and AP_TAX_RECVRY_RULES_ALL (recovery rates and rules), AP_SYSTEM_PARAMETERS_ALL, FINANCIALS_SYSTEM_PARAMS_ALL, and FND_PRODUCT_GROUPS for organizational and system context. Lookup-related tables FND_LANGUAGES, FND_LOOKUP_TYPES, FND_LOOKUP_TYPES_TL, and FND_LOOKUP_VALUES are consulted and populated by the lookup migration. Destination E-Business Tax tables include ZX_ACCOUNTS and ZX_ACCOUNTS_S (tax accounts), and ZX_CONDITIONS and ZX_CONDITIONS_S (condition groups and their translated/seed rows). Additional ZX tables not explicitly listed (such as ZX_TAXES_B, ZX_TAX_STATUS_B, ZX_RATES_B, and ZX_RULES_B) are implied by the procedure semantics. AR_VAT_TAX_ALL_B is referenced to align VAT tax definitions between Receivables and the tax engine.

Usage Notes

ZX_MIGRATE_TAX_DEF is a setup/migration-time utility rather than a runtime API. It is typically invoked from controlled environments such as migration scripts, SQL*Plus sessions as the APPS user, or wrapper concurrent programs, often executed procedure-by-procedure in the documented sequence (lookups and classifications first, then statuses, taxes, condition groups, rules, and accounts). The optional p_tax_id parameter allows administrators to re-run or validate migration for a single tax code without reprocessing the entire configuration. It is referenced by one other package, indicating that a higher-level orchestration routine may call it. ETRM classifies it as OTHER rather than a public API, so it should be used cautiously, with full backups and testing, and is not a supported integration point for ongoing tax maintenance.