Search Results intended_use

Overview

ZX_FC_INTENDED_USE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the FND – Application Object Library product grouping. It exposes the set of Intended Use classifications maintained within the Oracle E-Business Tax (E-Business Tax / ZX) regime, presenting both flexfield-derived category values and directly defined tax classification codes as a single, query-friendly result set. In ETRM terms, Intended Use is one of the tax classification types (alongside Tax Regime, Tax Status, Tax Rate, and Tax Jurisdiction) used to determine how a transaction line is taxed. The view is therefore a reference and lookup object rather than a transactional one: it does not store tax results, but supplies the valid Intended Use codes and their effective date ranges that downstream logic, reports, and integrations consult. Its UNION structure reflects the two sources from which Intended Use values can be defined — inventory category flexfield values and native tax classification codes — which makes it particularly useful when validating or reporting on the Intended Use dimension of a tax determination setup.

Underlying Base Objects

The view is defined over the following documented base objects: FND_ID_FLEX_STRUCTURES_VL (view), MTL_CATEGORIES_B_KFV (view), MTL_CATEGORIES_TL (synonym), MTL_CATEGORY_SETS_B (synonym), ZX_FC_CODES_VL (view), and ZX_FC_TYPES_B (synonym). Two logical branches are combined with UNION. The first branch joins ZX_FC_TYPES_B (restricted to CLASSIFICATION_TYPE_CODE = 'INTENDED_USE') to MTL_CATEGORY_SETS_B via OWNER_ID_NUM = CATEGORY_SET_ID, then to FND_ID_FLEX_STRUCTURES_VL on STRUCTURE_ID = ID_FLEX_NUM with APPLICATION_ID = 401 and ID_FLEX_CODE = 'MCAT'. It further joins MTL_CATEGORIES_B_KFV and MTL_CATEGORIES_TL to retrieve the concatenated segment value, description, and end date. The second branch reads ZX_FC_CODES_VL directly for rows whose CLASSIFICATION_TYPE_CODE = 'INTENDED_USE', returning classification code, name, country code, and effective dates.

Key Columns

• CODE — the Intended Use identifier. In the flexfield branch it is the concatenated category segment value with the segment delimiter removed via REPLACE; in the codes branch it is ZX_FC_CODES_VL.CLASSIFICATION_CODE.
• NAME — the descriptive label, taken from MTL_CATEGORIES_TL.DESCRIPTION or ZX_FC_CODES_VL.CLASSIFICATION_NAME.
• COUNTRY_CODE — populated only for directly defined classification codes; the flexfield branch returns NULL, indicating a non-country-specific entry.
• EFFECTIVE_FROM — ZX_FC_TYPES_B.EFFECTIVE_FROM in the first branch, ZX_FC_CODES_VL.EFFECTIVE_FROM in the second.
• EFFECTIVE_TO — MTL_CATEGORIES_B_KFV.END_DATE_ACTIVE in the first branch, ZX_FC_CODES_VL.EFFECTIVE_TO in the second.

The view also relies on MTL_CATEGORIES_TL.LANGUAGE = USERENV('LANG') and MTL_CATEGORIES_B_KFV.ENABLED_FLAG = 'Y', so results are session-language-filtered and restricted to enabled categories.

Common Use Cases and Queries

Typical uses include populating Intended Use lists of values in custom tax setup pages, reconciling which Intended Use codes are active for a given period, and auditing whether a value originated from the inventory category flexfield or from a native tax classification code.

List all available Intended Use values:

SELECT code, name, country_code, effective_from, effective_to FROM apps.zx_fc_intended_use_v ORDER BY code;

Retrieve only currently effective values:

SELECT code, name FROM apps.zx_fc_intended_use_v WHERE SYSDATE BETWEEN NVL(effective_from, SYSDATE) AND NVL(effective_to, SYSDATE);

Distinguish country-specific codes from flexfield-derived entries:

SELECT code, name, country_code, DECODE(country_code, NULL, 'FLEXFIELD', 'TAX_CODE') source_type FROM apps.zx_fc_intended_use_v;