EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 1 of 18
Electronic Data Interchange / Integration
The main advantage of using EDI is time factor and reducing the work time of
the user. For ex. Partner will rise the Purchase order/request, it will come as
inbound Idoc to SAP and creates the Sales Order and send the order
acknowledge to partner and creates the delivery and invoice and sends to
Partner through the Outbound Idoc. See the below fig
The Idoc is converted into EDI message and vise versa. If the data is correct then
it will create the sales order. 90% of EDI issues are related to data problem and
10% of issues are related to Configuration problem. Configuration problem is
like credit check and CMIR like that.
For inbound process the most important Transaction code in SAP is VOE4 the
table for this screen is EDPAR for making customer EDI. The Key fields for this
screen is Cust. No, Partner Function, External No. & Internal No..
Functional module picks up all the data from Idoc and places it in to BDC table.
There are two ways are for EDI to SAP. 1. Calling a BAPI 2. Calling an Idoc.
BAPI – Business Application Program Interface. The main disadvantage of BAPI
is the total control is in EDI sub system. If BAPI is failed it is difficult to trace
out.
EDI Partner PO GR IR
EDIOur system SO DELV IN
Inbound Outbound Outbound
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 2 of 18
SAP Architecture
R/3 – 1. Presentation layer, 2. Application layer, 3. Database layer.
Common layer is application layer in R/3. So we built the link between two SAP
R/3 systems is called ALE – Application Link Enabling. Logical system is
nothing but ALE.
* Standard functional module is available for Credit check.
SAP and EDI are two different systems which are in single operating system.
Most of the operating systems are UNIX only. IDOC Idoc means Intermediate document. The use or Idoc is we can track easily.
There are 3 sets of mandatory records available for Idoc
1. Control Records – Table is EDIDC
2. Data Records – Table is EDID4
3. Status Records – Table is EDIDS
Control records contains the following data
Who is sending the data to whom
What sort of data sending like order, delivery or invoice etc
Through what container we are sending
When this document is created / updated
What direction it is like inbound (2) or outbound (1) etc.
Status records contains the which status the Idoc is. Status code has only two
digits 01 – 99 out of that 01 – 49 is for outbound and 51 – 99 for inbound.
Following figure shows how status is converted from one to another
SAP OS EDI PARTNER
SO Idoc (03) Idoc (06) EDI message (12)
Idoc (01)
Ready to process – 30; +ve acknowledge from partner – 16, -ve – 17.
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 3 of 18
Data records:
These records are used to carry actual data in the segments, like all partner
functions data in one segment and all data functions in another segment etc.
All the Idoc segment names will start with ‘E1ED’ the 5th Character will play vital
role like header data or item data. Here ‘K’ – Header data; ‘P’ – Line item data; ‘S’
– Summary. The summary is necessary because if you have created a sales
order with line items 25 then the summary contains the data of sales with line
items 25 and net value of the document and how much tax like that.
If you take orders Idoc the segments are like below screen dump. The T.code for
that is WE30. The invoice Idoc also same like Orders idoc
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 4 of 18
The transaction code here is WE82
The transaction code here is WE82
• E1EDK01 : IDoc: Document header general data
Status: Required , min. number : 1 , max. number : 1
• E1EDK14 : IDoc: Document Header Organizational Data
Status: Optional , min. number : 1 , max. number : 12
• E1EDK03 : IDoc: Document header date segment
Status: Optional , min. number : 1 , max. number : 10
• E1EDK04 : IDoc: Document header taxes
Status: Optional , min. number : 1 , max. number : 10
• E1EDK05 : IDoc: Document header conditions
Status: Optional , min. number : 1 , max. number : 16
• E1EDKA1 : IDoc: Document Header Partner Information
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 5 of 18
Status: Optional , min. number : 1 , max. number : 99
• E1EDK02 : IDoc: Document header reference data
Status: Optional , min. number : 1 , max. number : 10
• E1EDK17 : IDoc: Document Header Terms of Delivery
Status: Optional , min. number : 1 , max. number : 4
• E1EDK18 : IDoc: Document Header Terms of Payment
Status: Optional , min. number : 1 , max. number : 3
• E1EDKT1 : IDoc: Document Header Text Identification
Status: Optional , min. number : 1 , max. number : 99
o E1EDKT2 : IDoc: Document Header Texts
Status: Optional , min. number : 1 , max. number : 9999999999
• E1EDP01 : IDoc: Document Item General Data
Status: Optional , min. number : 1 , max. number : 999999
o E1EDP02 : IDoc: Document Item Reference Data
Status: Optional , min. number : 1 , max. number : 10
o E1EDP03 : IDoc: Document Item Date Segment
Status: Optional , min. number : 1 , max. number : 10
o E1EDP04 : IDoc: Document Item Taxes
Status: Optional , min. number : 1 , max. number : 10
o E1EDP05 : IDoc: Document Item Conditions
Status: Optional , min. number : 1 , max. number : 16
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 6 of 18
o E1EDP20 : IDoc schedule lines
Status: Optional , min. number : 1 , max. number : 9999
o E1EDPA1 : IDoc: Doc.item partner information
Status: Optional , min. number : 1 , max. number : 8
o E1EDP19 : IDoc: Document Item Object Identification
Status: Optional , min. number : 1 , max. number : 5
o E1EDP17 : IDoc: Document item terms of delivery
Status: Optional , min. number : 1 , max. number : 5
o E1EDP18 : IDoc: Document Item Terms of Payment
Status: Optional , min. number : 1 , max. number : 3
o E1EDPT1 : IDoc: Document Item Text Identification
Status: Optional , min. number : 1 , max. number : 9999999999
E1EDPT2 : IDoc: Document Item Texts
Status: Optional , min. number : 1 , max. number : 9999999999
• E1EDS01 : IDoc: Summary segment general
Status: Optional , min. number : 1 , max. number : 5
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 7 of 18
For delivery
The transaction code here is WE82
• E1EDK07 : IDoc: Document header shipping notification (transport)
Status: Required , min. number : 1 , max. number : 1
o E1EDKA1 : IDoc: Document Header Partner Information
Status: Required , min. number : 1 , max. number : 9999
o E1EDK03 : IDoc: Document header date segment
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 8 of 18
Status: Required , min. number : 1 , max. number : 9999
o E1EDKT1 : IDoc: Document Header Text Identification
Status: Optional , min. number : 1 , max. number : 9999
E1EDKT2 : IDoc: Document Header Texts
Status: Required , min. number : 1 , max. number : 9999
• E1EDK08 : IDoc: Document header shipping notification (delivery)
Status: Required , min. number : 1 , max. number : 99999
o E1EDS01 : IDoc: Summary segment general
Status: Optional , min. number : 1 , max. number : 99999
o E1EDKA2 : IDoc: Document Header Partner Information
Status: Required , min. number : 1 , max. number : 99999
o E1EDK06 : IDoc: Document header date segment
Status: Required , min. number : 1 , max. number : 99999
o E1EDKT3 : IDoc: Document Header Text Identification
Status: Optional , min. number : 1 , max. number : 99999
E1EDKT4 : IDoc: Document header text
Status: Required , min. number : 1 , max. number : 9999
o E1EDP06 : IDoc: Package identification total
Status: Optional , min. number : 1 , max. number : 99999
o E1EDP07 : IDoc: Purchase order data shipping notification
Status: Required , min. number : 1 , max. number : 99999
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 9 of 18
E1EDP08 : IDoc: Package data individual
Status: Optional , min. number : 1 , max. number : 99999
E1EDP09 : IDoc: Item data shipping notification
Status: Required , min. number : 1 , max. number : 99999
E1EDPT1 : IDoc: Document Item Text Identification
Status: Optional , min. number : 1 , max. number : 99999
E1EDPT2 : IDoc: Document Item Texts
Status: Required , min. number : 1 , max. number : 9999
• E1EDS02 : IDoc: Summary segment
Status: Optional , min. number : 1 , max. number : 99999
Idoc types & Message types
Idoc is a re-useable structure. Idoc type is defined as a container. Container is
nothing but what sort of data of segment I need to accommodate in Idoc type.
Idoc type is two fields 1. Basic type, 2. Extension.
Basic type is nothing but what standard SAP has provided Extension is nothing
but if you need extra data to insert in segments you need to create and attach to
Basic type. For ex: - Basic type is ORDERS01; Extension is ZORDERS01. Customer Master Data Message type and Basic types
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 10 of 18
Material Master Data Message type and Basic types
Vendor Master Data Message type and Basic types
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 11 of 18
PARTNER PROFILES DETAILS – The transaction code for partner profile is
WE20
Here the Customer 3070 having the Outbound interfaces for Order, Delivery &
Invoice. If you double click on DESADV you may seen the below screen.
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 12 of 18
1. Partner No:- The customer no. which SAP is sending
2. Partn.Type:- Which type of partner he is like Kunnr (Cust), Vendor etc
3. Partner Role:- partner function like SP, SH, BP & PY
4. Message Type:- Which type of data SAP is sending
5. Message code:-
6. Message function:-
7. Test:-
8. Receiver port:- From this port only the Idoc is going to (OS) Unix level
9. Pack. Size:-
10. Queue Processing:-
11. Transfer IDoc Immed.:- If you select this after saving the delivery the
output will trigger to IDoc and it process automatically
12. Collect IDocs:- If you select this after saving the delivery the output will
trigger to IDoc and it will ready to process state. Another program should
run for process this idocs. The program name is RSEOUT00 for
1 2
3 4
5
6 7
8
9 10
11
12
13
14 15
16 17
18 19
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 13 of 18
processing the fresh idocs.
13. Output Mode:-
14. Basic type:- This is Basic type of DESADV. SAP has provided many basic
types for Delivery (DESADV). Here we are using DELVRY01
15. Extension:- If you have any extension of DELVRY01 here we need to give
16. View:-
17. Cancel processing After syntax error:- If you select this if any syntax error
then the IDoc should not be processed further.
The next tab page is Message control
1. Application:- V2 for Delivery
2. Message Type:- LALE is the output type for EDI at Delivery level
3. Process code:- Here the process code is DELV if you double click on
Process code it will show the Function module which will create the Idoc.
4. Change:- Used for sending the changes in the document
1 2
3
4
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 14 of 18
So for creating the Idoc from LALE output type SAP standard has provided
the functional Module “IDOC_OUTPUT_DELVRY”. If you double click the
functional module.
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 15 of 18
Double click on Line 27 “PERFORM REDUCTION_TABLE_CREATE”
Double click on Line 16 “PERFORM SEGMENTS_TO_READ_SET”
This is how this functional module is filling the data in to Segments from
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 16 of 18
various tables.
The another tab page is Post Processing: Permitted Agent which is used for
work flow trigger to Agent.
The another tab page is Telephony used for telephone nos if idoc has failure.
The another tab page is EDI Standard used for
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 17 of 18
PORT DETAILS:- Here the transaction code is WE21
Here I just opened the port CPFR2-VMI;
1. The version of Idoc
2. The Unix directory
3. The functional module which takes the Idoc from SAP to specified Unix
path
The Outbound: Trigger tab page
1. The Remote Function Call destination.
2. The Unix directory where the Unix script is available.
3. The Unix script; Same like Inbound file and status file tab page also.
1
2
3
1
2
3
EDI TRAINING MATERIAL By Mahesh
Prepared by Chandra Sekhar On 10/09/07 to 14/09/07
Page 18 of 18
After creating the port we need to modify in partner profiles at receiver port.
For list of Idocs the transaction code is WE02
If you double click the First Idoc you can find the following screen
Here you can see the Control record, data record with contain the data
segments and status records, beside that you can find the information about
Idoc.
The screen shots are taken from ECC 6; User name: CRMGEN; Password is
Intelli321.