cancel
Showing results for 
Search instead for 
Did you mean: 

Parthner Profile status 37: Entry in outbound table not found

Former Member
0 Kudos

hi every one...

i crated we20 Partner Profile for sender in R3 with outbound parameter as Cremas..

but when i use we19 tool for testing....iam gting an error with status code 37 : Entry in outbound table not found

can anyone help me...

thx in advance

john wesly

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi John,

Can you check the entry of your message type specific to IDoc in outbound parameters while maintaining partner profiles in WE20?

and are you using any message variant specific to message type?

Regards,

Anoop

Former Member
0 Kudos

Hi,

Have you used correct Control record values while Testing

Check this

/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi

Regards

Seshagiri

Former Member
0 Kudos

hi..

i kno how to test an Idoc,.....

iam gting an error with with status code 37...Entry in outbound table not found

how to solve this problem...i hope u gt it..

its showing that there is prob in Partner no...

but i configured it properly.....

thx..

john

Former Member
0 Kudos

Hi,

Iam sure abt the error that you have made an error

1) Either in message type havent mentioned the correct port

2) In control record values are inconsistance

Regards

Seshagiri

Former Member
0 Kudos

hi...

receiver port (PI7CLNT001) and Message type(CREMAS) are correct...

but control record values are also correct....sender details and receiver details are perfect...

can u clarify it..

thx..

john

Former Member
0 Kudos

Hi,

the status code indicates that IDoc added incorrectly..it means there is problem of missing the settings...

Troubleshooting IDOC scenario

1. Start with checking the status in sm58 of sender R/3

Follow the steps

2. Try deleating the IDoc from IDX2 and refiring the same.

3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).

In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system

4. Monitor the SM58 in R/3 for IDOC status.

Also check other status fine in the IDOC status segment

Thanks

Swarup