Mapping EDI to IDoc

hi all
I need some good links for the entire mapping process from EDI to the SAP IDoc fromat.
Please send me some good links or docs.This is a rather urgent requirement.

Hi,
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
FOR EDI SUBSYSTEMS:
http://www.erpgenie.com/sapedi/edi_subsystems.htm
Look at the below link, it wil have a link for a PDF file which is having all the SUBSYSTEMS used in SAP
SAP - EDI Subsystems (CA-EDI) [original link is broken]
reward points if useful
regards
Anji

Similar Messages

Mapping EDI 820 (remittance advice) to IDOC

Hi,
Can anyone give me the steps required to do a mapping of EDI 820 (Remittance advice) to IDOC? If you have the mapping already, can you send that to me at garapatic at yahoo.com

Hi Greetson,
    Before I posted information on this forum, I checked the web to see if I can look at any helpful stuff for this mapping and I could not find any.
   I tried to look for EDI EDIFACT stuff on the website for my mapping EDI vendor(Biztalk) and could not find any.
   Can you point me to specific websites which will be helpful to me? Or to any mapping document.
Thanks,
Nile

EDI to IDOC mapping with MII

Hi,
is it possible to map edi document to IDOC with MII?
Thanks.

Currently there is example available.
In the thread [can MII read edifact|Re: can MII read edifact?; Jeremy mentioned an idea which may be interesting for you. Have a look at the following Wikipedia article about [XML/EDIFACT|http://en.wikipedia.org/wiki/XML/EDIFACT]. Use case 1 proposes to use a converter build a XML file from the original Edifact message. Then you can process that XML with MII.
Maybe this helps.
Michael

Map EDI messages to SAP iDocs

Hi all,
Is is possible to map EDI messages to SAP iDocs using Oracle Integration?
Thanks

Yes, OracleAS Integration has several components. One is called Integration B2B, which allow you to send and receive EDI messages. You can then pass this on either using Integration InterConnect or BPEL Process Manager to the SAP adapter which can talk to SAP systems using e.g. iDocs.

Seeburger EDI to IDoc

Hi,
The actual payload is not getting generated in the EDI to IDoc scenario.
The acknowledgment is getting generated.
What could be the possible error?

Anu,
is your mapping determined automatically or are you explicitly stating the mapping name in your
module configuration?
If you set mappingName to Auto BIC tries determine the correct mapping by looking at the
the UNH segments, e.g. UNH1ORDERS:D:97A:AA'. If your mapping has been labeled
differently in the Mapping Designer, for instance E2X_ORDERS_UN_D97A the system
won't be able to find the mapping and therefore you won't get any payload.
As I suggested before try using the parameter u2018logAttIDu2019 Value u2018ConverterLogu2019 in your
module chain that will most likely tell you what the problem is.
Sven
Edited by: Sven Buttler on Jul 9, 2010 10:26 AM

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

Help on EDI to IDOC scenario using seeburger

Hi,
Anyone plzz explain me edi 850 to idoc orders05 scenario. at the same time how generated idoc will creat salesorder.
Thanks,
Seenu.

Hi,
You can see some basics about this integration in this blog:
/people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
You need to get the 850 xsd and import it in IR. Then map your xsd to order05 idoc. Then to test first seeburger adapters need to be deployed. Now you need to configure your classifier and then the splitter if you have multiple 850s within one transmission. Then finally the BIC module to convert edi to xml. Then once you have your xml you need to do your message mapping with the idoc and send to sap.
Once you install the seeburger adapters in your landscape you will have the documents for each of these ones. Go through them and configure.
Regards,
---Satish

Regarding EDI----XI----IDOC

Hi All,
I have One Requirement here is that
My Client's Customer will send EDI Formated Data (ANSI Type ) to Client. That Data has to be Posted into SAP R/3 Database. So here We are Using XI For that .
Can Any One Explain me what could be the Scenario here And
How to Handle this ANSI Data Format.
Regards
Babu

Hi
Scenario is EDI-XI-IDOC
Data Will come in the Form of ANSI
1) I Will Use IDOC Adapter in the Receiver End
2) For Sender Side Which Adapter I Need to Use & How to do the Conversion From ANSI Format to XML ??????
Can You Provide Any Real time Scenario Or Any thing Which meets this Requirement.
I am Still in Confusion How this ANSI Data Will be Converted into XML Either it Can Happen in Seburger Adapter OR in XI Also
Can You Expalin me How this Conversion in Detailed
>>>>>>>>>>>>>>>>
if you are getting the data in the format like ANSI then you have to first create the XML message with the help of the BIC mapper.
the BIC mapper is basically used to convert the EDI message into the XML message. to convert the EDI message into XML message ypu have to create the mapping using the option createE2xmapping in the BIC mapper.
the mapping that will be generated using the BIC mapper have to be deployed on the server.
and in the adapter you have to used the same mapping name that you have deploy on the XI server in the module tab of the adapter.
if you still face the problem please reply me back.
Thanks
Rinku

Mapping issue in idoc to JDBC scenario

mapping issue in idoc to JDBC scenario
source structure
E1KNB1M
BUKRS = 1000
E1KNB1M
BUKRS= 9000
E1KNB1M
BUKRS= 2000
THE NODE E1KNB1M is repeated many times and the field BUKRS is also repeated with E1KNB1M as above
TARGET field : ISFRANCHISE
if any where value of BUKRS =9000 we have to pass Y to the target filed, else N
if BUKRS = 9000   THEN ISFRANCHISE= Y
               ELSE
            ISFRANCHISE=N
I've done the mapping as below
BUKRS = 9000--> IF THEN Y ELSE N--
> ISFRANCHISE
BUT everry time the target value is N only
pl suggest
rgds
mojib

mapped like this
BUKRS--->SORT---->
                                             EQUALS --------IF---THEN    Y
9000------------------------>                                               ----------------->ISFRANCHISE
                                                              ELSE   N
context of BUKRS set to parent node
its worked
thanks to all for valuable suggestions
rgds
mojib

Mapping to an IDOC using an externally created XSL file

I want to map a message to an IDoc using an ABAP XSLT transform. I am creating the XSLT in an external tool.
I need to use an XSD definition of the IDOC as the target document of the mapping. I can get that in two ways:
1) Get the XSD definition of the IDOC from transaction WE60 and use the menu command 'Documentation -> XML Schema'
2) In the Integration Repository, export the XSD of the imported IDOC.
The problem is, there are significant syntax differences between these versions, and I don't know which is the correct version. For instance, the XSD exported from the Integration Repository has a mandatory attribute 'SEGMENT' for each segment that must be filled to create a valid XML message; this is not the case when the XSD definition is created in WE60.
Can somebody advise which is the correct version to use?

Hi Anthony,
This is really strange...
In both case XSD should be same...can you please tell for which idoc you are generating xsd?
Eventhough if you generate XML Schema using WE60, mandatory attribute 'SEGMENT' for each segment has to be there....this validation would be done while posting idoc. It will check for all mandatory fields.
I have some different thoughts that what wojciech has suggested...
"If were your shoes I would use xsd from integration repository because that's the expected result...."
But final goal is not to achieve mapping but posting idoc with proper data in R/3 system successfully.
Your second question..
"Do I assume then that placing a constant value of 1 in the SEGMENT attribute is just to satisfy the validation of the XML message against the XSD:..?
ummm...I think if you assign constant "1" to segment it will generate that segment while creating idoc. Its mandatory to assign constant value to segment which you want to generate...
"Can I assume that the IDoc adapter will fill the SEGMENT attribute with the correct value?.."
I dont think so Idoc adapter will fill this attribute automatically...you need to assign constant to field segment.
Nilesh

Mandatory fields for mapping in ORDERS idoc.

Hi
I m working on File to idoc scenario for creation of sales order in ECC 6.0 , now I want to know what are the mandatory fields in ORDERS idoc which needs to be populated or else disbaled so that the sales order gets created properly in the ECC 6.0..
Pl let me know the method of finding mandatory field for mapping for any idoc and which fileds of idoc are to be disabled.
Pl help ..
ans will be rewarded .
thanks & rgds
mojib

HI,
U can disable the control record segment and in the IDOC adapter use the option apply control record from payload.
If you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the following fields are filled from the IDoc-XML payload:
·        MESCOD
·        MESCFT
·        TEST
·        EXPRSS
·        STD
·        STDVRS
·        STDMES
·        SNDSAD
·        SNDLAD
·        RCVSAD
·        RCVLAD
·        REFINT
·        REFGRP
·        REFMES
·        STATUS
·        DIRECT
·        OUTMOD
·        CREDAT
·        CRETIM
read the information in below link:
http://help.sap.com/saphelp_nw70/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm
thnx,
chirag

Mapping issue: FCC: Idoc for each record in file

Hi,
I have file to Idoc scenario.
I receive csv file with multiple records.
The requirement is to create an Idoc for each record.
For eg.
source file
A1,B1,C1
A2,B2,C2
A3,B3,C3
After FCC
<MT>
<TRANS>
<ROW>
<A>A1</A>
B1
<C>C1</C>
</ROW>
<ROW>
<A>A2</A>
B2
<C>C2</C>
</ROW>
<ROW>
<A>A3</A>
B3
<C>C3</C>
</ROW>
</TRANS>
<MT>
I have first tested it with only 1 record to test end to end connectivity. It works as expected and Idoc is posted to target system.
Now when I am trying to send multiple records, I am getting some issues.
Below are the steps that I have taken to process multiple records:
1. Changed the cardinality of ROW (child of RecordSet) from 1 to Unbounded.
2. Changed the occurance of Idoc to Unbounded.
3. Mapped ROW to Idoc root.
I have tested the mapping in IR and it generates multiple IDOCs.
When I send the test file, it fails with error Tag found instead of tag IDOC BEGIN=
I can see the xml message created with multiple ROWs in XI by File adapter in sxmb_moni.
When I do Test Configuration in ID, with the XML message extracted from sxmbmoni, the result that I got was:_
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1></ns0:Message1></ns0:Messages>
This means that idoc was not created while mapping.
But the same sample message works OK in IR!
Pls help where I have missed.
Regards,
Anirudh.

Sudhir,
Thanks for your response.
FCC is working fine. I have taken the XML message in XI created after FCC from csv sample message.
I have tested this message in IR by placing it between
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
</ns0:Message1>
</ns0:Message>
It is working fine and Idocs are created in mapping in IR.
But the same sample message is creating below output ID!
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1></ns0:Message1></ns0:Messages>
Regards,
Anirudh.

In EDI to IDOC or Idoc to EDI can we go for Dynamic recevier determination

Hi all
I am doing an EDI to IDOC scenario involving SEEBURGER( AS2) adapter .can we go for extended receiver determination
Regars
Saurabh

Saurabh,
You can not use Extended Receiver Determination coz AS2 connection is like point-to-point connection which requires AS2 id of both sender and receiver. Therefore you can not use the Extended receiver determination.
Reagrds,
Sarvesh

Mapping shipment 05 idoc

hi experts,
we have a scenario to map shipment 05 idoc to delivery 05 idoc. there will be one or more handling units in source idoc.for every handling unit in shipment 05 we should map respective article information to seperate delivery 05 idoc. this means foe every e1edl37 segement in source idoc we need to create seperate delivery05 . but the occurence of the imported delivery 05 idoc is 1. so how to map this.. do we need to go for bpm. can anyone please suggest.

Hi,
1)Double Click on the imported IDOC
2)Export the WSDL file to your desktop.
3)Change the max occurrence of the IDOC Segment.
e.g.
Original
<xsd:element name="IDOC" type="CAP_PRIMCOST.CAP_PRIMCOST01" />
Change
<xsd:element name="IDOC" type="CAP_PRIMCOST.CAP_PRIMCOST01" minOccurs="0" maxOccurs="999999999" />
4)Import the new WSDL as an external definition and use it insted of IDOC.
Regards,
Himanshu
Edited by: Himanshu Mohan on Oct 7, 2008 1:55 PM

ALE, EDI and IDOCS

Hi
I am learning some stuff on ALE,EDI and IDOCS... are there any good sites which gives clear step by step procedure for the above.
Thanks in Advance.
Sudhi

Hi Sudhi
You can find details on SAP courses from your country's sap.com site. You can find links from http://www.sap.com/contactsap/countries/index.aspx .
Also some Education Partners of SAP give courses. Some info about these will also be there...
Regards...
*--Serdar

Mapping EDI to IDoc

Similar Messages

Maybe you are looking for