2006 Jul 05 5:15 AM
hi,
when i am doing the ALE configuration,
1. created logical systems
2. created RFC destination
3. Created Disturbution Model
4. To generated Partner profile, i ranned transaction BD82 and i am getting the following error
RFC destination for synchronous communication ( message type SYNCH) partner profile LS DEVCLNT800 SYNCH does not exist
generate partner profile
or specify outbound partner profilefor messages type synch
cheers
hi,
when i am doing the ALE configuration,
1. created logical systems
2. created RFC destination
3. Created Disturbution Model
4. To generated Partner profile, i ranned transaction BD82 and i am getting the following error
RFC destination for synchronous communication ( message type SYNCH) partner profile LS DEVCLNT800 SYNCH does not exist
generate partner profile
or specify outbound partner profilefor messages type synch
cheers
2006 Jul 05 5:18 AM
Hi,
Please create a partner profile in the transaction WE20 and then check.
Regs,
Venkat Ramanan
2006 Jul 05 5:27 AM
hi,
but when i generate the partner profile by using Bd82 by specifying the distrubution model which is created using BD64, should it automatically or not.
cheers
2006 Jul 05 5:36 AM
BD64 will do it for all the message types you specify as a part of the model. For SYNCH you will have to do that explicitly in WE20 transaction
Regards,
Ravi
Note : Please mark all the helpful answers
2006 Jul 05 5:40 AM
Hi ravi,
but the message type i am using is only MATMAs iam not using SYNCH message type. I dont no why ia mgetting this error because the the distrubution model that i create is only having MATMAS message type and not the SYNCH message type.
cheers
2006 Jul 05 10:21 AM
Hai Kumar
Check the following Steps for ALE Configuration
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
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
3)
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
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
-
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Thanks & regards
Sreenivasulu P
2006 Jul 05 12:53 PM
Hi Kumar,
Please add manually message type <b>SYNCH</b> and IDoc type <b>SYNCHRON</b> in your partner profile (WE20) as Ravi suggested earlier. Eventhough you are dealing with messge type MATMAS.
Message type SYNCH is a dummy message type for determination of RFC destinations and IDoc type SYNCHRON is a dummy IDoc type for synchronous communication.
You can setup something like this.
Outbound parameter options:
Field Value
Message type SYNCH
Receiver port A000000015 (Transactional RFC)
PacketSize 100
Output mode Transfer IDoc immed.
Basic type SYNCHRON
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |