Need help in updating user accounts via CSV file in Sourcing 10

[Former Member]

Hi All,

We have created some extension fields in User Account object like Supervisor (reference to another User Account object), Job Profile(String), etc. This custom data is already present in our ECC system and there is an ABAP program in place which pulls the data from custom tables of ECC and provides a csv file to sourcing. This is the format of the csv file with one line sample data:

#DataType[upp.user_account]

NAME,FIRST_NAME,LAST_NAME,EMAIL,USERCOSTCENTER,COMP_GRADE,JOB_PROFILE,USERSUPERVISOR,BUYER_COMP

<Sourcing user id>,John,Doe,john.doe@doe.com,1234,2,CONSULTANT,<Supervisors sourcing user id>,<Company code>

If I upload this file via the UI, using Setup -> System Administration -> Import Data, then all the custom details are updated correctly in the corresponding user account objects. But when the same file is placed in the shared interface folder on Sourcing server and a Data Import Monitor scheduled task tries to pick it up, then it fails to process even a single record.The failure trace has this message repeated for all objects in the csv:

....Import failed for object number 1. The object referenced in column BUYER_COMP could not be found.

So what are we missing here? Is there any other extra detail that a scheduled job expects from a csv file? If anyone has tried updating user accounts via csv upload, please help.

We have an internal directory configured for Buyer side, this directory is marked as the Default directory and Driver used is NetWeaver UME.

Thanks in advance,

Gayathri

[katie_doody2]

Just a thought but did you check the it is not excluded in your integrated document configuration in SAP Sourcing?

[Former Member]

Hi Krish and Katie,

Thank you for your answers. Krish, we have included BUYER_COMP and kept its value as company external id - but that didnt help.

Hi Katie,

Can you please elaborate - what do I need to check in Integrated Document Configuration? Currently in our env, the Excluded/Included Attribute list contains the following 6 values:

contracts.Contract

contracts.Agreement

rfx.RFXDoc

ontology.LineItemDoc

masterdata.Vendor

odp.masterdata.VendorLogSys

I am not aware of this functionality. Should I try including upp.user_account in this list?

Thanks,

Gayathri

[katie_doody2]

Hi Gayathri, we use pi for the integration but I know I have had to add it to the integrated document. I think it is worth a shot. It should show your extensions as well.

[Former Member]

Hi Katie,

We tried that - added upp.user_account in Integrated Document Configuration and checked all the extension fields for inclusion. But still facing the same error -"The object referenced in column BUYER_COMP could not be found." The error message is pretty misleading since we have added BUYER_COMP column header and correct value (Company external id) and the same file works fine via UI upload.

Thanks,

Gayathri

[former_member190023]

Hi Gayathri,

It could be related to something else... But the only solution is to:

- set logs to Debug

- replicate again

- fetch logs and check the stack trace

If you get the trace then you can paste it here and we can take a look

Regards,

Bogdan

[Former Member]

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

[Former Member]

Hi Gayathri,

"BUYER_COMP" is a required field, include it to the header and provide company external id as value.

Hope this will help you.

Thanks

Krish