Enhanced Conversion Program for Creation and Maintenance of HR Mini Master

Title: TS_CON_D-060-001_Document Load ProgramDocument Number: GBP-SAP-FS-C2E-C1-3000Revision: 1.0

1 of 27

Title: CON_D-030-003_Enhanced Conversion Program for creation and

maintenance of HR Mini Master

Document Number: GBP-SAP-FS-C2E-C10-3209

Revision: A

Approval Signatures

List all approvers in the table below

Printed Name Signature Date Role

Helen Beran Technical Lead

Chris TylerDevelopment Lead

Business Process Owner


2 of 27

Table of Contents

1 General Attributes...............................................................................................................................3

1.1 Object information......................................................................................................................3

2 Definitions...........................................................................................................................................5

3 References, Attachments and Documentation....................................................................................6

3.1 Related RICEFW Objects (SAP / Legacy).......................................................................................6

4 Technical Details..................................................................................................................................6

4.1 General Conversion Description..................................................................................................6

4.2 Technical Logic Flow....................................................................................................................6

4.3 Program Structure and Processing..............................................................................................9

4.4 Selection Screen........................................................................................................................10

...............................................................................................................................................................11

4.5 Data Mapping............................................................................................................................11

4.6 Restart Capability.......................................................................................................................11

4.7 Verification and Reconciliation..................................................................................................12

4.8 Technical Assumptions and Dependencies................................................................................12

5 Error Handling...................................................................................................................................13

5.1 Posting Error Requirements.......................................................................................................13

5.2 Acceptance/Failure Criteria.......................................................................................................13

5.3 Error Notification Requirements................................................................................................13

5.4 Email Reports Requirements.....................................................................................................13

6 Security..............................................................................................................................................14

6.1 Security Considerations.............................................................................................................14

6.2 Control Considerations..............................................................................................................14

7 Technical and Unit Test plan..............................................................................................................15

8 Appendix / Object Templates............................................................................................................16

9 Revision History.................................................................................................................................25


3 of 27

1 General Attributes

1.1 Object information

Object Information

Program Name(s)

ZC2EC_HRMASTER

Include Files ZC2EC_HRMASTER_TOP

ZC2EC_HRMASTER_SEL

ZC2EC_HRMASTER_F01

Area Menu N/A

Print Transaction

N/A

Authorization Object Used

N/A

Output Type Text File

Run Mode Foreground Background Both

Frequency

Daily Weekly Monthly Others

Data Volume (Records)

3500

a) Custom Object Attributes

Program Attributes: {Provide relevant program attributes}

Name ZC2EC_HRMASTER

Description Create and Maintain HR Mini Master

Logical Database N/A

Development Package ZC2E

Editor Lock Yes No

Start using variant; Yes No


4 of 27

Fixed Point Arithmetic: Yes No

Transaction Attributes: {Provide relevant attributes based on transaction type}

Name ZHRMINI

Description Create and Maintain HR Mini Master


Type Program and selection screen

Program/Transaction Transaction

Screen Number 1000

Variant N/A

Describe other attributes N/A


Name ZHRMAST01

Description HR Mini Master


Type Parameter Transaction

Program/Transaction SM30 / ZTC2E_HRMM_TRANS

Screen Number 0

Variant N/A

Describe other attributes ZTC2E_HRMM_TRANS Table Maintenance Transaction

Table/Structure Attributes: {Provide one template for each new custom table created for this object}

Name: ZTC2E_HRMM_TRANS

Short Text: HR Mini Master Translation table

Type Transparent Pooled Cluster

Structure APPEND CI Customer include


Delivery Class: C

Table Maintenance: Allowed

Data Class: APPL1 (Transaction data, transparent tables)

Size: 0 (Expected data records 0 to 17,000)

Buffering: Not Allowed

Table Locking: N/A

Authorization Group: &NC&

Tables and Structures Fields: {Provide all fields that are new, changed, or deleted. Highlight the key fields and provide information if the field has been added, changed or

deleted}

Table/Structure: ZTC2E_HRMM_TRANS

Expected Size: N/A


5 of 27

Field Name Data Element Domain Description (Change, Add, Delete, Key, etc.)

MANDT MANDT MANDT Key

ZZWORKDAY_OBJ ZWORKDAY_OBJ CHAR Key

ZZWORKDAY_VAL ZWORKDAY_VAL CHAR Key

ZZSAP_OBJ ZSAP_OBJ CHAR Key

ZZSAP_VAL ZSAP_VAL CHAR

Message Class Attributes: {Provide relevant attributes for the message class}

Name ZC2E

Description Message class for C2E

Development Package

ZC2E

Msg. Number

Message Text Long Text (Y/N)

Definitions

Term Definition

HR Mini Master HR Mini master refers to creating an employee master record in SAP to enable functionalities in areas other than SAP HR (for example, time sheet booking). Out of the many Infotypes used in SAP employee master, the mini master uses only a few (mostly related to Personnel Administration – PA)

Personnel Area A personnel area is a Personnel Administration specific unit and is a subunit of the company code.

In Illumina Personnel Areas will represent company codes.

Personnel Sub Area A personnel subarea represents a subunit of the personnel area. It is at this level that the organizational control of pay scale structures, wage type structures, and work schedules occurs.

In Illumina, personnel subareas will represent locations.

Employee Group Employee groups represent a primary subdivision of personnel. An employee group defines the extent to which its employees place their


6 of 27

labor at the disposal of the enterprise.

Cost Center Organizational unit within a controlling area that represents a clearly delimited location where costs occur. You can make organizational divisions on the basis of functional, settlement-related, activity-related, spatial, and/or responsibility-related standpoints.

Activity Type Activity types classify the activities produced in the cost centers within a controlling area.

Relationships Relationships are the connections that exist between objects in Personnel Management.

Relationships are defined by creating and maintaining relationship Infotype records (Infotype 1001). In the Infotype record, you specify the two objects concerned and the type of relationship between them.

Org Unit An Org Unit is the organizational object (object type key O), which forms the basis of an organizational plan. Organizational units are functional units of an enterprise. Depending on how tasks are distributed in an enterprise, these can be departments, groups or project teams.

Organizational units are different from other enterprise entities, such as company codes, business area and personnel areas. These are used to form administrative or accounting structures, for example in the relevant components.

In Illumina these will be used to represent the Workday Supervisory Orgs.

2 References, Attachments and Documentation

Document Number Document Title

GBP-SAP-FS-C2E-C10-3209

‘Enhanced’ conversion program for creation and maintenance of employee Mini Master


7 of 27

2.1 Related RICEFW Objects (SAP / Legacy)

DOC ID Name Association (Describe how these objects are

related)

Document name (if known)

N/A N/A N/A N/A

3 Technical Details3.1 General Conversion Description

This program will create, update,transfer and terminate the employee mini master in SAP. If the org unit is not present, the program will create new Org unit is SAP. The program will also update employee related information like organizational assignment of employees, personal data, Work schedule, address data, bank data, communication details, timesheeting defaults and some costing related data.

3.2 Technical Logic Flow


8 of 27


9 of 27

3.3 Program Structure and Processing

Read file from physical server or the application server depending on the radio button selected in

selection screen

Get the record number range present in selection screen. If no record number is mentioned then

consider all the records else consider the records mentioned in the screen.

Loop through the records of input file.

Check the update key of the record

For I – initial data for hiring action

Check if the parent org unit is present in the custom translation table

ZTC2E_HRMM_TRANS

If not available, log the error in the error log

If org unit is present, check the relationship with the parent, else create the org unit

using the FM RH_OBJECT_CREATE and relationship using FM

RH_RELATION_MAINTAIN.

If manager position is available, else create the position using FM

RH_OBJECT_CREATE and create the relationship A003 with org using


If manager is the head of the org unit, else create the relationship A012 with org

using RH_RELATION_MAINTAIN.

Create the relationship B440 and B441 between the manager and the org using


If staff position is present, else create the position using FM RH_OBJECT_CREATE

and create the relationship A003 with org using RH_RELATION_MAINTAIN


10 of 27

Update the custom table ZTC2E_HRMM_TRANS with SAP org unit value against the

corresponding Workday Parent Org unit

Create employee in SAP using the personnel number in the file.

Use the time recording (51) for new employee

Pass the org. assignment data(0001), address(0006), Working time(0007),

bank details(0009), communications(0105), CATS(0315) from the input file to

proposed value table and called the function module

HR_MAINTAIN_MASTERDATA with action INS.

For U – Updating date

Validate the data by checking if the data relevant to infotype 0001 and 0315 is

present, else error out the record.

Check if the personnel number in the input file is present in SAP, if not error out the

record, else update the employee details.




HR_MAINTAIN_MASTERDATA with action MOD.

For E – Terminations

Check if the personnel number is in the input file, if not error out the record, else

update the end date as the system date.

For T – Transfers

Check if the personnel number is in the input file, if not error out the record

Check if the org unit is in the custom table, if not error out the record


11 of 27

If available, use the parent org unit, org unit manager’s employee id and cost center

to create the org unit.

If the relationship does not exist, create the relationship




HR_MAINTAIN_MASTERDATA with action MOD.

3.4 Selection Screen

Element Type Field name Default Values

From – To

Validation

(Required / Optional)

CHECKBOX P_SIM X N/A

RADIOBUTTON P_PRES NONE N/A

RADIOBUTTON P_APPL NONE N/A

SELECT_OPTION S_RECID NONE OPTIONAL

PARAMETERS P_IHEAD X N/A

PARAMETRS P_INPUT NONE REQUIRED


12 of 27

3.5 Data Mapping

3.6 Restart Capability

Execute the file.

Check the error log file created.

Fix all the errors and reload the file.

3.7 Verification and Reconciliation

Following details will be provided as a log along with audit/error/archive file.

LOG Display –

Conversion name

Conversion run date

Execution mode

Total count of record processed

Total count of successful records

Total count of error records

Input File

Audit file

Error file

Archive file


13 of 27

3.8 Technical Assumptions and Dependencies

Assumptions / DependenciesSAP test, validation, and production environments would need to be configured before the Document Load Program could be executed.


14 of 27

4 Error Handling

4.1 Posting Error Requirements

An error log will be created and saved during the execution of the program.

4.2 Acceptance/Failure Criteria

All the valid data should be successfully loaded to the system

All the invalid records should be present in the error log.

After fixing the errors the records should be reloaded to system.

4.3 Error Notification Requirements

This program will be executed in the cut over phase. It will be continuously monitored by the user. There is no specific error notification facility required to be developed.

4.4 Email Reports Requirements

Email ID Reporting To PositionEmail Always/

Occasional (Situation)

Reporting Details

N/A N/A N/A N/A N/A


15 of 27

5 Security

5.1 Security Considerations

Transaction code should be assigned with authorization group maintained for all C2E

conversions.

5.2 Control Considerations

Financial/SOX Impact

N/A

Regulatory Impact

N/A

Operational Impact

N/A


16 of 27

6 Technical and Unit Test plan

Sl. Test Scenario Description Expected Result Comment

1. Prepare input file with details of the employees to be hired.Run the program with the input file

All records in the file should be successfully created in SAP as employee mini master

2. Prepare input file with details of the employees to be hired.

Run the program with the input file

The program should create any necessary new org units, create 2 positions for the org unit and maintain details of the org unit in the custom table.

It should then successfully create all records in SAP as employee mini master

3. Prepare input file with list of employees to be transferred.


All the employees in the input file should be transferred.

4. Prepare input file with list of employees to be transferred.


The program should create any necessary new org units, create 2 positions for the org unit and maintain details of the org unit in the custom table.

It should then successfully transfer the relevant employee mini masters.

5 Prepare input file with list of employees to be transferred.


All the employees in the input file should be terminated.ransferred to system.

6 Prepare input file to just update master record and run no personnel actions.Run the program with the input file

Mini master data should be updated as per the input file.

7 Prepare input file to with changes in Infotypes 0001 and 0315 as well as changes in some of the other fields.

Employees should be transferred as well as the other data updated in mini master.


17 of 27



18 of 27

7 Appendix / Object Templates

N/A

Program Attributes: {Provide relevant program attributes}

Name N/A

Description

Logical Database

Development Package

Editor Lock Yes No

Start using variant; Yes No

Fixed Point Arithmetic:

Yes No

Unicode Yes No


Name N/A

Description

Development Package

Type

Program/Transaction

Screen Number

Variant

Describe other attributes

Screen Attributes: {Provide a description of each screen include fields, possible User actions and any Processing that should happen}

Program Name N/A

Description

Development Package

Screen Type

Field Definition:

Screen No.

Field Name

Field Type

Field Text

Format

F4 Help

Validation Error Actions


19 of 27

Screen Logic PBO: {Provide the modules needed for the process before output. Do not provide the coding here, but the steps that need to be performed such as “Set GUI STATUS and TITLE, Initialize Data, etc.}

Screen Logic PAI: {Provide the modules needed for the process after input. Do not provide the coding here, but the steps that need to be performed such as “Verify Input,

Process OK-Code, etc.}

Screen GUI Title: {Provide relevant GUI Title attributes for the screen}

Program Name N/A

Title Code

Description

Screen Status: {Provide relevant attributes for Screen Status}

Program Name N/A

Status Name

Description

Status Type

Menu Bar: {Provide the menu list and sub-menu with the corresponding menu items. If for a menu item you have a sub-menu, then write first the main menu, then sub-menu

and as function code write “SUB”. For the sub-menu write the sub-menu, then the menu item, and then the function code representing the menu item}

Menu/Sub-menu

Sub-menu/Menu Item

Function Code

Description

N/A N/A N/A N/A

Application Toolbar: {Provide the required attributes for application toolbar items. Insert more lines into table when needed}

Item Number

Function Code Description

Function Keys: {Provide the required attributes for application toolbar items}

Function Key

Function Code Description


20 of 27

Function Group Attributes: {Provide relevant attributes for function group}

Name N/A

Description

Development Package

Function Module Attributes: {Provide relevant attributes for the function module}

Name N/A

Function Group

Description

Development Package

Processing Type

Update mode (if applicable)

Import Parameters: {Provide the required attributes for function’s import parameters. Insert more lines into table when needed}

Parameter Name

Typing

Associated Type

Default Value

Optional (Y/N)

Pass Value (Y/N)

Description

Export Parameters: {Provide the required attributes for function’s export parameters. Insert more lines into table when needed}

Parameter Name.

Typing

Associated Type

Pass Value (Y/N)

Description

N/A


21 of 27

Changing Parameters: {Provide the required attributes for function’s changing parameters. Insert more lines into table when needed}

Parameter Name

Typing

Associated Type

Default Value

Optional (Y/N)

Pass Value (Y/N)

Description

Table Parameters: {Provide the required attributes for function’s table parameters. Insert more lines into table when needed}

Parameter Name

Typing

Associated Type

Optional (Y/N)

Description

Exceptions: {Provide the required attributes for function’s exceptions. Insert more lines into table when needed}

OO ABAP Class/Interface Attributes: {Provide relevant attributes for the OO ABAP Class/Interface}

Name N/A

Description

Development Package

Interface Yes No

Instantiation

Class Type

Final Yes No

Only Modeled? Yes No


22 of 27

Super Class

Interface: {Provide the required attributes for class interface definitions. Insert more lines into table when needed}

Interface Abstract (Y/N)

Final (Y/N)

Modeled only (Y/N)

Description

N/A

Friends: {Provide the required attributes for classes’ friends definitions. Insert more lines into table when needed}

Friend Modeled Only (Y/N)

Description

Attributes: {Provide the required information for classes’ attributes. Insert more lines into table when needed}

Attribute

Level

Visibility

Read only (Y/N)

Associated Type

Initial Value

Description

Methods: {Provide the required attributes for classes’ methods. Insert more lines into table when needed}

Method Level

Visibility

Description


23 of 27

Events: {Provide the required attributes for classes’ events. Insert more lines into table when needed}

Event Type

Visibility

Description

Types: {Provide the required attributes for classes’ types. Insert more lines into table when needed}

Type Visibility

Associated type

Description

Table Parameters: {Provide the required attributes for function’s table parameters. Insert more lines into table when needed}

Parameter Name.

Typing

Associated type

Optional (Y/N)

Description


OO ABAP Method Attributes: {Provide relevant attributes for the OO ABAP Method}

Name N/A

Description

Development Package

ABAP OO Class


24 of 27

Parameters: {Provide the required attributes for method parameters. Insert more lines into table when needed}

Parameter

Type

Pass Value (Y/N)

Optional (Y/N)

Typing Method

Associated Type

Default Value

Description


Message Class Attributes: {Provide relevant attributes for the message class}

Name N/A

Description

Development Package

Msg. Number Message Text Long Text (Y/N)

Table/Structure Attributes: {Provide one template for each new custom table created for this object}

Name: N/A

Short Text:

Type Transparent Pooled Cluster

Structure APPEND CI Customer include

Development Package

Delivery Class:

Table Maintenance:

Data Class:

Size:

Buffering:

Table Locking:


25 of 27

Authorization Group:

Tables and Structures Fields: {Provide all fields that are new, changed, or deleted. Highlight the key fields and provide information if the field has been added, changed or

deleted}

Table/Structure: Expected Size:

Field Name Data Element

Domain Description (Change, Add, Delete, Key, etc.)

View attributes: {Provide all fields, joins, conditions that are new, changed, or deleted. Highlight the key fields and provide information if the field has been added, changed or

delete}

Name: N/A

Short Text:

Development Package

Data Access

Table Maintenance:

View Fields: {Provide all fields that are new, changed, or deleted. Highlight the key fields and provide information if the field has been added, changed or deleted. Also,

mention in the description if Data Element was changed from the original}.

View Field Name Table Name

Field Name

Description (Change, Add, Delete, Key, etc.)

Selection Condition: {Provide all fields that are used for selection, the value, the operator and logical conditions}

Table and Field Name

Operator

(=, >, <, <>, etc.)

Comparison Value AND/OR

Table Joins: {Provide all table join conditions.}

Left Table Name

Left Field Name

Right Table Name Right Field Name


26 of 27

Domain Attributes: {Provide details of all custom domains created for this object}

Domain Name

Description Data Type/Length

Output Length

Lower Case

Check Table

Data Elements Attributes: {Provide details of all custom data elements created for this object}

Data Element Name

Description Domain

Parameter ID

Field Labels

Search Help Attributes: {Provide relevant attributes for the search help}

Name

Description

Lock Object Attributes: {Provide relevant attributes for the lock object}

Name N/A

Description

Development Package

Primary Table:

Primary Lock Mode

Secondary Lock Tables: {Provide information about secondary tables}

Name Lock Mode

Lock Parameters: {Provide information about the lock parameters}

Lock Parameter wanted Lock Parameter Name

Table Field


27 of 27

8 Revision History

Revision Reason for Change Description of Change

<Initial Release, any change to the content of the document…>

<If not an initial release, describe the changes to the document>

Date post:	05-Jan-2016
Category:	Documents
Upload:	shashank-jaiswal
View:	239 times
Download:	0 times

Enhanced Conversion Program for Creation and Maintenance of HR Mini Master

Documents