ALE Configuration problem

[Former Member]

Hi All,

I have to send idoc from R/3 to R/3.

For this i have created logical systems(D100 and R200) in both the clients(100 sender and 200 Receiver ). I am able to remote login from sender and receiver systems.

I have created the ports in both the systems with the sender and receiver logical system as the RFC destination for receiver and sender system. In sender RFC destination will be R200 and in receiver system RFC destination will be D100.

I have created partner profiles with the logical system names (D100 and R200) in both the clients.

In sender sytem, i have created outbound parameters and in receiving system i have created inbound parameters. I have used MATMAS as message type and MATMAS05 as basic type in sender outbound parameters.

I have created Model view distributer ( BD64) in both the clients.

I am able to remote login from both sender and receiver systems.

Now i am going to WE19 and selecting the basic type as MATMAS05 and executing. there i have to select the sender and reciver details. Here i am unable to get the receiver port details, and i am unable to send the idoc. Can anyone ple let me know whats missing here... if my process is completely incorrect, pls send the complete configuration that needs to be done on sender and receiver systems so that i can send the idoc.

Thank,

Raju

[Former Member]

Hi,

WE19 is the testing tool used to edit existing IDocs. So, if u have an IDoc errored and you wanna change the data record or control record of the failed IDoc, you go in for WE19, give the IDoc number, make the necessary changes and proceed with IDoc generation, in which case, a new IDoc will be created having the changed fields as required.

Now that you have made the necessary ALE set up to send materials, use transaction BD10 and provide the material number to be sent and the required receiver. You would get your IDocs generated. Note down the time duration and you can view the generated IDocs via WE02 or BD87.

~ Bineah

[Former Member]

Hi,

Go to system D100 execute the transaction BD10. Make a entry of following fields

Material Number

Message type : MATMAS

Logical system : R200

execute it. It will generate idoc, let us know what is the status of idoc.

Thanks,

Asit Purbey.

[Former Member]

Hi,

Is that the error which you are facing within WE19 is "Recipient port invalid"

When using the test tool WE19,receiver port should be given like this . SAP<sy-sysid>.

Thanks Sruthi .

[Former Member]

Ok a Little different approch. Check if this works for you.

After creating tRFC Port, do not do anything for partner profiles. Just define the Distribution model the way you want and from Menu Option in BD64 Environment->generate partner Profiles.

Regards

Shital

[Former Member]

Hi Shital,

When i am going to BD64 and distributing, i am getting the error " RFC destination for synchronous communication (message type SYNCH) Partner profile LS D100 SYNCH does not exist.

i have added the message type SYNCH as outbound parameters. Still getting the same error.

Pls let me know what can i do now.

Thanks,

Raju

[GauthamV]

You should not add synch manually ,once you genarate partner profiles

from BD64 ,it will be generated automatically.

[Former Member]

Hi Gautam,

After going to distribute in BD64, i am getting the error "RFC destination for synchronous communication (message type SYNCH) Partner profile LS D100 SYNCH does not exist".

How to remove this error.

Thanks,

Raju

[Former Member]

Hi,

To overcome this, add the dummy message type SYNCH in the outbound partner profile. Now distribute, you will find it distributed successfully.

~ Bineah.

[Former Member]

Hi Bineah,

I added the dummy message type SYNCH, still getting the same error.

Thanks,

Raju

[soumya_jose3]

Hi Raja,

Generate partner profile first and then distribute the model through BD64.

This should solve your problem.

Regards,

Soumya.

[babu_kilari4]

Raj,

Do one thing. Write a small report program. In that report program try to create two internal tables one for data records(EDID4) and another one for control records(EDIDC).

As you know the name of the Port, Message type. Assign it appropriarely in the above table.

Use the FM MASTER_IDOC_DISTRIBUTE to create the Idoc. This would definitely work as you are populating the port and message types of the target partner.

Hope you got it.

Thanks,

Babu Kilari

[Former Member]

Hi ,

I think data passed to port is not fine.Can you check it out once by the following way.

Execute the sap standard program RBDMOIND and check the idoc status again.If the status is showing as 03 check the TRFC log (SM58) for entries with INBOUND_IDOC_PROCESS if it is found test the RFC destination and fix the problem then restart the failed TRFC entries and check the status of idoc. Whether entries with INBOUND_IDOC_PROCESS not found it indicates the server problem for that check the system log in SM21.

Warm Regards,

Shobhan

[Former Member]

Hi Raj,

After going through your post, I came to know that you are trying to create an IDoc by using WE19 tcode. Usualy, WE19 is used for analysis of existed IDoc.

1.

Here, you have tried this to create an IDoc with message type MATMAS05. After excuting the first screen of we19, you wil be getting the empty structure of the IDoc. There you have to fil the Control Reccord and DataRecords. Till this point you were suceeded.

The issue came into picture while you are going to fill the Cotrol Record. It is not giving you the tRFC port name in F4 help. Here, in this case, you have to provide manually the tRFC name which you created. You manually fill the selected segments.

2.

The other issue is with the partner profile. Here you have created partner profiles(not generated from Distribution model) . After creating the partner profiles we usualy forget to test them.

To test the Partner Profiles execute the programme RSECHK07 and give the partner profile names which you created. It will clearly give the analysis.

By doing this, the post may be solved. HOpe you have understand and might be helpful.

Thanks

Ram.