You are on page 1of 6

Qatar: Wage Protection System User Manual

The WPS file format with an example is attached below. The file also specifies
from which system (HCM or FIN) the data will be filled.

WPS File Format.xlsx

1 Customizing
a. Sponsor ID: View V_T7QA17H has to be maintained. In IT0002, sponsor
ID is made a mandatory field now. All the employees working for a
Qatari company should have a sponsor associated with them. The
sponsor company registration number maintained in this view will be
reported as the Employer EID in the WPS file.

b. Payer EID: The Establishment ID of the salary paying company code


should be maintained in OBY6 transaction. The parameter Payer
Establishment ID should be maintained.
c. Payer QID: The QID of the salary paying company code should be
maintained in OBY6 transaction. The parameters Payer Qatari ID
should be maintained.
For example:

Click on Additional Data button to maintain the parameters.

d. Evaluation Class: The evaluation class 03 specification 01 can be


maintained for the wage types which needs to be cumulated to form
basic pay in IT0008 for an employee.
For Example:

e. Maintain the Feature QAWPS. Refer to the Manual Instruction


document for feature documentation.

2 Procedure
Once the customizing data is all maintained, for a given period
1. Execute Payroll in live mode.
2. Execute PRE-DME report HQACDTA0 in live mode with the option WPS
File Fields checked in the selection screen.

The PRE-DME report will update the required WPS field values in
REGUH and REGUP tables which the finance system will read to
generate the WPS file.

3 WPS File Fields


The Pre-DME report updates HCM specific WPS values to fields in REGUH &
REGUP tables. Refer to the note 2232790 for details about FIN
specific fields. The HCM specific WPS fields and the data source from
where these fields are filled and mapping to REGUH & REGUP tables are
below,

Header
a. Employer EID: This is the registration number of the Sponsor who
sponsors employee to work in Qatar. The Sponsor details are
maintained in the view V_T7QA17H. The sponsor of an employee is
maintained in IT0002.
b. Payer EID: The Establishment ID of the salary paying company code
should be maintained in OBY6 transaction. A new parameter PAYEID Payer Establishment ID is delivered by SAP which has to be used by
the customers to maintain PAYER EID.
c. Payer QID: The QID of the salary paying company code should be
maintained in OBY6 transaction. A new parameter PAYQID - Payer
Qatari ID is delivered by SAP which has to be used by the customers
to maintain PAYER QID.
Note: Either Payer EID or Payer QID should be filled. For a company
code if both values are filled then PAYERQID will picked for reporting.
d. Salary Year and Month: This will be derived from Begin date of the
period for which PRE-DME is executed. For Example PRE-DME is
executed for payroll area QA for period 02 2015. The begin date is
defaulted to 01.02.2015. The salary year and month field will be
022015.

Details Salary Records


a. Employee QID: The value is obtained from IT0185 subtype 01 for all
the employees working in Qatar. For expatriates if QID is not available
then WORK VISA is a must. The latest record in IT0185 for the given
period is read.
b. Employee Visa ID: The value is obtained from IT0185 subtype 4 for
non-Qatari national. This value should exist if Qatari ID is not
maintained for the employee. The latest record in IT0185 for the given
period is read.
Note: Either Employee QID or Employee Visa ID should be filled in the
file. If both are available then Employee QID is reported in the file.
c. Employee Name: The data is already available in REGUH table hence
need not be derived.
d. Employee Account: The data is already available in REGUH table
hence need not be derived.

e. Salary Frequency: Derived from Payroll period parameter of the


payroll area for which the PRE-DME is executed.

f. Number of Working days: The value will be derived as:


Number of calendar days in WPBP table Absences (Calendar days
from Payroll cluster ABC).
g. Basic Salary: The basic pay is the agreed amount by the employer
which is paid to employees. This should not be confused with the basic
salary in payroll result as that would be the prorated data. The basic
pay in this file will be the cumulated value of the certain wage types
maintained in IT0008 of an employee.
Since customers can choose any wage type in IT0008 to form basic pay
for an employee, SAP is delivering a new evaluation class 03 with
specification 01 for Qatar solution. The evaluation class can be
maintained for the wage types which needs to be cumulated to form
basic pay in IT0008.
h. Extra hours: This value is the overtime an employee works in the
company for a given pay period. The value is derived in /852 wage
type. To derive the value customers have to configure overtime wages
in their system. For e.g., the view V_T510S can be maintained for the
overtime wage types the customers use to pay the employees.
i. Extra income: Derived as Gross (cumulation of /101, /551, /552)
Basic Salary (Basic salary is what is present in RT of payroll result for
the wage types maintained with Evaluation Class 03 Specification 01)
j. Deductions: Derived as Gross Net income. Cumulation of /101, /551
& /552 - /559.
k. Payment Type: This is an optional field in the file and customer can
choose to fill it using BADI.
BADI Name: PADQA_WPS_FIELDS
Method Name: GET_WPS_FIELDS
The changing parameter PAY_TYPE should be used for setting the field
value. This field is only char 35 long.
l. Notes / Comments: This is an optional field in the file and customer
can choose to fill it using BADI.
BADI Name: PADQA_WPS_FIELDS
Method Name: GET_WPS_FIELDS
The changing parameter IV_COMMENT should be used for setting the
field value. This field is only Char 130 long.

The Field mapping for WPS file fields with the REGUH &
REGUP tables

WPS Field Name


Employer EID
Payer EID
Payer QID
Salary Year and Month
Employee QID
Employee Visa ID
Employee Name
Employee Account
Salary Frequency
Number of Working days
Net Salary
Basic Salary
Extra hours
Extra income
Deductions
Payment Type
Notes / Comments

PRE-DME
Table Field
Mapping
REGUH-ZNME3
REGUH-ZNME4
REGUH-ZORT2
REGUH-ZPST2
REGUH-ZTLFX
REGUH-ZTELX
REGUH-ZNME1 &
ZNME2
REGUH-ZIBAN
REGUH-ZPFAC
REGUP-KIDNO
REGUH-RWBTR
REGUP-QSSHB
REGUP-ESRRE
REGUP-WSKTO
REGUP-QBSHB
REGUH-NAME2
REGUH-NAME3 &
NAME4 & REGUHKOINH

You might also like