topic Re: IDOCs in Application Development and Automation Discussions

IDOCs

Former Member — Wed, 03 Jan 2007 05:26:33 GMT

HI,

CAN ANYONE SEND ME SOME DOCUMENTS ON IDOCs.I DONT WANT THE IDOC links, because i already got many links from the forum..i want it to be in a simple,understanding way without much jorgans..

thanx in advance

regards,

Priya

Re: IDOCs

Former Member — Wed, 03 Jan 2007 05:28:36 GMT

This is the simplest and the best link

<i><b>The SAP R/3 Guide to EDI and Interfaces:</b></i>

http://rapidshare.de/files/6008346/SAP_R3_Guide_To_EDI.pdf.html

Regards,

Balaji Reddy G

***Rewards if answers are helpful

Re: IDOCs

rahulkavuri — Wed, 03 Jan 2007 05:36:19 GMT

hi as far as i know, just check this simple process to know about IDOC's

about IDOC's

http://www.sapbrain.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html

http://www.allsaplinks.com/idoc.html

creating an IDOC - example

http://www.allsaplinks.com/idoc_sample.html

u even have files out there if u want to explore more, award points if found helpful

Re: IDOCs

Former Member — Wed, 03 Jan 2007 05:37:41 GMT

Hi Priya,

For Inbound ALE Configurations: (Example)

Create Idoc segments – Transaction WE31.

Idoc segments

zmara02

zmatk01

zmarc02

zmarm02

Zmara02

Fields Data Length Data element

matnr 18 matnr

matkl 9 matkl

meins 3 meins

brgew 15 brgew

Zmatk01

Fields Data Length Data element

matnr 18 matnr

maktx 40 maktx

spras 1 spras

Zmarc02

Fields Data Length Data element

matnr 18 matnr

werks 4 werks

bwtty 1 bwtty_d

Zmarm02

Fields Data Length Data element

matnr 18 matnr

umren 6 umren

umrez 6 umrez

volum 15 volum

Create Idoc type – Transaction WE30.

Idoc type Idoc segments

Z_mat_idoc Parent - zmara02

Child - zmatk01

zmarc02

zmarm02

Create Message Type – Transaction WE81.

Message type

z_msg_type_01

Assign Message Type to Idoc type – Transaction WE82.

Idoc type Message type

z_mat_idoc z_msg_type_01

Create a function module through SE37

z_idoc_input_type_01

Assign characteristic of function module BD51

Assign fn module to Idoc type and Message Type WE57

Idoc type Message type Fn Module

z_mat_idoc z_msg_type_01 z_idoc_input_type_01

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

Process code Inbound function module

zmat z_idoc_input_type_01

Create a distribution Model - Transaction BD64

Create distribution model for distribution of messages from cpb105_01 to cpa105 with the message type of z_msg_type_01.

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

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

Update outbound parameters of the Partner profile – Transaction WE20

For the Logical system A for the above two message types update the partner profile.

For each message type specify the Port and the IDoc types.

( Note : Port definition need to maintained using transaction WE21 and

it has to be defined as a Transactional RFC port with RFC destination for

system specified, which need to be maintained using SM59 ).

Regards,

Priyanka

Message was edited by:

Priyanka Neelam

Re: IDOCs

SantoshKallem — Wed, 03 Jan 2007 05:59:20 GMT

SAP Document : ALE

APPLICATION LINKING ENABLING

Let us assume we are working with two clients namely Client 100 and Client 200

System Name : cysap03

The settings for Decentralized Sales and Centralized Shipping are Done in

Following Manner.

The Receiving System is Client 100 and Sending System is client 200 i.e.

Sales Order created in client 200 initiates a Purchase Order automatically.

This P.O. is send to client 100 as a Sales Order.

The following is the step-by-step procedure:

1) SETUP LOGICAL SYSTEM:

To do setup the Logical System follow the following steps

In IMG Settings

Cross Applications à Distribution (ALE) à Basic Cofiguration.

Set up ‘Logical System à Maintain Logical System.

Create New Entries (Eg. ALEINSO receiving system)

(ALEPOOUT sending system)

2) ALLOCATE the created logical systems to respective clients.

ALEINSO assign to client 100

ALEPOOUT assign to client 200

3) DEFINE the RFC Destination. Do the following.

Cross Application à Distribution (ALE)àCommunication.

Execute RFC Destination.

SAP Document : ALE

Create for R/3 Connections ALEINSO in RFC destination box. Connection

type as 3.

Give Target machine as cysap03.

User: User11 (This is the logon for dist.)

Client : 100

Password: *** Enter the client logon password.

Test connection and remote logon to verify.

Repeat this procedure for ALEPOOUT for client 200.

4) Distributing the Customer Model

Ø Execute Maintain customer distribution model directly for creating the customer

model.

Ø Specify the source logical system (ALEPOOUT) and Create a customer model

name. (POOUT).

Ø Select the target logical system (ALEINSO) from the list.

Ø Create Message Type.

Ø In the resulting screen, in log message type enter ORDERS, ORDCHG,

MATMAS, CREMAS, and DEBMAS.

Ø Transfer and Save.

Ø Distribute customer model on the previous screen

SAP Document : ALE

5) Generate Partner Profiles using Cross Application à

Distribution (ALE)àDistribution Customer Model

Select generate partner profiles. In customer model box enter the model name that

you created (POOUT).

You should get a screen mentioning successful creation of customer model in green

color.

6) Distribute The Customer Model Again

Use Customer Model (ALEPOOUT) and Receiving System as (ALEINSO).

On execution you get the following message

copy with RFC destination ALEINSO

model data sent successfully.

7) Log on to client 100.

Cross applicationsàDistribution ALEàCommunicationsà generate partner

profiles for customer model (POOUT).

The system tells whether inbound parameters have been created or not.

Besides the above settings Check the following settings and if required do them.

1) CHECK ISO settings for Currency ,

Unit of measure in Cross Applications à Distribution (ALE) à Basic Configuration

à CHECK ISO settings

a) Currency. Check whether the currency is existing for ISO code.

b) Unit of Dimension Check whether the unit of measurement is existing, if

so in the detail screen enter the ISO code and mark the primary code field .

2) Check ALE Consistency checking in SET UP Sale scenarios.

SAP Document : ALE

3) Set the message types of the sending system for ALE medium in the sending

system.

Sending System

Once the settings are through Execute the transaction completely (i.e. S.O.

àP.R.àP.O.)

Check whether the Idoc has been created and whether it is at the port.

Dispatch the Idoc using the following path

LogisticsàCenter Functionsà Period. Work à Check Idoc Dispatch.

Receiving System

Check Whether Idoc has been posted in the application

LogisticsàCenter FunctionsàMonitoring àIdoc Overview

If the Idoc has not been posted then it can be checked why it is not been posted by

testing

The path is

Tools àAdministrationàProcess Technology à Idoc àIdoc Basisà Test à

Test Tool

Here enter the Idoc no and create it.

On the next screen Function module name has to be entered in debugging mode .

Reward if useful

Re: IDOCs

Former Member — Wed, 03 Jan 2007 06:16:02 GMT

Hi Priya,

Have a look at below links. It gives you PDF docs with the help of which you can get the knowledge about IDOCs.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEHR/CABFAALEHR_ALE_QS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/ECPCA/ECPCA_ALE_154.pdf

I hope it helps.

Best Regards,

Vibha

*Please mark all the helpful answers

Re: IDOCs

Former Member — Fri, 02 Mar 2007 11:41:06 GMT

Can Anoy one share ou send to lmigueljesus@gmail.com

The SAP R/3 Guide to EDI and Interfaces:

http://rapidshare.de/files/6008346/SAP_R3_Guide_To_EDI.pdf.html

link is offline

best Regards

Miguel

Re: IDOCs

Former Member — Fri, 02 Mar 2007 11:52:44 GMT

Hi Priya,

Send your mail ID.

Thanks

Sunil

Re: IDOCs

Former Member — Fri, 02 Mar 2007 19:55:35 GMT

Hi Miguel!

I think there is a problem with this file on RapidShare. It gives an error saying "File not Found".

I´m still looking for EDI Document settings (IDoc How to or something like that).

Do you have this file yet? Could you post again? or send to my e-mail addrs?

Tks in advance.

Marcelo Franç

Re: IDOCs

Former Member — Fri, 02 Mar 2007 20:05:05 GMT

Please check this links.

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

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

Re: IDOCS

Posted: Sep 6, 2006 6:54 AM in response to: srinivas kamire... Reply E-mail this post

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm

http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm

http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm

http://searchsap.techtarget.com/sDefinition/0,,sid21_gci852485,00.html

ALE is SAP technology to support distributed yet Integerated processes across several SAP systems, for which we use IDOC which are nothing but documents.

The step-by-step procedure to setup the ALE IDOC:

1.SETUP LOGICAL SYSTEM:Execute SALE Transaction Code.

2.Now you have to allocate the created logical systems to respective clients.

3. Maintain RFC Destination: TR.CODE:SM59.

4. Maintain Distribution Model TR.CODE:BD64.

5. Eg : Create Material using MM03 Tr.Code.

6.Execute BD10 to transfer the material.

7.Execute BD11 to get the material.

8.Execute Tr.code MM03 and give the material.

9.Execute Tr.code WE19( for rectification of errors).

10.Execute Tr.code MM03 and give the materialon other system/client.

11.Monitoring of IDOCS.

Transaction Codes:

IDOC Display of Status: WE 05.

IDOC Date and Time: WE07.

I hope these steps will help you.

ALL The BEst

sri

Re: IDOCs

Former Member — Fri, 02 Mar 2007 20:34:41 GMT

Hi Here I am giving you some info regarding idocs n i am giving you some more links also for further information

Intermediate Documents (IDOCs)

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.

The two available process for IDOCs are 1) Outbound Process 2) Inbound Process.

There are basically two types of IDOCs.:

1. Basic IDOC type defines the structure and format of the business document that is to be

exchanged between two systems.

2. Extension Idoc: Extending the functionality by adding more segments to existing Basic IDOCs.

-àTo Create Idoc we need to follow these steps:

1. Create Segment ( WE31)

2. Create Idoc Type ( WE30)

3. Create Message Type ( WE81)

4. Assign Idoc Type to Message Type ( WE82)

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

2. Create Idoc Type (WE30)

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

3. Create Message Type (WE81)

Go to transaction code WE81

Change the details from Display mode to Change modenAfter selection, the system will give this message “The table is cross-client (see Help for further info)”. Press EnternClick New Entries to create new Message Type

Fill details

Save it and go back

4. Assign Idoc Type to Message Type (WE82)

Go to transaction code WE82

Change the details from Display mode to Change moden 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

There are three types of records :

Control Record nData Record nStatus Record

Control Record - contains the key information like destination, IDoc type, message type, port and sender information. Control records are of EDIDC type of structure.

Data Records - This contains two parts.

Administrative Section and Data Section

Administrative Section consists of Idoc number, Segment Name, Segment number, Version, Segment Hierarchy etc.

Data Section contains the data of respective segment

Data records are of EDIDD type of structure

nStatus Record - whenever a process is taken place, system will generate status records.

We can identify the process with the number of status record.

01 - 49 for Outbound Process

50 - 75 for Inbound Process

when IDoc is processed the messages are:

01 - IDoc is created

30 - IDoc is ready for dispatch