Performing Post-Productive Activities in PCC

Creating posting documents occurs through Payroll Control Center. Start this process by executing the program and assigning the appropriate variant. Next, check the program to ensure everything is working properly. The process step must be confirmed if completed successfully.

The Posting process requires you to confirm each step before continuing on. Confirmation is required due to the transferring of documents to other functions. During this process, it is harder to make corrections or manipulations, so the information should be accurate to avoid repeated efforts to make additional corrections.

For the Monitoring and Productive process, you only need to confirm the last step. This is because you stay in the HCM area, making it easier to make corrections along the way.

You will see in the images below that creating, releasing, and transferring posting documents is a straightforward and simple process.

You will follow similar steps to release posting documents.

You will follow similar steps to transfer posting documents.

Next, let’s focus on how you as the consultant will set up bank transfers. In this lesson, you will first learn your responsibilities as the PCC consultant; then, you will learn about the responsibilities of the Payroll Process Manager.

Whereas the variant for the posting process was general, this bank transfer process is very specific. As a consultant you will use specific variants for specific banks. You’ll also be working with Data Medium Exchange (DME) files as part of these processes.

There are two process types connected with subsequent payroll activities refer to OT Others Category:

• Posting
• Bank Transfer

Steps:

1. Create the pre-DME file
2. Create the DME file
3. Send the DME file

The first step of the bank transfer process uses a specific program that marks some records as already paid for the employee. Keep in mind that you must define the Payment Medium Format used by the customer.

The figure, Bank Transfer Process Type - Step 1, shows the two reports for this first step.

• The first report (PRCDTAX0) marks the specific wage type amount from the payroll results as "ready for payment".
• The second report (SAPFPAYM) allows the customer to use the appropriate format for the bank transfer file. This program will help to put the information into the correct format.

If changes are made to the current payroll period and the system finds that the employee has already been paid, the system will generate a specific wage type with the delta, avoiding a double payment to the employee. The system will take into account the previous payment and make up the difference.

The second step for the bank transfer process works to create the entire DME file to prepare the correct format, making it acceptable for the bank. Once the employee wage amount is set, the team can prepare the data in the correct format, generating the file into the correct format. You must define the report name and variant that is used by the customer to create the DME file.

The last step is to send the information to the bank.

Next, let’s see what tasks the Payroll Process Manager must complete on their end.

When the Payroll Process Manager creates a new bank transfer payroll process, they must assign it to the appropriate payroll process type, assign the payroll area, and the payroll period.

When the consultant prepares this process type, the payroll process manager will be able to create the process. The payroll process manager needs to provide information about the payroll area (list of employees collected for system processes) and payroll period. The system just needs to know the list of employees for processing and the payment period.

Now the Payroll Process Manager is ready to run this process and create the pre-DME file. The process step must be confirmed if completed successfully.

To complete this process, the Payroll Process Manager will follow these steps:

1. Mark as ready for payment.
2. Prepare payment information according to specific bank requirements (data format).

Now that the pre-DME file is ready, the Payroll Process Manager can prepare to send it.

As a last step, the Payroll Process Manager will then send the DME file to the bank based on the previous preparation steps.

When the customer wants to include additional steps in the process, for example, generating or printing a payslip or including a standard or custom report as a process step, use the category "OT Others" that was used in the previous steps.

If the customer needs to generate pay slips for all employees processed in the process (from the corresponding payroll area), it is necessary to include a Create and Print Payslip step in the process, for example, of Productive Payroll.

If the customer needs to generate pay slips only for those employees for whom alerts were generated, it is necessary to use the appropriate analytical designer and assign it to the corresponding validation rule.

Provide the country or customer specific information on the form. Different organizations will have different requirements, resulting in different payslip configuration. It is possible to create a payslip in a PDF format or other standard format.

To print payslips, the Payroll Process Manager needs to specify the default printer in the user’s own parameters (Transaction su3). A default printer is important for security reasons. Not all customers will use paper payslips, but the functionality must be accessible for customers.

You may be asked to add a customer report for the payroll process. To add an additional step per the customer’s request, perform the following steps:

1. Use Step Template ID PYP_V2_ASYNC_BATCH_BASE in your configuration to call a report such as the Wage Type Reporter.
2. Define the program and variant.
3. Use Step PYP_V2_ASYNC_BATCH_BASE to include a standard or custom report as a process step. The image below shows an example for the report Wage Type Reporter.

The figure, Print Reports Process Run, shows how to print reports. This is what it will look like when you complete the additional process step as described in the previous step.