ALE Configuration issues..

Hi,
I am trying to set up ALE configuration between two SAP systems. I have defined partner profile(WE20) in sender system, there is a tab 'Post processing : Permmitted Agent', I have chosen type as User and agent as system user Id. I would like to know on what basis value of type and agent should be chosen?
I have another query....I am sending Idocs from one system to other. I am defining control records in a program in sender system. In control record I have mentioned sender port name(sndpor), sender partner number(sndprn) and sender partner type(sndprt). I would like to know whether i need to mention receiver port number(rcvpro), receiver partner number(rcvprn) and receiver partner type(rcvprt) ?? Please note that I am not receiving any data to my system but only sending Idocs to other system.
Thanks.

Hi,
in the sender system you will have to define the sending options
In the receiver system you will have to define the receiving options
that is the partner profile.
if you are not useful with this, you could play with BD64
In WE20, you specify with this partner (the system receiver) I will send this kind of data.
In the receiver system, in WE20, you will specify with this partner (the sender) I will received this kind of data
so if you send other things, the receiver system will refused it
You could also specify the system in some transaction, for example BD10 for material, but if the WE20 customizing is missing, the system will don't do anything
regards
Fred

Similar Messages

Issue with ALE configuration for creating the idoc for Purchase orders

Hello,
I am trying to send the purchase order through message type configuration using ALE.
I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
I have done ALE distribution using BD64.
Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
In NAST table, the entry is there but on executing RSNAST00 nothing happens.
Please provide me the pointers to solve the given problem.
Regards,
Mayank

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

ALE Configuration Again !!!

Hi All,
I am trying to do ale configuration for idoc to file scenario. I created two RFC connection one for XI system and one for R3 system. Then I created ports for both the RFC. After that I created two Logical system having same name as the two RFC above. But as per the instruction , i should assign client to above logical system. But problem is that the client number ie 030 is already defined to R3 system. My XI system have same client id, so when i am trying to assign client 030 to XI logical system, it is giving as client number is already present. I don;t understand the logic of assigning client to LS.
what should i do here?
Second thing: Can we create more than one logical name for the same system. I asked this because in the RFC list of R3 system, i already have RFC for R3 system , logical name is also present. So can i create another logical system for R3 system?
Ranjeet Singh.

An excerpt from SAP documentation on Logical System Names.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: <System-ID>CLNT<Client>. Refer to url
http://help.sap.com/saphelp_nw04/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
SCC4 should already have been set. So I assume that you are creating your logical systems in the IMG to then assign in WE20 (Partner Profiles). As the XI SystemID will be different to your R3 SystemID, CLNT should not be an issue.
If not then please clearly define the issue to include where you want to create the logical system and which way your IDOC will travel. We currently send IDOCs from CRM to XI and vica versa

Help required in ALE configuration

Hello All,
I am working on SAP Demo version. I have created a logical system and saved it.
After defining logical system i tried to create a distribution model but i don't see any logical system in the distribution model? Can anyone help me in this issue.
Regards,
Lisa

<<Posting list of links is not permitted. Please do not do it again. Further violations can result in points being deducted, or your account being deleted>>
Hi,
Refer below links.
Re: tell me about ale configuration
reg:ALE Configuration
Re: ALE and Idocs configuration
Re: ALE Configuration
Regards
Md.MahaboobKhan
Edited by: Matt on Jan 19, 2009 7:38 PM

ALE configuration for Outbound Idoc - Help me

Hi Experts,
I am newbee in SAP and XI. I was trying to send MATMAS Idoc from R3 and i was running into some issues. So i would appreciate if someone can help me.
I am using following link as reference. /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I did all the steps mentioned in the above link ( Creating Logical Systems, Assigning Client and RFC destnations, Creating distribution models ..... etc)
and then everything went well and i saw success messags in all the steps.
I used BD10 to send material and it went well. But when i check TRFC queue, i see some error messages; "No service for system SAPRDI, client 800 in Integrion Directory"
And all the messages are hanging in the TRFC queue.
Note: I havent configured anything in XI yet. I wanted to make sure IDoc gets to XI client first.
Thank you in advance. Pls help me its very urgent.
Thanks,
Surya

I created RFC destination (SM59) and Port (IDX1)
Then i sent another material (BD10) and checked tRFC queue. i found bunch of error in the Queue.
1.connection to host 10.4.23.120, service sapgw00 timed out / CPI-C error C
No service for system SAPRDI, client 800 in Integration Directory
partner not reached (host 10.16.176.29, service sapgw00) / CPI-C error CM
connection to host 10.16.136.127, service sapgw58 timed out / CPI-C error
Note: i have noticed entries for R3 in SLD as below
System Name: RDI ( not SAPRDI as mentioned in the error message)
System Home: r3ides
That might be reason. If so, how to change it in R3 box? Any suggestions?
Please send me if you guys have any links or docs to address this issue.
Thanks,
Surya

ALE Configuration Questions

Hello Experts,
I have a few questions regarding ALE Configuration, help appreciated
1) Is it necessary to create user for ALE transfer in both sender and receiver system ?
2) Is it necessary to create logical system for both sender and receiver in both the systems ?
3) Can tRFC created in sender system have a different port name than the logical system name ?
Is it ok, if only configuration is done in the sender system, if I am looking for one way transfer of Idocs from sender to receiver ? The receiver will receive the Idocs and process internally, sender is responsible only for sending in my case.
I have referred the below link,
7 Steps For ALE Configuration - ABAP Development - SCN Wiki
Best Regards,
Ameya B.

Hi Mili,
You do not need to generate partner profile during the ditribution model view process (BD64). You can add manually the partner profile via WE20 for inbound and outbound parameters. As long as distriburon model has been setup and distribute, you can continue the next step for example generating IDoc and so on.
Sometimes, you may face an issue to generate partner profile from BD64 for some reason. I found by generating manually partner profile always quick, safe and stay away from any trouble shooting for an error.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

ALE Configuration error

Hi,
I did the ALE configuration in sending and recieving system like creating LS,Assigning LS to Client,Model View For Message type,ports and partner profiles.
When i was trying to distribute the model view it is giving error:
RFC Destination not configured or partner profiles not generated.
I can remote logon from sender system to reciever system and vice versa.
The partner profiles are created for the LS Sender and reciever.
So can any one help me on this issue.
Thank you.

Hi Mili,
You do not need to generate partner profile during the ditribution model view process (BD64). You can add manually the partner profile via WE20 for inbound and outbound parameters. As long as distriburon model has been setup and distribute, you can continue the next step for example generating IDoc and so on.
Sometimes, you may face an issue to generate partner profile from BD64 for some reason. I found by generating manually partner profile always quick, safe and stay away from any trouble shooting for an error.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Got error in ALE configuration

hello experts
              I configured a ALE.when i tried for connection test its giving the below error.i checked all the information given in the ALE configuration is correct.but got the below error every time.
connection to host timed out / CPI-C.
ERROR                connection to host timed out / CPI-C.
LOCATION             SAP-Gateway on host DETAIL               NiPConnect
COMPONENT            NI (network interface)
COUNTER              2701
MODULE               nixxi.c
LINE                 805
RETURN CODE          -12
SUBRC                    0
RELEASE              620
TIME                 Thu Mar 23 12:42:38 2006
VERSION              36
can anybody resolve it out.
Thanks in advance........
Regards
Ravinder

Hi Ravindra,
This is a network connectivity issue.
Please make sure that the ip address of the target system is correctly maintained in SM59 and that the Connection type is R3.
When you say that you tried a connection test, you mean through SM59 right ?
Regards,
Urmila

Single Transaction code for ALE Configuration

Hi All,
I want to Know is there any Single Transaction code for the ALE Configuration instead of going through SALE, WEDI t-code or with defining logical systems assigning them to clients, creating RFC and Distribution Model, generate partner function and..so on.
Please let me know if there is any t-code through which i can do the ALE configuration in a single T-code.
Thanking you in advance,
Bhanu

hi ars
i got a task saying that message type is DESADV01 ,but u told that DESADV01
is basic type,can i know the difference.
regards
sagar

Configuration Issue in User Mapping ..

Hi,
Pls help resolve this issue..
When i go to " UserMapping " option using the "Personalize " link , i get the following error msg..
"There is a configuration issue which leads to problem when accessing user mapping data for the selected backend system"
Also , if i go thru "User Administration -> User Mapping "
then it says,
--"There is a configuration issue which leads to problem when accessing user mapping data for the selected backend system .
Usually reason is user mapping being configured for Strong encryption, but necessary additional files might be missing.Check Security log file for information "--
I am not able to solve this problem..Pls help
Thanks in advance

Hi Venkat,
Here the quick and dirty solution:
In your portal go to 'System Administration' -> 'System Configuration' -> 'UM Configuration' -> 'Direct Editing'.
There locate the parameter 'ume.usermapping.unsecure', set it to 'TRUE' and restart your server.
I would rather recommend to install the unlimited strength jurisdiction policy files.
For more info on this, check this thread:
JCE Jurisdiction does not allow Portal to start
Hope this helps,
Robert

Configuration issue of syslog.conf

Dear All,
My client is facing a configuration issue of syslog.conf.
They have set a cacti on a Linux server for monitoring of all servers snmp & syslog.
The part of snmp has set up successfully but cannot send the syslog to the cacti.
My client want the syslog can keep on the localhost and send to cacti for monitoring
we have tried to do the following things for make it work:
Insert the information (*.* @10.251.99.74) in /etc/syslog.conf
Restart service of system-log
Deleted all word of loghost in the /etc/hosts file
But still not work. Anyone can give me suggestion or idea about this?

Thank you for your reply.
It is tab. But I think the problem is solaris cannot use *.* to represent all logs.
I have used the following is work
*.err;ker.debug;daemon.notice;mail.crit @10.251.99.74
If that is not the mail reason, please put me right.

Anti-relay filter configuration issues

Configuration issues with the anti-relay filter in Messaging Server 4.1x.
The following information addresses common questions about configuration issues
with the anti-relay filter in Messaging Server 4.1x: 

<OL>
<LI>Question: 
What is the difference between the delivery
and submission
options? 

Answer: 
The submission option
allows specified users to send email to any email address in the world.
These users are typically internal users.

The delivery option
allows specified users to receive email from anybody. These users
are also typically internal users.

A standard filter will appear something as follows: 

# This is the anti-relay config file written by Jay at iPlanet
# The first section sets default conditions
resolvehostnames:0
useauthinfo:0
advertiseauthinfo:1
# This section sets domains to be delivered to by anybody
delivery:*@my.domain.com
# This section sets domains that can send any place
submission:129.12.4.*


<LI>Question: 
The delivery
option works properly. However, why doesn't the
submission option
appear to be allowing emails from specified users to pass through?

Answer: 
The problem with the submission behavior could be due to the setting of the
the resolvehostnames
parameter. If this parameter is turned on
(resolvehostnames:1),
then all entries in this configuration file must be fully qualified
host names. Although wildcards will work, you cannot specify IP
addresses with this configuration setting.


<LI>Question: 
Is it possible to allow people outside of my network to connect to the server
and send mail out?

Answer: 
Yes. To allow outside users to connect to the server and send mail
to any address, without granting the same privilege to the rest of the world,
activate the authenticated SMTP portion of the filter via the
useauthinfo option.
Setting this parameter to "1" (i.e., useauthinfo:1
) will require a user who is not in a
submission address and who is attempting to send email to an address not in
the delivery range to authenticate with a user ID and password.
</OL>

For additional information on the anti-relay filter, please refer to the
Messaging Server 4.1 Administrator's Guide at 

http://docs.iplanet.com/docs/manuals/messaging/nms41/ag/ubefiltr.htm#1073677

Prashant:
Are you using a UBE filter to configure domain-based anti-relayinging? We had better luck with the anti-relay plug-in. There is some info on this (for 4.15) at
http://docs.sun.com/source/816-6044-10/ubefiltr.htm#1069973
You have to enable the plug-in using configutil, per the above. The anti-relay plug-in is controlled by antirelay.conf. Be aware that the pattern matching rules are very limited, and not well documented. Fortunately, the source code to the plug-in is included, and you can see what it is doing. To pass the tests we had to add a hard-coded test for a "%" in the source and recompile:
*** antirelay.c.orig Thu Oct 31 04:42:13 2002
--- antirelay.c Thu Oct 31 04:22:07 2002
*** 934,939 ****
--- 934,940 ----
* Weight must be non-zero to begin with so that matches on just "*"
* will work.
+ if( strchr(text,'%') != NULL ) return ABORT;
weight = TRUE;
for ( ; *p; text++, p++) {
if (*text == '\0' && p != '')
Not a really elegant hack, but we didn't need a fully functional regex engine.

ALE Configurations?

Hi All,
Currently i'm working on the following requirements. we are using TIBCO system as a middleware tool and it will ceate an IDOC which needs to be directed to R/3 system. As we have already imported the IDOC to the TIBCO system and then it will fetch the data from non-SAP system and creates the IDOC and sends it to R/3 system? I've done the following ALE configurations but got the error message as 56..."Partner profile is not define".
I've done the following ALE configurations at R/3 side.
1. Created a logical system and RFC destination for TIBCO.
2. created a TRFC port.
3. Create a Partner profile and linked the TRFC port.
4. posted an IDOC from WE19.
but when i checked the status of IDOC in WE02 its displaying an warning message with status code 56 "Partner profile is not define". and i think no need to do any ALE Configuration at sender side since the sender system is TIBCO.
pls correct me if i'm wrong. as one of my colleage suugested me to create FIle port instead of TRFC port?
regards
Faisal

HI
SAP R/3
R/3 to 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 (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.
XI to 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 (IDX1) ( Create port to get IDOC Meta data from sender system)
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) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Refer the below links for further assistance
4.create partner profile using idx2
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)
cheers

ALE Configurations in File to IDOC Scenario

Hi All,
We are doing File to IDOC Scenario.
ALE Configurations done:
R/3 Side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to XI.
2. Created port in R/3(using automatically generated port name) and assigned the RFC dest created above.
3. Created partner profile and assigned the ports to the message types.
4. Created Logical system
XI side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to r/3.
2. Created port using IDX1 transaction with port name starting with SAP<SID> and assigned the RFC dest created above. (SID of XI)
3. Unable to load metadata in XI.
Now we are unable to test the scenario as it provides an error message in MONI as "Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors".
Also Let me know whether the steps mentioned above are correct for the scenario.
Regards,
Nithiyanandam

Hello,
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 XI 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 #####+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.
With Regards,
Vidya.
*******Reward with Points if found useful

ALE Configuration for Transactional Data (Purchase Order)

Dear Experts,
I want to configure ALE for Purchase Orders(Transactional Data).
For that:
I have done neccessary Condition Records at NACE with necessary Output Type Configuration. Configured Port and Partner Profile with Message Types: ORDERS and ORDECHG (as Outbound Parametrs) .Assigned those Message Types against defined Sender and the Receiver at Customer Distribution Model . Configured Port and Partner Profile at the Receiver System also.
Now I have 2 queries.
i) Is this much of ALE configuration is enough for Transactional Data for communication between 2 systems or I have to do something more?
ii) For Master Data we configure Change Pointer(we can see field assignments against Change Document Object at BD52 for Master Data Messaage Types) . Is it necessary to configure Change Pointer for Transactional Data or it will autometically handled by the system(field assignments cannot be seen against Change Document Objects at BD52 for Transactional Data Messaage Types)?
Regards
Arnab

Hi kumar,
what Alexander said is absolutely correct .
from your second question no master data distribution configuration is required for the transactional data distribution.
let us know once if you face any problems.
~linagnna

ALE Configuration issues..

Similar Messages

Maybe you are looking for