EDI Conversion

Hi All,
We are using ANSX12 EDI Messages we are sending the message
using File Adapter but XI is not accept the EDI Format Directly.
So what we have to use for Conversion?
Is Module Program is the Solution?
Please provide me some solution for my Problem.
Gaurav

Hi Gaurav,
you would need EDI application adapter like SEEBURGER or Conversion Agent by Itemfield,with Conversion agent you convert the EDI structure to XSD and import that into XI as external definitions and do the mapping in the general scenario.
go through below links may be too many but some of them are very useful.
/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
Check this for Conversions-
/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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
regards,
Babu

Similar Messages

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

IDOC to EDI Conversion

Hi, I am New to EDI-IDocs,We have a requirement over here to send the iDocs from SAP to Non-SAP sys(JCAPS).
Need step-by-step details to convert the iDoc to EDI format.
Helpfull Answers will b Rewarded.
Regards
Giridhar Reddy

Hi,
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
u2022 Create a Customer Distribution Model (CDM);
u2022 Add appropriate message types and filters to the CDM;
u2022 Generate outbound partner profiles;
u2022 Distribute the CDM to the receiving systems; and
u2022 Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC u2013 Creating IDoc Type from Change Pointers
RSEOUT00 u2013 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Regards,
Shiva Kumar

IDOC-EDI Conversion usinf File content cpnversion

Hi all,
I need to convert an IDOC to EDI. I went through a few threads where I underrstood We dont need seeburger adapter for the same. It can also be done using File COntent Conversion. Can someone guide me with the steps.
Is it necessary to use seeburger adaps. Any related blogs would be helpful.
Regards,
Vinithra

Hi Vinithra,
--> refer the below link
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80b8db75-e481-2d10-7e94-81e1e29594e9?quicklink=index&overridelayout=true
the above may not explain exactly as per your requirement but gives some idea.
-->We can not use any custom adapter module for conversion of IDOC to EDI.For IDOC adaper module will be disabled.(as oer my knowledge)
Thanks

StrictXml2PlainBean - to have an XML - EDI conversion?

Dear Experts,
I'm experimenting with the EDIFACT XML --> EDIFACT conversion in XI. As we already know, there is no "out of the box" solution for it from SAP itslef. That's why we have to use a 3rd party solution for this conversion. (e.g. Seeburger, ACTIS, conversion agent,...)
But what about the StrictXml2PlainBean adapter module?
In this docu I read that it's good for XML to plain text conversions:
http://help.sap.com/saphelp_nw04/helpdata/en/44/748d595dab6fb5e10000000a155369/content.htm
Do you have any experience with this?
Is it OK for this kind of complex tasks or is it just an alternative for the File adapter's file content conversion funcionality?
Any comments/experiences are welcome!
Thank you in advance!
Andras

But what about the StrictXml2PlainBean adapter module?
>>>
this module is very similar to what we have as FCC in the file adapter. But for complex structure like EDIFACT, i dont think it can be of much use.

EDI conversion of external tax rate

Hi Gurus,
good day. please help on below.
why is it important to maintain external tax rate in OBCD when posting EDI invoice? Is this SAP standard? How does this work? Would greatly appreciate if you can provide docus for OBCD.
Thanks in advance.

Hi,
Tax type: Represents the tax Code of an externally assigned tax type. And to determine the SAP tax Code we are entering the entries in this T Code: OBCD, so that when ever a EDI document received into SAP with Tax Type XX and Tax rate xx%, there by system looks in this table and derives the Tax Code maintained in SAP.
And this relation is not maintained anywhere else. that's why we maintaining here.
Check this link
http://wiki.sdn.sap.com/wiki/display/PLM/Intercompanyresourcerelated+billing
Hope it is clear.
Regards
KK

Error in StrictXml2PlainBean (XML to Text Conversion)

Hi All,
I am trying to convert the XML to Plain file in receiver file adapter. I am using module - StrictXml2PlainBean.
Below is my target structure
B2B_HEADER (1..1)                    Level1
SHIPMENT_HEADER(1...1)          Level1
SHIPMENT_CUSTOMER (1..Unbounded)     Level1
   CARTON_HEADER     (1..Unbounded)         Level2 Child node of Shipment_customer
     CARTON_DETAIL (1..Unbounded)         Level3 Child node of Carton_header
I have mention below parameters in module tab,
                      B2B_Header.endSeparator             \n
     B2B_Header.fieldLengthExceeded     cut
     B2B_Header.fieldLengths     8,8,8,16,15,14,5,38,14,66,8
     Carton_Detail.endSeparator     \n
     Carton_Detail.fieldLengthExceeded     cut
     Carton_Detail.fieldLengths     6,14,4,10,14,10,35,10,6
     Carton_Header.endSeparator     \n
     Carton_Header.fieldLengthExceeded     cut
     Carton_Header.fieldLengths     6,20,20,12,2,7,2
     Shipment_Customer.endSeparator     \n
     Shipment_Customer.fieldLengthExceeded     cut
     Shipment_Customer.fieldLengths     6,8,10,40,40,40,40,40,10,2,15,40,1
     Shipment_Header.endSeparator     \n
     Shipment_Header.fieldLengthExceeded     cut
     Shipment_Header.fieldLengths     6,20,4,20,35,30,10,30,3,3,35,35,30,10,30,3,30,10,30,30,9,10,3,30,6,12,14,3
     recordTypes     B2B_Header,Shipment_Header,Shipment_Customer,Carton_Header,Carton_Detail
I have getting below error in communicatipon channel monitoring...
*Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: The element nesting level for the structure Shipment_Customer is too deep (reference: 3 levels, found: 4 levels) at XML element CreateAndAcknowledgePickPackShipmentGIS_Async_V01,Shipment_Customer,Carton_Header,RecordIndicator
RecordIndicator is a field in Carton_Header. Am i missing something in the configuration?
Regards
Amol
Edited by: AMOL BHARTI on Dec 24, 2010 8:59 AM

Hi Amol,
You XML structure contains deep levels. As far as i understand about the StrictXML2PlainBean module, this is not capable of handling deep structures.
This module is just an alternative to use FCC type functionality for other receiver adapters.
Please take a look at these links:
https://help.sap.com/saphelp_nwpi711/helpdata/EN/44/748d595dab6fb5e10000000a155369/content.htm
StrictXml2PlainBean - to have an XML - EDI conversion?
In case you want to achieve nested level content conversion, you may try this:
/people/karthiknarayan.kesavan2/blog/2007/08/22/file-content-conversion-for-multi-hierarchical-structure
I hope this helps.
Regards, Gaurav.

SAP Conversion Agent

Hi,
I have browsed the net for quite some time to get some idea about EDI message handling in XI using the SAP Conversion Agent (CA). I have understood what is CA all about. but i still have few questions unanswered.
1. How flexible or complex it is to use the the CA as compared to SEEBURGER ?
2. It is a must to use the EDI message parsing templates provided in the CA library ?
3. the cost factor. I have read that it is free for development and test landscapes. but for production landscape, we need to pay some license fee. Will this deprive us of any key functionality in the Dev and QUA landscape ?
I have gone throught the help document. Please help me find answers for the above questions.
Thanks,
Hari

Hi SreeHari,
Please refer to the link below,which might help you.
[SeeburgerVsConversion Agent |Re: Seeburger EDI conversion Vs XI Conversion Agent EDI conversion?;
Regards,
Madhu

How Can I transfer invoice details to customer through IDOC in EDI

Dear Sir,
I have some requirements That I want to Transfer Invoce To My Customer In EDI.so how can I do that .I have no Idea Plz Help Me and give the Details Steps with TCODES.

Hello Anil
There are not any transactions available. What you need to do is to convert your IDoc to the EDI message format of your customer (e.g. EDIFACT, TRADACOM, etc.). Usually the mapping process looks like:
SAP R/3 sends IDoc -> converted to IDoc-XML (e.g. by using SAP-XI) -> XSLT mapping to EDI-XML -> convert to EDI file using EDI converter
You may have a look at <a href="http://www.mendelson-e-c.com/">Mendelson (EDI conversion)</a>
Regards
Uwe

How to convert 864 Transaction code into XML in EDI to File Scenario

Hello Friends,
 Can any body help me out in using 864 Transaction Code (Tex Message) in EDI to Flat File Conversion?? I mean i am using just 2 Fields i.e Name and Address.I didnt understand the Format given..Here is the format for Name
N1 Name Pos: 040 Max: 1
 Heading - Optional
 Loop: N1 Elements: 4
To identify a party by type of organization, name, and code
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N101 98 Entity Identifier Code M ID 2/3 Must use
Description: Code identifying an organizational entity, a physical
location, property or an individual
All valid standard codes are used.
N102 93 Name C AN 1/60 Used
Description: Free-form name
N103 66 Identification Code Qualifier C ID 1/2 Used
Description: Code designating the system/method of code structure used
for Identification Code (67)
All valid standard codes are used.
N104 67 Identification Code C AN 2/80 Used
Description: Code identifying a party or other code
Syntax:
1. N102 R0203 -- At least one of N102 or N103 is required.
2. N103 P0304 -- If either N103 or N104 are present, then the others are required.
Comments:
1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104)
must provide a key to the table maintained by the transaction processing party.
2. N105 and N106 further define the type of entity in N101.
[b]
Here is the format for Address
N3 Address Information Pos: 060 Max: 2
 Heading - Optional
 Loop: N1 Elements: 2
To specify the location of the named party
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N301 166 Address Information M AN 1/55 Must use
Description: Address information
N302 166 Address Information
Description: Address information O AN 1/55 Used
So Help me hoe to convert this into XML...

try this
For EDI U need SEEBURGER Adapter or Conversion agent by itemfield.
Using Conversion agent convert EDI Into XSD and Import using External definition.
Have look
EDI Conversion
Re: Seeburger Splitter adapter!!
Thanks

Design approach help : BIC Mapping Tool Conversion

Hi All,
Design approach:
we know that BIC mapping tool can be used for EDI to XML conversion. also i know that its a Any to any converter.
But we prefer EDI to EDI XML conversion only via this tool and do the mapping in SAP PI as it would be easy to do mapping change if any in PI than redeploy the mapping in module location every time.
My question is:
we know that sender file adapter supports FCC for max of 3 hierarchy levels.
Can we make it a practice of accepting requirements in SAP PI which has complex Flat file structure (more than 3 levels). and use BIC mapping tool to convert the Complex flat file Structure (with more than 3 levels) into PI required format and proceed with the mapping and Configuration. (Note: hear the assumption is that the organisation has BIC Mapping tool procured for some EDI message scenario's ).
or is it best practice to ask the Source system to supply flat files strictly in Header,with 1 line item format?
Suggestions would be deeply appreciated.
Warm Regards,
Senthilprakash

>
> if you are thinking of using only BIC mapping tool for converting flat file to xml and want to proceed with normal configuration without using BIC modules then it is not feasible.
>
Dear Suresh,
I am very well aware of that. we have Seeburger SFTP adapter installed in our PI system. and for EDI conversion we use BIC for converting to XML and deploy the module in the adapter level.
Now my question is that: weather is it the rite way to start accepting requirement from source which has complex flat file structure (non edi messages) and using BIC module in adapter to convert it into XML and proceed with configuration or better to ask the source system to send the flat file in a format which is accepted by our file adater FCC.
what are the drawbacks/bottlenecks we see in using BIC module for converting non EDI complex flat files into XML format? in PI
Regards,
Senthilprakash.

AS2 Adapter EDI scenario - question

I am working on a EDI scenario, involving AS2 adapter.
Could anyone tell me any steps to be done on ABAP engine.
reg

Hi Naveen,
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.
steps in IR and ID.
In IR:
You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.
In ID:
This is the scenario for AS2
Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.
Example of mapping:
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
1) After deploying mapping program.
We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
1)The value of the Agency field must be Seeburger.
2)The value of the Schema field must be AS2ID.
Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab
Configuration in adapter:
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
You can refer my thread reply:
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.
EDI-SEEberger-XI-IDOc-R/3
flow of the data from EDi to SAp r/3 using seeburger:
1) Data will be coming thorugh WAN or mailbox.
2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.
3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.
4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.
5) Once you XML is generated then it will be used in MM
6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.
Thnx
Chirag

IDOC to EDI

Hi all,
I am working on Idoc to EDI ANSI X12 Invoice 810 scenario, I created a receiver communication channel with File adapter and included those modules. But I am not sure is there any other additional module parameter that needs to be specified other than the once that are mentioned below.
Processing sequence:
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
and
Module configuration:
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName See_X2E_ANSIX12_810_V4010.
I am getting the following error in receiver communication channel,
"Message processing failed. Cause: java.lang.Exception: Cannot cast to XI message. Reason: BIC module error: Message which was recieved from module processor was null"
But the file in getting generated in the target directory as an xml file, actually the file has to be in EDI format.
Please let me know whether the module is not properly configured or the File adapter does not handle the IDOC to EDI conversion eventhough the module used does the conversion.
Regards,
Nithiyanandam

Hi,
Seeburger tool will not fail to conver the data into file format,they all are already predefined mappings and ANSI X12 is a common mapping used by most of the users and the module parameters which u have specified i dont find any thing more u have to give.
Check ur mapping which u have done and also check all the setting onces
any way iam giving some links on Seeburger check them.
/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
Check this for Conversions-
/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
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
Regards,
phani
Reward points if Helpful

Without using Seeburger Adapter can we convert EDI 864 TC to XML

Hello Friends,
Can we convert 864 Transaction code (Text Message) to XML with out an External adapter like Seeburger Adapter? I mean can we write a code in JAVA for conversion? If so, what should i use in that Java code?

Hi
These blog can help u....
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/srinivas.vanamala2/blog/2006/12/11/edi-basics
Already discussed thread:
EDI Conversion
Re: Seeburger Splitter adapter!!
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

Conversion Agent Serializer

Hi All,
I am doing an IDOC to EDI File scenario, and EDI Conversion using Conversion agent. I have designed the Serializer from the standard library in Conversion agent studio. I need to to add the Line wrap for the output EDI file. How can i do this in Conversion agent studio?
Suman

http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/90bf7c8d-a197-2b10-96b9-a0feb39b5ddb [original link is broken]

EDI Conversion

Similar Messages

Maybe you are looking for