on 2008 Feb 20 10:02 AM
Hi!
I've tried to test my scenario of EDI to customized (.csv) flatfile conversion.
I've encountered discrepancies on my output.
Instead of one .csv file, i've produced many files, in which, one file consists of one line.
PERIO;EAN;ILN;SALES;TURNO;PERFL;SUBSFL;SALUN;%CURRENCY%;STOCK;STOUN;ARTNR
20080112;737052056760 ;4327926000003; 1; 12.90;W;X;ST ;EUR;0000000000;ST ;
PERIO;EAN;ILN;SALES;TURNO;PERFL;SUBSFL;SALUN;%CURRENCY%;STOCK;STOUN;ARTNR
20080112;737052056852 ;4327926000003; 4; 41.80;W;X;ST ;EUR;0000000000;ST ;
PERIO;EAN;ILN;SALES;TURNO;PERFL;SUBSFL;SALUN;%CURRENCY%;STOCK;STOUN;ARTNR
20080112;737052057101 ;4327926000003; 1; 12.90;W;X;ST ;EUR;0000000000;ST ;
The output should be one file, containing all lines.
PERIO;EAN;ILN;SALES;TURNO;PERFL;SUBSFL;SALUN;%CURRENCY%;STOCK;STOUN;ARTNR
20080112;737052056760 ;4327926000003; 1; 12.90;W;X;ST ;EUR;0000000000;ST ;
20080112;737052056852 ;4327926000003; 4; 41.80;W;X;ST ;EUR;0000000000;ST ;
20080112;737052057101 ;4327926000003; 1; 12.90;W;X;ST ;EUR;0000000000;ST ;
Kindly advise if whether there are changes in configurations that i should made.
Thank you!
Hi,
Please can you give me the details that you had configured in File content conversion.
Refer
How to process CSV data with XI file adapter
/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
Thanks
swarup
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
I've configured Receiver File Adapter.
The output from XI is a XML of the customized flatfile.
Here is the configurations i've made,
Transport Protocol: File System (NFS)
Message Protocol: File Content Conversion
Adapter Engine: Integration Server
File Access Parameters
Target Directory: (my specified directory)
File Name Scheme: .csv
Processing Parameters
File Construction Mode: Add Message ID
Write Mode: Directly
File Type: Text
Variable Substitution (target Directory/File Name Scheme)
- Enabled
Variable Name : var1
Reference: message:receiver party
Run Operating System Command After Message Processing
Command Line: chmod 664 %F
Content Conversion Parameters:
Recordset Structure: SLI
SLI.addHeaderLine: 3
SLI.headerLine: PERIO;EAN;ILN,....
SLI.fieldSeparator: ;
SLI.endSeparator: 'nl'
Adapter Status:
State: Active
Hi,
You are using the NFS system with content conversion.
Try to replace above CC parameters as
File Name Scheme: %var1%.txt
Processing Parameters
File Construction Mode: Add Message ID
Write Mode: Directly
File Type: Binary
Refer below link for the Receiver side snap-shots
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Thanks
Swarup
Hi,
Check with the link I had shared in above post
How to process CSV data with XI file adapter
/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
Here you will get all the confugurations for receiver CC.
Just the difference is that here its used the FTP with File content conversion,
In your case its NFS with content conversion.
But Please try it with mentioned steps in XI for receiver CC.
I had applied it on my system and its working fine.
Thanks
swarup
Hi,
Thanks for the information.
But, I believe, the one mentioned in the Blogs is converting csv file into xml?
Is it ok if I configure my actual scenario for this flatfile conversion?
3rd party -
> SAP XI ---> File Directory
3rd party will send an EDI message (D96A_SLSRPT) to SAP XI.
SAP XI, then translate this EDI message into a customized format flatfile.
The output from XI is XML flatfile.
What happened is that when EDI message enters Seeburger, it splits the message depending on the number of UNH segments contained in the EDI.
That's why, if it enter XI, it will be mapped per message splitted.
The message will enter XI not as a one content message but a splitted message.
I think, Comm channel is ok, the problem is on the splitting of the message.
E.g. this is my EDI source message that will enter XI,
UNA:.? 'UNBUNOC:34304218000002:144004711000003:14080113:004313369+SLSRPT+EANCOM'UNH1SLSRPT:D:96A:UN:EAN004'BGM73E::9432792620080112'DTM137:20080113:102'NADFR4304218000002::9'NADSU4004711000003::9'LOC1624327926000003::9'DTM356:20080112:102'LIN1+737052056760:EN'PRIAAB:12.9::RTP'QTY153:1'LIN2+737052056852:EN'PRIAAB:10.45::RTP'QTY153:4'LIN3+737052057101:EN'PRIAAB:12.9::RTP'QTY153:1'LIN4+737052073552:EN'PRIAAB:10.49::RTP'QTY153:1'LIN5+737052073750:EN'RFFPD:018099'PRIAAB:5::RTP'QTY153:1'LIN6737052078397:EN'PRIAAB:10.95::RTP'QTY153:1'LIN7+737052083247:EN'PRIAAB:10.95::RTP'QTY153:3'LIN8+737052091426:EN'PRIAAB:10.95::RTP'QTY153:1'LIN9+737052093727:EN'PRIAAB:15.95::RTP'QTY153:1'LIN10+737052133430:EN'PRIAAB:9.95::RTP'QTY153:2'LIN11+4004711091100:EN'PRIAAB:12.95::RTP'QTY153:1'LIN12+4004711113802:EN'PRIAAB:9.95::RTP'QTY153:3'LIN13+4004711119002:EN'PRIAAB:9.95::RTP'QTY153:1'LIN14+4004711119309:EN'PRIAAB:9.95::RTP'QTY153:2'LIN15+4004711721908:EN'PRIAAB:8.95::RTP'QTY153:2'LIN16+4004711729300:EN'PRIAAB:9.95::RTP'QTY153:1'LIN17+4004711731907:EN'PRIAAB:8.95::RTP'QTY153:2'LIN18+4004711751905:EN'PRIAAB:8.95::RTP'QTY153:1'LIN19+4004711800108:EN'PRIAAB:6.95::RTP'QTY153:1'LIN20+4004711800146:EN'PRIAAB:6.95::RTP'QTY153:1'LIN21+4004711800832:EN'PRIAAB:16.45::RTP'QTY153:1'LIN22+4004711860416:EN'PRIAAB:12.75::RTP'QTY153:1'LIN23+4082800028510:EN'PRIAAB:13.95::RTP'QTY153:1'LIN24+4082800140007:EN'PRIAAB:7.95::RTP'QTY153:1'LIN25+4082800160906:EN'PRIAAB:10.95::RTP'QTY153:1'LIN26+4082800171902:EN'PRIAAB:10.45::RTP'QTY153:2'LIN27+4082800180805:EN'PRIAAB:10.95::RTP'QTY153:1'LIN28+4082800189303:EN'PRIAAB:8.95::RTP'QTY153:1'LIN29+4082800350444:EN'PRIAAB:16.95::RTP'QTY153:1'LIN30+4082800351007:EN'PRIAAB:10.95::RTP'QTY153:1'LIN31+4082800351304:EN'PRIAAB:9.95::RTP'QTY153:1'LIN32+4082800381103:EN'PRIAAB:9.95::RTP'QTY153:1'LIN33+4082800381301:EN'PRIAAB:10.95::RTP'QTY153:1'LIN34+4082800500269:EN'PRIAAB:17.45::RTP'QTY153:2'LIN35+4082800501730:EN'PRIAAB:10.95::RTP'QTY153:1'LIN36+4082800561369:EN'PRIAAB:19.95::RTP'QTY153:1'LIN37+4082800713058:EN'PRIAAB:9.95::RTP'QTY153:1'LIN38+4082800783402:EN'PRIAAB:19.95::RTP'QTY153:1'UNT123+1
This EDI message will enter Seeburger, and will be splitter depending on the number of UNH segments.
then the splitted message will be translated into XML, then will be mapped on customized flatfile.
Output is one UNH segment (one tag XML) will be converted into .csv flatfile.
Thats why the output is many files because of the splitted message from Seeburger.
Could you advise on what will be the configurations to be done so as Seeburger will not split the message?
And the whole EDI message will enter XI as a whole?
Thank you very much for your time.
Fred
Hi,
Split 997 will split the message on UNH level and will generate multiple output for every UNH.
Sometime it may require that for every UHN u have to post one IDOC at R3 so that time u require split 997 channel.
In ur case what is the requirement?
U need to have separate output file for each UHN or one one file for whole message.
Thnx
Chirag
Hi Chirag!
For our scenario, we have one EDI message file.
In which, it contains multiple UNH segments.
The output .csv file must be ONE only, containing all of the UNH segments, which is translated into flatfiles.
PERIO;EAN;ILN;SALES;TURNO;PERFL;SUBSFL;SALUN;%CURRENCY%;STOCK;STOUN;ARTNR
20080112;737052018324;4319814000004;1;12.95;W;X;ST;EUR;000000000;ST -- > depends on the value of UNH segment
20080112;737052018324;4319814000004;1;12.95;W;X;ST;EUR;000000000;ST --> UNH 2
20080112;737052018324;4319814000004;1;12.95;W;X;ST;EUR;000000000;ST --> UNH 3
The output must be ONE .csv file only for whole message.
Kindly advise.
Thank you very much!
Hi,
Let me tell u what I understood till now.
U have two sender communication channel
1) Splitt 997
2) File sender adapter
and two sender agreements.
At the receiver side also u r using receiver file adapter.
If u do not want to split the file then u remove the split channel from configuration and use only sender file adapter in configuration scenario.
In order to change the EDI to XML u need to do configuration in the file sender adapter u need to write the module parameter name so that it will conver the EDI-XML and u know the FCC parameter of Receiver adapter.
Thnx
Chirag
User | Count |
---|---|
73 | |
10 | |
9 | |
8 | |
8 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.