Search Results synch_ptp_code_assigment




Overview
Explore in AI Chat

Overview

ZX_TCM_BES_REGISTRATION_PVT is a private PL/SQL package in the Oracle E-Business Tax (EBTax) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. It forms part of the Tax Configuration Manager (TCM) layer that maintains the registration and tax profile data of third-party entities — suppliers in Accounts Payable and their corresponding trading parties and party sites in the TCA (Trading Community Architecture) model. The package encapsulates the "BES" (Business Event Subscriptions) registration logic that keeps supplier tax attributes synchronized with the party tax profile repository stored in ZX_PARTY_TAX_PROFILE.

Its primary business function is to propagate and reconcile tax registration information — VAT registration numbers, VAT codes, withholding status and start dates, tax calculation and rounding flags — between supplier records and the centralized party tax profile used by the tax engine. It also serves as the subscription handler for workflow business events emitted when third-party tax profiles change, ensuring that updates to a trading party or party site are reflected consistently across dependent supplier records.

Key Procedures and Functions

  • UPDATE_SUPPLIERS — Updates supplier-level tax attributes for a given party, including indicators for whether amounts include tax, the AP tax rounding rule, automatic tax calculation, offset tax, VAT code and VAT registration number, and withholding start date and status. This is the principal entry point for maintaining supplier tax defaults.
  • UPDATE_SUPPLIER_SITES — Performs the analogous update at the supplier site level, accepting the party site identifier along with the same tax flags, VAT code and VAT registration number. It allows site-specific tax treatment distinct from the supplier header.
  • SYNCH_PARTY_IMPORT_PTP — Synchronizes party import data with the party tax profile, driven by a concurrent request identifier. It is used to reconcile records created or modified through bulk import processes.
  • PARTY_TAX_PROF_TRD_PARTY — A workflow business event subscription function that handles trading party tax profile change events, returning a completion status and receiving the standard subscription GUID and workflow event payload.
  • PARTY_TAX_PROF_TRD_PTY_SITE — The parallel subscription handler for party site tax profile events, applying the same event-driven synchronization pattern at the site level.
  • SYNCH_PTP_CODE_ASSIGMENT — Synchronizes code assignments on the party tax profile for a given party, class category and class code, returning standard return status, message count and message data. It aligns tax classification codes between the party and its tax profile.

Tables Accessed

The package operates across the AP supplier and TCA/EBTax party tables. AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL hold the supplier header and site records updated by the two UPDATE procedures. ZX_PARTY_TAX_PROFILE and its _S (sequence/identifier) table store the centralized tax profile data written during synchronization. HZ_PARTIES and HZ_PARTY_SITES provide the TCA party and site identifiers that link supplier records to their tax profiles, while HZ_CODE_ASSIGNMENTS and HZ_CODE_ASSIGNMENTS_S store the classification code assignments managed by SYNCH_PTP_CODE_ASSIGMENT. WF_EVENT_T is the workflow event payload structure consumed by the two subscription functions. All access is via APPS synonyms.

Usage Notes

As a PVT-classified package, ZX_TCM_BES_REGISTRATION_PVT is not intended for direct invocation by external code; it is called internally by EBTax configuration and registration flows, most commonly from the Supplier and Supplier Site setup forms in Payables when tax attributes are entered or changed. The UPDATE procedures are typically driven by form-level logic, while SYNCH_PARTY_IMPORT_PTP and SYNCH_PTP_CODE_ASSIGMENT are invoked from concurrent or import-driven synchronization processes. The PARTY_TAX_PROF functions are registered as Business Event System subscriptions, so they execute automatically when the corresponding party or party site tax profile events are raised. The package is referenced by one other documented package, and customizations should treat these signatures as internal and subject to change across releases such as 12.1.1 and 12.2.2.