Search Results flex_field_code

Overview

BIS_FLEX_FIELDS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the BIS (Applications BIS) product family. It presents a consolidated, user-facing inventory of the flexfield definitions registered within an EBS instance, spanning both key flexfields and descriptive flexfields. The view's purpose is to expose a single unified list of flexfield identifiers—colloquially the "flex field code"—together with the owning application and descriptive metadata, so that downstream reports, integrations, and diagnostic queries can enumerate the flexfields available without having to union the underlying key and descriptive flexfield repositories themselves.

Because the view already performs the union and applies a filter to exclude internal system flexfields, it functions as a stable abstraction layer over the FND flexfield dictionary tables. This makes it particularly useful for metadata-driven tooling, such as utilities that need to discover which flexfields exist before invoking the Flexfield APIs, or cross-reference reports that map flexfield usage to specific applications. The view is validated (status VALID) and documented at the 12.2.2 release, and remains applicable to the 12.1.1 code line, where the underlying dictionary objects retain the same structure.

Underlying Base Objects

The view definition is a two-branch UNION, each branch drawing from the flexfield dictionary and joined to FND_APPLICATION_VL to resolve the owning application name. The documented referenced base objects are FND_APPLICATION_VL (view), FND_DESCRIPTIVE_FLEXS_VL (view), and FND_ID_FLEXS (synonym).

• Key flexfields: sourced from FND_ID_FLEXS, with ID_FLEX_CODE mapped to FLEX_FIELD_CODE and ID_FLEX_NAME mapped to FLEX_FIELD_NAME. A literal discriminator 'K' identifies these rows as key flexfields.
• Descriptive flexfields: sourced from FND_DESCRIPTIVE_FLEXS_VL, with DESCRIPTIVE_FLEXFIELD_NAME mapped to FLEX_FIELD_CODE and TITLE mapped to FLEX_FIELD_NAME. Rows whose name begins with $SRS$ are excluded, filtering out internal concurrent-program parameter flexfields.
• Application resolution: both branches join FND_APPLICATION_VL on APPLICATION_ID to supply the application name.

Key Columns

• ROW_ID — the physical row identifier from the contributing base object; useful for uniqueness but not a stable primary key across the union.
• APPLICATION_ID / APPLICATION_NAME — the owning application, enabling filtering by module.
• FLEX_FIELD_CODE — the flexfield identifier matched by the search term "flex_field_code"; carries the key flexfield code or the descriptive flexfield name.
• FLEX_FIELD_NAME — the human-readable title of the flexfield.
• FLEX_FIELD_TYPE — discriminator distinguishing key ('K') from descriptive ('D') flexfields.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include enumerating all flexfields for a given application, resolving a flexfield code to its title, and separating key from descriptive definitions.

• List all flexfields for a named application: SELECT flex_field_code, flex_field_name, flex_field_type FROM bis_flex_fields_v WHERE application_name = 'General Ledger';
• Find a specific flexfield: SELECT * FROM bis_flex_fields_v WHERE flex_field_code = 'GL#';
• List only descriptive flexfields: SELECT flex_field_code, flex_field_name FROM bis_flex_fields_v WHERE flex_field_type = 'D';
• Count definitions by application: SELECT application_name, flex_field_type, COUNT(*) FROM bis_flex_fields_v GROUP BY application_name, flex_field_type;