License required for EP read/write to R3 operation

[Former Member]

I read some message here regarding EP - R3 License. I'd like to get more clear license requirement for my case.

In our region, we hardly find clear response from SAP on this issue.

My scenarios is typical : Many User Account in EP UME (either local db or link to AD, but not in R3), and we have lots of custom Web Dynpro application using JCo destination to read as well as write data to R3.

Let's say we have 5 concurrent EP user having "WRITE" operation (via our web dynpro and then JCo, RFC) against R3.

We're not sure "how many" R3 License needed ? one communication user account license ? or 5 dialog user account licenses? or 5 ESS/MSS user license ? or ...?

Hope somebody can share his experience.

Thanks

[benjamin_houttuin]

>

> 
> Let's say we have 5 concurrent EP user having "WRITE" operation (via our web dynpro and then JCo, RFC) against R3. 
> We're not sure "how many" R3 License needed ? one communication user account license ? or 5 dialog user account licenses? or 5 ESS/MSS user license ? or ...?
> 

Depends how you configured/maintained your JCO...

1. When defining the JCo destination for application data, select authentication method Ticket.
The useru2019s logon ticket is sent to the SAP system.

2. When defining the JCo destination for metadata, only authentication method User/Password is supported.

Note
The user is predefined for authentication method User/Password and cannot be changed. 
This user is a technical user who does not need dialog authorization. 
The name and password assigned to this user must be known in the backend. 
The authorizations for this user must be set in the backend so that this user can access all DDIC function modules.

source: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/94/3c1b40fcdd8f5ce10000000a155106/frameset.htm

So when you use a dedicated user for application data instead, then there is actually only 1 user that is "talking" with the backend R3 system. Technically speaking you only would need 1 licence for that user only and not 5 for the portal user that indirectly use that R3 user. But... I've know of situations where companies implemented scenario's with shared users to save money on Licences and SAP was not happy with that.

But.. I think when the functionality is allowing you to use a dedicated user and it is not a work around to save license money on purpose then that should be OK. To be sure it's best to contact your SAP Account Manager, because every company can have its own tailor made contracts.

In addition I would like to address something else.. "Compliance"...

When using a dedicated user to connect to your R3 system (via JCO) then action done in the system (write, update, delete) are done with that dedicated user. So when the functionality is in the area of finance or other important functions like authorisations then you cannot trace who did the actual action. For example in the portal you have 5 users A,B,C,D and E and all use the same app that connects via JCO to R3 via user X then all actions are registered on user X.

When something goes wrong (by accident or on purpose) then you cannot trace who did it. And if you cannot trace it a Auditor cannot trace it either.

Cheers,

Benjamin