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

Similar Messages

SAP CONVERSION AGENT - XPATH not found in DATA HOLDER?

Hi Eperts,
I'm trying to work on this Tool, getting some problem in Conversion Agent Studio..
I Had created my project with PARSER in Conversion Agent, source file will be Pipeline separated Text File , which has multile rows...And I had created XSD for my Message Interface in XI..
When i'm defining my ANCHORS/MARKERS/CONTENT/ .
getting error in DATA Holder, I'm not able see my Schema / XPATH in the respective namespace...
Could anyone can guide me pl.
Thanks in Advance..
regards,
vasantj.

Hi vasantj,
Did you manage to resolve this issue?
I face the same problem.
Please ellaorate.
Nimrod.G

Meta-data conversion

Is there any info on when a tool will be available to convert kodo 3
jdo/mapping files to JDO 2 meta-data files?
thanks,
Clive

Is there any info on when a tool will be available to convert kodo 3
jdo/mapping files to JDO 2 meta-data files?You should be able to convert files using the mappingtool's built-in
export/import capabilities. Something like this:
<with MappingFactory set to kodo3 value:>
mappingtool -a export -m true -f export.jdo2 package.jdo
<change MappingFactory to kodo4 value, then:>
mappingtool -a import -m true export.jdo2
Check the docs on the mappingtool for exact options.

Soap Adapter meta data is not available in XI3.0

Hi,
We are not getting SOAP Adapter meta data in Integration Builder. Inspite of that we have imported package as the XI content for Software version SAP Basis 6.4 (XI3_0_SAP_BASIS_6.40_00_00.tpz).
When we configuring one of our business scenario using SOAP Adapter. Integration Builder (Configuration), In Communication channel, Adapter type SOAP is not appearing.
Any idea on this?
System:
XI 3.0, SP 10, OS: WINDOWS 2000
Regards,
Rohit Goyal

Pl check in the back end table at R3 side whether there is any records there or not and check with the functional team that they have entered data.
If data is there then initialize the set up tables and then check in RSA3
Thanks
Shivani

Seeburger EDI conversion Vs XI Conversion Agent EDI conversion?

We have implemented Seeburger's EDI solution at a client, and our another client wants to an EDI solution for them.
I cam across this weblog, and it is very interesting. I have some questions.
1. Does Converstion Agent support the converstion of all versions of native EDI X12 and EDIFACT to the corresponding XML verions, and vice versa.
2. What are the differences between Seeburger's and XI Conversion Agent's EDI soultions?
Your feedback would be greatly appreciated.
Thanks a lot.
Karma

Hi Karma,
SAP Conversion Agent by Itemfield is a data conversion system that enables you to create interfaces between any data formats and XML-based systems. The Conversion Agent can convert unstructured, semi-structured, and structured formats to XML, and the other way around.
Have a look at these links:
/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
Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.
For more i would suggest you to go through these links:
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
Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
3. create a one to one mapping between input en output.
4. export the metadata in xsd or sda format for import in XI.
5. generate an SDA which can be deployed in XI and used as a module.
Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
There are also a few ways to use EDI with the ALE system of R3.
inbound EDI to R3
1.use a 3rd party adapter for the EDI protocol(eg.SEEBURDER) from the EDI system,send the produced XML to the XI ,map the xml message to a matching IDoc using the IDoc adapter.
outbound ALE message from R3 to EDI system
1. Configure the ALE system to point to the XI the relevant IDoc (SM59,WE21,WE20...)
2.use a file adapter3rd party EDI adapter and map the fields to the target structure.
have a look at this example:
http://www.ean.se/EANCOM%202000/iftmin/example.htm
Details on how to configure can be found on SDN
I hope this helps....
Regards,
Abhy

Conversion Agent ?

Hi experts,
Our scenario is EDI-X12 data to XI to R/3 (both side)
For Converison Purpose,
We want to use Conversion Agent by Itemfield, but there are some other options also in the market like Seeburger and Iway adapters.
We have approx 50-60 EDI Scenarios.
Now, we want to justify that why we are using Conversion Agent not other adapters ?
Please help us ?
Regards,
Study SAP

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

Conversion Agent - (EDI - XI - IDOC) - Help

Hi Experts,
I am working on the scenario (EDI - XI - IDOC) using Conversion Agent for Converting EDI data into XML.
I am facing many problems in Real Time, can any one who has already worked on the same scenario send me complete scenario with screen shots,
I need immediate help, really it is very urgent for me.
Regards,
Study SAP

Hi Kishore,
Thanks for your reply, We are using Standard IDOC Orders05 and EDI message ANSI X12 - Message Type 850 for Purchase Order.
Posting EDI Data of Purchase Order in R/3 Sales Order as INBOUND Message.
Using Conversion Agent Parser for the same and deployed this project at Integration Server in ServiceDB Directory.
The Conversion Module CMTransformBean is also deployed at XI Server.
When we are puting file at FTP Server, our XI System is not picking up file while using Conversion Agent Module,
while it is picking up without conversion module successfully.
Please help,
Regards,
Study SAP
[email protected]

IDOC - XI - ANSI X12

Hi
I am working on a scenario iDOC - XI - ANSI X12.I am following the best practices guide provided by SAP .I am using conversion agent to convert the idoc to Ansi X12 format .For that I have created a serializer and deployed that on DBservice folder of the XI server .But after configuring the file adapter with module parameter I am getting runtime errors ." Could not parse Channel " and " Could not parse Outbinding with Objectid:".I found this errors in RWB cache monitoring .Can any one provide me some document for this scenario specific to the setting for conversion agent service in file adapter?
Thanks
-Alok

Hi
Have a look
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/da1e7c16-0c01-0010-278a-eaed5eae5a5f
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1e545914-0b01-0010-5a9d-c52a4bffdbab
http://help.sap.com/saphelp_nw04/helpdata/en/de/a4415b8634ba49b0f62a75dc415adc/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5c/895738d1884d50e10000009b38f842/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/6f1f39a08e6fcae10000000a1553f6/CMSUserGd.pdf
Replacing EDI subsystem with SAP XI
/people/lionel.biennier/blog/2006/07/21/sap-xi-supports-edi-x12
XI with EDI Format
Thanks

IDOC Types and their equivalent messages in EDIFACT and ANSI X12

Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
Regards,

Hi,
Please check these perhaps they may help.
Mapping ANSI X12 to SAP Message Type and IDoc Type:
204 Motor carrier shipment information
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880), EDI - Inbound INVOIC posting configuration
The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is DELFOR01.
832 Price catalog (also 879, 888, 889)
The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04. Outbound processing is supported.
850 Purchase order or order (also 875)
The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
The logical message is PROACT, the IDoc type PROACT01.
855 Ordering or order response (also 865)
The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
For delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
860 Ordering or order modification (also 876)
The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
The logical message is GSVERF, the IDoc type GSVERF01.
862 delivery schedule (FAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is DELFOR01.
864 Text message
The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional Acknowledgment
This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
"22" Shipping OK, acknowledgment has yet to come
"16" Functional Acknowledgment positive
"17" Functional Acknowledgment negative
The status values "14" and "15" are available for the Interchange Acknowledgment accordingly.
Regards,
Ferry Lianto

Conversion Agent (license)

Hi all,
Does the Conversion Agent still need a seperat license?
And if so what are the costs?
Thank You
Regards, Thomas

Hi!
There are also other conversion adapter modules available for SAP XI.
We offer for example a SAP certificated EDI conversion module for 9990,- Euro and it is not limited in data transfer volume.
Thanks,
Leo
mendelson-e-commerce GmbH
http://www.mendelson-e-c.com/

CONVERSION AGENT 4.0

Hi All!
I'm new on this tool, and I need to convert a X12 v2003 message (Message 830 - Planning schedule with release capability) to an IDoc.
I didn't find this version of X12 message (version 2003) on the library that is installed with the CA. Is there any place that I can download this version? Or do I need to develop this by myself?
Tks.

H,
Check Below Links....
http://help.sap.com/saphelp_nw04/helpdata/en/43/6d95e0ac846fcbe10000000a1553f6/CMGetStart.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/content.htm
/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
/people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
/people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
All you need to know about conversion agaent can be found here:
https://websmp102.sap-ag.de/~sapdownload/011000358700001090982006E/ConvAgentDocSP16.zip
https://websmp102.sap-ag.de/~sapdownload/011000358700004921152005E/ConversionAgent.pdf
/people/sap.user72/blog/2005/07/27/xi-generate-pdf-file-out-of-file-adapter
/people/sap.user72/blog/2005/07/31/xi-read-data-from-pdf-file-in-sender-adapter
/people/alessandro.guarneri/blog/2007/02/21/sap-xi-acting-as-a-huge-file-mover
Regards,
Phani
Reward Points if Helpful

Conversion Agent - EDI Parser Problem

Hi Experts,
We are writing a parser for EDI message type 850.
When we are giving Repeating Group and Marker "ST", it is taking more fields also, having this value "ST", which are in other Segments other then ST.
and reading that ST fields as a segment,
the output data is not correct due to this problem,
Please help,
Regards,
Study SAP

Hi VJ,
thanks for your reply,
We are writing this Parser at Conversion Agent for EDI 850 & 856, X12 Version 4030.
The example file for the problem is here :
ST/856/00001~
BSN/00/013721/20070806/1808/0001~
HL/1//S~
TD1/CTN25/17////G/198/LB~
TD5//2/HRMN/M/HERMANN TRUCKIN~
REF/BM/67450800000020664~
REF/CN/125173569~
REF/PUA/125173569~
PER/IC/dan/EM/[email protected]~
DTM/011/20070806/1807~
N1/ST//92/93922~
ST is a segment, when we are going to give this as Marker in Repeating Group, it is picking ST of N1 Segment also.
'/' is seperator for fields and '~' is seperator for lines.
Regards,
Study SAP

Seeburger BIC vs Informatica Conversion Agent

Hi Experts,
I am hoping I can seek some feedback on the above mentioned subject. I am going through an implementation currently which involves EDIFACT and X12 - various message types e.g. Orders, Desadv, Invoice, Order Confirmation and a few more.
As part of the implementation we need to choose a tool to do EDI to XML conversion which can also do EDIFACT/X12 validations (syntax & semantic) plus a functional Acknowledgment.
The two final options we have chosen are Informatica's Conversion Agent and Seeburger BIC (given we are using Seeburger FTP adapter for communication already).
Now to make a final decision I was hoping if some people can share their experience (s) and give some pro's and con's for choosing one or the other please?
Any comments will be highly appreciated.
regards

Hi mimranacc,
I was hoping if someone can comment on Conversion Agent as well or if there is a white paper on the comparison of the two?
I have extensively worked on Conversion Agent. My experience has been real good with this tool. It is quite handy and easy to use.
Apart from unstructured messages from MS Word, PDF, Excel, PowerPoint etc, Conversion Agent can manage semi-structured formats like EDI, HL7, ANSI X12, COBOL and HIPA.
It consists of set of libraries that are deployed on PI's J2EE server and is accessed by AE during runtime.
The +ve points are -
1. Very easy to install and use,
2. Easily integrated with SAP PI,
3. No additional adapter required for transformation to / from XML,
4. No extra adapters installed on PI server, which enhances the performance,
5. Monitor Conversion Agent messages in Integration Server.
Unfortunately, I haven't worked with Seeburger BIC, so can't provide you a comparison.
Hope this helps.
Regards,
Neetesh

How to download SAP Conversion Agent 7.1 by Informatica

Hi Gurus,
I tried to download SAP Conversion Agent 7.1 by Informatica from following location
Sap Software Download Center---->Browse Our Download Catalog----->Installations and Upgrades----->Adapters----->Informatica----->SAP CA For SAP Netweaver 7.1
but its showing No data available. Can anybody help me how to get this conversion agent.

Well, I see it like this and everything work for me:
Are you logged in with your S-user account? Also I think you have to be authorized for downloading the software. Can you check under your profile, if you have some authorizations?

How to extract meta data of documents from SAP R/3

dear all,
i`am working in aproject where we connect the documents for SAP R/3 applications.we maintain our own repository for that purpose.it may be in bound or out bound according to customer needs.the meata data related to the documents is stored in SAP.our requirement now is to have that metadata available in our repository .can any one guide me how to write ABAP code for extracting meata data from SAP and enable even nonSAP users to have the access for the documents.
thanks in advance
ravi

Hi,
One way to do this is probably set a connection between SAP Database and an external database and store the meta data into external database from where a non-sap user will have an eccess to the data.
Steps required are :
1. we have to involve basis team also in that.
2. they will make one entry
in DBCON table
(that entry will point to secondary database/external database)
(suppose the name of this secondary connection is HRCON)
3. Also they will make connection string
in application server.
4. After that,
we should have
the table definition in SAP dd dictionary
and also
the same defintion
in the external database.
5. now in abap code,
we have to use like this.
DATA: mydbcon(30) TYPE c.
mydbcon = 'HRCON'.
INSERT ydev_msg_cur CONNECTION (mydbcon)
FROM msg_cur .
<b>Hope this helps.
Please mark helpful answer.</b>
Regards,
Amit Mishra

ANSI X12 meta data availability in conversion agent??

Similar Messages

Maybe you are looking for