I changed inbound IDoc processing from immediate to batch. Under immediate processing, IDoc status went from 64 to 62 to, for example, 53 in one second. Under batch processing, the IDoc went from 64 to 62 in 2 hours then to 53 in one second. I am trying to process a total of 1,500 IDocs. The immediate runs were on a message server that is all dialogue. The batch was routed to a standard app server that has dialogues and background WP. Both servers were identical. Any ideas on what is going on? There is definitely a batch job defined (standard call is to ABAP RBDINP01 or RBDMANIN) which processes the IDocs. This job is apparently scheduled for a certain time only. Try to find the job with SM37 by either looking at the period when your IDocs are indeed processed or try to find a step with RBDINP01 or RBDMANIN.
An SAP user is receiving an error message while integrating SAP iDoc PORDCR1 for a purchase order.
SAP expert Axel Angeli explains how to update the "further dates" tab information in am SAP transaction through an SAP IDoc.
An SAP R/3 4.7 user wants looking to post a document entry using different trading partner fields for credit and debit for function FB01.