- 12 Nov 2026
Oracle HCM Extensible Flexfields: Where the Data Is Stored
An extensible flexfield (EFF) in Oracle Fusion HCM lets administrators add custom attributes to a business object, such as a person, job, or assignment, without writing code. The attributes are organized into contexts, and Oracle stores the values in a separate extension table rather than the standard table. A single-row context holds one set of values, and a multi-row context holds several. You configure an EFF with the Manage Extensible Flexfields task in Setup and Maintenance, deploy it, and report on it once its segments are BI enabled.
Every HR team eventually needs to capture something Oracle did not anticipate: a professional certification, a security clearance, a visa record, or a regional compliance field. Extensible flexfields are the supported way to do it, and they are also one of the most misunderstood features, partly because people are unsure where the data goes.
This page explains what EFFs are, how their building blocks fit together, where the data is stored, how EFFs differ from descriptive flexfields, and what to check when you configure, load, and report on them. If you want the wider picture of Oracle HCM data, see our Oracle HCM tables and views article.
Quick Summary
Key Takeaways
- EFFs are Oracle’s supported way to extend HCM objects. They are configured, not coded.
- Values live in extension tables. They are separate from the standard table, which is what allows multiple rows per record.
- Contexts can be single-row or multi-row. Multi-row contexts need a unique key made from one or more segments.
- Deployment is a required step. Oracle says you can only deploy EFFs with the Manage Extensible Flexfields task.
- Reporting needs preparation. Segments must be BI-enabled before they appear in reporting subject areas.
What Extensible Flexfields Do for HCM
Standard Oracle HCM objects come with a fixed set of fields. An extensible flexfield adds a configurable expansion area to an object such as a person, job, location, or organization, so you can capture information that your organization needs and Oracle does not provide.
Take certifications. One employee may hold several, each with a name, issuing authority, issue date, and expiry date. A multi-row context lets you capture all of them for the same person, with each certification as its own row. That one-to-many shape is what a single descriptive field cannot do.
What this means for you: If the data you need repeats for each record, such as several certifications or visas per person, you are looking at an EFF, not a simple custom field.
The Building Blocks in Plain English
- Context. A group of related segments, such as “Certification” or “Security Clearance.” A context can be single-row, with one set of values for the record, or multi-row, with several. Oracle notes that a single-row context behaves like a descriptive flexfield context.
- Segment. One field in a context, such as a date, number, text value, or choice from a list.
- Category. A grouping of contexts. Most EFFs have only one category that holds all their contexts, but some have several, and you then choose which contexts apply to each category.
- Logical page. A way to group contexts for display, so related fields appear together for the user.
Contexts are reusable within a given EFF, which saves rework when the same group of fields is needed in more than one place.
Where the EFF Data Is Stored
This is the question the data team asks first. Oracle’s developer documentation describes the design clearly:
- EFF values are stored in an extension table, separate from the standard application table. Each flexfield usage has a base extension table, named with a _B suffix.
- Translatable contexts store their values in a translation extension table (_TL), with one row per installed language. Non-translatable contexts store values in the base extension table.
- Each segment maps to a column in the extension table, for example, a character or number attribute column, and a context column records which context a row belongs to.
- One record can have many extension rows. That is how multi-row contexts hold several certifications for one person.
The exact table names depend on the flexfield, so do not guess them. In Oracle’s HCM documentation, the codes you will encounter include PER_PERSON_EIT_EFF for person information and PER_JOBS_EIT_EFF for jobs. If you write queries, look up the flexfield’s details in Manage Extensible Flexfields, and see our Oracle HCM table suffixes article for how _B, _TL, _F, and view suffixes work.
What this means for you: Because EFF data sits in extension tables, a report that only joins the standard HCM tables will miss it. Plan the join, or use a reporting subject area that already exposes the flexfield.
EFF vs DFF: Which Should You Use?
| Question | Extensible Flexfield | Descriptive Flexfield |
|---|---|---|
| Where are the values stored? | In separate extension tables | In attribute columns on the standard table |
| How many contexts can a record use? | Several, grouped by category | One context at a time |
| Can a record hold several rows? | Yes, with multi-row contexts | No |
| How are fields grouped on the page? | By logical page and context | By context only |
| What is it best for? | Repeating or structured data | A few simple extra fields |
If you only need one or two extra fields on a record, a DFF is simpler. If the data repeats or has structure, use an EFF.
How to Configure One, Step by Step
- Open Setup and Maintenance and search for the Manage Extensible Flexfields task.
- Find the flexfield for the business object you want to extend, and open it for editing.
- Create a context. Choose single-row or multi-row. For multi-row, mark the segments that together make each row unique.
- Add segments. Choose each data type or value set, and mark segments BI enabled if you plan to report on them.
- Associate the context with the category, and place it on a logical page.
- Deploy the flexfield. Oracle says deployment must be done through this task, and it can run as a background process so you can keep working. Flexfields with more than 30 categories must be deployed that way.
- Check it on the page and in a test report. On Redwood pages, Oracle’s guidance says you may need to refresh and deploy offline before all context codes appear, and page layout changes use Visual Builder Studio or HCM Experience Design Studio, depending on your update level.
Do the work in a test environment first, and retest after each quarterly update.
Loading and Reporting on EFF Data
Loading. When you load EFF data with HCM Data Loader, Oracle documents that each MERGE line for an EFF record can have only one context. For multi-row contexts, the segments that form the unique key identify the row, so you need the source key or the complete user key to update it.
Reporting. Oracle’s flexfield guidance for reporting is to enable the BI Enabled option when you define the segments, run the process that imports Fusion data extensions for transactional business intelligence, and then add the flexfield from the subject area to your analysis. OTBI names these attributes by combining the category and context. EFF data can also flow into BI Publisher, HCM Extract, and Oracle Analytics, and our Oracle HCM analytics, pre-built HCM reports, and Oracle HCM Cloud analytics pages show what that looks like.
Our reports conversion service and our BI reports and dashboard development team also build reporting on top of custom HCM data. For an example of HCM reporting delivered end to end, see our Creighton University story.
Common Mistakes and Best Practices
- Forgetting to deploy. A configuration change does nothing visible until the flexfield is deployed.
- Skipping BI-enabled. Segments that are not BI-enabled will not show up in reporting subject areas.
- Weak keys on multi-row contexts. If the unique key does not separate rows, updates and loads become ambiguous.
- Creating contexts you do not need. Reuse contexts, and keep naming consistent.
- Ignoring security. Decide who can see and edit each context, as our Oracle HCM security roles article explains.
- Skipping documentation and retesting. Record every configuration, and retest after quarterly updates.
For the wider setup context, our Oracle Fusion HCM architecture, Oracle HCM Cloud implementation, and Oracle Fusion HCM articles are good starting points.
Considerations for Regulated and Public Sector Teams
This section is planning guidance, not a statement of DataTerrain’s authorization status or government work. EFFs often hold the most sensitive HR data, such as certifications, clearances, and immigration records. Regulated and public sector teams should limit who can view and edit each context, keep a record of who approved each configuration, and confirm retention rules before storing sensitive values. Our Advanced HCM Controls article covers governance in more depth.
Frequently Asked Questions
Scope Your HCM Flexfield and Reporting Work with DataTerrain
The costly mistake is configuring a flexfield well and then discovering that nobody can report on it. DataTerrain brings 17+ years and 400+ clients in data and reporting modernization, with Oracle HCM reporting, BI Publisher and OTBI design, and migration support built around your custom data. See more Oracle HCM customer stories on our site.
Related Reading
Oracle HCM Cloud Roadmap | AI Agents in Oracle Fusion HCM | Advantages of Using Oracle HCM | Oracle Health Analytics | Compensation in Oracle Fusion HCM | Generative AI in Oracle HCM