IDOC Status 51 for HTTP to SAP ECC

[Former Member]

Hello Experts,

I have a HTTP to IDOC Scenario , its running fine for messages. Some messages are failing in ECC with the IDOC status as 51 ,  with the error that it was using the User as different one for the failed ones. But for successful one it was using the correct one which we have maintained in RFC destination . Can some one suggest me what needs to be done.

Thanks,
Vijay Kumar

[Former Member]

Hi Vijay

As you have written that the idoc fails with 51 status, which means the idoc has created in ECC and failed in ECC during final posting.

status 51 occurrs only when the idoc is generated and having some problem duirng final posting ecc due some reason.

[Former Member]

Hi Vijay,

As said by Indra Kumar Idoc is posted and created but failing to post the data to applications.  Check with ABAPer of functional team understand the issue.  It might be due to data problem.

Thanks,

Satish.

[Former Member]

In the above scenario for the failed messages (with the Status 51) , it was using the different user which we have not maintained in RFC destination for this scenario. for the successful messages it was using the correct user in the RFC destination.

[Former Member]

Hi Vijay

Idoc falied in ECC with 51 status mainly because of the data issue in the iodc.

Check the idoc in ECC using we02 or we05, click on the status, it will show you an error message.

If you are not able to understand the error message, then take the help from ABAP.

[Former Member]

Hi Indrajit,

Idoc falied in ECC with 51 status mainly because of the data issue in the iodc.

---> Actually it was not failed in mapping , it was successful in PI , but It was not creating any idoc in the ECC system.

Also the message contains different user name other than the messages which are successful .

[Former Member]

Hi Vijay,

To get more details of Idoc error, go to Idoc status record, browse for 51 details which will be in red.

As you mentioned user was different than you were using, these Idocs could be created from other system may be CRM, SRM, other PI or even internal to ECC. Check with ABAPer to get more details of the error.

Regards,

Pranav