topic Re: ale/idoc in Application Development and Automation Discussions

ale/idoc

Former Member — Fri, 05 May 2006 09:17:54 GMT

can anyone send me one object u have done on IDOC

one master idoc and one using extended idoc

with detail proceedure of doing it

regards venkat

Re: ale/idoc

Former Member — Fri, 05 May 2006 09:22:27 GMT

Venkat,

These documents should help you.

http://www.sappro.com/downloads/OneClientDistribution.pdf

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

Regards,

Ravi

Note : Please mark the helpful posts.

Re: ale/idoc

abdul_hakim — Fri, 05 May 2006 09:27:20 GMT

hi venkat.

get the below book.it will help you a lot.

ALE,EDI and IDoc Technologies for SAP by Arvind Nagpal..

Cheers,

Abdul Hakim

Re: ale/idoc

Former Member — Fri, 05 May 2006 09:29:49 GMT

Hai Venkat

Try with the follwoing steps

Sending System(Outbound ALE Process)

Tcode SALE „³ for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 ¡V Create Model View

Tcode BD82 ¡V Generate partner Profiles & Create Ports

Tcode BD64 ¡V Distribute the Model view

This is Receiving system Settings

Receiving System(Inbound ALE )

Tcode SALE „³ for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

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

Tcode BD82 -- Generate partner Profiles & Create Ports

Tcode BD11 Getting Material Data

Tcode WE05 ¡V Idoc List for inbound status codes

Message Type MATMAS

Tcode BD10 ¡V Send Material Data

Tcode WE05 ¡V Idoc List for watching any Errors

1)a Goto Tcode SALE

Click on Sending & Receiving Systems-->Select Logical Systems

Here Define Logical Systems---> Click on Execute Button

go for new entries

1) System Name : ERP000

Description : Sending System

2) System Name : ERP800

Description : Receiving System

press Enter & Save

it will ask Request

if you want new request create new Request orpress continue for transfering the objects

B) goto Tcode SALE

Select Assign Client to Logical Systems-->Execute

000--> Double click on this

Give the following Information

Client : ERP 000

City :

Logical System

Currency

Client role

Save this Data

Step 2) For RFC Creation

Goto Tcode SM59-->Select R/3 Connects

Click on Create Button

RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

give the information for required fields

RFC Destination : ERP800

Connection type: 3

Description

Target Host : ERP000

System No:000

lan : EN

Client : 800

User : Login User Name

Password:

save this & Test it & RemortLogin

Goto Tcode BD64 -- click on Change mode button

click on create moduleview

short text : xxxxxxxxxxxxxx

Technical Neme : MODEL_ALV

save this & Press ok

select your just created modelview Name :'MODEL_ALV'.

goto add message type

Model Name : MODEL_ALV

sender : ERP000

Receiver : ERP800

Message type :MATMAS

save & Press Enter

4) Goto Tcode BD82

Give Model View : MODEL_ALV

Partner system : ERP800

execute this by press F8 Button

it will gives you sending system port No :A000000015(Like)

5) Goto Tcode BD64

seelct the modelview

goto ~~>edit~~>modelview-->distribute

press ok & Press enter

6)goto Tcode : BD10 for Material sending

Material : mat_001

Message Type : MATMAS

Logical System : ERP800

and Execute

7)goto Tcode : BD11 for Material Receiving

Material : mat_001

Message Type : MATMAS

and Execute --> 1 request idoc created for message type Matmas

press enter

Thanks & regards

Sreenivas

Here Master Idoc set for Messge type MATMAS-->press Enter

1 Communication Idoc generated for Message Type

this is your IDOC

Take a look at this guide.

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

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

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/ale/configuration.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapdevelopment.co.uk/training

Thanks & regards

Sreenivasulu P

Re: ale/idoc

Former Member — Fri, 05 May 2006 09:32:43 GMT

hi srini

if possible can u send me one realtime object which u had done and the proceedure and code for me

to venkateswar_br@hotmail.com

regards venkat

Re: ale/idoc

Former Member — Fri, 05 May 2006 09:56:31 GMT

hi srini

if u have any problem in sending that its ok

regards venkat

Re: ale/idoc

Former Member — Fri, 05 May 2006 10:09:55 GMT

Hi,

Check out this article:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/03e6e790-0201-0010-9d98-ab8102817a92

cheers

Aveek

Award points if helpful

Re: ale/idoc

Former Member — Fri, 05 May 2006 10:17:24 GMT

hi aveek

thank u

regards venkat

Re: ale/idoc

Former Member — Sun, 15 Jul 2007 13:06:50 GMT

Hi Venkat,

Hope the following will help..

Create The Extension Segment

Transaction: WE31

The first step in extending an IDoc is to create the new segments that will go into that IDoc. There are some rules that you need to follow when creating the segments:

- The name of each segment type must start with ‘Z1’

- For each field in the segment you need to define a field name and a

data element.

- The data element for the segment structure must be of data type ‘CHAR’.

How to create new segments:

Run the segment maintenance transaction WE31.

Type your new segment name, and click on Create.

Define the fields of your segment:

Field name

Data Element for the field (from the ABAP dictionary).

Do not change the Export length!

Save the segment

Run Segment -->Check to check the segment for consistency.

Release the segment for transport. Select Edit -->Set Release. Note that the “Release’ column now has a check mark.

Create the Extension IDoc Type

Transaction: WE30

After you create the segments to be added to the extension type, you can create the extension type itself. Execute transaction WE30, enter the extension name, select Extension type, and click Create. You now have three options:

Create new type: Does not refer to other extension types

Create copy: Copies info from an extension type that already exists

Create successor: Extends an extension type from a previous release

of R/3. You can only have one version of an extension type for

each release.

Enter the Basic IDoc type that this extension type will extend.

The screen now shows the structure of the IDoc type you used as

a reference.

Position the cursor on one of the segments and click Create. This will insert an extension segment as a child of the selected segment.

NOTE: A segment cannot appear more than once in an IDoc type! You must control the use of duplicate segments with the segment attributes (the next screen).

The segment attribute screen appears. Enter the information and save.

Extension segments should not be mandatory (for future upgrades), and will need to have minimum and maximum number of instances defined. This answers the question, “for each instance of the parent segment, how many instances of the child segment may we have?”

You can press the Segment Editor pushbutton to view or change the segment definition.

Create the new Message Type

You can only use an extension IDoc type by assigning it to a message type. You can create a new message type for this.

First the message type itself needs to be created.

Transaction: WE81

Create a new entry and save. Use SAP established customer naming conventions (good form is to start with a Z and retain the rest of the related SAP message type, so, for example, MATMAS becomes ZMATMAS).

After creating the message type, associate it with the corresponding Basic IDoc Type and Extension Type. This relationship is used when IDocs are sent to or received from a partner to determine what segments are valid and what the hierarchy for those segments is.

Transaction: WE82

Create a new entry and enter the Message type, Basic IDoc type, Extension type, and Release, and save your data. Note: the release assignment is not valid for prior SAP releases.

One message type can be associated with many basic IDoc types; however, you need a one-to-one relationship for distribution via ALE.

Thanks,

Sathish Raj.