Results for “effective_to”

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

Overview

The ZX_FC_USER_DEFINED_V view is a reporting and integration object in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema within the FND — Application Object Library product family. It exposes a filtered subset of fiscal classification codes maintained in Oracle's E-Business Tax (ZX) module, specifically those records whose classification type is designated as "USER_DEFINED." The view presents a simplified vertical slice of the underlying classification code data, allowing developers and consultants to retrieve user-defined fiscal classifications without navigating the broader classification hierarchy stored in the base table.

In practice, the view acts as a convenience layer for reports, concurrent programs, and inbound/outbound integrations that must reference only customer- or implementation-defined classifications — as opposed to seeded, system-delivered classifications. Because it restricts results to a single classification type, it reduces the query complexity required to isolate user-created codes and is commonly used in tax determination, reporting, and data migration routines within EBS.

Underlying Base Objects

The view is defined directly over a single documented base object: ZX_FC_CODES_VL, which is itself a view (the "_VL" suffix indicates a translated view that joins the base table with its translation table to expose language-dependent columns such as name and description). The ZX_FC_CODES_VL object surfaces the fiscal classification codes maintained in the ZX_FC_CODES entity.

The defining query is:

• SELECT FC.CLASSIFICATION_CODE, FC.CLASSIFICATION_NAME, FC.COUNTRY_CODE, FC.EFFECTIVE_FROM, FC.EFFECTIVE_TO FROM ZX_FC_CODES_VL FC WHERE FC.CLASSIFICATION_TYPE_CODE = 'USER_DEFINED'

Because ZX_FC_USER_DEFINED_V inherits its structure from ZX_FC_CODES_VL, any change to the underlying classification code definition — such as the addition of effective dating rules or translation support — propagates automatically to consumers of this view. The view is documented as VALID under the APPS schema in the ETRM metadata for 12.2.2.

Key Columns

The view exposes five columns, each projecting a specific attribute of the underlying fiscal classification code:

• CLASSIFICATION_CODE — The unique identifier code assigned to the user-defined fiscal classification. This is the value typically stored on transactional records and referenced during tax calculation.
• CLASSIFICATION_NAME — The translated, user-facing name of the classification, drawn from the "_VL" translation layer so that multilingual implementations receive the appropriate language version.
• COUNTRY_CODE — The country to which the classification applies, enabling country-specific tax and fiscal reporting scenarios.
• EFFECTIVE_FROM — The date from which the classification becomes valid, supporting date-effective queries and point-in-time reporting.
• EFFECTIVE_TO — The date on which the classification expires, allowing implementations to retire codes without deleting historical records.

Common Use Cases and Queries

Typical scenarios include populating a value set or LOV with only user-defined classifications, extracting active classifications for a given country, and validating that a proposed classification exists and is effective for a transaction date. A basic retrieval of all user-defined classifications is:

• SELECT classification_code, classification_name, country_code, effective_from, effective_to FROM apps.zx_fc_user_defined_v;

To restrict results to currently effective classifications for a specific country:

• SELECT classification_code, classification_name FROM apps.zx_fc_user_defined_v WHERE country_code = 'US' AND TRUNC(SYSDATE) BETWEEN effective_from AND NVL(effective_to, TRUNC(SYSDATE));

For point-in-time reporting against a historical transaction date, the effective dating columns allow a query to reproduce the set of valid user-defined classifications as of that date. These patterns are common in tax reporting extracts, migration validation scripts, and interface programs that must distinguish user-created classifications from Oracle-seeded ones.