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

Author
Venkata Sai Kishore L
Version Status Date (DD-MM-YYYY)
1.1 Final 07-06-2016

REVISION HISTORY

Version Date Description

1.0 10-05-2016 Mass Upload of Employee Photos
1.0 14-05-2016 Initial Review - Vijay
1.0 20-05-2016 Initial Review - Prateek
Included comments from SS (Systems Impacted – DMS, Permissible File Types,
1.1 04-06-2016
Additional Test Conditions)

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

ASAP Implementation Methodology

REVIEW AND APPROVAL

Name Date (DD-MM-YYYY)

Key Stakeholder

Name Date (DD-MM-YYYY)

Key Stakeholder

Name Date (DD-MM-YYYY)

Key Stakeholder

Name Date (DD-MM-YYYY)

Key Stakeholder

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

ASAP Implementation Methodology

TABLE OF CONTENT

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

2. GENERAL OBJECT OVERVIEW.........................................................................................................5
2.1 Process Requirements Reference.................................................................................................5
2.2 Generic Conversion Descriptions..................................................................................................6
3. OBJECT SPECIFIC DESIGN............................................................................................................... 8
3.1 Data Conversion / Historical Data..................................................................................................8
4. TEST CONDITIONS........................................................................................................................... 10

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

ASAP Implementation Methodology

1. Purpose of this document

Mass Upload of Employee Photos in the system

2. General Object Overview

Object Overview

Development Server IP 10.10.65.37

Server Name
Address

200 / 220 Object ID (Ex:

Client R_HR1_001, C_HR1_029
C_HR1_001)

608 HCM
SAP Release SAP Module

Object Title Mass Upload of Employee Photos in the system

Object Description Mass Upload of Employee Photos in the system

( X ) ECC
( ) CRM Required
Systems Impacted ( ) BI/BO Development DD-MM-YYYY
( ) BPC Completion Date
( X ) Others - DMS
Low Medium
Complexity of Object Priority

SAP Transaction NA
Name
OAAD (Process to Upload
Similar SAP Similar SAP NA
employee photos)
Transaction Program

FS CONTROL

Functional Consultant Venkata Sai Kishore L Business Process Last Name, First Name
– Author Owner

Planned Date of FS 10-05-2016 Actual Date of FS 10-05-2016

Completion Completion
Vijaya Kumar K 14-05-2016
FS Reviewed By FS Review Date

Prateek Prakash 20-05-2016

FS Approved By FS Approval Date

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

ASAP Implementation Methodology

2.1 Process Requirements Reference

Process Reference
Requirement ID C_HR1_029
Requirement
Description Mass upload of Employee Photos in the system
Gap to be addressed Addressed through Custom Development
Alternative SAP NA
Standard Solution

2.2 Generic Conversion Descriptions

Justification
 LSMW will not fit for the requirement and hence BDC is developed.

FUNCTIONAL DESCRIPTION / DESIGN

 To upload multiple employee photos in the system

TRANSACTION VOLUME
 Approximately 5000 records

FREQUENCY & TIMING

 Whenever an employee is hired / transferred into the division

DEPENDENCIES
 PA Master data should be available in the system

AUTHORIZATION REQUIREMENTS
 Controlled through General Authorizations defined in the system. T code Authorization control.

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

REPORT, ETC)

BBP Requirement Document Ref to WRICEF - C_HR1_029

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

ASAP Implementation Methodology

3. Object Specific Design

3.1 Data Conversion / Historical Data

Conversions
WWRICE Conversion Source Conversion Conversion # of Objects to be
F-ID Object Activities Method (manual converted
(e.g. / automated)
cleansing)
C_HR1_0 Photo NA 1
29 Manual Module Pool
Upload

1MAPPING SAP FIELDS TO SOURCE / TARGET

Please refer to the word document how to upload photo in the system is as follows

Files Allowed - Employee’s photograph will be stored as a .jpeg / .jpg file

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

ASAP Implementation Methodology

RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

Reporting

NA

Approach

Employees’ photographs will be kept in a folder with the file name as “Employee Number.jpeg
/ Employee Number.jpg”. The program should be able to upload the photograph against the
respective Employee Number either individually or in a bulk upload.

Transaction Code = OAAD; Method = Module Pool / BDC

Metrics
NA

Error Handling
1. Authorization Issue. Unable to execute the Transaction code ( Obtain Authorization for the
T_code OAAD and the BDC program )
2. Recheck the following values if it is giving an upload error.
 Menu Archived Link: Store and Assign
 Business object = PREL
 Document type = HRICOLFOTO
 Personnel number = < Employees Pers. No >
 Check the photograph format
3. If the Employee Number does not exist then the system will display an error message

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

ASAP Implementation Methodology

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

Scenario # Input Selection Criteria Expected Result

Process to Based on the Input Selection Photos loaded in the system against to the
Upload Screen personnel numbers.
Multiple
Photos in  Used BDC T code
the system  Employee Number
 Photo in .Jpg format

Photograph Based on the Input Selection Employee should not be able to change his /
retrieval / Screen her photograph.
update and Only HR Administrator will be able to change
version  Used BDC T code the photograph.
control  Employee Number Once the photograph is changed then the old
 Photo in .Jpg format photograph will be overwritten. Only the latest
photograph will be maintained in ECC and
DMS. Only the latest photograph will be visible
to the employee in portal. No version control is
required.
Upload a Based on the Input Selection Error to be displayed to check the file format.
photograph Screen
in a file
format  Used BDC T code
different  Employee Number
form .jpg / .j  Photo in .Jpg format
peg

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