Results for “ship_from”

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

Overview

ZX_TDS_PROCESS_CEC_PVT is a private (PVT) PL/SQL package owned by APPS within the Oracle E-Business Suite Tax (ZX) module, specifically the Tax Determination Service (TDS) component of E-Business Tax (EBTax). The suffix "CEC" refers to Condition Evaluation Criteria, and the package implements the engine that evaluates tax condition sets and exception sets to determine which tax rules, tax codes, and tax groups apply to a given transaction line. It is a private package, meaning it is not exposed as a public API; it is invoked internally by the tax determination stack to process the hierarchy of condition-driven rules that underpin EBTax configuration for Release 12.1.1 and 12.2.2.

Its central mechanic is the EVALUATE_CEC procedure, which accepts a comprehensive set of transaction context attributes — parties, party sites, locations, transaction and line identifiers, ledger, organizations, product, transaction type, date, and FOB point — and returns a boolean result together with a table of actions (TAX_CODE, TAX_GROUP, USER_MESSAGE, and so on) and status/error buffers. This allows the calling tax determination layer to apply the correct tax treatment without embedding rule logic elsewhere.

Key Procedures and Functions

The package exposes 22 documented procedures and functions organized around the CEC evaluation model:

• EVALUATE_CEC — The primary driver procedure. It evaluates a condition set or exception set against the supplied transaction context and returns a result flag, a table of action records, a return status, and an error buffer.
• SHIP_TO, BILL_TO, SHIP_FROM, POO, POA, TRX, ITEM — Context evaluator functions that test specific transaction attributes (ship-to party, bill-to party, ship-from party, point of order origin, point of order acceptance, transaction, and item) against configured classification, operator, and value criteria, returning a boolean match.
• TAX_CODE, USER_MESSAGE, SYSTEM_MESSAGE — Action handlers that determine tax codes or surface user and system messages as outcomes of rule evaluation.
• APPLY_EXCEPTION, DO_NOT_APPLY_EXCEPTION — Exception handlers controlling whether an exception set applies to the evaluated context.
• USE_TAX_CODE, USE_THIS_TAX_CODE, DEFAULT_TAX_CODE, USE_THIS_TAX_GROUP — Action routines that select and apply tax codes and tax groups.
• DO_NOT_USE_THIS_TAX_CODE, DO_NOT_USE_THIS_TAX_GROUP — Suppression routines that exclude specified tax codes or tax groups from application.
• GET_LOCATION_COLUMN — Utility function that retrieves location-related column values for the evaluation of location-dependent conditions.

Tables Accessed

The package reads and writes across the EBTax and Trading Community foundation tables, including: AR_TAX_CONDITIONS_ALL, AR_TAX_CONDITION_ACTIONS_ALL, and AR_TAX_CONDITION_LINES_ALL (condition definitions, actions, and lines); AR_SYSTEM_PARAMETERS (system-wide AR/tax defaults); ZX_PARTY_TAX_PROFILE and ZX_REGISTRATIONS (party tax profiles and tax registrations used in party-based conditions); HR_LOCATIONS_ALL, HZ_LOCATIONS, HZ_PARTIES, HZ_PARTY_SITES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL (location, party, and customer site context); MTL_SYSTEM_ITEMS (item context for item-based conditions); and FND_DESCR_FLEX_CONTEXTS (descriptive flexfield context data). These accesses support condition matching and action resolution during determination.

Usage Notes

ZX_TDS_PROCESS_CEC_PVT is a private package and is referenced by two other packages within the Tax Determination Service. It is not intended for direct invocation from forms, concurrent programs, or custom code. In standard EBS 12.1.1 and 12.2.2 operation, it is called internally when EBTax evaluates tax rules — for example, during transaction entry in Order Management, Receivables, or Payables, when the tax engine determines applicable taxes for a transaction line. Because it is private, any custom extension should target the public tax determination APIs rather than this package; direct calls risk breakage across patches such as the documented Bug 5128566 fix reflected in the package header.