Hi Bogdan,
I tried placing multiple variants of the file in the interface folder with help from our Basis team. In one of the test files having 8 records, 7 were picked up by the scheduled task. The one failed record was for a user (existing user in Sourcing) with value "CREDIT & COLLECTION ANALYST" for Job profile (one of the extension fields we are trying to update, field data type String). This led me to the assumption that maybe the scheduled task doesn't like special characters. So I removed EMAIL column from the input file and tried uploading a file with just NAME and extension fields. This time many more records were picked up - even the CREDIT & COLLECTION ANALYST one which failed earlier!!!
The Java debug log is enabled and Trace.txt still gives the same misleading message for ALL failed records:
A sample from Trace.txt
| Sat May 21 09:08:44 PDT 2016 | ....Import failed for object number 1,682. The object referenced in column BUYER_COMP could not be found. |
I guess SAP needs to work on fine-tuning error message logging.
I am still going through all failed records in the latest upload and trying to remove the ones which failed because of missing user account in sourcing (I am running the tests in our dev env where all production user accounts are not present). Meanwhile any idea on why the scheduled task doesnt like EMAIL column in the user account upload file? Is there any special character/anything else that I should look out for?
Thanks,
Gayathri