Deprecated: Creation of dynamic property Pusher\Log\Logger::$file is deprecated in /html/wordpress/wp-content/plugins/wppusher/Pusher/Log/Logger.php on line 18

Deprecated: Creation of dynamic property Pusher\Log\Logger::$file is deprecated in /html/wordpress/wp-content/plugins/wppusher/Pusher/Log/Logger.php on line 18

Deprecated: Creation of dynamic property Pusher\Dashboard::$pusher is deprecated in /html/wordpress/wp-content/plugins/wppusher/Pusher/Dashboard.php on line 68

Deprecated: Creation of dynamic property Pusher\Log\Logger::$file is deprecated in /html/wordpress/wp-content/plugins/wppusher/Pusher/Log/Logger.php on line 18

Deprecated: Creation of dynamic property Pusher\Log\Logger::$file is deprecated in /html/wordpress/wp-content/plugins/wppusher/Pusher/Log/Logger.php on line 18
SuccessFactors Archives - j&s-soft

Category: SuccessFactors

  • Modern SAP Payroll Control Center (Part 3): Setting Up Background Processes

    Modern SAP Payroll Control Center (Part 3): Setting Up Background Processes

    The functionality of the Payroll Control Center (PCC) is enabled through background processes that run at regular intervals. These processes execute the defined process steps and check master data and payroll results for monitoring and alert purposes. They can be configured and scheduled using the pyc_admin_transaction report.

    Before configuring these processes, the steps for the Configuration Workbench (CW) and Manage Configuration (MC) should already be completed. Instructions for this can be found in Part 1: Activating the Configuration Workbench, and Part 2: Activating the Manage Configuration App of this blog series.

    User for Background Processes

    Any user can be specified here, under whose name the processes will run. In productive scenarios, it is recommended to use a dedicated batch user. For testing purposes, I pragmatically used my own user account, RWALLSCH.

    Daemon Prozess

    The daemons check master data and payroll results in order to trigger alerts and update monitoring results. On our test system, a repetition interval of 5 minutes has proven to be sufficient. Clicking ‘Start’ schedules the process.

    Activating the Daemons

    Event Handler Process

    Event handlers execute the process steps and their sub-steps. I have set a repetition interval of 10 minutes here. This means a process step with 5 sub-steps will take at least 50 minutes to complete, as each sub-step triggers a new event to initiate the next. If this is too slow for testing, the interval can be reduced. I simply wanted to minimise the system overhead. Clicking ‘Start’ will schedule the process.

    A list of processes already registered with the event handler is shown below.

    Activating the Event Handler

    Wrap-Up Prozess

    The wrap-up executes a set of reports to clean up temporary and expired process data. A single click on ‘Register’ is sufficient to schedule the process.

    Activating the Wrap-Up

    Final Steps

    In the Master Data Maintenance Users list, you can enter your own username. Users listed here are authorised to make changes to master data during alert processing — changes which are immediately reflected in the live payroll run. This is essential for payroll administrators who need to resolve alerts.
    Finally, a process ID must be generated for the HR Process Workbench. Simply click ‘Generate’, and the rest happens automatically.

    This is the third and final part of the blog series.
    You can find Part 1, which covers the activation of the Configuration Workbench, [here].
    Part 2, covering the activation of the Manage Configuration App, is available [here].

  • Modern SAP Payroll Control Center (Part 2)

    Modern SAP Payroll Control Center (Part 2)

    Activating the Manage Configuration App

    The Manage Configuration (MC) UI5 app complements the classic Configuration Workbench (CW). It allows you to define your own validation rules, KPIs and analyses without having to use the SAP GUI and the CW directly. However, the types of validation rules still need to be defined within the CW, so it is not possible to completely avoid the classic environment.

    Before activation, the steps for setting up the Configuration Workbench (CW) should already have been completed. More information on this can be found in the first part of this blog series.

    Business Functions

    In addition to the CW business functions, only two further business functions are required for the MC app. These are activated via transaction SFW5, as usual. You can find the required functions listed under point 2 here, or alternatively in the screenshot below.

    Business Functions for MC

    SAPUI5 Applications

    The MC app consists of several sub-apps, all of which must be activated. This is done using transaction SICF. The list of services can be found under point 3 here or in the table below.

    SAPUI5 ApplicationApplication Service Path
    Manage Configuration/sap/bc/ui5_ui5/sap/
    • hrpy_pcc_lib_v7
    • hrpy_pcc_ckp_v1
    • hrpy_pcc_cvr_v1
    • hrpy_pcc_ctl_v1
    • hrpy_pcc_can_v1
    • hrpy_pcc_cdn_v1
    Access for Application Index queries/sap/bc/ui2/app_index

    OData Services

    Next, as is commonly known, the activation of the OData services follows. These supply the UI5 apps with data and are activated using transaction /IWFND/MAINT_SERVICE. The services that need to be activated are listed under point 4 here or in the following table.

    OData ServiceTechnical Name
    Manage ConfigurationPYC_CFG_SRV
    PYC_CFG_VR_SRV
    PYC_KPI_CONFIG_1_SRV
    PYC_DNG_CONFIG_1_SRV*
    PYC_CFG_ANALYTICS_SRV*

    It is important to ensure that the OData service is properly activated and that the system alias is maintained. In this case, we use LOCAL, as shown in the image.

    Activating the OData Service

    If the ERP system is running HCM for S/4HANA (H4S4), the two OData services marked with an asterisk (*) will be missing from the list and must be added manually. To do this, go to transaction /IWFND/MAINT_SERVICE, select Add Service, and add the two missing services. SAP’s official guide for this can be found here.

    Adding the missing OData Services

    SAPUI5 Application Index

    Finally, it is recommended to update the SAPUI5 Application Index. This is required for the cache buster mechanism. The update is performed using the report /UI5/APP_INDEX_CALCULATE.

    In the third and final part of this blog series, we will cover the setup of background processes in the SAP PCC.

    You can find the first part, which covers the activation of the Configuration Workbench, here.

    In the third and final part of our blog series , we walk you through the setup of the background processes, here.

  • Modern SAP Payroll Control Center

    Modern SAP Payroll Control Center

    With SAP SuccessFactors Employee Central Payroll (ECP), the management and monitoring of payroll processes are to be carried out directly from SuccessFactors. Technically, it is a web portal into which UI5 applications from an ERP backend are embedded. The actual payroll accounting and payroll runs continue to be performed in an ERP backend. A core component of ECP is the Payroll Control Centre (PCC), which has been offered as an add-on for ERP systems since 2014. The ECP portal primarily serves as a modern user interface providing access to the same underlying technology.

    If you already have an ERP backend and wish to use the modern PCC interface, you can do so without SuccessFactors. This blog details every step required to achieve this, based on SAP’s official setup guide.

    This blog article is the first part of a series on activating the PCC, focusing on the activation of the Configuration Workbench.

    Activating the Configuration Workbench

    The Configuration Workbench (CW) is used to set up validation rules and process types for the PCC. After activation, it can be accessed via transaction PYC_CONF_WB.

    Business Functions

    First, the required business functions must be activated using transaction SFW5. A list of the functions to be activated can be found here under point 2, or in the figure below. All functions are located in the ENTERPRISE_BUSINESS_FUNCTIONS folder. To activate them, tick the checkbox for ‘Planned Status’. Afterwards, you can save and activate the changes.

    Activating the business functions in SFW5

    SAPUI5 Applications

    Next, the UI5 applications that will later be embedded in SuccessFactors need to be activated. They are activated via transaction SICF. The list can be found here under point 3, or in the following table.
    To activate them, locate the service in the hierarchy, right-click on it, and select ‘Activate Service’.

    SAPUI5 ApplicationService Path
    Manage Teams/sap/bc/ui5_ui5/sap/hrpy_pcc_tm_1 (In der SAP-Doku falsch)
    My Teams/sap/bc/ui5_ui5/sap/hrpy_pcc_mc_1 (In der SAP-Doku falsch)
    My Processes/sap/bc/ui5_ui5/sap/hrpy_pcc_proc_3 (In der SAP-Doku falsch)
    My Alerts/sap/bc/ui5_ui5/sap/hrpy_pcc_errm_2
    Unassigned Alerts/sap/bc/ui5_ui5/sap/hrpy_pcc_em_t_2
    Manage Policies/sap/bc/ui5_ui5/sap/hrpy_pcc_conf_2
    Manage Processes/sap/bc/ui5_ui5/sap/hrpy_pcc_conf_1
    My Off-Cycles/sap/bc/ui5_ui5/sap/hrpy_pcc_oc_1
    Audit Trail/sap/bc/ui5_ui5/sap/hrpy_pcc_al_2

    OData Services

    The UI5 apps communicate with the backend via OData services to read and write data.
    If the UI5 apps run on a different backend than the payroll system, routing must be configured in the Reference IMG (transaction SPRO) under ‘Manage SAP System Aliases’. The exact hierarchy is shown in the screenshot below.
    In this test system, both the UI5 apps and the payroll run on the same backend, so this step is skipped and the existing system alias LOCAL is used.

    Customizing System Routing

    Now the OData services need to be activated.
    This is done via transaction /IWFND/MAINT_SERVICE. The list can be found here under point 4.
    The following services are required:

    OData ServiceTechnical Name
    Manage TeamsPYC_TEAM_MANAGER_SRV
    My TeamsPYC_TEAM_MAINT_SRV
    My ProcessesPYC_PROCESS_MANAGER_SRV
    My AlertsPYC_ALERT_MANAGER_SRV
    Unassigned AlertsPYC_TEAM_ALERTS_SRV
    Manage Policies
    Manage Processes
    PYC_CONF_SRV
    My Off-CyclesPYC_OFF_CYCLE_SRV
    Audit TrailPYC_CONT_003_SRV

    To activate the service, select it from the list and click on ‘ICF Node’ -> Activate in the bottom left corner of the window.
    In the bottom right corner of the window, the system alias must be added (here: LOCAL).
    If everything has worked correctly, the OData service can be tested using the SAP Gateway Client.

    Service Activation

    Declustering

    To store the validation data, declustering must be activated.
    In this process, data from encrypted cluster tables is copied into readable transparent tables. Payroll results are stored in cluster PCL2. This cluster consists of several tables, including the RT (Result Table) and WPBP (Work Center/Basic Pay) tables, which contain the data required for the PCC.
    We will configure the declustering so that the data is simultaneously stored in the transparent tables P2RX_RT and P2RX_WPBP when it is created in the cluster.

    To do this, you must once again access the Customising (SPRO).
    The path is: ‘SAP Customizing Implementation Guide’ -> Payroll -> ‘Payroll: Germany’ -> ‘Declustering Tools’ -> ‘Define Settings for Declustering Tools’.
    There, set ‘Switch Option’ to ‘Switched on with synchronous declustering’.
    ‘DB Connection’ remains empty.

    Define Settings for Declustering Tools

    In the same level of the Customising hierarchy, select ‘Select Tables with Payroll Results for Declustering’.
    We add the RT and WPBP tables.

    Select Tables with Payroll Results for Declustering

    In the next part of this blog series, we will activate the Manage Configuration app. You find it here.

    In the third and final part of our blog series on activating the Payroll Control Center (PCC), we walk you through the setup of the background processes. More here.