topic Re: STEPS for creating IDOC . in Application Development and Automation Discussions

STEPS for creating IDOC .

Former Member — Mon, 30 Jul 2007 12:11:44 GMT

I need to creat IDOC for whenever delivery is created .

Re: STEPS for creating IDOC .

Former Member — Tue, 04 Feb 2025 07:52:17 GMT

hi,

Go to We31 -> create a Segment

Go to We30 -> enter objname -> choose basic type

create new-> click on the objname -> enter the segment name -> Minnumber = 1 Max number = 1 Hirerachy level = 1.

Go to WE81 create a logical message type

Go to WE82 link your IDOC with message type.

This is the above process for creating an IDOC.

For more information in details on the same along with the examples can be viewed on:

***REMOVED BY MODERATION***

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm

***REMOVED BY MODERATION***

Rgds

Reshma

Re: STEPS for creating IDOC .

Former Member — Tue, 04 Feb 2025 07:50:33 GMT

Take the correct Idoc type and Message Type and process code from EDBAS and EDMSG tables and use

see the doc

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

For more information in details on the same along with the examples can be viewed on:

***REMOVED BY MODERATION**

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm

***REMOVED BY MODERATION***

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

Check these out..

Check below link. It will give the step by step procedure for IDOC creation.

***REMOVED BY MODERATION***

ALE/ IDOC

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

***REMOVED BY MODERATION***

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

***REMOVED BY MODERATION***

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

***REMOVED BY MODERATION***

go trough these links.

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

***REMOVED BY MODERATION***

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

***REMOVED BY MODERATION***

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

***REMOVED BY MODERATION***

http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

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...

1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.

2.IDOCs are independent of the sending and receiving systems.

3.IDOCs are independent of the direction of data exchange.

The two available process for IDOCs are

Outbound Process

Inbound Process

AND There are basically two types of IDOCs.

Basic IDOCs

Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

Extended IDOCs

Extending the functionality by adding more segments to existing Basic IDOCs.

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)

imp links

***REMOVED BY MODERATION***

--here u can find the ppts and basic seetings for ALE

***REMOVED BY MODERATION***

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..Hope this will help.

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

Important Transaction Codes:

SALE - IMG ALE Configuration root

WE20 - Manually maintain partner profiles

BD64 - Maintain customer distribution model

BD71 - Distribute customer distribution model

SM59 - Create RFC Destinations

BDM5 - Consistency check (Transaction scenarios)

BD82 - Generate Partner Profiles

BD61 - Activate Change Pointers - Globally

BD50 - Activate Change Pointer for Msg Type

BD52 - Activate change pointer per change.doc object

BD59 - Allocation object type -> IDOC type

BD56 - Maintain IDOC Segment Filters

BD53 - Reduction of Message Types

BD21 - Select Change Pointer

BD87 - Status Monitor for ALE Messages

BDM5 - Consistency check (Transaction scenarios)

BD62 - Define rules

BD79 - Maintain rules

BD55 - Defining settings for IDoc conversion

WEDI - ALE IDoc Administration

WE21 - Ports in Idoc processing

WE60 - IDoc documentation

SARA - IDoc archiving (Object type IDOC)

WE47 - IDoc status maintenance

WE07 - IDoc statistics

BALE - ALE Distribution Administration

WE05 - IDoc overview

BD87 - Inbound IDoc reprocessing

BD88 - Outbound IDoc reprocessing

BDM2 - IDoc Trace

BDM7 - IDoc Audit Analysis

BD21 - Create IDocs from change pointers

SM58 - Schedule RFC Failures

Basic config for Distributed data:

BD64: Maintain a Distributed Model

BD82: Generate Partner Profile

BD64: Distribute the distribution Model

Programs

RBDMIDOC – Creating IDoc Type from Change Pointers

RSEOUT00 – Process all selected IDocs (EDI)

RBDAPP01 - Inbound Processing of IDocs Ready for Transfer

RSARFCEX - Execute Calls Not Yet Executed

RBDMOIND - Status Conversion with Successful tRFC Execution

RBDMANIN - Start error handling for non-posted IDocs

RBDSTATE - Send Audit Confirmations

FOr testing you can use WE19.

Reward points for useful Answers

Regards

Anji

Re: STEPS for creating IDOC .

Former Member — Tue, 04 Feb 2025 07:44:01 GMT

ALE/ IDOC

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

***REMOVED BY MODERATION***

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

***REMOVED BY MODERATION***

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

***REMOVED BY MODERATION***

Check these step-by-step links

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287

https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985

for Smartforms material

/message/3815745#3815745 [original link is broken]

Re: STEPS for creating IDOC .

Former Member — Mon, 30 Jul 2007 12:18:01 GMT

ALE IDOC

Sending System(Outbound ALE Process)

Tcode SALE ? for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 - Create Model View

Tcode BD82 - Generate partner Profiles & Create Ports

Tcode BD64 -Distribute the Model view

Message Type MATMAS

Tcode BD10 ? Send Material Data

Tcode WE05 ? Idoc List for watching any Errors

Receiving System(Inbound ALE )

Tcode SALE ? for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 -- Check for Model view whether it has distributed or not

Tcode BD82 -- Generate partner Profiles & Create Ports

Tcode BD11 Getting Material Data

Tcode WE05 -- Idoc List for inbound status codes

reward for helpful ans

regards

Re: STEPS for creating IDOC .

Vijay — Tue, 04 Feb 2025 09:20:34 GMT

just refer to the link below

***REMOVED BY MODERATION***

step by step procedure with screen shots

regards

vijay

plz dont forget to reward points if helpful

Re: STEPS for creating IDOC .

Former Member — Mon, 30 Jul 2007 15:49:23 GMT

Hi ,

Go to NACE and select V2 and click output type from menu.

Give following value.

Condition component Value

Access sequence 0005 (sales organization/customer)

Condition 0 (no condition)

“Exclusive” select

Output type LAVA (shipping notification outbound)

Procedure V10000 (shipping output)

Application V2 (shipping)

Processing subroutine Program RSNASTED,

form routine EDI-PROCESSING

General data Select Condition access and Multiple sending of output, otherwise

leave the fields blank

Time e.g. 4 (immediately, IDocs are generated immediately after

posting)

Transmission medium 6

Partner function WE

Language DE (German)

You must maintain following values for outbound partner profile.

Output category : Desadv

Partner type : Ku

Partner function : WE

Port : Subsystem

Outbput mode: Collect idoc

Basic type : Delvry01

Packet size: 1

Application: V2

Output type : LAVA

Process code: DELV.

You can post the delivery by selecting Logistics Sales and Distribution Shipping, Delivery

Create (transaction VL01). Output control is used to find the condition record and the shipping

notification is sent to the customer via EDI (IDoc Interface). The shipping time in the condition

record determines when the corresponding outbound IDoc is generated.

Thanks,

Narayan

Re: STEPS for creating IDOC .

Former Member — Mon, 30 Jul 2007 16:08:31 GMT

Hi,

Receiving System(Inbound ALE )

Create Idoc type – Transaction WE30.

Idoc type Idoc segments

Z_idoc

Create Message Type – Transaction WE81.

Message type

z_msg

Assign Message Type to Idoc type – Transaction WE82.

Idoc type Message type

z_idoc z_msg

Create a function module through SE37

z_idoc_input

Assign characteristic of function module BD51

Assign fn module to Idoc type and Message Type WE57

Idoc type Message type Fn Module

z_idoc z_msg z_idoc_input

Create Inbound process code and assign inbound function module – Transaction WE42.

Process code Inbound function module

zcode z_idoc_input

Create a distribution Model - Transaction BD64

Create distribution model for distribution of messages

with the message type of z_msg

Update inbound parameters of the Partner profile – Transaction WE20

For the Logical system A for the above message type update the partner profile

inbound parameter and specify the process code of zcode.

For Outbound ALE Configurations: (Example)

IDoc definitions and necessary ALE configurations settings for the outbound .

Create Idoc segments – Transaction WE31.

Create Idoc type – Transaction WE30.

Create Message Type – Transaction WE81.

Assign Message Type to Idoc type – Transaction WE82.

Create a distribution Model - Transaction BD64

plz reward points if helpful

Re: STEPS for creating IDOC .

MadhavSharma — Fri, 19 Apr 2024 05:32:04 GMT

Awesome explanation man.