EDI to Flatfile Conversion

Hi all!
I am new in SAP XI. And i am researching on how will I convert EDI (SLSRPT) to a flatfile. Can everybody advise me on how will I handle this?
I can convert EDI to XML using Seeburger Adapter, and from XML, I will convert it to Flatfile. The conversion will take place in SAP XI. Can i use graphical mapping for this one?
Kindly advise.
Thank you!
Fred

Hi,
For the same requirement you need to follow the below steps:
1) First deploye the Std seeburger mapping provided by see burger on XI
2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
If you wanted to know more about seebuger and the configuration then refer the below breif into about seeburger and the reply to many of my threads.
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
Refer this forum which is replied by me which talka about the configuration which need to be done for AS2 adapter. This is very helpful:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.
Seeburger info:
Re: seeburger adapter
Re: SEEBURGER's VAN Adapter
AS2 info:
Re: Regarding Seeburger AS2 Adapter
SEEBURGER EDI adapter
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
Thnx
Chirag
Reward points if it helps.

Similar Messages

EDI to customized (.csv) flatfile conversion

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,
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

Error in XI while using standard EDI Libraries of Conversion Agent

Hi,
We are planning to use conversion agent for EDI to XML conversion using standard libraries.
Right now working on EDI 867 and is working fine in my local system. But when we moved the contents
to XI server, we are getting the following error
*ConversionAgent/ServiceDB/TS_867_Product_Transfer_and_Resale_Report_Parser/TS_867_Product_Transfer
andResale_Report_parsers_segments.tgp(547): is_optional is not a known profile or PT*
Can anybody help us to solve this issue?
Regards,
Ravi

HI,
The module name must be localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean.
The parameter name must be TransformationName.
The parameter value must be the conversion agent project name deployed in serviceDB. In the above example, the Tutorial_3 project from the documentation in step 1 is used.
And also it was failed to update the log.See the folder access onceagain.
many links provided in that blog itself ,plz check.
Regards
Chilla..

Create EDI 997 with conversion agent

Hello,
I work with conversion agent by ItemField to convert EDI messages to xi and from XI to EDI.
I succeeded to receive EDI 850, to parse this message and to transfer it to the IDOC and create purchase order.
Now I try to send back to the customer EDI acknowledgment (997).
I'll be happy to hear if someone use with conversion agent to create EDI 997.
Elad

Hi Elad,
What are 997s?
997 Functional Acknowledgments are EDI transactions that a receiver of EDI transaction sets sends back to the party that sent the EDI transaction sets. All EDI transactions require an EDI 997 to be sent back.
Here is an example
Wal-Mart sends an EDI Purchase Order to a supplier. With EDI Standard X12, Wal-Mart expects a 997 to be sent back to them. The 997 lets Wal-Mart know that the supplier received the Purchase Order. It does not say that the supplier accepts the terms or conditions of the purchase order. It simply lets them know that the supplier successfully received the Purchase Order.
Here is another example. A supplier sends Wal-Mart an EDI Invoice. Wal-Mart will send a 997 back to the supplier. The 997 informs the supplier that Wal-Mart has successfully received the invoice.
CovalentWorks handles all of your EDI transactions for you, including 997s, as an outsourced EDI service. If you choose us as your EDI provider, our system will automatically send and receive all your 997 Functional Acknowledgements. And every one of them is processed for you at no charge.
Thanks,
Satya Kumar..

Urgent: IDOC to EDI with SAP Conversion Agent

Hi,
I have a requiremetn like IDOC to EDI ( Gentran ) scenario.
We have decided to use SAP Conversion Agent to deal the same.
Can anybody share their experiences on this kind of scenario.
Needed step by step information to complete would be appreciated with the full of points.
Cheers.,
E

check with tis may helpful for you
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/frameset.htm
Regds
Abhishek

INVOIC96a to EDI-XML by Conversion Agent fails, Special Character Problem

Hi,
with your help in another thread, I recognized that the EDIFACT INVIOC96a Parser of the Itemfield Conversion Agent has a Problem with special characters.
So like described in this blog SAP XI supports EDIFACT i created a Library Project and tried to test the conversion.
It is only working when no special characters are in the EDI file. If there a special characters insight the file, conversion agent say's no error, but the xml file is corrupted. In fact you can't display it in IE or by opening it with XMLPad it says "Not well formed".
Hope that someone has an idea for this problem
Thank you
regards

Hi,
I have already faced the same problem when using Itemfield Conversion Agent.
I solved the same with change properties of the project.
In conversion agent project :
opne the menu : Project --> Properties --> Encoding --> Change the output Encoding Schema (None).
use None in that schema in place of XML.
Your problem can be solved.
Regards,
Sandeep Kaushik

NO Ruleset for GENRAL\96A available (EDI to XML Conversion Error)

Hi,
My Scenario is Inbound EDI Scenario. I am facing problem during conversion of EANCOM to XML .
Control Key Scenario Association part with the EDI Content Manager is filled in properly. we are not doing anything in the above Control Key
Scenario Association part .Because whatever we are saving we are not able to see in the screen. Please find the below screen shot attached.
XSD produced from B2B Integration Cockpit was being used in the ESR.
No Acknowledgement Enabled.
We have checked with the possible option in the below blog.But not working
http://scn.sap.com/thread/3309007
Regards,
Prem

Hi Dmitri/Ruchir,
By mistake I have uploaded Message Type ORDERS screen shot with Message Protocol EANCOM,but my actual one is Message Type GENRAL with Message Protocol EANCOM only
The combination of message type and version specified in the UNH segment is not maintained in the tables?
the above mentined EDIFACT\EANCOM seems different issue.
Message could not be forwarded to the JCA adapter.
Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException:
Message cannot be dispatched: Message cannot be dispatched: Error Occured :
Error in conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
available.
MP: exception caught with cause
javax.resource.ResourceException:
com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message
cannot be dispatched: Message cannot be dispatched: Error Occured : Error in
conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
available.
Exception caught by adapter framework:
com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message
cannot be dispatched: Message cannot be dispatched: Error Occured : Error in
conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
available.
Transmitting the message to endpoint <local>
using connection File_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
javax.resource.ResourceException:
com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message
cannot be dispatched: Message cannot be dispatched: Error Occured : Error in
conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
available.
if you need mu input payload please let me know
Please suggest me.
Thanks
Prem

Output Flatfile Conversion

Hi All,
I am doing Flatfile to Flatfile scenario.My input format is like ID,Name,Address.I want to get the output which should be same like Input format but through mapping.I am using J2SE file Adapter in both sending and receiving side.I am getting output in Flatfile but with only one field that is "ID".I am not getting the remaining fields i.e., Name and Address in my output flatfile.
My input structure from SXMB_MONI is
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_FCC1 xmlns:ns="namespace">
- <Recordset>
- <Data>
<ID>100</ID>
<Name>X</Name>
<Address>Y</Address>
</Data>
</Recordset>
</ns:MT_FCC1>
Content Conversion Parameters which i have specified at receiver side is
xml.recordsetStructure=Recordset,Data
xml.addHeaderLine=0
xml.fieldSeparator=,
xml.endSeparator='nl'
Can anyone suggest me what to do ASAP?
Thanks in Advance
Dinakar

Hi Dinakar,
U should use it like this
Recordset Structure :- Recordser,DATA
DATA.addHeaderLine=0
DATA.fieldSeparator=,
DATA.endSeparator='nl'
insted of
xml.addHeaderLine=0
xml.fieldSeparator=,
xml.endSeparator='nl'
chk this link
Re: file2file receiver side
Sachin
Message was edited by:
Sachin Dhingra

EDI 820 EDI to XML conversion error

Hi Experts,
We have configure EDI 820 Inbound Scenario in our system. The incoming EDI 820 file is not getting converted in XML from EDI. I try to convert it into XML in BIC Mapping Designer but it is displaying the below error message.
"Error:ID=2099;LEVEL=1] InhouseDocReader doSyntaxCheck(): offset[326]: the found segment
ENT is not in the message description.
DESCRIPTION: InhouseDocReader Error: The Segment
ENT is missing in the message description. Check your file."
Please find below the EDI file.
"ISA*00* *00* *12*123456789 *01*111122233 *140317*1432*U*00401*120000004*0*T*>~GS*PO*123456789*111122233*20140317*14315990*4*X*004010~ST*820*0001~BPR*I*264.9*C*CHK~REF*IA*6400900~REF*CK*7896883~DTM*097*20080811~N1*PE*COMPANY ABC~N3*21 PENN PLAZA*SUITE 909~N4*NEW YORK CITY*NY*10001~
ENT*1~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195112**137.33*137.33~REF*PO*008471856056~DTM*003*20080711~ENT*2~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195040**162.38*162.38~REF*PO*008471852792~DTM*003*20080711~ENT*3~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0194903**104.8*104.8~REF*PO*008471816334~DTM*003*20080711~ENT*4~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195039**137.33*137.33~REF*PO*008471846520~DTM*003*20080712~ENT*5~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*RV0047997934**-224.54*-224.54~REF*RZ*0004891~DTM*003*20080807~ENT*6~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*RV0084791384**-52.4*-52.4~REF*RZ*8471700434~DTM*003*20080807~SE*39*0001~GE*1*4~IEA*1*120000004~"
Can anyone let me know what could be error is?
Regards
Faisal

Dear Abdul,
I copied the file from your posting into a text-file and tried to convert it with my 820 BIC-Mapping.
I just had to make two modifications:
- add some spaces so that the Sender/Receiver fields in the ISA segement were 15 fields long
- remove a "space" before ENT*1, but this space might also just have been there because of how you posted the content into this posting.
After I had made this small changes the file could be translated perfectly fine with the mapping
See_E2X_ANSIX12_820_V4010
So it looks like eitehr your settings are not correct in the channel (e.g. a wrong mapping is used) or the file has been modified manually (with some additional blanks, CRLF, etc...)
Regards
Stefan

EDI TO IDOC Conversion

Hi,
I need to convert EDI 850 data into IDOC PO data at the same time, it has to be generate 997 automatically using seeburger.
Can anyone help me on this issue. with the steps.
I found some scenarios in Forums but those are not giving clear idea.
Plzz help me on this task.
Thanks,
Singh.

Do you have access to Seeburger documents available with the Seeburger installation CD? There you have a document called FunctionAcknowledgement explaining this scenario very clearly.
Regards,
Prateek

XI FlatFile conversion

Hi all,
i can convert very simple flat file to xml, but i don't know how set Content Conversion Parameters.
Example: I have file with content aaaaaaaaaa nothing else
Transport Protocol: NFS
Message Protocol: File Content Conversion
Document Name: DName
Document Namespace: http://AC_flatfile.cz
Document Offset: 0
Recordset Name: RSname
Recordset Namespace: http://AC_flatfile.cz
Recordset Structure: NameA,*
Recordset Sequence: Variable
Recordsets per Message: *
Key Field Name: *
Key Field Type: String (CI)
NameA.fieldFixedLengths: 10
NameA.fieldFixedType: char
NameA.fieldNames: NameA
... and file not processing and nothing information on SXMB_MONI.
Do you know why?
Have you some examples for set it?
Best regards, Pavel Korinek

HI Korinek,
First you have to make a data type in such a manner that you have field names that can hold your values from file.Foe eg if you are sending "aaaa" it must be some field..
The data type should be
<datatypename>
<RSname>
<NameA>
<field1>
<field2>
etc...
so the mandatory filecontent parameters will
NameA.fieldseperator
NameA.endseperator
NameA.fieldNames
NameA.keyFieldValue
This format should work.Your flat file was not getting picked up coz you have not mentioned the required format.
Also go through the link
http://help.sap.com/saphelp_erp2004/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/frameset.htm
Regards,
Rashmi

EDI to file conversion

Please tell me how to convert EDI to File format.

Hi Prasad,
Have a look at
Re: Seeburger Splitter adapter!!
regards
Piyush

Flatfile conversion with output file has a NAMING CONVENTION

Dear SAP experts,
I need some advise regarding my scenario.
I am converting a message into flatfile. (customized .csv)
But, the output .csv flatfile must have a naming convention.
E.g. Globus_20071020 (Customer name_YearMonthDate)
Can somebody give me ideas/inputs on what will I configure in File Receiver (FCC) in order to have an output file having a naming convention indicated above.
Or do i need additional configurations?
Please advise.
Thank you very much in advance.
Fred

Hi,
You could pass this kind of File name from mapping at runtime or
You could use the variable substitutions to create the fiel neame as per naming convention as adding date .
With reference to Variables youcould set file name as Globus_%payload.<Date>%
Pass the value in date field of payload
Refer
Variable Substitution
How to use Variable substituion
/people/sameer.shadab/blog/2005/09/23/an-interesting-usage-of-variable-substitution-in-xi
/people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
how to use attributes in variable substitution???:(
Dynamic file name
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i --> Dynamic File Name using XI 3.0 SP12 Part I
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii --> Dynamic file name(XSLT Mapping with Java Enhancement) using XI 3.0 SP12 Part -II
Dynamic File name in File adapter
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
1. In the sender file adapter , select Adapter Specific Attributes --> FileName.
2. Use the code in this link to read the filename inside a UDF in your mapping.
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(
http://sap.com/xi/XI/System/File,
FileName);
String filename = conf.get(key);
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
Thanks
Swarup

ANSI X12 meta data availability in conversion agent??

Hello,
Is there a provision for availability of ANSI X12 meta data in SAP conversion agent. We are trying to process EDI orders using the X12 INDUSTRY standard. Please advise.
-Kris

hi,
SAP Conversion Agent together with SAP Net Weaver, enables to automate complex integration activities for a multitude of data and document formats. These include unstructured and partially structured documents such as Office files, data streams, printing applications, and other application-specific formats.
Easily integrate unstructured and semi-structured data into SAP Net Weaver Process Integration using the Conversion Agent.
Conversion Agent dynamically converts unstructured messages from   Microsoft Word,Excel,PDF plain text.
Semi-structured formats such as HL7,SWIFT,HIPA, ANSI X12 and COBOL to   PI understandable SOAP XML.
          So that it helps to easily integrate the information need into the back-end systems. Conversion can also be used as the reverse process to convert from XML to unstructured or semi-structured formats
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sap%2bconversion%2bagent%2b-%2bthe%2blong%2bjourney
Conversion Agent - Handling EDI termination characters
Conversion Agent a Free Lunch?
Integrate SAP Conversion Agent by Itemfield with SAP XI
regards
sr

EDI using Seeburger BIC

Hi,
I am using the BIC module provided by Seeburger for EDI to XML conversion. The input EDI message is a 850 version 4010 message. I have configured the sender communication channel for Functional Acknowledgement and configured the message splitter which is working fine.
When I run this scenario for a few of the test files with a 850 4010 message, the classifier module does not recognise the EDI message as a 850 4010 message and hence the mapping(See_E2X_ANSIX12_850_V4010) is not called. There are no errors in the sender communication channel monitoring and I get only the functional acknowledgement message.
There is a warning message in the CC monitoring which says SEEBURGER/MSGSPLITTER: There is no attachment to split. So there is nothing to do
Am is missing anything here? If so could you please throw some light on this issue.
I have seen this thread Re: SEEBURGER/MSGSPLITTER: There is no attachment to split., but could not get much info.
Thanks,
Chandra

Hi Frederic,
I have configured the message splitter in the seeburger work bench and the split parameter has been set to true in the module configuration. As per my understanding, the 997 message will have a rejected status only if the EDI mapping is called, but this apparently never happens and my guess is that the 850 4010 message is not recognised by the classifier.
The setting works perfectly with one of my test files which is a 850 message as well, so the configuration is right. The situation described in my query occurs for a few 850 messages, since the test data is obtained from several partner systems.
Thanks,
Chandra

EDI to Flatfile Conversion

Similar Messages

Maybe you are looking for