![]() ![]() If function module fails, there is an RFC issue.NOTE: when entering RFC destination, keep in mind the field is case sensitive. Hit test button, Enter RFC destination (the interface system of the IDoc).Note: In most of the case we'll not have access to SM59 to test the RFC Connection. Go to SE37, enter function module RFC_PING. If IDoc is still stuck in SM58, check RFC connection. Validate in receiving system via WE05 that the IDoc was received. If after the RSARFCEX program has ran and IDocs are not in SM58, issue should be solved.If message type exist and Run the Program 'RSARFCEX' If entries exist in SM58, look for Message Type.Enter a ‘*’ in all fields except leave Display period field with default values. If the IDoc is located and status is successful but receiver has not received the IDoc, execute transaction SM58 to determine if IDoc is stuck in the ALE/RFC layer.If the IDoc is in Yellow status (Status-30), you can push through Transaction code - BD87.Use steps in Case 1 and 2 to verify if the IDoc was created or not and if IDoc is in a successful status or not.Case 3: IDoc created, but not received by receiving application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |