Suggest Approach - Flat file to SAP

[Former Member]

Hi Experts,

Client having below format for Input data i.e txt and want to integrate through PI 7.1 into SAP.

As shown is one type of record and it is getting change with every new record and there are more than 1000 entries ..

As there is only mechanism is FCC , Is it possible as it having huge file size of 10MB

BFH0000000101ASR 000 1201100000 000000

BCH0000000202 0120110F

BOH000000030311000415120110BOPGS EUR2 120110BGF 4LZ20005268

BKT0000000406XXX 000000BOPGS 2012-01-10 000 00000000 00000000 00000000

BKS00000005241201100000000710480183953 110137890310 VOID EQPPCA BOP4AS

BKS00000006301201100000000710480183953 10000000150{0000000000{ 0000000000{ 0000000000{0000000000{0000000000{ EUR2

BKS00000007391201100000000710480183953 1 0000{0000000000{ 0000{0000000000{0000{0000000000{0000000000{

BKS00000008450000000000000715324520425 5 34 0000000000{ 000000

BAR00000009641201100000000710480183953 10000000150{ 0000000000{ EUR2

BAR00000010651201100000000710480183953 1MAGEOT/THIERRY

BKP0000001184000000000000CA 0000000149F 000000

BKT0000001206TKTE 000000BOPGS 2012-01-10 000 00000000 00000000 00000000

Please suggest right approach ?

Thanks.

[Former Member]

Hi Praveen & Raja,

Thanks. At SAP end it is going to table through RFC because functional want to use it.

Please comment !

[rajasekhar_reddy14]

Your source structure looks unstructured one, did your functional team shared Data mapping document.

If defining FCC in generic way not possible then read evry one line as a string and as per data mapping document perfrom spliting.

[rajasekhar_reddy14]

Do you want to convert to IDoc/BAPI ? or simply dump in to SAP NFS?

if there is no conversion required then without ESR objects configure ID part and dump to NFS,100 mb not a biug deal.

If you want to post it as a IDoc or BAPI then as praveen suggested go with record sept per message option.

[former_member181985]

10MB flat file might lead to heavy XML message depending upon the field names length in XML structure.

Use recordsets/per message concept in sender file channel to chunk the data which is best suitable for IE in terms of performance (SAP recommendation: ideal message size for IE is 5 MB)