SLD setup for UDF to RFC Call in XI

Hello,
I am trying to create a UDF that has an RFC Call to the XI backend and I have it working in my development system. But for some reason I cannot create the Business Service > Communication Channel > GeneratedReceiverChannel_RFC in my Assurance system.
I'm guessing it has something to do with a missing connection in my SLD but right now I can't see what could be missing. What do I need to create in the SLD to allow XI to appear as a business service?
Thanks,
Matt

Hi
you dont need to do anything in SLD
follow this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70d90a91-3cf4-2a10-d189-bfd37d9c3231
infact there is another way (from what is explained in this doc), even without importing the RFC in IR/ ESR
more info
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35
Regards
Vishnu

Similar Messages

SLD part for SOAP to RFC

Hi,
Can any one give me the settings that are to be made under SLD.
i mean what needs to be done for technical system and for business systems ...steps to configure technical and business systems for both sender and receiver.
no links please
Points immediately rewarded.
Thanks

HI,
You need to create Sender and Receiver Technical system as well as Business system
For Communication of RFC i.e. with R/3 you can use th Technical system and Business Systems. For SOAP ie.e web application you can go for Business Service also that to be created in Integration Directory.
In SLD,
1. Goto Technilca Landscape and Create new Technical system by giving all server connection detials
2. Then Create the Business Landscape
3. Assign the Product to Technical landscape so the Software components related to the Product will refer to the Technical and Business systems
Registering a new technical system in SLD - ABAP based
/people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
Thanks
Swarup

Recommended SLD setup for NWDI

I have been looking at the SLD planning guide and noticed a few scenarios listed there. Does anyone here have recommendations.
The one that looked good to me was the 2 SLD (1 for DEV and QAS) with NWDI connected, and another (1 for PRD).
I was wondering if NWDI is only connected to a non prod sld, will this be a problem when you want to migrate objects to production?
Also from what I gather in this guide, it appears that NWDI can have its own SLD. Are there any advantages/disadvantages to this?
Thanks

Hi
> I was wondering if NWDI is only connected to a non
> prod sld, will this be a problem when you want to
> migrate objects to production?
No this will not pose an issue, the NWDI uses the SLD only during the configuration process. Deployments are done independant of your SLD configuration.
> Also from what I gather in this guide, it appears
> that NWDI can have its own SLD. Are there any
> advantages/disadvantages to this?
Yes this is an option too. Although this does not remind me of any advantages, other than the ease(to a very samll degree) of configuration.
> Thanks
Regards
Pran

Sld objects for SOAP to RFC syn.

Hai..All....
I am very new to Xi and i am doing a soap to rfc syn scenario..
pls give me a hint of what type of Sld object are required for the scenarion
like what should be the TS abd BSystem for the scenario and how many BS are required.
can it be done using a single BS for both the communications.
Dear experts i m waiing for ur responses.....
thx
simraan

Hi Simraan,
Can you please let me know the process flow.
Call to RFC is in the SAP system hence you need to create the Business system at SLD. You need to create the Business system and import it into ID and use that one.
Refer the below weblog for SOAP.
For SOAP you first need to generate the WSDL from ID and import that WSDL in IR external definition.
Refer the weblog for SOAP:
How to use webservices in XI
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
How to use SOAP adapter.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Refer the below weblog for RFC:
HTTP to RFC - A Starter Kit /people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
Thnx
Chirag

SLD setup for SneakPreview

Hi,
I have installed SneakPreview NW04. I need to setup SLD so that I can create JCo connection to my R/3 system. Can anyone help me with the steps. I dont find lcr roles available in the installed WAS Server.
Regards,
Gandolf S

<i>> There is a Blog on How-To execute steps.</i>
And here's the blog mentioned above --> <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2167">Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak</a>
Hope it helps.
Regards,
Norman

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

IDOC setup for SLD

Dear XI experts,
I woule like to ask you when I want to do the PI setup for IDOC sending and receiving in the SLD, as to what steps I have to take for this. I had done the setup and chosen ABAP as a choice in the Technical and Business system, however, I am not clear where I should define the Integration server to be able to choose this when I create a Technical and Business system and do the assignment of the Integration server.
Perhaps I need to do step by step the SLD setup for IDOC sending and receiving from SAP Backend and viceversa to find what I am missing.
Thanks for your input.
Best regards

Hello,
Check this blog "How To Configure IDoc Adapters" https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
It consist all setting including all steps required for SLD.
BR,
Dzmitry

How to loop through single XML File and send multiple RFC calls?

I am looking for the best approach to use for making multiple RFC calls (can be sequential) using a single XML file of data. I have been attempting to get a BPM loop working, but to no avail. My RFC only accepts a single set of delivery input and I have been told to try to work with it as is.
input xml sample:
<?xml version="1.0" encoding="UTF-8"?>
<ProofOfDelivery>
   <POD>
      <delivery_number>1</delivery_number>
      <carrier_name>UPS</carrier_name>
   </POD>
   <POD>
      <delivery_number>2</delivery_number>
      <carrier_name>UPS</carrier_name>
   </POD>
</ProofOfDelivery>
I need to make a synchronous RFC call for each set of POD data.
Thanks in advance!

Thanks for the inputs.
I tried with a BPM and multi-mapping transformation before a ForEach block. I am getting this error:
Work item 000000028028: Object FLOWITEM method EXECUTE cannot be executed
Error during result processing of work item 000000028029
com/sap/xi/tf/_ProofOfDeliveryMultiMapping_com.sap.aii.utilxi.misc.api.BaseRuntimeExceptionRuntim
Error: Exception CX_MERGE_SPLIT occurred (program: CL_MERGE_SPLIT_SERVICE========CP, include: CL_
Probably because I am not making/using the container objects properly. Here is a screenshot of my BPM. Can anyone spot my issue or point me to an example on this sort of container use?
[http://kdwendel.brinkster.net/images/bpm.jpg|http://kdwendel.brinkster.net/images/bpm.jpg]
Thanks

SLD Setup - Technical System

Hi All,
I need to send/receive data from the third party using SOAP adapter. in our environmnet we follow the SLD setups for third party.
Hence I would like to know what setup needs to be done in the SLD for this.
I think I do not need to create new product and software component.
Specifically when I am trying to create a new technical system the its asking for the system name and host name.
I beleive system name I can give anything . What about the host name ?
Is it the host name of the third party system??
Could some one explain me detail?
Thanks

H i
What about the host name ?
You can give the IP address or actual host name of the system you are trying to connect. it cannot be any generic name.
As mentioned above for soap based system , generally we use Business Service but yes if you can get all the details you can set up TS for non -ABAP based systems also . Whatever the details the TS wizard asks you to give , you have to get those details from your SOAP system admin .
http://help.sap.com/saphelp_nw70/helpdata/en/31/f0ff69551e4f259fdad799a229363e/frameset.htm
Have a look at http://wiki.sdn.sap.com/wiki/display/XI/WorkingwithSystemLandscapeDirectory+%28SLD%29 for basic understanding
Regards,
Srinivas

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.

Flat File-to-RFC question, multiple RFC calls for one file.

Hi guys,
I'm quite new to XI / PI and I have a question regarding a File-to-RFC scenario we're trying in NW PI 7.1.
We have a flat file which has two lines with two fields each, let's take this as an example :
001,001
002,002
The files needs to be converted to XML and then transferred to the RFC program which will update a table with the values above.
In the ESR I've created 3 data types (z_row1,z_record1 and z_fileinput1), 1 message type (z_file2rfc_ob_mt), 1 message mapping (z_file2rfc_mm), 2 Service Interface (z_file2rfc_ob_si and z_file2rfc_ib_ztestpi) and 1 operation mapping (z_file2rfc_om).
In the Integration Builder (ID) I've created everything required (The sender and receiver communication channels, sender and receiver agreement, receiver determination and interface mapping).
We're also using content conversion to convert the flat file to XML, this does seem to work because I see all the lines/field in the message when it gets into PI. The problem is that the RFC can only accept two fields at a time and only the first line gets updated. I see that only the first line gets sent to the RFC.
How can I make the RFC call for each and every line ?
Thanks !!

Create the RFC with table, which takes multiple lineitem as input and update the table in single call.
If you want response back then call RFC as synchrounous else in Asynchrounous mode.
By doing this in single call it will update the complete table.
Gaurav Jain
Reward Points if answer is helpful

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.

SAP adapter giving the merged result set (First RFC call data + Second RFC call data) for second RFC call

I have a WCF Adapter service to call a SAP RFC. When I call the RFC first time, it gives me correct no of result set but when I call this RFC second time immediately after first call, it gives me merged result set (First Result set + Second Result Set).
e.g. We have a RFC which receives vendor number and blank object of result set as parameter and gives back the list of purchase orders as Response in object of result set for that vendor.
Suppose, we have a vendor "a" and vendor "b". For vendor "a" there are 5 purchase orders and for vendor "b", we have 4 purchase orders in SAP. When I call the WCF adapter service for this RFC for vendor "a",
it gives me 5 purchase orders. Immediately after first call, when I call WCF service for vendor "b", it gives me 9 (5+4) purchase order records which is wrong.
In brief, one RFC call is affected by its previous call.
For each new WCF request, a new object of result set is created, connection is opened, rfc is executed and connection is closed.
Can anybody have any idea on this?
Thanks.
Thanks, Nishant Gupta

Hi，
Please refer to the document
http://seroter.wordpress.com/biztalk-and-wcf-part-vii-about-the-biztalk-adapter-pack/

Strange response time for an RFC call viewed from STAD on R/3 4.7

Hello,
On our R/3 4.7 production system, we have a lot of external RFC calls to execute an abap module function. There are 70 000 of these calls per day.
The mean response time for this RFC call is 35 ms.
Some times a few of them (maybe 10 to 20 per day) are way much longer.
I am currently analysing with STAD one of these long calls which lasted 10 seconds !
Here is the info from STAD
Response time :                10 683 ms
Total time in workprocess : 10 683 ms
CPU time :                               0 ms
RFC+CPIC time :                       0 ms
Wait for work process           0 ms
Processing time           10.679 ms
Load time                            1 ms
Generating time                   0 ms
Roll (in) time                        0 ms
Database request time         3 ms
Enqueue time                      0 ms
Number      Roll ins            0
                 Roll outs           0
                 Enqueues         0
Load time   Program             1 ms
                  Screen              0 ms
                 CUA interf.          0 ms
Roll time    Out                 0 ms
                  In                  0 ms
                Wait                0 ms
Frontend    No.roundtrips       0
                  GUI time            0 ms
                  Net time            0 ms
There is nearly no abap processing in the function module.
I really don't uderstand what is this 10 679 ms processing time especially with 0 ms cpu time and 0 ms wait time.
A usual fast RFC call gives this data
23 ms response time
16 ms cpu time
14 ms processing time
1 ms load time
8 ms Database request time
Does anybody have an idea of what is the system doing during the 10 seconds processing time ?
Regards,
Olivier

Hi Graham,
Thank you for your input and thoughts.
I will have to investigate on RZ23N and RZ21 because I'm not used to use them.
I'm used to investigate performance problems with ST03 and STAD.
My system is R/3 4.7 WAS 6.20. ABAP and BASIS 43
Kernel 6.40 patch level 109
We know these are old patch levels but we are not allowed to stop this system for upgrade "if it's not broken" as it is used 7/7 24/24.
I'm nearlly sure that the problem is not an RFC issue because I've found other slow dialog steps for web service calls and even for a SAPSYS technical dialog step of type <no buffer>. (what is this ?)
This SAPSYS dialog step has the following data :
User : SAPSYS
Task type : B
Program : <no buffer>
CPU time                       0 ms
RFC+CPIC time              0 ms
Total time in workprocs    5.490 ms
Response time               5.490 ms
Wait for work process           0 ms
Processing time             5.489 ms
Load time                            0 ms
Generating time                   0 ms
Roll (in+wait) time                0 ms
Database request time          1 ms ( 3 Database requests)
Enqueue time                       0 ms
All hundreds of other SAPSYS <no buffer> steps have a less than 5 ms response time.
It looks like the system was frozen during 5 seconds...
Here are some extracts from STAD of another case from last saturday.
11:00:03     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     13     13     0     0
11:00:03     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
11:00:04     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     16
11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     77     77     0     16
11:00:04     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     16
11:00:05     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     16
11:00:05     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     53     53     0     0
11:00:06     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     76     76     0     0
11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     20     20     0     31
11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     0
11:00:06     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     13     13     0     0
11:00:06     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     34     34     0     16
11:00:07     bt1sqkvh_PLG_18      RFC     R     0     USER_LECDIS     15     15     0     0
11:00:07     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     13     13     0     16
11:00:07     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     0
11:00:07     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     23     13     10     0
11:00:07     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     38     38     0     0
11:00:08     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     20     20     0     16
11:00:09     bt1sqkvg_PLG_18      RFC     R     0     USER_LECDIS     9 495     9 495     0     16
11:00:09     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     9 404     9 404     0     0
11:00:09     bt1sqkvh_PLG_18      RFC     R     1     USER_LECKIT     9 181     9 181     0     0
11:00:10     bt1fsaplpr02_PLG RFC     R     3     USER_LECDIS     23     23     0     0
11:00:10     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     8 465     8 465     0     16
11:00:18     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     18     18     0     16
11:00:18     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     89     89     0     0
11:00:18     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     75     75     0     0
11:00:18     bt1sqkvh_PLG_18      RFC     R     1     USER_LECDIS     43     43     0     0
11:00:18     bt1sqk2t_PLG_18      RFC     R     1     USER_LECDIS     32     32     0     16
11:00:18     bt1sqkvg_PLG_18      RFC     R     1     USER_LECDIS     15     15     0     16
11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     0
11:00:18     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     69     69     0     16
11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     49     49     0     16
11:00:18     bt1sqkve_PLG_18     RFC     R     5     USER_LECKIT     19     19     0     16
11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     15     15     0     16
The load at that time was very light with only a few jobs starting :
11:00:08 bt1fsaplpr02_PLG RSCONN01                     B 31 USER_BATCH     39
11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 31 USER_BATCH     34
11:00:08 bt1fsaplpr02_PLG /SDF/RSORAVSH                B 33 USER_BATCH     64
11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 33 USER_BATCH     43
11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 34 USER_BATCH     34
11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 35 USER_BATCH     37
11:00:09 bt1fsaplpr02_PLG RVV50R10C                    B 34 USER_BATCH     60
11:00:09 bt1fsaplpr02_PLG ZLM_HDS_IS_PURGE_RESERVATION B 35 USER_BATCH    206
I'm thinking also now about the message server as there is load balancing for each RFC call ?
Regards,
Olivier

User Name and Password for JCO RFC call to BAPI

Hi all,
What I think I know:
--We do NOT have Single Sign On configured so don't tell me to use SSO please - I agree, but...
--We have a requirement to do a goods receipt which prints labels for the handling units
.....The printer to which the labels are directed depends on the user who is running the transaction
What I think this means
--We will need to specify a user name and password in the RFC call so the label will go to the correct printer
--I cannot use the IllumnLoginPassword (or whatever its name is) for the password
--I need to prompt the user for their password a second time after they login to our MII app
The problem
--I will need to store the password somewhere for the duration of the session
......In session variable that has been encryted
.............I didn't see an encryption action block so I could create my own
......In the database using database column encryption
.............A little bit of a pain, but not too bad
Any corrections, alternatives, ideas .... ???
Thanks,
--Amy Smith
--Haworth

Thanks for the attention guys. A little clarification.
1. I have been assuming that I cannot use the IllumnLoginPassword for the JCO SAP password in the action block. If this is NOT true, then it solves my whole problem.
2. It would not work to prompt a shop floor person for their password every time they do an operation completion. Well, at least
if I don't want to not get lynched!
3. I am planning on prompting people every time they log on for their ECC password and retaining it somewhere secure while they are logged on (and longer if they skip the logoff step.)
4. I have been focusing on how/where to retain the password, but also need a way to encrypt it during transmission. Jeremy said the applet/BLS would at least encode it for me. That is good.
--Amy Smith
--Haworth
Edited by: Amy Smith on Feb 18, 2010 1:30 PM

SLD setup for UDF to RFC Call in XI

Similar Messages

Maybe you are looking for