Results for “data_type_m”

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

Overview

FFBV_DATABASE_ITEM_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered under the PAY (Payroll) product. It exposes metadata about database items defined within Oracle FastFormula — the abstracted data elements that formulas reference at runtime to obtain values from payroll, HR, and related application tables. In EBS 12.1.1 and 12.2.2, the view is documented as VALID and serves as a reporting and integration surface over the FF_DATABASE_ITEMS base table, presenting the physical column definitions, data types, and nullability characteristics of each database item.

Because FastFormula database items are internally defined and frequently seeded by Oracle, technical consultants and integration developers use FFBV_DATABASE_ITEM_V to inspect the available item catalogue, verify whether specific items exist, and audit their attributes without querying the underlying DDL objects directly. The view adds a decoded, user-facing data type value alongside the raw type code, which simplifies ad hoc reporting.

Underlying Base Objects

The view is defined over two referenced objects documented in the ETRM metadata:

• FF_DATABASE_ITEMS (SYNONYM) — the primary base table holding database item definitions. The view selects FDI.USER_NAME, FDI.DEFINITION_TEXT, FDI.NULL_ALLOWED_FLAG, FDI.DESCRIPTION, FDI.DATA_TYPE, FDI.USER_ENTITY_ID, and the standard audit columns from this table.
• HR_BIS (PACKAGE) — invoked through HR_BIS.BIS_DECODE_LOOKUP('DATA_TYPE', FDI.DATA_TYPE) to translate the stored DATA_TYPE code into the human-readable DATA_TYPE_M value.

The view is created WITH READ ONLY, so it cannot be used for DML. It is a pure projection and decode layer; no joins to additional tables are present in the documented view text.

Key Columns

• USER_NAME — the database item's user-facing identifier, as referenced in FastFormula code.
• DATA_TYPE_M — the decoded, descriptive data type derived via BIS_DECODE_LOOKUP, suitable for reporting.
• DATA_TYPE — the raw internal data type code stored on FF_DATABASE_ITEMS.
• NULL_ALLOWED_FLAG — indicates whether the database item may return a null value. This is the column users commonly search for when validating formula logic or troubleshooting null-related errors.
• DEFINITION_TEXT — the definition or derivation text associated with the item.
• DESCRIPTION — descriptive text explaining the item's purpose.
• USER_ENTITY_ID — the identifier of the owning user entity, linking the item to its defining context.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE support change tracking.

Common Use Cases and Queries

Typical scenarios include auditing database item nullability, inventorying available items by type, and validating seeded definitions before building or modifying FastFormula logic.

• Locate items that permit nulls:

SELECT user_name, data_type_m, null_allowed_flag, description
FROM apps.ffbv_database_item_v
WHERE null_allowed_flag = 'Y';

• Search for a specific item by name:

SELECT user_name, data_type_m, definition_text, null_allowed_flag
FROM apps.ffbv_database_item_v
WHERE user_name LIKE '&item_name%';

• Group items by decoded data type for an inventory report:

SELECT data_type_m, COUNT(*)
FROM apps.ffbv_database_item_v
GROUP BY data_type_m;

Because the view is read-only and rooted in a synonym over an Oracle-owned table, query access is normally granted to the APPS schema and custom reporting responsibilities. All queries should be executed with an appropriate APPS-level or custom read-only user.