Results for “partner_processing_flag”

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

Overview

ZX_TRX_PRE_PROC_OPTIONS_GT is a global temporary table owned by the ZX schema in Oracle E-Business Tax. It stores the provider pre-processing options that apply to the regime governing a transaction under consideration, assembled before the tax engine invokes the corresponding service of the tax provider. In practice the table acts as a transient decision buffer: E-Business Tax populates it with the processing posture for each transaction line item — whether tax should be calculated, whether partner-side processing is required, whether the event is a quotation, and which tax provider is responsible — and then services such as the third-party or internal tax calculation interfaces read those flags to determine their behavior.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. As a modeling suggestion, it is therefore best treated as an independent staging or work structure rather than as a hub, link, or satellite. Its composite primary key carries transaction identity, and no downstream foreign keys were identified, which reinforces its role as a session-scoped intermediate rather than a durable master or reference entity.

Key Information Stored

The table is documented with 24 columns. The most significant are:

• APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID — the four columns constituting the primary key ZX_TRX_PRE_PROC_OPTIONS_GT_PK and the unique index ZX_TRX_PRE_PROC_OPTIONS_GT_U1. Together they identify the application, the entity (for example a line or header), the event class, and the transaction itself; this quartet is the business-key candidate.
• TAX_REGIME_CODE — the tax regime applicable to the transaction, the anchor for the pre-processing rules being evaluated.
• TAX_PROVIDER_ID — the tax provider whose service will be called after the options are resolved.
• ALLOW_TAX_CALCULATION_FLAG — indicates whether tax calculation is permitted for the transaction.
• PARTNER_PROCESSING_FLAG and RECORD_FOR_PARTNERS_FLAG — control whether partner-side processing applies and whether records must be retained for partners.
• QUOTE_FLAG and RECORD_FLAG — distinguish quotation-style processing from records intended to be persisted.
• TAX_EVENT_TYPE_CODE, EVENT_ID, EVNT_CLS_MAPPING_ID — identify the tax event and its event-class mapping.
• PROD_FAMILY_GRP_CODE — the product family group qualifying the transaction.
• INTERNAL_ORGANIZATION_ID, APPLICATION_SHORT_NAME, LEGAL_ENTITY_NUMBER, ESTABLISHMENT_NUMBER — organizational and legal-entity context.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard audit columns.

Common Use Cases and Queries

Because the table is a global temporary structure, its contents persist only for the session or transaction that populated them. Typical uses include debugging why tax was suppressed on a transaction, verifying which provider was selected for a given regime, and supporting reconciliation of partner processing. A representative query retrieves the pre-processing posture for a specific transaction:

• SELECT trx_id, tax_regime_code, tax_provider_id, allow_tax_calculation_flag, partner_processing_flag, quote_flag, record_flag FROM zx.zx_trx_pre_proc_options_gt WHERE application_id = :app_id AND entity_code = :entity AND event_class_code = :event_class AND trx_id = :trx_id;
• SELECT tax_provider_id, allow_tax_calculation_flag, COUNT(*) FROM zx.zx_trx_pre_proc_options_gt GROUP BY tax_provider_id, allow_tax_calculation_flag; to profile how many transactions in the current session were routed to each provider.
• A join to the event-class mapping to confirm the event taxonomy: ... WHERE evnt_cls_mapping_id = :mapping_id.

Reporting against this table is inherently limited to live session data; historical analysis should draw on E-Business Tax repository and audit objects instead.

Related Objects

The documented relationship data classifies the table as standalone, with no foreign keys to or from other objects. In operational terms, however, it is read alongside the wider E-Business Tax infrastructure:

• ZX_TRX_PRE_PROC_OPTIONS_GT consumes transaction identity that originates from the application transaction tables referenced by APPLICATION_ID and ENTITY_CODE.
• Tax regime and provider reference data joined via TAX_REGIME_CODE and TAX_PROVIDER_ID.
• Event-class mapping objects referenced through EVNT_CLS_MAPPING_ID and TAX_EVENT_TYPE_CODE.
• E-Business Tax calculation and service APIs that read the option flags before invoking the provider.
• Tax repository and audit tables that retain the deterministic output once the pre-processing decision has been made.

No FK constraints are documented, so joins are conventional rather than enforced, and the table should be treated as a transient input to the tax determination flow.