cancel
Showing results for 
Search instead for 
Did you mean: 

flatfile idoc sender scenario

0 Kudos

Hi all,

we try to implement a flat file-XI-IDoc scenario. We receive flat files with idoc structure

In ID I used sender file adapter and a receiver idoc adapter

I have to use the option "File Content Conversion" in the file adapter and do I have to reproduce the whole IDoc structure in the content conversion parameters

and since i get structure/segment name ahead of each line how to i handle this

please see below

adapter content conversion parameters:

EDI_DC40.fieldFixedLengths 10,3,16,4,2,1,1,1,1,30,30,30,3,3,1,6,6,10,2,2,10,21,70,10,2,2,10,21,70,8,6,14,14,14,70,20

EDI_DC40.endSeparator 'nlu2019

EDI_DC40.fieldNames TABNAM,MANDT,DOCNUM,DOCREL,STATUS,DIRECT,OUTMOD,EXPRSS,TEST,IDOCTYP,CIMTYP,MESTYP,MESCOD,MESFCT,STD,STDVRS,STDMES,SNDPOR,

SNDPRT,SNDPFC,SNDPRN,SNDSAD,SNDLAD,RCVPOR,RCVPRT,RCVPFC,RCVPRN,RCVSAD,RCVLAD,CREDAT,CRETIM,REFINT,REFGRP,REFMES,ARCKEY,SERIAL

EDI_DC40.keyFieldValue 0

EDI_DC40.keyFieldInStructure ignore

E1EDL20.fieldFixedLengths 10,4,4,2,4,3,25,3,28,6,2,17,15,3,15,3,5,35,4,20,10,35,35,8,6,3,1,1,1,1

E1EDL20.endSeparator 'nl'

E1EDL20.fieldNames VBELN,VSTEL,VKORG,LSTEL,VKBUR,LGNUM,ABLAD,INCO1,INCO2,ROUTE,VSBED,BTGEW,NTGEW,GEWEI,VOLUM,VOLEH,ANZPK,BOLNR,TRATY,TRAID,XABLN,

LIFEX,PARID,PODAT,POTIM,LOC_SEQ,HOLD,MAX_ERR_TYPE,LE_SCENARIO,RECIPIENT_CREATE

E1EDL20.keyFieldValue 0

E1EDL20.keyFieldInStructure ignore

E1EDL22.fieldFixedLengths 30,20,20,20,25,30,40,20,20

E1EDL22.endSeparator 'nl'

E1EDL22.fieldNames VSTEL_BEZ,VKORG_BEZ,LSTEL_BEZ,VKBUR_BEZ,LGNUM_BEZ,INCO1_BEZ,ROUTE_BEZ,VSBED_BEZ,TRATY_BEZ

E1EDL22.keyFieldValue 0

E1EDL22.keyFieldInStructure ignore

sender file:

EDI_DC40 3000000001870383062700 3014 DESADV01 DESADV X004010856 SAPD7B LS SAPD7B ZSHIPNOTIFLISP0000000018 20100513233418 20100513

E2EDK07001 300000000187038306200000100000001000LLF000030003 6910689255 FOBFREE ON BOARD Y5 H502 oluquilla Wh Domestic MX00

E2EDKA1003 300000000187038306200000200000102

E2EDK03 300000000187038306200000300000102

E2EDK08001 3000000001870383062000004000000020006910689255 FOBFREE ON BOARD Y5 H502 oluquilla Wh Domestic MX00 BC

E2EDS01 3000000001870383062000005000004030011

E2EDS01 3000000001870383062000006000004030216.645 KGM

E2EDS01 3000000001870383062000007000004030226.646 KGM

E2EDS01 3000000001870383062000008000004030236.646 KGM

E2EDS01 30000000018703830620000090000040301400001

the above examples are not complete (just an example) Any help is appreciated.

Thanks,

siddu.236atgmail.com

Accepted Solutions (1)

Accepted Solutions (1)

AbinashNanda
Product and Topic Expert
Product and Topic Expert
0 Kudos

If you are on PI 711 you can use the IDOCFlatToXmlConvertor in the Module Processor. Please remember this module has certain limitations

Regards,

Abinash

0 Kudos

thank you for the reply, but its NW 4.0, and i think its XI 3.0

lets consider i want to work the conventional way, creating content conversion parameters

if so then

q1. do i have to write content conversion parameters for all fields in an idoc

q2. flat file i get on sender side has segment names on starting of each segment data, how can i skip them since i dont have to process them going further

you can see the sample of content conversion parameters i wrote in the above post

please advise

Former Member
0 Kudos

Hi,

If possible please change your scenario as like below..

Trigger the IDCO'S through TRFC port instead of using file port and doing content conversion so that you can avoid the FCC.

Former Member
0 Kudos

If you are on PI 7.11 try as Abilash suggested.

otherwise pass the flatfile IDoc as it is to R3 file directroy and process it through Inbound file port.

the program which process the Inbound flatfile Idoc is RSEINB00 and avoid FCC.

Suresh

0 Kudos

Suresh Reddy/ Venugopalarao/ Abinash thank you for guys for your quick reply

but the scenario is bit complex, we have SNC involved, we have existing scenario of sender idocs initially built,

later sender told, he can only send flatfile idoc

so i thought only change of adapter and content conversion parameters will solve this issue

please advise

can you please elaborate if you have a suggestion,

thank you

siddu.236atgmail.com

Former Member
0 Kudos

but the scenario is bit complex, we have SNC involved, we have existing scenario of sender idocs initially built,

later sender told, he can only send flatfile idoc - Can you elobarate complete your exitsting scenario if possible do the necessary changes existing one reason is below...

You should not approach the FCC becuase it's not mandatory all the segments are fields will come always order..IF Data segments field order changed then your FCC will not work properly...FCC always assume that you are getting correct order 100%. I mean field order....

Regards,

Venu.

0 Kudos

venu,

thank you for your quick reply

Trigger the IDCO'S through TRFC port instead of using file port and doing content conversion so that you can avoid the FCC.

can you please elaborate the process please, can you give me steps

thank you for your support

AbinashNanda
Product and Topic Expert
Product and Topic Expert
0 Kudos

In that case Do n't use FCC for IDOC flat file conversion to IDOC XML. Use the report RSEINB00 to convert rather. It uses a File port. Please remember this report only works if your input file has extact one IDOC.

Abinash

Answers (0)