Search Results intended_use




Overview
Explore in AI Chat

Overview

The APPS.ZX_FC_INTENDED_USE_V view is a reporting and integration object within the Oracle E-Business Suite (EBS) tax and configuration framework, spanning releases 12.1.1 and 12.2.2. It exposes the set of valid "Intended Use" classifications that the EBS tax engine (E-Business Tax / ZX schema) recognizes when determining tax applicability and tax registration rules for goods and services. Intended Use is a first-party classification type consumed by tax configuration setups, notably in the context of country-specific tax rules and product fiscal classifications.

The view consolidates two distinct sources of Intended Use codes into a single, uniform result set: inventory category-based definitions and standalone classification codes. This UNION structure allows downstream consumers — tax setup forms, validation logic, and custom reporting — to query one object rather than resolving both the EBS Inventory category hierarchy and the tax classification code tables separately. Because the object is owned by APPS and defined as a view, it is read-only and carries no independent storage.

The view is defined with a single, consistent four-column projection (CODE, NAME, COUNTRY_CODE, EFFECTIVE_FROM, EFFECTIVE_TO), which makes it suitable for LOV (List of Values) population and lookup validation.

Underlying Base Objects

The view is defined over six documented base objects, joined across the Inventory category and E-Business Tax schemas:

The first branch returns Intended Use values derived from Inventory categories; the second returns Intended Use values defined directly as tax fiscal classification codes. The UNION combines them into one master lookup.

Key Columns

  • CODE — The Intended Use identifier. In the category branch this is the concatenated category segments with the flexfield delimiter removed (via REPLACE); in the code branch it is CLASSIFICATION_CODE.
  • NAME — The descriptive name. Category-branch values come from MTL_CATEGORIES_TL.DESCRIPTION (language-sensitive); code-branch values come from CLASSIFICATION_NAME.
  • COUNTRY_CODE — The country to which the Intended Use applies. It is always NULL for category-based entries and populated only from ZX_FC_CODES_VL for standalone codes.
  • EFFECTIVE_FROM — Start date of validity; sourced from ZX_FC_TYPES_B.EFFECTIVE_FROM or ZX_FC_CODES_VL.EFFECTIVE_FROM.
  • EFFECTIVE_TO — End date of validity; category-branch value is MTL_CATEGORIES_B_KFV.END_DATE_ACTIVE, code-branch value is ZX_FC_CODES_VL.EFFECTIVE_TO. A NULL generally indicates no expiration.

Common Use Cases and Queries

Typical usage includes populating Intended Use selection lists, validating user-entered values against enabled classifications, and building tax setup reconciliations.

  • Retrieve all enabled Intended Use codes with names: 
    SELECT code, name, effective_from, effective_to
FROM   apps.zx_fc_intended_use_v
ORDER BY code;
  • Restrict to currently effective entries: 
    SELECT code, name, country_code
FROM   apps.zx_fc_intended_use_v
WHERE  TRUNC(SYSDATE) BETWEEN NVL(effective_from, TRUNC(SYSDATE))
                          AND NVL(effective_to, TRUNC(SYSDATE));
  • Isolate country-specific (non-category) definitions: 
    SELECT code, name, country_code
FROM   apps.zx_fc_intended_use_v
WHERE  country_code IS NOT NULL;

Because the view strips category delimiters and applies language filtering, it returns values in the format expected by tax classification fields, making it the preferred lookup object for Intended Use validation in both 12.1.1 and 12.2.2 environments.