Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

RFC which will be accessed by a system non-sap.

RJSA
Active Participant
0 Kudos

Scenario:

The client (implementation) has a few user licenses of SAP, therefore chose to develop a portal in java that will be used by users who just don't have account (user) in SAP and the communication process with SAP will be done by RFC function.

These RFCs will be used to capture and process information by BAPIs in SAP (online), the user will login into the portal (java) which will call the RFCs for each type of processing.

I have a question:

For this type of processing, the client should buy more user licenses for SAP that this process is done this way, or we can use a single user to do this communication with the SAP (RFC user)?

Best regards,

Rafael Sá

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

If you want to get only data from SAP and display it in other non-SAP application, a user with type "Communication" can be used and it will not be considered as a license user. However,if you want to allow user to logon in SAP system and view the data then a user with type "Service" might be used.

Per my knowledge usually service users do not appear on licensing reports even if we allocate them to a license type. So a Service type user ID may limit the number of licensed users you have on a system but at the same time it could put you in breach of the terms of your licensing agreement.A service type user is allowed very restricted, usually not interactive, access to a system ..often for true anonymous access to information in SAP.

As advised earlier please check your customer licensing agreement with SAP before adopting any approach since each customer agreement can be different.

Cheers!

Sandipan

8 REPLIES 8

brad_bohn
Active Contributor
0 Kudos

That's not an ABAP question but it's been asked before here. It certainly can be done but that doesn't mean that your license allows it. Why don't you check your license agreement or ask your account rep?

martin_voros
Active Contributor
0 Kudos

Hi,

I just want to mention a disadvantage of using one user only. All transactions will be executed under this user so it will be harder to figure out who actually performed that action. You loose visibility and maybe there are some legal requirements and constraints for your case.

Cheers

Former Member
0 Kudos

Theoretically you could create your own ERP system which connects directly to the SAP DB via APIs. Workflow does much the same.

Probably it will be worthwhile talking to your SAP account manager about a corporate license based on the use of the software.

From a security perspective, generic access is always a pain.

Cheers,

Julius

RJSA
Active Participant
0 Kudos

The only problem is that the portal is not SAP (Webdynpro), the client will internally develop the portal and this portal will run on the intranet. The development platform will be in Java, but not be a Webdynpro portal. If it were, I think the possibility exists using SSO, but in this case, how can be done?

0 Kudos

You can use SNC from non-SAP systems, but by far an easier route would be to create a webservice for the BAPI - then more authentication options will open up for you (such as SAML).

Which BAPI is it and do you need or want the named user on the backend? (I would first clarify that: security and audit requirements, license costs, etc).

Cheers,

Julius

0 Kudos

you can use webserice integration to your JAVA based portal, there might be option of ABAP based webdynpro to publish URL directly in JAVA portal.

However on WSDL binding in webservice, there are certain option for authentication. such as BASIC authentication, SAML, tickets. while going out of SAP can be proxies.

Former Member
0 Kudos

As mentioned by other you should check with SAP and your contractual agreement for this.

However RFC and using generic user should be avoided. If you still go ahead with this option, explore options, authenticating based on log on tickets and do user switch to generic user. This way you would know who logged in based on time stamp and still use generic user.

Former Member
0 Kudos

Hi,

If you want to get only data from SAP and display it in other non-SAP application, a user with type "Communication" can be used and it will not be considered as a license user. However,if you want to allow user to logon in SAP system and view the data then a user with type "Service" might be used.

Per my knowledge usually service users do not appear on licensing reports even if we allocate them to a license type. So a Service type user ID may limit the number of licensed users you have on a system but at the same time it could put you in breach of the terms of your licensing agreement.A service type user is allowed very restricted, usually not interactive, access to a system ..often for true anonymous access to information in SAP.

As advised earlier please check your customer licensing agreement with SAP before adopting any approach since each customer agreement can be different.

Cheers!

Sandipan