I am going to describe our scenario and the problem we have. An external system sends a file with the information to integrate into SAP R3. We make the transformation in three steps (3 message interfaces).
Sender -> Message interface -> Receiver
External system -> File information extration -> XI
XI -> Interface (mapping) determination depending on file information -> XI
XI -> Map the information in Idoc format -> R3
The first step extracts the information and builds a xml with all the information in one tag. The second step determine the mapping to run depending on file data.
The problem happens when the extracted data in the first step has a length of 8115 characters. This information is put in one tag called <Data>...</data> and this message is used as inbound message of second step. In this case the second step (message) stops with an error "Conection closed (no data)" in the inbound queue. In runtime workbench monitoring the message stays in "To be delivered" status.
If the lenght of extracted data is longer or shorter no error is generated. It's certainly a mistery.
Edited by: Alberto on Sep 16, 2009 2:44 PM
Edited by: Alberto on Sep 16, 2009 2:46 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.