Implementation
Implementation
Process will start from Set up Project Board members not from Sales and Marketing
(Sales and Marketing which comes under Non-SAP)
The ASAP Road map was developed by SAP to help customers implement SAP software
in a quick, cost-effective manner.
The Change Team will identify the gaps between the package and the business
requirements, re-engineer some of the businesses process to cope with the package, train
the users to ensure implementation is smooth as possible into the business.
The Technical Team will prepare the systems environment for the package, apply any
software fixes from the vendor, implement the software in the best way possible for the
organization set up and tune the software for the particular technical environment.
GAP Analysis
A through gap analysis will identify the gaps between how the business operates ad its
needs against what the package can can't do. For each gap there will be one of three
outcomes which must be recorded and actioned, GAP must be closed and customized
software can be developed close the gap, GAP must be closed but software cannot be
written therefore a workaround is required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap
analysis is the study of the differences between two different information systems or
applications ( ex; existing system or legacy system with Client and new is SAP), often for
the purpose of determining how to get from one state to a new state. A gap is sometimes
spoken of as "the space between where we are and where we want to be." Gap analysis is
undertaken as a means of bridging that space. Actual gap analysis is time consuming and
it plays vital role in blue print stage.
Train Users
Well trained users will support and defend the system on site. Unsupportive users will
continually undermine the system and eventually it will be replaced. Therefore the more
effort you put into helping the users master the system early the better.
And a look at Activities and Deliverable in Phase I - Project Preparation Key
Key Activities Deliverables
Finalize Project Team Organization Project Team Structure Organization Chart
Finalize Project Team Training Plan Project Team Training Schedule
Define Team Facilities Requirements Project Team Seating Chart (including
required equipment)
Develop Project Plans Baseline Project Plans
Initial Activities Planned
Resource Plan
Develop Project Strategies and Scope Draft:
Implementation Strategy
End-User Training Strategy
Development Strategies
Testing Strategy
Technical Strategies
Security and Controls Strategy
Review Existing Implementations High-level Project Scope Document
List of Lessons Learned
Define Project Management Standards Project Management Standards and
and Procedures Procedures (Issue Mgt Plan, Status Report
Format, Change Control Forms,
Documentation standards, etc,)
Develop Benefits Realization Strategy Benefits Realization Approach
Develop Project Risk Assessment Risk Management Plan, Report and
recommendations to mitigate project risks,
and summary of Critical Success Factors
Define Post-Implementation Support Post-Implementation Support Approach
Perform Technical Requirements Complete Technical Questionnaires
Gathering Define Technical Infrastructure Needs
Procure Hardware Size Initial Hardware
Approve Sizing Results
Order Initial Hardware and Software
Order Remote Network Connection
Define System Landscape Strategy System Landscape Strategy
Define Project Methodologies, Tools and Established Project Methodologies, Tools
Project Governance Standards and Governance Standards
Define Quality Assurance Plan Quality Assurance Plan
Develop Communication Strategy and Communication Plan/Strategy
Plan
Confirm Process, Organization and Sign-off by Customer
Technical Scope
Develop and perform Change Readiness Change Readiness Assessment Results
Assessment and Report
Produce and Deliver Program Completed Status Report
Management Status Reports Updated Issues Log
Prepare for Project Kickoff Kickoff Meeting
Phase II: Business Blueprint
Business Blueprint Key Activities and Deliverables
Sub-Modules of HR:
1. Personal Administrations
2. Organizational Management
3. Time Management
4. Payroll Management
And other Sub-modules like Benefits, Personal Development, ESS, Recruitment's, CATS...
Functional Consultants will contract Clients Core- team and will gather all the requirements
and starts mapping to SAP. This is called AS - IS, TO - BE.
As- is
Functional consultant involves understanding the complete functionality of the system. It
involves detailed understanding of how the HR department is functioning because based
on that only you would provide a solution to them.
Like suppose you are implementing SAP HR module for them then in the AS-IS and TO-
BE phase, you need to prepare all the documents of the process flow (you can prepare
them in word).
Like suppose you are implementing for PA then you need to identify how many personnel
areas you need to make, how many subareas you will make, employee groups,
subgroups, based on what you are classifying them? This all will come in the master data
document which has to be approved from the client whoever he is.
Like if the current system is on mainframe or for some specific applications like for
recruitment the system is on mainframes and the client wants to keep that system as well
then interfaces need to be identified which will be there because you will have to upload
the data to sap system using bdc.
- Hiring
- Newly Hire
- Termination
- Transfer
- Layoff etc
You will have to see what all actions your client wants, like if there is an action transfer
which is run for employee what all will be the reasons you will be configuring for that
action. This will be told by the client which can come out after a series of meetings and
after discussions you will have to come out with the document that these will be action
types. These will be the action reasons, these will be the action codes for that. This will be
in the TO BE process document.
Symptoms: You are the implementation Project Manager for a consulting firm and you
have a client that just selected an ERP system. You (the project manager) and your team
start gathering requirements from end users through focus groups, workshops, sessions
with SMEs, etc. After gathering information from end users you erroneously conclude that
you have all the necessary information and requirements to successfully implement the “to
be” software system. Since you believe you understand the “to be” system you neglect to
document the “as is” system.
During UAT (User’s Acceptance Testing) you find out that the system does not meet end
user’s expectations and the UAT participants cannot validate your implemented solution.
Your client is dissatisfied with the proposed solution, and you are now challenged to prove
that your implemented ERP solution is consistent with the client’s business needs, and
requirements. Given clients’ complaints you are put in a position where you cannot explain
how the proposed ERP solution meets or exceeds previous system functionality. The
question now becomes how does the ERP system meet replaced system functionality if at
all?
Suggestions: Determine if there are any existing documents in the form of functional
specs, architecture diagrams, requirements or flow process diagrams that describe current
system functionality. Work with the client and in particular programmers who designed the
legacy systems to understand the nuances and high-risk areas of the system that will be
replaced. Document from your findings your understanding of the current “as is” system
and also specify how you will replace the “as is” functionality with the “to be” ERP system.
Draft test cases that specifically address how the replaced functionality will be verified
within the ERP system and also allow the UAT members to peer-review the drafted test
cases as they become available. Document any feedback from the UAT members for the
drafted test cases and as time allows produce prototypes of the proposed solution to
minimize the impact on the end users.
To-be
Mapping "AS-IN" to SAP called "TO-BE"
CONFIGURATION: we will configure the system to meet the needs of your business by
using the existing data.
Customization can be costly and can complicate future upgrades to the software because
the code changes may not easily migrate to the new version. Wherever possible,
governments should avoid customization by using configuration to meet their goals.
Governments also should understand their vendor's particular terminology with regard to
this issue since words like "modifications" or "extensions" often mean different things to
different vendors.
We do in SAP R/3
We know that SAP R/3 is software, it particular it is client-server software. This means that
the groups/layers that make up a R/3 System are designed to run simultaneously across
several separate computer systems.
When you install Microsoft Excel on your PC, each component of Excel (printing
components, graphing components, word processing components, and etc.) is stored,
managed, and processed via the hardware of your PC. When a company installs SAP’s
software each component (or "layer” in R/3’s case) is stored, managed, and processed via
the hardware of separate and specialized computer systems. Each of the various layers is
capable of calling upon the specialty of any of the other installed layers in order to
complete a given task.
Those components/layers that are requesting services are called “clients”, those
components/layers that are providing services are called “servers”. Thus the term -
“client/server”. SAP is an ERP (Enterprise Resource Planning) module, ECC is the version
of SAP, like 4.6, 4.6c and 4.7 in that series new version is ECC-6. Its known as Enterprise
core component.
The sole purpose of an R/3 system is to provide a suite of tightly integrated, large-scale
business applications.
The standard set of applications delivered with each R/3 system are the following:
PP (Production Planning)
MM (Materials Management)
SD (Sales and Distribution)
FI (Financial Accounting)
CO (Controlling)
AM (Fixed Assets Management)
PS (Project System)
WF (Workflow)
IS (Industry Solutions)
HR (Human Resources)
PM (Plant Maintenance)
QM (Quality Management)
CRM (Customer Relationship Management)
These applications are called the functional areas, or application areas, or at times the
functional modules of R/3. All of these terms are synonymous with each other.
R/3 comes prepackaged with the core business applications needed by most large
corporations. These applications coexist in one homogenous environment. They are
designed from the ground up to run using a single database and one (very large) set of
tables. Current production database sizes range from 12 gigabytes to near 3 terabytes.
Around 8,000 database tables are shipped with the standard delivery R/3 product.
SAP Process is like Consulting -> Configuring -> Testing -> Support
Testers are basically no need any SAP knowledge just test how the system works -
BASICALLY END-USER ROLE.
And Support Consultant who basically supports the Project, Role comes after
configuration, testing and Go live. Like after live if client got any error or any
changes....
Business Blueprint
This function documents the business processes in your company that you want to
implement in the system. In a Business Blueprint for Projects, you create a project
structure in which relevant business scenarios, business processes and process steps are
organized in a hierarchical structure. You can also create project documentation and
assign it to individual scenarios, processes or process steps. You then assign transactions
to each process step, to specify how your business processes should run in your SAP
systems. The Business Blueprint is a detailed description of your business processes and
system requirements. You can print it out.
Integration
You can continue to use the project documentation and the project structure that you
create during the Business Blueprint, in the configuration and test organization phases.
When you configure your business processes, the system displays the Business Blueprint
project structure. You can use the Business Blueprint project structure as a point of
reference during configuration.
You can also display and edit the project documentation from the Business Blueprint
phase, during configuration.
You base all test plans that you create during test organization, on the Business Blueprint
project structure. The transactions that you assign to process steps in the Business
Blueprint are put in test plans during test plan generation, and run as function tests to test
the transactions.
Prerequisites
You have created a project of type implementation, template, or upgrade, in the project
administration.
Definition
A Business Blueprint documents the business process requirements of a company. In
collaborative business processes, several companies are involved.
Use
The Business Blueprint gives you a general idea of how your business processes could be
mapped in one or more SAP Systems. The Business Blueprint documents in detail the
scope of business scenarios, business processes, process steps, and the requirements of
an SAP solution implementation.
Structure
A Business Blueprint comprises the following structure elements in a hierarchy:
Organizational Units
Master data
Business scenarios
Business processes
Process steps
You assign content, for example, project documentation, Business Configuration Sets, or
transactions to individual structure elements, in the SAP Solution Manager.
You can also create structure elements for organizational units and master data, below a
business scenario. You only use these structure elements if the organizational units and
master data are only relevant to the business process above them in the structure.
Integration
The Business Blueprint is the prerequisite in the Solution Manager for configuration and
test organization:
Configuration:
You configure your business processes with reference to the Business Blueprint project
structure. You can also display and edit the project documentation from the Business
Blueprint phase.
Test Organization:
You base all test plans that you create during test organization, on the Business Blueprint
project structure. The transactions which you assign in Business Blueprint process steps,
are put in test plans when you generate them. You can run these transactions as function
tests, to test the transactions.
Activities
1. Create a Blueprint structure in the Structure tab, using predefined substructures.
2. Check the Business Blueprint structure, and the business scenarios, business processes
and process steps it contains.
3. Decide which business scenarios, business processes and process steps you want to
include in the Business Blueprint. You can enhance the processes and process steps, or
adjust the names of individual processes to suit your company requirements.
4. Create project documentation to save in the Business Blueprint, in the Project
Documentation tab.
5. Assign transactions to process steps in the Transactions tab. This specifies which
transactions in the system correspond to the process steps in your enterprise.
6. Print the Business Blueprint document.
7. When the Business Blueprint is complete, you can start to set up the development system
landscape.
Result
You have specified a Business Blueprint. You can reuse the Business Blueprint and the
project structure to configure and test your business processes.
Create Company
Company Company Name
BP01 SAP Best Practice
Company
Create Controlling Area
Controlling Area Name CoCd->CO Area Currency Type Currency Chart of Accts FY Variant
BP01 Controlling Cross-company-code 30 USD 0010 K4
area BP01 cost accounting
Enterprise Structure
Personnel Area Personnel Subarea
1010 Headquarters 0001 Administration
0002 Human Resources
0003 Finance
0004 Sales/Marketing
0005 Manufacturing
0006 Operations
0007 Research & Dev.
0008 Field Support
0009 Inform Tech
0010 Union ‘A’
1011 Product ‘A’ 0001 Sales/Marketing
0002 Manufacturing
0003 Operations
0004 Research & Dev.
0005 Union ‘A’
1012 Product ‘B’ 0001 Plant ‘A’
0002 Plant ‘B’
0003 Union ‘A’
1013 Subsidiary ‘A’ 0001 Location ‘A’
0002 Location ‘B’
Second Structure
Personnel Area Personnel Subarea
1020 East 0001 New York
0002 Philadelphia
0003 Washington, DC
0004 Atlanta
1021 Central 0001 Chicago
0002 Dallas
0003 Minneapolis
1022 West 0001 Human Resources
0002 Development
0003 Sales
Third Structure
Personnel Area Personnel Subarea
1030 Union 0001 Local ‘112’
0002 Local ‘083’
1032 Non-Union 0001 Human Resources
0002 Development
0003 Sales
Personnel Structure
Employee Group Employee Subgroup
1 Employee U0 Hourly
U1 Salaried-Exempt
U2 Salaried-Non Exempt
U3 Executives
U4 Sales
2 Retiree/ Pensioner U3 Executive
U5 Survivor w/ Ben
U6 Survivor w/o Ben
U7 Regular Retiree
4 Interns U0 Hourly
U1 Salaried-Exempt
U2 Salaried-Non Exempt
7 Temp/Seasonal U0 Hourly
U1 Salaried-Exempt
U2 Salaried-Non Exempt
8 Expatriate U1 Salaried-Exempt
U3 Executives
U6 Non-Payroll w/Benefits
9 External U8 Contractor
U9 Service Provider
U Inpatriate U1 Salaried-Exempt
U3 Executives
Number Ranges
No. From Number To Number Current Number External
01 00000001 00999999 Select
10 01000000 01999999 0
99 90000000 99999999 Select
Forms of Address
FOA key Title Long Text Gender
1 Mr Mr 1
2 Mrs Mrs 2
3 Miss Miss 2
4 Ms Ms 2
5 Dr DR
Residence Status
Residence Status Residence Status Text
A Non-Resident Alien
C Citizen
N Non-Citizen
ID Type
IMG Path Personnel Management Personnel Administration Personal Data Residence
Status Residence status
Transaction Code SPRO
Payroll Area
Payroll Payroll Area Period Period Date
Area Text Parameter parameter text Payroll Relevant Modifier
10 Monthly 01 Monthly Select 01
11 Semi-monthly 02 Semi-monthly Select 01
12 Weekly 03 Weekly Select 01
13 Bi-weekly 04 Bi-Weekly Select 01
99 Non-payroll relevant 01 Monthly 01
Define Administrator
Group Admin. Code Administrator Telephone Number SAP Name
APPL 001 Joanne Henderson 4274
APPL 002 Edward Carter 4424
APPL 003 Benoit LeBrun 4454
APPL 004 Andrée Gagnon 4434
US01 001 Joanne Henderson 5778
US01 002 Edward Carter 5665
US01 003 Robert Bell 5880
US01 004 Chris Appleman 5766
US01 005 Nicola Davenport 5990
2.On the Change View “Subtype Characteristics”: Overview screen, choose the New Entries ****on and enter the
following values:
SubType Name
01 Key(s)
02 Clothing
03 Books
04 Tool(s)
05 Company ID
90 Cell Phone
91 Pager
92 Company Credit Card
93 Company Car
94 Computer/Laptop
95 Security Pass
96 Parking Pass
97 Handheld Organizer
3.Choose Save.
Basic Pay
WT Wage Type Long Text Text Start Date End Date
1001 Base Rate / Hourly Wage Hrly Rat 01/01/1900 12/31/9999
1002 Payscale Salary PSSalary 01/01/1900 12/31/9999
1003 Pay Period Salary PPSalary 01/01/1900 12/31/9999
1004 Pension / Retiree Pay PensPay 01/01/1900 12/31/9999
1005 External Hrly Rate ExtRate 01/01/1900 12/31/9999
PCR Grouping
EG Employee Group ESG Employee Subgroup PCR CAP
1 Employee U0 Hourly 1 1
1 Employee U1 Salaried-Exempt 3 3
1 Employee U2 Salary-Non Exempt 3 2
1 Employee U3 Executive 3 4
1 Employee U4 Sales 3 5
2 Retiree / Pensioner U3 Executive 2 6
2 Retiree / Pensioner U5 Survivor w/Benefits 2 6
2 Retiree / Pensioner U6 Survivor w/o Benefits 2 6
2 Retiree / Pensioner U7 Regular Retiree 2 6
4 Intern U0 Hourly 1 1
4 Intern U1 Salary-Exempt 3 3
4 Intern U2 Salary-Non Exempt 3 2
7 Temp/Seasonal U0 Hourly 1 1
7 Temp/Seasonal U1 Salary-Exempt 3 3
7 Temp/Seasonal U2 Salary-Non Exempt 3 2
8 Expatriate U1 Salary-Exempt 3 3
8 Expatriate U3 Executive 3 4
9 External U8 Contractor 1 1
9 External U9 Service Provider 1 1
U Inpatriate U1 Salaried-Exempt 3 3
U Inpatriate U3 Executive 3 4
Description Level Minimum. Grade Level Maximum Grade Level Reference Salary
Salaried Exempt – East Region 00 85,000.00 210,000.00 135,000,00
Salaried Exempt – West Region 00 80,000,00 180,000,00 120,000,00
Salaried Non-Exempt – East Region 00 20,000,00 35, 000,00 27, 000,00
01 30,000,00 45, 000,00 37, 000,00
02 40,000,00 55, 000,00 47, 000,00
03 50,000,00 65, 000,00 57, 000,00
04 60,000,00 75, 000,00 67, 000,00
05 70,000,00 90, 000,00 80, 000,00
Salaried Non-Exempt – West Region 00 16,000,00 24,000,00 20,000,00
01 25,000,00 45,000,00 35,000,00
02 32,000,00 55,000,00 32,000,00
03 42,000,00 65,000,00 53,000,00
04 55,000,00 75,000,00 55,000,00
05 62,000,00 85,000,00 73,000,00
Additional Payments
Wage Type Wage Type Text Wage Type Wage Type Text
1100 Tip income 2007 Miscellaneous Arrears Recovery
1105 Gross up regular method 2008 Credit arrears $ purge
1107 Gross up supplemental method 2010 Parking Deduction
1108 Gross up result-supp method 2011 Miscellaneous Deduction
1109 Non-tax income 2012 Cafeteria Deduction
1110 Bonus 2015 Bond Purchase - Deduction
1112 Commission 2016 Bond Purchase - Balance
1113 Severance pay 2035 Computer Loan - Deduction
1120 Uniform allowance 2036 Computer Loan - Balance
1121 Equipment allowance 2040 401K Loan Deduction
1122 Car allowance 2045 Education Loan - Deduction
1123 Tuition reimbursement - taxable 2046 Education Loan - Balance
1124 Tuition reimbursement - non-tax 2057 PPD: Deduction - Benefits
1125 Relocation expenses 2058 PPD: Reimburse - Benefits
1500 1099R Non-Taxable wages 2061 PPD: Payment - Benefits
1501 1099R Taxable Wages 2856 Claim Clearing Bal Tx0
1510 1099R Total Distribution 2859 Claim Clearing Bal Tx1
2000 Charitable Donation - Amt 2862 Claim Clearing Bal Tx2
2002 Charitable - Balance 2915 Cash Non-Taxable
2004 Miscellaneous Dedn arrears dedn 2916 Claim of right
2005 Miscellaneous Dedn arrears bal 6055 Non Cash taxable
Off Cycle Payments (0267)
Wage Type Wage Type Text Wage Type Wage Type Text
1105 Gross up regular method 2803 Claim Repayment Txblty 1
1107 Gross up suppl method 2804 Claim Forgiveness Txblty 2
1111 Bonus - special pay run 2805 Claim Payment Txblty 2
1112 Commission 2850 CC Dedn Recovery Txblty 0
1113 Severance pay 2851 CC Dedn Recovery Txblty 1
2800 Claim Forgiveness Txblty 0 2852 CC Dedn Recovery Txblty L
2801 Claim Payment Txblty 0 2853 CC Dedn Recovery Txblty G
2802 Claim Forgiveness Txblty 1
Leave Compensation
ESG PSG Comp. Method Description Rule Description Quota Type
1 10 1000 Free Compensation
1 10 1001 Vacation Payout 003 Vacation
1 10 1002 Sick time payout 004 Sick/Illness
1 10 1003 Personal Time Off payout 010 Personal Time Off
1 10 1004 Floating Holidaypayout 002 Floating Holiday
1 10 1005 Overtime Comp Time Payout 001 Comp Time for Overtime
2 10 1000 Free Compensation
2 10 1001 Vacation Payout 003 Vacation
2 10 1002 Sick time payout 004 Sick/Illness
2 10 1003 Personal Time Off payout 010 Personal Time Off
2 10 1004 Floating Holidaypayout 002 Holiday Lieu
2 10 1005 Overtime Comp Time Payout 001 Comp Time for Overtime
4 10 1000 Free Compensation
4 10 1001 Vacation Payout 003 Vacation
4 10 1002 Sick time payout 004 Sick/Illness
4 10 1003 Personal Time Off payout 010 Personal Time Off
4 10 1004 Floating Holidaypayout 002 Holiday Lieu
4 10 1005 Overtime Comp Time Payout 001 Comp Time for Overtime
Wage Types for Time Quota Compensation
Wage Type Wage Type Text
1294 FMLA Payout
1295 Vacation Payout
1296 Personal Time Off Payout
1297 Floating Holiday Payout
1298 Comp Time Payout
1299 Sick Payout
Infotype Menu
Menu Menu Text Seq. # Infotype Infotype text
U1 Basic Personal Data 00 0000 Actions
02 0001 Organizational Assignment
04 0002 Personal Data
06 0006 Addresses
08 0007 Planned Working Time
10 0008 Basic Pay
12 0021 Family Member/Dependents
14 0094 Residence Status
16 0077 Additional Personal Data
18 0105 Communication
Personal Actions
U0 Hiring 10 05 INS 0001 Organizational Assignment
10 10 INS 0002 Personnel Data
10 15 INS 0006 1 Addresses
10 20 INS 0210 FED Withholding Info W4/W5 US
10 25 INS 0007 Planned Working Time
10 30 INS 0008 Basic Pay
10 35 INS 0009 Bank Details
10 40 MOD 0041 Date Specifications
10 45 INS 0077 Additional Personal Data
10 50 INS 0094 Residence Status
10 55 INS 0171 General Benefits Data
10 60 INS 0378 HIRE Adjustment Reasons
10 70 INS 0017 Travel Privileges
10 20 05 INS 0001 Organizational Assignment
10 20 10 INS 0002 Personnel Data
10 20 15 INS 0006 1 Addresses
10 20 20 INS 0210 FED Withholding Info W4/W5 US
10 20 25 INS 0007 Planned Working Time
10 20 30 INS 0008 Basic Pay
10 20 35 INS 0009 Bank Details
U0 – Hiring No Reason
U1 New Position
U2 New Product Line
U3 Re-Organization
U4 Attrition
U5 Special Projects
U6 Acquisition
U7 Survivor
U1 – Quick Hire No Reason
U1 New Position
U2 New Product Line
U3 Re-Organization
U4 Attrition
U5 Special Projects
U6 Acquisition
U7 Survivor
U2 – Transfer/Relocation No Reason
U1 Career Opportunity
U2 Re-Organization
U3 Temporary Move
U4 Personal
U3 – Change in Position No Reason
U1 Promotion
U2 Lateral Move
U3 Demotion
U4 Reclassification
U5 Temporary to Regular
U6 Regular to Temporary
U4 – Change in Pay No Reason
U1 Pay Scale Reclassification
U2 Pay Scale Increase
U3 Annual Review
U4 Promotion
U5 Demotion
U6 Adjustment
U5 – Termination No Reason
U1 Career Opportunity
U2 Relocation
U3 Health Reasons
U4 Further Study
U5 Mutual Agreement
U6 Involuntary
U8 Death of Employee
U9 Management Conflict
UA Seasonal
U6 – Rehire No Reason
U1 Reinstatement
U2 Seasonal
U7 – Retirement No Reason
U1 Early Retirement
U8 – Leave of Absence – Active Status No Reason
U1 Medical
U2 FMLA/Extended Family Care
U3 Sabbatical
U4 Short Term Disability
U5 Long Term Disability
U6 Workers’ Compensation
U7 Personal Leave
U8 Education Leave
U9 Layoff with Severance
UA Military
U9 – Leave of Absence – Inactive Status No Reason
U1 Medical
U2 FMLA/Extended Family Care
U3 Sabbatical
U4 Short Term Disability
U5 Long Term Disability
U6 Workers’ Compensation
U7 Personal Leave
U8 Education Leave
U9 Layoff with Severance
UA Military
QA – Return to Work from Inactive Status No Reason
U1 End of Leave
U2 Restaffing
U3 End of shut down
QB – Return to Work from Active Status No Reason
U1 End of Leave
U2 Restaffing
U3 End of shut down
U4 Return from work reduction
QC – Reduction in Work Force No Reason
U1 Plant Closing
U2 Profitability/Economic
QD – Hire Applicant No Reason
U1 New Position
U2 New Product Line
U3 Re-organization
U4 Attrition
U5 Special Projects
U6 Acquisition
QE – Change in Personal Data No Reason
U1 Family Status Change
U2 Name change
U3 Address change
No Reason
QF – Quick Hire Follow-Up U2 Quick Hire Follow-Up
Payroll Areas
PayrollArea Payroll Area Text Period Parameter Period Parameter Text Payroll Relevant Date Modifier
10 Monthly 01 Monthly 01
11 Semi-monthly 02 Semi-Monthly 01
12 Weekly 03 Weekly 01
13 Bi-weekly 04 Bi-Weekly 01
99 Non-payroll Relevant
Period Modifiers
Personnel Control Record
Payroll Payroll Area Control Record Payroll period Run Earliest Retroactive Accounting
Area Text Type Period
01/01/2006 –
10 Monthly 01 Payroll 01 2006 01/31/2006 0 01 2006 01/01/2006
11 Semi-monthly 01 Payroll 01 2006 01/01/2006 – 01/15/2006 0 01 2006 01/01/2006
12 Weekly 01 Payroll 02 2006 01/01/2006 – 01/07/2006 0 02 2006 01/01/2006
13 Bi-weekly 01 Payroll 02 2006 01/01/2006 – 01/14/2006 0 02 2006 01/01/2006