ESS License – cast iron (middleware) - single user id

[Former Member]

Hi

We are in a process of implementing a solution for leave request and leave approval in a third party non –sap platform. This application will be talking to our ERP SAP System through a middle ware cast iron. Cast iron can invoke RFCs from ERP system.

So we have used a mix set of standard and custom RFCs to build the process related to leave management.

On approval of the request we are updating the leave related information in the Infotypes of the employee.

I would like to clarify my doubt regarding the SAP Licensing related to the whole process.

From cast iron we have maintained one one single user id to invoke the RFCs related to the process. So a single user id in the ERP system is used to fetch as well as create the record in the backend.

Does this approach has any implication on the license?

Do we need to use ESS license for all the employees who are going to use the third party application?

Regards,

[former_member182426 · Accepted solution]

As per my knowledge, you shouldn't update directly SAP tables from 3rd party applications.

You need to create your own Z RFC's to read / update and Z tables to update the data from 3rd party application. Once it's updated in Z tables inside SAP you can have some background report to update SAP tables from your Z tables.

Now your using only one user id to connect SAP for reading and updating the data.

Like in sap system, In 3rd party system also are you maintaining the employee details and leave quotas etc or replicate it from sap.

If your maintaining the employee details and leave information in 3rd party system also, you can have interface to upload this leave details file at end of the day in sap application server and upload in sap system. So that you can skip that direct access with sap user id from your 3rd party application.

[siddharthrajora · Accepted solution]

no license implication if they dont access ESS

you can directly update Infotypes using BAPIS or RFCs or custom ABAP program

You can also confirm with your account exeuctive, in your case main license would be how many users use ECC etc

[Former Member · Accepted solution]

Hi

Thanks for the reply,

So you mean if we create custom screen say in sap portal and use one single user id to update the leave's information in ECC backend. It is not creating any issue with license?

User A, User B, User C all login with different user ids in the front end application and we hit backend with one single user id and update pernr information using that. Is it ok without having 3 licenses for ESS here?

I consulted some of the guys they are saying it could be a case of indirect access and could be an issue at the time of SAP AUDIT.

Any clarity will be helpful

Regards,

[siddharthrajora · Accepted solution]

yes this can cause issue, typically ess license are separate from ECC backend system.

You can check the SAP notes for this and you sap account team can direct you on how licenes were solved, typically, it varies from customer to customer, it would be best you contact them or raise an OSS message

https://scn.sap.com/thread/3817959

https://scn.sap.com/thread/1224328

[Former Member]

HI

Any insight will be helpful on this

Regards