Search Results zx_party_tax_profile_s




Overview
Explore in AI Chat

Overview

ZX_TCM_BES_REGISTRATION_PVT is a private PL/SQL package body in the APPS schema that supports the registration and synchronization of third-party (TCM/BES) party tax profiles within Oracle E-Business Tax. Its principal business function is to reconcile tax registration data captured outside the standard EBS tax setup flows back into the EBS Tax repository, specifically against the ZX_PARTY_TAX_PROFILE entity and its related supplier, party, and party site records. The package operates as an internal (private, classification PVT) implementation component rather than as a public API, meaning it is designed to be invoked by a thin public wrapper or a higher-level registration program rather than directly by end users or by external integrations.

Because it is not referenced by any other database object per the ETRM metadata, it acts as a leaf dependency: it consumes shared services from FND_API, FND_GLOBAL, and the Workflow event stack (WF_EVENT_T) but exposes no referential surface for downstream packages. The package therefore serves as the internal engine that transforms inbound third-party tax registration payloads into consistent supplier, supplier site, and party tax profile records.

Key Procedures and Functions

  • UPDATE_SUPPLIERS — Updates supplier-level records in AP_SUPPLIERS, aligning supplier registration attributes (such as tax identifiers and registration numbers) with the corresponding party tax profile.
  • UPDATE_SUPPLIER_SITES — Updates supplier site records in AP_SUPPLIER_SITES_ALL, propagating site-level tax registration details to the associated party site tax profile.
  • SYNCH_PARTY_IMPORT_PTP — Synchronizes imported party data with the party tax profile, ensuring that newly imported or refreshed parties carry the correct registration attributes within ZX_PARTY_TAX_PROFILE.
  • PARTY_TAX_PROF_TRD_PARTY — Handles party-level (third-party/trading party) tax profile synchronization for the top-level party entity.
  • PARTY_TAX_PROF_TRD_PTY_SITE — Handles party-site-level tax profile synchronization for the individual party site associated with a trading partner.
  • SYNCH_PTP_CODE_ASSIGMENT — Synchronizes code assignments held in HZ_CODE_ASSIGNMENTS and HZ_CODE_ASSIGNMENTS_S with the party tax profile, maintaining consistency between classification codes and tax registration records.

Tables Accessed

The package reads and writes the core Tax and Trading Community repositories through APPS synonyms:

  • ZX_PARTY_TAX_PROFILE / ZX_PARTY_TAX_PROFILE_S — The primary target of all synchronization activity; stores party and party-site tax registration and profile data.
  • AP_SUPPLIERS / AP_SUPPLIER_SITES_ALL — Supplier and supplier site master records updated with registration attributes.
  • HZ_PARTIES / HZ_PARTY_SITES — The TCA party and party site entities providing the parent context for tax profiles.
  • HZ_CODE_ASSIGNMENTS / HZ_CODE_ASSIGNMENTS_S — Classification code assignments synchronized alongside the tax profile.
  • WF_EVENT_T — Workflow event structure used to raise business events upon synchronization.

Usage Notes

This private package is not intended for direct invocation. It is typically called by the public party tax profile registration and import APIs, by concurrent programs that process third-party (TCM/BES) registration feeds, and by the Oracle Trading Community import/registration pipeline that creates or updates suppliers and parties. Custom code should not call ZX_TCM_BES_REGISTRATION_PVT directly; integrators should use the corresponding public API surface so that validation, event publication, and transactional integrity are preserved. Because the package publishes Workflow events (WF_EVENT_T), synchronization activities may trigger downstream subscription logic, including tax profile event handlers. The presence of ZX_PARTY_TAX_PROFILE_S indicates that profile records are maintained in a multilingual/translated table pair, so users should query the _S (_TL) variant when retrieving descriptive fields and the base table when retrieving transactional identifiers. This behavior is consistent across Oracle EBS 12.1.1 and 12.2.2, with the 12.2.2 ETRM metadata confirming six documented program units and the table set listed above.