Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Partner Profile for IDOC - configuration

Former Member
0 Kudos

Hi..

I have an inbound IDOC TPSSHT01, which has been extended by adding a Z segment.. But I keep getting an error message.. The IDOC is created with status 56 and the message says "No inbound profile found".. I have configured the Inbound profile to include the message type 'SHIP' in WE20 and also added the message type in WE57 and WE82... Do i need to do any further settings?

Thanks

Rishi

5 REPLIES 5

Former Member
0 Kudos

hI,

Please use transaction code WE20 to generate inbound partner profile

Goto WE20 transaction of the client 200 where you are posting the idoc and maintain the partner profile for the inbound type for the idoc type and the corresponding message type of SHIP. This is because you would have maintained it as the outbound parameter from client 100. But at the receiver end also you need to configure the same.

Status 56 comes up when the partner profile for the idoc type is not maintained. Once its maintained, the idocs which you post will go into 53 if its successfully processed and to 51 if its failing due to any inbound processing program validation

<b>*Reward points</b>

Regards

Former Member
0 Kudos

keep the outbound parameters in partner profile ,here fill the message control.

Former Member
0 Kudos

Hi,

Did you provide the extension you created in the partner profile under the "Extension" field?

~ Bineah.

Former Member
0 Kudos

Here is one way you may want to take.

1) Delete the existing Parner profiles through WE20 for Particular Message Types

2) Go to BD64 , Click on Model Environment - generate Partner Profiles

Now check whether the parner profiles are generated correctly.

Or you still face the issue.

Regards

Shital

Former Member
0 Kudos

Hi,

-> where the extension released in WE30?

->BD64, model distributed?

->Has SYNCH message type been included in the outbound parameters in the partner profile?

Thanks

Krithika