ALE Config

Hi,
When i am configuring the ALE in my system, i have created the logical systems, the RFC test is successful. and i have even modelled the distribution but when i try to exute the profile parameters i am getting the msg like:
Log for Partner Profile Generation
Distribution model                        No messages have been defined for the selection conditions in the model
i ignored that msg and continued with the recieving system profile parameters generation , but i got same msg....
when i try to distribute the model i am getting the error like :
Distribution of model view VENDMODEL
Target System LCDCLNT300   RFC Destination for synchronous communication ( message type SYNCH )
                                             Partner Profile LS LIDCLNT300 SYNCH doesnot exist.
                                             Generate Partner Profile
                                             or specify outbound partner profile for message type SYNCH
but i have already try to maintain partner profile for clinet 300 but i got msg.
can i know where would be the problem in my process.
Thanx & Regards,
Srinath

regarding the SYNCH problem.
You have to configure each receiving System in the SendingSystem PartnerProfiles.
Partnertype: LS (Logical System)
Sender = Sendersystem of the Distribution Model
Receiver = Receiver of the distributes Modelview.
Messagetype: SYNCH
IDoctype: SYNCHRON

Similar Messages

CRM to PI outbound IDOC scenario : IDOC ALE config

Hi folks,
I have a scenario: CRM-> PI
CRM system posts an IDOC to PI,
I have done all the necessary ALE configs:
1. comm. id on PI
2. RFC Destination on CRM to PI
3. Port on CRM. we21
4.Logical SYsm on CRM
5. Partn Prof on CRM
now, when i try to push out an idoc out of CRM , it fails in CRMs TRFC queu(SM58)
with this error:
Transaction IDX1: Port SAPDX1, client 500, RFC destination contain error
I have no clue why it failed with this error.
1. No idea from where it picked up this port as well.
2. Port i created to PI was an autogenerated Port and not SAPDX1, don't knw how it picks this up.
Would appreciate any help with respect to this.
Thanks,
Hank

Also, for your reference just double check if the following steps are completed properly for outbound processing:
1.Define Logical Systems and Assign Client to Logical System u2013 Transaction SALE
2.Maintain RFC Destinations u2013 Transaction SM59
3.Define Ports u2013 Transaction WE21
4. Maintain Distribution Model u2013 Transaction BD64
5.Generate/Create Partner Profile u2013 Transactions BD82/WE20
6.Distribute Model View u2013 Transaction BD64
    -Select the Model View
     -Go to menu path Edit -> Model View -> Distribute
     -Result log will be displayed on the next screen
Hopefully it should work now.
Puneet

ALE Config for Solman BPs

Is there any documentation out there to help me in setting up ALE between ECC and Solman to create BPs in Solman. I have basic documentation on ALE config in general but am looking for specific docs for Solman BP population.
Thank you,
Alex

Hi Alex,
Solution Manager was based on CRM so I will recomend you to start with Note 550055 - EBP/CRM: New integration for business partner
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index
This will give you the guideline, what I would suggest is to mantain as well the Org Structure in 1 system in this case ECC and then replicate maybe the Support Org Structure along with the BP's to Solution Manager.
Another SAP Note you cam use 615896 - HR-ALX: Distribution models - Templates, Most probably you have the templates in your system if you have current SP's, I do remember I saw some templates for CRM which will work fine for Solution Manager.
Hope this helps
Best regards,
Juan Jose Alvarado
Edited by: Juan Jose Alvarado on Mar 1, 2010 5:27 PM
Edited by: Juan Jose Alvarado on Mar 1, 2010 5:31 PM

Ale config part 2...question

Hi,
While doing the ale config as per blog...
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I managed to distribute the model view..however when i go to BD10 and select the specified material SWAR1...out of matmas...i get an error telling me that no material could be found.............How can i test that i can send an idoc to the XI system....? is there a standard material that i can send to verify this...
Venkat

There are no standard material numbers avaiable in SAP. All u need to do it to create in the TC MM01 and u can refer to the table MARA and the material number field is MATNR.
Coming WRT to the blog when u want to test it either u press F4 to get the list of material avaiable or check in MARA.

Urgent...problem in manuall ale config

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 it shows no message type is assigned to modelview.
2)in partner profiles i generate ports . here also i got error. partnet profile is not generated to the xxxx log sys and cancelled in both xxxx and yyyy log sys..
reply please.
vijay

Hi,
Try creating the ports and partner profiles manually through transactions WE21 and WE20 respectively and then the distribution model (txn BD64). Now try distributing the model view and proceed with the Idoc generation.
~ Bineah.

Transport abt ALE Config

Hi,
We have done all IDOC to File scenarios
We have configured the ALE settings on SAP R/3's DEv server.
Can i transport these Config to SAP R/3's QTY Server or Should i create them as it is appear in the SAP R/3's DEV server???
Regards
Suman

Hi Suman..
This was the ALE settings...
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.\
idoc to idoc
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
regards,
Kishore

Setting up Logical system in ALE Config !

Hi,
I have set up the ALE logical system in SAP to transfer data. Basically RFC destination setting. While I am trying to test the connection, I am getting an Error Program INBOUNDASYNC not registered.
Could any one help me out here.
Thanks,
Senthil

Hello,
Please make sure you have completed the starting of SMD agent also after the setup, u can find it in the guide.
also check the p4 or Https port number is correctly mentioned.
The user and pass mostly would be that of SMDadmin, created during the setup, or u can use SIDADM which will wrk fine.
sometimes root needs to be used as even sidadm can be restricted in ur envt. ( just in case).
Regards,
Kaustubh.

Custom IDOCS and ALE config

Hi All!
I am extending a basic IDoc and adding custom segments to it.I will be using change pointers to automatically initiate the ALE process when there are changes in the Master document.
Please anybody give me the process to follow.Is programming necessary for the extended IDoc to retrieve data.If so please guide me with any pseudo code.
Thanks in advance
Prasanna Kumar

Hi
Choose SAP Menu ® Tools ® Business Communications ® IDoc Basis ® Development ® IDoc types . The IDoc type editor is displayed.
If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select Request ® Create and reply to the questions which appear on screen. By selecting you can return to the IDoc type editor.
Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose .
The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.
Choose one of the following options:
Create New: Create the extension without a reference.
Create copy, which you can then change if necessary
Create as successor: Note that only one successor is allowed per release for each extension.
Select the basic type which is to be combined with your extension. Confirm your entries.
The basic type is displayed as a tree structure. See the color legend (Utilities ® Color legend).
Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose . You must now assign attributes for these child segments:
Mandatory segment (indicator): Must data be written to this segment in the IDoc?
Maximum and minimum frequency of use: How often may/must a segment occur in the IDoc?
You can add further children or "grandchildren" to this or any other reference segment in the basic type.
When the new extension is complete, you can save your entry.
You should keep the following factors in mind when dealing with extensions:
Segments must not explicitly occur more than once in the IDoc type - this means that the extension cannot have any segments which already exist in the basic type. This also means that a successor must not have any segments which already exist in the predecessor.
Parent segments of predecessors must remain parent segments in the case of successors.
Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.
In the example call your extension Z1ORDERS . Append Z1TEST1 child segment to E1EDP19 reference segment in ORDERS01 basic type. The child segment can be used only once.
regards
Prashant

Problem in ALE config

Hi all,
Ihave created 2 logical systems gir800 , gir810 in the same server for the clients 800 and 810,when i am trying to configure ALE while running <b>Generate partner Profile</b>, i am getting the Error
<b>Port could not be created
RFC destination GIR800 not specified for system GIR800
Enter the RFC destination and restart the generation    </b>
Please let me know what could be the Problem,
I checked SM59 everything is ok,
Help me with the solution........................
Thanks,
Girish

Hi Girish Kosuri
Just follow the procedure
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
STEP 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
     -System Name : ERP000
     -Description : Sending System
        -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
STEP 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
STEP 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)
STEP 5) Goto Tcode BD64
     select the modelview
     goto >edit>modelview-->distribute
     press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
     Material : mat_001
     Message Type : MATMAS
     Logical System : ERP800
     and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
     Material : 100-300
     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
Good luck and Reward me for the same
Thanks
Ashok.N

Small Doubt in ALE config

Hi,
Iam reffering this blog to do ALE settings
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
If i completly follow this Blog means , Is there is any need to do in WE20 & WE21 entries ????
Instead of doing through this blog can i do in this way....
1) Create LS in SALE
2) Create RFC Destination in SM59 with the above created LS name
3) Create WE21 Port
4) Create We20 Partner Profile
Is this way is ok rather than going in the Above mentioned Blog.
What is the difference between these Two Approches
Regards

Hi Vamasi,
After creating distribution model, you can generate partner profile automatically by just one single push button. It avoids our manual process of creating partener profile.
However you can create partner profile manually as well using WE20 / WE21. But in both cases you need distribution model if you want to send message to XI system.
"Generate the partner profiles by selecting the navigation path from the main menu, Environment --> Generate Partner profiles " --> Will make life easier by auto. generating profile for you base on distribution model parameter. ( Just one click n everything would be done).
Both are doing same thing.
Hope this will ans. your query.
Thanks,
Nilesh

ALE config & Idocs

Hi All,
I have a requirement to Transport Idocs from XI server to ECC-R3 server(Both are Different Servers).
I need help in creation of Logical Systems, Ports and Partner Profile Creations.
Before that i have few doubts,
1. What is the Significance of "Assigning Logical Systems to Client?"
2. What is the Significance of the "Customer Distribution Models?"
Now my questions?
1. How many Logical Systems must i have in ECC-R/3? Do we need to create any LS in XI server?
   similarly how many Ports and Partner profiles i need to create in both ECC and XI servers.
   Actully Inbound Process runs in ECC by using a Process Code(It drives our custom FM).
Thanks in Advance,
Sekhar.J

Hi,
Lets Take everything One by One:
1. What is the Significance of "Assigning Logical Systems to Client?"
*Answer: Logical System is nothing but a Name assigned to a Client for Data Transfer, which will be used as the name of Sender or Reciever System.*
2. What is the Significance of the "Customer Distribution Models?"
Answer: CDM is generally required when you have Multiple Recievers for your IDOC, and you want to have ALE/IDOC settings for all Recievers in a central place. You achieve the concept of segment Filtering & IDOC reduction via CDM.
I need help in creation of Logical Systems, Ports and Partner Profile Creations.
*Creation of Logical Systems:It can be defined by TX code BD54. Just enter the name and description of LS.
Creation of Ports: Go to transaction WE21 to create a port which will be used for transferring the data.
Creation of Partner Profile: use Txn WE20.*
Now my questions?
1. How many Logical Systems must i have in ECC-R/3?
    Only One
Do we need to create any LS in XI server? No
similarly how many Ports and Partner profiles i need to create in both ECC and XI servers.
Only One Port & Partner Profile in XI server.
Thanks,
Ajay

ALE Config Problem

Hi Guru
I have two SAP System ,
1. MOP client (100) and 2. PQR Client (200)
MOP system sending Idoc to PQR. There is no Idoc is flowing from PQR to MOP.
Now my Question is
In PQR system Config Require
In defined Logical System PQR in PQR System
now in Assignment part of Logical system
I need to assign PQR to client 100 or Clent 200 ?
Regards
RJ

200.
Your partner profile in the MOP system will have an outbound LS partner representing your PQR/200 system. This name will match the setting you made in BD54 for your logical system. The message type that you add to the profile will point to a receiver port which has an RFC destination assigned. The RFC destination will point to your PQR/200 system.

T-codes for ALE config

Hi experts,
can anyone help me with T-codes for configuring ALEs.

hi,
check the below links you will find good material along with all the tcodes and examples
http://www.erpgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://help.sap.com/saphelp_nw04/helpdata/en/78/217da751ce11d189570000e829fbbd/content.htm
if you find it useful plz mark the points
Regards,
GNK.

Ale Config! Help Needed!

Hi Guys!
Pls look at the diagram below,
Service Receiver Service Provider
P.order -
>Sales Order------|
Order Confirmation<----
|
P.order Change -
> Sales Order Change
Invoice Receipt< -
Invoice
Reverse Invoice Receipt----
> Cancel Invoice.
Here, Two logical Systems Service Provider & Service Receiver
Two Clients
Here 4 transactions taking place, according to my knowledge ( p.order, order confir, invoice receipt, cancel invoce) between two systems.
( pls correct me if i am wrong)
Questions?
1) I want to know for these 4 transactions how many port definitions & Distribution model has to set up in both the systems.
2) What about Partner profiles is it same for the 4 transactions .
Pls Explain me briefly.
Pls correct me if i am wrong.
Thanking You all for your Answers in Advance
Rahul.

Hi,
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
Thanks
Naveen khan

Purchase Order Download ALE Config for automation

We need to automate the current PO idoc creation message download whenever a PO is created , changed or deleted. We have set up an output type Z005 for it and manual creation of idocs from the Purchase Order works fine. We need to automate it though. We have used the transactions NACE, VK01 and MN04 but the PO download message ORDERS is not triggered automatically.
regards
Aveek Ghose

Hi Aveek,
You first have to check if the output type you have customized for the Purchase Orders is triggered. So create a PO and check in the message determination that your output type is triggered. If it has been triggered save the Purchase order and re-enter the purchase order to check the message has been processed succesfully (yout output type should be "green" now).
Regards,
John.

ALE Config

Similar Messages

Maybe you are looking for