1. when a single BillingDocumentRequest_In message includes several billing documents, are invoices created sequentially or is execution split into parallel jobs?
Within one message the backend logic of the API will process the serveral invoices togehter and try to converge billable items taking into account the split criterias.
2. if a second message is sent while the first one is still in progress, are the invoices of the second one created only after the first one is complete or can the respective documents be mixed?
Sending a message the message will process in seperate job and has no dependencies to the first message.
3. during month-end collective billing, the external system can send messages containing up to 1.000 invoices with up to 100 items each: based on the experience of other installations, should we expect performance problems, negative impacts on the other running apps, shortage of resources, locks overflow, etc:? immediate elaboration of output message has already been switched off.
Several thousands of items can be processed at once but from 50.000 items the system runs into paging problems caused by memory shortages (from ABAP side). Then a packaging of the items to be processed is recommended: a good criterion could be the sold-to party. And if the packages are still too big, the billing date could be an additional criterion but only if it shall not be overwritten by a default date. That means, the numbers of invoices per call must be reduced.
4. is there a limit in the size of the SOAP call?
The maximum size is limited by 5 MB.
5. is there a timeout in the call of the SOAP message?
The timeout for SOAP Calls is 30 seconds.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.