SAP ERP ==> SAP Administration

What is the procedure for creation of inbound idoc?

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

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

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:
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)

Get help for your Basis problems
Do you have a SAP Basis Question?

SAP Basis Admin Books
SAP System Administration, Security, Authorization, ALE, Performance Tuning Reference Books

SAP Basis Tips

• SAP BC Tips and Basis Components Discussion Forum
• Administration In SAP - Sapgui, Unix, SAP ITS, Router, Client Copy and IDES