Results for “ece_cdmo_line_tax_v”

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

Overview

ECE_CDMO_LINE_TAX_V is a private view owned by the APPS schema in Oracle E-Business Suite, defined within the e-Commerce Gateway (EC) product. It is documented as the Credit/Debit Memo Line Tax View and is registered as a BUSINESS_ENTITY under the AR product family with an active lifecycle status. Its stated purpose is to extract line-level tax information for the outbound Credit/Debit Memo transaction, referenced in EDI terms as 812/CREADV/DEBADV.

In practice, this view functions as the data source that e-Commerce Gateway uses when generating the outbound 812 Credit/Debit Memo interface. Rather than exposing raw transactional columns directly, it reshapes receivables tax lines into the flattened structure expected by the outbound mapping, combining header, line, and tax code attributes into a single row per tax line. It is therefore an integration-facing object rather than an end-user reporting view.

Underlying Base Objects

The view is defined over three documented base objects in the APPS schema, all exposed as synonyms:

• RA_CUSTOMER_TRX (aliased RCT) — the receivables transaction header, supplying the transaction identifier.
• RA_CUSTOMER_TRX_LINES (aliased RCTL1 and RCTL2) — the transaction lines, self-referenced twice: RCTL1 resolves the parent line to which the tax applies, while RCTL2 supplies the tax line itself.
• AR_VAT_TAX (aliased AVT) — the tax code definition, supplying tax codes, descriptions, tax types, VAT transaction types, and VAT-level descriptive attributes.

Because RA_CUSTOMER_TRX_LINES is joined to itself, the view correlates each tax line back to the inventory or memo line it is linked to via LINK_TO_CUST_TRX_LINE_ID, producing a hierarchical tax representation suitable for outbound conversion.

Key Columns

The view exposes a broad column set covering identity, amounts, tax reference data, and descriptive attributes:

• TRANSACTION_ID / LINE_NUMBER — the header transaction identifier and the parent line number.
• CUSTOMER_TRX_LINE_ID / TAX_LINE_NUMBER / LINE_TYPE — the tax line's identifier, its line number, and its line type classification.
• TAX_AMOUNT / TAX_RATE — the extended amount and rate applied to the tax line.
• TAX_PRECEDENCE — the precedence value carried on the tax line, indicating the order in which the tax applies relative to other taxes. This is the column most relevant to the user's search term, tax_precedence.
• TAX_CODE / DESCRIPTION / TAX_TYPE / VAT_TRANSACTION_TYPE — tax code reference data sourced from AR_VAT_TAX.
• TAX_EXEMPT_FLAG / TAX_EXEMPT_NUMBER / TAX_EXEMPT_REASON_CODE — exemption indicators carried from the tax line.
• TAX_ATTRIBUTEn (1–15) and VAT_TAX_ATTRIBUTEn (1–11) — descriptive flexfield attribute columns from the tax line and from the tax code definition respectively.
• LOCATION / TAX_CLASSIFICATION — both are returned as NULL literals in the view text and therefore carry no values.

Common Use Cases and Queries

Typical usage centers on validating or debugging the outbound 812 extract, particularly where tax precedence or tax amount sequencing appears incorrect in the generated flat file. A representative query joining the view to the transaction header is:

• SELECT h.trx_number, t.line_number, t.tax_line_number, t.tax_code, t.tax_amount, t.tax_rate, t.tax_precedence FROM ece_cdmo_line_tax_v t, ra_customer_trx_all h WHERE t.transaction_id = h.customer_trx_id AND h.trx_number = :trx_number ORDER BY t.line_number, t.tax_precedence;
• Filtering on tax_precedence to confirm ordering — WHERE t.tax_precedence IS NOT NULL — is common when reconciling multi-level tax structures.
• Exemption auditing via SELECT transaction_id, tax_line_number, tax_exempt_flag, tax_exempt_number FROM ece_cdmo_line_tax_v WHERE tax_exempt_flag = 'Y';

Because the view is private, it should be treated as an internal e-Commerce Gateway artifact. Direct modification or reliance for custom reporting carries support risk, and taxable scenarios should reference the documented columns above rather than the NULL placeholders LOCATION and TAX_CLASSIFICATION.