Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PY-XX (Application Component) Payroll: General Parts⤷
PCAL (Package) SAP HR Payroll Application Development
Basic Data
| Data Element | FORNA |
| Short Description | Routine name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR7 | |
| Data Type | CHAR | Character String |
| Length | 7 | |
| Decimal Places | 0 | |
| Output Length | 7 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Routine |
| Medium | 15 | Routine name |
| Long | 20 | Routine name |
| Heading | 8 | Routine |
Documentation
Definition
This field contains the name of the routine that is accessed by Payroll or Time Management when the operation or function is processed.
The name must only be entered if it differs from the convention, according to which the name of the routine consists of OP+object name or FU+object name. For example, the routine for function PRINT is called FUPRINT and does not have to be entered in this field.
There are a number of functions that cannot be executed. Instead, they are used to set specific flags for generating personnel calculation schemas. The routine name DUMMY must be entered for these functions.
If a function is no longer to be executed, the routine name DUMMY2 must be entered.
Note: If the payroll program accesses the routine DUMMY, the personnel number is rejected. An error has occurred in the indexed PERFORM.
Enhancement: To be able to create more functions than the indexed PERFORM technically permits, you have the option of using the international standard subprogram FUXCALL. In the future, every function that has entered this subprogram as the #name of the self-defined form routine# in transaction PE04 (maintenance functions and operations) is assigned the value 170 (= Hex AA) when the schema is generated.
In FUXCALL, the subprogram FUXCALL_NATIO is called for countries and the subprogram FUXCALL_CUST is called for customers. You can use a statement CASE AS-FUNCO. to jump to the actual coding for your new functions (use the name that you entered in PE04 instead of FUXCALL for the form routine).
If you use the standard name suggested in PE04 for your form routine (this is only possible for the special characters _ - $ % in the customer namespace), you do not have to implement FUXCALL_NATIO or FUXCALL_CUST.
Note that performance may worsen for functions created in this way since the indexed perform is no longer directly used for the jump. However, this will only affect performance if the function is called regularly in your schema (for example, in a net iteration).
This also applies to operations with the subprograms OPXCALL, OPXCALL_NATIO, and OPXCALL_CUST, and the statement CASE OP-OPCOD.
History
| Last changed by/on | SAP | 19950403 |
| SAP Release Created in |
