file to idoc status 56

[former_member190389]

Hi,

I have already defined the partner profile in we20, but still i am receiving this error for inbound idoc.

In PI the message is successful in sxmb_moni.

I have carried the following steps in PI:

1 RFC destin in PI i.e. ERD250100 sm59

2 Port in idx1 SAPERD250

3 load metadata of ISM_MATMAS03

The following steps in ERP

1. bd54 added source file system logical name BIBLIO01

2. we20 part no. : BIBLIO01 and added the inbound parameters as ISM_MATMAS

Also in receiver idoc CC i added SAPERD250 as port and ERD250100 as the rfc destination

Now I am not able to receive idocs and before i received it with status 56

Please Help

[jose_augastine3 · Accepted solution]

Hi,

Hope this helps

File To IDOC - Part1 (SLD and Design)

http://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/File%20To%20IDOC

File To IDOC - Part2 (Configuration)

http://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/File%20To%20IDOC%20-%20Part2%20(Configuratio...

File To IDOC - Part3 (Steps required in XI and R3)

http://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/File%20To%20IDOC%20-%20Part3%20(Steps%20requ...

Regards,

J Augastine

[former_member185881]

Hi

Try this also

From PI perspective everything is fine, you were able to create an IDOC structure and push it to R/3 system and there is also successfully created but it has failed with the error 56. It is due to invalid partner profile, check the transaction WE20 whether a partner profile has been created for that partner or not, if it is created then whether the message type is configured for that partner or not.

The error is basically due to invalid partner profile and you need to correct that in WE20 transaction, once you correct that then you can reprocess the idoc through BD87 transaction.

Regards

Dheeraj Kumar

[former_member185881]

Hi

Check this blog also

/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

Check this also :

the port maintained must be of naming convention

SAP<SID>

Check this also:

Solution:-Check the partner profile is created or not, if not create partner profile, restart the process by TA.BD87.

If partner profile is exist then check the control information in the IDoc file is incorrect. Correct the IDoc file and restart the process

TA. BD87.

1. Execute transaction BD87.

2. From the screen displayed, fill in the selection criteria.

3. On the next screen, select a summary line click the process button to reprocess all IDocs represented by the line. By clicking the Restrict and process button, you will be shown another selection screen to further restrict the number of IDocs to be processed.

Check this also:

Delete the Entries under that inbound Parameters.and Add again.

Check this also:

In XI Mapping, Fill the Control Record values manually

And in the Receiver Idoc Adapter, Check the boxes

Take Sender from Payload

Take Receiver from Payload

apply control record values from payload

trigger this time and check

Hope any one of the above solution will help you.

Regards

Dheeraj Kumar

[former_member190389]

Hi All,

I tried every thing but now i am not able to receive the idocs.

This happens everytime .

Sometimes i receive the Idocs with status 56 and sometimes they dont arrive.

Please Help

[former_member190389]

Also i checked transaction Id in IDX5 of XI there is nothing wrong there.

Please Help

[Former Member]

Hi,

you mean to say that the idocs received in SAP are failing with error code 56 sometimes and not for all the idocs sent by PI..

if this is the case ,is the error code 56 is showing for the bulk of idocs sent by PI to SAP at a time ? then check the SAP Idoc sndprn is that getting replaced with the some other number....

same thing happened to me that idocs SNDPRN is getting replaced with some other internal customer no and as a result idocs were failing with error code 56...when checked with SAP team they found that some user exists were associated to that partner profile which was resulting the above...

check the same in your case too...nothing was wrong in PI side...

HTH

Rajesh

[former_member190389]

In XI I can see the send PRN properly but when i receive them there the partner info is not available with status 56.Although I have done it in we20.

Also now i am not receiveing Idocs at all.In XI I can see them but not in R/3.

[Former Member]

Hi,

if IDoc doesn't arrive at all then check SM58 on PI and R3.

try to reprocess the idocs in error with program RBDMANI2.

provide the exact status text under the status.

and as Rajesh suggested check the control record.

Suresh

[former_member190389]

I found out one clue

Actually I have to change the client from 520 to 250 for this idocs.

Now in ID i have done the required config.

But the idocs still appear in older client i.e 520 i want to have them in 250

[Former Member]

Then check the BS in SLD it might still pointing to old client 520.

and if you are using RFC destination in receiver IDoc chaneel check the client mentioned in that.

[former_member185881]

Hi Progirl Progirl

for 51 or 56 Errors do the following steps

goto WE19 > give the IDOC Number and Execute>

Press on Inbound function Module

Hope it helps

Regards

Dheeraj Kumar

[Former Member]

Hi,

Need to associate the inbound parameter for the sender partner profile of idoc....

check the Idoc SNDPRN and SNDPRT and ensure the same in SAP R/3 also the same...

Check the below blog last section which gives you more details

/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system

HTH

Rajesh