cancel
Showing results for 
Search instead for 
Did you mean: 

No authorization for changing Customer Centrally- Idoc in Error Status 51

Former Member
0 Kudos

Hi Experts,

We are implementing MDM for one of the client.

The client runs a modification scenario in MDM for Customer Master.

He modifies a customer record in MDM and this record is transfered from MDM to ECC via PI through Idocs.

We are using standard Idocs for Customer Master which is DEBMDM

There are 2 Idoc's generated in ECC by PI from DEBMDM as DEBMAS and ADRMAS.

ADRMAS Idoc is succesfull in ECC and the corresponding record is modified.

Now the issue is that the corresponding DEBMAS Idoc goes into Error 51.

The Error details is as below:

No authorization for changing vendor Centrally

Message no. F2326

System Response

You cannot access the requested data.

Procedure for System Administration

If necessary, include an entry in the user's authorization profile for

the authorization object and parameters specified below.

Authorization object:

o F_KNA1_APP

Parameters:

o Activity: 02

o Application authorization : *

We gave the respective authorization object to the RFC User ID used in PI RFC created to connect to ECC.

Also we have given the user id Tcode authorization like XD01/02/03.

But this error still persists.

Request to throw some light on this.

Cheers

Dhwani

Accepted Solutions (0)

Answers (1)

Answers (1)

Lakshmipathi
Active Contributor
0 Kudos

Check these threads

[Re: IDOC STATUS - 51 " IDOC HAS TEST STATUS|;

[Error Inbound IDoc - Status 51|;

thanks

G. Lakshmipathi

Former Member
0 Kudos

Hi Lakshmi,

Thanks for your response, checked the above links....no luck here....

Any other clue?

Cheers

Dhwani

Former Member
0 Kudos

Hi Experts,

The above issue has been resolved.

The resolution is as below:

The IDOC's once reach ECC are run by Background jobs.

These background jobs were scheduled by a totally different user which did not have any authorization to do any Transaction entry.

We found the user id and gave the necessary authorizations and now the error is no more visbile.

Cheers

Dhwani