A ‐ 13
Many specific examples are contained in the Operations PBOT document. However, some specific examples of challenges
include: 1) Five working day access for OBPA transactions, 2) conflicting answers to business process answers when other
Bureau involved, 3) difficulty working through process issues when the issue involves a process with many Bureau (i.e., EBS,
BHR, central payroll, auditor's office). There are numerous areas where there are too many stakeholders involved but no one
specific entity is responsible.
We are unable to accurately reconcile payroll‐related accounts in timely manner. Without an adequate payroll register, we are
unable to reconcile payroll checks outstanding in a timely manner. Tracking payroll transaction from HCM to Accounts Payable
and General Ledger is too tedious and time‐consuming and sometimes virtually impossible. Note that some of these
challenges are system‐based, and some are user process/training‐based.
The changes in time keeping rules since the OSII is with a backup, infrequent user. There is no easy way to find out what
someone is being paid ‐ base pay info is OK, but premium pay is cumbersome and cannot see longevity pay.
Explain the challenges you are facing with reporting within HCM?
The invisible lunch hour is extremely frustrating to avoid overtime. Individual OT is not reflected prior to reporting the next
day. This would be helpful if the system could generate 'real time' feedback if there is encountering OT for the specific pay
HCM is very difficult to use especially when using PA40 and getting information and personnel data when we do not use it
every day. Online step‐by‐step processes would be helpful.
Better reporting instructions; reporting platform needed‐used to be able to easily access run reports in CARs; now no
comprehensive platform, instructions on how to get to data for end users/managers.
The time in understanding OM and the maintenance of position management is huge and cumbersome (channels through
which changes must occur). To run accurate reports, I often must run multiple reports (in SAP and outside) to ensure the
information is correct (such as with the vacancy reporting for the Bureau). Also, there is no reminder system set up ‐ if you set
someone as a double fill, or limited term position, it is easier to set a reminder about it in Microsoft Outlook since the
monitoring of tasks does not auto pull or have a reminder for you to pull the report. ZFIPYFOR ‐ detail report would be helpful
if rate of OT was included on the report.
Users need a list of which reports are available to them, what they do, and how to use them. Examples of each would be
helpful. Some reports only sort by first name and not by last name. While a user can sort by personnel number or other
numeric column, last name is how personnel administrators in our Bureau sort.
HCM reports are not intuitive and are challenging to use for the casual user. Org unit reports return org unit numbers but
casual users don’t refer to their org unit by number, they want the full org unit name.
Our users would like to see locked global layout templates to that an end user can create a user specific report but would not
change the global layout. Currently a user can go in and change and save layout templates.
Reporting has improved, but there is still a large gap with managers not being able to see the time that is being entered as the
Time Reviewers role is insufficient to expect managers to sustain the review process, since it is too clunky. They also lack vision
into their positions, employee pay rates, etc. Most of this will be solved with Manager Self Service, but that has been promised
for years and has yet to become a final product with workflow and all.
This is also identified in the Operations PBOT document but overall most do not know how to actually run specific reports and
the reports often do not work for what is needed (ex. vacancy reports that need additional financial information). The Bureau
frequently takes SAP information from several modules and manually combines them into working reports.
Our interface only shows current pay period. If a change is made in a prior pay period we do not know about it. This makes
paying for disability very difficult and time consuming. It would be nice to have a PTBAL/CATSDA listing report.