Results for “template_usage_code”

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

Overview

The view ZX_DET_FACTOR_TEMPL_VL is a predefined Oracle E-Business Suite (EBS) database object owned by the APPS schema. It is classified under the FND – Application Object Library product grouping because it is a translated (_VL, or "view with language") view constructed in the standard Oracle multi-language deployment pattern. In Oracle EBS Release 12.1.1 and 12.2.2, this view exposes determinant factor template definitions used by the E-Business Tax (EBTax / ETRM) engine. Determinant factor templates determine which tax rules apply to a transaction by mapping a factor set (for example, regime, tax, tax status, and related attributes) to given configurations.

The view joins the base table to its translation table so that the descriptive text (name and description) is returned in the language of the current user session. Because it is a database view rather than a physical table, it does not store data itself; it presents a consolidated, user-facing projection over tax configuration data. This makes it suitable for reporting, data extraction, integration, and lookup purposes where translated template information is required without writing the join logic manually.

Underlying Base Objects

The view is defined over two documented synonyms, each resolving to an ETRM base table:

• ZX_DET_FACTOR_TEMPL_B — the base table holding the language-independent template attributes such as identifiers, codes, ledger references, template usage code, and record type code. It also supplies standard EBS WHO columns (created_by, creation_date, last_updated_by, and so on).
• ZX_DET_FACTOR_TEMPL_TL — the translation table holding the language-dependent template name (DET_FACTOR_TEMPL_NAME) and description (DET_FACTOR_TEMPL_DESC).

The join condition is B.DET_FACTOR_TEMPL_ID = T.DET_FACTOR_TEMPL_ID AND T.LANGUAGE = USERENV('LANG'), restricting the translation row to the language of the current database session. The B.ROWID value is exposed as ROW_ID, and the object version number is carried forward for concurrency control.

Key Columns

• DET_FACTOR_TEMPL_ID — primary identifier linking the base and translation tables.
• DET_FACTOR_TEMPL_CODE — the language-independent code used for programmatic lookups and integrations.
• DET_FACTOR_TEMPL_NAME / DET_FACTOR_TEMPL_DESC — translated, user-facing name and description.
• TAX_REGIME_CODE — identifies the tax regime to which the template belongs.
• LEDGER_ID — the ledger (set of books) context for the template.
• CHART_OF_ACCOUNTS_ID — the chart of accounts associated with the configuration.
• TEMPLATE_USAGE_CODE and RECORD_TYPE_CODE — control how and where the template is applied within the tax determination process.
• OBJECT_VERSION_NUMBER — supports optimistic locking for DML operations.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, PROGRAM_ID, REQUEST_ID) — standard audit and concurrent program context.

Common Use Cases and Queries

Typical scenarios include validating E-Business Tax configuration, extracting template metadata for migration or reconciliation, and joining templates to tax rule definitions. Because the view already applies the language join, reporting tools such as Oracle Reports, BI Publisher, and ad-hoc SQL can query it directly.

• Listing templates by regime: SELECT det_factor_templ_code, det_factor_templ_name, tax_regime_code FROM zx_det_factor_templ_vl ORDER BY tax_regime_code;
• Querying a specific template: SELECT * FROM zx_det_factor_templ_vl WHERE det_factor_templ_code = :p_code;
• Reporting by ledger: SELECT det_factor_templ_id, det_factor_templ_name, ledger_id FROM zx_det_factor_templ_vl WHERE ledger_id = :p_ledger_id;

Since the view is read-only in practical terms (it is defined over the base and translation tables), inserts and updates should be directed to ZX_DET_FACTOR_TEMPL_B and ZX_DET_FACTOR_TEMPL_TL respectively, with the display view reserved for query access.