Doubt in ALE config

Hi
I have created the process code for the function module. How do i associate the module in the configuration.

Hi Niranjana,
Can you pls. elaborate your problem?
Pls. refer to this link
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
This has the step by step procedure for IDoc Configuration with screen shots
Regards,
Chitra

Similar Messages

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

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

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

Doubt in ale/idocs urjent

hi,
i have a doubt in ALE/IDOCS requirement is add a field to segment
in tcode BD53(reduce message type) after adding a field.
what configuration i need to do.

welcome to SDN.
Post this ABAP forum for quicker response.
ABAP Development
Regards
Raja

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

Doubt in ALE

hi all
In ALE configuration, how may logical systems we have to create?
As per my knowledge 2 logical systems will be created.is it not?
But we r sending the data ,so one logical system(destination) is enough, to send the data to destination. ...
please clear my doubt , with example

Check the link below:
http://www.atomhr.com/know_preview/ale_logical_system.htm
Logical System
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/5aa2a0deb91548a1842f8485dee4a2/frameset.htm
Setting Up a logical system
http://help.sap.com/saphelp_nw2004s/helpdata/en/b4/b0b13bb3acef3ce10000000a11402f/frameset.htm
Securities of Logical system
http://help.sap.com/saphelp_nw2004s/helpdata/en/56/98a340f590a35be10000000a1550b0/frameset.htm
Assigning Logical Systems
http://help.sap.com/saphelp_nw2004s/helpdata/en/cb/0f3040cbe60d418d7b4373c0cbf84a/frameset.htm
Assigning Logical Systems to client
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/b4b13b00ae793be10000000a11402f/frameset.htm
Regards.

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

New to SAP...Doubts regarding ALE.

Hi all,
I am new to SAP.
Can any one please explain me the following.!
What is the difference between EDI and ALE?
What is Logical system, Port, RFC destination, Customer Distribution Model, Partner Profile, Message type, Message control and if any of the important terminology that I have missed in the ALE concept?
Please help to explain me clearly in detail as I have no knowledge reg these and tried searching for info in various links, but still found difficult to understand?
Many thanks in advance....
Regards
Nani Ancha

ALE/EDI
Purpose
Electronic Data Interchange (EDI) and Application Link Enabling (ALE) are used for exchanging business data between different systems.
For both these forms of communication, you require the IDoc Interface. The IDoc interface is made up of the definition of a data structure and the processing logic of this data structure. The data structure is the IDoc. The IDoc is the general exchange format of the communicating systems. IDocs can be sent using different methods (for example, Structure linkRFC or as a file).
Application Link Enabling (ALE)
You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems. ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
· ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor). The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12). This enables communication with non-SAP systems.
· By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message.

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.

Basic doubts in ALE/IDOC processing

Hi All,
1.How are IDOC Type and Message Type related? Many to one or One to Many?
2. what is the prominence of msg code and msg function in ALE outbound processing?
3. During outbound processing what is the startegy followed by the ALE service layer to pick up the customer model?
It would be great if any one can answer these questions in plain words rather than referring links. Reward guaranteed.

Hi Ravi,
1.Can'te we assign more than one IDOC to the same msg type if the IDOC's are of different versions?
Yes we can. Doesn't SAP do that? For example, ORDERS01, ORDERS02 ... ORDERS05 are having the same message type ORDERS. You can also create your own IDoc type or extend the standard IDoc type.
3. When we run a stand alone program to trigger IDOC processing the only mandatory field will be the message type, so how can the sending system identify the receiving system?
You need to setup partner profile (t/code WE20) and distribution model (t/code BD64). Once this configuration are done, The system will populate automatically the IDoc Control Record for sender and recepient system information when the IDoc generated based partner profile setup.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Doubt in ALE/IDOC's

Hi Friends,
    I have 2 inbound idocs in which
     one idoc posts the document in SAP
     seecond oneconfirms that document.
what my problem is if the second idoc comes first and try to confirm before the documnet posted it gets fail. SO that i want this confirmation to be done only after the document is posted. How can i achieve this.
Thanks& Regards,
Naren.

hi,
there is an excellent concept in ALE called <b>SERIALIZATION</b>.
1. goto transaction code SALE.
2. MODELLING AND IMPLEMENTING BUSINESS PROCESS -> MASTER DATA DISTRIBUTION -> SERIALIZATION FOR SENDING AND RECEIVING DATA -> SERIALIZATION USING MESSAGE TYPES
3. what u actually do is,
<b>example :</b>
let us say IDoc1 is of message type CLFMAS, IDoc2 is of message type MATMAS. now u configure in the path given above that, MATMAS should be received first and CLFMAS should be received next. this is known even to the partner.
this is how u correctly receive IDoc in the sequence.
hope it helps.
reward if useful...

Doubt in ALE config

Similar Messages

Maybe you are looking for