Create Custom Function and Operation For Payroll

&UHDWLQJ)XQFWLRQVDQG
2SHUDWLRQVIRU3D\UROO
$FFRXQWLQJDQG7LPH
0DQDJHPHQW
;
;
$
3

3
/
(
+
5HOHDVH%
&UHDWLQJ)XQFWLRQVDQG2SHUDWLRQVIRU3D\UROO$FFDQG7LPH0DQDJHPHQW
6$3$*
&RS\ULJKW
Copyright 1998 SAP AG. All rights reserved.
No part of this brochure may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without
prior notice.
SAP AG further does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within these materials. SAP AG shall not be liable for any special,
indirect, incidental, or consequential damages, including without limitation, lost revenues or lost
profits, which may result from the use of these materials. The information in this documentation is
subject to change without notice and does not represent a commitment on the part of SAP AG for
the future.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, WINDOWS, NT, EXCEL and SQL-Server are registered trademarks of
Microsoft Corporation.
IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390,
AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.
OSF/Motif is a registered trademark of Open Software Foundation.
ORACLE is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX-OnLine IRU6$3 is a registered trademark of Informix Software Incorporated.
UNIX and X/Open are registered trademarks of SCO Santa Cruz Operation.
ADABAS is a registered trademark of Software AG.
SAP, R/2, R/3, RIVA, ABAP/4, SAP ArchiveLink, SAPaccess, SAPmail,
SAPoffice, SAP-EDI, R/3 Retail, SAP EarlyWatch, SAP Business Workflow, ALE/WEB,
Team SAP, BAPI, Management Cockpit are registered or unregistered trademarks of SAP
AG.
,FRQV
,FRQ
0HDQLQJ
Caution
Example
Note
-XQH
6$3$*
&RQWHQWV
&UHDWLQJ)XQFWLRQVDQG2SHUDWLRQVIRU3D\UROO$FFRXQWLQJDQG
7LPH0DQDJHPHQW
&UHDWLQJ)XQFWLRQV
&UHDWLQJ&KDQJLQJDQG'HOHWLQJ)XQFWLRQV
$FWLYDWLQJ)XQFWLRQV
'RFXPHQWLQJ)XQFWLRQV
&UHDWLQJ2SHUDWLRQV
&UHDWLQJ&KDQJLQJDQG'HOHWLQJ2SHUDWLRQV
$FWLYDWLQJ2SHUDWLRQV
'RFXPHQWLQJ2SHUDWLRQV
7UDQVSRUW&RQQHFWLRQ
&UHDWLQJDQ2SHUDWLRQ&KHFN
'HWDLOHG'HVFULSWLRQRIWKH2SHUDWLRQ&KHFN
Check Tables T52BM-T52BO .................................................................................................. 17
*HQHUDO6WUXFWXUDO'HVFULSWLRQ
Notes on Rule Type.................................................................................................................. 19
Admissible Types for Parameter and Value Check.................................................................. 20
Checking the Parameters of an Operation ............................................................................... 21
Using Dummy Statements........................................................................................................ 22
'HVFULSWLRQRI6WUXFWXUH$FFRUGLQJWR2SHUDWLRQ7\SH
Normal Operations ................................................................................................................... 24
Decision Operations ................................................................................................................. 25
Jump Operations ...................................................................................................................... 26
Operations Which Run a Subrule............................................................................................. 27
$VVLJQLQJ2SHUDWLRQVWR,QFOXGHV
*HQHUDWLQJWKH5XOH&KHFN
5HSRUWVDQG7DEOHVIRU)XQFWLRQVDQG2SHUDWLRQV
Report Generation from T52A0 ................................................................................................ 31
Accessing Functions ........................................................................................................... 32
Generating a Calculation Rule Check ...................................................................................... 33
Generation/Checking of Schemas............................................................................................ 35
Number and Name for Turbocase............................................................................................ 36
Assigning Values to Objects..................................................................................................... 37
Function Parameters ................................................................................................................ 38
Valid Function Parameter Values............................................................................................. 39
Use of Infotypes for Objects ..................................................................................................... 40
Operation Models ..................................................................................................................... 41
Assigning Models to Operations............................................................................................... 42
Operation Parameters .............................................................................................................. 43
3URJUDP7\SH0,;
-XQH
6$3$*
&UHDWLQJ)XQFWLRQVDQG2SHUDWLRQVIRU3D\UROO
$FFRXQWLQJDQG7LPH0DQDJHPHQW
&UHDWLQJ)XQFWLRQV>3DJH@
&UHDWLQJ2SHUDWLRQV>3DJH@
&UHDWLQJDQ2SHUDWLRQ&KHFN>3DJH@
7KH0,;3URJUDP7\SH>3DJH@
-XQH
6$3$*
&UHDWLQJ)XQFWLRQV
&UHDWLQJ)XQFWLRQV
1. Create the coding.
Customer functions are stored in include RPCBURZ0.
2. Use transaction PE04 to create the function (see Creating, Changing and Deleting
Functions [Page 6]).
3. Activate the function (see Activating Functions [Page 7])
4. Document the function (see Documenting Functions [Page 8])
-XQH
6$3$*
Transaction PE04 enables you to create, change and delete functions.
In the 1DPHfield, enter the function name. The name may contain a maximum of 5 characters.
Customer functions must contain a special character.

Assign the function an object class (3D\UROO or 7LPH0DQDJHPHQW) and the object type )XQFWLRQ.
When creating a new function or changing an existing one, you can make the following settings
in the screen which now appears:
Name of form routine

If the routine name differs from the naming convention FU<Funktionsname>, select
the 6HOI'HILQHGfield, and enter the routine name.
Country assignment
In this block, you can select the countries for which you want the function to be
available.
If you delete a country from the country assignment block, it will also
automatically be deleted from country assignment of parameter values.
Parameters
In the 3DUDPHWHU/LVWyou can edit the parameter and its characteristics (number,
parameter name, meaning, parameter type, or obligatory parameter).
Parameter value
If the parameter is of parameter type EODQNyou must also specify the parameter
value.
To do this, select a parameter and choose 6HOHFW'HWDLO The system displays a list in
which you can enter all values for this parameter and their meanings.
You can use the &KRRVHkey in this list to define the valid countries for each individual
parameter value.
The system only displays the countries you have selected for the country
assignment for the complete function.
Infotypes used
If the function belongs to the 3D\UROO object class, you must specify the infotypes
used. Choose ,QIRW\SHV8VHG
Choose 6DYH This activates the transport connection [Page 14].

Although you have created the function, it cannot be used yet. To you first perform several
checks and generations (refer to Activating Functions [Page 7]).
-XQH
6$3$*
$FWLYDWLQJ)XQFWLRQV
$FWLYDWLQJ)XQFWLRQV
Enter the name of the function in the field provided. Assign the function an object class (3D\UROO
or 7LPH0DQDJHPHQW) and the object type )XQFWLRQ.
Choose $FWLYDWH The system starts all required reports [Page 30]
-XQH
6$3$*
Function documentation is recorded in RPDSYS00. For more information, see RPDSYS00 under
0DLQWHQDQFHDQG6WUXFWXUH
Create a DSYS module for your function. The name of the module is as follows:
Object type:
)81& if the object class is Payroll or )817 for Time Management.
Object name:
This is the name you used when you created the function.
You can now write the documentation for your function in this module.
If you want the system to display a list of the parameters and their values with the module, you
must insert an include reference at the end of your documentation, referring the reader to the
module )8;&[[[[[ or )8;7[[[[[
(for example, !,1)8;&,)) according to the object class in question (Payroll & or Time
Management 7). [[[[[ stands for the name of your function.
Function IF (Payroll object class).

The documentation is stored in the DSYS module FUNC.IF:
7DVN
7KLVIXQFWLRQHQDEOHV\RXWR
!,1)8;&,)
-XQH
6$3$*
&UHDWLQJ2SHUDWLRQV
&UHDWLQJ2SHUDWLRQV
1. Create the coding.
Customer operations are stored in include 53&%85=.
2. Use transaction PE04 to create the operation.
3. If necessary, write your own coding for the operation check [Page 15].
4. Activate the operation.
5. Use the operation in the 0DLQWDLQ3HUVRQQHO&DOFXODWLRQ5XOHVtransaction (PE02)
6. To check the function, choose &KHFN
7. Test all possible parameters.
Unpermitted parameters should trigger an error message.
8. Document the new operation.
1. or more information on creating and generating your own check, see Creating
an Operation Check [Page 15]. However, it is rarely necessary to create and
generate your own check.
2. If you have changed the country assignment of a function you already
activated, you may have to regenerate the schemas. If this is the case, the
system displays the appropriate report to be started. Execute the transport of
the schemas PDQXDOO\.
-XQH
6$3$*
Transaction PE04 enables you to create, change and delete operations.
In the 1DPHfield, enter the operation name. Select an object class and an object type. The name
may contain a maximum of 5 characters.
Customer operations must contain a special symbol.

Assign the operation an object class (3D\UROO or 7LPH0DQDJHPHQW) and the object type
2SHUDWLRQ.
When creating a new operation or changing an existing one, you can make the following settings
in the screen which now appears:
Name of form routine

If the routine name differs from the naming convention FU<operation name>,
select the 6HOI'HILQHGfield, and enter the routine name.
Country assignment
In this block, you can select the countries for which you want the operation to be
available.
If you delete a country from the country assignment block, it will also
automatically be deleted from country assignment of parameter values.
Model
Assign a model to your operation in this field.
If no suitable model exists, create a model in table T52BM [Page 30].
Choose 2ZQ&KHFN5RXWLQH
If you have your own check routine for the operation, please flag this checkbox.
Parameters
The 3DUDPHWHU/LVW allows you to maintain parameters and their characteristics.
Choose &KRRVH'HWDLOto maintain the parameter values and their country
assignment.
The system only displays the countries you have selected for the country
assignment for the complete operation.
Choose 6DYH This activates the transport connection [Page 14].
Although you have created the operation, it cannot be used yet. To you first perform several
checks and generations (refer to Activating Operations [Page 12]).

-XQH
6$3$*
1. If you have created an operation and want to write your own operation check
[Page 15], you must create the check.
2. If you have changed the country assignment of an operation which has
already been activated, you may have to make corrections to personnel
calculation rules. The system displays the appropriate report to be started.
Execute the transport of the calculation rules PDQXDOO\.
-XQH

6$3$*
Enter the name of the operation in the field provided. Assign the operation an object class
(3D\UROO or 7LPH0DQDJHPHQW) and the object type )XQFWLRQ.
Choose $FWLYDWH The system starts all required reports [Page 30]

-XQH
6$3$*
Operation documentation is recorded in RPDSYS00. For more information, see RPDSYS00
under 0DLQWHQDQFHDQG6WUXFWXUH Create a DSYS module for your operation. The name of the
module is as follows:
1. Object type:
23(& if the object class is Payroll or 23(7 for Time Management.
2. Object name:
Object name: This is the name you used when you created the function.
You can now write the documentation for your function in this module.
-XQH

6$3$*
7UDQVSRUW&RQQHFWLRQ
7UDQVSRUW&RQQHFWLRQ
Transaction PE04 has an automatic transport link.
Logical transport objects are used to transport the table entries for a function or operation
(including documentation in RPDSYS00). Importing these objects also triggers generation of the
indexed Perform and the schema or personnel calculation rule check in the target system. (In the
original system, this is done by activating the function or operation.) The logical transport objects
are written to the selected transport request when the function or operation is saved. This means
it is no longer necessary to transport the includes or manually place table entries on a transport
request.
The names of the new transport objects are as follows:

1DPH
7\SH
1DPHUDQJH
$UHD
PFCS
Function
SAP
Payroll
PFCC
Function
Customer
Payroll
PFTS
Function
SAP
Time Management
PFTC
Function
Customer
Time Management
POCS
Operation
SAP
Payroll
POCC
Operation
Customer
Payroll
POTS
Operation
SAP
Time Management
POTC
Operation
Customer
Time Management
-XQH
6$3$*
This section contains the following information:
Detailed description of the operation check [Page 16]

This describes how you create the check routine and which parts of the program are
required, depending on the type of operation.
Assigning Operations to Includes [Page 28]

The section indicates in which includes you must enter the coding.
Generating the Rule Check [Page 29]

The procedure for generating checks is described.
-XQH

6$3$*
A check is required for each operation. This check ensures that the operation parameter and the
operation syntax are correct.
The first part describes which tables must be maintained in order to check the parameter settings
for the operations. This section also explains how to maintain the tables and what they can be
used to check. If you want to create further checks, parts 2 and 3 describe how to do this.
The second part describes the general procedure and predefined routines which can be used
according to the operation type. The principal purpose of this part is to check that the parameters
are correct and complete.
The third part outlines the special features of the various types and specifies which variables
must be entered or which routines must be accessed for each type in order to determine whether
the syntax of the operation is correct.
The entries always include a reference to the long text of an error message which would be
displayed during a check on a personnel calculation rule if an error was discovered in the
operation. This is to emphasise the importance of an entry.
6HHDOVR
Check Tables T52BM-T52BO [Page 17]
General Structural Description [Page 18]
Description of Structure According to Operation Type [Page 23]

-XQH
6$3$*
&KHFN7DEOHV7%07%2
&KHFN7DEOHV7%07%2
Each operation is assigned a model. This assignment is made by means of the model name.
Each operation is assigned a model name in table T52BN. If you want to write a further check,
indicate this in the table. After editing the table, generate the check program (report
RPUGCC00).
Enter the valid parameters for the operation in table T52BO. Note the model for the operation.
Under the name of the operation, enter the O-block in the model. The F-block belongs to the
field, and the S-block to the indicator. Describe the V-block under Value. Enter the type and
length of the value. If the processing of the rule is changed by the operation, enter this under
Reaction. For example, if the variable key is created, enter D or ?.
If you enhance the variable key, you must also specify this (type and length).
In the second line, enter a short text for the parameter. This text should be displayed in
RPDSYS00 along with the documentation on the operation.
If you want to write a further check, you can specify this by means of the $FFHVV &KHFN field in
the check program, for example, operation VALEN.
-XQH

6$3$*
Notes on Rule Type [Page 19]
Admissible Types for Parameter and Value Check [Page 20]
Checking the Parameters of an Operation [Page 21]
Use of Dummy Statements [Page 22]

-XQH
6$3$*
1RWHVRQ5XOH7\SH
1RWHVRQ5XOH7\SH
You must enter an appropriate rule type in the rule line for all decision / jump operations. Only
one operation is allowed here.
Here you may only enter a decision operation (type '), although several operations may be
entered in one line.
If a line contains only normal operations (without decision or jump) and a rule type is still
specified, an error will occur during the check.
-XQH

6$3$*
$GPLVVLEOH7\SHVIRU3DUDPHWHUDQG9DOXH&KHFN
$GPLVVLEOH7\SHVIRU3DUDPHWHUDQG9DOXH&KHFN
The types listed here can be used to check the parameters of an operation and, with some
exceptions, to check the specification entered in the variable key:
3HUPLWWHG7\SHV

7\SH
0HDQLQJ
MASK
The only characters allowed are $= and .
WGTYP
Only one wage type is allowed, which must be among those listed in table
T512W.
TWGTYP
Only one wage type is allowed, which must be among those listed in table
T512W or corresponds to one of the identifiers .
TIMTYP
Only one corresponding time type is allowed, which must be among those
listed in table T555A.
DAYPRG
Only one daily work schedule variant is allowed, which must be among
those listed in table T550A.
HRS
The different parameters of time management operation HRS are checked

using their own type.
NUMERIC
The only characters allowed are .
ALPHA
The only characters allowed are $=.
ALL
All characters which can be printed and displayed.

Tip: For example, if operation WGTYP? is used, a wage type is placed in
the variable key, therefore the type WGTYP should be used. However, if
operations VAOFF or VALEN are used to process only part of the data, in
other words, ARG_LEN less than 4, you should use the type ALL.
COMPARE
The only characters allowed are DQG!.
PLUSMINUS
The only characters allowed are and -.
YESNO
The only characters allowed are <and1.
RELEVANCE
The only characters allowed are 5and, (R = relevant; I = irrelevant).
SWITCH
The only characters allowed are ; and 6SDFH. This type should be used for
X fields. Please note that it is not possible to carry out a direct query using
a space in the variable key, but instead only as an OTHERS case for "X".
SPECIAL
The allowed characters are not specified directly. This type cannot be used
in connection with a specification for the variable key.
-XQH
6$3$*
&KHFNLQJWKH3DUDPHWHUVRIDQ2SHUDWLRQ
&KHFNLQJWKH3DUDPHWHUVRIDQ2SHUDWLRQ
There are two routines for checking parameters. Routine CHECK_TYPE checks whether there
are characters belonging to a particular type in the position being checked. If the positions are
numerical, routine CHECK_RANGE checks whether the value lies within the specified value
range.
The access must be as follows:
PERFORM CHECK_TYPE USING OPERATION+ofs(len) type SPACE.
or
PERFORM CHECK_TYPE USING OPERATION+ofs(len) SPECIAL string.
PREFORM CHECK_RANGE USING OPERATION+ofs(len) low high.
0HDQLQJRISODFHKROGHUV
ofs, len
Positions to be checked
type
Admissible type with the exception of the type SPECIAL
string
List of all allowed characters
low
First allowed value
high
Last allowed value
If the value lies out of the allowed value range, the system displays an error message.
If an error has occurred after the routine is called, you must end processing (for example, with
the command EXIT).
-XQH

6$3$*
8VLQJ'XPP\6WDWHPHQWV
8VLQJ'XPP\6WDWHPHQWV
There are operations which cannot be assigned uniquely to a particular country and program
class. However, some parameters may be admissible for all combinations while others are only
admissible for certain countries or program classes. When creating the version of the check for a
specific program class or country, all pieces of coding which are not admissible for the
combination in question are removed. An error message is therefore displayed if you use an
operation parameter which is not admissible for the country or program class in question.
This is done by working with certain dummy statements. The parts of the coding which are
specific to particular program classes and countries are surrounded by an IF condition.
Please note that these dummy statements can only occur in commentry lines.
The procedure is illustrated by the following example:
ERROR = 4. Since parts of the coding are removed later, it is generally

to be assumed that an error has occurred, and the error
should only be reset to zero if the parameter settings
are correct.
"Coding at this point means that there is no delimitation to specific
"countries or program classes
* CIF PCL:T. "Program elements which are only valid for Time Management
"should be positioned here.
* CENDIF.
* CIF PCL:C.
Coding valid for Payroll Accounting
* CIF CNT:01.
Coding valid for Payroll Accounting Germany
* CENDIF.
* CIF CNT:02,03.
"Coding valid for Payroll Accounting Switzerland and Austria
* CENDIF.
* CENDIF.
In this way you can exercise detailed control over the admissibility of parameters. We plan to
extend this delimitation function to component level at a later date. It is only necessary to use
these dummy statements if you cannot assign an operation to a program class or to a country on
the parameter level.

-XQH
6$3$*
There are 4 types of operations:
Normal operations [Page 24]
Decision operations [Page 25]
Jump operations [Page 26]
Operations which run a subrule [Page 27]
-XQH

6$3$*
1RUPDO2SHUDWLRQV
1RUPDO2SHUDWLRQV
There are operations which end processing in the line in which they appear (for example,
ERROR or NEXTR). For this reason, this operation may not be followed by others. You must set
a switch for these operations.
OP_FORCED_STOP = X.
If further operations follow this operation, the system displays an error message.

-XQH
6$3$*
'HFLVLRQ2SHUDWLRQV
'HFLVLRQ2SHUDWLRQV
The statements listed below must be entered in the coding for every decision operation:
The type of operation must be defined:

OP_TYPE = DECISION.
If a different rule type is specified for the line containing the operation, the system
displays an error message when the check is performed.
If there is more than one decision operation in a line, an error will occur.
This does not apply to rule type 6. Since no entry is made in the variable key, there
can be more than one decision operation.
A decision operation enters data in the variable key. You must specify the type and
length of the specification.
ARG_TYPE = x.
x = admissible type for specification
ARG_LEN = y.
y = maximum length of specification
The length can be reduced by operations VAOFF and VALEN. For this reason, you
must call a corresponding routine afterwards to determine the length the specification
is to have in the variable key.
3(5)250'(7(50,1(B/(1*7+86,1*$5*B/(19$2))9$/(1
The above does not apply to operations AMT, NUM and RTE. For these operations,
the offset and length are specified directly as a parameter, so that the coding might
be as follows:
PERFORM DETERMINE_LENGTH USING ARG_LEN
OPERATION+ofs1(len1)
OPERATION+ofs2(len2).
For error processing, the error number must be queried, for example,:
IF ERROR GT 0. EXIT. ENDIF.
The routine tests whether the section determined by VAOFF and VALEN is
admissible. Since the variable key can only contain a certain number of characters, it
may not be possible to enter the new specification there.
The routine also tests whether the variable key has been set up according to the
decision operations.
-XQH

6$3$*
-XPS2SHUDWLRQV
-XPS2SHUDWLRQV
You must enter the following variables to ensure that the check can function correctly.

23B7<3( *272
A jump operation ends processing in the line in which it appears and continues with
the new rule. For this reason, this operation may not be followed by others.
23B)25&('B6723
;
If further operations follow this operation, the system displays an error message.
The rule to be accessed must be specified.

23B&&<&/ 23(5$7,21RIVOHQ
If a payroll type is specified for the operation:

23B$%$57 23(5$7,21RIVOHQ
If the wage type is to be generalized:

23B/*$57

The system uses a check to determine whether or not the rule exists. If the rule does not exist,
the system displays an error message.
If youe enter the current rule as the new rule, this also triggers an error message.

-XQH
6$3$*
2SHUDWLRQV:KLFK5XQD6XEUXOH
2SHUDWLRQV:KLFK5XQD6XEUXOH
The variables below must be entered in order to carry out the necessary checks.

23B7<3( 3(5)250
You must specify the rule to be run.

23B&&<&/ 23(5$7,21RIVOHQ)
If a payroll type is specified for the operation:

23B$%$57 23(5$7,21RIVOHQ
If the wage type is to be generalized:

23B/*$57

The system uses a check to determine whether or not the rule exists. If the rule does not exist,
the system displays an error message.
If youe enter the current rule as the rule to be executed, this also triggers an error message.
-XQH

6$3$*
In accordance with various criteria, the coding of an operation must be entered in certain
includes:

This is generally used to determine whether the routine is a main routine in the
operation or a subroutine. The names of main routines are made up of the ID OP
and the operation name. These routines are entered in the include which has an F
as placeholder <a>. All other routines are in the include with an S as placeholder
<a>.
Since you can only load members up to a certain size into the Editor, all includes in a
group are numbered sequentially - this number is represented by placeholder <z>.
A further criterion is whether the operation is international or can be assigned to a

group of countries, or whether it can only be assigned to one program class and
country grouping (unique assignment). Placeholder <x> stands for the program class
and <y> for the HR country indicator which is derived from the country grouping (table
T500L). The HR country indicator for program class T is always 0.
RPxCOayz includes contain the operations which can be assigned uniquely.

Examples of these are the Time Management operations, which are not countrydependent, and the operations assigned to one country in table T52B5. By definition,
the routines in these includes can contain no dummy statements. The remaining
operations must be entered in the RPCCOa0z includes.
When a rule check is generated for a particular program class and country, the
system removes inadmissible operations and parameters from the RPCCOa0z
includes and uses them to generate the RPUCOxyz includes. The RPxCOayz
includes are selected by program class and country and taken over unchanged.
If you need to create new includes, please set the class to PU02 (HR Utilities Payroll
Accounting) in the attributes.
-XQH
6$3$*
Report RPUGCC00 generates various members (main report and includes) according to the
parameters set for the SURJUDPFODVV and FRXQWU\JURXSLQJ. These PHPEHUV are required in
order to check the specified parameter combination in the rule editor.
The following provides an overview of the includes required for generation and the members
which are generated:
RPxCOayz
Contains the coding for all operations for which unique assignments can
be made:
-
Time Management operations
Payroll operations if they can be assigned to one country.
The &XVWRPHU&KHFN5RXWLQHfield must be flagged in table T52BN

(Input+output).
RPCCOa0z
Contains the coding for all operations which do not meet the criteria
described above. The &XVWRPHU&KHFN5RXWLQHfield must be flagged in
table T52BN (Input).
RPUCCxy0
This is the main report accessed from the Rule Editor (Output).
RPUCOxyz
Contains the coding for all operations which are admissible for the
program class and country grouping in question and are not already in an
RPxCOayz include (Output).
Meaning of placeholders:
a
Type of routine
a=F
Main routines for operations
a=S
Subroutines for operations
Program class
x=C
Payroll
x=T
Time Management
For program class C, this is the HR country indicator, which is derived from the HR
country grouping (T500L) (with program class T: y = 0).
Sequential numbering
Please note that to call up the check you require another include, which is generated by another
report.
RPxOIPy0
-XQH
Contains the indexed PERFORM.

6$3$*
The following contains a list of the tables and reports for use in maintaining functions and
operations.
All tables for maintaining functions and operations for Payroll Accounting and
Time Management are edited by means of transaction PE04 (with the exception
of table T52BM, 2SHUDWLRQ0RGHOV).
It is not usually necessary to maintain the tables directly using transaction SM30
or SM31, and this should be avoided in the interests of the consistency of the
data.
The following tables are used for functions and operations:
Internal object numbers (view V_T52A0) [Page 36]
Valid object values (table T52B5) [Page 37]
Function parameter (view V_T52B6) [Page 38]
Function parameter value (view V_T52B7) [Page 39]
Use of infotypes with objects (view V_T52B9) [Page 40]
Operation model (table T52BM) [Page 41]
Assignment of models to operations (table T52BN) [Page 42]
Operation parameter (view V_T52BO) [Page 43]
The following reports are used to activate functions and operations:

Report generation from T52A0 (choice of procedure), report generation from T52A0
[Page 31].
Generation of calculation rule check, generation of a calculation rule check [Page 33]
Generation/checking of schemas, generation/checking of schemas [Page 35].
-XQH
6$3$*
5HSRUW*HQHUDWLRQIURP7$
5HSRUW*HQHUDWLRQIURP7$
5HSRUW538&7
The Internal Object Numbers [Page 32] (T52A0) and $VVLJQPHQWRI9DOXHVWR2EMHFWV (T52B5)
tables are used to generate includes and programs for the various payroll programs.
Method:
TURBOCASE directly in main report
generating an include
The reports generated comply with the following naming conventions:
Functions:
RPxASFy0
Include in main report
X stands for the program class and y for the country grouping (y = 0 if x = T).
Operations:
RPxBO1y0
Include in main report
X stands for the program class and y for the country grouping (y = 0 if x = T).
-XQH

6$3$*
$FFHVVLQJ)XQFWLRQV
$FFHVVLQJ)XQFWLRQV
Each payroll driver contains an include. In this include, routine AS-FUNKTION accesses the
individual function modules in an indexed PERFORM. To facilitate this procedure, each function
is assigned a number between 1 and 255 in table T52A0. Transaction PE04 is used to make this
assignment.
The include RPCASFx0 is generated by the report RPUCT700 [Page 30]. The system starts
report RPUCT700 automatically when the function is activated using transaction PE04.

-XQH
6$3$*
*HQHUDWLQJD&DOFXODWLRQ5XOH&KHFN
5HSRUW538*&&
This report generates various PHPEHUV(main report and includes) according to the 3URJUDP
&ODVVand &RXQWU\*URXSLQJparameter These PHPEHUV are required in order to check the
specified parameter combination in the rule editor.
This section describes the includes required for generation and the members which are
generated:
RPxCOayz
Contains the coding for all operations for which unique assignments can be made:
7LPH0DQDJHPHQW operations
3D\UROO operations if they can be assigned to one country. The &XVWRPHU&KHFN

5RXWLQHfield (Input + Output) must be flagged in table T52BN, $VVLJQLQJ0RGHOV
WR2SHUDWLRQV.
RPCCOa0z
Contains the coding for all operations which do not meet the criteria described above.
The &XVWRPHU&KHFN5RXWLQHfield must be flagged in table T52BN (Input).
RPUCCxy0
This is the main report accessed from the Rule Editor (Output).
RPUCOxyz
Contains the coding for all operations which are admissible for the program class and
country grouping in question and are not already in an RPxCOayz include (Output).
<A> stands for the type of routine (a = F: Main routines for operations, a = S:
Main routines for operations)
<x> stands for program class
<y> stands for RP country indicator, derived from the RP country modifier.
<z> stands for a sequential number.
Please note that to call up the check you require another include, which is generated
by another report.
RPxOIPy0
Contains the indexed PERFORM.
5HSRUW3DUDPHWHUV
6(/(&7237,21 &RXQWU\JURXSLQJ
&KHFN
If 7LPH0DQDJHPHQW is entered as the program class, you must not enter a country grouping.
If 3D\UROO$FFRXQWLQJ is entered as the program class, you may enter any country grouping from
table T500L.
-XQH

6$3$*
8VH
The country groupings are used to determine the HR country indicator, which is needed when
naming the report to be generated. It is also used when selecting the valid operations and
parameters. A rule check is created for each country grouping.
3$5$0(7(5
3URJUDPFODVV
&KHFN
The only entries allowed are T for 7LPH0DQDJHPHQW and C for 3D\UROO$FFRXQWLQJ.
8VH
The program class is used when naming the report to be generated and to determine the
admissible operations and parameters.

-XQH
6$3$*
*HQHUDWLRQ&KHFNLQJRI6FKHPDV
*HQHUDWLRQ&KHFNLQJRI6FKHPDV
5HSRUW5386&*
RPUSCG00 is an important report in Payroll Accounting. It determines whether a schema must
be generated again, and if necessary, generates schemas.
Schemas are saved in tables and are accessed by generating the PCL2 file. When the payroll
driver is started, it reads the schemas from PCL2 using report RPUSCG00. This report checks
each schema to determine whether it has been changed since it was last generated. If this is the
case, the report checks and generates the schema.
However, the system also generates the schema if those specified are not yet stored in file
PCL2.
You can start the generation from the initial screen of the schema maintenance function. Choose
6FKHPD*HQHUDWH The system also evaluates the LSCHE feature. You can use this feature to
specify the languages, apart from the logon language, in which the schema is to be generated.
-XQH

6$3$*
1XPEHUDQG1DPHIRU7XUERFDVH
1XPEHUDQG1DPHIRU7XUERFDVH
7DEOH7$
All objects used in the payroll driver and in the Time Management report are entered in this table.
All objects are sorted by program class and object type.
This table is used as a check table. To increase performance, it is also possible to assign a
number to each object. This means that the objects are no longer identified by their names in the
programs but by their "Turbocase number". This table is maintained automatically using
transaction PE04.

-XQH
6$3$*
$VVLJQLQJ9DOXHVWR2EMHFWV
$VVLJQLQJ9DOXHVWR2EMHFWV
7DEOH7%
Objects are assigned attributes in this table. The objects are identified by their object class and
object name.
This table is maintained automatically using transaction PE04.
This table is not a check table. The objects, attributes and part combinations entered here are
checked in the following tables:
Object classes
Table T52B1
Attribute
Table T52B2
Valid object class attributes
Table T52B3
Valid attribute values
Table T52B4
-XQH

6$3$*
)XQFWLRQ3DUDPHWHUV
)XQFWLRQ3DUDPHWHUV
7DEOH7%
This table is a check table for functions in the 3D\UROO$FFRXQWLQJand 7LPH0DQDJHPHQW
components. All admissible function parameter combinations are defined here for each program
class.
You can also specify how entries are to be made in transaction PE01 (schema maintenance) in
this table, in other words, the column (parameter 1to 4) for the entry and whether or not the entry
must be made. The entry value can either be determined from the 3DUDPHWHU7\SH column or
taken from the 9DOXH column in table T52B7, )XQFWLRQ3DUDPHWHU9DOXHV.

-XQH
6$3$*
9DOLG)XQFWLRQ3DUDPHWHU9DOXHV
9DOLG)XQFWLRQ3DUDPHWHU9DOXHV
7DEOH7%
In this table you can set the valid specifications for the function parameter combinations for which
no entry can be made in the 3DUDPHWHU7\SHfield in table T52B6, )XQFWLRQ3DUDPHWHUV.
-XQH

6$3$*
8VHRI,QIRW\SHVIRU2EMHFWV
8VHRI,QIRW\SHVIRU2EMHFWV
7DEOH7%
Data fields for +50DVWHU'DWD7LPH0DQDJHPHQWand$SSOLFDQW'DWD are grouped together
logically in infotypes.
Infotype Family, Work Center, Basic Pay

The following naming conventions apply to infotypes:
Infotypes 0000 to 0999
HR master data and possibly applicant data
Planning and Development data
Time data
Applicant data
Customers own
In this table, you can specify which infotypes are read by an object during payroll for each
program class and object type.
The program class determines where an object, for example, a schema or rule, is used
(T = Time Management, C = Payroll Accounting).
The object type determines the purpose of the object. This means that the object TIME can be
used either as a function (with object type FU) or as an operation (with object type OP).
At present, object types )8 (functions) and 23 (operations) are admissible,

although only object type )8 is evaluated during schema generation.

-XQH
6$3$*
2SHUDWLRQ0RGHOV
2SHUDWLRQ0RGHOV
7DEOH7%0
Each model name is assigned to a model in this table. The system uses this model to check the
operations and the permitted parameters for 3D\UROO$FFRXQWLQJand 7LPH0DQDJPHQW
You do not need to maintain this table since a new operation is assigned to a model entered
here. However, if none of the existing models is suitable, you must create one.
This entry will not be transported automatically.
-XQH

6$3$*
$VVLJQLQJ0RGHOVWR2SHUDWLRQV
$VVLJQLQJ0RGHOVWR2SHUDWLRQV
7DEOH7%1
In this table each operation from 3D\UROO$FFRXQWLQJand 7LPH0DQDJHPHQWis assigned a model.
The system uses this model to check the operations and the permitted parameters for 3D\UROO
$FFRXQWLQJand 7LPH0DQDJHPHQW

-XQH
6$3$*
2SHUDWLRQ3DUDPHWHUV
2SHUDWLRQ3DUDPHWHUV
7DEOH7%2
This table is a check table for operations in the 3D\UROO$FFRXQWLQJand 7LPH0DQDJHPHQW
components.
You can define all admissible combinations of operations and parameters for each program
class. You can also define specifications for the operation-parameter combinations.
This table is used in the check in transaction PE02, 0DLQWDLQ3D\UROO5XOHV, and also in the value
help for the individual operations.
-XQH

6$3$*
3URJUDP7\SH0,;
3URJUDP7\SH0,;
Program type MIX (see also RPDSYS00 documentation on function PGM) enables you to create
a schema to carry out both payroll accounting and evaluation (in other words, data transfer to
FI/CO).
You can use program type MIX for simulate payroll accounting and evaluate the generated data
directly. This is of particular use, for example, in Cost Planning.
Function XCAEV splits the schema into the payroll part and the evaluation part. Program
RPCALCX0 then carries out the following steps for each of the selected personnel numbers:
Payroll accounting, taking account of individual and general retroactive runs.
Evaluation of results obtained in the first step.
No database updates take place with program type MIX.

-XQH

Create Custom Function and Operation For Payroll

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Create Custom Function and Operation For Payroll

Uploaded by

Copyright:

Available Formats

&UHDWLQJ)XQFWLRQVDQG

Customer functions must contain a special character.

Name of form routine

Choose 6DYH This activates the transport connection [Page 14].

Function IF (Payroll object class).

Customer operations must contain a special symbol.

Name of form routine

If no suitable model exists, create a model in table T52BM [Page 30].

Detailed description of the operation check [Page 16]

Assigning Operations to Includes [Page 28]

Generating the Rule Check [Page 29]

The only characters allowed are $= and .

The different parameters of time management operation HRS are checked

The only characters allowed are .

The only characters allowed are $=.

All characters which can be printed and displayed.

The only characters allowed are  DQG!.

The only characters allowed are and -.

The only characters allowed are <and1.

The only characters allowed are 5and, (R = relevant; I = irrelevant).

Admissible type with the exception of the type SPECIAL

List of all allowed characters

First allowed value

Last allowed value

ERROR = 4. Since parts of the coding are removed later, it is generally

Normal operations [Page 24]

Decision operations [Page 25]

Jump operations [Page 26]

Operations which run a subrule [Page 27]

The type of operation must be defined:

x = admissible type for specification

y = maximum length of specification

The type of operation must be defined:

The rule to be accessed must be specified.

If a payroll type is specified for the operation:

If the wage type is to be generalized:

The type of operation must be defined:

You must specify the rule to be run.

If a payroll type is specified for the operation:

If the wage type is to be generalized:

A further criterion is whether the operation is international or can be assigned to a

RPxCOayz includes contain the operations which can be assigned uniquely.

Time Management operations

Payroll operations if they can be assigned to one country.

The &XVWRPHU&KHFN5RXWLQHfield must be flagged in table T52BN

Main routines for operations

Subroutines for operations

Contains the indexed PERFORM.

Internal object numbers (view V_T52A0) [Page 36]

Valid object values (table T52B5) [Page 37]

Function parameter (view V_T52B6) [Page 38]

Function parameter value (view V_T52B7) [Page 39]

Use of infotypes with objects (view V_T52B9) [Page 40]

Operation model (table T52BM) [Page 41]

Assignment of models to operations (table T52BN) [Page 42]

Operation parameter (view V_T52BO) [Page 43]

The following reports are used to activate functions and operations:

Generation/checking of schemas, generation/checking of schemas [Page 35].

TURBOCASE directly in main report

The reports generated comply with the following naming conventions:

Include in main report

Include in main report

3D\UROO operations if they can be assigned to one country. The &XVWRPHU&KHFN

Choose 6DYH This activates the transport connection [Page 14].

The only characters allowed are $= and .

The only characters allowed are .

The only characters allowed are $=.

The only characters allowed are DQG!.

The only characters allowed are and -.