How You Load Data for Multiple Contexts' Descriptive Flexfields in HDL

In the world of Oracle Fusion HCM integrations, we typically deal with a single context for a Descriptive Flexfield (DFF). It’s straightforward: one record, one context, one set of attributes.

However, "standard" doesn't always mean "simple." There are rare but critical scenarios where you must populate multiple contexts for the same DFF simultaneously. A classic example is when you have mandatory attributes in the Global Data Elements (the default context) while needing to populate a specific Custom Context (like XXABFUNDCODE) at the same time.

Here is how you handle this complexity in your data headers.

The Challenge: The "Double Context" Scenario

When you have a requirement to pass data for both a custom context and the global context, a standard single-column header won't suffice. If you try to pass them separately or in a sequence that the system doesn't recognize, the integration will likely fail or ignore one of the segments.

The Solution: Strategic Header Formatting

To successfully map these, you need to explicitly define the contexts within your header row. Using the example of an Assignment DFF (PER_ASG_DF), your file structure should look like this:

1. The Header Mapping

You must reference the DFF name and specify which attribute belongs to which context using the FLEX prefix notation.

The Syntax:

FLEX:DFF_CODE|AttributeName(FLEX:DFF_CODE=CONTEXT_CODE)

Your Header Example:

FLEX:PER_ASG_DF|abcId(FLEX:PER_ASG_DF=XXABFUNDCODE)|defId(FLEX:PER_ASG_DF=Global Data Elements)

2. The Data Row

Once the headers are mapped to their respective contexts, the data row follows the order defined above.

Your Data Example:

XXABFUNDCODE|ABCFUNDCODE|ValueForGlobalDataElements

---

Breakdown of the Logic

Component	Purpose
FLEX:PER_ASG_DF	This is the primary discriminator. It tells the loader which DFF is being targeted.
abcId(...=XXABFUNDCODE)	This explicitly routes the value ABCFUNDCODE into the custom segment of the XXABFUNDCODE context.
defId(...=Global Data Elements)	This ensures the mandatory global attribute receives its value, preventing validation errors.

This is how the syntax in the METADATA looks like,
FLEX:PER_ASG_DF|abcId(FLEX:PER_ASG_DF=XXABFUNDCODE)|defId(FLEX:PER_ASG_DF=Global Data Elements)
XXABFUNDCODE|ABCFUNDCODE|defValueGlobalData