message failing in outbound status

[Former Member]

hi all,

we have SNC - ECC scenario( Proxy to IDoc)

the message is successful in PI i.e. it has black checked flag in status coloumn,But in Outbound status coloumn it has red flag.

no messages struck in smq1, smq2 and sm58 (both on ECC side and PI side).

The IDoc is not reaching the target system i.e we cannot see any IDocs in we02.

can anyone please tell me how and where do we see the error details for such messages?

Regards,

Aditi.

[Former Member · Accepted solution]

Hi Aditi,

If your message has red flag in outbound side, it would be stuck in SM58. Could you verify if you checked SM58 by removing your SAP user name and putting * there.

You could find the reason for error there which will help us to answer you better.

hope this helps,

Ankit

[Former Member · Accepted solution]

thanks for the quick replies.

after removing the user from SM58 in PI system.

the error we are getting is ' name or password is incorrect(repeat logon)'.

So is this referring to logon details in RFC Destination?

[Former Member · Accepted solution]

yes

in XI system, go to SM59 and test the R/3 connection to ECC system.

[former_member184681 · Accepted solution]

Hi,

Yes it does refer to RFC Destination logon credentials. You need to put them back there, otherwise you won't be able to send messages to that target system. After you put the credetials back, perform the Connectivity Test and Unicode Test, then check if the Unicode settings matches the results.

Hope this helps,
Greg

[Former Member · Accepted solution]

already suggested that you have to check the RFC destination...either reset the password of the user or use the new user credentials and after that do a connection test of your RFC destination...

[Former Member · Accepted solution]

Hi Aditi,

As already suggested by Greg & Amit, Correct the login credential in RFC destination or get it corrected from Basis.

Once that is done you can re execute the LUW to send the stucked idocs. To Re-execute Go to SM58, put the cursor on LUW and from Edit Menu -> Execute LUW.

hope this helps,

Ankit

[Former Member]

Go to the RFC destination

Utilities -> Test -> Authorization Test.

This will test the connection with the User Credentials.

[Former Member]

Check SM58 for the same date as the IDOCs failed in PI in outbound status. It may help in these cases

[Former Member]

Hi,

I doubt this is something related to RFC destination which is pointing to your ECC system (used in IDOC receiver channel)..check the same...

Thanks

Amit Srivastava

[Former Member]

Seems like User ID  of ECC System which is mentioned in the RFC Destination is having the issue.

go to ECC system , tcode SU01/ Su01d  -  check the user ID there. It may be locked or password may be expired.

The best way to conform it is a credential issue is by doing a Remote Login and Connection Test.

Once you click on Remote login - / If it is asking for a passord , that confirms that the USER ID mentioned is unable to login to ECC.

So, you need to fix the user Id and then just refresh the messsage it will move to ECC.

Regards,
Biplab Das

[iaki_vila]

Hi Aditil Goel,

Check st22 in ECC in orde to watch if your IDOC throws any exception and you could give us the SAP PI exception in outbound side (sxmb_moni transaction).

On the other side the metadata for an IDoc is loaded in the Integration Server when the first message for the particular IDoc is processed by the Integration Engine. You can see the IDoc metadata using the transaction IDX2

Regards

[Former Member]

check in IDX5 transaction in XI system if you see anything for this error.

also in XI system run SXMB_ADM transaction - manage queues option, register all queues and activate queues.

then rerun your scenario again from source system and see if your IDOC reaches ECC system.