Diiferent user for RFC call

Hi All,
Can we have use different user IDs to make RFC calls to SAP? Do we have option to call RFC using different users like DEV1, DEV2 etc which is specific to the user logging in to MII. This is required to maintain the change history record while posting data back to SAP
As per the current set up its always user which is configured in SAP server editor in MII, makes the change in SAP.
Any input is appreciable
Thanks in advance
Namita

Ajay,
It is like passing any other parameter to your BLS.
For example :
1.In your BLT, create 2 trx params
UserName,Password.
In your Jco Action Block assign these params in the Links Tab of the action.
2. Create a xAcute Query Template wrapping this BLS transaction.Set Param1 as UserName and Param2 as Password.
3. Now in your frontpage screen, create an iCommand applet wrapping the above xAcute Query Template.
4. In your screen have 2 input fields to enter username and password.
In the "OnClick()" event, use the setParam() method to set the values from the Input fields.
Hope this helps. I do not have the resources to give you the code but i think this should work. Let me know if this helps,
Thanks,
Ram

Similar Messages

RFC Adapter Receiver - change SAP User for each call

Hi guys,
I need to create one connection between PI and SAP, all right, i can use RFC Adapter Receiver, no problem.
But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
Can anybody help me, please?

hi,
>>But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
sure we can help you but no in this way:)
it is possible to change the user for RFC adapter but using
principal propagation:
/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
this is the way you need to go and not send password in XML payload
(this is certainly not the way and no client will approve it)
why use a password is anyone can see it ?
Regards,
Michal Krawczyk

Which user type to user for RFC receiver channel

Hi Forum,
I m developing XI scenarios which include RFC receiver chhanel (in IB: Integration Directory), to call a function moule in a R/3,
which kind of user should i use for this purpose, i mean to say,
which user type:
                SYSTEM
                Dialog
                Communication
                System
                Reference
and what should be the roles of that user,
which type of the user doesnt gets locked, on wrong attempts

Hi,
Generally S_RFC and S_SERVICE authorizations are nedded while calling RFC module from R3. Also check for role S_RFC_ADM
The backend should have the authorization to execute the RFC on the backend.
You can test the module in R3 and create a role using PFCG assign the tcode - SU53 (authorization check) and also assign the S_RFC and S_SERVICE to role.
Refer
RFC Logon user authorizations
Question on service userid - for RFC call
End User Authorizations and Roles
Calling R3 RFC via http
For RFC different authorization object is requried. You can ask your basis team to add the relevant authorization object in a new role and then add the new role to any existing service user or better create a new system user and add the role.
Thanks
swarup

Login information for RFC call

Hi there,
I would like to know if there is a way to authenticate a user via bsp and get that login information to make the RFC call to different systems.
i tried the to call an FM via RFC directly from abap and it forces me to login and it works but when i put that code to bsp. I just get a "page cannot be displayed" error.
I know i can enter an ID and password on sm59 for the connection but i need to let the user login
I am using this for a user creation tool.. instead of using su01 to create a user it will be done via bsp and would like to reflect the changes done when running the reports from SUIM
thanks in advance
Ryan

Hi Ryan,
I will assume your RFC Destination already trusted system and using current user logon (see my previous reply).
However this still prerequisite for the next step.
Now, please correct me if my understanding is wrong.
In your reply, you have at least 2 System, right?
S1 & S2.
Where S1 has BSP Application (Ex:/ FormRegistration)
And S2 is where you control the user and Function Module.
Do you put, generic user for all BSP Service in System S1?
You can create another BSP Application in System S1 (Ex:/ CallingFM)
but this time don't put default user in BSP Service.
And from BSP Application FormRegistration, you create 1 button to call the BSP Application CallingFM.
I will give you sample code:
FormRegistration: address:http://systemS1.sap.com/FormRegistration/page1.htm
HTML Part:
===========
<HTML>
<input type="button" value="Register the user" onclick="submitUser();">
<script>
   function submitUser(){
       document.forms[0].action = 'http://systemS1.sap.com/CallingFM/page1.htm';
       document.forms[0].target = '_new';
        //it will open new window, just put it empty if you don't want to open new window.
       document.forms[0].submit();
</script>
</HTML>
Now, when user click Button "Register the user" it will open the new window.
But because it doesn't allow you to using default user, it will prompt user id and password.
After that it will submit the data to CallingFM
Now in CallingFM we already have the sy-uname = user-B.
CallingFM: address-> http://systemS1.sap.com/CallingFM/page1.htm
OnInputProcessing Part:
=================
call function 'zcreate_user' destination 'S2'
Why you need CallingFM BSP application? because you need to re-assign sy-uname in S1 from default user with user-B ID, and use it to connect to System S2, S3, etc.
Please note: SM59 and User Id must be set before this.
Because when you call RFC from other destination, SAP will refer to Logon setting in SM59 for that destination.
Hope this will help you.

Question on service userid - for RFC call

Hi
In XI 3.0 SP18 , we are making a RFC call from XI mapping runtime - to XI's ABAP stack - RFC function module . In the RFC receiver communication channel , I tried using service user XIISUSER , XIAPPLUSER for this RFC call - I got short dumps on XI ABAP stack mentioning that these two service users do not have authorization to make RFC calls -
Does anybody out there know what service user on XI has RFC call authorization that can used to make RFC calls onto XI ABAP stack from its mapping runtime ?
Correct answers will be rewarded rightaway. Thanks for your time in advance.

Hi,
u have to make entry in sld...
Hi,,
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
The Client must be the client number of the backend SAP system.
Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
Double-click on the business system in the Integration Directory.
Switch to Edit mode.
Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
The RFC Destination is from step 3.1.
The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Reward points if find useful.

ROLEs for RFC call

Hi all,
Is there any specific role, that should be assigned to the USER, so that he can make RFC calls to BAPIs.
Or by default any USER can make the RFC calls to the BAPIs. For example, I am writing a Java/JCO appliation to call BAPIS. The current user I am using has all the permissions (I guess).
Thanks,
Nagarjuna.

Your basis admin should be able to tell you. I know that it would be included in SAPALL. I can't really say, because it can very from system to system.
Regarsds,
Rich Heilman

'Classic' RFC library - password limited for rfc calls ?

Hi ,
we are using the 'classic' RFC library to connect to SAP for calling RFC function modules. Due to the fact that there are often older SAP systems involed, we use only passwords with 8 digits. But now we have the requirement to use passwords for the rfc user with more than 8 digits. According to my todays knowlede, the password is limited to 8 digits with the standard rfc lib.
Can the newer SAP NW RFC lib handle a password with more than 8 digits ?
But am i right that the SAPNW RFC lib is unable to handle rfc calls with opening a SAPGUI ?
thx
Heike

Hi,
thank you for your answer!
I have investigated something new yesterday:
I thought at the beginning, that the problem just occurs, when the system work processes are reached. The system has for example set up 15 dialog processes and the external server is calling the function 20 times in parallel. Then we normally need 5 dialog processes more. The system is taking then all 15 dialog processes and the locks got stucked.
That means, that I´ll maybe only get 4 or 5 uploads, which have really been updated the tables. All the others couldn´t get the table locked for their process.
But if I now let the server call the function just about 13 times in parallel, nearly all uploads have been updated the table!
From my point of view, the lock from SAP gets stucked, when the limit of dialog processes is reached. It´s not working in the right way anymore...
The same is happening, when you set up in the system, that only 10 work proecesses can be used by RFC. If I have more than 10, it´s going to be critical with the locks....
WEIRD!
Can anybody help me out of trouble?
Thank you!

Switch user in RFC call

hi @ all,
i´m faced with the following problem and could not find a solution yet:
we are building an externel SAP-addon-application that uses SAP as data store. the connection is done via RFC-calls. in the normal scenario we have a typical client-server-application, so all RFC´s are done in a named user context (similiarly to SAPGUI).
the challenge now is that we ar planning to build an application server that communicates also to the SAP backend. due to performance issues we want to keep a configurable amount of open connections (some kind of connection pool). every request from a client should now be redirected to the SAP-backend using one of the open sessions in the real user-context. if there is no open connection for the required user we would need a way to perform a user-context-switch.
we already did some tries with the function SUSR_INTERNET_USERSWITCH. but we couldn´t find the desired result because there is no way back once the switch from service-user to dialog user was done. so another switch won´t be possible.
we dont want to keep a specific session alive for every user on the application-server because they are not needed highly frequent (from one users view).
does anyone know a way to solve my problem?
thanx,
thomas

HI, Eric -
...The Idenity Cerificate is not yet valid...
Check the date setting in the Date & Time control panel. If the date has reverted to something in the past, reset it. This could also indicate that the battery in the machine needs to be replaced.

Best approach for RFC call from Adapter module

What is the best approach for making a RFC call from a <b>reciever</b> file adapter module?
1. JCo
2. Is it possible to make use of MappingLookupAPI classes to achieve this or those run in the mapping runtime environment only?
3. Any other way?
Has anybody ever tried this? Any pointers????
Regards,
Amol

Hi ,
The JCo lookup is internally the same as the Jco call. the only difference being you are not hardcoding the system related data in the code. So its easier to maintain during transportation.
Also the JCO lookup code is more readable.
Regards
Vijaya

XML pay load for RFC call in java mapping

Hi,
I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
Say i have 2 import parameters(input1,input2) and one output(output1)......
Thanks in advance,
H.L.Babu

>
hlbabu123 wrote:
> Hi,
> I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
>
> Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
>
> Say i have 2 import parameters(input1,input2) and one output(output1)......
>
> Thanks in advance,
> H.L.Babu
have a look at this document - https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439&overridelayout=true
in case u still have issues do get back

Where used for RFC calls to different system

Hi,
I want to change the interface of a function module which exists in our XI system.
The function is called from R/3 in different places and hence will need to be changed in each location.
Is there an easy way of determining all the different calling points?
The only way I can see would be to run a text search utility against the code.
Thanks,
Alan

You cannot user SE37 and whereused list for this. due RFC available in XI and you need to check for R/3 for whereused points
Try to run the program RS_ABAP_SOURCE_SCAN and in the search string put your function module name and execute
( if it is a custom function module search. in the search pattern use all custom package names)
a®s
Edited by: a®s on Jul 14, 2008 9:24 AM

Target system(Destination) for RFC call ?

Need some help in calling an RFC for xi interface.
For triggering the data in to xi , RFC needs to be called. This RFC can be called using an ABAP Program / report . BUT inorder to call that RFC a Destination / Target system needs to be defined . Even though RFC destinations can be managed by transaction SM59 what will be the target system for calling this RFC in a generic sense?
Like what destination i should be expecting this code : ?
REPORT Z_TEST.
CALL FUNCTION 'ZFunctest' destination ????
Please suggest
Krishna

Yes i now understand the scenario : well is this statment correct ?
When we say like this :
CALL Function 'ZTEST' Destination SIDCLNT015
does this mean ZTEST should be there in destination system ? which means the RFC i am writing should be there on xi systems whose system id is SID ?
As i heard some where that ZTEST should be there on targetsystem i call for ?
Please suggest
Krishna

Which paramter configures the timeout for rfc call (to R/3 ) from BPM

hi froum,
i have a scenario, with BPM, in which theres a synchronous send to a rcf Function Module in R/3,
now, can u tell me which paramter decides the time out for this Sync call to rfc enabled Function Module in R/3,
i mean which paramater in SXMB_ADM or anywhere else that dictates the time period

Check this out, RFC adapter section
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards,
Prateek

Configuring WCF-SAP for RFC Call

Hi,
I want help in configuring the WCF-SAP adapter in a receive port.
I have done configuration set like below:
But when SAP calls RFC then I am getting below error in application log:
Thanks, Girish R. Patil.

Examine the non-resumable message in your Group Box. It will reveal the Context Properties of the message from SAP that the Publish/Subscribe engine tried (and failed) to find a matching subscription for.
After examining the message, create an Orchestration and/or Send Port that subscribes to some of the Context Properties.
Also: Remember that if your subscriptions require message type or you have Map(s) on your Receive Port, you need to use the XMLReceive Pipeline and not the PassThruReceive.
Morten la Cour

Message mapping transformation error for RFC calls

Hi,
I am having a weird problem. recently client migrated the server and we started getting all possible errors in XI which we are able to fix. Now we have a strange problem in quality system alone where the bapi calls are made from QA11 and MIGO. The bapi call from MIGO is sucessfull but from QA11 it fails with below error
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_MP_RFC_PROXY_GOODS_RECEIPT_:
RuntimeException in Message-Mapping transformatio~
I checked in development system and production where it is sucessfull but in quality its failing. I checked the cache and refreshed for confirmation and checked the trace and log files but couldt find any solution. The call made from a test report is also sucesfull but only bapi calls from QA11 are failing.
Note: i am using same bapi in MIGO and QA11 and the integration is same as well. There is no difference in data between 2 transaction just the trigerring point is differenct.
I tested my message mapping, interface mapping and configuration as well with sample payload and they are working fine.
I checked SDN and saw that similar issue is faced by others but no solution is provided.
Regards,
Jayaram
Edited by: JAYARAM MAGANTI on Jun 9, 2009 1:14 PM

Hi all,
Has anyone ever faced this issue?
i tried all the options that i think of and as a last attempt even restarted XI engine though it makes no sense. but still i am having the same issue.
If anyone had come across similar kindly update the solution
Jayaram

Diiferent user for RFC call

Similar Messages

Maybe you are looking for