2080145 - How to Analyze & Process EC Payroll issues for development? - Employee Central

SAP Knowledge Base Articles - public

2080145 - How to Analyze & Process EC Payroll issues for development? - Employee Central


  • This documents describes the steps and pre-requisites before creating a BCP message or a JIRA ticket for the Payroll development team.
  • What analysis should be performed before creating a JIRA or BCP message for an ECPayroll Integration issue reported by customer?


  • Employee Central.


  • Before creating a JIRA or BCP messages for the Payroll Development teams, please make sure to provide the below information in the JIRA/BCP.

Who is it about?

  1. Customer Name.
  2. Describe for which employee id / personnel number the issue exists.
  3. Describe where to find the sample data.

What is the issue? 

  1. Describe the symptoms.
  2. Describe how to reproduce the issue in system.
  3.  Check whether the symptoms are still existing(does Boomi process still fails, does application logs still have error messages, does API audit logs still shows error?).

When did it take place?

  1. Describe date and timestamp when the issue happened.
  2. Check Payroll System: Provide date and time to find an error message in the application log SLG1 / SRTUTIL.
  3. Check Boomi Platform: Provide the BOOMI Process logs with time information, execution ID and the Data logs.
  4. For Java exception on Employee Central UI or API: Server logs are required.
    1. EC UI: Provide the server logs either by yourself using Splunk or creating a Cloud Ops JIRA providing the exact timestamp and server details. To find the timestamp and Server details, ask the customer to provide the Version details by following the below steps:
      1. Go to the bottom of the screen and click on Version information. 
      2. Then ask customer to provide the screenshot of the pop-up window that comes up on the UI.
    2. API errors: Provide the server logs either by yourself using Splunk or creating a Cloud Ops JIRA providing the exact timestamp and server details. You can find the server details from the 'session id' in Boomi process logs or API Audit Logs or API Debug logs and the session ID will look like '9A0BD0E0DA8943C27733B79161976978.dc8sfapi02' and dc8sfapi02 is the host name to look upon in Splunk.
  5. Check with the customer: Clarify whether debugging is allowed and whether we are allowed to download the xml with the sample employee data and whether we are allowed to execute that xml manually via development web service.


Where did it take place?

  1. Describe the system details: EC system and Payroll system details.
  2. Login credentials: The way how to request login credentials.
    1. Cloud Payroll: use CAM to get system access. Check this link for user creation https://jam4.sapjam.com/groups/06pFw...G/slide_viewer.
    2. OnPremise Payroll/ERP: request customer to provide the user credentials in the CSS secure area. Ask the name of Customer's IT admin person on whose name you should create a BCP message. Now create a BCP message on this IT admin name and put it into customer action asking for opening the connection and providing the user details in secure area.
  3. Please check with customer to provide standard authorizations for the analysis(transactions, se16, slg1, srtutil, se80, pa20?).


Check of documentation

  1. Check if the issue is described in the implementation guide. https://sapneth2.wdf.sap.corp/ec-ondemand.
  2. Check the SAP Notes to find the solution of the problem mentioned by customer. Use the component LOD-EC-GCP-PY for finding the SAP Notes.
    1. If the issue is described in the SAP note, confirm with customer that the note is implemented.
  3. Check the Trouble shooting guides to see if the issue is already described there.
    1. Boomi Guide: https://jam4.sapjam.com/#groups/06pF...q/slide_viewer
    2. ERP/Payroll Guide https://jam4.sapjam.com/#groups/06pF...u/slide_viewer


Prioritizing the BCP and JIRA created by you:

  • Customer might not create a case with appropriate priority. For any case created by customer, analyze the case and understand the business criticality and then talk to customer if a re-prioritization of the the case is required. For any P1 case, a Business impact should be provided by the customer and if the business impact is not maintained by the customer then speak to him  and get the impact. By process, P1 means a business down situation, P2 means a critical business process is impacted. Hence choose the Priority of BCP and JIRA accordingly.


Process to be followed

  • While interacting with the ECPayroll development team, please follow the below process:
  1. Always provide the above information while creating any BCP/JIRA for ECPayroll Development teams.
  2. For JIRA tickets, always enter a memo in JIRA to ask for any updates. Add the developer's name in the watchers list so that he will always be informed for any update in JIRA.
  3. For a BCP message, always enter an internal note asking for an update from the customer. If you do not get any updates in BCP.
  4. Always update the SeOD with the latest updates in BCP/JIRA.


KBA , LOD-SF-EC , Employee Central , How To


SAP SuccessFactors HCM Core all versions