Results for “ship_to_address_code”

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

Overview

The AS_TAX_LINES_SUMMARY_VBR view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the JL – Latin America Localizations product family. The suffix "VBR" denotes a "View By Request," a naming convention Oracle uses for reporting views whose row population is governed by a concurrent request identifier (REQUEST_ID). Such views are typically consumed by Oracle Reports, BI Publisher templates, and external integration layers that extract localized tax line detail from the E-Business Tax (EBTax) and Receivables tax engines for Latin American country requirements.

The view presents a horizontally flattened tax line summary: transactional header and line identifiers, customer ship-to and bill-to information, tax regime attributes (tax code, rate, amount, exempt and taxable flags), accounting context (GL date, set of books, currency, exchange rate), and a broad set of descriptive flexfield columns (ATTRIBUTE1–5 and NUMERIC_ATTRIBUTE1–5). It is designed to support statutory Latin America tax reporting, including fiscal book reporting, VAT and withholding analysis, and audit extracts.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the only documented referenced base object for AS_TAX_LINES_SUMMARY_VBR is DUAL, which is accessed through a SYNONYM. This is significant: the documented view text selects a series of literal NULL values from DUAL, producing a structurally complete but empty result set. In other words, in the shipped, unpatched form, the view acts as a placeholder or template whose column projection defines the contract expected by downstream reports, while the actual row-producing logic is supplied or substituted by localization patches, country-specific implementations, or customer extensions.

Because no transactional base tables (such as RA_CUSTOMER_TRX_LINES, ZX_LINES, or JL tax tables) are documented as direct references, the view should be treated as a presentation-layer stub. Implementations that require populated data must rely on Oracle-supplied localization patches or a customer-defined replacement view conforming to the same column signature.

Key Columns

• TRX_HEADER_ID, TRX_LINE_ID, TRX_LINK_TO_CUST_TRX_LINE_ID – Transaction header and line linkage into Receivables and E-Business Tax.
• TRX_NUMBER, TRX_DATE, TRX_TYPE_ID, TRX_LINE_TYPE – Transaction identification and classification.
• SHIP_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_NAME, BILL_TO_CUSTOMER_NUMBER – Party and site context for tax determination.
• TAX_CODE, TAX_RATE, TAX_AMOUNT, TAXABLE_FLAG, TAX_EXEMPT_FLAG, TAX_ROUNDING_RULE – Core tax computation and exemption attributes.
• GL_DATE, SET_OF_BOOKS_ID, CURRENCY_CODE, EXCHANGE_RATE – Accounting and conversion context.
• SHIP_TO_POSTAL_CODE, BILL_TO_POSTAL_CODE, LOCATION_QUALIFIER, POO_ADDRESS_CODE, FOB_CODE – Geography and place-of-supply determinants used in Latin America tax rules.
• TAX_EXEMPTION_ID, TAX_EXCEPTION_ID, VENDOR_CONTROL_EXEMPTIONS, TAX_EXEMPT_NUMBER – Exemption and exception tracking.
• ATTRIBUTE1–5, NUMERIC_ATTRIBUTE1–5 – Descriptive flexfield segments for localization-specific data.
• REQUEST_ID – Concurrent request key, confirming the "by request" reporting pattern.

Common Use Cases and Queries

Typical usage includes statutory Latin America tax reports, fiscal audit extracts, and reconciliations between E-Business Tax lines and General Ledger. Because the shipped view returns no rows, queries are generally executed after localization patches are applied or against a customer extension view. A representative query follows:

SELECT request_id,
       trx_number,
       trx_date,
       tax_code,
       tax_rate,
       tax_amount,
       taxable_flag,
       currency_code,
       ship_to_postal_code
  FROM apps.as_tax_lines_summary_vbr
 WHERE request_id = :p_request_id
   AND trx_date BETWEEN :p_from_date AND :p_to_date
 ORDER BY trx_date, trx_number;

Consultants should verify column data types, confirm whether a localization patch populates the view, and validate row counts before using it as a reporting source. Where the shipped definition is insufficient, the recommended approach is to create a custom view with an identical column signature and substitute it in the report definition.