GrowCloudSkills

Introduction

Once you move beyond simple examples in Fast Formula, you quickly realize one thing:

Formulas are useless without data.

This is where Database Items (DBIs) come in.

DBIs allow Fast Formulas to read real employee data from Oracle Fusion HCM. This includes attributes such as salary, grade, assignment details, and dates. Many other attributes are accessible without writing SQL or touching database tables.

In this guide, you’ll learn:

• What DBIs are
• How they work
• Different types of DBIs
• How contexts affect DBIs
• Best practices and common mistakes

All explained in simple language with practical examples.

What Are Database Items (DBIs)?

A Database Item (DBI) is a predefined data reference that allows a Fast Formula to access information stored in Oracle Fusion HCM tables.

In simple words:

DBIs are read-only data points used inside Fast Formulas.

Examples of what DBIs can retrieve:

• Employee salary
• Assignment number
• Grade
• Job
• Hire date
• Length of service

You do not create DBIs manually in most cases—Oracle delivers them.

Why DBIs Are Critical in Fast Formula

DBIs are the bridge between:

• HCM data
• Business rules

Without DBIs:

• Formulas would not know employee data
• Logic would be hardcoded
• Configuration would be inflexible

DBIs ensure:

• Secure access to data
• Upgrade-safe logic
• No dependency on SQL or custom code

How DBIs Work (Conceptual Understanding)

When a Fast Formula runs:

1. Oracle sets the execution context
2. The formula requests a DBI value
3. Oracle fetches the correct data based on context
4. The DBI value is returned to the formula

👉 This is why context and DBIs are tightly connected.

Types of Database Items in Oracle Fusion HCM

DBIs can be broadly classified into three main categories.

1. Standard DBIs

These are predefined DBIs delivered by Oracle.

Examples:

• Salary Amount
• Assignment Start Date
• Grade Name
• Job Code

They are commonly used in:

• Payroll
• Absence
• Benefits
• Compensation formulas

Standard DBIs are:

• Stable
• Well-tested
• Safe to use

2. Context-Sensitive DBIs

These DBIs depend on which context is active.

For example:

• Assignment DBIs require assignment context
• Payroll DBIs require payroll relationship context

If the correct context is missing:

• DBI returns null
• Formula may fail
• Results may be incorrect

👉 Context handling will be explained in detail in the next post.

3. Flexfield DBIs

Flexfield DBIs allow formulas to read:

• Descriptive Flexfields (DFF)
• Extensible Flexfields (EFF)

Use cases:

• Custom attributes
• Client-specific logic
• Extended employee information

Flexfield DBIs provide flexibility but should be used carefully for performance reasons.

How to Use DBIs in Fast Formula

DBIs are used just like variables.

Example:

DEFAULT FOR BASIC_SALARY IS 0

Here, BASIC_SALARY is a DBI.

You do not declare DBIs using INPUTS ARE.
They are system-provided.

DEFAULT Values for DBIs (Very Important)

DBIs may return null if:

• Data does not exist
• Context is incorrect
• Record is missing

Always define DEFAULT values.

Example:

DEFAULT FOR ANNUAL_SALARY IS 0

👉 Missing DEFAULTs for DBIs is one of the top causes of runtime errors.

DBIs and Context Relationship

DBIs do not work in isolation.

Why Context Matters

• DBIs fetch data for the current record
• Context defines which employee, assignment, or payroll relationship is active

Example contexts:

• Assignment
• Payroll relationship
• Absence entry

Without correct context:

• DBI may return wrong values
• Formula logic may break

👉 Contexts deserve a full dedicated blog (next in this series).

Practical Example: Using DBIs in a Formula

Scenario

Provide an allowance only to employees whose grade is “M1”.

Conceptual Logic:

• Read grade DBI
• Compare value
• Return allowance

Example:

DEFAULT FOR GRADE_NAME IS 'NA'
IF GRADE_NAME = 'M1' THEN
  ALLOWANCE = 3000
ELSE
  ALLOWANCE = 0
RETURN ALLOWANCE

This example shows:

• Reading DBI data
• Default handling
• Conditional logic

How to Find Available DBIs

Oracle provides tools to identify DBIs:

• Fast Formula UI
• Database Item search
• Context-based item lists

Best practice:

• Search DBIs by business requirement
• Avoid guessing DBI names
• Validate data source

DBI Performance Considerations

Poor DBI usage can slow down processing.

Best Practices:

✔ Use only required DBIs
✔ Avoid unnecessary flexfield DBIs
✔ Avoid repeated DBI references
✔ Ensure correct context

Performance issues often appear during:

• Payroll runs
• Absence accruals
• Mass processing

Common DBI-Related Mistakes

Avoid these errors:

❌ Forgetting DEFAULT values
❌ Using DBIs without context
❌ Confusing DBIs with inputs
❌ Using wrong DBI for requirement
❌ Overusing flexfield DBIs

Most DBI issues are design problems, not syntax issues.

DBIs vs Input Variables (Quick Comparison)

👉 Choosing the right one improves formula quality.

How This Fits in the Fast Formula Learning Path

So far, you’ve learned:

• Syntax & structure
• Variables & inputs
• Database Items (DBIs)

Next, you’ll learn:

• Contexts
• How Oracle determines which data DBIs return

👉 Refer back to the Pillar Blog for the full roadmap.

Conclusion

DBIs are the heart of real-world Fast Formulas.

If you understand:

• What data you need
• Which DBI provides it
• Which context controls it

Then you are already thinking like a production-level Oracle Fusion HCM consultant.

Follow GrowCloudSkills for the next post in this Fast Formula series.