Ooredoo

<Manage Human Resources>

<Functional Design Infotype Enhancement>

Prepared by
Date

Wellina
Leonardy
17 Dec 2013

Reviewed by

Approved by

Date

Date

Infotype Enhancement
Functional Design

File Name: 271301759

Status: DRAFT

Page 1 of 15
Date Printed: 24/05/2015

Ooredoo
<Manage Human Resources>
<Functional Design Infotype Enhancement>

Sign-Off
Name

Date (DD-MM-YYYY)

Signature

Revision History
Version
0.1
1.0

File Name: 271301759

Status: DRAFT

Date
17/12/2013
06/02/2014

Author
Wellina Leonardy
Wellina Leonardy

Status
Initial Draft
Final

Description

Page 3 of 15
Date Printed: 24/05/2015

Ooredoo
<Manage Human Resources>
<Functional Design Infotype Enhancement>

RICEF Work Unit #: (Required)

[<Fun_Module>-E-###]

Enhancement Title: Infotype Enhancement

Module & Sub module: HCM (Human Capital Management) PA (Personnel Admin)
1a. General Requirements
Functional Description of Enhancement:
This development is required for the creation of new custom Infotypes to accommodate other enhancements for Tax
Data and Social Security Data. This is due to the fact that SAP Standard does not provide statutory Infotypes for
Myanmar.
These data will be used for payroll calculation.
No.
1
2

Enhancement
Tax Data
Social Security Data

Infotype
9401
9402

Description
This Infotype is used to store required information
related to Tax Data
This Infotype is used to store required information
related to Social Security Data

Summary Level: Drill Down

Output: Screen

Frequency: Ad-Hoc

Processing Type: (Required)

Owner: IT

Audience: IT

Business Driver:
Enhancements in SAP HCM
Business Requirements for Additional Master Data
Priority: High
Complexity: Medium
Processed By: N/A
Design Assumptions: N/A

File Name: 271301759

Status: DRAFT

Page 5 of 15
Date Printed: 24/05/2015

Ooredoo
<Manage Human Resources>
<Functional Design Infotype Enhancement>

1b. Design
Process Flow Diagram:

Figure 1: New Custom Infotypes in SAP

Processing Details (Business Rules/Selection Criteria and Validation):

New Infotypes will be introduced to accommodate enhancement activities performed in Human Capital Management.
No.
1
2

Enhancement
Tax Data
Social Security Data

Infotype
9401
9402

Description
This Infotype is used to store required information
related to Tax Data
This Infotype is used to store required information
related to Social Security Data

Infotype 9401 (Tax Data)

Infotype 9401 is used to manage employee tax data. HR Officer will be able to manage tax data through PA20 to
display or PA30 to entry/maintain tax data.

File Name: 271301759

Status: DRAFT

Page 7 of 15
Date Printed: 24/05/2015

Ooredoo
<Manage Human Resources>
<Functional Design Infotype Enhancement>

Below are data structures used for Infotype 9401 (Tax Data):
No.

Field Name

TAX_ID

SPOUSE_BE
N
NO_DEPEND

Data
Element

Data
Type

ZDE_TAX_I
D
ZDE_SPOU
SE_BEN
ZDE_NO_D
EPEND

Length

Decimal

Short Description

CHAR

15

Personal Tax ID

CHAR

CHAR

Flag for Spouse

Benefit
No. of Dependents

Remarks
Mandatory field

Fixed dropdown
value:
01 1
02 2
03 3
04 4
05 5
06 Use Family
Info

Infotype 9402 (Social Security Data)

Infotype 9402 is used to manage employee social security data. HR Officer will be able to manage social security
data through PA20 to display or PA30 to entry/maintain social security data.

File Name: 271301759

Status: DRAFT

Page 9 of 15
Date Printed: 24/05/2015

Ooredoo
<Manage Human Resources>
<Functional Design Infotype Enhancement>

Below are data structures used for Infotype 9402 (Social Security Data):
No.

Field Name

INSTY

CLEVL

ACC_ID

4
5

WAERS
PCTER

PCTEE

AMTER

AMTEE

RULER

10

RULEE

11

NOTE

Data
Element

Data
Type

ZDE_INST
Y
ZDE_LEVE
L
ZDE_ACC
_ID
WAERS
ZDE_PCT
ER
ZDE_PCT
EE
ZDE_AMT
ER
ZDE_AMT
EE
ZDE_RUL
ER
ZDE_RUL
EE
ZDE_NOT
E

Length

Decimal

Short Description

Remarks

CHAR

Social Security Type

Mandatory field

CHAR

Mandatory field

CHAR

15

Insurance Scheme
Contribution Level
Account ID

CUKY
DEC

5
7

0
4

DEC

CURR

15

CURR

15

CHAR

CHAR

CHAR

255

Currency Key
Employer Percentage
Contribution
Employee Percentage
Contribution
Employer Amount
Contribution
Employee Amount
Contribution
Employer Calculation
Rule
Employee Calculation
Rule
Note for Unauthorized
Unpaid Leave

Design Constraints:
Detailed Additional Logic in Infotype 9402 (Social Security Data):
In Calculation Rule, there are 3 fixed values:
01 = Percentage
02 = Amount
03 = Percentage & Amount
For default value in Employer and Employee Calculation Rule is 01 (Percentage). The logic of the program checks
calculation rule and Percentage & Amount field will be applied as below:
Calculation Rule

Percentage

Amount

01 (default)

Enabled

Disabled (grey out)

02
03

Disabled (grey out)

Enabled

Enabled
Enabled

In addition, user exit ZXPADU02 will be implemented in order to read value in table Z* (Social Security custom table
in document AP350 FD E HCM EH013 - Payroll Calculation for Myanmar). The reference key is Begin Date
(BEGDA), End Date (ENDDA), Insurance Scheme (INSTY), and Insurance Level (CLEVL) and system will generate
data as below:

If Calculation Rule = 01, get PCTER (Employer Percentage Contribution) and PCTEE (Employee
Percentage Contribution) value from table Z* and insert into field PCTER and PCTEE in Infotype 9402
(Social Security Data).

File Name: 271301759

Status: DRAFT

Page 11 of 15
Date Printed: 24/05/2015

Ooredoo
<Manage Human Resources>
<Functional Design Infotype Enhancement>

If Calculation Rule = 02, get AMTER (Employer Amount Contribution) and AMTEE (Employee Amount
Contribution) value from table Z* and insert into field AMTER and AMTEE in Infotype 9402 (Social Security
Data).

If Calculation Rule = 03, get PCTER (Employer Percentage Contribution), PCTEE (Employee Percentage
Contribution), AMTER (Employer Amount Contribution), and AMTEE (Employee Amount Contribution) value
from table Z* and insert into field PCTER, PCTEE, AMTER, and AMTEE in Infotype 9402 (Social Security
Data).

Authorization Check
[Provide the authorization check requirements, such as the field to check, authorization objects, field value, etc. This authorization check should
be able to control that only user with the correct authorization can execute/view the data in this enhancement. ]

2a. Error Handling

Potential Errors:
[Describe instances where errors may occur. This should include the extent to which the organization is responsible for error monitoring in
correction versus users responsibilities. Full details on how operations will be notified are not required; however, state the business expectations
for level of service provided.]

No

Possible Errors

File Name: 271301759

Status: DRAFT

Notification Procedures
<Report>
<eMail>
<View in Application>
<View in log file>
<Exception Report>

Page 13 of 15
Date Printed: 24/05/2015

Ooredoo
<Manage Human Resources>
<Functional Design Infotype Enhancement>

3a. Existing/Sample Enhancement or Related Transaction

Existing SAP Program Name:
[Enter the name of the related SAP program]

Existing SAP Menu/Transaction:

[Enter the related SAP Menu path and/or transaction]

Legacy Form Name:

[Indicate document/sample cross reference or link design object into form.]

Legacy Form Number:

[Indicate legacy number on document/sample cross reference.]

3b. Related Documents

No.

Related Documents

Description

Attachment

1.

AP350 FD E HCM EH013

Payroll Calculation for Myanmar

Custom program

2.
3c. Configuration Requirements:
[What configuration is required to support this process?
transactional data exist in the development system? ]

Does this process require master data to be loaded? Do all configuration, master, and

3d. Component Testing Requirements

[List at a high level any requirements that exist to fully test this program.. Please enter functional conditions that are required for testing. Please
include normal conditions and error handling conditions. This should include the following categories of test conditions:
(1) Normal Processing: To test and display the form as the normal situation.
(2) Exception Processing: To test and display the exception process (e.g.: zero amounts are not display, do not show deleted material, etc).
(3) Error Processing: To test and display the error message (e.g.: invalid company code, invalid sales order number, etc).]

Test condition
Normal Processing
Error Processing: No data

Expected results
Data created in SAP
Data is not created in SAP with error
message Fill in all required entry fields
Custom Infotype screen is not displayed with
error message No Authorization

Error Processing: No authorization

Test Data: (Required)

[Provide the test data that to perform the above test conditions]

3e. Performance Watch

[Consider the following items:
1. Online & time critical reports.
2. Transaction volume.]

APPENDIX A : Screen shots of process

[Set of screen shots to clarify steps of process. For example if the form is a standard modification, then provide the screen shots of transaction]

File Name: 271301759

Status: DRAFT

Page 15 of 15
Date Printed: 24/05/2015