Results for “action_name”

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

Overview

The ZX_TAX_CONDITION_ACTIONS_V view is an Oracle E-Business Suite dictionary object owned by the APPS schema and registered under the FND – Application Object Library product. It exposes the E-Business Tax (EBTax / ETRM) condition action definitions maintained in the tax configuration repository. A "condition action" represents the outcome applied when a tax condition evaluates to true — for example, setting the tax rate, applying a tax jurisdiction, applying a tax status, or triggering a tax rule action within the tax determination process.

The view does not store data independently. It is a denormalized read-only projection of AR_TAX_CONDITION_ACTIONS_ALL, enriched with lookup meaning columns from ZX_CEC_LOOKUPS. Its principal role is to present condition action records together with their human-readable action type and action code descriptions, which are otherwise held only as short lookup codes in the base table. This makes the view suitable for reporting, data extraction, and integration interfaces that must render EBTax configuration in a business-usable form.

Underlying Base Objects

The view is defined over two documented referenced objects:

• AR_TAX_CONDITION_ACTIONS_ALL (exposed through a synonym) — the base table holding condition action records, including the owning ORG_ID, the parent TAX_CONDITION_ID, the action type and action code, the action value, display order, descriptive flexfield attributes, and the standard WHO audit columns.
• ZX_CEC_LOOKUPS (view) — the EBTax lookup view, joined twice. The first join resolves TAX_CONDITION_ACTION_TYPE against lookup type TAX_CONDITION_ACTION_TYPE; the second resolves TAX_CONDITION_ACTION_CODE against lookup type TAX_CONDITION_ACTION_CODE.

Both joins are equi-joins on LOOKUP_CODE, with the lookup type supplied as a literal filter predicate. Internally the view also selects ROWID from the base table, reflecting its read-only, non-updatable nature. Because the base table carries an ORG_ID column, the underlying object is multi-org (partitioned by operating unit) from a data model perspective.

Key Columns

• TAX_CONDITION_ACTION_ID — primary identifier of the condition action record.
• TAX_CONDITION_ID — foreign key to the parent tax condition; used to group actions under their governing condition.
• TAX_CONDITION_ACTION_TYPE / ACTION_TYPE_NAME — the action type code and its lookup meaning.
• TAX_CONDITION_ACTION_CODE / ACTION_NAME — the action code and its lookup meaning.
• TAX_CONDITION_ACTION_VALUE / ACTION_VALUE_NAME — the value applied by the action (the view aliases the same base column twice, exposing both raw and named forms).
• DISPLAY_ORDER / ACTION_DISPLAY_ORDER — sequence in which the action is evaluated or rendered.
• ORG_ID / CONTENT_OWNER_ID — the content owner (operating unit) that owns the configuration row.
• ATTRIBUTE1–ATTRIBUTE15 and GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20 — descriptive flexfield and global descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include auditing tax condition configuration, diagnosing tax determination behavior, and extracting action mappings for migration or reconciliation between environments.

• Retrieve all actions for a given tax condition:

SELECT tax_condition_action_id,
       action_type_name,
       action_name,
       action_value_name,
       action_display_order
FROM   apps.zx_tax_condition_actions_v
WHERE  tax_condition_id = :p_condition_id
ORDER  BY action_display_order;

• List distinct action types and codes with their meanings:

SELECT DISTINCT action_type_name, action_name
FROM   apps.zx_tax_condition_actions_v
ORDER  BY 1, 2;

• Filter by content owner where multi-org visibility applies:

SELECT tax_condition_action_id, action_name, content_owner_id
FROM   apps.zx_tax_condition_actions_v
WHERE  content_owner_id = :p_org_id;

Because the repository is read-only and joined to lookup views, queries should be treated as reporting-only. Transactional updates must target AR_TAX_CONDITION_ACTIONS_ALL through the supported EBTax configuration UI or APIs rather than this view.