cancel
Showing results for 
Search instead for 
Did you mean: 

OUTBINDING">CO_TXT_OUTBINDING_ERROR in sxmb_moni

Former Member
0 Kudos

Hi Experts,

My scenario is file 2 proxy. I am getting the error in sxmb_moni: OUTBINDING">CO_TXT_OUTBINDING_ERROR.

Tested my configuration in Integartion Builder Configuration toll and its showing Green.

I have deleted the SA,RA,ID and RD and created once again,but still showing the same error.

Do i have to apply the below notes or do we have any other solution for this.

SAP notes

Note 1278244 - System error in interface ServiceRequestConfirmation

Note 1284103 - System error in interface ServiceRequestConfirmation

1278273

Regards

Santiosh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Did you checked the sender keys generated at runtime

i.e Sender Party(if used) ,sender Business system/service, sender interface namespacename and interface name and these

details are exactly matching with the Receiver agreement of your scenario..

please cross-check the same and if everything is fine ...then check the cache and do a refresh of the both SXI_CACHE and CPA Cache...

HTH

Rajesh

Former Member
0 Kudos

Hi Rajesh,

Where will i get get the sender keys

The Business system/service, sender interface namespacename and interface name and these details are exactly matching with the Receiver agreement of your scenario..

All are matching exactly.

I have done the SXI_Cache as well as CPA Cache

Regards

Santosh

former_member200962
Active Contributor
0 Kudos
Where will i get get the sender keys

In SXMB_MONI in the header section for that message processing.

Former Member
0 Kudos

Hi Abhishek,

I tried to compare the success message with soap hearder with the failed one.

http://XXX.com/PI/MATERIAL_MASTER_SizeGroup">MT_Material_SizeGroup - failed message

http://xxx.com/PI/MATERIAL_MASTER">MI_Material_OB - Success message

In failed message its taking Messahe type whereas in success its taking Message interface.

Now pls let me know where should i chage the particular value.

Now

Former Member
0 Kudos

Hi Abhishek/Rajesh

I have checked in Sender agrement and as well as receiver agrement it has MI_Material_OB and in receiver agrement its MI_SizeGroup_IB but when i go to sxmb_moni and see soap header its taking MT_Material_SizeGroup . I tried to refresh cache and tried to deactivate and activate the queue but no change .

Since i designed the scenario in pi7.0 and now its upgraded to pi7.1 its the problem.

please let me tell me how to proceed furher.

Regards

Santosh

Former Member
0 Kudos

Hi Abishek/Rajesh,

The problem got resolved . We cannot implement the sap notes.

While testing from RWB i am giving the Message type instead of Message Interface.

By giving the right Messager Interface the problem got resolved.

Regards

Santosh

Answers (3)

Answers (3)

Former Member
0 Kudos

Answered

Former Member
0 Kudos

Hi,

Check in this For IDOC related Errors

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

Also check Receiver Agreement is active or not.

Also in Configuration Environment->Cache Status Overview.

if any object is not activated properly select the particular one and Reactivate by clicking Repeat Cache Notification.

Finally test your scenario by Tools->Test Configuration.

regds,

Pinangshuk.

Former Member
0 Kudos

Hi Pinangshuk

Its not related to IDOC

Receiver Agreement is active.

Cache status configuration is good,

Tested the scenario in Tools - test configuration

The strange observation is in SA,RA i have given the correct MI but in SXMB_MONI in soap header -main- its pointing towards MT because of which error is coming .

Regards

Santosh

former_member200962
Active Contributor
0 Kudos

Are the ID objects referring to proper message interfaces and Interface mappings?

Not sure of the notes but the above mentioned problem occurs when either sender agreement is really not created or when it is mis-configured or when the cache is not properly activated.

Regards,

Abhishek.