Go Back   Wiki NewForum | Latest Entertainment News > Career Forum & Tips > SAP HCM Forum


Resolved - Leave request workflow and document status inconsistent !


Reply
Views: 1906  
Thread Tools Rating: Thread Rating: 66 votes, 2.52 average.
Payroll Time OM & PA Portal Payroll Fixes Career Tips SuccessFactors
  #1  
Old 06-02-2021, 05:58 PM
welcomewiki welcomewiki is offline
Member
 
Join Date: Dec 2008
Location: India
Posts: 80,566
Default Resolved - Leave request workflow and document status inconsistent !

Question, Issue, Problem:

Dear HCM experts,



I need your assistance to find out root cause of below issue since it not getting replicated in non-prod environments.
We have 2 level w/f implemented for different leave/attendance types. There is option available to approvers to accept/reject these requests en masse or individually.

At every level of leave request a new version (and its status) is generated in the following sequence.
  • 1.SENT – Request is submitted.
  • 2.SENT – Request Approved by 1st level approver.
  • 3.APPROVED - Request Approved by 2nd level approver.
  • 4.POSTED – (3) step requests picked up by RPTARQPOST (periodic batch job) for Info type (2001, 2002) update.
After 1st level approval, these ATTABS requests either achieve the status ‘APPROVED’ or ‘SENT’. And this is real issue, since ATTABS requests receive the status ‘APPROVED’, subsequently program RPTARQPOST picks up these ‘APPROVED’ request for posting even though 2nd level approval is still pending.
And w/f status is still ‘STARTED’ or ‘IN PROCESS’.
Incorrect leave requests would follow sequence.
  • 1. SENT – Request is submitted.
  • 2.APPROVED - Request Approved by 1st level approver.
  • 3.POSTED – (2) step requests picked up by RPTARQPOST (periodic batch job) for Info type (2001, 2002) update.
Since we are having counter scenario running alongside i.e. some leave request having 4 version created as well as for other leave requests 3 versions are getting created (as shown in attached screen shot).
Further, I checked the configuration table PTREQ_STATUS_TRA and it seems config entry with ‘2’ return code is getting triggered.

P.S. I can confirm that leave / attendance type, employee and w/f triggered in these cases are the same.
Reply With Quote
Payroll Time OM & PA Portal Payroll Fixes Career Tips SuccessFactors
  #2  
Old 06-02-2021, 05:59 PM
welcomewiki welcomewiki is offline
Member
 
Join Date: Dec 2008
Location: India
Posts: 80,566
Answer, Fix, Solution:

Basically approver were approving requests via Fiori application and it was suitable to process single level w/f (i.e. transition event in every case was 'Approve' hence 2 level were impacted as a result.
Reply With Quote
Reply

Latest News in SAP HCM Forum





Powered by vBulletin® Version 3.8.10
Copyright ©2000 - 2024, vBulletin Solutions, Inc.