OUTWP - Load Work Center and Basic Pay Data

Object

Operation

Use

The OUTWP operation loads the currently valid work center and basic pay
data.

If you use the operation OUTWP in an evaluation schema, you can only
query the fields that are part of the payroll results (generally as an
entry in table WPBP). It is not permissible to query values from
infotypes within the framework of evaluation schemas, since you must be
able to repeat evaluation runs in retroactive accounting and so they
cannot be based on other information.

Input

The WPBP table (Work Center/ Basic Pay) serves as input for this
operation.

Procedure

You can use this operand to determine the field of table WBPB from which
the return value is determined.

Output

The value of the field in the operand is moved into the variable key.

Syntax

OOOOOVVVVV

OOOOO OUTWP Name of operation

VVVVV
ABART Employee subgroup grouping-
Personnel calculation rule
PAYSB Payroll area***)
EMPLR Employment contract
ATIND Additional Time Management I0007*)
PARTT Part-time from I0007*)
WWEEK Working week from I0007*)
PLTSC Personnel subarea****)
PLANT Personnel area****)
COMPY Company code****)
COSTC Cost center
The variable key has 8 characters, the
cost center has 10 characters. Use the
operations VALEN
and Operation VAOFF
to select the section
 to be transferred from the cost center
and placed in the variable key
COSTD Cost distribution indicator
An 'X' is placed in the variable
key if IT 0027 (cost distribution)
exists for the EE, otherwise an '*'
is entered.
CTYMO Country modifier for wage types
PERSG Employee group
PERSB Employee subgroup
SHIFT Shift indicator
JOBNO Job
TRFAR Pay scale type
TRFGB Pay scale area
TRFGR Pay scale group
TRFST Pay scale level
ITRFA Internal pay scale type from T510A
If this field is not maintained,
'**' is entered in the variable key
instead.
TIMER Time recording
INWID Participation in Time WTs from T503**)
ORGEH Organizational unit

*) This information is not contained in the WPBP, but is read from the
Planned Working Time infotype (0007) (internal table P0007). The
restrictions mentioned in the section Use apply here.

**) This information is queried from the specified Customizing table on

the basis of a value from table WPBP. The restrictions mentioned in the
section Use do not apply here.

***) This information is not in the WPBP. It depends on the country

version used in Report RPCALCx0.

****) The system always reads the personnel subarea, the personnel area
and the cost center from table WPBP in the form of a four digit string.
If the name of the personnel subarea, the personnel area or the cost
center is less than four digits long, the system replaces the blank
spaces with an asterix (*). However, in the personnel calculation rule
the personnel subarea, the personnel area and the cost center are
entered without an *. Therefore, in such instances the operation does
not find the correct branch of the personnel calculation rule and uses
the **** branch instead.
If, in your system, you use personnel subareas, personnel areas or cost
centers that have less than four digits, then you must change the
corresponding branches in the personnel calculation rule. Replace the
blank spaces with an *.

Example

1. You want to execute different processing depending on the company

code

2. You want to perform special calculations for certain shifts

Method
 OOOOOVVVVV
1. OUTWPCOMPY
2. OUTWPSHIFT

Note

If you want to use operation OUTWP with parameterization COSTC, you must
take the following points into consideration:

o The cost center is put in table WPBP in field KOSTL with 10 digits.
A maximum of 8 digits can be placed in the variable key. However,
the cost center is read by parameterization COSTC with a leading
"0". This can generally be done away with.

o As of Release 3.0, it is possible to specify the length and the

offset with which the calculation rule should be read. This is done
using operations VALEN and VAOFF.

Example: Depending on the last four digits of the cost center you
want to assign a certain value to modifier 1. The corresponding
calculation rule is as follows:

VarKey. NL T Operation Operation Operation Operation Operation

----------------+--------+--------+--------+--------+-------
D VAOFF 6 VALEN 4 OUTWPCOSTC
**** MODIF 1=1
1000 MODIF 1=2

Such a calculation rule will lead to the following error message:

Offset- or Length exceeds the field length. You can ignore this
error message. If you use the calculation rule, you will obtain the
desired result.