Hi,
Try to see in sm59 transaction of SAP. Also check if there is another adapter listening to your program ID of SAP. this program ID should be unique for every running R3 adapter instance. All the services should be under one adapter instance.
Verify the configuration on SAP AS.
Configure the appropriate message type for the partner in the outbound parameter of the partner profile (WE20) . Afterwards reprocess your failed idoc using the program RBDAGAIN
Try Posting the Idoc with the help of WE19 instead of using your report.
Status 29 indicates that the Partner Profile is not configured correctly.
As you know the target logical system is nothing but the partner, select that and click on Outbound Parameters and add the message type.
Status 30 indicates that the Idoc has been generated successfully.
Status 03 indicates that the Idoc has been reached Middleware.
Try running the standard program RSEOUT00.
All the Idocs in 30 statuses will change to 03.
To get all the IDOC's in status '03'
after MASTER_IDOC_DISTRIBUTE
Call FM "EDI_DOCUMENT_DEQUEUE_LATER"
Review transactions currently in queue using SAP transaction SM58. If the transaction is in error, it can either be retried manually or retried automatically by the SAP system using the configuration defined for the corresponding RFC destination. It is not recommended to retry manually unless the outbound adapter is running. If the manual retry is unsuccessful then the automated SAP retry would cease and manual intervention is required.
Hope this help!
Regards,
Ashvin