BBP

Global Template SAP Business Blueprint Document
Current Version: Business Owner: Version Release 1.10
Author: Approved By:
Approval Date:
Version R 1.10
SAP Business Blueprint Document Global Template
Page 1 of 124
Business Blueprint Document
Revision History
Ver. No. Date Updated Revision Author Brief Description of Changes
Table of Contents
1 EXECUTIVE SUMMARY SAP BLUEPRINT............................................................................3 2 COMPANY NAME PROJECT BACKGROUND.......................................................................5 3 GLOBAL TEMPLATE PROCESS SCOPE .............................................................................5 4 HCM STRATEGIC ELEMENTS ORGANIZATION MANAGEMENT......................................12 5 HCM STRATEGIC ELEMENTS PERSONNEL ADMINISTRATION .....................................19 6 HCM ADMINISTRATION ..........................................................................................................28 7 HCM PAYROLL ADMINISTRATION & TIME ADMINISTRATION ........................................83 8 ADDITIONAL CONFIGURATION ELEMENTS ........................................................................99 9 GLOBAL CONFIGURATION ELEMENTS ............................................................................120 10 GLOSSARY OF TERMS.......................................................................................................123
Version R 1.10
Page 2 of 124
1
1.1
Executive Summary SAP Blueprint

Purpose of this document The Blueprint design document is a sign-off milestone in the XXX Template project. The design contained in this document represents how the Global Template will be configured and delivered in SAP HCM ECC 6.0, and the same to be adopted and rolled out to zones/countries. This blueprint document defines setup and requirements for the first release of the Global template 1.0. Further adjustments and additional requirements not considered in scope of this Release 1.0 will be consolidated in the next Bronze release. Sign-off of this document will trigger the Realization phase (build) in which the SAP HCM system plus all associated technical objects (reports and interfaces) will be configured and developed to deliver the design which is set out in this document. The Blueprint document will be deemed accepted on sign-off. The target date for sign-off is close of business X.
1.2
Changes to Blueprint Design The signed-off Blueprint document is the basis of all design decisions and subsequent build. This document contains all requirements, as the Blueprint alone becomes the one source of functional and technical design for the system build. This Blueprint supersedes all other requirements, design and scope document. The subsequent testing after build phase will be to confirm that the configuration and development of the SAP HCM system and associated technical objects are as per design stated in this Blueprint document. Amendments to the configured SAP HCM system during the testing cycles will be limited to bring the system back to conformity with the Blueprint design. Testing, including User Acceptance Testing (UAT) is not an opportunity for redesign. Any subsequent changes to design after the sign-off of the Blueprint design document will be subjected to rigorous scope/change control. Any subsequent changes to design after the sign-off of the Blueprint design document will result in additional cost, may result in re-work and may delay the rollout of Global Template to NA rollout.
1.3
Document Structure The SAP Blueprint has been broken down into the following sections: a) Project Background
Version R 1.10
Page 3 of 124
Business Blueprint Document This section covers the overall background of project, Global Template approach, Global Template blueprint scope. b) Global Template Process Scope This section details the People processes in scope of the Global Template Bronze package, delivered and signed off by XXX Global Template business team at Company Name. c) Global Template Data Scope This section details the data scope (both Global and Local) for processes in scope of the Global Template, delivered and signed off by zone representatives part of the Global Template business team. d) HCM Strategic Elements Organization Management This section covers the details of the HCM Strategic Elements Organization management in scope of the Global template. This includes the scope of Organization structure comprising of standard and custom objects and relationships among them. e) HCM Strategic Elements Personnel Administration This section covers the details of the HCM Strategic Elements Personnel administration in scope of the Global template. This includes the Enterprise structure and Personnel structure f) HCM Administration This section details the information that will be configured, delivered and maintained for the processes and data in scope of the package. This will be the basis for the respective zones to adopt and incorporate additional country specific requirements on top of it. g) Additional Configuration elements This section covers the action and action reasons to be configured to execute employee lifecycle. In addition this section details the infotypes grouping (infogroups) corresponding to each action. h) Global Configuration Elements This section provides the list of all configuration items related to modules in scope for this release, along with details of future maintenance. i) 1.4 Glossary of Terms Blueprint Approval The full Business Blueprint document will be in excess of 100 pages. Business process owners and representatives of the business at Company Name will need to validate and approve the processes outlined in the blueprint document. Initial validation has occurred in process workshops and Gap workshops by the interaction of the project team with the core business representatives of Company Name and Company Name.
Version R 1.10
Page 4 of 124
Company Name Project Background

Company Name People Excellence program is the umbrella program delivering business solutions to enable and provide a unified People Service Delivery Model, across all zones. The People Excellence program aims to enhance the role of HR in the organization by way of redefining the role that the Human Resources function plays in driving workforce performance, focusing on benefit and consultancy, rather than administration. Company Name is one of the projects under the umbrella of People Excellence program aimed to automate people functions and deliver HR transaction layer. The approach to Company Name project is a modular one in order to allow the zones/countries to select the capabilities that are required to address the current business needs for the respective zones.
3
3.1
Global Template Process scope

This section details the People processes in scope of the Global Template Organization Management Processes The Organization management functions at Company Name include processes related to creation of jobs and positions, strategic and operational reorganization and deletions of obsolete jobs/positions. All these process/subprocess are handled by SAP Organization Management (OM) module. The SAP OM module helps in maintaining and depicting Organizational structures and employee assignments within the organization structures. The SAP OM module supports the following processes in line with Company Name Organization management requirements: Depict Organizational Structures Manage employee jobs and positions Re-organize/ re-structure organizational units, jobs and positions Design and deliver system based workflow processes Permit and grant security at the Organizational level within the system
The following are the list of processes, the Global template team has identified and delivered, related to employee organization management. There are total of five (5) processes.
Process No. ORG_001 ORG_002
HR Process Map Description Organization Management Create & Review Position Budget Create/update new position
Version R 1.10
Page 5 of 124
ORG_003 ORG_004 ORG_005
Delete Positions Operational reorganization Creation of new department or jobs within Zones Strategic reorganization Creation of new department or jobs across Zones
3.2
Employee Workforce Administration Workforce administration at Company Name includes processes related to employee hiring, on-boarding, organizational reassignments (probation confirmations, transfers, promotions, demotions), & terminations. All these processes/sub-processes are handled by SAP Personnel Administration (PA) module. The SAP PA modules handle the basic employee personnel procedures of hiring, employee organizational reassignments and terminations, including employee master data administration. The following are the list of processes related to employee workforce administration, the Global template team has identified and delivered. There are total of 16 processes. Process No. WFA_101 WFA_102 WFA_103 WFA_104 WFA_105 WFA_106 WFA_107 WFA_108 WFA_109 WFA_110 WFA_111 WFA_112 WFA_113 WFA_114 HR Process Map Description Workforce Administration Employee Hire/Rehire/Recall into System On boarding & Probationary confirmation Company Assets Allocation (Objects on Loan) Request for additional assets Employee Transfers Employee Demotion Employee Leave Planned Vacation Employee Leave Unplanned Employee Leave Maternity Employee Leave Strikes Termination Voluntary Termination Involuntary Termination Death Termination- Layoff
Version R 1.10
Page 6 of 124
WFA_115 WFA_116
Data Changes Employee Personnel Data Change in Rewards Merit/Adhoc
Exceptions Time Management: The above processes include a part of time management. This is related to exception time regarding namely Employee leave and absence recording. Full time management; positive time recording, overtime recording, etc., including reporting will be included in next release. 3.3 SAP Infotypes & Subtypes
3.3.1
Definition Infotypes
SAP stores all types of information about an employee in Human Resources infotypes (IT). SAP HR infotypes provides the data store for related set of information and facilitates employee data entry, and storing of data for specific periods. In each IT, information about a particular subject is stored. For e.g. the IT Personal data contains the information related to names (first, last, middle, etc.), birth date, birthplace, nationalities and marital status of an employee, whereas the IT Education stores the certificates of the employee with detailed information on his/her grade(s).
3.3.2
Definition Subtypes
In SAP, certain infotypes data stores can be further divided. The need is store multiple entries for a similar data. This is achieved by Subtypes, whereby an SAP infotypes can contain several subtypes. For e.g. infotype Family/ Related person is divided into subtypes such as Spouse, Child, Cohabitant, etc From a functional point of view, each HR data store has a corresponding screen in SAP. This screen can be at the level of an infotype or at the level of a subtype. For e.g. each of the subtype in the IT-Family data, a different screen exists to store the information of the family members or other relation of the employee. Note: Each infotype and subtypes are represented in SAP by unique identification no. For e.g. infotype Personal Data is refereed as IT 0002, infotype Education data is referred by IT 0022. Similarly, infotype Family data is referred by IT 0021, whereas subtypes for the infotype are also numbered; spouse is subtype 01, child is subtype 02, etc.
Version R 1.10
Page 7 of 124

3.3.3 Data Validity Periods
All employee-related data is logged with the exact date into various infotypes. Data remains transparent and reflects in terms of time progression, and creates the basis for sound personnel decisions. Each IT screen has a validity period, and is reflected in the header of the screen (refer to figure below) and determines the period the data displayed is/was valid. If the end date of the validity of record is not yet known, the end date will be 31.12.9999, and the record is active.
Figure: Data validity period

3.3.4 Time Constraints
For each screen (infotype or subtype) has a time constraint. It indicates how many data screens may or must exist at a certain moment. The following time constraints are maintained in SAP: Time constraint 1: An infotype record must be available at all times. This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted (mandatory information no gaps no overlaps).
Figure: Time constraint-1 data sequence Time constraint 2: Only one record may be available at one time, but time gaps are permitted (non-mandatory information possible gaps no overlaps).
Figure: Time constraint-2 data sequence Time constraint 3: Any number of records may be valid at one time, and time gaps are permitted (non-mandatory information possible gaps possible overlaps).
Version R 1.10
Page 8 of 124
Figure: Time constraint-3 data sequence 3.4 Global Data elements mapping with SAP Infotypes The required global HR data elements were consolidated based on the inputs provided by zones. These data elements where then grouped into two sets: one global and another local. Based on the segregation, the final list of global data elements where signed off by all zones. Enclosed is excel file containing the list of global data elements.
All the global data elements are grouped into SAP infotypes. The following are the list of global infotypes configured in Global template and maintained at the global level:
Global Infotypes OM 1000 1001 1003 1007
Descriptions Organization Objects Object Relationships Department/Staff Vacancy infotype
Global Infotypes PA 0000 0001 0002 0004 Actions
Descriptions
Organizational Assignments Employee Personnel Data Challenge
Version R 1.10
Page 9 of 124
Global Infotypes PA 0006 0009 0016 0019 0021 0027 0037 0040 0041 0077 0080 0105 0185 0442 0709 0710
Descriptions Employee Addresses Bank Details Contract Elements Monitoring of Tasks Employee Family/dependents data Cost distribution Insurance Infotype Objects on Loan Date Specifications Additional data Maternity Protection Communications Person IDs Company car Global ID Global Assignment details
Global Infotypes PY 0008 0014 0015
Descriptions Employee Basic Pay Recurring Payment Additional Payments
Global Infotypes TIME 0007 2001
Descriptions Planned Working Time Absence
Version R 1.10
Page 10 of 124
2002 2006 2007 2013
Attendance Absence Quota Attendance Quota Quota Corrections
3.5
Setup of Global data elements The following key principles will be adopted for Company Name, related to setup and maintenance of global data elements: The infotypes listed in the above section related to OM, PA and PY are global infotypes. The content of these infotypes will be managed on a global level
Version R 1.10
Page 11 of 124
HCM Strategic Elements Organization Management

This section outlines how the various strategic elements in Organizational management (OM) component of SAP HCM will be configured and used in Company Name. This section focuses on the factors that need to be accommodated in order to meet Company Name current requirements and ensure that the Organizational structure supports future requirements. The detail includes the various Organizational objects and the possible relationships among the objects leading to organization structure.
4.1
Organizational management requirements for Company Name Company Name had defined their organization management requirements by what is referred as Blueprint. The Blueprint is the basis of delivering and administering the employee organization structure, namely: Org. units, Departments, Jobs, Bands and Positions. Currently Company Name has adopted and maintaining the organization management based on Blueprint for Management employees Band I to IV and Band V to VII, across all zones and countries. The organization structure for the banded employees is defined to two (2) levels referred as EBM-2 (Execute Board of management). Based on the discussions as part of requirements gathering, it has been agreed to implement the Blueprint for Company Name. The Blueprint organization structure will be the basis for the Global Template.
4.1.1
Setting up of Organization structure for Company Name
The current structure of Company Name will be copied via the ALE interface into Company Name just before go-live. This means that all organization units and positions that are already defined and implemented in Company Name will be setup in Company Name at the time of go-live. Any data cleansing in the OM structure which is now in Company Name must be done manually directly in Company Name before go-live Once updated in Company Name, these positions needs to be linked with the employee no. (New PERNR in Company Name) and will be interfaced back to Company Name after migration of new PERNR in Company Name. In addition, Company Name will extend the current OM structure with the missing employees (those who are not yet setup in Company Name) After going live, any changes/additions to the objects (org. units, positions and relationships) will be interfaced back and updated in Company Name. Both the Company Name and Company Name will be aligned on periodic basis by way of bi-directional interfaces post go-live.
Version R 1.10
Page 12 of 124

4.1.2 OM Objects in scope of Global Template
The following organization (OM) objects are in scope of the Global template. Object Type O S C K P CP
4.1.3
Descriptions Organization units Positions Jobs Cost Centers Person/Employee Person ID Relationships
Organizational Units
Organizational Units represents a functional unit in your enterprise. Depending on how tasks are distributed in an enterprise, these can be departments, groups or project teams, for e.g. marketing department, finance department, brewery operations etc. In SAP, an organizational unit is an organizational object of type O forms the basis of an organizational plan. Proposals: Setting up of organizational units leading to organization structure:
Jobs
4.1.4
Jobs will be adopted from Company Name into Company Name for band I-IV & EBM-2 employees at the time of go-live. After go-live, all data maintenance related to job for band I-IV employees will be carried out in Company Name and interfaced back to Company Name. Till a global job catalog is not implemented, Company Name will maintain external number ranges for jobs. This will act as added validation in Company Name to not create jobs for other employees.
4.1.5 Positions
Positions are used to describe a seat in the organization. Positions are concrete and are occupied by holders (employees). For e.g. purchasing clerk, European sales manager or Secretary to VP, are positions. Positions will be grouped together in one organizational unit. Each organizational unit will have a chief position (head of the organizational unit).
Version R 1.10
Page 13 of 124
Business Blueprint Document In SAP, a Position is an organizational object of type S which is used to distribute tasks in an organizational plan as well as to model the reporting structure. Relationships are set between Positions (Object type S) and Organization unit (object type O).
Figure: snapshot showing employee holding multiple positions in OM
Version R 1.10
Page 14 of 124
4.1.6
Cost Centers
In SAP OM module, Cost Centers can be assigned to organizational units to track labor costs of employees holding positions in the organizational unit.
4.1.7
Number ranges for OM Objects
To distinguish between Company Name and Company Name objects (Org. units, Jobs and Positions); both systems will follow different number ranges. Proposals: The Company Name number range will start from 10000000 internal number assignment for local O, local S. The Company Name will maintain an external number for C as described in section related to jobs. For objects CP (global ID), refer section on Employee number ranges.
4.1.8
Naming conventions for Organization objects
The following naming conventions will be adopted by zones for all Organization objects (Org. units, Jobs, Positions): All organization objects; Organization Units, Jobs and Positions descriptions will be in English for all levels, in additions to maintaining in local languages if any. (SAP allows descriptions for these objects to be maintained in multiple languages) The Organization units will follow the Company Name organization blueprint standards. Naming Conventions for Positions The position title abbreviations must be in CAPITALS. The short position description must contain only the generic title abbreviation (VP, GM, ZP ...), for e.g. all General Managers will have same abbreviation GM, while the Position names will be specific, like GM Hungary, GM Canada, etc.
Version R 1.10
Page 15 of 124
Figure: OM object naming conventions (for Position) The long description must contain the generic title abbreviation. The following is the list of generic title abbreviation 4 VP = Vice president 5 SVP = Senior Vice President 6 GM = General Manager 7 ZP = Zone President 8 BUP = Business President 9 MGR = Manager 10 DIR = Director
Version R 1.10
Page 16 of 124
4.2
Relationships
Organization Management Data Model Object
Within the module of SAP Organizational Management, an organizational structure or organizational plan will be set up. This structure is build out of several components (objects), which are related to each other by concept of Relationships. The relationship between different objects is the key in setting up of Company Name Organization management. Without relationships, all you have are isolated pieces of information. Creating and editing relationship infotype records is an essential part of setting up information in the Organizational Management component to establish reporting needs. Relationships between objects are reciprocal. For e.g. if a job describes a position, then the position, in turn, will be described by the job. Hence, it is required to create a relationship in one direction. The inverse relationship will automatically be created by the system In addition to the standard object relationships, one can set up custom relationships, based on additional reporting requirements. However, the standard relationships between basic object types provided by SAP will not be changed.
Figure: SAP OM Objects & relationships in Company Name
Version R 1.10
Page 17 of 124
Proposals: The following object relationships will be setup and maintained in Company Name between organization objects. Relationshi p Type OO OS SS SP SK P CP Relationships A002 A003 + A012 A004 A008 A011 A209 Description Reports to Belongs to Reports to- Dotted Line Manager Holder Has cost centers
Version R 1.10
Page 18 of 124
HCM Strategic Elements Personnel Administration

This section outlines the necessary strategic and structural elements related to Personnel administration (PA) component of SAP HCM, in addition to how these will be configured and used in Company Name. The elements documented here will drive processing decisions within the SAP HCM module and will form the basis for global reporting requirements at Company Name. This section provides details of Enterprise structure and Personnel structure that need to be accommodated in order to meet Company Name reporting requirements and ensure that the Personnel Structure supports future requirements. The Enterprise Structure outlines the integration with the overall Company Name finance structure and details the employee grouping/classifications to be adopted, whereas the Personnel Structure will be used for employee classification within Company Name, and consists of the following components:
5.1
Personnel Administration Data Model All Company Name employees, including external employees must be assigned to the following structural classifications: The Enterprise Structure reflects the finance structure at Company Name, and consists of the following components: a. Company Code b. Personnel Area c. Personnel Subarea The Personnel Structure will be used for employee classification within Company Name, and consists of the following components: a. Employee Group b. Employee Subgroup c. Payroll Structure, this consists of the Payroll Area (This is outside the scope of Global template configuration, and will be configured by zones/countries implementation team)
5.2
Enterprise Structure for Global Template SAP assigns employees to a part of the Enterprise structure. This is performed through assignment to a company code, personnel area and personnel sub area. All these three elements are held in infotype 0001 Organization Assignment.
5.2.1 Company Code
The first level of the enterprise structure is the Company code. The company code is the top level of the SAP HR Enterprise structure. The
Version R 1.10
Page 19 of 124
Business Blueprint Document company code in SAP represents an independent company or legal entity with a separate financial accounting. The company code is the smallest organizational unit of external accounting in which complete and isolated financial accounting statements can be created. All events that affect the company code and the creation of all statements for a legal financial statement, for example balances, profit and loss calculations are contained with the company code organizational units This is defined and controlled in the Financial Accounting (FI) module of SAP. Proposals: The proposal is to adopt the current list of Company codes setup and maintained in Company Name into Company Name. Enclosed is list of company codes extract from Company Name with changes as required for North America. Setup of Company Code: After Company Name goes live, any new addition of Company codes will be created physically along with other finance objects, like cost centers.
5.2.2 Personnel Area
The second level of the enterprise structure is the level of the Personnel area (PA). A personnel area is a specific HR organizational unit, and is a subdivision of the company code and represents a delimited enterprise area. The Personnel area is commonly used to represent one of the following: Physical Facilities Geographic Regions Logical Divisions Office Locations
The personnel area is only used in Personnel Administration and is unique. Personnel Areas are related to the country code in the system and are country specific. Therefore, when an employee is hired onto SAP they inherit the national characteristics of that Personnel Area e.g. the currency their annual salary is expressed in or the format of their home address. Usage of Personnel Areas Personnel areas are a key selection criterion for standard SAP evaluations & reports, e.g. How many employees work here?
Version R 1.10
Page 20 of 124
Business Blueprint Document Used as an entity for authorization checks Used for defaulting values in fields. For example, Payroll area, work schedules For defining benefit areas and identifying eligibility for various benefit plans
Proposals: Personnel Area is a 4-character alphanumeric code in SAP. The proposal is to adopt the current list of Personnel areas setup and maintained in Company Name into Company Name. There is a one-to-one relationship between Personnel areas and Company codes, with same code and names. Enclosed is list of PA extract from Company Name.
5.2.3
Personnel Subarea
Personnel areas are sub-divided into Personnel subareas (PSA). A personnel area is assigned to a company code, which has the financial accounting values that are relevant for the personnel area, whereas a Personnel Sub area is a sub division of Personnel Area and it is used to define public holiday calendar, pay scale area, pay scale type, work schedule rules and define absence types. Personnel subarea is the lowest level of Enterprise structure where an employee will be physically located and is used only in Personnel administration. Organizational data can be stored in Personnel area and personnel sub area level. Usage of Personnel subareas Determine which entries from the set of infotypes screen assigned to an action are allowed for an employee within a company code/personnel area. To group Payroll and time data; Pay scale type/area, work schedules, absence types, leave types, To define location-specific Public holiday calendar To default Primary wage types/wage type model for a pay scale structure Personnel Subarea is also a key standard selection criterion for evaluation & reports Defining benefits area for administration of benefit plans Identifying eligibility for various benefits plans
Version R 1.10
Page 21 of 124
Business Blueprint Document Proposals: The Personnel subareas at Company Name will represent the physical location/offices/plants/warehouses. Personnel subareas are 4-character alphanumeric code in SAP. The proposal is to adopt the current list of Personnel subareas setup and maintained in Company Name into Company Name. The PSAs codes will be running sequential no. Every time a new PSA is created the same needs to be set up and synchronized with same code in both Company Name and Company Name. Enclosed is list of PSA extract from Company Name.
Version R 1.10
Page 22 of 124
5.3
Personnel Structure for Global Template The Personnel structure is a functional way of dividing the employee population. The division is made at two levels: Employee Groups (EG) and Employee Subgroups (ESG). Within each personnel file (per SAP personnel number P) an assignment to an employee group and subgroup must be available. This assignment is stored in infotype 0001 Organizational assignment.
5.3.1 Employee Group
Employee groups represent a primary subdivision of personnel. An employee group defines the extent to which its employees place their labor at the disposal of the enterprise. EG defines the relationship between the employee and the company in terms of work contribution, for e.g. active/regular employees, retirees/pensioners, external employee, etc. The employee group has the following organizational functions: Employee groups allow default values during employee actions, for e.g. employee payroll accounting area or an employees basic pay. Employee groups along with employee subgroups serve as selection criteria for most of the standard SAP reporting. Employee groups constitute an authorization check unit.
Proposal for Employee Group: The following Employee Groups will be defined and configured in Global template. The same will be adopted by respective zones and countries. These employee groups have been standardized based on global reporting requirements. Employee Group 1 2 3 4 5 6 7
Description White Collar Blue Collar Executives (Bands I to VII) Retirees/ Pensioners External Employee Expats Inpats (CR_NA_2007_08-03)
A new employee group Inpats has been added to design. The following is the difference in which Expats and Inpats groups will be treated in Company Name. ((CR_NA_2007_08-03) The Expats employee group will be used by the Home country The Inpats employee group will be used by the Host country
Version R 1.10
Page 23 of 124

5.3.2 Employee Subgroup
Employee subgroups subdivide employee groups. Within the employee group for active employees, for example, a distinction is made between the following employee subgroups, for e.g. white collared employee, management employees, hourly wage employees, etc. All of the control features for the personnel structure are defined at the employee subgroup level. The most important control features are as follows: Standardize or differentiate how an employee is dealt with for a personnel calculation rule using the grouping of employee subgroups. For example, employees remuneration that is to be calculated either on a monthly or hourly basis can be controlled using this grouping. Determining which wage types are permissible for which employee subgroups using the employee subgroup grouping for the primary wage types. With the employee subgroup grouping for collective agreement provision, the eligibility of pay scale groups can be restricted, so that only certain pay scale groups are valid for specific employee subgroups. Determining which work schedules are permissible for which employee subgroups using the employee subgroup grouping for the work schedule.
Proposal for Employee subgroup: Employee subgroups to be defined by zones: Each zone will be authorized to define its own set of employee sub-groups. Employee Sub-Groups will be determined based on local requirements driven mainly by Payroll, Benefits and Time. There are certain employee sub-groups which need to be adopted and maintained at the global level. The following subgroups will be adopted by all zones for the following:
Employee group 6-Expats
Employe e Subgrou p E1
Description
Comment s
White Collar Short term
Version R 1.10
Page 24 of 124
Business Blueprint Document Employee group Employe e Subgrou p E2 E3 E4 E5 E6 7-Inpats (CR_NA_2007_08 -03) I1 I2 I3 I4 I5 I6 3-Executives T1 Description Comment s
Executives Short Term White Collar Long term Executives Long Term Third country national White Collar Third country national Executives White Collar Short term Executives Short Term White Collar Long term Executives Long Term Third country national White Collar Third country national Executives Global Management Trainees They all are executives and hired at the global level
T2 1-White collared T1
AIESEC Trainees Global Management Trainees
The above sub-group for trainees and Expats had to be defined and followed by all zones to track employees hired as Expats and Trainees (to track carrier progression).
Proposed standardization of defining Employee sub-groups
5.3.3
Employee subgroups are 2 characters, and the following naming conventions will be adopted by the zones for defining Employee subgroups. First character is first letter of country (A-Z) or numbers (0-9) if letters not available Second character is sequential numbering (0,1,...9,A ...Z)
Version R 1.10
Page 25 of 124
Exceptions: In case a zone wants to use common sub-groups for countries within a zone, they can have the alphabets or numerals representing the first letter/digit of country code and document the same in their respective blueprints, for e.g. if Belgium and Luxemburg wants to share the same ESG, then the code can be as follows: B0, B1, B2, B3, etc.
5.3.4 Define Employee Attributes
As part of the Enterprise structure setup, once the employee groups and employee subgroups are setup, there is a additional requirement to assign one of the following statuses to those employee groups and employee subgroups: Activity status Employment status Education and training status Enclosed is the mapping sheet, mapping EG, ESG with the corresponding valid/applicable attributes.
E:\Projects\Inbev\ Global Templates_Bronze\Blueprint\Employee Group_Employee subgroup attributes_V 0.1.xls
The meanings of the statuses in SAP are predefined and will not be changed.
5.3.5 Payroll Area
Another component of the Personnel structure hierarchy is the Payroll area. Payroll areas are an organizational unit in the Human Resources department, which can be defined for a unified payroll area. Based on organizational assignment criteria, all of the employees who are accounted simultaneously in the payroll are assigned to the same payroll area. Proposals: The Payroll areas will be defined by zones/countries if Payroll processing will be done through Company Name.
Proposed standardization of defining Payroll areas Payroll areas are 2 characters, and the following naming conventions will be adopted by the zones for defining Payroll areas.
Version R 1.10
Page 26 of 124
Business Blueprint Document First character is first letter of country (A-Z) or numbers (0-9) if letter not available Second character is sequential numbering (0,1,...9,A ...Z)
Version R 1.10
Page 27 of 124
6
6.1
HCM Administration
OM Infotypes in scope of Global Template SAP Organizational Management is fully integrated with the Personnel Administration module in SAP. This integration occurs when an employee is assigned a position in Personnel Administration during hiring or organizational re-assignments. Once assigned to a position, an employee automatically inherits all of the details about the position, the job describing it and the organizational unit to which it has been assigned. This integration provides an efficient way of maintaining data in that it reduces the amount of data that must be manually entered for an employee. In addition, the OM data reduces the amount of duplicate entries that would be required when employee organization data changes. For example, cost centers are assigned to the Position. Since PA & OM are integrated, any employee assigned to the position will automatically inherit the cost center assigned. The following OM infotypes will be configured and maintained in SAP by Global Template. Global Infotypes OM 1000 1001 1003 1007 Descriptions
Organization Objects Object Relationships Department/Staff Vacancy Infotype
Version R 1.10
Page 28 of 124
6.1.1
IT 1000 Objects
Infotype 1000, determines the existence of an organizational object, namely Organization unit, job etc. and the validity period
Figure: Snapshot screen of IT 1000

Object Type O S C CP Description Organization Unit Positions Jobs Central Person Remarks SAP Standard SAP Standard SAP Standard SAP Standard
Version R 1.10
Page 29 of 124
6.1.2
IT 1001 Relationships
Infotype 1001 defines the relationships between different objects (Org. units, Jobs and Positions) as per Infotype 1000.

All the possible relationships between objects (O, S and C) are setup and stored in IT 1001. Creating and editing relationship infotype records is an essential part of setting up information in the Organizational Management component. Without relationships, all you have are isolated pieces of information Proposals The following relationships will be set up and maintained as part of Global Template: Relationshi p Type OO OS SS SP SK P CP Relationships A002 A003 + A012 A004 A008 A011 A209 Description Reports to Belongs to Reports to- Dotted Line Manager Holder Has cost centers Remarks SAP Standard SAP Standard Customized SAP Standard SAP Standard SAP Standard
Version R 1.10
Page 30 of 124
6.1.3
IT 1003 Department/Staff
Infotype IT 1003 will be maintained with which you can allocate a staff indicator to organizational units and positions, or flag organizational units as departments. This infotype also allows applying a Department flag to organizational units
Global Data elements
The following fields related to IT 1003 will be configured as part of Global Template. Term Staff Definition / Use / Possible entries Allows you to apply a staff flag to a position or an organizational unit. A staff flag indicates that a position or organizational unit is not part of the normal reporting structure at your firm, but rather reports directly to a high level position or organizational unit. Optional/ Mandatory Optional Kit/Core Core
Version R 1.10
Page 31 of 124
Proposals: To apply the staff flag to both organizational units and positions. Using this flag will help in identifying a Staff department or positions.
IT 1007 Vacancy
6.1.4
Infotype 1007 will create a vacancy for open positions. Maintaining the vacancy infotype will help create a vacancy record for an occupied position if. For e.g. when an employee is taking maternity leave or on a long leave, and there is a need to fill in the position for the intervening period. The vacancy infotype will be set up as part of Global template, so as to distinguish between occupied and unoccupied positions.
Global Data elements The following fields related to IT 1007 will be configured as part of Global Template. Term Open Definition / Use / Possible entries This is used to specify that the selected position is vacant, that is, is available to be occupied This indicator is used to Optional/M andatory Mandatory Kit/Core Core
Vacancy
Mandatory
Core
Version R 1.10
Page 32 of 124
Business Blueprint Document Term Filled Definition / Use / Possible entries specify that the selected position is no longer vacant but occupied. Optional/M andatory Kit/Core
Version R 1.10
Page 33 of 124
6.2
PA Infotypes in scope of Global Template Currently the employee data captured in different legacy HR applications across zones/countries will be captured in SAP PA module using the relevant infotypes. Some of these objects are important for design; configuring and maintenance in SAP Personnel Administration module are listed below. The following PA infotypes will be configured and maintained in SAP by Global Template.
Global Infotypes PA 0000 0001 0002 0004 0006 0009 0016 0019 0021 0027 0037 0040 0041 0077 0080 0105 0185 0442 0709 0710 Actions
Descriptions
Organizational Assignments Employee Personnel Data Challenge Employee Addresses Bank Details Contract Elements Monitoring of Tasks Employee Family/dependents data Cost distribution Insurance infotype Objects on Loan Date Specifications Additional data Maternity Protection Communications Person IDs Company car Global ID Global Assignment details
Version R 1.10
Page 34 of 124

6.2.1 Action IT 0000
This infotype contains a history of all of the personnel actions (Processes) that have been performed for the employee. HR process such as hiring an employee, organizational reassignment, or employee termination, are represented and define in IT 0000.

Global Data Elements The following fields related to IT 0000 will be configured as part of Global Template. Term Action type Reason for action Employment status Position Personnel area Employee group Employee subgroup Definition / Use / Possible entries See further in this document See further in this document Status assigned as part of the process of performing an employee action. Optional/ Mandatory Mandatory Mandatory Mandatory Kit/Core Core Core Core
Mandatory Mandatory Mandatory Mandatory
Core Core Core Core
Version R 1.10
Page 35 of 124
The following Action infotype data elements will be configured and delivered in Global Template: Action Type Action Reasons Employment Status
Action Type & Action Reasons The details of the action type and action reasons to be configured are provided in section: 8.1 and section 8.2. Employment Status Employment status is one of the key fields for reporting and timeconstraint validation. Employment status reporting is used to indicate entries into and exists from the company. The following are the four (4) type of employment status that is standardized and is being configured for Global template.
Description Active Inactive Withdrawn Retired The employment status ties up with employee action as shown below in the figure below. Every employee action receives an Employment Status assignment as part of the process of creating an action. When a specific action is executed against an employee, the system updates their Employment Status on IT 0000
Figure: Employment status update on Employee action
Version R 1.10
Page 36 of 124
6.2.2
Organizational Assignment IT 0001
The Organizational Assignment infotype deals with the incorporation of the employee into the organizational structure and the personnel structure. This infotype contains key details/information about an employees role, position and function within the organization, including the position number, personnel area, personnel subarea, business area, payroll area, employee group and employee subgroup.
Figure: Snapshot screen of IT 0001 Global Data Elements The following fields related to IT 0001 will be configured as part of Global Template. Term Company code Legal person Personnel area Personnel Subarea Definition / Use / Possible entries Company codes will be synchronized with that in Company Name. Company code will be filled. Used for legal reporting. One to one mapping with company code. Same as Company code. Personnel subarea will be synchronized with that in Company Name. Optional/ Mandatory Mandatory Mandatory Mandatory Mandatory Kit/Core Core Core Core Core
Version R 1.10
Page 37 of 124
Business Blueprint Document Term Cost center Definition / Use / Possible entries Values to be provided and assigned by zones. Use the same codes as in zone/country finance system
A unit in an enterprise that groups product and market combinations as homogeneously as possible for the purpose of developing unified business policy.
Optional/ Mandatory Mandatory
Kit/Core Core
Business Area
Optional
Employee group Employee subgroup
Refer to section 6.3.1 ESGs to be defined and configured by local zones. Refer to section 6.3.2 for sub-groups provided for certain employee groups. Values to be provided and assigned by zones. Will be used to store the descriptions of union to which employee belongs to. Refer to section 5.2.3 Refer to section 5.2.3 Refer to section 5.2.2 Refer to section 5.2.1 Will be empty Will follow Company Name/SAP standard (ISO codes) We will define local HR contact persons as personnel administrators. We will define time data administrator who will responsible for the employees assigned to him or her. We can use this field for authorization checks. We will define payroll administrator who will responsible for the employees assigned to
Mandatory Mandatory
Core Core
Payroll area Work Contract Percentage Position Jobs Organization al unit Organization al key Administrato r group Personnel Administrato r Time Administrato r
Mandatory Optional
Core Core
Mandatory Mandatory Optional Mandatory Optional Mandatory Mandatory Optional
Core Core Core Core Core Core Core Core
Payroll Administrato r
Optional
Core
Version R 1.10
Page 38 of 124
Business Blueprint Document Term Definition / Use / Possible entries him or her for payroll related issues. We can use this field for authorization checks. Optional/ Mandatory Kit/Core
The following data standardization and naming convention will be followed for data related to infotype 0001 Administrator Group One administrator will be defined for each PA with the same code. Like for example for Canada, one administrator group CA09 will be defined which is similar to the Personnel Area in Canada i.e., CA09. Administrator Codes The following naming conventions and groupings will be followed for defining administrator codes in Company Name: Administrator Codes Administrator Type Time/travel administrators range Payroll administrators range Personnel administrators range Code 001 999 001 999 001 999
Administrator Descriptions The administrator description will be name of the administrator.
Version R 1.10
Page 39 of 124
6.2.3
Personal Data IT 0002
The Personal Data infotype stores data for identifying an employee. This infotype enables to record an employees personal information such as Name, Employee Identification No., Birth date, Gender, and Marital status.
Figure: Snapshot screen of IT 0002 Global Date Elements The following are the fields related to IT 0002, which will be configured as part of Global Template. Fields Title Definition / Use / Possible entries Employees title. This field defines the gender of the employee. Possible values are: Miss, Mr., & Mrs. This entry will define how the employees complete name will be composed. This complete name will be the name used in most of the standard SAP reports. One standard option will be defined for all countries: Concatenation of the two fields Known as and Last name The employees last name Note: In case of a married employee, it depends on the national legislation whether Optional/ Mandatory Mandatory Kit/Core Core
Name format
Optional
Core
Last name
Mandatory
Core
Version R 1.10
Page 40 of 124
Business Blueprint Document Fields Definition / Use / Possible entries this is the employees maiden name. In some countries, a new infotype with a new name could be created in case of marriage during the employment valid as of date of marriage. Prefixes and suffixes are part of the last name. Last (family) name at birth The persons official first names Note: If a person has more than one official first name, then all of them are part of the first name. The persons middle name The employees initials These are defined as the first letters of the employees second names. Commonly used (first) name If not available, copy first name Display only. Combination of Title, First Name and Last Name This is sensitive information in Canada. Date of Birth Language of communication and correspondence This field indicates the persons nationality. This is sensitive information in Canada. Optional/ Mandatory Kit/Core
Birth name First name
Optional Mandatory
Core Core
Middle Name Initials
Optional Optional Core
Nick Name Name SIN Birth date Language Nationality Nationality 2nd/3rd nationality Gender Marital status
Mandatory Mandatory Mandatory Mandatory Optional Optional Optional Mandatory Mandatory
Core
Core Core
Core Core Core
In this field, enter marital status of the person.
Dependents
Number of dependents
Optional
Version R 1.10
Page 41 of 124
The following Personal Data infotype configuration will be delivered in Global Template: Tile/Form of Address Key The Form of Address Key or Title field holds the title by which the employee would like to be addressed. SAP provided the following standards form of address key, which will be retained and standardized for Global Template. SAP Standard Form of Address type FOA Desc. Long text Gender key 1 Mr Mr 1 2 Mrs Mrs 2 3 Miss Miss 2 4 Ms Miss 2 Name Format The Name Format field holds a pattern of name-related fields that define a standard format for addressing an employee in documents generated from SAP. This entry will define how the employees complete name will be composed. This complete name will be the name used in most of the standard SAP reports. The standard option to be define for Global Template will be Concatenation of the two fields; First Name and Last name Marital Status The Marital Status field holds the current marital status of the employee. SAP delvers a standard list of universally used marital status, which will be adopted for Global Template. The following marital statuses are available in Standard SAP. Code 0 1 2 3 5 6 7 9 Marital Status Designations Description Single Marr. Wid. Div. Sep. Cohab. Unk RegCou
Version R 1.10
Page 42 of 124
Version R 1.10
Page 43 of 124
6.2.4
Challenge IT 0004
The Challenge infotype is maintained for handicapped employees. It holds a lot of key on different ability employees working in the organization. This information could have influence on how an employee has to work. In certain countries, this infotype data is used to report on legal obligations/reporting related to employment of severely challenged persons in the organization.
Figure: Snapshot screen of IT 0004 Global Data elements The following fields related to IT 0004 will be configured as part of Global Template. Fields Definition / Use / Possible entries Challenge group can be used to distinguish between challenged trainees and challenged persons who have completed vocational training. These groups are stipulated by statutory regulations. The system proposes the challenge groups with their official abbreviations. In this field we can enter the Optional/ Mandatory Mandatory Kit/Core
Challenge Group
Degree of
Optional
Version R 1.10
Page 44 of 124
Business Blueprint Document Fields Definition / Use / Possible entries percentage for the severe challenge in accordance with the Severely Challenged Persons Law. The Type of Challenge can be used to distinguish between challenged persons with unlimited or limited working capability. Optional/ Mandatory Kit/Core
Challenge
Type of challenge
Mandatory
The following Challenge infotype configuration will be delivered in Global Template: Challenge Groups SAP provided standards will be adopted for Challenge Group in Global template. Any local requirements will be added by local zones. Code 1 2 3 4 5 6 7 8 9 11 12 13 14 15 16 17 18 19 21 23 24 26 28 40 41 50 NA Challenge Groups Description Severely challenged Sev.challgd./trainee Sev.challgd/employer Challenged peer Peer/trainee Mult.empld/sev.chllg Mult.empld/SC/train. Mult.empld/peer Mult.empld/peer/tr. Miners ins.policy SC/Workshops Peer/Workshops SC/Training Rehab Peer/Training- Rehab SC/Train. SubseqYr Peer/Train- SubseqYr Mult. SC/Workshops Mult. Peer/Workshops SC/other training SCER/other training Peer/other training MSC /other training Mpeer/other training Mult. SC/Train-Rehab Mult. Peer/Tr.-Rehab SAP Night-shift challgd Business Blueprint Document Work incapacity
Global Template
Version R 1.10
Page 45 of 124
Business Blueprint Document Type of Challenge SAP provided standards will be adopted for Type of Challenge in Global template. Any local requirements will be added by local zones. Type of Challenge Description Unlim.wrk.capability Lim.work capability Sitting jobs only Perm. Part.Disab. MX Perm. Total Disab.MX
Type 1 2 3 4 5
6.2.5
Addresses IT 0006
The Addresses Data infotype stores personal address data for an employee. Using different subtypes, it can hold one or more types of current address for an employee at the same time, like employees home, work, and emergency addresses.
Figure: Snapshot screen of IT 0006 Global Data elements The following are the fields related to IT 0006 will be configured as part of Global Template. Fields Address type C/O Definition / Use / Possible entries The address type specifies whether the address in question is the employees permanent or temporary place of residence. Referred to as: In Care of Optional/ Mandatory Mandatory Kit/ Core Core
Optional
Core
Version R 1.10
Page 46 of 124
Business Blueprint Document Fields Street House No. Apartme nt No. 2nd address line Postal code City Region/ State Country Key Definition / Use / Possible entries Street Name (field name: P0006STRAS) House number (SAP field name: P0006-HSNMR) We can mention Apartment no. (if employee lives in apartment) (SAP field name: P0006 POSTA) We can make additional specifications for an address in this field. Zip code Name of City Name of Region or state (as applicable for the country) The country key contains information which the system uses to check entries such as the length of the postal code or bank account number. Employee Contact No. corresponding to the address type Optional/ Mandatory Mandatory Mandatory Optional Optional Mandatory Mandatory Optional Mandatory Kit/ Core Core Core Core Core Core Core Core Core
Telephon e No.
Optional
Core
The following fields related to address data infotype will be configured and delivered in Global Template: Address Type The Address Type identifies the different addresses that may be held on one employee record. The following address types will be configured: Subtypes 1 2 4 6 Address Types Primary Address Secondary Address Emergency Address Emergency Address 2 (CR_NA_2007_08-03) Requirements for NA (Quebec) Renamed the standard subtype 6 Nursing address, Remarks Main contact/ Permanent residence address Temporary or current address of stay
Version R 1.10
Page 47 of 124
Business Blueprint Document Subtypes Address Types Remarks instead of adding new subtype.
Version R 1.10
Page 48 of 124
6.2.6
Bank Details IT 0009
The Bank Details infotype is used to store the name of the banks and details of account to which the employee pay and other benefits are deposited/credited. This also stores Payment methods (direct deposits, check deposits, etc.). Payments can be distributed to several payees and/or accounts by creating an additional record for the additional payee/account and specifying the amount to be transferred as an absolute value or as a percentage. (This will be required for garnishments payments, etc.)
Figure: Snapshot screen of IT 0009 Global Data Elements The following fields related to IT 0009 will be configured as part of Global Template. Fields Bank Detail type Definition / Use / Possible entries Bank detail type 0 (primary bank details) is the employees primary bank details payments of wages or salaries. It can exist just once at any one time. The standard value and standard percentage fields are left empty for this bank detail type. We can enter payee name in this field We can enter city name. Optional/ Mandatory Mandatory Kit/Core Core
Payee Postal code City
Mandatory Mandatory Mandatory
Core Core Core
Version R 1.10
Page 49 of 124
Business Blueprint Document Fields Bank country Bank key Definition / Use / Possible entries This field identifies the country in which the bank is located In this field, we can specify the bank key under which bank data from the respective country is stored. This field contains the number under which the account is managed at the bank. We can enter the payment method (remittance to bank or cash payment etc.). The purpose is indicated on the bank transfer form. We can enter currency, in which payment is to be made. Optional/ Mandatory Mandatory Mandatory Kit/Core Core Core
Bank account number Payment method Purpose Payment currency
Mandatory
Core
Mandatory Optional Mandatory
Core Core Core
The following fields related to bank details infotype will be configured and delivered in Global Template: Bank Detail Type Subtype 0: Main bank for net Pay as well off-cycle pay Subtype 2: Travel expenses
Bank Key & Payment method Both will be based on the setup in local finance systems, and in lines with ISO standard. Employee Bank data will be interfaced with Employee mini master interface from Company Name to Company Name. After go live, Company Name becomes master for these data. After go live E-ERP, data will be interfaced from E-ERP to Company Name.
Version R 1.10
Page 50 of 124

Contracts Elements-0016
The Contract Elements infotype (0016), store data related to the employees employment contract.
Figure: Snapshot screen of IT 0016 Global Data Elements The following fields related to IT 0016 will be configured as part of Global Template. Field Contract type Work Permit Initial Entry Entry into Group Definition / Use / Possible entries The contract type classifies a contract of employment according to its intended validity period and legal status. For expatriates Day the work permit of a foreign employee expires. This will be the hiring date in the legal entity Same as Initial entry date. Will be different, if date of entry into Company Name groups is different from the legal entity in which the employee was hired. It is duration of probationary period Will be defined locally This field contains the unit that is the basis for the corresponding calculation Optional/ Mandatory Mandatory Kit/ Core Core
Optional Mandatory Mandatory
Core Core Core
Probationary period (number) Probationary period (unit)
Mandatory Mandatory
Core Core
The following fields related to address data infotype will be configured and delivered in Global Template: Contract Type
Version R 1.10
Page 51 of 124
Business Blueprint Document The following three contract types is being standardized at the global level Contract Types Contract Type 01 02 03 Description Permanent Temps Seasonal
Additional Requirements In addition to the above, SAP provided standards contracts can be added and adopted by zones/countries. Contract Types Contract Type 21 24 25 26 27 29 30 41 42 43 44 45 99 P1 P2 P3 P4 P5 P6 P7 W1 W2 W3 W4 W5 Description Unlimited Youth work scheme AR Trial period AR Part-time AR Employ.initiative AR Apprenticeship AR Set term AR Set period INCE placement Undergrad. Placement Postgrad. Placement School leaver plcmnt Hours Worked Full-time Part-time Consultant Casual/Temp On Commission Piece-worker Trainee Standard Contract Working Director External Director Contractor Student
Version R 1.10
Page 52 of 124
Contract Types Contract Type W6 W7 W8 W9 Description Part Time Casual Long Term Temporary External Contractor
If zones require other contract types then the global and SAP standard ones, same naming conventions have to be applied as for ESG.
Version R 1.10
Page 53 of 124
6.2.7
Monitoring of Tasks/Dates IT 0019
The Monitoring of Tasks infotype is provided so that you can monitor certain key dates related to employee life-cycle events that require actions by HR. This infotype enables you to keep track of dates in an employees career that need reminders and monitoring. Using this infotype, organization can hold event dates that can then be reported upon to provide a reminder list of forthcoming events requiring HR action. This is not a notifications, instead a report (available as SAP standard report) which provide a consolidated view of upcoming tasks/events as defined as setup below. The standard SAP report is S_PH0_4800450 Date Monitoring, under menu path Human resources Report Personnel Management Administration Employee
Figure: Snapshot screen of IT 0019 Global Data elements The following fields related to IT 0019 will be configured as part of Global Template. Field Task Type Definition / Use / Possible entries The Task Type field is used to define the HR related employee events of which the HR administrator wishes to be reminded. Date on which/ by which the Optional/ Mandatory Mandatory Kit/ Core Core
Date of Task
Mandatory
Core
Version R 1.10
Page 54 of 124
Business Blueprint Document Field Definition / Use / Possible entries task needs to be completed Processing indicator for monitoring of tasks Optional/ Mandatory Mandatory Kit/ Core
Processing Indicator
Reminder Date Lead/Followup time Comments
Date on which the reminder needs to be triggered Lead time To include any additional information that needs to be captured
Mandatory Optional Optional
Core Core Core
The following fields related to address data infotype will be configured and delivered in Global Template: Task Type Lead/Follow up time
Task Type The following task types will be configured in the Global template Task Types Contract end date Probation end date Salary continuance end date Retirement start date Leave return date Wage Change date Hourly Benefits eligibility date Work Permit expiry date End of Demotion Grandfathering End of Expatriation Date from which employee will be eligible for benefits Will be used for Expats employee working on work permits Will inform the end of grandfathering duration Reminder on expected date of Expats employee back to home country Comments End date for temporary/causal employees End date of probation after which employee has to be confirmed A day before employee will retire Date on which employee reports back from leave (This will include all type of leaves: Maternity, LTD, etc.)
Reminder Date defaults for Task Type: The following task types will be configured in the Global template
Version R 1.10
Page 55 of 124
Business Blueprint Document Lead/ Follow up time 4 Weeks in advance 4 weeks in advance To be defined by local 8 Weeks in advance 2 weeks before expiry of leave (For long term leave) To be defined by local On Probation confirmation 4 weeks before expiry of work permit 4 weeks before expiry of grandfathering 4 weeks before completion of assignment
Task Types Contract End date Probation End date Salary continuance End date Retirement Start Date Leave Return Date Wage Change date Hourly Benefits Eligible date Work Permit expiry date End of Demotion Grandfathering End of Expatriation
Additional Requirements Exit Interview details Usage of monitoring of tasks infotype for maintaining exit interview details This infotype will be used to capture exit interviews details. As on date, there is no SAP standard infotype available to store the exit interviews as required by Company Name. In future releases, the Global template team will look into enhancing this requirement as a standard for all zones.
Version R 1.10
Page 56 of 124
6.2.8
Family/Related Persons IT 0021
The Family Member/Dependents infotype records basic details of the employees family members as required for HR purposes. This infotype stores the data of an employees family members, other related persons, as well as emergency contact information.
Figure: Snapshot screen of IT 0021 Global Data elements The following fields related to IT 0021 will be configured as part of Global Template. Field Type of family Last name First name Gender Birth date Reference Personnel Number Definition / Use / Possible entries Each employees family members and other related persons will be referred by a unique subtype. We can store last name of family member We can store first name of family member We can store Birth date We can use this field to enter the testators personnel number for pension payments to surviving dependents or the reference number of a Optional/ Mandatory Mandatory Kit/ Core Kit
Kit Kit Kit Kit
Version R 1.10
Page 57 of 124
Business Blueprint Document Field Definition / Use / Possible entries family member to be used for storing additional data in the system. Optional/ Mandatory Kit/ Core
Telephone Number Separation Date SIN Legal Separation date This field enables you to enter the employees social insurance or tax number.
The following fields related to Family data infotype will be configuration and delivered in Global Template: Family Type The type of family record specifies the family member it regards. The record type is part of the sort term for family data. The following SAP sub-types will be adopted in Global template. Family Type Sub Type 1 3 5 7 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Description Spouse Legal guardian Guardian Emergency contact Divorced spouse Father Mother Domestic Partner Child of Domestic Partner Common Law Spouse Same Sex Spouse Fiance Estate Daughter Son Sister Brother Niece Nephew
Version R 1.10
Page 58 of 124
Family Type Sub Type 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46

6.2.9
Description Aunt Uncle Grandmother Grandfather Grandson Granddaughter Friend Cousin Sister in law Brother in law Father in law Mother in law Daughter in law Son in law Step mother Step father Step daughter Step son Step sister Step brother Trust PACS
Education IT 0022
The infotype 0022, store what education and training qualifications, an employee or an applicant has passed. Exceptions: Although this infotypes is part of Global data elements, it has been decided that Company Name will maintain and update the IT 0022 via ESS/MSS. Their will be no interfaces as of now from Company Name to Company Name to updated these data.
6.2.10
Previous Employment History - IT 0023
The infotype 0023 is used to store previous employment history of the employee.
Version R 1.10
Page 59 of 124
6.2.11
Cost Distribution - IT 0027
The infotype 0027, cost Distribution will be maintained to determine how costs for an employee are to be distributed to different account assignment objects.
Figure: Snapshot screen of IT 0027 Global Data elements The following fields related to IT 0027 will be configured as part of Global Template. Field Distribution type Co code Cost ctr Master Cost Centre Prcnt. Order WBS Element Name Name of Aux Acct Assignment Definition / Use / Possible entries Cost type that is distributed Company code of cost centre Cost centre the cost centre the cost of an employee are booked on before being distributed Percentage that employee is attributed to this cost centre Order Number Work Breakdown Structure Element Name of CO Account Assignment Name of Auxiliary Account Assignment Optional/ Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Kit/ Core
Version R 1.10
Page 60 of 124
6.2.12
Reference Personnel No. - IT 0032
Version R 1.10
Page 61 of 124
6.2.13
Corporate function Infotype IT 0034
The corporate function infotype will be used to store if the employee is enrolled in ESPP (Employee Share purchase plan).
Figure: Snapshot screen of IT 0034 Global Data elements The following fields related to IT 0034 will be configured as part of Global Template. Field Corporate Function Acquired on Definition / Use / Possible entries This is a subtype which will store the ESPP flag Date on which the corporate function begins. Optional/ Mandatory Mandatory Mandatory Kit/ Core
Subtype for ESPP A custom subtype 9000 ESPP will be created. For employees enrolled in the ESPP program this subtype will be maintained.
Insurance Infotype IT 0037
6.2.14
The insurance infotype will be used to store the employees insurance data in the Insurance infotype (0037).
Version R 1.10
Page 62 of 124
Figure: Snapshot screen of IT 0037 Global Data elements The following fields related to IT 0037 will be configured as part of Global Template. Field Insurance type Company Insurance number Insurance tariff. Amount Insured 1st different total 2nd different total Premium base Definition / Use / Possible entries The insurance type indicates which risks the insurance covers Insurance company key. The insurance number uniquely identifies the employee. Insurance rate Amount Insured Germany only Amount Insured Amount Insured Basis for percentage calculation of insurance premium. Optional/ Mandatory Mandatory Mandatory Mandatory Optional Mandatory Optional Optional Optional Kit/ Core
Insurance premium
Basis for percentage calculation of insurance premium.
Fully vested on
Vesting date for Germany only
Version R 1.10
Page 63 of 124
The following fields related to insurance infotype will be configured and delivered in Global Template: Insurance Type Each insurance type is stored as subtypes. The standard SAP system contains the following insurance types that will be adopted as part of Global template configuration. Insurance Type Descriptions Company Insurance Group Accident Insurance Life Insurance Supplementary Insurance Not Liable Risk Risk/Pension Nursing care Sick pay
Sub Type 0001 0002 0003 0005 0010 0011 0012 0020 0021
Version R 1.10
Page 64 of 124
6.2.15
Objects on Loan IT 0040
This infotype enables to track company-owned assets/equipment, such as a personal computer, mobile phones and other tools, loaned to an employee.
Figure: Snapshot screen of IT 0040 Global data elements The following fields related to IT 0040 will be configured as part of Global Template. Field Object on Loan Number/ Unit Loan Object No Comment Lines Definition / Use / Possible entries We can enter the key of the object the employee has borrowed from the company in this field. Number will be defaulted to 1 and Unit will be defaulted to Pieces This field will store the unique no. of the objects manufacture serial no. We can enter a user-defined comment text in this field. This entry is not checked by the system. Use this field for storing Model and manufacturer or any descriptions related to asset allocation. A maximum of 3 line comments Optional/ Mandatory Mandatory Kit/ Core Kit
Kit Kit Kit
Version R 1.10
Page 65 of 124
Business Blueprint Document Field Definition / Use / Possible entries can be added. Optional/ Mandatory Kit/ Core
The following fields related to objects on loan infotype will be configured and delivered in Global Template: Objects on Loan All object (assets) loaned to employee will be stores in Company Name.. List of Technology Assets The following list of assets objects will be maintained as part of global template. Asset List Descriptions Laptop/Notebooks Mobile phone Mobile email (Blackberry) Palmtops Printer - Inkjet Printer Laser Monitors Desktop/Tower PC Full Page Scanner Digital Cameras Disc Drives Printer/Scanner/Copier (All in one) Video Projection units Servers
Object ID 1 2 3 4 5 6 7 8 9 10 11 12 13 14
List of Other Assets The following are list of additional objects will be maintained as part of global template. Asset List Descriptions Home Network Drive Laptop bag Laptop Power Adapter Laptop Ergonomic Stand External Keyboard
Object ID 51 52 53 54 55
Version R 1.10
Page 66 of 124
Object ID 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70
Asset List Descriptions Mouse Memory stick Photo camera (assigned by department) Fixed Telephone Account Treo / Blackberry Smartphone Treo / Blackberry Charger Treo / Blackberry Leather Case Treo / Blackberry Ear set Mobile phone charger SIM-card Duo Sim-Card Calling card Books Badge Job Accessories (E.g. Clothing, shoes, etc)
Version R 1.10
Page 67 of 124
6.2.16
Date Specifications IT 0041
The Date Specifications infotype is used to hold dates significant to an employees terms and conditions, benefits and employment contract. Maintaining this infotype will help to have important dates maintained for an employee, and these dates will be view in one screen as shown below.
Figure: Snapshot screen of IT 0041 Global data elements The following fields related to IT 0041 will be configured along with the data as part of Global Template. Field Date Type Definition / Use / Possible entries The date types defines the meaning of a particular date, for e.g. Original hire date i.e. date of employee hired Date value Optional/ Mandatory Mandatory Kit/ Core Kit
Date
Mandatory
Kit
The following date types will be maintained as part of global template. (CR_NA_2007_08-01) Date Type code ZA ZB ZC ZD Date Types Original Hire date Position Start date Probation Start date Probation End date Comments Date of hiring Start date in the current positions
Version R 1.10
Page 68 of 124
Business Blueprint Document Date Type code ZE ZF ZG ZH ZI ZJ ZK Date Types Deceased date Service Seniority Retirement date Start of Expatriation End of Expatriation Termination date Last day worked Comments Employee deceased date Start date of the retirement Start date of expatriation in host country End date of expatriation and return to home country Use this date for end date of temporary contracts For some employees last day worked will be different from the termination or retirement date End date of expatriation and return to home country
ZI
End of Expatriation
Following Date Types will be updated via dynamic actions corresponding to a specific action. Original Hire Date ZA Probation Start Date ZC Deceased Date ZE Termination Date ZJ Last Day Worked ZK
All other Date Types will be maintained via PA30 by the end user manually. Additional Date types: In addition to the above date types defined and maintained global, the following additional requirements from zone (NA) can also be maintained. Date types code CA CB CC CD Comments Date Types Position End Union Seniority Contract start Contract end Date of hiring Start date for employees on temp. contracts End date for employees on temp. contract
Version R 1.10
Page 69 of 124
Business Blueprint Document Date types code CE CF CG CH CI CJ CK CL CM CN CO CP CQ Comments
Date Types Leave of absence start Leave of absence end Work Permit Expiry Date Benefit Eligibility date (Hourly) Salary Continuance Start date Salary continuance End Date STD Start Date STD End Date LTD Start Maternity Start Date Maternity End Date WCB Start Date WCB End Date
6.2.17
Membership fees IT 0057
Version R 1.10
Page 70 of 124
6.2.18
Additional Personal Data IT 0077
Infotype additional personal data (0077), stores personal information that is not stored in the other master data infotypes. This infotype contains information that is confidential, and should only be accessed by a select few employees.
Figure: Snapshot screen of IT 0077 Exceptions: The IT 0077 is country specific infotype and the data element for this infotype varies from country to country. This implies that the data elements maintained through infotype screen will be different for US, Canada, South Africa and other county grouping to which this infotype is attached.
Version R 1.10
Page 71 of 124
Business Blueprint Document Based on specific country requirements this infotype will be adopted or extended if not available for a particular country and needs to be maintained.
Maternity Protection-0080
6.2.19
The maternity protection infotype allows special processing types to calculate absences for maternity protection and parental leave.

Global data elements The following fields related to IT 0080 will be configured as part of Global Template. Field Pregnancy Notification Date Expected date of Delivery Definition / Use / Possible entries Date on which employer was notified of pregnancy In this field we can enter the presumed Date of Delivery. The System uses this date to calculate the anticipated absence for the employee. If the Actual Date of Delivery field contains an entry, calculations are based on this Optional/ Mandatory Mandatory Mandatory Kit/ Core Kit Kit
Version R 1.10
Page 72 of 124
Business Blueprint Document Field Definition / Use / Possible entries date instead. This was the actual date of delivery. If this is different from the expected delivery date, the absences may be recalculated. Optional/ Mandatory Optional Kit/ Core Kit
Actual date of Delivery
Type of Birth Date Officially Reported Sequence Number
Optional Optional The object identification (object ID) is used to make a distinction between data records with the same infotype, subtype, lock indicator, start date, and end date. The sequential number links the absence records you have entered on this screen. Attendance types are primarily used to document employees' work, and typically describe the type of activity. Mandatory
Kit Kit Kit
Att/abs. Type
Optional
Kit
Att/abs. Type Text Start End
Optional Start Date End date Optional Optional
Kit Kit Kit
Version R 1.10
Page 73 of 124
6.2.20
Communications IT 0105
This infotype enables you to record an employees various forms of communication contacts such as a cell phone, email address, etc.
Figure: Snapshot screen of IT 0105 Global Data elements The following fields related to IT 0105, which will be configured as part of Global Template. Field Type Definition / Use / Possible entries We can enter the type of communication that is required, such as the system user name for the R/3 System, For the communication type 0001, we can enter the employee's system user name. Enter the employee's SAP login user-id. This user-id will be used to setup user authorizations. Optional/ Mandatory Mandatory Kit/ Core Core
User ID/ Number
Mandatory
Core
The following fields related to Communications configured and delivered in Global Template: Communication Type
infotype
will
be
The following communication sub-types will be setup and maintained in Global template. Subtype 0001 0005 0010 0020 CELL Communication Subtypes Descriptions System User Name(SY-UNAME) Fax E-mail First telephone number at work Cell Phone
Version R 1.10
Page 74 of 124
6.2.21
Person IDs IT 0185
This infotype enables you to record employees personal details like Passport details, driving license details, etc. Employees drive Companys vehicle for the transportation of products. The need for this infotype is to record Drivers License related information for employees who drive the company vehicle. This information will be maintained as additional fields in infotype 0185 under subtype Drivers License.
Figure: Snapshot screen of IT 0185 Enhancement to IT0185: The infotype has been enhanced to include the following fields for the IC Type Driving License. Vehicle Class Driver Mention Special Condition License Follow-up Verification Date 1 Verification Date 2
Field Descriptions
Version R 1.10
Page 75 of 124
Business Blueprint Document The following are the fields related to IT 0185, which will be configured as part of Global Template. Field ID Type Definition / Use / Possible entries This will define the type of ID. Their will be one each for Passport, Driving license, Corporate Credit cards, etc. This will be managed by Subtypes. This is a custom field which will be used to store the vehicle class. This will be tied to a custom table which will store the values of code and descriptions for vehicle class This is a custom field to store the mention code (will be specific for NA Quebec) This will be another custom field to store if there are any special physical conditions on drivers license (e.g. need glasses to drive) which needs to be recorded. To store This will be used to store the issuing authority of the driving license Driving license no. License issues date License expiry date This field stores the date on which the employee's personal identification expires. The date on which the document expires must fall after the date that it is entered in the system. Optional/ Mandatory Mandatory Kit/ Core Kit
Vehicle Class
Mandatory
Kit
Mention Condition
Optional Optional
ID Number Author Issuing Number Date of issue Valid to Date of Expiry
Mandatory
Kit
Kit Kit Kit
Previous ID Number Place of Issue Country of
Previous ID Number Place of Issue of identification Country of Issue
Optional Optional Optional
Version R 1.10
Page 76 of 124
Business Blueprint Document Field Issue Country No Check License Follow up Verification Date 1 Verification Date 2 Exceptions The IT 0185 will be enhanced to include an additional field, namely Vehicle Class. This field is required to store the class of vehicle; namely mini vans, trucks, etc. Refer to Chapter 10 Global infotypes enhancements for more details on the enhancement. The following fields related to Communications infotype will be enhanced in IT 185, configured and delivered in Global Template: ID Type The following sub-types will be setup and maintained in Global template. Subtype DL Person IDs Subtype Descriptions Driving License Definition / Use / Possible entries Country of ID Indicator for overriding consistency check License Follow up Date Reminder Date Reminder Optional/ Mandatory Optional Optional Optional Optional Optional Kit/ Core
Vehicle Class (Custom Field) - Examples This custom field will be used to store the type of vehicles. Table below shows an example of vehicle class that will be maintained in the custom field. Class 1 2 3 4A 4B 4C 5 6A 6B 6C 6D Descriptions Heavy vehicles combination Bus Straight Truck Emergency vehicle Small Bus or Mini Bus Taxicab Passenger Vehicle All Motor Cycles Cylinder size of 400 cc or less Cylinder size of 125 cc or less Moped or Motorized Scooter
Version R 1.10
Page 77 of 124
Business Blueprint Document Class 8 Note: Each country can maintain there own set of codes for vehicle class. This will be setup in custom table details of which is covered in Chapter 10.1.6. Verification date-1 and Verification date-2 These two date fields will be enhanced in the infotype to store reminder dates when the driver license needs to be verified. This requirement wills arise, when the government asks to check the drivers license validity twice time during the validity period.
6.2.22 Company Car IT 0442
Descriptions Farm tracker
This infotype will enable to maintain employee company car information. The information on the infotype has been divided into the following categories: Car information (Only this data will be maintained as part of Global template) Price & Benefit & Additional information (valid only in Sweden)
Details maintained on this infotype provide the system with the information necessary to calculate employee contributions toward the company car and the corresponding tax implications, if any.
Version R 1.10
Page 78 of 124
Figure: Snapshot screen of IT 0442 Global data elements The following fields related to IT 0442 will be configured as part of Global Template. Field Vehicle class Definition / Use / Possible entries Type of class that determines the reason why the employee has the right to the company car Car manufacturers name (brand). Car model name license plate number The official registration date of the car Optional/ Mandatory Mandatory Kit/ Core Kit
Car Manufacturer Car Model License plate number Registration date
Kit Kit Kit Kit
The following fields related to Car infotype will be configured and delivered in Global Template: Vehicle Class Vehicle classification name Casual Car Company Car No company car (Change description to - Private Car)
6.2.23
Global ID - IT 0709
This infotype is used for employee who has more than one personnel assignment in the company to maintain Global ID. In SAP, each personnel assignment is uniquely identified in by the personnel number (PERNR). The Global ID will link all personnel numbers by assigning several personnel assignments to a central person (object CP).
Version R 1.10
Page 79 of 124
Figure: Snapshot screen of IT 0709 Global data elements The following fields related to IT 0709 will be configured as part of Global Template. Field Person ID Definition / Use / Possible entries Specifies a unique number for an employee. The central person is determined automatically by SAP by internal number assignment
6.2.24 Global Assignment Details IT 0710
Optional/ Mandatory Mandatory
Kit/ Core Core
This infotype will maintain details of Global assignments for Expats. This infotype enables to define the assignment characteristics and has three sections as described below: Future assignment details Assignment attributes Current assignment details
Version R 1.10
Page 80 of 124
Business Blueprint Document Figure: Snapshot screen of IT 0710 Global Data elements The following fields related to IT 0710 will be configured as part of Global Template. This has two sections: Field Type of assignment Start Date End Date Duration Definition / Use / Possible entries This will define the type of assignment, Short term, long term, etc. Start date of assignment End Date of assignment (Default Value) Duration of the assignment (months/ years) This will calculate the end date of the assignment Family Status - Specify whether the Expats family will accompany the employee If employee is moving on promotion or with no promotion Maintain the various personnel numbers used by the global employee during his assignment. This has option to store personnel no. in case required, one for home country and another for sending country. Refers to the group the employee of the international HR department in charge of the assignment process belongs to. (Default Value from Administrator Group) Refers to the employee of the international HR department in charge of the assignment process Optional/ Mandatory Mandatory Kit/ Core Kit
Optional
Kit
Mandatory
Kit
Family Status Promotion on Transfer Current assignment details
Mandatory Mandatory Optional
Kit Kit Kit
Administrato r Group
Mandatory
Internationa l HR Administrato r
Optional
Version R 1.10
Page 81 of 124
Business Blueprint Document Field Career Sponsor Definition / Use / Possible entries The career sponsor usually refers to the line manager, who normally acts as a contact person for the global employee during the assignment period. Enables you to specify the global employee's employment percentage during his/her assignment. You can enter a percentage between 0 and 100. The value of this field is retrieved upon activation by report Assignment Activation and stored in infotype Planned Working Time (0007) of the host country. Optional/ Mandatory Optional Kit/ Core
Capacity Utilization
Mandatory
The following fields related to Global assignment details infotype will be configured and delivered in Global Template: Type of assignment Type of assignment Short Term Assignment Long Term assignment Third Country National Remarks SAP Standard SAP Standard To be Customized for Company Name
Family Status Family Status Accompanying Unaccompanying Remarks SAP Standard SAP Standard
Promotion on Transfer Promotion on Transfer Promotion on Transfer No promotion on Transfer Remarks SAP Standard SAP Standard
Version R 1.10
Page 82 of 124
HCM Payroll administration & Time administration

Currently the payroll data administration and processing varies per country. In some countries only the payroll data (earnings and standard deductions) are maintained for employees in respective infotypes and send to third party fro payroll processing, while in some countries, the payroll is processed within (either in SAP or non-SAP). As part of the current release, the Global template design has standardized the payroll infotypes from data maintenance perspective. The following Payroll infotypes will be configured and maintained in SAP by Global Template. Global Infotypes - PY 0008 0014 0015 Descriptions Employee Basic Pay Recurring Payment Additional Payments
7.1
7.1.1
PY Infotypes in scope of Global Template

Basic Pay IT 0008
The Basic Pay infotype holds the employees contractual salary data. In certain zones/countries where the Payroll processing is outsourced, the employee payroll data will be interfaced with service providers application.
Version R 1.10
Page 83 of 124
Business Blueprint Document Global Data elements The following fields related to IT 0008, which will be configured as part of Global Template. Field Reason Pay Scale Type Pay Scale Area Pay Scale Group Pay Scale Level Capacity util. Level Wage Type Amount Number Unit Work hours/period Definition / Use / Possible entries The reason codes are used to document why changes to the basic pay were done. It defines the sector of industry which the collective agreement is valid. Manager reward categories Reference Market Category It defines Pay Grade of person Refinement within pay grade Actual working percentage Basic Pay reward Item Actual amount of basic pay reward item Number of units of Basic Pay reward Items Units of Basic Pay reward items This field shows how many hours the employee works in one payroll period. The default value is determined by the Planned Working Time infotype (0007). Optional/ Mandatory Optional Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Optional Optional Optional Kit/ Core Kit Core Core Core Core Core Core Core Core Core
Next Increase
If you want to assign an
additional pay scale level increase on the basis of age or seniority, enter the date on which the increase should take effect in this field. Evaluation programs give this date priority and delete it once the increase has been paid.
Optional
Annual Salary
Annual salary from an employee's basic pay.
Mandatory
Version R 1.10
Page 84 of 124
The following fields related to basic pay infotype will be configured and delivered in Global Template: Reason Code The reason codes on infotype 0008 will be used to document why changes to the basic pay were effected. The reason codes are an important basis for global reporting. If more then one reason is applicable at the same day, e.g. there is a collective increase and an employee changes role, please use the combined reason codes described below. The global reasons for basic pay to be adopted are: Reasons Codes for IT 0008 Descriptions Comments Others Promotion Contractual Change Change in working time Demotion End of Grandfathering Employee Retention Index + Annual increase Index increase Collective agreement Salary increase - Annual Salary increase - Adhoc Use only if none of the below reasons are applicable
Reason Codes 00 04 05 06 07 08 09 10 15 16 18 20
Use when both reasons are applicable on the same day Change due to comparison with the market reference All changes due to Collective Labor Agreement (CLA) Salary increase due to individual performance or merit
Pay Scale Type The following pay scale type will be configured and standardized as part of Global template. Zones will realign the existing pay scale type to one proposed as below:
Version R 1.10
Page 85 of 124
Business Blueprint Document Pay Scale type for IT 0008 Descriptions Remarks CEO CEO EBM All executive board members Top Executives Also referred to as Sr. executives Band I-III Managers Managers White Collar White Collar Blue Collar Blue Collar
Code 55 56 57 58 59 60
Zones cannot add any additional pay scale type locally from the one mentioned above. Pay Scale Group The following pay scale groups will be configured and standardized as part of Global template. All Pay scale groups for Executives (Band I to VII) need to be adopted by zones as proposed below: Pay Scale groups for IT 0008 Pay scale type Pay scale groups 55 CEO CEO 56 EBM EBM 57 Top Executives I-A I-B II-A II-B III-A III-B 58 Managers IV-A IV-B V-A V-B VI-A VI-B VII-A VII-B 59 White Collar 60 Blue Collar Exceptions:
Version R 1.10
Page 86 of 124
Business Blueprint Document Zones can define their own Pay Scale group only for White and Blue collared employees. However, the first 2 characters of zone to be included in the description when Pay Scale groups for Pay Scale types White collar & Blue collar are added. Pay Scale Area The following SAP standard pay scale area will be configured and delivered as part of Global template. Zones will realign the existing pay scale area to one proposed as below: Pay Scale areas for IT 0008 Code Descriptions 01 02 03 04 05 06 07 08 10 11 12 15 17 18 21 25 28 29 2T 30 31 33 36 37 41 58 BA BG CU FMCG Germany Not relevant Not relevant Spain The Netherlands France FMCG Canada Great Britain FMCG US Irelands Belgium Italy Venezuela Czech Republic Hungary Singapore China Top CNY Argentina china Top USD Luxembourg Slovakia Russia Ukraine FMCG Brazil General Market S.Kor Croatia Bosnia-Herzegovina Bulgaria Cuba
Version R 1.10
Page 87 of 124
Business Blueprint Document Pay Scale areas for IT 0008 Code Descriptions DO E1 E2 E3 EC GT PE RO UY YU Dominican Republic FMCG Europe FMCG UK FMCG Europe (USD) Equador Guatemala Peru Romania Uruguay Serbia and Montenger
Version R 1.10
Page 88 of 124
7.1.2
Recurring Payments IT 0014
The Recurring Payments/Deductions infotype holds wage types that are paid or deducted in every payroll period, or at regular intervals, for a defined period. This period will be a minimum of two payroll periods and is defined by a start and end date. In certain zones/countries where the Payroll processing is outsourced, the recurring payments data will be interfaced with service providers application.
Figure: Snapshot screen of IT 0014 Global Data elements The following fields related to IT 0014, which will be configured as part of Global Template. Field Wage Type Amount currency Ind.val. number Unit Reason for change Definition / Use / Possible entries Recurring payment reward item actual amount of recurring payment reward item Currency of the payment Indicates whether the amount is calculated automatically or not Number of units of Recurring Payment reward Items Units of Recurring Payment reward items Reason for change Optional/ Mandatory Mandatory Mandatory Mandatory Mandatory Optional Optional Mandatory Kit/ Core Kit Kit Kit Kit Kit Kit Kit
Version R 1.10
Page 89 of 124
Business Blueprint Document Field Payment Model Definition / Use / Possible entries The payment model defines a time pattern in which deductions are withdrawn and payments made. Optional/ Mandatory Optional Kit/ Core Kit
Assignment Number
Assignment Number
Optional
Reason for Code The reason codes on infotype 0014 will be used to document why changes to the recurring payments were effected. The global reasons to be adopted are:
Reason Codes 00 04 05 06 07 08 09 10 15 16 18 20 21
Reasons Codes for IT 0014 Descriptions Comments Others Promotion Contractual Change Change in working time Demotion End of Grandfathering Employee Retention Index + Annual increase Index increase Collective agreement Salary increase - Annual Salary increase - Adhoc Tax Directive Use only if none of the below reasons are applicable
Use when both reasons are applicable on the same day Change due to comparison with the market reference All changes due to Collective Labor Agreement (CLA) Salary increase due to individual performance or merit Deductions arising out of additional taxes
Version R 1.10
Page 90 of 124
7.1.3
Additional Payments/Deductions IT 0015
The Additional Payments infotype is used to hold ad hoc, one-off lump sum payments, for example, bonus payments. These payments will be interfaced to Payroll; therefore, values maintained here will be automatically paid to the employee.
Figure: Snapshot screen of IT 0015 Global Data elements The following fields related to IT 0015, which will be configured as part of Global Template. Field Wage Type Amount Number/ unit Date of origin Default date Reason for change Assignment Number Definition / Use / Possible entries Additional payment reward item Number of units of Additional Payment reward Items Units of Additional Payment reward items Date of payment Automatic calculated field Reason for change Assignment Number Optional/ Mandatory Mandatory Mandatory Optional Mandatory Optional Mandatory Optional Kit/ Core Kit Kit Kit Kit Kit Kit
Reason for Change - Codes The reason codes on infotype 0015 will be used to document why changes to the additional payment/deductions were effected. The global reasons to be adopted are:
Version R 1.10
Page 91 of 124
Reason Codes 00 04 05 06 07 08 09 10 15 16 18 20 21
Reasons Codes for IT 0015 Descriptions Comments Others Promotion Contractual Change Change in working time Demotion End of Grandfathering Employee Retention Index + Annual increase Index increase Collective agreement Salary increase - Annual Salary increase - Adhoc Tax Directive Use only if none of the below reasons are applicable
Use when both reasons are applicable on the same day Change due to comparison with the market reference All changes due to Collective Labor Agreement (CLA) Salary increase due to individual performance or merit Deductions arising out of additional taxes
Version R 1.10
Page 92 of 124
Setting up of Pay structure
Each pay grade (corresponding pay scale group in IT 8) will have the following data maintained. Minimum Salary Maximum Salary Mid market reference
All of the above will be setup in table T710.
Version R 1.10
Page 93 of 124
7.2
TIME Infotypes in scope of Global Template All Time related infotypes and components such as time types, work schedules, attendances, absences and quotas will be configured in Company Name. The configuration of these infotypes will be carried out by respective zones as time recoding and management will vary from country-to-country. However to enable time related KPI reporting, it is important that certain key time data configurations needs to be standardized. The Global template proposes the following standardization related to time infotypes. The following global time infotypes will be setup as part of Global template. Global Infotypes - TIME 0007
Descriptions Planned Working Time
Version R 1.10
Page 94 of 124
7.2.1
Planned Working Time 0007
The planned working infotype stores the work schedule rule information, time management status and also working time in hours daily, hourly, monthly and annually.
Figure: Snapshot screen of IT 0007 Global Data elements The following fields related to IT 0007, which will be configured as part of Global Template. Field Work schedule rule Time managemen t status Working week Employment percent Daily working hours Weekly working hours Monthly working hours Annual Definition / Use / Possible entries Determines which period work schedule is used to setup the work schedule This Indicator is assigned to employees who take part in time evaluation Defines sequence of days on a regular basis. Indicates percentage according to the work schedule. No of hours an employee must work per day Specifies the no of days the employee usually work per week Specifies the no of monthly working hours of an employee is to work. Average annual working time in hours Mandatory/ Optional Mandatory Mandatory Optional Mandatory Mandatory Mandatory Mandatory Mandatory
Version R 1.10
Page 95 of 124
Business Blueprint Document Field working hours Weekly workdays Min Max Definition / Use / Possible entries Mandatory/ Optional
Specifies the no of days the employee usually works per week. Allows creating min flexible work schedule rules for part-time employees. Allows creating max flexible work schedule rules for part-time employees.
7.2.2
Planned working times IT 0007
A work schedule consists of several different elements that can be combined much like building blocks in a variety of ways to form a complete work schedule. These elements can still be processed individually, offering flexibility and precision when you define and set up the time data relevant for your business requirements Daily work schedules: Daily Work Schedules are the smallest units of the work schedule. Daily work schedules contain the authorized working times and break times for a particular day. These times include fixed working times, flex-time, as well as daily work schedules for days off. The table below defines the standards to be adopted by zones to maintain daily work schedules by zones. Daily Work schedule XNNN Where X represents the type of shift, and will have one of the values: D M E N If it is a Daytime shift If it is a Morning shift If it is a Evening shift If it is a Night shift
NNN represents the sequential number Exceptions: For days off - define a work schedule code FREE to mark days off.
Version R 1.10
Page 96 of 124
Business Blueprint Document Period work schedules Each working time model contains a combination of both working days and days off (for example, Monday to Friday = work; Saturday and Sunday = days off). This pattern of working and non-working days repeats itself within a certain period of time (one week, for example), or repeats as rotating shifts within a particular number of weeks. This sequence of daily work schedules for particular working days and daily work schedules for days off is determined in the Period Work Schedule. The following is the proposal to define and maintain periodic work schedules by zones. Period Work schedule XXNN XX represents the 2 digit city code for which the shift is being defined. NN represents running number. In the description its suggested to provide details like number of hours For e.g. A 8 hour weekend shift in Leuven will be defined as LV01 Work Schedule Rules You specify in the work schedule rule which period work schedule is to be used when, and on which day of the period for the work schedule to be generated. In Company Name the period work schedule rules will be set up, using the following naming convention: Work schedule rules XXNN-Y XX represents the 2 digit city code for which the shift is being defined. NN represents the number of the period work schedule Y represents the week number of the work schedule rule. For 1-week schedules, Y will always be 1 so you will only have one version. For schedules that go over 1 week, you will have two versions of the work schedule rule: one with y = 1 and one with y = 2 (for 2 week schedules), etc.
Version R 1.10
Page 97 of 124
Time Management Status - IT 0007 The Time Management status to control whether and how employees are processed by time evaluation. The status has a fundamental significance for time evaluation. The following Time Management status is used to signify whether an employees time data is Evaluated by Time Evaluation Passed on to Payroll Processed only by Payroll The Time Management status is defined for each employees in the Planned Working Time infotype (0007). The following SAP standards flags will be used in Company Name: Time Management Status Time evaluation with planned times (0) Descriptions
Employees with this status are not selected for time evaluation, and cannot therefore be processed in time evaluation. The employees time wage types are determined in Payroll time data processing.
Time Evaluation PDC (2)
Employees with this status have all their actual times, that is, all attendance and absence data, recorded. It makes no difference whether attendance times are recorded at time recording terminals or in the Attendances infotype (2002).
Time evaluation with planned times (9)
These employees have only the deviations from their work schedule recorded for them. The employees planned working times from their personal work schedule are used as the basis for time evaluation.
Version R 1.10
Page 98 of 124

7.2.3 Public Holiday calendar
The public holiday calendar consists of all public holidays for a country or zone. When work schedules are created, they are linked to the Public Holiday Calendar. For that group of employees, the SAP system automatically knows when employees have a public holiday. The Public Holiday Calendar is linked to the combination of Personnel Area/Sub-area. The general rule for Company Name is to use the standard calendar ID. If there are holidays missing in the calendar IDs, they need to be added. The following is the proposal related to naming conventions for Public holiday calendars if more than 1 calendar ID is required for a country. Take the first digit from the standard calendar ID corresponding to country grouping (refer table below) Add the second digit from 0-9.
For e.g., If Canada needs two different holiday calendars, one for Ontario and other for BC, then define the same as C1 and C2 respectively.
Additional Configuration Elements

This section details the additional configurations that will be carried out at the Global template.
8.1
Organization objects maintenance Once the Organizational objects are setup in Company Name, this will require updates from time-to-time, in addition to creation of new objects. The maintenance will involve creating/deleting/modifying of objects, including relationships among the objects. As part of global template, the following OM object maintenance will be configured to create and update organizational elements: Note: The actions related to position change will be triggered from Personnel administration module. In PA, an action Change in position will be configured to change the position for an employee. Creation of Organization Units Creation of Position Creation of Job Delete Positions (Make position obsolete) Change description of objects Assign relationships among objects
Version R 1.10
Page 99 of 124
Business Blueprint Document 8.2 Employee Personnel Actions (PA Actions) A Personnel Action is used to transfer the employee's data into the SAP System. HR processes related to workforce administration, such as hiring an employee, organizational reassignment, employee transfers, etc., are represented and processed by customer-defined personnel actions in the SAP Personnel Administration module. Each personnel action contains a group of infotypes (known as Infogroup) that needs to be created and maintained to capture the data relevant to a particular process. Consequently, the infotypes will vary from one personnel action to another according to the requirements of that particular HR process. Executing a personnel action prompts the system to display these infotypes one after the other to ensure that all the core data relevant for this process is entered. When a personnel action is executed, a new action record is created in IT-0000, recording the type of action (HR process) that has been performed. Over time, this infotype builds a history of employee career events/milestones. Proposals for Infogroups: To each action, only the Global infotypes that are applicable for an action will be defined by the Global Template. Country specific infotypes will be defined and attached to the actions at the local country level. Each action will have a unique set of applicable action reasons assigned to it. The action reasons are one of the criteria for various reporting. Proposals for Infotypes Screens: Screen headers and infotype layouts are important to accurate and quick data entry while performing employee actions. The following are the guidelines related to screen modification for the infotypes in scope. Screen headers: SAP standard screen headers will be used across all rollouts. Screen layouts: The infotype fields which are mandatory will be set up to be used by all zones. The infotypes data fields not used during an employee action will be hidden.
Version R 1.10
Page 100 of 124
Set up Action Type & Reason codes for Personnel action The employee related actions type and action reasons has been standardized and signed off for all the processes in scope of Global Template. When creating an action the system will ask to enter a reason, explaining why this action is made on the employee. Once the action reasons are set up, its asked to never delete or change the reasons for actions, only add new ones if necessary. The table below lists the action type and action reasons that is standardized and will be defined and configured in SAP for the Global Template.
S. No. Process Name (As Per Process Maps) Action Type Emplo yment Status Action Reasons Comments
Employee Hire/ Rehire/Recall into System
Hiring - Regular Employees
Active
New Position Replacement Change Country (not Expat)
New hiring against a new position Hiring against existing vacant position Employee hired in other country returning back to home country First time hire Hiring for short term employment This will be the reason code for Initial data conversion to Company Name Temporary hiring for peak seasons and increasing work Hiring arising out of internal restructuring Expats being hired in the host country for first time
Temporary Employee Technical Hiring
CR_GT_2008_0 7_50Additional Global Action Reasons
Seasonal Peak
Internal Restructuring
Hiring Inpats Employee
Active
Expatriate receive from home
Version R 1.10
Page 101 of 124

Hiring - External Employees
Active
External Employee
Separate action for External Employees (Student trainees, Contractors, Survivors, etc.) These employees will not get any benefits from Company Name
Employee Hire/ Rehire/Recall into System Employee Hire/ Rehire/Recall into System
Hiring - External to Internal
Active
Hire External --> Internal
Hiring External employee as regular employee Re-hiring Ex Employees & Retirees (Voluntary Terminations) Recall Terminated employee (Involuntary terminations) Expats coming back to home country (Already have an Employee no. in home country) Employee hired in other country returning back to home country on his own. (Not coming back as expats) Use this if he has already has a Personnel No. Rehiring previously hired Seasonal/temporar y employee Temporary hiring for peak seasons
Reentry into Company
Active
Re-hire
Recall
Repatriate retrieve from host
Change Country (not Expat)
Temporary Employee CR_GT_2008_0 7_50Seasonal Peak
Version R 1.10
Page 102 of 124

Additional Global Action Reasons Internal Restructuring
and increasing work Hiring arising out of internal restructuring Employee changes to a position within the same level of responsibility Change Legal Entity, Employee Status (Not to be used for Expats) Domestic Physical work Relocation (within Zone/Country) Changes in work schedules Changes in work schedules Extension of existing Contracts - For Seasonal contracts Change in Job/ Position along with change in Rewards
Employee Transfers
Organization Reassignment
Active
Lateral Move
Change Legal Entity (No Expatriate) Local Transfers
Full time to Part time Part time to Full time Extension of Contract
Employee Change in Rewards with Promotion Employee Demotion
Active
Promotion
Active
Demotion Demotion Grandfathering Keeps the personnel grade while holding a lower position grade. Referred to as Red Circle in North America End of Grandfathering
Version R 1.10
Page 103 of 124

CR_GT_2008_0 7_50Additional Global Action Reasons
Active
Temporary Transfer Return to Base Location New collective agreement
Changes to employee organization data arising out of new collective agreement
Active Active
Extension of Probation In Transit Will be used when employee is in transition along with new employee for the period before he is promoted, transferred, terminated, etc.
Internal Restructuring 7 Employee Change in Rewards No Action Active Salary Increase Change in Rewards/Salary due to Merit/ Adhoc. Job re-grading (Band Changes) All this will be requiring changes to IT 8, their will not be any action type and action reasons for Employee data changes and will be handled by SAP transaction PA30 (based on authorization available for the
Version R 1.10
Page 104 of 124

user). Use the Reason filed to store the changes
Employee Data changes
No Action
Active
Their will not be any action type and action reasons for Employee data changes and will be handled by SAP transaction PA30 (based on authorization available for the user) Probation Completion Excellent Performance
Probationary confirmation
Probationary confirmation
Active
Confirmation before completion of Probation period Approved Long term leave with no Benefits, and as well not counted in Head count reports Approved Long term leave with Company Benefits. This will be also used for Banked vacation (Quebec Canada)
10
Employee Leave Unplanned
Long Term Absence
Inacti ve
Approved Leave - No Benefits
Approved Leave - with Benefits
Version R 1.10
Page 105 of 124

Not attending office
Under Severance Pay
No Information available from Employee Inactive and Payroll suspended till further notice Employee under severance pay. Will be terminated or retired after severance pay period No Benefits to survivors
11
Termination Death
Termination Voluntary
Withdr awn
Withdr awn
Employee Deceased Survivor Deceased Retiree employee deceased Resignation (Restructuring) Resignation (General) Resignation (Salary) Resignation (Culture) Resignation (Lack of career development) Mutual Agreement Resignation (Leadership support) Expatriate Sending to host
Repatriate return to home Resignation (Restructuring)
Termination in the home country (for countries which does not provide any benefits to employee in home country) Termination in the host country
Version R 1.10
Page 106 of 124

12
Termination Involuntary
Termination Involuntary
Withdr awn
Poor performance Redundancy
Position Obsolete End of Contract Dismissal Outsourcing Mutual Agreement Layoffs Substitution
Positions/Jobs made redundant as part of Organization restructuring Decided not to fill the open position any more Terminated on end of contract period
Terminated in consent with Employee Mass terminations Terminated as Employee was substituting for other employee who has returned back Early retirement with Benefits Normal Retirement with Benefits
13
Termination Retirement
Retirement
Retire d
Early Retirement Regular Retirement Retirement with no Benefits Retiree Survivor assumes Benefits
Regular Survivor assumes Benefits
This will be used for Pensioner Survivor assumes benefits. When the survivor deceased, use termination voluntary to terminate the survivor. This will be used for Regular employee survivor assumes benefits. If the benefits are for limited period,
Version R 1.10
Page 107 of 124

then set the date specification for end date. 18 Termination Retirement (CR_NA_2008_ 01_02) Survivor Retiree Deceased (Introduced new action) Retire d Survivor assumes benefits Use this action, if the Survivor assumes benefits once the retiree is deceased. Note: In addition to new action, the SAP standard feature MSN-31 modified to allow multiple actions on employee with status Retired.
8.3
Defining and configuring Infogroups An infogroup is the group of infotypes that will be displayed sequentially for each Personnel Action. A generic infogroup must be defined for each Action Type, exceptions can then be defined by Action Reason, or even by Personnel Structure eg. Employee Group, Employee Subgroup, Personnel Area or Personnel SubArea. Each infotype within the infogroup is assigned an Operation; this defines which editing mode should be used to process the infotype in an action e.g. Create, Copy, Change and Delimit or updated through interface. Note: Revised inforgroups for corresponding actions based on the SIT/UAT feedback.
Hiring Action - Regular employees Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0009
Organizational Assignment Personal Data Addresses Bank Details 1,2,4 0, 2 Primary Address, Secondary Address, Emergency Address, Primary bank for
Create Create Create Create
Version R 1.10
Page 108 of 124
Hiring Action - Regular employees Info Types Info Types Description Sub Type Subtype Description Operation Mode
Salary Secondary bank for travel expenses 0016 0019 0041 0105 0185 0008 0034 Contract Element Monitoring of Task Date Specification Communication Personal IDs Basic Pay Corporate Function Create Create Create 9001 DL Legacy employee no. Drivers license Only for Employee group 2Blue collared employees Create Create Create 9002 INSS
Note: IT 0185 Subtype DL cannot be maintained through PA40

Hiring Action Inpats employees Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006
Organizational Assignment Personal data Addresses 1,2,4 Primary Address, Secondary Address, Emergency Address, Primary bank for Salary Secondary bank for travel expenses
Create Create Create
0009 0016 0019 0041 0185 0710 0008
Bank Details Contract Element Monitoring of Task Date Specification Personal IDs Global Assignment Details Basic pay
0, 2
Create Create Create Create Create Create Create
Version R 1.10
Page 109 of 124

Hiring Action Inpats employees Info Types Info Types Description Sub Type Subtype Description Operation Mode
0034
Corporate Function
9002
INSS
Hiring Action External Employees Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0009 0016 0019 0041 0008 0034
Organizational Assignment Personal Data Addresses Bank Detail Contract Elements Monitoring of tasks Date Specification Basic pay Corporate Function 1,2,4 0 Primary Address, Secondary Address, Emergency Address
Create Create Create Create Create Create Create Create 9002 INSS
Hiring Action External to Internal Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0009 0016 0019 0041 0008 0034
Organizational Assignment Personal Data Addresses Bank Details Contract Element Monitoring of Task Date Specification Basic pay Corporate 1,2,4 0 Primary Address, Secondary Address, Emergency Address
Copy Copy Copy Copy Create Create Change 9002 Create INSS
Version R 1.10
Page 110 of 124
Business Blueprint Document Function

Rehire Action - Re-entry into Company Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0009 0016 0019 0041 0008 0034
Organizational Assignment Personal Data Addresses Bank Details Contract Element Monitoring of Task Date Specification Basic pay Corporate Function 1,2,4 0 Primary Address, Secondary Address, Emergency Address
Create Copy Copy Copy Copy Copy Copy Create 9002 INSS
Action : Transfers (Domestic) /Demotion/ Promotion Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0016 0019 0041 0008 0034
Organizational Assignment Personal Data Addresses Contract Element Monitoring of Task Date Specification Basic pay Corporate Function 1,2,4 Primary Address, Secondary Address, Emergency Address
Copy Display Copy Copy Create Change Copy 9002 INSS
Action : Probationary Confirmation Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0016
Organizational Assignment Personal Data Contract Element
Copy Display Copy
Version R 1.10
Page 111 of 124
0041 0008 0034
Date Specification Basic pay Corporate Function
Change Copy 9002 INSS
Action Long Term Absence Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0019 0041 2001 0008 0034
Organizational Assignment Personal Data Addresses Monitoring of Task Date Specification Absence Basic pay Corporate Function
Copy 4 Emergency Address, Display Copy Create Change Create Copy 9002 INSS
Action Medical Leave Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0019 0041 0080 2001 0008 0034
Organizational Assignment Personal Data Addresses Monitoring of Task Date Specification Maternity Protection Absence Basic pay Corporate Function
Copy 4 Emergency Address, Display Copy Create Change Create Create Copy 9002 INSS
Action Leave of Absence Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002
Organizational Assignment Personal Data
Copy Display
Version R 1.10
Page 112 of 124
0006 2001 0008 0034
Addresses Absence Basic pay Corporate Function
Emergency Address
Copy Create Copy INSS
9002
Action Return from Long Term Absence Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0041 2001 0008 0034
Organizational Assignment Personal Data Date Specification Absence Basic pay Corporate Function
Copy Display Change Change Copy 9002 INSS
Action Return from Medical Leave Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0019 0041 0080 2001 0008 0034
Organizational Assignment Personal Data Monitoring of Task Date Specification Maternity Protection Absence Basic pay Corporate Function
Copy Display Create Change Change Change Copy 9002 INSS
Action: Termination Voluntary Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0009
Organizational Assignment Personal Data Address Bank Details
Copy Display Copy Copy
1 0
Version R 1.10
Page 113 of 124

Action: Termination Voluntary Info Types Info Types Description Sub Type Subtype Description Operation Mode
0014 0016 0019 0040 0041 0442 0008 0034
Recurring Payments / Deduction Contract Elements Monitoring of Task Object on Loan Date Specification Company Car Basic pay Corporate Function
Delimit Copy Copy Delimit Change Delimit Copy 9002 INSS
Action: Termination Involuntary Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0009 0014 0016 0019 0040 0041 0442 0008 0034
Organizational Assignment Personal Data Address Bank Details Recurring Payments / Deduction Contract Element Monitoring of Task Object on Loan Date Specification Company Car Basic pay Corporate Function
Copy Display Copy Copy Delimit Copy Copy Delimit Change Delimit Copy 9002 INSS
1 0
Version R 1.10
Page 114 of 124

Action: Retirement Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0009 0014 0016 0019 0040 0041 0442 0034 0008 0034
Organizational Assignment Personal Data Addresses Bank Details Recurring Payments / Deduction Contract Elements Monitoring of Task Object on Loan Date Specification Company Car Corporate Function Basic pay Corporate Function
Copy Display Copy Copy Delimit Copy Copy Delimit Change Delimit INSS Copy 9002 INSS
1 0
9002
Action: Survivor-Retiree Deceased (CR_NA_2008_01_02) Info Types Info Types Description Sub Type Subtype Description Operation Mode
0001 0002 0006 0009 0014 0016 0019 0040 0041 0442
Organizational Assignment Personal Data Addresses Bank Details Recurring Payments / Deduction Contract Elements Monitoring of Task Object on Loan Date Specification Company Car
Copy Display Copy Copy Delimit Copy Copy Delimit Change Delimit
1 0
Version R 1.10
Page 115 of 124

Action: Survivor-Retiree Deceased (CR_NA_2008_01_02) Info Types Info Types Description Sub Type Subtype Description Operation Mode
0034 0008 0034
Corporate Function Basic pay Corporate Function
9002
INSS Copy
9002
INSS
8.4
Employee ID (Personnel Nos & Global ID) Company Name has employees working as Expats at different zones/countries. The Expatriates are mostly Executives (Band I to VII) and are transferred based on their assignments and managed globally by GHQ. The need is to have a common ID for the Expatriate employee, linking current and past data while working in respective zones/countries. Currently in Company Name, a Global-ID is generated every time an employee is hired first time in the System. The country specific employee number assigned by country HR applications is stored as a reference number in Company Name. In addition, Company Name being a SAP system creates a running Employee No. called Personnel No. (referred to as PERNR in SAP).
8.4.1 Key Principles for Employee Personnel No. and Global ID
The following are the key principles for defining and standardizing Employee Number and Global ID for Company Name: Company Name will be the master for Employee for countries live in Company Name. Company Name will be the master for Global ID for employees in Company Name. Company Name to adopt the Company Name numbers, both for Employee number (PERNR) and Global ID, as Company Name is rolled out to each country.
Proposals for Employee Personnel No. and Global ID
8.4.2
Based on the discussions and agreements, the following is the proposal for Employee number and Global ID: Each country will have a separate employee number ranges (PERNR). The country specific employee no. range (PERNR) will be maintained and internally generated in Company Name. A unique Global ID will be maintained and internally generated in Company Name. Company Name to re-configure the system to accept External PERNR Nos. for country going live in Company Name
Version R 1.10
Page 116 of 124
Company Name to have one time effort to clone new Company Name PERNR and Global ID, every time a country rolls out
Version R 1.10
Page 117 of 124
8.4.3
Maintain Number ranges for Employee Personnel Nos.
It is proposed for all the countries to have an 8 digit employee number ranges. The following are the proposed number range(s) defined (Internal number assignment) for Employee Personnel number: Sl No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Proposals: North America has peripheral systems, which stores only 6-digit employee numbers. To meet the NA requirements (there may be similar requirements for other countries in future), only the last 6 digits will be extracted and interfaced back to legacy applications. If possible, the current legacy numbers will be adopted Company Name for initial data migration of employees into Company Name. Country Name USA Canada Bulgaria Croatia Czech Hungary Montenegro Romania Russia Serbia Ukraine Brazil Dominican Rep. Ecuador Guatemala Peru Venezuela Argentina Bolivia Chile Paraguay Uruguay Belgium & Global HQ Luxembourg France Germany Italy Netherlands UK Ireland Number range Assigned 105xxxxx to 105xxxxx 07xxxxxx to 07xxxxxx 88xxxxxx to 88xxxxxx 58xxxxxx to 58xxxxxx 18xxxxxx to 18xxxxxx 21xxxxxx to 21xxxxxx 89xxxxxx to 89xxxxxx 61xxxxxx to 61xxxxxx 33xxxxxx to 33xxxxxx 98xxxxxx to 98xxxxxx 36xxxxxx to 36xxxxxx 37xxxxxx to 37xxxxxx 97xxxxxx to 97xxxxxx 96xxxxxx to 96xxxxxx 95xxxxxx to 95xxxxxx 94xxxxxx to 94xxxxxx 17xxxxxx to 17xxxxxx 29xxxxxx to 29xxxxxx 93xxxxxx to 93xxxxxx 39xxxxxx to 39xxxxxx 90xxxxxx to 90xxxxxx 91xxxxxx to 91xxxxxx 12xxxxxx to 12xxxxxx 30xxxxxx to 30xxxxxx 06xxxxxx to 06xxxxxx 01xxxxxx to 01xxxxxx 15xxxxxx to 15xxxxxx 05xxxxxx to 05xxxxxx 08xxxxxx to 08xxxxxx 11xxxxxx to 11xxxxxx
Version R 1.10
Page 118 of 124
Business Blueprint Document The legacy number will be prefixed by two digit country code defined in the above table. For e.g. if the existing employee number is 1234 for US, then during initial upload the number will be uploaded as 10001234. (where first 2 digit 10 is US country code) During initial data migration, the employee number range will be set to external. At go-live the employee number range will be set to internal with next available number starting the number range.
Exceptions: For NA, (both Canada and US) use a common downstream applications and will only interface the last 6 digits number from SAP. After go live, to be able to keep unique numbering for USA and Canada, US will have further segregation on number range starting as mentioned in the table above.
8.4.4
Maintain Number ranges for Employee Global ID:
The following are the number range(s) defined (Internal number assignment) for Employee Personnel ID (Global ID): S. No. 1 8.5 Number range Assigned 10000000 to 49999999 Dynamic Actions Dynamic actions trigger automatic processing when infotypes are maintained. Whenever a change is carried out to the personnel data for a given infotype, a change needs to be effected on the data of a second infotype. This change can be automated by way of dynamic actions, whereby the system automatically displays the second infotype on changes to the first infotype. These dynamic actions are started automatically by the system, unlike the Personnel Actions which is initiated by the users. The details of the dynamic actions configured are provided herewith: (Based on SIT issue log) Action ZB Hiring Inpat in 0041 - (Original Hire date removed ), Probation start date defaulted Action ZD Hiring External to Internal - in 0041 - (Original Hire date - removed ), Probation start date defaulted Action Ze Reentry - in 0041 - (Original Hire date removed ), Probation start date defaulted Only for Reentry , the operation for 0041 Is Copy
Version R 1.10
Page 119 of 124
Business Blueprint Document And for other actions, like Hiring Inpat, Hiring External to Internal - the operation for 0041 is Mod
Global Configuration Elements

This section details the various configurations and the corresponding data that will be configured, maintained and supported by the Global Template team. The following is the list of global data elements that will be configured and maintained by the Global Template. For some of these data elements the values will be provided by local zones/countries, but will be configured and maintained by Global template.
Global Template Configurable Items Bronze Package Define Company Define Company Code Assigning Company Code to Company Maintain Personnel Areas Maintain Personnel Sub Areas Maintain Employee Group Maintain Employee Sub Group Assignment of Personnel Area to Company code Assign Employee subgroup to Employee group Maintain Number Ranges Org. units, Jobs and Positions Maintain User Parameters Maintain number range intervals for Personnel numbers (PERNR) Determine defaults for number ranges Maintain Forms of Address Create Name affixes Maintain titles Create Marital status Future maintenance: Global Vs Local Global Global Global Global Global Global Global (Local to provide data) Global Global Global Global (Local to provide data) Global Global Global Global Global Global
S. No 1 2 3 4 5 6 7 8 9 10
Activities/Remarks Will be extracted and uploaded from Company Name Will be extracted and uploaded from Company Name Will be extracted and uploaded from Company Name Will be extracted and uploaded from Company Name Will be extracted and uploaded from Company Name Global Configuration Country specific (Local) configuration will be provided to Global for configuration Will be extracted and uploaded from Company Name Global Configuration Country specific ranges will be defined for each country. The no. ranges will be Internal. Maintaining & defining user profile is part of global but extending the user profile roles and attaching to user is local Global Configuration Global Configuration Global Configuration SAP standard SAP standard SAP standard
11
12 13 14 15 16 17
Version R 1.10
Page 120 of 124

Future maintenance: Global Vs Local Global Global Global Global (Local to provide data) Global (Local to provide data) Global (Local to provide data) Global (Local to provide data) Global (Local to provide data) Global (Local to provide data) Global Global Global Global (Local to provide data) Global (Local to provide data) Global (Local to provide data) Global (Local to provide data) Global (Local to provide data) Global Global Global Global
S. No 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
Global Template Configurable Items Bronze Package Define Family types Create Address Types Maintain Communication types Define Payment method Determine Default Payment Method Define International terms of employment Create Payroll Area Define Payroll Groups Check Default Payroll Area Define Organizational Units Define Jobs Define Administrator Groups Define Administrator Contract Elements Determine Periods of Notice Determine Default Contract elements Define Objects on Loan Infotype Menu Determine choice of infotype menus. Define Infogroups - Only for Global Infotypes Set up Personnel actions Global Processes
Activities/Remarks SAP standard SAP standard SAP standard SAP Standard & Global Configuration Global Configuration Global Configuration Country specific (Local) configuration Global Configuration Country specific (Local) configuration SAP standard To receive extract from Company Name and update as part of Global Template To be discussed later Global Configuration & Local Configuration Country specific (Local) configuration Country specific (Local) configuration Country specific (Local) configuration Country specific (Local) configuration SAP standard SAP standard Global Configuration Global Configuration
Version R 1.10
Page 121 of 124

Future maintenance: Global Vs Local Global Global Global (Local to provide data) Global Global (Local to provide data) Global Global
S. No 39 40 41 42 43 44 45
Global Template Configurable Items Bronze Package Create Reasons for personnel actions Change action menu - User group dependency of the action menu Change action menu Action Menu Person ID Language Notification Object & Relationship
Activities/Remarks Global Configuration Global Configuration Global Configuration + Country specific (Local) configuration Global Configuration Maintained in English as well country specific (Local ) languages as required Global Configuration Global Configuration Only Global roles/authorizations will be part of the Global Template. Country specific roles/authorizations will be provided to Global for configuration
46
User Roles & Authorizations
Global (Local to provide data)
Version R 1.10
Page 122 of 124
10 Glossary of Terms
Terms Personnel Number Descriptions The employee number that identifies a set of records belonging to one contract record within SAP For Company Name, this will mean the employee that relate to an employees assignment in each country. For example, an employee hired in Canada from Belgium, would have a Canada personnel assignment number and a Belgium personnel number. This number can be viewed on the header data of all infotypes Global ID (Referred to also as Person ID) Person Id is an employees unique number on SAP. An employee can have many personnel numbers as explained above, but only one Person id. This number is automatically created when an Employee is initially hired onto SAP and will be based on their first personnel assignment number. Customer Specific Status This field on the Actions infotype (0000) is provided for customers to use as they please. For Company Name it will be used to indicate where the employees personnel assignment record is currently. All employees will have a valid Customer Status record. Employment Status This field on the Actions infotype (0000) is used throughout SAP to determine whether an employee is currently within the firm or not. All employees will have a valid Employment Status record. Personnel Action Personnel Actions record career events (hiring, transfer, promotion etc.) and present a series of infotypes requiring maintenance to update the effected employee data. It stores the Subset of a type of information. For example, Permanent Residence is a type of
Subtype
Version R 1.10
Page 123 of 124
Business Blueprint Document Terms Descriptions address within SAP. Infotypes grouped together in a sequence in which it needs to be accessed and updated for a particular action Zero Based Budgeting Business Configuration Sets Wage Types are used to make a distinction between different amounts of money or time units that are included in various ways in the calculation of employee remuneration package. E.g., their will be a wage type for each contractual component of employee remuneration.
Infogroups ZBB BC Sets Wage Types
Version R 1.10
Page 124 of 124

BBP

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BBP

Caricato da

Copyright:

Formati disponibili

Global Template SAP Business Blueprint Document

Current Version: Business Owner: Version Release 1.10

Author: Approved By:

SAP Business Blueprint Document Global Template

Business Blueprint Document

SAP Business Blueprint Document Global Template

Business Blueprint Document

Executive Summary SAP Blueprint

SAP Business Blueprint Document Global Template

SAP Business Blueprint Document Global Template

Business Blueprint Document

Company Name Project Background

Global Template Process scope

Process No. ORG_001 ORG_002

SAP Business Blueprint Document Global Template

Business Blueprint Document

ORG_003 ORG_004 ORG_005

SAP Business Blueprint Document Global Template

Business Blueprint Document

Data Changes Employee Personnel Data Change in Rewards Merit/Adhoc

SAP Business Blueprint Document Global Template

Business Blueprint Document

Figure: Data validity period

SAP Business Blueprint Document Global Template

Business Blueprint Document

Global Infotypes OM 1000 1001 1003 1007

Descriptions Organization Objects Object Relationships Department/Staff Vacancy infotype

Global Infotypes PA 0000 0001 0002 0004 Actions

Organizational Assignments Employee Personnel Data Challenge

SAP Business Blueprint Document Global Template

Business Blueprint Document

Global Infotypes PY 0008 0014 0015

Descriptions Employee Basic Pay Recurring Payment Additional Payments

Global Infotypes TIME 0007 2001

Descriptions Planned Working Time Absence

SAP Business Blueprint Document Global Template

Business Blueprint Document

2002 2006 2007 2013

Attendance Absence Quota Attendance Quota Quota Corrections

SAP Business Blueprint Document Global Template

Business Blueprint Document

HCM Strategic Elements Organization Management

Setting up of Organization structure for Company Name

SAP Business Blueprint Document Global Template

Business Blueprint Document

SAP Business Blueprint Document Global Template

Figure: snapshot showing employee holding multiple positions in OM

SAP Business Blueprint Document Global Template

Business Blueprint Document

Number ranges for OM Objects

Naming conventions for Organization objects

SAP Business Blueprint Document Global Template

Business Blueprint Document

SAP Business Blueprint Document Global Template

Business Blueprint Document

Organization Management Data Model Object

Figure: SAP OM Objects & relationships in Company Name

SAP Business Blueprint Document Global Template

Business Blueprint Document

SAP Business Blueprint Document Global Template

Business Blueprint Document

HCM Strategic Elements Personnel Administration