You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Global Mapping not working for File-based Integration

edited Jun 27, 2026 1:05PM in Planning 8 comments

Issue:

We are trying to run a file-based integration through Global Mapping which is not working.

Source file has year (FY27, FY28…) and period (Jul, Aug…) columns. Global mapping has also been defined using same year (FY27, FY28…) and period (Jul, Aug…) format, as referred in the screenshon. In DLR, we selected Default period mapping i.e. Global mappings. We expected that the integration will run successfully, but it ended up with Warning i.e. no data found in the source file (no failed status though).

Troubleshooting Performed so far:

We also defined Explicit mapping under Source Mappings for File Type under a Calendar name. Attached this Calendar to the DLR. The integration ran successfully in this case.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!