OutBound : Pushing data from source to Target
InBound : Receiving data from tartet to Source
Message Type : ( WE81) : MATMAS (Material Master ) , DAMMAS (Customer Master) , Invoice, Billing, Delivery note, GL master , Vendor Master, etc,,,,,
Ex: MATMAS
DAMMAS
Please take latest Message Type to use. Why because SAP added more fields in latest Massage Type.
Basic Type Or IDOC Type : ( WE30 , WE19 ,WE60 ) :
Basic Type : Further Division like versions 01,02,03,04 like thatbelow
Ex: DAMMAS01
DAMMAS02
DAMMAS03
DAMMAS04
Stored information in IDOC has message Type means what data calling like customer, vendor, orders, invoice, GL, in the we have basic type like latest devisions.
Message Type Linked with Basic Type ( WE82 ) : This is form of storing segments or fields . or Holding the information in the form of segments / fields.
Extenstion means : some message type require custom fields adding custom field / Z field called Extension
Go to WE82
Here we can see Massage type to Basic Type with latest versions.
Go To WE 60
Here we can download the all fields for customer master and sent to Other team.
Go to WE19
IDOC Structure
Control Record : having parters, Basic type, Message Type
Data Record : contains segments along with fiels
Status Recerod : IDOC status like failure, success, where IDOC is on which status,
We can see IDOC ; WE02
How to get mapping fields
T.Code : WE60
In this screens we can see fields as per Control record, data records, status record
If want to download into excel sheet.
How to Open fields of IDOC
WE30 VS SE11 to see the fields, which screen is easy to view fields.
Here we can get the fields / what are segments having fields .
T.code : WE30
See the segment along with fields , which segment having which fields.
If want to see more into details
Go to T.Code : SE11
Just copy which highlated segment E1KNVVM and enter in below SE11
Here we can see all fields on segment wise . we can see clear fields. Which segment having which fields.
Here is one Note. Within client we are doing IDOC process. Some times client to client IDOC Process
Create Logical System: done by the Basis team/ some time ABAP team
T.Code : SALE
1) Define Logical System
New entry
2) Assign Logical System to Client
Double click on client 100
Create RFC Destination
Normally BASIS team will create RFC destinations. Create in SM59 . RFC means connection required to communicate between
system to system. Communicate from system to system. Sending PO from system A to system B.
T.code : SM59
Click on Create botton
Target Host : give Host or IP Address : to get IP address go t.code : OS01
Double clickon application server
Create Port and assign to RFC destination
Here we can create Port and map the Port to RFC destination.
Create Port : WE21
Here select the RFC destination which we careated above step and PORT generated automatically
Port : A000000019
SAVE
Distibutor Receiver
Vendor : 30007001
Purchase Org : E100
Customer :
BP :7512
Customer : 7502
Sales Org; E100
Dc : E1
Division : E1
Create Purchase Info Record : ME11
Purchasing info record 5300000138 E100 E100 created
Condition for Output Control - T.Code : NECE
T.Code : NECE
Here output configuration maintained for IDOC
If required any we will do create anything by functional consultant
Maintain Output records for PO ( From distributor to company )
T.code : MN04
Enter
Give vendor name and select EDI as 6 and save.
SAVE
Partner Profile : WE20
Here setup sender and receiver communication. That
Select partner LI and click on create botton
Here Click on create Outbound Parameters and maintained outbound parameters
SAVE
Create Purchase Order – ME21N
Click On Message . Here see the EDI details. Which are updated automatically from above config.
with this output IDOC will be generated.
SAVE Purchase order
Standard PO created under the number 4500000131
Go to T.Code : Me23N
Click on Messages
Green color means no issues.
Select line item and click on Processing log
IDOC is generated . see above screen. With IDOC no 198012
Go to T.code : WE02
Give the IDOC no which is created above
IDOC Status Record Table : EDIDS
IDOC Data Record Table : EDID4
IDOC Control Record Table : EDIDC
IDOC Issues and IDOC reprocessing
T.code : BD87 / WE19
Some time we can not see error details in WE02 – In such case Go to T.code : BD87
We can do the foreground process OR forground with errors and find the issue and correct the data and save the IDOC
Then see IDOC status in WE02 again.
2nd Scenario : Purchase Data from Source System to Target System as create Sales Order
Here sales order will create in Target system by using PO Data from source system
Go to T.code : SALE
Here we can created logical systems and assign the logical system to client
Go to T.code : WE21
Here create the Port and assign the port to RFC destination.
In this scenario we are using same port which are created above config.
Go to T.code : SM59
Here created RFC destination. Here assign the target system details.
Call the target system.
Go to T.code : WE20 - Create Partner Profile
Now create partner profile as logical system
Select logical system and click on create botton
SAVE. Once saved above screen . that is convert into edit mode
Click on Inbound parameters icon then enter details.
SAVE---> BACK
Go to T.code : VOE2
This is not mandatory . here link between this vendor suppose to supply goods to this customer
SAVE
Go to T.code : VOE4
External Partner is Plant ( E100) and SP&SH is sold to party and ship to party.
Go to T.code : BP vendor
In vendor master need to assign the customer in purchase data tab
SAVE
Go to T.code : ME12
Go to T.code : ME21N – Create purchase order
Standard PO created under the number 4500000135
