ALE modelview error

[Former Member]

hi all,

when iam doing ale config for a a simple vendor master data transfer i got error.

the first 3 steps r ok. rfc destination and test connection and remote logon is ok.

in step 4 ..i assigned a message type(cremas) to the modelview.when i expand modelview i shows sender lg sys,rec log sys and cremas,no fillers in cremas.

1)but when distribute modelview error shows" no message have been defined for the selection condition in the model."

2)target sys VBR000 rfc destination for syncronous communication (message type SYNCH) partner profile Loical sys VBR800 SYNCH does not exist.generate partnet profile OR specify outbound partner for message type SYNCH."

wat is the prblem .give reply.

vijay

[Former Member]

Hi

look at it u may get idea

Application Linking and Enabling (ALE)

In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients

For our purpose we have two clients

namely Client 100 and Client 200.

System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).

Distribution of Material Master Data Between two Systems

1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)

To do this follow the following steps

Execute SALE Transaction Code

On The Screen Click on Sending and Receiving Systems.

Then Click on Logical Systems.

Then Click Defining Logical Systems.

Click New Entries Button

(E.g. (LG100 sending system)

(LG200 receiving system))

Enter two logical system names and their description.

Save

Comeback to SALE Transaction Code screen.

2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)

LG100 assign to client 100

LG200 assign to client 200

To do this, do the following.

Click Assigning Client to Logical System.

Ignore the message that comes up on the screen.

Select client 100

Click details button on the toolbar icon or press F2.

In the logical system box, enter LG100.

Click on the save Icon

Click the back button.

Now select client 200.

Click details icon or press f2.

In logical Systems box, enter LG200.

Save

Back.

Comeback to SALE Transaction Code screen.

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

(Note: Do Not Create This Step)

Click Create Button on the Screen

On the Screen Maintain RFC Destination i.e LG200.

Enter LG200 in RFC destination box.

Connection type is 3

Give a description for the RFC destination.

Maintain Technical Settings on Details on Technical Settings tab

Target Host as : SAPKDC (NOTE: Save it as a Host Name)

Maintain Logon Details on Logon/Security tab.

Language: EN.

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

Client : 200

Password: MM1234.

Save.

Click on create to do the above process for Client 200 in

The client 200 system.

4) Maintain Distribution Model.(BD64). (ABAPer role starts here)

Execute Maintain distribution model directly for

creating the model.

Click on change mode button on App tool bar of the Screen.

Create Model View pushbutton on App tool bar of the Screen.

A pop screen will appear in which you specify

Short text as Distribution for MM Data.

Enter Technical Name as LGMODEL.

Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.

A popup screen will appear in which you specify

Model View as LGMODEL.

Sender as LG100.

Receiver as LG200.

Again Click on Add Message Type Pushbutton on App toolbar of the Screen.

A popup screen will appear in which you specify

Model View as LGMODEL.

Sender as LG200.

Receiver as LG100.

SAVE.

On the same screen goto Menubar and select Environment.

And then select Generate Partner Profiles , then execute it.

On the Screen specify the Logical System as LG200.

Then execute the screen.

Click back.

Again On the same screen goto Menubar and select EDIT.

Again select Model View and then select Distribute.

****LOGIN to client 200.

Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.

And then select Generate Partner Profiles , then execute it.

On the Screen specify the Model View as LGMODEL

And Specify the Logical System as LG100.

Then execute the screen.

Click back.

*******Switch back to client 100 Session.

5) Create Material using MM03 Tr.Code.

Enter the material name as LGMATERIAL

Industry sector as Mechanical Engineering

Material Type as Finished Products.

And then Click on Data Pushbutton on the App tool bar.

Select views.

In the select views box for materials check basic data 1 AND 2.

Click enter icon.

In the next screen that you get

Give the text of the material as NEW MATERIAL.

Base unit of measure as KG.

Gross Weight as 200.

Net Weight as 100.

Weight Unit as KG.

In the description area language (E) and material description.

Click Save.

Now I Created a Material in Client 100 , I want to transfer this data to Client 200.

6) Execute BD10 to transfer the material in which you specify

the material as LGMATERIAL and

message type as MATMAS (client100).

Then a Screen will be displayed in which it shows that

1 Master Idoc Generated .. Enter

1 Communication Idoc Generated..Enter.

*******LOGIN to Client 200.

7) Execute BD11 to get the material in which you specify

the material as LGMATERIAL and

message type as MATMAS (client200).

😎 Execute Tr.code MM03 and give the material as LGMATERIAL

and see that the material is displayed as it was in Client 100.

If not follow these steps.

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

Specify the Existing Idoc Number and Executes it .

A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.

10) Execute Tr.code MM03 and give the material as LGMATERIAL

and see that the material is displayed as it was in Client 100.

Now the Material is correctly displayed in Client 200.

11) Monitoring of IDOCS.

Transaction Codes:

IDOC Display of Status: WE 05.

IDOC Date and Time: WE07.

Outbound:

Step 1. Application document is created when transaction is saved.

2. Message control is invoked.

3. Messages are processed by system.

4. Messages are Edited (if desired).

5. Output (ALE / EDI) is checked

6. Validate against Message control record from Partner Profile

7. Application Document is saved.

8. Entry NAST table is created for every selected output program

along with Medium & Timing.

9. Check for Process Immediately .

If (yes)

Determine Processing Program from TNAPR Table.

ELSE

Execute RSNASTED Program.

10. Read Partner Profile to determine Process Code.

11. Process Code points to the Function Module & Invoked.

12. IDoc is generated.

13. Check for ALE Request.

if (Yes)

Perform Filters, Conversions, Version Changes etc.

Else.

IDoc is stored in DATABASE.

INBOUND:

Step 1. EDI Subsystem creates an IDoc file from EDI Messages

2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.

3. Data in Control Record is validate against the Partner Profile.

4. IDoc is generated in Database and syntax check is carried out.

5. IDoc file is deleted once file read.

6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.

7. Check for Process Immediately.

If NO

Execute RBDAPP01 Program

Else

Read Process Code from Partner Profile

Process Code Points to Function Module

Application Document Posted.

further help:

check url

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

And also u can get lots of inof from the below link.

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

Regards