Results for “zx_id_tcc_mapping”

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

Overview

APPS.PO_SHIPMENTS_SV9 is a server-side PL/SQL package body in the Oracle E-Business Suite Purchasing (PO) module. It belongs to the family of shipment validation and server-side helper packages (SV1, SV2, SV3, SV5, SV9, SV10) that support the shipment and distribution processing logic used by the Oracle Purchasing forms and the underlying shipment server routines.

The package is classified as an "OTHER" API object rather than a public interface API. Its procedures are predominantly prefixed with TEST_VAL_ and TEST_GET_, indicating that this is an internal utility package used to validate shipment-level attributes and retrieve shipment information during form processing. It is not a published integration API and, per the ETRM dependency metadata, is not referenced by any other database object. Its principal role is to encapsulate validation and retrieval logic for shipment records, including planned shipment information, shipment numbering, scheduling, approval status, and start/end date ranges, so that those checks can be reused by the Oracle Purchasing shipment forms and by the other SV-series packages.

The package is valid in both 12.1.1 and 12.2.2. One notable element of its dependency footprint is ZX_ID_TCC_MAPPING, a Tax configuration (ZX) table used by E-Business Tax to map tax classification codes to tax regimes and taxes. A user searching for "zx_id_tcc_mapping" is typically investigating where this tax mapping table is queried within the Purchasing code base; PO_SHIPMENTS_SV9 is one such location.

Key Procedures and Functions

The package body exposes thirteen documented procedures and functions, all of which are internal test/utility routines:

• TEST_GET_SHIPMENT_NUM — retrieves the shipment number for a given shipment/distribution context.
• TEST_GET_PLANNED_SHIP_INFO — returns planned shipment information (for example, planned dates and quantities) for a line location.
• TEST_GET_SCHED_RELEASED_QTY — obtains the quantity already released against a shipment schedule.
• TEST_GET_NUMBER_SHIPMENTS — returns the count of shipments associated with a given line or line location.
• TEST_VAL_RELEASE_SHIPMENTS — validates whether a shipment may be released, based on current shipment state.
• TEST_GET_LINE_LOCATION_ID — retrieves the LINE_LOCATION_ID that uniquely identifies a shipment/distribution record.
• TEST_GET_SHIPMENT_STATUS — returns the current status of a shipment.
• TEST_VAL_SHIP_QTY — validates shipment quantities against sourcing and tolerance rules.
• TEST_VAL_SHIP_PRICE — validates the shipment price against the associated purchase order or agreement price.
• TEST_VAL_APPROVAL_STATUS — validates the approval status of the shipment or its parent document.
• TEST_SOURCE_LINE_SERVER_COVER — determines whether a sourcing line covers the requested shipment, used in the sourcing/coverage validation path.
• TEST_VAL_START_DATES — validates start date values for shipment scheduling.
• TEST_VAL_END_DATES — validates end date values for shipment scheduling.

Parameter lists are not documented in the ETRM metadata and should not be assumed; the descriptions above reflect the semantic purpose implied by the procedure names.

Tables Accessed

The documented table references for this package are:

• ZX_ID_TCC_MAPPING (via APPS synonym) — the E-Business Tax mapping table linking tax classification codes to tax regimes and taxes. Within this package it is referenced as part of the tax-related validation performed during shipment pricing and approval checks, so that the correct tax classification is applied to the shipment.
• HR_LOCATIONS_ALL — the HR locations table, used to resolve ship-to or deliver-to location identifiers and addresses associated with a shipment or line location.
• DBMS_OUTPUT — the standard Oracle debug/output package, referenced for diagnostic or test-time messaging. Its presence reinforces the internal, non-production nature of this package.

In addition, the package body depends on the sibling packages PO_SHIPMENTS_SV1, SV2, SV3, SV5, and SV10 by way of shared internal logic. These dependencies are code-level references, not table accesses.

Usage Notes

PO_SHIPMENTS_SV9 is not a published API and is not referenced by any other database object per the ETRM dependency report. It is characteristically invoked indirectly from the Oracle Purchasing shipment and distribution forms (for example, the Purchase Order Shipments and Distributions windows) and from the shipment server routines that handle scheduling, release, and approval. Developers extending or debugging Oracle Purchasing shipment validation should treat the TEST_ prefixed procedures as diagnostic entry points; the prefix signals that they are intended for internal testing rather than supported integration.

Because the package is not callable from a supported public interface, custom code should not invoke PO_SHIPMENTS_SV9 directly. Customers requiring shipment validation logic should use the supported PO APIs (such as PO_Document_Control_API or the PO_Shipments_PUB patterns) instead. Any investigation involving ZX_ID_TCC_MAPPING that reaches this package should be treated as a study of internal Oracle code, and modifications should not be made to the package body itself.