Kontakt

Ansicht
Dokumentation

PYC_ADMIN_TRANSACTION - Admin Transaction Report

PYC_ADMIN_TRANSACTION - Admin Transaction Report

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this report to do various administration tasks for the Payroll Control Center. For example, you can specify which predefined daemon jobs should be run, at what frequency, and under the authorizations of which user.

Please make sure that all the lights on the left are green.

Red lights mean that something has gone wrong and needs your attention.

Yellow light means that something is suspicious and requires your attention. For example, you have changed the recurrence value for an activity and then switched to another activity without saving the change.

Integration

Prerequisites

In order to maintain the batch user name or schedule the daemon job in this report, you must have the corresponding application authorization (P_PYD_AAUT) and the authorization to schedule a batch job for the daemon user (S_BTCH_NAM).

  • P_PYD_AAUT: This authorization object decides whether a user can use this report.
  • S_BTCH_NAM: This authorization object decides whether a user is allowed to schedule a job where a different user (the so-called "authorization user") is used to perform the authorization checks for one or more job steps. This authorization object is checked if a dialog on the frontend should not have too many authorizations but should at least be able to triggerjobs. The job themselves are then performed by a batch user with many authorizations that cannot be used in dialog.

For more information, see the corresponding authorization object document.

Similarly, a frontend user of the Payroll Control Center does not have to have the full authorization required to run payroll anymore, but it is sufficient to have the payroll process authorization to start a step for a given process (authorization object P_PYD_INST) and the authorization to schedule a batch job for the batch user (S_BTCH_NAM).

Features

Maintain User Name for Batch Processing

Here you define the user name using whose authorizations the daemon jobs should be run. The batch user name you specify here should have the authorizations for running the reports included in the Payroll Control Center process steps.

As a result, for example, when a payroll manager clicks the Run Payroll button on the frontend UI of the Payroll Control Center, the daemon jobs are running in the background using the authorizations of the batch user.

If you want to change user here, you must stop daemon job first; otherwise, there will be an error message. Since the batch user is used for scheduling all of the batch processing programs that are started by the Daemon report, it is suggested that you create a non-dialog user for this purpose in order not to interfere with the user's daily work.

Maintain Recurrence for Daemon Jobs

A daemon report is like a web server. After being scheduled, it periodically detects the processing request and calls the predefined procedure to process the request.

Define the recurrence of daemon job, typically the Payroll Data Source Framework Use Case Processing (PYD_DAE_PROCESS) report. It is suggested that you set a short interval, for example, 1 minute.

Busy Waiting

If you set the daemon job to Busy Waiting, it means that the daemon job is a recurring job but during its run time, the daemon job is active in an endless loop, waits for input, and immediately reacts if any new request occurs to be processed. Busy Waiting improves the system response time with respect to asynchronous processing in the Payroll Control Center but mainly blocks one batch job process on the application server. You can decide whether to select this option based on the specific customer situation. If Busy Waitingis selected, the recurrence can only be Minutes with a value less than or equal to 10.

The content of the table is determined by the system based on an analysis of the currently planned jobs having PYD_DAE_PROCESS as one step. The table might have more than one entry in case other jobs have been manually scheduled via transaction SM36 or SE38. If you see other entries than PYD_DAE_PROCESS in the table, stop these extra entries as they reflect an inconsistent system setup.

If Busy Waiting is not enabled, the daemon will only process one daemon request once, which means you have to wait for another interval of the recurrence time.

Timeout for Recheck

When the payroll admin validates an alert by choosing the Validatebutton, if the background jobs take longer than the defined recheck timeout value to respond, the system will prompt an error.

You define this timeout value. It is suggested that you enter a value slightly bigger than the time required for executing the jobs required for the validation or recheck.

Note

The timeout value applies to the batch user, rather than the user who modifies the timeout value.

Maintain Recurrence for Event Handler Jobs

Define a proper recurrence of event handler jobs. The Event Handler identifies relevant master data changes using Infotype framework and validates these changes against the defined policies by automatically restarting a shadow process only for the employees with change.

The following settings can be made:

  • Recurrence period in minutes
Event handler jobs recur in the defined frequency. Master data changes during the period are picked up and processed. You can determine the recurrence period based on the business use case (for example, how frequently the customer expects the validations to detect new alerts).
  • Activation status of event handler enabled processes
In the configuration of Process/Process Type, there is a field Enable Event Handler for a Monitoring Payroll Process. In Admin Transaction Report, the production system admin can further decide which of these event-handler-enabled processes he or she wants to activate.
By default, all the Monitoring Payroll Process enabled for event handler are activated.
The scheduled Event Handler job will exclude those processes in inactive status.
  • Start/Stop the event handler job with the specified period and processes

Maintain Recurrence for Regular Wrap-Up Jobs

Define the recurrence of regular wrap-up jobs. Once registered, the daemon automatically starts the jobs (using the report PYD_REGULAR_WRAP_UP) at every recurrence. The purpose is to delete temporary data that has been produced during the use of the Payroll Control Center. The interval time should not be too short.

The PYD_REGULAR_WRAP_UP report starts individual jobs for the following reports:

  • Payroll Data Source Framework: Delete Expired User Sessions (PYD_DELETE_EXPIRED_SESSIONS)
This report was supposed to be started manually in previous feature packs. From Feature Pack 3, this is scheduled automatically, and the manually scheduled jobs for this report should be cancelled.
  • Payroll Data Source Framework Daemon: Reorganize Registries (PYD_DAE_REGS_REORG)
This report deletes daemon registrations (use cases and events) that have been processed already by the regular daemon job.
  • Reorganize Finished Shadows (PYD_SHADOWS_REORG)
"Shadows" are used to hold information about selection objects (for example PERNRs) that can be used to start a process step instance for a subset of the original selection.
For example: A process runs for payroll area XY. A process step instance that processes PERNRs runs for period 12.2014 of that payroll area. If PERNRs are found by the consistency checks later and master data corrections have been done, the user might want to restart that step instance in order to get the errors corrected. That restart can be done for the overall selection (payroll area) or only for the reduced list of PERNRs for which errors were found. That list is stored on process instance level, as so-called "selection object list of the deviating selection shadow". When the process instance is closed, that shadow is not used any longer and can be deleted. This report does the deletion.
  • Reorganize Re-Check Shadows (PYD_RC_SHADOW_REORG)
This report cleans up the Re-Check shadows.
  • Reorganize Event Handler Items (PYC_EVENT_HANDLER_REORG)
This report cleans up the Event Handler Items.
  • Automatic process configuration migration (PYC_CFG_AUTO)
Once a process has been defined, if any of the following configured is modified, you must run this report to ensure configuration consistency:
  • Selection parameter of the process

  • Process template category

  • Process and policy namespace used in simplified configuration

A namespace is a prefix for the generated processes and policies in simplified configuration. Defining the namespace prevents the generated processes or policies from being changed or deleted in the backend views or view clusters.
Warning
It is not recommended to modify the policy and process namespace once a process is defined. Modifying the namespace increases the risks of accidental deletion of important data.

Specify the variant that you have created for the reports.

Maintain User List for Master Data Maintenance

Maintain user list for master data maintenance even if the control record is released for payroll. If payroll control record is locked, the users in the list have authorization to change master data.

This is used in special cases for productive payroll process. In productive payroll, typically, a payroll admin has to release the control record before starting productive payroll. However, in the subsequent Initiate Policies step in Payroll Control Center, there might be check alerts for some employees. In this case, it is necessary to modify the master data of employees with these check alerts even though the current payroll control record is locked.

By default, the payroll admins who are assigned to handle the check alerts automatically have the authorization to correct master data when payroll control record is locked.

The reason for maintaining additional users in this activity is for cases when the master data change for employees with check alerts is done in a third-party system. For example, if user changes master data in Employee Central, those changes will be replicated to backend ERP through the API of master data framework with a special user named something like WF_BATCH (for example). By adding these user names in this activity, they are also authorized to modify master data when the current payroll control record is locked.

Generate General process ID for HR Process Workbench

This ID is used by the system to integrate the Payroll Control Center with HR Process Workbench (transactions PEST and PUST). Using the general process ID, all reports (standard reports as well as customer reports) that have been enabled for the HR process management are able to pass their status information (error status of selection objects and workflow container) to the Payroll Control Center.

A dummy process model SAPXXPCCis used for the interaction between Payroll Control Center and the HR Process Workbench. The process ID generated here is used for the run instance for this dummy process model. Reports that support the HR Process Workbench status notification will be automatically integrated with the Payroll Control Center and their error notifications will be caught by Payroll Control Center and used in step error details in Payroll Control Center.

Maintain Database Access Option

Some database system (for example, MaxDB) has low performance when dealing with multiple joins, so option with alternative SQL statement using EXISTS instead of JOIN is provided.

Maintain General Settings

The payroll process manager can upload documents for the current active step of a process instance by choosing Notes and then clicking the Upload icon in the Payroll Control Center - Process Management application.

You maintain general settings to allow or disallow document upload and define maximum file size for document upload.

After you enable document upload in general settings, you can use the Customizing activity Define Allowed MIME Types for Document Upload to define the allowed file types for document upload.

You can also specify a maximum number of rows that is allowed for the download in Alert History.

Maintain Lock Entries

Team Configuration

When a user uses the Team Configuration app to configure teams for handling alerts for a Team Monitoring process, the process is locked by him or her, and nobody else can configure teams for this same process. In case the first user leaves without saving the configuration, you might be requested to manually delete the lock entry for the process, so that another user can edit teams for the same process.

Policy Configuration

When a user uses the Policy Configuration app to configure a policy, the policy is locked and nobody else can configure this policy. If the user expires in the system, for example, if he or she leaves the company, you can assign the policy to another user that has the authorization for Policy Configuration.

Note

  • Change must be saved before it can take effect. Once you assign the policy to another user and save the change, the names under In Process By columns are changed to the new user.
  • The assigned user must have the authorization for the policy in Policy Configuration:
Authorization object P_PYC_POL:
  • ACTVT - Full Authorization

  • BO_SERVICE - Full Authorization

  • P_PYC_POLT - Prefix or full ID of the policy type

Process Configuration

When a user uses the Process Configuration app to configure a process, the process is locked and nobody else can configure this process. If the user expires in the system, for example, if he or she leaves the company, you can assign the process to another user that has the authorization for Process Configuration.

Note

  • Change must be saved before it can take effect. Once you assign the process to another user and save the change, the names under In Process By columns are changed to the new user.
  • The assigned user must have the authorization for the process in Process Configuration:
Authorization Object: P_PYC_PYP:
  • ACTVT - Full Authorization

  • BO_SERVICE- Full Authorization

  • P_PYC_PYPT - Prefix or full ID of the process type

Validation Rule Configuration

When a user uses the Manage Configuration app to configure a validation rule, the validation rule is locked and nobody else can configure it. If the user expires in the system, for example, if he or she leaves the company, you can assign the validation rule to another user that has the authorization for Manage Configuration.

Note

  • Change must be saved before it can take effect. Once you assign the validation rule to another user and save the change, the names under In Process By columns are changed to the new user.
  • The assigned user must have the authorization for the validation rule in Manage Configuration:
Authorization Object: Authorization for Manage Configuration (P_PYT_CFG)
  • P_PYT_CAT – VR (Validation Rule Configuration)

  • P_PYT_AUT – 01 (Display), 02 (Edit)

KPI Configuration

When a user uses the Manage Configuration app to configure a KPI, the KPI is locked and nobody else can configure KPI. If the user expires in the system, for example, if he or she leaves the company, you can assign the KPI to another user that has the authorization for Manage Configuration.

Note

  • Change must be saved before it can take effect. Once you assign the KPI to another user and save the change, the names under In Process By columns are changed to the new user.
  • The assigned user must have the authorization for the KPI in Manage Configuration:
Authorization Object: Authorization for Manage Configuration (P_PYT_CFG)
  • P_PYT_CAT – KP (KPI Configuration)

  • P_PYT_AUT – 01 (Display), 02 (Edit)

Analytics Configuration

When a user uses the Manage Configuration app to configure an analytics, the analytics is locked and nobody else can configure it. If the user expires in the system, for example, if he or she leaves the company, you can assign the analytics to another user that has the authorization for Manage Configuration.

Note

  • Change must be saved before it can take effect. Once you assign the analytics to another user and save the change, the names under In Process By columns are changed to the new user.
  • The assigned user must have the authorization for the analytics in Manage Configuration:
Authorization Object: Authorization for Manage Configuration (P_PYT_CFG)
  • P_PYT_CAT – AN (Analytics Configuration)

  • P_PYT_AUT – 01 (Display), 02 (Edit)

Selection

Standard Variants

Output

Activities

To access this report on the SAP Easy Access Menu, choose Human Resources -> Payroll -> International -> Tools -> Payroll Control Center -> Admin Transaction Report.

Example

More Information

For information about the authorization for Payroll Control Center, open the following URL in a web browser:

  • SAP ERP HCM: https://help.sap.com/viewer/pypccen608/576a4720562b4c6f8aa93e1d0428ff20.html
  • SAP SuccessFactors Employee Central Payroll: https://help.sap.com/viewer/185f14fbe60d4bbb8d7d5e4f8d89b24b/latest/en-US/66f37968867f4d15b7b27887390f26b9.html






General Data in Customer Master   General Material Data  
This documentation is copyright by SAP AG.

Length: 20925 Date: 20240520 Time: 083634     sap01-206 ( 339 ms )