Results for “interface_entity_code”

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

Overview

ZX_IMPORT_TAX_LINES_GT is a global temporary table (GTT) in the ZX (E-Business Tax) schema of Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented purpose is to pass summary or detail tax lines when importing documents with tax. In practice, it serves as the inbound staging interface for external applications, legacy systems, and third-party integrations that must create tax lines within E-Business Tax without directly writing to the permanent tax tables. The GTT footprint means rows are session-scoped: data persisted here is visible only to the importing session and is normally consumed and purged as part of the import or tax calculation process. From a heuristic Data Vault modeling perspective, this object is best classified as a standalone structure, since the mined foreign-key relationships point outward to operational tables rather than forming an internal hub-link-satellite chain within the table itself. It behaves as a transient transaction-level staging artifact rather than a durable entity in the tax data model.

Key Information Stored

The table contains 48 documented columns, reflecting the breadth of attributes required to reconstruct a tax line during import. The most significant columns fall into identity, context, and tax computation groups:

• Business-key and context columns: APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, and SUMMARY_TAX_LINE_NUMBER collectively form the unique index ZX_IMPORT_TAX_LINES_GT_U1, which acts as the business-key candidate for the staging row.
• Internal identifiers: INTERNAL_ORGANIZATION_ID identifies the operating unit context, while TRX_LINE_ID (a foreign key to CN_TRX_LINES_ALL) ties the tax line to a specific transaction line.
• Header reference keys: HDR_TRX_USER_KEY1 through HDR_TRX_USER_KEY6 carry user-defined transaction identifiers used to match inbound tax records to their source documents.
• Tax definition attributes: TAX_REGIME_CODE, TAX, TAX_STATUS_CODE, TAX_RATE_CODE, TAX_RATE, and TAX_JURISDICTION_CODE describe the tax being applied, with TAX_RATE_ID and TAX_PROVIDER_ID referencing determinate configuration.
• Tax amounts: TAX_AMT and TAX_AMT_INCLUDED_FLAG capture the computed tax value and whether it is embedded in the line amount.
• Exemption and exception data: TAX_EXCEPTION_ID (foreign key to ZX_EXCEPTIONS), TAX_EXEMPTION_ID, EXEMPT_REASON_CODE, and EXEMPT_CERTIFICATE_NUMBER support exemption handling.
• Interface and allocation fields: INTERFACE_ENTITY_CODE, INTERFACE_TAX_LINE_ID, TAX_LINE_ALLOCATION_FLAG, and TAX_DATE drive downstream processing and allocation logic.
• Descriptive flexfields: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 provide extensibility for integration-specific data.

No standalone surrogate primary key column is documented; the unique index on the business attributes serves as the logical key.

Common Use Cases and Queries

Typical usage involves a calling program inserting tax line rows into the GTT, invoking the tax import or calculation API to process them, and then validating the outcome. Common queries include checking staged rows prior to import, reconciling tax amounts against source documents, and diagnosing rejected or unmatched lines. A representative pattern joins the GTT to transaction lines for validation:

• SELECT g.SUMMARY_TAX_LINE_NUMBER, g.TRX_ID, g.TAX_REGIME_CODE, g.TAX_AMT FROM ZX_IMPORT_TAX_LINES_GT g WHERE g.TRX_ID = :trx_id;
• Joining ZX_IMPORT_TAX_LINES_GT to CN_TRX_LINES_ALL on TRX_LINE_ID to confirm line-level correspondence.
• Reporting on TAX_STATUS_CODE or TAX_EXCEPTION_ID distributions across an import batch.
• Auditing exemption certificates via EXEMPT_CERTIFICATE_NUMBER for compliance reporting.

Because the table is temporary and session-scoped, queries must execute within the same database session that populated it; data is not available for cross-session reporting.

Related Objects

The documented foreign keys and surrounding tax model point to several significant related objects:

• CN_TRX_LINES_ALL — referenced by TRX_LINE_ID; the transaction line to which the imported tax applies.
• ZX_EXCEPTIONS — referenced by TAX_EXCEPTION_ID; holds exception definitions applied during tax determination.
• ZX_LINES / ZX_LINES_DET_FACTORS — permanent tax line tables that ultimately receive processed results.
• ZX_RATES_B and ZX_RATE_CODES_B — provide the rate configuration referenced by TAX_RATE_ID and TAX_RATE_CODE.
• ZX_REGIMES_B and ZX_JURISDICTIONS_B — define the regime and jurisdiction named by TAX_REGIME_CODE and TAX_JURISDICTION_CODE.
• ZX_EXEMPTIONS — supplies exemption records linked through TAX_EXEMPTION_ID.
• Public APIs such as ZX_TAX_PUB or the ZX import program consume this GTT as their inbound interface.

Together these objects form the determination-and-import path that carries external tax data into the E-Business Tax repository.