Showing results for 
Search instead for 
Did you mean: 

HRMD Idoc. "No structural authorisation for obj."

Active Contributor
0 Kudos


When processing an inbound IDOC (of type HRMD) we get the message "No structural authorisation for obj.". This is for object type CP i.e. central Person.

I then reprocess the IDOC, without changing any system settings or authorisations, and the IDOC processes perfectly!

I have a document on Structural Authorisations, therefore I am basically familiar with how this is set up and on our system everything looks fine for the IDOC userid.

I just don't understand why we get this message, and then reprocess (1 hour later) and it works fine? Nothing has changed on the system i.e. same authorisations exist, it is processed in the same way i.e. in background, with the same userid.

Has anyone experienced this, or can shed any light on this?

We get this error adhoc, and not often, usually once a month or so.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos


Strucural authorization is sometimes behaving strange.

It seems that the message is coming for the user processing the IDOC.

You have to check if the user as a correct structural profile. In table T77UA or transaction HRAUTH. He has to be listed there with "ALL" as structural profile or not be listed at all (then uses the rights of user SAP*). This way the user would allowed to process all objects.

You have to check also the regular authorizations but seems fine following your message.

Why the Idoc processing is working the second time and not the first... If your user has a structural profile and allowed objects are stored in the INDX cluster (check via transaction HRAUTH), it is possible that the CP object to be uploaded from the idoc is not yet in that list. Because the list needs to be updated with the program RHBAUS00... On the second try, some objects could have been uodated by the first run and then...

Best regards,


Answers (0)