EDI and mapping specification

Hi SAP expertise,
I had test the EDI connection between my company SAP system with another simulated client SAP system and is wokring fine.
Now i need to prepare the mapping specification. any idea how to proceed ?
i never do EDI before...need your helps here
Thanks your helps !

Hello
If you are talking about "EDI" between SAP systems you probably want to connect the two SAP systems via ALE. In this case the message format would be IDoc.
Example: You have a distribution company (A) which sells products of the production company (B). (A) sends purchase order IDocs (ORDERS05) to (B). (B) processes these IDocs and creates sales orders in its SAP system.
If this is you scenario you need to do the required ALE / IDoc customizing (WE21 = ports, WE20 = partner profiles, BD64 = distribution models). If there are changes required between the ORDERS05 IDoc sent and the ORDERS05 IDoc received you may need to activate user-exits in IDoc processing (e.g. function group XVED).
Alternatively, if you connect the two SAP systems via SAP-XI you can do the mapping on SAP-XI.
Regards
Uwe

Similar Messages

EDI Idoc Mapping For Apparel and footwear Solutions (AFS)

Hello Gurus
I am trying to map Orders sent thru EDI using message type Orders and Idoc type /AFS/ORDERS06 and process code J3AA.
I am running into problems like no item category could be found and other errors which stops me proceeding further. I have worked with after market EDI and when I use message Orders and Orders 05 Idoc. I do not run inot these issues.
Is there any specific doumentationavailable for processing AFS EDI?. Any help would be appreciated and points will be awarded.
Thanks a lot for your help in advance.
Sunny

hi,
If you want to make huge volume of updation then you should go for idoc.
otherwise you go for Bapi call from xi or RFC.
regards,
ujjwal kumar

IDOC to EDI Seeburger Mapping Issue

Hi,
I am new to seeburger, Currently I am working on PAYEXT IDOC to EDI scenario using seeburger adapter.
As per my little knowledge i can understand that i need two step mapping:
1) IDOC XML to EDI XML
2) EDI XML to EDI
Now the problem is how can i do 1st mapping if i have to do 1:1 mapping in PI mapper than it will be a tedious task as I dont know which idoc field is mapped to which EDI XML field.
Also i dont know how i can map the 2nd mapping.
when we installed seeburger adapter than i got three files from basis guys related to PAYEXT
msg_PAYEXT_UN_D96A.xml
msg_XML_PAYEXT_UN_D96A.xml
XML_PAYEXT_UN_D96A.xsd
Note: I imported .xsd file in IR, but i dont know what to do with these xml files.
Please experts reply soon as it is delaying my project
Regards,
Shradha

Shradha,
You can check the seeburger software component versions where all the mappings would be provided by Seeburger as part of the package.
You can have a look whether PAYEXT is there and would be useful
To start with
1. You need a functional or EDI Business analyst to guide you on the various mapping specifications needed.
2. You should also liase with your business partners to prepare an business rules and other conditions.
3.Also decide whether you are going to deliver it via AS2 communication or via VAN
4. Accordingly you need to configure the seeburger adapters.
5.The mappings provided to you are from XML to EDI and EDI to XML which is a second stage automatically done by seeburger once you specify the module steps in the comms channel.
I am afraid that without knowing business rules or mapping specifications, you can't work on EDI.
Regards
Krish

SAP to 3rd party: EDI and XI: Needed advantages and disadvantages

HI All,
I have a requirement to sent PO data from SAP to 3rd party Vendors.(more than 30 vendors). Client insists on using EDI.!!
I have completed the config on SAP R/3 side and IDOCS are created in SAP R/3.
Since we have XI in the landscape, I have a few questions in my mind. Appreciate if you could give you feedback on these questions:
1. Should we send data directly from SAP to 3rd party using EDI adapter and avoid XI.
2. I assume EDI adapter will automatically convert IDOC to vendor format data and vice-versa.
3. All 30+ vendors will need to access this EDI adapter system or do they all need to have a separate one installed in there landscape.
4. If we use XI, will the adapter be able to communicate to XI. If yes what is the adapter name which connects to XI.
5. All vendors need this data in a slightly different format, so will the EDI adapter do the format conversion for every vendor ?
6. Since all vendors have a diff file format needed, I want to avoid doing extensive message mapping in XI. So can the EDI adapter handle it or is ther any easy way to do this mapping.
7. If mapping is not possible, then does it mean I will have to create a separate IDOC for each vendor in R/3 ( in vendor specific format) and send that to them.
Thanks in advance.
Regards
Shirin

Hi,
1) Should we send data directly from SAP to 3rd party using EDI adapter and avoid XI.
A) For EDI integration u need to have the EDi adapters and for that u need to purchase the seeburger license and which is need to be installed on XI and after that only u can use EDi adapter with Xi.
U can not ignore XI.
2. I assume EDI adapter will automatically convert IDOC to vendor format data and vice-versa.
A) Yes but only when u purchase the seeburger license. there are other ways as well either use conversion agent or module program which convert the XML to EDI format.
3. All 30+ vendors will need to access this EDI adapter system or do they all need to have a separate one installed in there landscape.
A) U have to use the EDI adapters with Xi and configure ur scenario in XI for all the vendors.
4. If we use XI, will the adapter be able to communicate to XI. If yes what is the adapter name which connects to XI.
A) Seeburger provide As2,X400,FTP,VAn adapters for EDi integration.
5. All vendors need this data in a slightly different format, so will the EDI adapter do the format conversion for every vendor ?
A) What EDI format ur vendor receivers the data it depends upon that.
6. Since all vendors have a diff file format needed, I want to avoid doing extensive message mapping in XI. So can the EDI adapter handle it or is ther any easy way to do this mapping.
A) Mapping is the part of desing and mapping changes accroding to the business requirement and mapping rule which is provided by Functional people.
7. If mapping is not possible, then does it mean I will have to create a separate IDOC for each vendor in R/3 ( in vendor specific format) and send that to them.
A) u need to do the mapping between IDOC and EDi then only the data will be mapped with the required target EDI strcuture.
chirag

PI 7.1 : Taking a input PDF file and mapping it to a hexBinary attribute

Hello All,
We have a requirement which involves taking in an input PDF file and mapping it to a message type with binary attribute and sending it to an R3 system.
Can anyone please detail the steps or point us to the correct documents for setting up the scenario.
The scenario is file to Proxy adapter. The part which we need assitance is pulling up the input pdf and mapping it to binary field.
Thanks.
Kiran

Thanks Praveen,Mayank,Sarvesh and Andreas for your valuable help with the issue.
I was able to successfully pick up the binary PDF file from a file server , encode it using Base 64 and post it to R3.
I used the following code snippet and added the mentioned jar files to create a new jar file which was used as java mapping in the operation mapping.
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.*;
import com.sap.aii.utilxi.base64.api.*;
import java.io.*;
import java.util.*;
public class Base64EncodingXIStandard implements StreamTransformation{
     String fileNameFromFileAdapterASMA;
     private Map param;
     public void setParameter (Map map)
          param = map;
          if (param == null)
               param = new HashMap();
     public static void main(String args[])
          Base64EncodingXIStandard con = new Base64EncodingXIStandard();
          try
               InputStream is = new FileInputStream(args[0]);
               OutputStream os = new FileOutputStream(args[1]);
               con.execute(is, os);
          catch (Exception e)
               e.printStackTrace();
public void execute(InputStream inputstream, OutputStream outputstream)
               DynamicConfiguration conf = (DynamicConfiguration) param.get("DynamicConfiguration");
               DynamicConfigurationKey KEY_FILENAME = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
               fileNameFromFileAdapterASMA = conf.get(KEY_FILENAME);
               if (fileNameFromFileAdapterASMA == null)
                    fileNameFromFileAdapterASMA = "ToBase64.txt";
          try
               while ((len = inputstream.read(buffer)) > 0)
                    baos.write(buffer, 0, len);
               str = Base64.encode(baos.toByteArray());     //buffer);
               outputstream.write("<?xml version=\"1.0\" encoding=\"utf-8\"?><ROOT>".getBytes());
               outputstream.write(("<FILENAME>" + fileNameFromFileAdapterASMA + "</FILENAME>").getBytes());
               outputstream.write( ("<BASE64DATA>" + str + "</BASE64DATA></ROOT>" ).getBytes());
          catch(Exception e)
               e.printStackTrace();
     byte[] buffer = new byte[1024*5000];
     ByteArrayOutputStream baos = new ByteArrayOutputStream();
     int len;
     String str = null;
I had to do the following configuration settings
1) Create a Sender Comm Channel with Adapter Specific message attributes and Filename checkbox checked.
2) Use the Java Mapping in the Operation mapping.
The scenario is working smoothly with out any issues.
Thanks.
Kiran

Help me please : Serious problems with collection-mapping, list-mapping and map-mappi

Hi everybody;
I have serious problems with list-mapping, collection-mapping and map-mapping.
Acording to specifications and requirements in a system I am working on it is needed to
get a "list" of values or an indivudual value.I am working with ORACLE 9i Database,
ORACLE 9i AS and ORACLE 9i JDEVELOPER.
I tried to map a master-detail relationship in an entity-bean, using list-mapping.
And this was very useful in order to get a "list" of details, ...but, when I wanted
to get a single value I have some problems with persistence, something about "saving a state"
despite I just want to get the value of a single detail.
I decided to change it to map-mapping and the problem related with a single detail
worked successfully, but I can get access to the whole bunch of details.
May anyone of you help me with that?
I am very confused I do not know what to do.
Have any of you a solution for that problem?
Thank you very much.

Have you tried a restore in iTunes?

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

Configuration of EDI and ALE

Hi,
I am new to Idocs i would like to know the cofiguration settings for EDI and ALE from starting.I know abt creating partner profiles and the other stuff. I would like to know in detail. Please let me know.
Thanks in Advance,
Srikanth.N

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 The table is cross-client (see Help for further info). 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 The table is cross-client (see Help for further info). 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)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
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 Creating IDoc Type from Change Pointers
RSEOUT00 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.
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
<b>Reward points for useful Answers</b>
Regards
Anji

Diff Btn EDI and ALE

Hi Experts,
What is the diff btn EDI and ALE.
Straight answers will be rewarded.
Regards,
SAI

Hi,
In simple words ...
ALE is technology for SAP mainly use to transfer data between SAP systems.
EDI is the independent technology use to transfer data between two systems, they can be SAP systems or non SAP systems.
ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
Regards,
Padmam.

Biztalk EDI 856 Mapping H1 Segment

Hi,
I'm new to EDI 856 mapping in Biztalk. I have to map xml schema to EDI 856 XSD and generate a EDI file through biztalk.
I've 3 datasets (repeating nodes) in internal schema (shipment level, order level and item level) I have to map this data to EDI 856 in Biztalk mapping. But the complexity is i have to map all the data's with-in HL loop. I have to repeat HL loop thrice
for shipment level , order level , and item level and each time i should map data to different segments. (ex: i should have LIN segment only at item level).
My output should be like
<HL> --SHIPMENT LEVEL
<TD1></TD1>
<TD3></TD3>
<REF></REF>
<FOB></FOB>
<HL> -- ORDER LEVEL
<TD1></TD1>
<REF></REF>
<N1></N1>
<HL> --ITEM LEVEL
<LIN></LIN>
<SN1></SN1>
<TD></TD>
The problem i face is since i loop HL segment the N1 which should be present only at order level gets repeated at shipment and item level too. Please help me or suggest any study material , its urgent.
Thanks in advance..

Hi,
I can anyone help me to map a flat XSD to a structured XSD in biztalk mapping.
Incoming Schema
Record
<Shipmentdata>
<Shipmentdata1>
<Shipmentdata2>
<Orderdata>
<Orderdata1>
<Orderdata2>
<ItemData>
<ItemData1>
<ItemData2>
OutputSchema
<shipmentData>
<OrderData>
<ItemData>
My input schema is a flat one which i take from DB (ex: if there is 15 items in one shipment and 3 orders the xml will repeat 15 times with repeating data in shipment node and order node). I should convert it into a Structured XML with 3 level of hierarchy.
Please help with Biztalk mapper example. Thanks in advance.

AP-grouping and SIte-Specific Vlan's question

Hi Friends,
I was wondering if Site-specific Vlan's can be implemented on Guest-vlans where SSId's are anchored to Anchor-controllers from main controllers.
I will appreciate any inputs.
Thanks
JAy

Unfortunately I don't believe this can be done. I've run in to this question before at least one other time.
Basically, AP Groups (inteface assignment) only work for the clients local to that controller. Once you hit an "anchored wlan" you are not using the interface assigned by the AP group.
As an anchored client, you are not seen as connected from a particular AP, but instead are see as a client from the foreign controller.
Your only option would be to create multiple SSIDs and map each SSID on the anchor controller to the required vlan. You could use AP groups (wlan override) to specify which guest ssid you want on a particular AP, but I think thats your only option
Perhaps if you were anchoring a client doing 802.1x, you could pass interface/vlan parameters that way, but it wouldn't work for a typical "webauth guest user"

EDI - IDOC mapping question

Dear Experts,
For transformations between EDI and basic IDOC types, are there any off-the shelf (ready to use) options? If yes what are they? If not, what is the easiest way of mapping in between these structures?
Our setup involves Seeburger's AS2 adapter.
Thanks

Hi Aamir,
Thank you for your response.
We are working in an environment where we do not have any control over the setup. So I have a few follow up questions, answers to which would help me immensely.
1. I saw that there are a"few" mappings available for which both the EDI and IDOC versions differ from what we need. So, is there anyway to get an actual listing of all supplied mappings?
2. In case you have worked for a similar scenario, is it possible for you to share a sample mapping spreadsheet ?
Thank you,
N

Import from Excel-Mapping Specific cells

I've used the SQL Import/Export tool to import simple Excel data in the past. These were often simple column to table imports...easy mappings. I currently have an Excel spreadsheet kept by our Sales people that needs to be imported. The data in these sheets
are not grouped into simple columns. For example, data values are either horizontal or I need to import specific data FROM cell A4 TO table column 'CCode' and cell A6 to 'CCode'.
The trouble I'm facing is that the import wizard wants to simply map column for column from Excel. Even when I go into, "Edit Mappings" I'm not really finding a way to map specific cell data to the SQL column. Any help would be greatly appreciated...
Excel Example:
SQL Table:

I'm seeing that now. I'll admit the format of the spreadsheet will be changing after I get these imported and moving forward. I should have mentioned this is on an older SQL 2005 server, and am playing around with an Integration Services Project...
Essentially I need to pluck the data in cells A1, C2, A4, C4-E4 and insert those values into an existing SQL table. I've defined my Excel Source. Seeing as the source sheet is a mess and I need to select certain cells (not all are in a neat range like C4-E4...I
have some single cell values I ALSO need to import like A1 & C2) I chose "SQL Command" as my data access mode.
The one thing I can't figure out is how to write a select statement that allows me to select certain cells and a small range of cells. I can select a single value by using: SELECT * FROM [sheet1$A1:A1] OR I can choose a range with the following: SELECT *
FROM [sheet1$C4:E4]...how would I format a select statement that will allow me to pick not only the individual cells but ALSO the ranges I need?
I have tried SELECT...UNION...SELECT but am limited to two select statements and places everything into a single F1 column when I need it in a row view to map with the SQL columns...so each cell I pull has a separate F value so I can properly map the data
to the correct SQL column like the following:
F1 F2 F3 F4 F5 F6 F7
A1 C2 A4 A6 C4 D4 E4

EDI Message Mapping Names

Hi All,
Can I please have the EDI message mapping names for the following:
1)Tradacoms versions 8 and 9
Inbound:Source message type ORDHDR and the target is IDOC structure ORDERS05(Sales Order)
outbound: Source message Invoic02 Idoc and the target message type INVFIL
2)EDIFACT D96A:
Outbound:Source message Invoic02 Idoc and the target message type INVOIC
3)ENACOM:
Outbound: For Source message Invoic02 Idoc and the target message type INVOIC
Your help is much appreciated.
Cheers,
Smith

Hi,
DO u have BIC installed on ur PC. if u have then u could find out the mapping name for the BIC itself.
Mapping program name for example:
See_E2X_ORDERS_D9A is the mapping name for ORDERS message type.
Chirag

ALE/EDI and RFC

Dear All,
Please, can anyone tell me what is the difference between ALE/EDI and RFCs?
Thanks in advance.
Kind Regards,
Umesh.

Hi prasad,
1) ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
2) In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
These r some major difference b/w ALE and EDI:
ALE: used to transfer IDOC with in the R3 distributed system.
EDI: used to transfer IDOC from R3 system to non sap system
ALE --This method is used to transfer master data
EDI--This method is maximum used to transfer transactional data.
ALE--RFC port is used
*EDI*-- FILE port is used
ALE--Data transfer takes place from one mother client to N different clients
EDI-- one partner 2 other partner thru customer distribution model
The philosophical difference between EDI and ALE can be pinned as follows:
If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to
reliable replicate data between trusting systems to store a redundant copy of the IDoc data.
The difference is made clear, when we think of a purchase order that is sent as an IDoc.
If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order.
However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
ALE
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.
ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.
ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.
The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.
ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.
ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
Benefits of ALE:
Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
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.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
REWARD IF USEFUL
THANKS AND REGARDS
SUMA SAILAJA PVN

EDI and mapping specification

Similar Messages

Maybe you are looking for