Results for “trx_line_number”

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

Overview

ZX_SYNC_LINES_INPUT_V is a view owned by the APPS schema in Oracle E-Business Suite, classified under the FND – Application Object Library product. As its name implies, it is an input (staging) view used within the Oracle E-Business Tax (ETRM / ZX) synchronization framework, specifically to drive the synchronization of transaction line-level data — tax drivers, line extended attributes, and transaction preprocessing factors — into the tax repository. The view consolidates the three principal inputs consumed when populating tax lines: deterministic factor data from the transaction line-level factors table, provider-defined line extension attributes held in a global temporary table, and transaction pre-processing options. It therefore serves as a single flattened query surface from which the tax synchronization program (typically the ZX_LINES sync concurrent processes) reads to build tax lines and their associated tax drivers.

The suffix "_V" identifies it as a view rather than a table, and the suffix "_INPUT" confirms its role as a feeder of source data rather than a persisted tax result. Because the view is defined at the line level, it is the intersection point where tax determination factors, user-defined line extended attributes configured in the tax regime, and processing options converge for each transaction line.

Underlying Base Objects

The documented ETRM 12.2.2 metadata lists three referenced base objects, all exposed to the view as APPS synonyms:

• ZX_LINES_DET_FACTORS (aliased ZLDF) — the transaction line deterministic factors used in tax determination. The view draws transaction identifiers, line identifiers, line numbers, descriptions, product descriptions, event class mapping identifiers, legal entity, and place of supply attributes from this source.
• ZX_PRVDR_LINE_EXTNS_GT (aliased ZPSLEA) — a global temporary table holding provider line extension attributes. This is the object most directly implied by the user's search term zx_prvdr_line_extns_gt. It supplies the 30 nullable varchar line extended attributes, 10 number line extended attributes, and date line extended attributes.
• ZX_TRX_PRE_PROC_OPTIONS_GT (aliased ZTPPO) — a global temporary table of transaction preprocessing options, contributing legal entity number and establishment name.

The use of global temporary tables signals that the view is populated within the context of a single session or concurrent run, where the sync process first loads provider extension data and processing options into the temporary tables and then joins them to the persistent factor data via the view.

Key Columns

The view exposes a wide projection dominated by the provider line extension columns, plus a set of transaction-identifying and factor columns. Notable columns include:

• TRX_LINE_ID, TRX_ID, TRX_LINE_NUMBER — transaction and line identifiers. Note that the view text carries a comment reflecting Bug 5090593, where TRX_NUMBER was changed to TRX_LINE_NUMBER, so consumers should treat the line number — not a transaction number — as the meaningful key.
• TRX_LEVEL_TYPE, EVENT_CLASS_MAPPING_ID — classification of the synchronization level and the tax event class mapping used for determination.
• INTERNAL_ORGANIZATION_ID, LEGAL_ENTITY_NUMBER, ESTABLISHMENT_NAME — party and organization context for the transaction line.
• PRODUCT_DESCRIPTION, TRX_DESCRIPTION — descriptive text for reporting and diagnostics.
• LINE_EXT_VARCHAR_ATTRIBUTE1 through 30 — configurable provider line extension varchar attributes.
• LINE_EXT_NUMBER_ATTRIBUTE1 through 10 — numeric provider line extension attributes.
• LINE_EXT_DATE_ATTRIBUTE1 onward — date-based provider line extension attributes.

These extension attribute columns are the mechanism by which customer-configured tax attributes flow from the provider interface into tax line derivation.

Common Use Cases and Queries

The primary use case is tax synchronization and diagnostics: identifying which transaction lines have provider extension attributes loaded, troubleshooting missing tax lines, or verifying that line-level deterministic factors align with provider-supplied attributes during a sync run.

• Inspect loaded provider line extensions for a session before a sync run:

SELECT trx_line_id, trx_line_number, line_ext_varchar_attribute1
FROM   apps.zx_sync_lines_input_v
WHERE  trx_line_id IS NOT NULL;

• Verify whether number or date extension attributes are populated for a given line:

SELECT trx_line_id, line_ext_number_attribute1, line_ext_date_attribute1
FROM   apps.zx_sync_lines_input_v;

Because the view depends on global temporary tables, queries executed outside the sync session will generally return no rows, and direct ad-hoc querying is best performed within the same session that loaded ZX_PRVDR_LINE_EXTNS_GT and ZX_TRX_PRE_PROC_OPTIONS_GT. Troubleshooting should therefore pair this view with the loading program rather than treating it as a standalone reporting object.