Results for “port_of_entry_code”

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

Overview

The ZX_TRANSACTIONS_V view is an Oracle E-Business Suite dictionary object owned by the APPS schema and registered under the FND – Application Object Library product. Despite its FND registration, the object is functionally part of the E-Business Tax (EBTax / ZX) reporting layer in EBS 12.1.1 and 12.2.2. It presents a denormalized, reporting-friendly projection of the E-Business Tax transaction repository, allowing users and integrators to read the tax-relevant attributes of a business transaction without navigating the numerous internal foreign keys and identifier columns held on the underlying base entity.

The view is most valuable because it resolves the raw surrogate identifiers stored on the tax transaction into human-readable values. Operating unit names, application names, and legal entity names are joined in, and the transactional parties, sites, and locations are exposed alongside their rounding counterparts. As a result, the view serves both as an ad hoc reporting source for tax analysts and as an integration endpoint for external tax engines, reconciliation extracts, and audit queries.

Underlying Base Objects

The view is defined over the following documented base objects:

• ZX_TRANSACTION – the core E-Business Tax transaction table that stores the tax attributes of each transaction. In the view text it is aliased as TRX and supplies the majority of columns, including the ROWID exposed as ROW_ID.
• HR_OPERATING_UNITS – joined to derive the OPERATING_UNIT column from the transaction's operating unit identifier.
• FND_APPLICATION_VL – joined on APPLICATION_ID to return APPLICATION_NAME, identifying the source application (for example Receivables, Payables, or Purchasing) that generated the transaction.
• XLE_ENTITY_PROFILES – joined to resolve the legal entity name, returned as an unnamed name column in the projection.

Because the view is built on these base objects, it inherits the validity and security characteristics of the underlying tax transaction records. Access is governed by APPS schema privileges and by any custom responsibility-level security applied to the ZX tables.

Key Columns

The view exposes a broad column set that can be grouped as follows:

• Identity and context: ROW_ID, TRX_ID, APPLICATION_ID, APPLICATION_NAME, ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE, DOCUMENT_EVENT_TYPE, TRX_NUMBER, and TRX_DESCRIPTION.
• Organization and ledger: FIRST_PTY_ORG_ID, OPERATING_UNIT, INTERNAL_ORGANIZATION_ID, LEDGER_ID, LEGAL_ENTITY_ID, LEGAL_ENTITY_PTP_ID, and the joined legal entity name.
• Dates and currency: TRX_DATE, TRX_CURRENCY_CODE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, and CURRENCY_CONVERSION_TYPE.
• Tax event attributes: TAX_EVENT_TYPE_CODE, TAX_MANUAL_ENTRY_FLAG, TAX_REPORTING_FLAG, QUOTE_FLAG, PROVNL_TAX_DETERMINATION_DATE, and APPLIED_TO_TRX_NUMBER.
• Accounting and precision: MINIMUM_ACCOUNTABLE_UNIT, PRECISION, and CTRL_TOTAL_HDR_TX_AMT.
• Party and location references: bill-to, ship-to, ship-from, bill-from, and rounding party identifiers, together with their corresponding site and location identifiers (including POA, POO, paying, own HQ, trading HQ, POC, POI, POD, and title transfer location).
• Invoicing: SUPPLIER_TAX_INVOICE_NUMBER, SUPPLIER_TAX_INVOICE_DATE, SUPPLIER_EXCHANGE_RATE, TAX_INVOICE_DATE, and TAX_INVOICE_NUMBER.

Common Use Cases and Queries

Typical uses include extracting taxable transactions for a period, reconciling tax with source subledgers, and diagnosing rounding or legal entity issues.

• Listing transactions for an operating unit within a date range.
• Joining to tax lines to analyse tax amounts by event class.
• Identifying manual tax entries for audit.

Example:

SELECT trx_number, operating_unit, application_name, entity_code,
       trx_date, trx_currency_code, ctrl_total_hdr_tx_amt
  FROM zx_transactions_v
 WHERE trx_date BETWEEN :p_from AND :p_to
   AND operating_unit = :p_ou;