35712710-Idoc-Day-2
196
Presentation On IDOC’s Hello Friends Good Morning Everybody
-
Upload
constantine-kiriakopoulos -
Category
Documents
-
view
13 -
download
0
description
SAP IDocs
Transcript of 35712710-Idoc-Day-2
Presentation OnIDOC’s
Hello Friends Good Morning Everybody
What is an IDOC ?
• The term IDOC stands for “Intermediate Document”. It’s not a process. 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.
• An IDOC is created as a result of execution of an outbound ALE or EDI process. In an inbound ALE or EDI process, an IDOC serves as an input to create application document.
• IDOC’s are independent of sending and receiving system. They can be used for SAP to SAP and SAP to non-SAP process communications as long as the participating processes can understand the syntax and semantics of the data.
IDOCs
• IDOCs are independent of the direction of data exchange.An IDOC can be used by an inbound as well as an outbound process.
For e.g the ORDERS01 IDOC is used by the purchasing module to send a purchase order and is also used by the sales and distribution module to accept a sales order. This avoids creating redundant IDOC types for the same information.
IDOCs
Idoc is also called as a data container.An idoc contains three parts. control record : To and From address store in this record (just like post card).Data record : Actual data is stored in this record.Status record : It shows the status weather the data record was sucessfully sending or not.
Control Record (EDIDC)
Data Record (EDIDD/EDID4)
Status Record (EDIDS)
IDOC is Data Container
IDOCs
AsynchronousDocument-related
R/3 System
System 1
SAPDocument
EDI subsystem R/3 System R/2 System 3rd party software
System 2
Document Transaction Message
IDoc
T.Codes used in IDOCs Creation
Used in Inbound & Outbound sides
1. BD54 Creation logical system,that is aliasing of server. 2. SCC4 Assigning logical system to the client.3. WE31 Create segment(segment contains fields).(segment is a
data base structure in terms of Idoc terminology.)
4. WE30 Create Idoc Type either basic or extension.(it is basically
used to know the format,That is in what format is used to sent data.It’s a collection of segments.)
5. WE81 Create Message type.(It defines what kind of data/information being transferred between the partners are identified by
using message types)6. WE82 Link message to Idoc Type.
T.Codes used in IDOCs Creation
ALE Settings: ALE just like set of configuration.Using ALE to send an idoc.
Idoc will use the rout created by ALE. ALE nothing but set of configuration done to transfer Idoc
from sender to receiver.
T.Codes For OUTBOUND ALE Settings:1. SM59 Creating RFC Destination.(always created on sender side)2. WE21 Create potr.(Here we assign RFC destination. It’s an
interface between Message type and RFC )3. BD51 Function module registration.4. WE57 Link between message type,idoc type and function module.5. WE41 Create outbound process code6. WE20 Create a Partner profiles(OutBound side).7. BD59 Set filtering used for validation.(If necessary).8. BD64 Distribution model.Note: 3,4 and 5 T.codes are used in message control Method.
T.Codes For INBOUND ALE Settings:
BD51 Function module registration.1. WE57 Link between message type,idoc type and function module.2. WE42 Create inbound process code.3. WE20 Create partner profiles(InBoumd Side).4. BD64 Distribution model.(It is not necessary to create.It
automatically creates when out bound model view has been generated.)
Note: 1,2 and 3 T.codes are used in message control Method.
T.Codes for showing the status:WE02 And WE05.RBDMOIND is a standard program to refresh the outbound status
03 to 12.
T.Codes used in IDOCs Creation
Hierarchy Of Creating message type,Idoc Type and Segments
MESSAGE TYPE
IDOC TYPE
BASIC EXTENDED
SEGMENT 1 SEGMENT 2
FIELD1 FIELD 2 FIELD 3 FIELD 4
..…
……
WE31
WE30
WE81
WE82
Bottom up Approach
Standalone Method for IDOC both
InBound And Outbound
Standalone Method
SAPLID SAPLIDSAPLIT : SenderSAPLID: Receiver
OutBound Creation
Segment Creation (T.code WE31)
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
OutBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
InBound Idoc
Your’s
N.Ashok Kumar Reddy.
Good Bye Everybody
