If you are currently on EhP4 and are using standard SAP ESS services for time sheet and leave request, you may have noticed that there is no out-of-the-box integration from SAP between these two applications. Enhancement is your only option. Since EhP4 services are based on Java WebDynpro, enhancing these applications is not always an easy task.
What’s new in EhP5 Time Sheet? With EhP5, SAP has introduced new functionality that integrates the ESS leave request with time sheet. Using this functionality, employees can view their approved absences in the time sheet (okay, what about the waiting for approval? Sorry, you have to do WD ABAP enhancement to show these requests).
In this blog we will discuss how to turn on this functionality on the CATS profile and also look at the required SOAMANAGER services and their configuration. Click here to learn more about SAP’s SOAMANAGER. I will discuss why we need SOAMANAGER little bit later in the blog.
First we need to enable this functionality on the time sheet. We can do this by setting up the CATS profile. SAP introduced a new section on the CATS profile (transaction code CAC1). See the below screen shot.
Select the check box “HR Enabled CATS”. You can decide if you want to add other functionality to your time sheet.
1. Display option: you can setup your time sheet display horizontal (each day as a column on the time sheet) or vertical (each day will be one row on the time sheet).
2. Public Holiday Type: you can auto populate public holidays for employees. All you need is create an absence type and plug it here. SAP also provides a BADI for any custom requirements around number of paid hours for public holiday. Work schedule is the default.
3. Cutoff Date: This is useful to display the time sheet due date to employees. By default you can set this to pay period begin/end date or set number of days (+/-) from pay period SAP also has a BADI to handle custom requirements. Below screen shot of EhP5 ESS time sheet.
Apart from the above configuration for CATS profile, we also need to configure some SOAMANAGER services.
Why SOAMANAGER? From SAP’s point of view, time sheet is a Cross Application Time Sheet. As far as SAP is concerned, this is not just for HCM system. Some customers will have the time sheet on FI system with integration to other systems – SAP HCM, PS, etc. However leave request, work schedules, payroll periods, etc. are housed exclusively in SAP HCM system. There is a need for communication between different systems. SAP uses service-oriented architecture for this purpose hence the SOAMANAGER configuration.
What if both time sheet and leave request are on my HCM system or all my modules are in one box? Unfortunately we still need to configure the SOAMANAGER. Hopefully, SAP will provide some kind of configuration option in the future so that we don’t need to touch SOAMANAGER when time sheet and leave request are both in the same SAP system.
What is SOAMANAGER? I am no SOAMANAGER expert, but I will try to put it in simple terms. I had to configure this the hard way, by trial and error, lot of exploring and disappointment. Of course it was sweet when it finally worked. So in my own simple terms this is what I understood. You have a a service provider and a consumer proxy. We need to link these two – for example, a service that provides work schedule info and a consumer that requires work schedule info. The link between these two is established by creating an “end point” for the service and “logical port” for the consumer proxy to access this end point.
Note: SAP systems involved in communication should be defined as business systems in SLD. Basis team can help you with this.You can also run SLDCHECK to make sure the setup is correct.
How do I start SOAMANAGER? Use the transaction code SOAMANAGER. This should open up in a browser for you. Get familiar with all the different bells and whistles. When you get comfortable, start configuring the below services.
What services are required? You can search for the service definition/consumer proxy. That is the easiest way to find these. Below are the required services and corresponding consumer proxies.
EETMEAGR_PWTP_EE_QR (service for work schedule): create an end point for this. Make note of the URL in the “Calculated URL Access” field. This is useful in the next step.
CO_CATSEMPLOYEE_TIME_AGREEMENT (corresponding consumer proxy for work schedules): create logical port using manual configuration option. Go to “Transport Settings” tab and specify the URL generated from the end point configuration. URL should include full SAP URL with corresponding application server/port etc.
You also have option to use single sign on or user name/password which will access these services. Apart from the above services SAP has two more.
1. EETMECAL_WTS_EE_QR is the service for team calendar and CO_CATS_EMPLOYEE_TIME_CALENDAR is the corresponding consumer proxy.
2. PYRLPROC_BDQE_EE_QR is the service for payroll periods and CO_CATSPAYROLL_PROCESS_ERPBASI is the corresponding consumer proxy.