cancel
Showing results for 
Search instead for 
Did you mean: 

File to IDoc scenario-CREMAS not getting posted

Former Member
0 Kudos

Hi Experts,

i am doing a file to idoc scenario in which i am giving the xml file from MDM ,consisting of Vendor Master data and posting the address and the general data into the ADRMAS and CREMAS idocs into the R/3 system.

The problem that i am facing is that the ARMAS is getting posted correctly but the CREMAS is getting posted with the red signal,status 51.It says "Not authorized to change the Vendor Centrally."

Can anyone please tell me what is the reason and the solution for this problem?

Is this a data error or XI error?

Thanks in advance,

Shweta.

Accepted Solutions (1)

Accepted Solutions (1)

ambili_jose
Explorer
0 Kudos

Hi Shweta,

I have done exactly the same scenario. ie MDM and R/3 Integration using XI.

Source - CREMDM (File)

Target - CREMAS & ADRMAS (IDoc)

The error you are facing is because of authorization issue only. Certain fields like Vendor details are sensitive data which hold the business unit. Not all users will have authorization to change that.

Hope this helps.

Regards,

Ambili

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Shweta

Status 51, 52 means Posting error

Please check wheteher all the configuration has been done or not

SM59-rfc destination

IDX1-port

IDX2-load metadata

we05-IDoc status records

BD54-Create Partner Number

We20-Create Partner Profile

WE19-Testing IDoc Processing

After That check the solution it is due to Authorization

Regards

Abhishek Mahajan

*Please reward points if helpful**

Former Member
0 Kudos

Hi,

IDOC status 51 means application document is not posted.may be you don't have the required authorizations for that.

Thanks,

Vijaya.

former_member181962
Active Contributor
0 Kudos

Looks like, it is an authorization issue.

It is not an XI issue.

The user ID that the idoc inbound processing function module may not be authorized to make certain changes to the master data.

Or try running in all screen mode in WE19 transaction to pin point the issue.

Regards,

Ravi