ALE ERROR

[Former Member]

Hi All,

Plz help me in resolving the issue, I am trying to configure ale to transfer material from one client to other and following this process.

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

ALE IDOC Steps

Sending System(Outbound ALE Process)

Tcode SALE ?3 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 ?3 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

I am getting the following error when I try to distribute in bd64, plz let me know hoe to resolve this.

This is the error message I am getting, plz let me know what is missing?

-

---

Distribution of model view MOD_EL

-

---

-

---

Target system NIT206	RFC destination for synchronous communication (message type SYNCH)
	Partner profile LS NIT206 SYNCH does not exist
	Generate partner profile
	or specify outbound partner profiles for message type SYNCH

-

---

Thanks.

[Former Member · Accepted solution]

Hello Ravi,

NIT206 seems to be the logical system for the target client. In the source system go to WE20 and then under Partner Type LS goto NIT206.

Go to outbound parameters and add SYNCH. Basic Type will be SYNCHRON and the port will be the port corresponding to NIT206 (check WE21-Transaction RFC ports).

After this generate the partner profile in BD82 once and try sending material through BD10.

Regards.

Ruchit.

[Former Member]

Hi Ruchit,

Thanks for that "SYCN" parameter which I was missing, I had once again created the link and this time I added this "SYCN", due to this the issue is resolved, one more thing I was missing is we19, I had to go and release from there, any how the issue is resolved.

[Former Member]

Now the previous error is removed and the new error is coming.

-

---

Distribution of model view MOD_EL

-

---

-

---

Target system NIT206	Model view MOD_EL has not been updated
	Rreason: Distribution model is currently being processed

-

---

In the outbound parameters of the sending client I had given MATMAS and SYCN.

In the sender system, when I go to we05, it is showing in green and "Data Passed Ok", however when I see in the other client There is no material.

[Former Member]

Hi Ravi,

It seems that BD64 is open in change mode in NIT206 . Make sure that BD64 is not open in change mode in target system. Once that is done please distribute the ALE model once more and then send the material.

Regards.

Ruchit.

[Former Member]

I had checked the rfc connection and found out that I can access one clent from other, how to check in Integration directory and is there anything where I can find out that the partner profile is correctly generated or not.

[Former Member]

Hello Ravi,

Did you had properly generated the partner profiles also did your RFC connection test has been successful?Have a look once again and reply again

Also check that the same LS is reflected in the Integration directory.

Regards,

Jafer