Message Mapping IDoc-segment

[Former Member]

Hello,

In my scenario I will do the following mapping with an source structure to an ORDERS05 Idoc:

file structure:

#E1EDP01|10|33|ST

#E1EDP20|33|20050823

inbound message:

<?xml version="1.0" encoding="utf-8" ?>

<ns:MT_ORDERS_OUT xmlns:ns="http:/ /ORDERS">

<E1EDP01>

<IDENTIFIER>#E1EDP01</IDENTIFIER>

<POSEX>10</POSEX>

<MENGE>33</MENGE>

<MENEE>ST</MENEE>

</E1EDP01>

<E1EDP20>

<IDENTIFIER>#E1EDP20</IDENTIFIER>

<WMENG>33</WMENG>

<EDATU>20050823</EDATU>

</E1EDP20>

</ns:MT_ORDERS_OUT>

MT_ORDERS_OUT to IDOC ORDERS05 :

E1EDP01 ___> E1EDP01

POSEX ____> - POSEX

MENGE ____> - MENGE

MENEE ____> - MENEE

E1EDP20 ______> E1EDP20

WMENG ________> - WMENG

EDATU _________> - EDATU

configuration of the file adapter:

recordsetstructure: E1EDP01,,E1EDP20,

keyfield: IDENTIFIER

E1EDP01.keyFieldValue = #E1EDP01

E1EDP01.endSeparator = 'nl'

E1EDP01.fieldSeparator = |

E1EDP01.fieldNames = IDENTIFIER,POSEX,MENGE,MENEE

E1EDP20.keyFieldValue = #E1EDP20

E1EDP20.endSeparator = 'nl'

E1EDP20.fieldSeparator = |

E1EDP20.fieldNames = IDENTIFIER,WMENG,EDATU

With this configuration, the result is only a mapping of the E1EDP01 fields.

I can't see the E1EDP20 fields in the IDoc.

Did I something wrong?

Regards

Christoph

[Former Member]

The inbound message you posted is from the payload ?

If yes copy and paste this in the Message Mapping and test it there.

Or your file adapter is not doing the conversion the way you are expecting ?

regards

Shravan

[Former Member]

Hello Shravan,

I guess my file adapter is not doing the correct conversion.

The payload of the inbound message must look as follow:

<E1EDP01>

<IDENTIFIER>#E1EDP01</IDENTIFIER>

<POSEX>10</POSEX>

<MENGE>33</MENGE>

<MENEE>ST</MENEE>

<E1EDP20>

<IDENTIFIER>#E1EDP20</IDENTIFIER>

<WMENG>33</WMENG>

<EDATU>20050823</EDATU>

</E1EDP20>

</E1EDP01>

my actuel payload looks like:

<E1EDP01>

<IDENTIFIER>#E1EDP01</IDENTIFIER>

<POSEX>10</POSEX>

<MENGE>33</MENGE>

<MENEE>ST</MENEE>

</E1EDP01>

<E1EDP20>

<IDENTIFIER>#E1EDP20</IDENTIFIER>

<WMENG>33</WMENG>

<EDATU>20050823</EDATU>

</E1EDP20>

Who can help me, with the conversion?

Christoph

[Former Member]

In the Content Conversion, did you mention parameter recordset Structure = E1EDP01,1,E1EDP20,*

That could be the problem.

regards

Shravan

[Former Member]

You also need to mention <b>Document Name, Document Namespace</b>.

Follow the weblog. remember to ignore the Recordset name, the last screen shot.

/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file

regards

Shravan

Message was edited by: Shravan Miryala

[Former Member]

I need the following recordset stucture:

E1EDP01,,E1EDP20,

because we are talking about itmes.

example:

E1EDP01

-10

-XXX

_E1EDP20

__XXX

__XXX

E1EDP01

-20

-XXX

_E1EDP20

__XXX

__XXX

regards

Christoph