Ansicht
Dokumentation

PYC_PYP_PT - Define Process Templates

BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

You use this Customizing activity to set up process templates, process step group templates, and process step templates in each process step group template.

You have defined parameter types in the Customizing activity Define Parameter Types.

You have defined process step templates in the Customizing activity Define Process Step Templates.

If you want to use fields from Infotype 0001, including SAP fields and custom fields, as team dimensions, you must have registered these fields as allowed team dimensions in the Customizing activity Register Fields of Infotype 0001 as Allowed Team Dimensions.

In the standard system, we deliver a complete, standard payroll process from end to end.

We recommend that you create your own process templates by copying a standard process template and then making corresponding changes.

You can also create new process templates from scratch.

1. Copy a process template and make necessary changes.
2. Define the business logic version for the process template

Business logic version determines whether to use the old or new screens and business logic version. Each process template should support only one business logic version. If you don't specify a business logic version, the default value is Initial (previous feature packs before Feature Pack 3) business logic version.

Note: You must not change the supported business logic version for any delivered standard entity. The step template base class checks the consistency between the business logic version of the process template, process, and the supported business logic version of the step template. If they are not consistent, no data is returned, no operations are active, and it dumps if any operation is nevertheless called.

1. If the business logic version for the process template is FP3, assign process template categories.

The default option is the Otherscategory.

• The process template category impacts the behavior of some step templates. For example, the Run Payroll step in a "Monitoring" process (that is, a process using a process template with category Monitoring) only creates test results. And the same step in a "Productive Payroll" process (that is, a process using a process template with category Productive Payroll) creates real results.

• The process template category is also used to simplify configuration and to hide various steps on the frontend UI.

For example, in a "Productive Payroll" process, it is clear that "open control record", "run payroll", "initiate policies", "monitoring" and "close control record" must be included; this could be done automatically without manual configuration. And if a process instance is started, the "open control record" can be started and confirmed automatically if there is no error; in this case, it is not necessary to show this step on the frontend UI. Similarly, if the monitoring step instance is confirmed and closed, the "close control record" can be started and confirmed automatically and therefore need not be shown on the frontend UI.

1. If the process template category for the process template is MO Monitoring, you can specify the Event Handler runtime class.

The Event Handler identifies automatically relevant master data changes and validates these changes against the defined policies for these employees with changes only.

The default runtime class for the Event Handler is CL_PYC_EHI_RELE_CHECK_DEF. It can be used if the instance selection parameter for the process template is ABKRS (Payroll Area) and the Event Handler item is PAR_TYPE PERNR (Personnel Number). It finds out which Event Handler item (PERNR) is relevant to a given process instance.

If you want to use your own runtime class, make sure that the runtime class implements the interface IF_PYC_EHI_RELEVANCE_CHECK and the method GET_PI_RELEVANT_EHI_LIST.

Note:If a monitoring process template is assigned an Event Handler runtime class, you must use the Customizing activity Define Processes to specify whether to enable the Event Handler for the processes that are assigned to this process template.

1. If the process template category for the process template is Planned Off-Cycle - Productive Payroll (PO), specify the selection run time class.

The selection run time class reads infotype 0267 and selects a list of employees for the off-cycle process.

1. If the process template category for the process template is Team Monitoring, you must specify the process template dimenions.

Team dimensions determine according to which criteria teams are defined.

Add parameter types as team dimensions based on your business needs, and define the sequence in which the dimenions are displayed in the Team Configuration app. Possible team dimensions come from table PYC_D_TMDI_DE (predelivered by SAP) and table PA0001 (custom fields of SAP and customer from Infotype 0001 that have been registered in Customizing activity Register Fields of Infotype 0001 as Allowed Team Dimensions).

The authorized user, for example the payroll process manager, can then use the Team Configuration app to set up teams for handling alerts of the Team Monitoring process by specifying the value of each team dimension.

Note

Each team must have a unique combination of values of all team dimensions so that the system can distribute alerts to teams properly. The system checks the team setup when the user tries to activate the team in Team Configuration.

1. Create process step group templates within the process template. For example, Pre-payroll, Payroll, Pay Slip, Posting, and Bank Transfer.
2. Assign step templates to each step group templates.

Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.

Length: 6822 Date: 20240523 Time: 195813     sap01-206 ( 127 ms )