We are working on FDM version 11.1.1.2 and loading the data in Essbase.

I am able to successfully automate the data loading process. As mentioned in admin guide, by putting the source data file inside the Input/Batches/OpenBatch folder and running the BatchLoad script, data is successfully loaded into Essbase.

Now, we have below further requirement-

Source data file may have unmapped accounts during the automation process. We need to list of these unmapped accounts.

I put some unmapped accounts in source file and place this file under the Input/Batches/OpenBatch folder. After running the batch script,
As per process, source data file has moved from Openbatch. But no data has been loaded into Essbase.

I checked in log file under Outbox/Logs folder. But, there is no error and it is showing all records have been processed successfully.

When there are any unmapped members, the validate step fails and processing for that POV stops.

There are 2 ways to address this. You can create a script that extracts the unmapped records (they are recorded during the batch cycle) or you can use the batch autocorrect option. This requires a new location to be set up with a default map for each mappable dimension. Any time FDM detects an unmapped member during a batch process, it will use the default mapping. There are more details in the admin guide.