Issue w/ File content conversion (Receiver side)

[Former Member]

Folks, there seems to be an issue with the conversion. I've read several of threads on this forum, but none helped! Although the file is generated with 8 bytes there seems to be nothing in the file.

However when 'File' message protocol is used, the xml file is generated correctly as expected. All my other settings are fine.

Here is the scenario:

1) created Message type -

MTX

..Material

..BaseUnit

..MatGrp

..Division

2) comm. channel created for -

Transport protocol: File (NFS)

Message protocol: File content conversion

Recordset Structure: MTX

parameters:

MTX.fieldSeparator: ,

MTX.endSeparator: 'nl'

Should recordset struc. and parameters have 'ns0' prefix, i.e.,

Recordset Structure: ns0:MTX

parameters:

ns0:MTX.fieldSeparator: ,

ns0:MTX.endSeparator: 'nl'

What esle is missing? any thoughts are welcome.

Thanks and appreciate your responses.

[Former Member · Accepted solution]

MTX is the message type.....you shouldn't give MTX in record set structure....

Create a node in data type and place the fields under this node.then give this node's name in recordset structure.....

the content conversion parameters shld start with this node name...

[former_member859847]

Hi ABAP JUNOON,

Could you please create another Test scenario and

try

MTI_XXX

- DATA(0..unbounded)

- fields?

i mean, without redundant RS(Record Structure).

and use

Transport protocol: File (NFS)

Message protocol: File content conversion

Recordset Structure: DATA.

it will written the complete output file.

some people create the Reciver data type for test scenario's as follows.

MTI_XXX

-RS

- DATA(0..unbounded)

- fields?

i mean with redundant RS

in this case file is generated, but nothing will be appear.

so plz take care while creating the reciver data type with FCC.

and the following case also will work i.e

MTI_XXX

-RS

-Header(0,1)

- fields?

- DATA(0..unbounded)

- fields?

- Trailer(0,1)

- fields?

Regards

Mahesh.

[Former Member]

Thank you all folks, finally I was able to generate a flat text file. How I resolved:

1) created a child node MTXC (w/ 0...unbounded occurence) under MTX in the Message type.

2) removed 'ns0' from recordset structure

-JUNOON

[former_member859847]

Hi ABAP JUNOON,

Could you please create another Test scenario and

try

MTI_XXX

- DATA(0..unbounded)

- fields?

i mean, without redundant RS(Record Structure).

and use

Transport protocol: File (NFS)

Message protocol: File content conversion

Recordset Structure: DATA.

it will written the complete output file.

some people create the Reciver data type for test scenario's as follows.

MTI_XXX

-RS

- DATA(0..unbounded)

- fields?

i mean with redundant RS

in this case file is generated, but nothing will be appear.

so plz take care while creating the reciver data type with FCC.

and the following case also will work i.e

MTI_XXX

-RS

-Header(0,1)

- fields?

- DATA(0..unbounded)

- fields?

- Trailer(0,1)

- fields?

Regards

Mahesh.

[Former Member]

Hi Junoon,

Include ignoreRecordsetName : true in the content conversion parameters in the sender communication channel and try.

Thanks and Regards,

Induja

[Former Member]

Induja, this is a conversion for the receiver side and NOT sender.

[Former Member]

Junoon,

You dont need to give ns0:MTX in the Recordset structure. Without this it should work. Since you are saying that xml file is writing fine and not the csv so there are some issues in content conversion. Can you give the target xml payload from sxmb_moni or the xml file what you have got so that somebody can suggest you the content conversion parameters.

Regards,

---Satish

[Former Member]

Thanks all for your quick response. Here is the payload:

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

- <ns0:MTX xmlns:ns0="http://test123.com">

<MaterialID>204490</MaterialID>

<BaseUnit>EA</BaseUnit>

<MaterialGroup>1234</MaterialGroup>

<Division>55</Division>

</ns0:MTX>