Andre,

Just a question:

> ... and in another Compute I concatenate these elements as required to
> create the required SAP IDOC format...

Why aren't you using the IDOC parser (embedded from CSD02) instead of
concatenating? In this case your process would be clear and simpler,
because all segment fields is defined in the MRM model.

HTH,

Tibor

----

> Hi,

> MQSI v2.0.1 - CSD6:
> I have an XML message which I need to convert to MRM (in SAP IDOC format).
> We have been working with SAP IDOCs in MRM format for quite a while, but the
> inbound data we have received up to now has always been in fixed length
> string format which makes it easy to convert it to IDOC (MRM) format.
> The problem I am having now is that the inbound messages are in XML format
> (not fixed length).
> One solution I tried was to first create an MRM message which resembles the
> XML structure (The reason for this was so I could add all the necessary
> padding character details by using this "interim" MRM message). I then map
> the XML tagged fields to each respective MRM element in this interim MRM
> message and in another Compute I concatenate these elements as required to
> create the required SAP IDOC format. Unfortunately what now happens is that
> the elements seem to be "trimmed" before concatenation but in SAP the IDOC
> data is expected to be in a pre-determined fixed length format (including
> all the padding characters specified in the "interim" MRM message). I have
> set the custom wire format of the "interim" MRM message to fixed length and
> specified a padding character of "space" - however the element padding
> doesn't seem to be holding during concatenation.

> Then I tried something else - in a compute node (same compute as where I do
> the concatenation) I declare a temporary field for each of the elements
> before concatenation and use PAD to obtain the required padding (spaces or
> zero's). Concatenating these temporary padded fields worked 100% with no
> leading or trailing spaces being trimmed.

> I would like to know if there is a simpler way to ensure that when an
> element of a message is used in concatenation, the entire element length
> (including padding characters) is used and not only the "trimmed" actual
> data.

> Thanks

> Andre

> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to