Ansicht
Dokumentation

PYC_PYD_DTL - Define Parameter Types

rdisp/max_wprun_time - Maximum work process run time CPI1466 during Backup
This documentation is copyright by SAP AG.

You use this Customizing activity to do the following:

Define parameter types

Parameter types are used to formulate the input and result for Payroll Control Center.

Define user interface (UI) categories and UI category attributes

A UI category defines either the UI technology for building the UI, for example, SAPUI5 or SAP GUI, or the data service for the UI to get data from the backend, for example, OData.

UI category attributes define the configurable elements of the UI. Some elements on the UI, for example, buttons, might be written in the code and are therefore not defined in UI category attributes.

We recommend that you do not modify the standard parameter types, UI category, and result detail types delivered by SAP.

You can create your own parameter types, UI category, and result detail types by copying a standard one and then making corresponding changes.

You can also do it from scratch.

Define UI category and UI category attributes

UI category can be a UI technology (defines how to build the user interface, e.g. UI5, SAPGUI) or the data service for the UI (how the user interface gets the data from backend, e.g. OData.)

UI category attributes define the configurable elements of user interface.

For OData, the UI Category attributes define from which data entity type the user interface gets the backend data.

Define result detail types and assign UI category attributes to result detail types

Result detail types define the data and operation of the result parameter for the steps. By assigning category attributes to result detail types, you specify the UI settings, such as icons and detail views, of the result detail types.

Runtime Class: Uses the interface IF_PYD_RDT_DTO. The runtime class provides the Set/Get method for the result detail type and the format and enrichment of the data.

Delegation Class: Uses the interface IF_PYD_RDT_DELEGATION. The deligation class defines the Get method for the result detail type. Some result detail types are needed by different result parameters which might not have inheritance relationship. Therefore, you can use the delegation class to maximize the reuse of the Get method for the result detail type.
By default, the system uses the ABAP class CL_PYD_RDT_DELEGATION_BASE.

Support Persistence: Specifies whether the result detail type supports persistence service. The persistence ensures that an object is initialized in a specified state and saves the state of that object when required.

Persistent Class: Uses the interface IF_PYD_RDT_PERSISTENCE. The persistent class provides the Get method for the result details and the list of result details that are to be deleted.

Define parameter types:

EDM Type: Choose an EDM type. This is important for conversion.

User Variant allowed for Par. Type: Whether this parameter type can be saved as a variant.

Parameter types allowed both for user variant and for Input are the available options for the Instance Parameter Type field in VC_PYD_CLASSN and in Define Process Templates.

If you selected Decimal in EDM Type, specify the precision of decimal value and number of decimal digits.

If you selected String in EDM Type, specify the number of digits for the string.

Par. Type reflects Amount: If you select this field, specify the currency for the amount.

Par. Type reflects Quantity: If you select this field, specify the measurement unit.

Par. Type for Time Selection: Parameter types for time selection are the available options for the Time Parameter(PYC_PROC_TPT) field in the Customizing activity Define Process Templates.

Designtime class is for result parameters requiring authorization checks, the class needs to implement interface IF_PYD_PAR_TYPE_DT, like personnel number (PERNR) needs to be filtered according to certain authorization objects before displaying to end user. The designtime class will implement the logic to select all the authorization types supported for the specific parameter.

Runtime class needs to implement interface IF_PYD_PAR_TYPE_RT. This class can provide the certain functions at execution of the check. It includes functions like providing the default value, getting input parameter value list and value descriptions, getting result parameter values and description from the check execution result, and performing authorization checks.

Par. Type allowed for input: Select this field if you want the system to use this parameter to formulate its input. For example, Payroll Area (ABKRS).

Par. Type allowed for result: Select this field if you want the system to use this parameter to formulate its results. For example, Personnel Number (PERNR).

HCM Location: Specify for which HCM location this parameter type can be used.

Data element: the data element ID for the filter/parameter type in the system

Specify which data element the parameter type refers to in the SAP system. For example, in SAP system, Payroll Area uses the 2-digit identifier, then if you enter1 for Payroll Area parameter type, the system will check the formatting.

Assign result detail types to a result parameter type.

This means for each result returned by the system, the user can click each result detail type on the user interface to see detailed information or carry out corresponding activities.

Assign UI category attributes to a parameter type.

This defines the UI settings, such as icons and detail views, of the parameter types.

Assign filter parameter types to a result parameter type.

These filter parameter types are used as the filtering criteria for the list of results by the Payroll Manager to create worklists for Payroll Admins.

For example, if you assign the filter parameter type Company Code (BUKRS) to a result parameter type Personnel Number (PERNR), this means that for the list of personnel numbers with errors returned by the system, the Payroll Manager can assign personnel numbers of Company Code XX to Payroll Admin A and personnel numbers of Company Code YY to Payroll Admin B.

Note for Team Dimensions

For process templates of the category Team Monitoring, you can assign team dimensions to these process templates. Team dimensions define the criteria (for example, payroll area and payroll policy) according to which teams can be set up for handling the alerts that match these criteria.

Previously, you can choose only the parameter types that have been predefined by SAP as team dimensions in table PYC_D_TMDI_DE. As of release EA-HRRXX 608 SP68, you can also define fields from Infotype 0001, including SAP fields and custom fields, as possible team dimensions.

In this Customizing activity, you define these fields as parameter types and pay attention to the following fields:

Data Element: Enter the exact technical name (as in Component Type column) of the field in structure P0001.

Designtime Class and Runtime Class: You must create a custom class inherited from CL_PYD_PAR_TYPE_BASE and rewrite the following methods:

IF_PYD_PAR_TYPE_RT~VALUES_ENRICH_NAME

IF_PYD_PAR_TYPE_RT~VALUES_GET_LIST

These two methods provide the value list for team criteria for setting up teams by using the Team Configuration app.

Please refer to the following sample classes delivered by SAP:

CL_PYD_PAR_TYPE_GSBER

CL_PYD_PAR_TYPE_BUKRS

CL_PYD_PAR_TYPE_BTRTL

After you define these fields as parameters, you can register these fields as allowed team dimensions in Customizing activity Register Fields in Infotype 0001 as Allowed Team Dimensions.

Example: PERNR (Personnel Number)

You have defined a parameter type PERNR (Personnel Number) for result paramter type. And you assign the following result detail types to the parameter type PERNR:

SAP_EEH (Employee Header)

SAP_GOV (Generic Overview)

SAP_SWT (Simple Wage Type)

This means that for the list of personnel numbers that have errors reported by the system, you can click each personnel number to view the detailed information such as employee header, generic overview, and wage type list.

Example: TPY_RES (Test Payroll Result indicator)

If the parameter value is X for this input parameter in the Generate Process Steps (PYC_GENERATE_STEP) report, it will produce the testing payroll run result.

Note that this configuration works only if the Test run checkbox is not selected in the payroll driver.

Example: PYP_INTERVAL (Interval for parallel execution)

This parameter specifies how many people will be grouped into one job to run the payroll. For example, if PYP_INTERAL equals 100, and if you have 1000 pernrs that you need to run payroll for, it will start 10 jobs .

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

Length: 11424 Date: 20240523 Time: 185037 sap01-206 ( 161 ms )