Triggering fscmService/TransactionManagerServiceV2 with massive amount of transaction lines (limit?)
Summary:
Hi,
We would like to understand the technical limit of the number of rows per call or the MB limitation of the request on the SOAP API call to the web service fscmService/TransactionManagerServiceV2.
OIC's restriction is 50 MB, but is there any other limitation specifically for this SOAP API?
We tried to trigger the SOAP API with 1 <InterfaceRow> and 6000 <InterfaceLotRows> attached to it, and it worked immediately.
However, while trying to trigger it with 1 <InterfaceRow> and 6000 <InterfaceLotRows> + 1 <InterfaceRow> and 20000 <InterfaceLotRows>, we received the following error:
"Error sending bytes: Cannot handle an err or that was raised during the invocation of a cloud application. Please check the logs or raise a support ticket. :Application Error"