How to Bulk Upload Oracle Fusion Lookup Codes with Context-Based DFF Values

If you’ve tried to bulk-load Lookup Codes in Oracle Fusion and also populate context-based Descriptive Flexfield (DFF) values, you may have seen errors like:

incorrect mapping of value row with header columns row
JBO-25058: Definition AttributeXX … is not found … LookupDFFVO

This post explains why those errors occur and provides a repeatable, practical method to load lookup codes with a DFF context and segment values correctly.

The scenario

You’ve created a Lookup Type and you need to upload Lookup Codes in bulk. Each lookup code must also be linked to a DFF context and populated with context-specific segments such as Entity, BU, Cost Center, or Additional Details.

Symptoms: What the errors are really telling you

1) “Incorrect mapping of value row with header columns row”

This typically means the number of fields in your data row does not match the header. Common causes include:

Wrong delimiter usage (or mixed delimiters)
Extra separators creating additional columns
Line breaks embedded inside a field
Trying to put multiple values into a single attribute field (causing variable-length rows)

2) JBO-25058 complaining about AttributeXX

If your header contains Attribute1/Attribute2/Attribute4 (or similar), the loader may fail because those are not valid DFF segment column names for Lookups DFF in your configuration. In other words: the file header doesn’t match the DFF metadata expected by the loader.

Root cause (the part most people miss)

To load context-based Lookups DFF values, your lookup code import file must:

Include a column named exactly CONTEXT_ATTRIBUTE
Use DFF segment internal codes (segment ‘code’/internal label) as column headers — not generic Attribute1/Attribute2/Attribute4

Step-by-step solution

Step 1 — Use the supported Lookup Import process and file rules

Use the standard import mechanism from Manage Standard Lookups / Manage Common Lookups. Prepare separate files for Lookup Types and Lookup Codes, follow the prescribed header structure, and keep encoding consistent (UTF‑8 is recommended).

Step 2 — Build a Lookup Codes header that supports context + DFF segments

Extend the standard Lookup Codes header by adding CONTEXT_ATTRIBUTE and then the DFF segment internal codes for the context you’re targeting. Conceptually, the header looks like this:

Step 3 — Ensure every data row matches the header column count

Each row must contain exactly one value per column. Avoid adding extra delimiters or packing multiple values into a single field. Example:

Take a look at below sample file:

LookupType|LookupCode|DisplaySequence|EnabledFlag|StartDateActive|EndDateActive|Meaning|Description|Tag|CONTEXT_ATTRIBUTE|testSegment1|testSegment2|testSegment
LOOKUP TEST|TEST LOOKUP CODE_1|1|Y|25/12/2014|25/12/2050|TEST LOOKUP MEAN_1|TEST LOOKUP DESC_1|Tag_1|TEST CONTEXT1|TEST SEG VAL 1|TEST SEG VAL 2|TEST SEG VAL 3
LOOKUP TEST|TEST LOOKUP CODE_2|2|Y|25/12/2014|25/12/2050|TEST LOOKUP MEAN_2|TEST LOOKUP DESC_2|Tag_2|TEST CONTEXT1|TEST SEG VAL 1|TEST SEG VAL 2|TEST SEG VAL 3
LOOKUP TEST|TEST LOOKUP CODE_3|3|Y|25/12/2012|25/12/2050|TEST LOOKUP MEAN_3|TEST LOOKUP DESC_3|Tag_3|TEST CONTEXT1|TEST SEG VAL 1|TEST SEG VAL 2|TEST SEG VAL 3
LOOKUP TEST|TEST LOOKUP CODE_4|4|Y|25/12/2012|25/12/2050|TEST LOOKUP MEAN_4|TEST LOOKUP DESC_4|Tag_4|TEST CONTEXT1|TEST SEG VAL 1|TEST SEG VAL 2|TEST SEG VAL 3

This is working fine for me. Below is how the lookup looks for me. Note that one value was loaded manually and the others using the above file.

Handling “multiple values” for a segment

If a single lookup code truly needs multiple values for one attribute (for example, multiple Natural Accounts), you generally have two options:

Create multiple rows (one per combination) so each row still aligns with the header.
Model multiple segments (Account1, Account2, Account3, …) if the business requirement is to store multiple values on one lookup code.

How to find the correct segment internal codes

The UI labels (e.g., ‘Entity’, ‘BU’) are often not the same as the segment internal codes needed in the file header. The most reliable way to identify the correct codes is via the Generic Lookups REST API and its Lookups DFF child resources.

Tip: start with the describe endpoint to see the fields exposed by your REST version: /fscmRestApi/resources/11.13.18.05/genericLookups/describe

https://XXXXXXX.fa.ocs.oraclecloud.com/fscmRestApi/resources/11.13.18.05/genericLookups?q=LookupType=**** LOOKUP TEST

And then I called the below one to get the DFF details. https://XXXXXXX.fa.ocs.oraclecloud.com/fscmRestApi/resources/11.13.18.05/genericLookups/<Lookup ID>/child/lookupCodes/TEST LOOKUP CODE1/child/lookupsDFF/

Validation tips

When the file is correct, your upload logs should indicate that the loader detected CONTEXT_ATTRIBUTE and also recognized your DFF segment columns from the header. If the log still references Attribute4 (or your DFF segments aren’t detected), revisit the header column names.

Alternative approach: Oracle Visual Builder Add-in for Excel (VBAFE)

If file-based loading remains cumbersome, consider Oracle Visual Builder Add-in for Excel. It provides a spreadsheet UI over REST services and is often a practical option for bulk maintenance of data that includes DFF.

Reusable checklist

Use the supported Lookup Import process (Manage Standard/Common Lookups → Import).
Add CONTEXT_ATTRIBUTE and set its value to your context code.
Use DFF segment internal codes as header columns (not Attribute1/Attribute2/Attribute4).
Ensure each row has the same number of fields as the header.
Use REST APIs (genericLookups + lookupsDFF) to confirm the exact segment codes.
Verify logs show DFF segments detected and processed without errors.

References

Oracle Docs — File Format for Importing Lookups: https://docs.oracle.com/en/cloud/saas/human-resources/25b/faucf/file-format-for-importing-lookups.html
Oracle Docs — Import Lookups overview: https://docs.oracle.com/en/cloud/saas/sales/oacdm/import-lookups.html
Oracle Docs — Generic Lookups REST Endpoints: https://docs.oracle.com/en/cloud/saas/applications-common/25a/farca/api-generic-lookups.html
Oracle Docs — Visual Builder Add-in for Excel download: https://www.oracle.com/downloads/cloud/visual-builder-addin-downloads.html

Leave a Reply Cancel reply