IDOCS – Intermediate Documentation

[Lingeswar_Karrennagari]

IDOCS – Intermediate Documentation:

 Basic Concepts to learn before learning Partner profile:

Concept:  IDOC is an intermediate document where many industries will use to transfer their data from one system to other system, it can be SAP to SAP or SAP to Non- SAP.

As an SAP MM consultant, we will work less on IDOC’s, but we should know the concept behind the IDOC for resolving the issues by Monitoring the IDOC.

Overview:

IDOC is an SAP object where data will be transferred inflow and outflow through electronic message, the main use of IDOC is transfer of data from SAP to Non-SAP through EDI and SAP to SAP through ALE.

Here we have 2 types of flows in SAP, where data will be flowed into SAP and other is data transfer to other tool from SAP through Inbound and Outbound.

Inbound: Data that received from other tool to SAP in the form electronic message.

Outbound: Data that will be flowed to other systems through SAP in terms of electronic message.

We have 2 IDOC types

1. Basic Type- It sends the information to the receiver port as per the mapping fields done by us.
2. Extension- When we want any extra information to send to receiving party then we have this IDOC extension.

Conversion Format:

If data is transferring SAP to Non-SAP, then data format is required that EDI acts as a data converter, it converts data to XML format and loads the data and sends to another tool respectively.

Mapping of fields has been done as per the size and data fields.

Mapping is same as LSMW method and it will be done by MM technical consultant and as a functional consultant we need check the port number and few major things explained below.

We have segments, where fields will be stored in the segments and mapping will be done according to the segments available in the IDOC.

We have Parent segment and Child segment; different fields will be stored in different segments.

Note: IDOC direction explains whether the data is flowing inbound or outbound.

Partner:

We have 3 partners in SAP R/3, where data will get exchanged within this and they are LI-Vendor, KU- Customer, LS- Logical system.

Vendor- Normally we use work with vendor for PO, Order confirmation, Order acknowledgement and Invoice.

Customer- SD side, Sales order

Logical system- we have other department systems, where weight lift measuring tool.

Data flows inside and outside as per the above examples.

Port:

The port we maintain it contain IP address of the source or receiving system and this port number will be provided by Basis Consultant.

 Partner Profile maintenance:

Partner profile should be maintained for all business partners where if we want to receive/send information to all the vendors.

T-code to maintain the partner profile is WE20.Double click on partner and click on LI-vendor, if we are setting partner profile with vendor.

Once we enter on vendor, we can see above screen where we can have options to enter inbound and outbound entries, as I told this will be electronic message where data flows.

We have message type in which we see inbound or outbound and, we can see contact information.  Select any of the two – either inbound or outbound.

And system will ask for receiver port number and this will be given by Basis consultant and here every filed is mapped and after they will provide the receiver port number to maintain in the below screen.

2.Next tab- Message Control:

If we are sending PO copy, we have message type for PO, insert message type and enter the link code ME10.

Whenever PO copy is created for this message type then IDOC number will be generated and transferred to receiver.Change message: In message control we can see change message option where if there is any change in document the IDOC will sends the changes automatically for that we need to maintain 1 more line in message control with change indicator.

3.Inbound options- Inbound Parameters:

Here we need to select the trigger by background program, so that it will take the parameters after saving and as per mapping it will send to receiver automatically.

4.Post processing:

Here we will maintain the agent who should receive the notification when EDI processing fails, System will send the log data and reason for failure.

5.Telephone:

 We can enter the telephone number of receivers.

6.EDI standard:

Here we can update the message type as per the purchase order.

Overview Explanation of above everything:

Receiver port means – the receiver IP address or data that is mapped and created a port that is receiver port.

We have IDOC type where it contains the segments in which it mapped all the fields, we will maintain the idoc type in outbound and it should be purchasing/sales.

Once we have IDOC type, we had message type where what kind of data that is transferring or mapped it can be purchase order, Acknowledgement, Contract.

Process code – where we have message type and idoc type contains the sending data information, now to process this we need some code that is process code.

By above 3 Idoc will trigger and sent to receiver.

Business Scenario: Transferring Material by ALE IDoc between two SAP Systems.

Sender System: DEV, Client -200.

Receiver System: QAS, client-200.

Step1. Go to Tcode- BD54 to create Logical system.

Step2. Click on New Entries Button.

Step3. Provide logical system name : CNT_DEV200 and save it.

Step4. Provide another logical system name : CNT_QAS200 and save it.

Step5.  Go to tcode- SCC4 to assign the logical system to the source client.

Step6. Click on edit button.

Step7. Double click on the source client 200 of the sender system .

Step8. Provide the logical system name to the client ans Save it

Step9. Go to the destination system QAS with client 200. Go to the Tcode- BD54 to create logical system.

Step10. Click on New Entries button.

Step11. Provide logical system name : CNT_QAS200 and save it.

Step12. Provide logical system name : CNT_DEV200 and save it.

Step13. Go to the Tcode- SM59 to create RFC destination in the Source system.

Step14. Create a RFC Destination ‘TO_QAS_200’ with details.

Step15. Maintain the log on details and save it.

Step16. Perform the connection test.

Step17. Go to Tcode- WE21 to create port.

Step18. Select the TRFC line and click on create button.

Step19. Select the first radio button and click on Continue button.

Step20. The system automatically creates a port. provide the description and assign the above created RFC destination and save it.

Step21. Go to the Tcode- SM59 to create RFC destination in the Destination system.

Step22. Create a RFC Destination ‘TO_dev_200’ with details.

Step23. Maintain the log on details and save it.

Step24. Perform the connection test.

Step25. Go to Tcode- WE21 to create port in the destination system.

Step26. Select the tRFC line and click on create button.

Step27. Select the first radio button and click on Continue button.

Step28. The system automatically creates a port. provide the description and assign the above created RFC destination and save it.

Step29. Now go to Tcode- WE20 to create partner profile in the source system.

Step30. Select the Partner Type LS and click on Create button.

Step31. Provide thePartner name ‘CNT_QAS200’, partner type as LS and click on Save button. Now click on the ADD button on the outbound parameter section.

Step32. Provide the message type as ‘MATMAS’ , port number and IDOC type as MATMAS05.

Save it and click on Back button.

Step33. Now the message MATMAS appears in the outbound parameters section.

Step34. Now go to Tcode- BD64 to create Customer Distribution Model in the source system.

Step35. Click on the Edit button.

Step36. Now click on the Create Model View button.

Step37. Provide the short test, Technical name as ‘DEVQASMAT’ of the Distribution Model and click on Continue button.

Step38. Now click on the Add Message type button.

Step39. Provide the sender logical system, receiver logical system and the message type. At last click on Continue button.

Step40. Noe the distribution Model ‘DEVQASMAT’ is created as shown below.

Step41. Now go to Tcode- BD82 to generate partner profile in the source system.

Step42. Provide the distribution Model name and execute it.

Step43. Al parameters are generated successfully.

Step44. Now In BD64 transaction, distribute the distribution model ‘DEVQASMAT’ as per the highlighted path.

Step45. Select the Destination system ‘CNT_QAS200’ to distribute the model.

Step46. The distribution model is created in the target system.

Step47. Now go to the Tcode- BD64 in the destination system.

Step48. The distribution model ‘DEVQASMAT’ is available here.

Step49. Now go to Tcode- WE20 to create partner Profile.

Step50. Select the Partner type LS and click on the Create button.

Step51. Provide the Partner as ‘CNT_DEV200’, type as ‘LS’ and Save it. Click on the ADD button under the Inbound parameters section.

Step52. Provide message type as ‘MATMAS’ and processing code as ‘MATM’. Save it and click on the Back button.

Step53. Now the message type ‘MATMAS’ appears in the Inbound section.

Step54. Now go to the Tcode- MM01 in the source system to create a material.

Step55. The material is created with number : 4066.

Step56. Go to the Tcode- MM03 in the destination system to see the material created above.

Step57. The material 4066 doesn’t exist in the destination system.

Step58. Go to the Tcode- BD10 in the source system.

Step59. Provide the material number: 4066, message type as ‘MATMAS’ and select the logical system as ‘CNT_QAS200’ and execute the program.

Step60. It generates a master Idoc. Click on continue button.

Step61. Again it generates a communication Idoc. Click on Continue button.

Step62. Now go to Tcode- BD87 in the source system to track the idoc status.

Step63. Provide the Partner system name and execute it.

Step64. Double click on message ‘MATMAS’.

Step65.  Double click on the line.

Step66. It displays the details of the Idoc in the source system.

Step67. Now go to Tcode- BD87 in the destination system.

Step68. Provide the partner System name ‘CNT_DEV200’ and execute it.

Step69. Double click on the message ‘MATMAS’.

Step70. Double click on the line.

Step71. It displays the details of the inbound Idoc.

Step72. Now go to Tcode- MM03 in the destination system.

Step73. Provide the material number- 4066 and click on Enter key.

Step74. The material is available in the destination system by IDoc.