ASAP Implementation Methodology

FUNCTIONAL SPECIFICATION

SCENARIO (BUSINESS AREA): PERSONNEL ADMINISTRATION

BUSINESS PROCESS: PERSONNEL ADMINISTRATION

PROJECT IDENTIFICATION

Project Name
FUSION

Customer Name
ITC Ltd

SAP Project Manager Customer Project Manager

Umesh Poojari Vasanth Kumar K

Author
Sreekanth / Kishore
Version Status Date (DD-MM-YYYY)
1.0 Completed 25-04-2016

REVISION HISTORY

Version Date Description

1.0 24-04-2016 Additional Fields in Infotype 0001 – Organizational Assignment
1.0 25-04-2016 Initial Review and modifications - Vijay
1.0 26-04-2016 Initial Review and modifications - Prateek

REVIEW AND APPROVAL

Copyright © 2015 SAP SE. All rights reserved 1 of 11

ASAP Implementation Methodology

Umesh Poojari Date (DD-MM-YYYY)

SAP Project Manager

Vasanth Kumar K Date (DD-MM-YYYY)

Customer Project Manager

Pratheek Prakash Date (DD-MM-YYYY)

ABD Core Team

Name Vijaya Kumar K Date (DD-MM-YYYY)

SAP HCM Lead

Name Sreekanth / Kishore Date (DD-MM-YYYY)

SAP HCM Team Member

Copyright © 2010 SAP AG. All rights reserved 2 of 11

ASAP Implementation Methodology

TABLE OF CONTENT

1. PURPOSE OF THIS DOCUMENT........................................................................................................4

2. GENERAL OBJECT OVERVIEW.........................................................................................................5
2.1 Process Requirements Reference.................................................................................................6
2.2 Generic Enhancement Descriptions..............................................................................................6
3. OBJECT SPECIFIC DESIGN............................................................................................................... 8
3.1 Enhancements............................................................................................................................... 8
4. TEST CONDITIONS........................................................................................................................... 10
5. REVIEW CHECKLIST........................................................................................................................ 10

Copyright © 2010 SAP AG. All rights reserved 3 of 11

ASAP Implementation Methodology

1. Purpose of this document

To incorporate Additional Fields in IT0001 – Organizational Assignment as per the need of the customer to track
additional details of the employee in HR Master data.

Additional Fields such as

1. Designation
2. Level of Responsibility
3. Job Level.
4. Reporting Manager
5. Branch & Cluster
6. Incumbency Status
7. Department

2. General Object Overview

Object Overview

Development Server IP 10.10.65.37

Server Name
Address
Object ID (Ex: E_HR1_004
200 / 220
Client R_HR1_001,
C_HR1_001)
608 HCM
SAP Release SAP Module

Object Title Additional Fields in IT0001 – Organizational Assignment

Additional Fields will be used to capture information about Employee
Object Description Designation, Level of Responsibility, Job Level, Incumbency Status, Branch,
Cluster, Department
( √) ECC
( ) CRM Required
( ) BI/BO Development
Systems Impacted DD-MM-YYYY
( ) BPC Completion
( ) Others Date
______________
Complexity of Medium Medium
Priority
Object
SAP Transaction Transaction Code: SE12 / PM01, Table: PA0001 and Infotype – 0001
Name (Organizational Assignment)

Similar SAP NA Similar SAP NA

Transaction Program
FS CONTROL

Copyright © 2010 SAP AG. All rights reserved 4 of 11

ASAP Implementation Methodology

Functional Sreekanth / Kishore Business Prateek Prakash

Consultant – Author Process Owner
23-04-2016
Planned Date of FS 23-04-2016 Actual Date of
Completion FS Completion
25-04-2016
FS Reviewed By Vijaya Kumar K FS Review Date
(SAP Lead)
26-04-2016
FS Reviewed By
Prateek Prakash
(Core Team & SAP FS Review Date
SS)
DD-MM-YYYY
Last Name, First Name FS Approval
FS Approved By
Date

2.1 Process Requirements Reference

Process Reference
Requirement ID
Requirement
Description
Gap to be addressed
Alternative SAP
Standard Solution
Personnel Administration
To Capture information about Designation, Responsibility Level, Reporting
Manager, Job Level, Incumbency Status, Branch, Cluster, Department
Custom Fields needs to be developed in Infotype 0001
Not Available

2.2 Generic Enhancement Descriptions

Justification

 Not part of standard Infotypes –

 Custom Fields to be developed to capture the Designation, Responsibility Level, Reporting
Manager, Job Level, Incumbency Status, Branch, Cluster, Department in Infotype 0001 –
Organizational Assignment.

FUNCTIONAL DESCRIPTION / DESIGN

Additional fields in IT0001 incorporated.

TRANSACTION VOLUME

 At the time of Personnel Actions like Onboarding / Joining; Confirmation, Transfers and
Separation etc., in the system and the relevant data would get captured for the employee
 Approximately 1000 transactions in a year

Copyright © 2010 SAP AG. All rights reserved 5 of 11

ASAP Implementation Methodology

FREQUENCY & TIMING

As and when required.

DEPENDENCIES
No Dependencies

AUTHORIZATION REQUIREMENTS

Authorisation based on HCM PA Authorisation Roles.

Authorisation Object: P_ORGIN
Field: INFTY. Infotype. IT0001

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING

REPORT, ETC)

 Requirement Document in BBP. Please refer to WRICEF E_HR1_004- Additional Fields in Infotype 0001
 Designation, Responsibility Level , Job Level, Incumbency Status, Branch, Cluster, Department

Copyright © 2010 SAP AG. All rights reserved 6 of 11

ASAP Implementation Methodology

3. Object Specific Design

3.1 Enhancements

Enhancements

WRICEF-ID Description Data Functional Alternative Reason Type (BAPI, Enhancement

Object Gap SAP User Exit, Name or BADI or
(Sales Standard etc.) Exit Name
Order)
E_HR1_004 Additional Infotype Fields are not Not Required Infotype Additional Fields
Fields in existed in available Fields are Screen in IT0001 –
Infotype 0001 Standard not part of Enhancemen Organizational
Designation, Infotype Standard t Assignment
Level of infotype
Responsibility
and Job Level

Functional Design / Flow, Validation and Variants

Business Workflow
Master data Capture during Business Process
Logic
Design for the Fields as –Below:
 Consideration
Designation Technical
 Responsibility Level
1. Designation – Text field
 Job Level
To incorporate Custom / Additional Fields in IT0001 for capturing information related to the employee such
 Incumbency
“Designation, StatusLevel and Job Level”.
Responsibility
2. Responsibility
Reporting Manager Level - Drop down list with Search Help
  Branch & Cluster
Additional Fields
 The table should
Incumbency be maintainable for the business users to add further values in the system
Status
1. Designation
 Department
2. Responsibility Level
3. Job Level Level of
Level of Responsibility Text Cadre Equivalent
Responsibility
Design Considerations
4. Incumbency Code
- Functional
Status
1. To5. Reporting
incorporate 02Custom
Char
Manager 40 Char
/ Additional Fields - text for capturing information
in IT0001 02 Char related to the
6. Branch
employee such “Designation, Responsibility Level and Job Level”.
7. Cluster Level - Drop down values provided for the field. (with F4 Help)
2. Responsibility
8. Department
3. Designation - Text field
4. Job level -
Following are the sample To betable
arrived using
values - business logic as explained blow.
Infotype 0001 – Organizational
5. Incumbency Status – To be Assignment
arrived using business logic as explained below
Additional fieldsManager
6. Reporting include PA0001 Tableas
to be arrived in CI_INCLUDE
per OM configuration
7. Branch – To be pulled from
Level of(Organizational Assignment)the custom table basedCadre
on the PA
Equivalent
Table8. – PA0001
Cluster – To be
Responsibility Code pulled from the custom table
Level of Responsibility Textbased on the PA
Field9.Name
Department – To be Data TypefromMax
pulled OMCharacters
based on theField Characteristics
attribute DEPT
L1
Designation CHAR
Level 1 60 L1
Text Field
L2 Level
Note – Screen
Responsibility need
Code CHARLevel
to be displayed 2 2
(Responsibility L2 down
Level, Job Level,
Drop Incumbency Status,help
list with search Branch & Cluster) only for the
following EGs -
L3 Level Text
Responsibility Level 3 40
CHAR L3
Dropdown
 Management, R&D Specialist, ABD Operations Specialist, Officer,listOffice
with search help ABD Non Management,
Associate,
 L4Responsibility
Incumbency Status JobLevel
Level, CHARLevel,4 Incumbency
10 Status areToL4berequired
not for other
derived based EGs.
on Job Designation
Level is required
and Responsibility Levelfor
all the EGs.
Job Level NUM 8 Logic need to be pulled from OM
Dropdown from custom table with search help based on the
Branch CHAR 4
Copyright © 2010 SAP AG. All rights reserved PA.7 Both
of 11code and text need to be displayed in the screen
Dropdown from custom table with search help based on the
Cluster CHAR 4
PA. Both code and text need to be displayed in the screen

To be pulled from OM. Both code and text need to be

Department CHAR 8
displayed in the screen
ASAP Implementation Methodology

L5 Level 5 L5
L6 Level 6 L6
L7 Level 7 L7
L8 Level 8 L8
R1 Chief Scientist L2
R2 Senior Principal Scientist L3
R3 Principal Scientist L3
R4 Senior Lead Scientist L4
R5 Lead Scientist L4
R6 Research Scientist L5
R7 Associate Scientist L5
R8 Assistant Scientist L6
R9 Research Associate L8
OS Operations Specialist OS
OA Office Associate OA

Note – Only the Responsibility Level Text needs to be displayed in the screen dropdown.

3. Job Level:

Default Job Level automatically in IT0001 and incorporate the logic in Module Pool (MP000100)
Logic for getting job Level
First get the Personnel Number PA0001-PERNR and Position Number from the table PA0001-PLANS

Enter Object Type in HRP1000-OTYPE = S and HPR1000-OBJID from the PA0001-PLANS and select
the relationship for A/B Z08 in the Table HRP1001-RSIGN and HRP1001-RELAT with the HRP1001-
SCLAS =ZL and get the value from the Table HRP1001 – SOBID based on the selection period of the
record in the table PA0001.

Note – Job level should not be editable

4. Incumbency Status:

If the Job Level = Responsibility Level then the Incumbency Status will be “At Par”

If the Job Level < Responsibility Level then the Incumbency Status will be “Step Up”

If the Job Level > Responsibility Level then the Incumbency Status will be “Step Down”

5. Reporting Manager: Default Reporting Manager automatically in IT0001 and incorporate the logic in
Module Pool (MP000100)

Logic for getting Reporting Manager

Copyright © 2010 SAP AG. All rights reserved 8 of 11

ASAP Implementation Methodology

Get the Personnel Number PA0001-PERNR and Position Number from the table PA0001-PLANS.

Enter Object Type in HRP1000-OTYPE = S and HRP1000-OBJID from table PA0001-PLANS and select
the relationship for A/B 0002 in the table HRP1001-RSIGN and HRP1001-RELAT with the HRP1001-
SCLAS=S and get the value from the table HRP1001-SOBID based on the selection period of the record
in the table PA0001

6. Branch & Cluster

Custom Table: ZHR_BRANCH_CLUSTER_MASTER (To be maintained through SM30)

PA Code PA Text Branch Code Branch Text Cluster Code Cluster Text

7. Department

To be pulled from OM structure based on the OM Attribute DEPT (check attribute in table HRP1222-ATTRIB). If
the employee’s OU is tagged as DEPT then the same will be displayed as the department. In case it is not
tagged then search for the parent OU (A002 relationship) till the OU is found which has the attribute DEPT.

Copyright © 2010 SAP AG. All rights reserved 9 of 11

ASAP Implementation Methodology

Copyright © 2010 SAP AG. All rights reserved 10 of 11

ASAP Implementation Methodology

4. Test Conditions
BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)

Scenario # Input Selection Criteria Expected Result

Onboarding /  Transaction code: Infotype 0001 will be called up during the process
Joining Actions PA40 and custom fields should get populated.
 Action Type:
Onboarding / Joining
 Start Date:

Maintaining HR  Transaction code: Should be able to change / edit / maintain the

Master Data PA30 relevant data in custom fields.
 Personnel Number
 Start Date:
 Infotype: 0001

5. Review Checklist

Copyright © 2010 SAP AG. All rights reserved 11 of 11