Search Results ship_from_address_code

Overview

ICX_TAX_LINES_CREDIT_CHECK_V is a database view historically shipped within the Oracle iProcurement (ICX) product family. Its name indicates its original purpose: to supply a normalized, tax-calculation-ready projection of purchasing document lines that a credit-checking or tax-interface routine could interrogate. The view flattens header, line, ship-to, bill-to, customer, and currency attributes into a single row per transaction line, together with derived quantity and extended-amount figures, so that an external tax engine or internal credit validation program could consume one consistent record per line.

In the ETRM metadata for Oracle EBS 12.2.2, the object is explicitly flagged as Obsolete and marked Not implemented in this database. No owner is documented, and no referenced base objects are enumerated in the repository. This status is consistent across the 12.1.1 and 12.2.2 documentation sets: the view is retained only as a legacy artifact of the view definition text and is not expected to exist in a functioning 12.2.2 instance. It should not be treated as a supported integration point or a reliable reporting source in current releases.

Underlying Base Objects

The ETRM metadata documents no base objects for this view. The retained view text, however, references several underlying constructs by alias, including a header table (H), a line table (L), customer account tables (A_SHIP, A_BILL), site-use tables (S_SHIP, S_BILL), a currency table (C), a tax code/rate source (V), and an inventory type lookup (INV_TYPE). These aliases point to the standard order-management and receivables-adjacent structures used for tax line extraction in that era. Because no exact base-object mapping is documented, the join relationships cannot be authoritatively reproduced from ETRM alone; any reconstruction would require inspecting a legacy pre-12.2 database where the view was still deployed.

Key Columns

The view exposes a broad set of tax-interface columns, many of which are unconditionally NULL placeholders inherited from a generic tax-line template:

• SHIP_TO_CUSTOMER_ID / BILL_TO_CUSTOMER_ID — customer identifiers resolved from the ship-to and bill-to account records.
• TRX_LINE_ID / TRX_HEADER_ID — the line and header primary keys of the underlying purchasing transaction.
• TRX_DATE — derived through nested NVL logic over SCHEDULE_DATE, DATE_REQUESTED_CURRENT, PROMISE_DATE, defaulting to SYSDATE.
• TAX_CODE / TAX_RATE — sourced from the tax code view alias; TAX_AMOUNT is NULL.
• SHIP_TO_POSTAL_CODE / BILL_TO_POSTAL_CODE and the corresponding LOCATION_CCID columns — address determinants used for jurisdiction resolution.
• EXTENDED_AMOUNT — computed as (ORDERED_QUANTITY minus CANCELLED_QUANTITY minus INVOICED_QUANTITY) multiplied by SELLING_PRICE.
• TAX_QUANTITY — the residual order quantity after cancellations and invoices.
• TAXABLE_FLAG — derived via DECODE from the inventory item tax calculation flag and the header tax-exempt flag.
• POO_ADDRESS_CODE / POA_ADDRESS_CODE / SHIP_FROM_ADDRESS_CODE / SHIP_TO_ADDRESS_CODE — all hard-coded NULL, with LOCATION_QUALIFIER fixed to the literal 'ALL'.

The presence of the poo_address_code column explains why this view surfaces in searches for that term, even though the column carries no data.

Common Use Cases and Queries

Because the object is obsolete, it has no sanctioned use case in 12.1.1 or 12.2.2. Historical queries against it were limited to tax-line extraction and credit-limit validation during iProcurement checkout. A representative legacy query took the form:

• SELECT trx_header_id, trx_line_id, tax_code, tax_rate, extended_amount, taxable_flag FROM icx_tax_lines_credit_check_v WHERE trx_header_id = :header_id;
• SELECT ship_to_postal_code, bill_to_postal_code, poo_address_code FROM icx_tax_lines_credit_check_v WHERE tax_quantity > 0;

Any reference to this view in a modern 12.2.2 instance will fail, since the object is not implemented. The correct remediation is to migrate to the supported E-Business Tax (EBTax) repository views, such as those in the ZX schema, or to the current iProcurement tax determination APIs. The poo_address_code column should be regarded purely as a template placeholder with no functional meaning.