Joseph Manuel Wilson

High Level Design (HLD) Module 14 – Salary Planning Contents REVISION HISTORY ........................................................................................................................................ 4 14. Salary Planning ................................................................................................................................... 5 Functionality in Brief ................................................................................................................................. 6 Main Menu................................................................................................................................................ 8 Salary Planning Menu ................................................................................................................................. 10 1. Generate and view the employee’s Current salary details .............................................................. 10 Functionality in Detail ............................................................................................................................- Should be able to define different categories of salary revision. ....................................... 12 3. 14.1B Should be able to define the salary revision cycles (maybe annual, half yearly, monthly, Date of joining, etc.) ......................................................................................................................... 13 4. 14.2 Should be able input salary revision types – Organization & Division/Department. ........ 15 5. 14.23A Should be able to input the salary revision cycle details (maybe Annual, Half Yearly or Quarterly) for the Organization.......................................................................................................-B Should be able to input the salary revision cycle details (Maybe Annual, Half Yearly, or Quarterly) for the Division/Department. ........................................................................................- Should be able to assign organization level type salary revision planning for the employees .......................................................................................................................................- Should be able assign department level type salary revision planning option to the employees. ....................................................................................................................................... 22 9. 14.4 Should be able define salary range for grades under each level ........................................ 25 10. 14.3 Should be able to define the salary revision budget for Manager ..................................... 27 11. 14.6 Should be able to define the salary revision guidelines, stating the increment percentage for each grade with different ratings under each level...................................................................- Should be able to lock (an option if required) the Manager’s salary planning budget utilization, so not to allow the budget utilization go above the approved level. ...........................- The manager should be able to generate and save the current salary details (grade, level, CTC Salary range, etc. as shown in the Entity below) data for all the employees due for salary revision. ...........................................................................................................................................- Should be able to revise salary for significant achievement. ............................................. 37 15. 14.7 Manager/End user should be able to do Annual/Half yearly etc. salary revision for all eligible employees as per the defined guidelines for grades at various levels with respect to performance rating of the individual. .............................................................................................. 44 Version 600 LS Software confidential document - Copyright © Protected. Page 1 of 109 High Level Design (HLD) Module 14 – Salary Planning 16. 14.8 The manager should be able to view the individual details (e.g. employee name, current department, current manager, grade, level, current CTC, last CTC revision date with reason) and be able to make changes to the revised salary by editing proposed percentage increase as per guidelines. .......................................................................................................................................- Manager/end user should be able to have a consolidated view of the salary planning for all the staff on the computer screen, to make required changes to percentage raise to keep the salary revision within the managers salary budget and complete the salary planning process .....- The manager/end user should be able view the actual salary budget, the balance of salary budget after salary revision. The balance salary budget may be negative (-ve) balance, if salary budget is not locked. Please refer Req. 14.13 .................................................................................-A The system should be able keep record of salary revision approval levels and approval details-B The Approving Manager/end user should be able to state the completion of salary planning and approve the salary planning and send a notification message to Next Level Approval Manager ..........................................................................................................................................-A The managers at different levels should be able to view approved salary planning details (emp. name, current salary grade, new salary grade, current salary, new salary, the percentage raise, the allocated budget, balance budget positive or negative balance) and if required should be able to request revision of salary. The system should send a notification to the Approving Manager requesting necessary change. ..........................................................................................-B The Managers at different levels should be able to view approved salary planning details (emp. name, current salary grade, new salary grade, current salary, new salary, the percentage raise, the allocated budget, balance budget positive or negative balance) and if no change is required Should be able to send it to next level of approval. A notification email should be sent to the next level approval. ...................................................................................................................- System should be able to send a notification email to HR, and Business Unit Head, when the final authority approves the salary planning. ...........................................................................- BU’s (Business Units) Should be able to send notification mail to HR when salary planning is completed for the BU.................................................................................................................- HR should be able to view the salary planning module, the budget allocated for salary planning and the budget balance remaining after allocation to all the department. ..................- Should be able create and store different letter templates/formats for increments, promotions etc. ................................................................................... Error! Bookmark not defined. 27. 14.22 HR should be able to choose the appropriate format (e.g. for increment, promotion, etc.) from a list of format to generate the respective Salary Revision letters and save it in PDF and word formats Error! Bookmark not defined. Version 600 LS Software confidential document - Copyright © Protected. Page 2 of 109 High Level Design (HLD) Module 14 – Salary Planning 28. 14.25 The system should be able to send salary revision details to the accounts team, clearly showing previous salary and the new salary. ...................................... Error! Bookmark not defined. 29. 14.14 After salary revision, the System should move the employee’s previous Salary Revision details from entity EMPLOYEE to EMPLOYEE HISTORY entity. Then the system should update the entity EMPLOYEE with the latest salary revision details from entity SALARY REVISION. .......... Error! Bookmark not defined. 30. 14.26 After the salary revision, System should insert the revised Employee CTC from the Salary revision entity to Revised CTC entity................................................... Error! Bookmark not defined. Version 600 LS Software confidential document - Copyright © Protected. Page 3 of 109 High Level Design (HLD) Module 14 – Salary Planning REVISION HISTORY Version Date Particulars Author Review Date - - Document Creation Enhanced Enhanced Enhanced Enhanced Enhanced Wilson Wilson Wilson Wilson Wilson Wilson - Version 600 Reviewed By Wilson Wilson Wilson Wilson Wilson Wilson LS Software confidential document - Copyright © Protected. Comments Approved Approved Approved Approved Approved Approved Page 4 of 109 High Level Design (HLD) Module 14 – Salary Planning 14. Salary Planning The Salary planning process deals with planning and revision of salary for the individual based on the individual performance rating, on completion of probation period or due to some significant event or achievement. The period for salary planning process may be annual event, half yearly, fixed monthly or based on date of joining. The period for salary planning may be same across the organization or parts of the organization can have different salary planning period. Salary planning process takes care of the individuals on probations (3-6 months) and revision of salary on confirmation. The salary revision has no pre-defined time frame, the revision can happen due some significant achievement of an individual. The salary revision/increase is done based on internal guide lines for a particular level and the percentage increase applicable. (all these are unique situations in organizations. All of them are not applicable to all organizations).The salary increase is based annual PMS rating of individual and the budget available with the manager. Each grade should have a salary range (organizations typically have this. Some might not have defined this). During the working of salary revision process ---- the details (e.g. employee name, current department, current manager, job grade, current salary, proposed percentage increase as per guidelines, actual increase, proposed salary, available budget, previous salary changes with date and reason, remaining budget available) should be visible to the manager. The manager may make an entry of his wish. The manager should be able to see the overall budget and the salary revision impact on the budget, and the balance budget available, balance may be –ve or +ve. In some cases a lock might have to be applied, to not to let the budget utilization go above the approved budget level. The revised salary after increase should be visible to the manager. The individuals grade and salary ranges should also be visible to the manager. The consolidate view of salary planning for each and every individual should be visible to the manager on the computer screen, to complete the salary planning process. After the manager complete and approve the salary planning information, the salary planning information is locked and no further changes is allowed. The lock on salary planning information can be removed only by the above level manager. The approved and locked salary planning, information is send to next level and then it moves on to higher levels. The next level managers should be able to see the approved salary planning details (emp name, current salary grade, new salary grade, current salary, new salary, the percentage raise, the allocated budget, balance budget positive or negative balance). The managers at respective level can approve it or request for a change, and also remove the lock on the salary planning, so the designated manager can carry out the changes. Once the final authority approves the salary planning, a mail is sent to HR, approving manager, and immediate superior of the approving manager. HR should be notified by mails by respective BU (Business Unit) heads, when the salary planning is completed. HR should be able to see the stages (levels) of salary planning approval for BU. HR should be able to see the BU levels that has completed has completed the salary planning and the Version 600 LS Software confidential document - Copyright © Protected. Page 5 of 109 High Level Design (HLD) Module 14 – Salary Planning BU yet to complete the salary planning, and accordingly send reminders to BU levels to complete the Salary Planning. HR should be able to see in the salary planning module, the budget allocated for salary planning and the budget balance remaining after allocation to all the department. HR should be able to generate the increment letter on predefined format for all the individual. The format of the letter may differ depending on the type of letter (increment, promotion, etc.). Should be able to save letter in PDF or word format. The salary revision details information (employee name, current salary grade, new salary grade, current salary, new salary) should flow to the accounts team, clearly showing the difference, it should show the previous salary and the new salary. The accounts will process the payroll based on the new salary. Functionality in Brief Sr. No-. Req.ID-B Functionality in Brief Should be able to define different categories of salary revision. Should be able to define the salary revision cycles (maybe annual, half yearly, monthly, Date of joining, etc.) 14.2 Should be able input salary revision types – Organization & Division/Department. 14.23A Should be able to input the salary revision cycle details (maybe Annual, Half Yearly or Quarterly) for the Organization. 14.23B Should be able to input the salary revision cycle details (maybe annual, half yearly, Quarterly, or monthly) for the Department. 14.24 Should be able to assign organization level type salary revision planning for the employees. 14.16 Should be able assign department level type salary revision planning to the employees. 14.4 Should be able define salary range for a level/grade for division/subdivision. 14.3 Should be able to define the salary revision budget for /Manager 14.6 Should be able to define the salary revision guidelines having increment percentage for grade at different levels, for different ratings 14.13 Should be able to lock (an option if required) the Manager salary planning budget utilization, so not to allow the budget utilization go above the approved level. The manager should be able to generate and save the current salary details (grade, level, 14.9 CTC Salary range, etc. as shown in the Entity below) data for all the employees due for salary revision. 13. 14. Version 600 14.5 14.7 The end user should also be able to view the employee’s salary details from the generated data. Should be able to revise CTC for significant achievement. Manager/End user should be able to do Annual/Half yearly etc. salary revision for all eligible employees as per the defined guidelines for grades at various levels with respect to performance rating of the individual. LS Software confidential document - Copyright © Protected. Page 6 of 109 High Level Design (HLD) Module 14 – Salary Planning 15. 14.8 16. 14.11 17. 14.12 18. 14.15A 19. 14.15B 20. 14.17A 21. 14.17B 22. 14.18 23. 14.19 24. 14.20 25. 14.21 26. 14.22 Version 600 The manager should be able to view the individual details (e.g. employee name, current department, current manager, grade, level, current CTC, last CTC revision date with reason) and be able to make changes to the revised salary by editing proposed percentage increase as per guidelines. The effect of change in percentage, should be visible against revised salary, actual increase, available budget, balance budget during individual salary revision process. Manager/end user should be able to have a consolidated view of the salary planning for all the staff on the computer screen, to make required changes to percentage raise to keep the salary revision within the managers salary budget and complete the salary planning process The manager/end user should be able view the actual salary budget, the balance of salary budget after salary revision. The balance salary budget may be negative (-ve) balance, if salary budget is not locked. Please refer Req. 14.13 The system should be able keep record of salary revision approval levels and approval details. The Approving Manager should be able to state the completion of salary planning and approve the salary planning and send a notification mail to the next level of approval. The managers at different levels should be able to view approved salary planning details (emp. name, current salary grade, new salary grade, current salary, new salary, the percentage raise, the allocated budget, balance budget positive or negative balance) and if required should be able to request revision of salary. The system should send a notification to the approving manager requesting necessary change. The Managers at different levels should be able to view approved salary planning details (emp. name, current salary grade, new salary grade, current salary, new salary, the percentage raise, the allocated budget, balance budget positive or negative balance) and if no change is required Should be able to send it to next level of approval. A notification email should be sent to the next level approval. System should be able to send a notification email to HR, and Business Unit Head, when the final authority approves the salary planning. BU’s (Business Units) Should be able to send notification mail to HR when salary planning is completed for the BU. HR should be able to view the salary planning module, the budget allocated for salary planning and the budget balance remaining after allocation to all the department. Should be able create and store different letter templates/formats for increments, promotions etc. HR should be able to choose the appropriate format (e.g. for increment, promotion, etc.) from a list of format to generate the respective Salary Revision letters and save it in PDF and word formats LS Software confidential document - Copyright © Protected. Page 7 of 109 High Level Design (HLD) Module 14 – Salary Planning 27. 14.25 28. 14.14 29. 14.26 The system should be able to send salary revision details to the accounts team, clearly showing previous salary and the new salary. After the first salary revision, update the entity Employee, Last Salary Revision Date, Salary revision date to next salary revision date, and other fields related to salary revision. After the salary revision, update the Employee CTC with latest CTC from the Salary revision entity Main Menu Sr.No. Module 1 Manpower Planning 2 Recruitment Recruitment 3 Selection 4 Offer 5 On Boarding 6 Benefits Administration Process 7 Employee self - service Process 8 Learning management systems (LMS) 9 Attendance & Leave management systems 10 Reports & Analytics 11 Travel Desk 12 Payroll Process 13 PMS 14 Salary Planning Process 15 Employee Survey Process 16 Incentive/Performance/Project Bonus User interface Version 600 LS Software confidential document - Copyright © Protected. Page 8 of 109 High Level Design (HLD) Module 14 – Salary Planning Version 600 LS Software confidential document - Copyright © Protected. Page 9 of 109 High Level Design (HLD) Module 14 – Salary Planning Salary Planning Menu (**Note: do not put the number 14.1, 14.2, it is shown here only for traceability purpose). Please use the below menu options as ‘Screen title’ of the screens invoked by the respective menu options. Sr. No. 1. Functionality in Brief Create Categories for Salary Revision. Req.ID 14.10 Menu Setup 2. Create the salary revision cycles 14.1B Setup 3. Create Salary Revision Types 14.2 Setup 4. Assign Salary Revision Cycle To Organization. 14.23A Admin Submenu Salary Revision Categories Salary Revision Cycles Salary Revision Type Employee 5. Assign Salary Revision Cycle To Department. 14.23B Admin Employee 6. Assign Organization Salary Revision Planning To Employees. 14.24 Admin Employee 7. Assign Department Salary Revision Planning To Employees. 14.16 Admin Employee 8. Define Salary Range For Grades Of Each Level. Define The Salary Revision Budget For Manager Define The Salary Revision Guidelines 14.4 Admin Define 14.3 Admin Define 14.6 Admin Define Lock the Manager salary planning budget Generate and view the employee’s Current salary details 14.13 Admin 14.9 Admin Lock Manager Salary Budget View 13. Significant achievement CTC Revision 14.5 14. Annual/Half yearly Salary Revision 14.7 15. View & Edit Employees Revised Salary Consolidated View & Edit of all Employees Revised Salary 14.8 Salary Revision Salary Revision Admin Signification Achievement Annual/ Half yearly Revision Modify/Edit 14.11 Manager Modify/Edit -. 16. Version 600 LS Software confidential document - Copyright © Protected. Sub-submenu Assign Organization Salary Revision Cycle Assign Division Salary Revision Cycle Assign Organization Salary Revision Planning Assign Department Salary Revision Planning Grade/Level Salary Range Manager Salary revision Budget Salary Revision Guidelines View Employee current salary details Employee Revised Salary All Employees Consolidate Revised Salary Page 10 of 109 High Level Design (HLD) Module 14 – Salary Planning-. 29. View Manager Actual Salary budget & balance After salary revision. Record of salary revision approvals 14.12 Manager 14.15A Salary Planning Completion and Approval by Approving Manager Next Level Change Request to Salary Revision Next Level Approval of Salary Revision. Final Level Approval & Notification to HR and BU BU Salary Planning Completion Notification to HR HR View of salary planning, Allocated budget & Balance budget Create letter templates for increments, promotions etc. Generate Salary Revision Letter 14.15B Salary Revision Manager Send salary revision details in Excel to the Accounts Update Employee Details with Latest Salary Revision information. - Salary Revision Salary Revision Admin Update Employee CTC with Revised CTC 14.26 Admin Version 600 14.17A 14.17B- Salary Revision Salary Revision Salary Revision Salary Planning Salary Planning Setup Actual & Balance Salary Budge Record Revision Approvals Salary Planning Approval Change Request Next Level Approval Final Level Approval HR Completion Notification Allocated Versus Balance Budget Define Letter Templates Generate Salary Revision Letter Send HR Salary Revision Details Update Employee Salary Revision Details Update Employee’s Revised CTC Details LS Software confidential document - Copyright © Protected. Page 11 of 109 High Level Design (HLD) Module 14 – Salary Planning Functionality in Detail Sr. No. 1. Req. ID 14.10 Requirement 14.10 Should be able to define different categories of salary revision. The end user should be able to define different categories salary revision, for e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “SALARY REVISION CATEGORY” Seq. No. 1. 2. Field Name Salary Revision Category ID Salary Revision Category Description Edit/ View Edit Edit Unit Particulars/ Validations/ Formulas Unique ID To uniquely identify Salary Revision Category To input salary revision category Description. The salary revision category can be of type – for e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity. Salary Revision Category Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 12 of 109 Data Type N C High Level Design (HLD) Module 14 – Salary Planning User interface Entities accessed Entity Name Salary Revision Category Sr. No. 2. Req. ID 14.1B Purpose To input all types of Salary revisions categories Requirement 14.1B Should be able to define the salary revision cycles (maybe annual, half yearly, monthly, Date of joining, etc.) Every company/organization has a predefined salary revision cycles, this can be annual, half yearly (i.e. April – Sept & Oct-March) or date of joining date to date of joining date etc. In case of half yearly cycle, the salary planning for employees joined between April – Sept, will be done in Oct, and like-wise, the salary planning for employees joined between Oct – March will be done in April. In case of Date of join, the employees Date of Joining, is compared to the fiscal year, to consider Annual or half yearly salary revision cycles. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface. Version 600 LS Software confidential document - Copyright © Protected. Page 13 of 109 High Level Design (HLD) Module 14 – Salary Planning ENTITY = “SALARY REVISION CYCLE” Seq. No. 1. Field Name Salary Revision Cycle ID Edit/ View Edit 2. Salary Revision Cycle Edit Unit Particulars/ Validations/ Formulas Unique ID. To uniquely identify each Salary Revision Cycle like Annual, Half yearly, or date of joining etc. Enter the name of Salary Revision Cycle. Note: The values can be “Annual”, Date of Joining” or Half yearly. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity. Salary Revision Cycle Process Flow User interface Version 600 LS Software confidential document - Copyright © Protected. Page 14 of 109 Data Type N C High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Salary Revision Cycle Sr. No. 3. Req. ID 14.2 Purpose To input all trainings of the company Requirement 14.2 Should be able input salary revision types – Organization & Division/Department. A company should have the option of choosing the organization type salary revision or department type salary revision. An Option of “Organization type” states that all employees falling under this option will have their salary revision, as per the salary planning period defined at organization level. Likewise all employees falling under the option Division/Department type, will have their salary revision, as per the salary planning period defined in for their respective departments. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “SALARY REVISION TYPE” Seq. No. 1. Version 600 Field Name Salary Revision Type ID Edit/ View Edit Unit Particulars/ Validations/ Formulas Unique ID. To uniquely identify the Salary Revision Type. LS Software confidential document - Copyright © Protected. Page 15 of 109 Data Type N High Level Design (HLD) Module 14 – Salary Planning 2. Salary Revision Type Description Edit Enter the salary revision type description. The Options can be “Organization”, “Division/Department” Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity “Salary Revision Type” Process Flow User interface Entities accessed Entity Name Salary Revision Type Version 600 Purpose To input Salary Revision types. LS Software confidential document - Copyright © Protected. Page 16 of 109 C High Level Design (HLD) Module 14 – Salary Planning Sr. No. 4. Req. ID 14.23A Requirement 14.23A Should be able to input the salary revision cycle details (maybe Annual, Half Yearly or Quarterly) for the Organization. The end user should be able define the salary planning details for the Organization. All the employee salary planning will be governed as per details defined for the organization which may be Annual, Half Yearly or Quarterly. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “ORGANIZATION” Seq. No. 1. 2. Field Name Organization ID Organization Edit/ View Edit View Description 3. 4. Salary Revision Cycle ID Salary Revision Cycle Edit Edit Unit Particulars/ Validations/ Formulas Pick from entity Organization Populate from entity Organization based on Organization ID. Pick from entity Salary Revision Cycle Populate from entity Salary Revision Cycle based on Salary Revision Cycle ID. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity Organization Process Flow User interface Version 600 LS Software confidential document - Copyright © Protected. Page 17 of 109 Data Type N C N C High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Organization Sr. No. 5. Req. ID 14.23B Purpose To input organizations salary planning details Requirement 1423B Should be able to input the salary revision cycle details (Maybe Annual, Half Yearly, or Quarterly) for the Division/Department. The end user should be able define the salary revision details for the Division/Department. All the employee salary planning will be governed as per details defined for the Division/Department which may be Annual, Half Yearly, or Quarterly. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface. ENTITY = “DIVISION” Seq. No. 1. 2. Version 600 Field Name Division ID Division Name Edit/ View Edit View Unit Particulars/ Validations/ Formulas Pick from entity Division Populate from entity Division based on Division ID. LS Software confidential document - Copyright © Protected. Page 18 of 109 Data Type N C High Level Design (HLD) Module 14 – Salary Planning 3. 4. Salary Revision Cycle ID Salary Revision Cycle Edit Edit Pick from entity Salary Revision Cycle Populate from entity Salary Revision Cycle based on Salary Revision Cycle ID. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity. Division Process Flow User interface Entities accessed Version 600 LS Software confidential document - Copyright © Protected. Page 19 of 109 N C High Level Design (HLD) Module 14 – Salary Planning Entity Name Division Sr. No. 6. Req. ID 14.24 Purpose To input Division/Department salary planning details Requirement 14.24 Should be able to assign organization level type salary revision planning for the employees. The end user should be able to assign organization level type salary planning Option for all the employees of the organization. All the employees become eligible for salary revision, based on the salary revision cycle mentioned at the organization level. ***Please Note: The end user should be able to input/modify/update values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface. ENTITY = “EMPLOYEE” Seq. No. 1. 2. Field Name Employee ID Employee Name Edit/ View Edit View 3. Joining Date View 4. Division/Departme nt ID Job title ID View View 7. Job title Description Level ID 8. 9. Level Description Grade ID View View 10. Grade Description View 11. Salary Revision Type ID Salary Revision Type Description Edit 5. 6. 12. Version 600 View View View Unit Particulars/ Validations/ Formulas Pick from entity Employee Populate from entity Employee based on Employee ID Retrieve from entity Employee based on Employee ID. Retrieve from entity Employee based on Employee ID. Retrieve from entity Employee based on Employee ID. Populate from entity Job title based on “Job title ID” Retrieve from entity Employee based on Employee ID. Populate from entity Level based on “Level ID” Retrieve from entity Employee based on Employee ID. Populate from entity Grade based on “Grade ID” Populate from entity Division based on Division ID Populate from entity Salary Revision Type based on Salary Revision Type ID. Here the value populated should be “Division/Department” LS Software confidential document - Copyright © Protected. Page 20 of 109 Data Type N C D N N C N C N C N C High Level Design (HLD) Module 14 – Salary Planning 13. Salary Revision Cycle ID Edit 14. Salary Revision Cycle Description Salary Revision Category View 15. View Populate from entity “Division” based on Division/Department ID Since the salary revision category is “Department” Populate from the entity “Salary Revision Cycle” The category of Salary revision. For. E.g. salary revision due to Annual Raise, Promotions, N C C Confirmation, Significant Achievement etc. 16. 17. Last Salary Revision Date Salary Revision Date View Edit Retrieve from entity Employee based on Employee ID. The Salary Revision Date, based on the employee “Joining Date and Salary revision cycle For Example: Salary Revision Date for :Annual Cycle = Salary Revision fiscal period. Half Yearly = employees Joining Date between April – Sept, will be done in Oct, and like-wise, the salary planning for employees Joining Date between Oct – March will be done in April. Date of Joining Cycle = employees Joining date to following year’s Joining Date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Assign” Button, the system should perform the following tasks 1. Warn the user through a dialogue box to continue … Y/N. If “N” remain in the same screen. 2. If “Y” update the entity “Employee” with the values in the fields Salary Revision Type ID, Salary Revision Cycle ID and Salary Revision Date. Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 21 of 109 D D High Level Design (HLD) Module 14 – Salary Planning User interface Entities accessed Entity Name Employee Sr. No. 7. Req. ID 14.16 Version 600 Purpose To input salary revision planning categories. Requirement 14.16 Should be able assign department level type salary revision planning option to the employees. The end user should be able to assign department level type salary planning option to all the employees of the respective department. Each department may LS Software confidential document - Copyright © Protected. Page 22 of 109 High Level Design (HLD) Module 14 – Salary Planning have its on salary revision planning cycle. All the employees become eligible for salary revision, based on the salary revision cycle mentioned for the department. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “EMPLOYEE” Seq. No. 1. 2. Field Name 3. Joining Date View 4. Division/Department ID View 5. Job title ID View 6. Job title Description View 7. Level ID View 8. Level Description View 9. Grade ID View 10. Grade Description View 11. Salary Revision Type ID Edit 12. Salary Revision Type Description View 13. Salary Revision Cycle ID Edit 14. Salary Revision Cycle View 15. Salary Revision Category View Version 600 Employee ID Employee Name Edit/ View Edit Unit Particulars/ Validations/ Formulas Pick from entity Employee Retrieve from entity Employee based on Employee ID. Retrieve from entity Employee based on Employee ID. Retrieve from entity Employee based on Employee ID. Retrieve from entity Employee based on Employee ID. Populate from entity Job title based on “Job title ID” Retrieve from entity Employee based on Employee ID. Populate from entity Level based on “Level ID” Retrieve from entity Employee based on Employee ID. Populate from entity Grade based on “Grade ID” Populate from entity Division based on Division ID Populate from entity Salary Revision Type based on Salary Revision Type ID. Here the value populated should be “Division/Department” Populate from entity “Division” based on Division/Department ID Since the salary revision category is “Department” Populate from the entity “Salary Revision Cycle” The category of Salary revision. For. E.g. salary revision due to Annual Raise, LS Software confidential document - Copyright © Protected. Page 23 of 109 Data Type N C D N N C N C C High Level Design (HLD) Module 14 – Salary Planning Promotions, Confirmation, Significant Achievement etc. 16. Last Salary Revision Date View 17. Salary Revision Date Edit Retrieve from entity Employee based on Employee ID. The Salary Revision Date, is DERIVED based on the employee “Joining Date, Salary revision cycle, and Department’s Salary Revision financial period start date and Salary Revision financial period end date. For Example: Salary Revision Date for :Annual Cycle = Salary Revision financial period end date. Half Yearly = employees Joining Date between April – Sept, will be done in Oct, and like-wise, the salary planning for employees Joining Date between Oct – March will be done in April. Date of Joining Cycle = employees Joining date to following year’s Joining Date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Assign” Button, the system should perform the following tasks 1. Warn the user through a dialogue box to continue … Y/N. If “N” remain in the same screen. 2. If “Y” update the entity “Employee” with the values in the fields Salary Revision Category ID, Salary Revision Cycle ID and Salary Revision Date. Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 24 of 109 D D High Level Design (HLD) Module 14 – Salary Planning User interface Entities accessed Entity Name Employee Sr. No. 8. Req. ID 14.4 Version 600 Purpose To input salary revision planning categories. Requirement 14.4 Should be able define salary range for grades under each level The end user should be able input the salary range for grades under each level. The salary range for a grade (technical) under a level (L4) may be different from grade (support) under the same level (L4). LS Software confidential document - Copyright © Protected. Page 25 of 109 High Level Design (HLD) Module 14 – Salary Planning ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “SALARY LEVEL” Seq. No. 1. 2. Field Name 3. Salary Level ID Salary Level Description Level ID 4. 5. 6. 7. 8. Level Name Grade ID Grade Name Salary start range Salary end range Edit/ View Edit View View View View View Edit Edit Unit Particulars/ Validations/ Formulas Pick Salary Level ID from the entity “Salary Level” Retrieve from the entity “Salary Level” based on Salary Level ID Retrieve from the entity “Salary Level” based on Salary Level ID Populate from the entity Level based on Level ID Retrieve from the entity “Grade” based on Grade ID Populate from entity Grade based on Grade ID To input the start range of the Salary To input the end range of the salary Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity. Salary Level Process Flow User interface Version 600 LS Software confidential document - Copyright © Protected. Page 26 of 109 Data Type N C N C N C N N High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Salary Level Sr. No. 9. Req. ID 14.3 Purpose To input salary ranges for each level for Division/Sub Division Requirement 14.3 Should be able to define the salary revision budget for Manager The end user should be able to define/input salary revision budget for each Manager. The Manager revises the salary for the employees within the limits of the salary revision budget. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “MANAGER SALARY BUDGET” Seq. No. 1. 2. Version 600 Field Name Manager Salary Budget ID Manager Salary Budget Description Edit/ View Edit Edit Unit Particulars/ Validations/ Formulas Unique ID To uniquely identify Manager Salary Budget Description of the Salary Budget LS Software confidential document - Copyright © Protected. Page 27 of 109 Data Type N C High Level Design (HLD) Module 14 – Salary Planning 3. Budget Year Edit 4. 5. Job Title ID Manager Employee ID Edit Edit 6. Manager Name View 7. Division ID Edit 8. Division Name View 9. Subdivision ID Edit 10. Subdivision Name View 11. 12. Salary Budget Balance Salary Budget Edit Edit 13. Budget Lock Edit To input the budget fiscal Year. E.g. Jan 2013-Dec 2013, or April 2013-March 2014 Pick the job title from the entity “Job title” Pick the Manager’s Employee ID from the entity “Employee” filtered on Job Title ID Populate from entity “Employee” based on Manager’s Employee ID Populate from entity “Employee” based on Manager’s Employee ID Populate from entity Division Based on Division ID Populate from entity “Employee” based on Manager’s Employee ID Populate from entity Subdivision Based on Subdivision ID To input Salary Revision Budget System Computed field. This field shows the balance of Salary Budge, after salary revision. Valid values “Y” or “N” Default Value= “Y” To Lock the budget, so the salary revision planning does not exceed the allocated salary budget. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity. Manager Salary Budget Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 28 of 109 C N N C C N C N N C High Level Design (HLD) Module 14 – Salary Planning User interface Entities accessed Entity Name Manager Salary Budget Sr. No. 10. Req. ID 14.6 Purpose To input Division Head Budget Requirement 14.6 Should be able to define the salary revision guidelines, stating the increment percentage for each grade with different ratings under each level. The end user should be able to define salary revision guideline stating the increment percentage for each grade with different ratings under each level. The employee’s raise in salary is based on this guidelines. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface Version 600 LS Software confidential document - Copyright © Protected. Page 29 of 109 High Level Design (HLD) Module 14 – Salary Planning ENTITY = “SALARY REVISION GUIDELINE” Seq. No. 1. Field Name 2. Edit 3. 4. Salary Revision Guidelines Description Level ID Level Name 5. 6. Grade ID Grade Name Edit Edit 7. Evaluation Scale Edit 8. Performance Rating Edit 9. Moderation Range ID Edit 10. Percentage Raise Edit Salary Revision Guidelines ID Edit/ View Edit Unit Edit View Grade, Weightage, Rating, Percentage 1 to 10 1 to 5 Particulars/ Validations/ Formulas Unique ID To uniquely identify Salary Revision Guidelines To Description of Salary Revision Guidelines. Pick from entity “Level” Populate from entity Level based on “Level ID” Pick from entity “Grade” Populate from entity “Grade” based on Grade ID Pick Grade or Weightage or Rating from entity Evaluation scale. C N C N C To enter the Performance result. It is C Based on the evaluation scale selected and will be any of the following values. Rating =>1 and <=5 or =>1 and <=10 Auto populated by the system. The system should check the Performance Rating in various range band (i.e. Moderation Starting Rating Range AND Moderation Ending Rating Range) defined in the entity “Moderation Range”, and Populating the appropriate Moderation ID from “Moderation Range entity. The value is populated from field “Percentage Salary Raise“ of entity Moderation Range based on Moderation Range ID Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity. Salary Revision Guideline. Version 600 Data Type N LS Software confidential document - Copyright © Protected. Page 30 of 109 N N High Level Design (HLD) Module 14 – Salary Planning Process Flow User interface Entities accessed Entity Name Version 600 Purpose LS Software confidential document - Copyright © Protected. Page 31 of 109 High Level Design (HLD) Module 14 – Salary Planning Salary Revision Guideline Sr. No. 11. Req. ID 14.13 To input salary revision guidelines for each level based on the performance ratings. Requirement 14.13 Should be able to lock (an option if required) the Manager’s salary planning budget utilization, so not to allow the budget utilization go above the approved level. The end user should be able to lock the salary planning budget utilization during salary planning process, thus not to allow the budget utilization go above the approved level. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface The notification mails should contain the details highlighted in bold. ENTITY = “MANAGER SALARY BUDGET” Seq. No. 1. 2. 3. 4. 5. Field Name Manager Salary Budget ID Manager Salary Budget Description Budget Year Edit/ View Edit Edit Edit Edit Edit 6. Job Title ID Manager Employee ID Manager Name 7. Division ID View 8. 9. Division Name Subdivision ID View View 10. Subdivision Name View 11. Salary Budget Edit 12. Balance Salary Budget Edit Version 600 View Unit Particulars/ Validations/ Formulas Retrieve the From entity Manager Salary Budget based on Manager Employee ID Retrieve form entity Salary Budget on based on Manager Salary Budget ID To input the budget fiscal Year. E.g. Jan 2013-Dec 2013, or April 2013-March 2014 Pick the job title from the entity “Job title” Pick the Manager’s Employee ID from the entity “Manager Salary Budget” Populate from entity “Employee” based on Manager’s Employee ID Retrieve form entity Salary Budget on based on Manager Salary Budget ID Populate from entity Division Based on Division ID Retrieve form entity Salary Budget on based on Manager Salary Budget ID Populate from entity Subdivision Based on Subdivision ID Retrieve form entity Salary Budget on based on Manager Salary Budget ID Retrieve form entity Salary Budget on based on Manager Salary Budget ID LS Software confidential document - Copyright © Protected. Page 32 of 109 Data Type N C C N N C C N C N N High Level Design (HLD) Module 14 – Salary Planning 13. Budget Lock Edit Retrieve form entity Salary Budget on based on Manager Salary Budget ID Valid values “Y” or “N” To Lock the budget, so the salary revision planning does not exceed the allocated salary budget. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity. Manager Salary Budget Process Flow User interface Version 600 LS Software confidential document - Copyright © Protected. Page 33 of 109 C High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Manager Salary Budget Sr. No. 12. Req. ID 14.9 Purpose To Lock/unlock salary revision budget. Requirement 14.9 The manager should be able to generate and save the current salary details (grade, level, CTC Salary range, etc. as shown in the Entity below) data for all the employees due for salary revision. The end user should also be able to view the employee’s salary details from the generated data. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface. Version 600 LS Software confidential document - Copyright © Protected. Page 34 of 109 High Level Design (HLD) Module 14 – Salary Planning ENTITY = “EMPLOYEE SALARY DETAIL” Seq. No. 1. 2. Field Name Employee ID Employee Name Edit/ View Edit View 3. Level ID View 4. Level Description View 5. Grade ID View 6. Grade Description 7. Salary Revision Category ID View Unit Particulars/ Validations/ Formulas Pick from entity “Employee” Populate from entity “Employee” based on Employee ID Populate from entity “Employee” based on Employee ID Populate from entity “Level” based on “Level ID” Populate from entity “Employee” based on Employee ID Populate from entity “Grade” based on “Grade ID” Populate from entity “Employee” based on Employee ID. For e.g. Annual Salary Data Type N C N C N C N review, Promotions, Confirmation, Significant Achievement etc. 8. Salary Revision Category View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 9. Division ID View 10. Division Description View 11. Subdivision ID View 12. Subdivision Description View 13. Employee CTC View 14. Salary Level ID View 15. Salary start Range View 16. Salary end Range View 17. Salary Revision Date View Populate from entity “Employee” based on Employee ID Populate from entity “Division” based on Division ID. Populate from entity “Employee” based on Employee ID Populate from entity “Subdivision” based on Subdivision ID Populate from entity “Employee CTC” based on “Employee ID” Populate from entity “Salary Level” based on “Level ID + Grade ID” Populate from entity “Salary Level” based on Salary Level ID Populate from entity “Salary Level” based on Salary Level ID Populate from entity “Employee” based on Employee ID Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows Version 600 LS Software confidential document - Copyright © Protected. Page 35 of 109 N C N C N N N N D High Level Design (HLD) Module 14 – Salary Planning 1. When the end user clicks “Cancel” Button, the system should exit from the screen. 2. When the end user clicks “Generate” Button, the system should be able to generate the above data, for employee whose “Salary Revision Date” falls within the Salary Revision Period, and save it to entity Employee Salary Detail. 3. Display the data in the format shown in User Interface section . Process Flow User interface Note there will be two UI’s 1. Revision Period From DD/MM/YYYY To DD/MM/YYYY 2. List all the fields shown in the above entity. Version 600 LS Software confidential document - Copyright © Protected. Page 36 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Employee Salary Detail Sr. No. 13. Req. ID 14.5 Purpose To view employee salary details. Requirement 14.5 Should be able to revise salary for significant achievement. The end user should be able to revise the salary of an employee because of significant achievement. The end user should also be able to see the details like employee’s CTC, salary range for the grade under that level, Manager’s budget, employee’s last salary revision date etc. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface Fields highlighted in RED will be in the header section Fields highlighted in Blue will be in the details section ENTITY = “SALARY REVISION” Seq. No. 1. 2. 3. 4. 5. Version 600 Field Name Salary Revision ID Salary Revision Description Salary Revision Type ID Salary Revision Type description Fiscal Period Start Date Edit/ View Edit Edit Edit Edit Unit Particulars/ Validations/ Formulas Data Type N Unique ID To uniquely identify Salary Revision To input salary revision description C Pick the Salary Revision Type ID from entity Salary Revision Type. The salary revision types e.g. Organization, Division/Department etc. Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date LS Software confidential document - Copyright © Protected. Page 37 of 109 N C D High Level Design (HLD) Module 14 – Salary Planning 6. 7. 8. Fiscal Period End date Salary Revision Category ID Edit To enter Fiscal Period End date D Edit Pick from entity Salary Revision Category. For e.g. N Salary Revision Category View Annual Salary review, Promotions, Confirmation, Significant Achievement etc. Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. C Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 9. Salary Revision Cycle ID 10. Salary Revision Cycle 11. 12. Employee ID Employee Name Edit View 13. Level ID View 14. Level Description Grade ID View -. Version 600 Grade Description Division ID View View View Division Description Subdivision ID View Subdivision Description Current CTC View Employee Salary Revision Date Last Salary Revision Category ID View View View View Populate from entity “Organization” or “Department” based on value in the Field Salary Revision Type ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. Pick From entity Employee. Populate from entity “Employee” based on Employee ID Populate from entity “Employee” based on Employee ID Populate from entity “Level” based on “Level ID” N C N C Populate from entity “Employee” based on Employee ID Populate from entity “Grade” based on “Grade ID” N Populate from entity “Employee” based on Employee ID Populate from entity “Division” based on Division ID. Populate from entity “Employee” based on Employee ID Populate from entity “Subdivision” based on Subdivision ID Populate from entity “Employee CTC” based on “Employee ID” Populate from entity “Employee” based on “Employee ID” Populate from field “Salary Revision Category ID” of entity Employee, based on Employee ID. N For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. LS Software confidential document - Copyright © Protected. Page 38 of 109 C C N C N D N High Level Design (HLD) Module 14 – Salary Planning 24. Last Salary Revision Category Description Last Salary Revision Date Performance Rating Salary Level ID View Level/grade Salary start Range Level/grade Salary end Range Salary Revision Guidelines ID Salary Revision Guidelines Percentage Raise View 33. Approving Manager ID View 34. Approving Manager Name View 35. View 36. Approving Manager Email ID Salary Budget 37. Revised Level Edit 38. Revised Grade -. 29. 30. 31. 32. Version 600 Populate from entity “Salary Revision Category” based on Salary Revision Category ID. C For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. View View View Populate from field “Last Salary Revision Date” of entity Employee, based on Employee ID. Populate from field “Moderated Rating” of entity Employee appraisal based on “Employee ID” Populate from entity “Salary Level” based on “Level ID + Grade ID” Populate from entity “Salary Level” based on Salary Level ID+ Grade ID N N N View Populate from entity “Salary Level” based on Salary Level ID + Grade ID N View Populate from entity “Salary Revision Guideline” based on Level ID + Grade ID Populate from entity “Salary Revision Guideline” based on “Salary Revision Guidelines ID” Populate from entity “Salary Revision Percentage” based on Salary Revision Guidelines ID +Performance Rating” “Salary Revision Guidelines ID” Populate Reporting Manager ID (Employee ID) of Employee from entity “Employee” based on employee’s Employee ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). N Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity Manager Salary Budget based on Approving Manager ID (Employee ID of Approving manager). Pick from the entity Level. Note: The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Pick from the entity Grade. Note: C View Edit View LS Software confidential document - Copyright © Protected. Page 39 of 109 C N N C N C C High Level Design (HLD) Module 14 – Salary Planning The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Derived by computing i.e. Revised CTC = 39. Revised CTC Edit 40. Actual CTC increase Budget Lock Edit View Compute the difference of (Revised CTC-Current CTC) Retrieved from entity Manager Salary Budget based on Approving Manager ID (employee ID of Manager) Balance Salary Budget Edit Valid values Y/N Derived after computing (Salary Budget - Actual CTC increase). N ((Current CTC * Percentage Raise) + Current CTC) 41. 42. 43. 44. 45. 46. 47. Change Required Change details Next Level Approval Required Next level Approval Manager ID Next level Approval Manager Name Edit Edit Edit Edit Edit Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve) A value “Y” indicates a change is required. Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Change required=”N” Valid Values Y or N. Default Value = Y This field is Enabled only when the field Approval at Next Level required=”Y” Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approval at Next Level required=”Y” Populate from entity Employee based on Next level Approval Manager ID. Version 600 LS Software confidential document - Copyright © Protected. Page 40 of 109 N C N C M C N C High Level Design (HLD) Module 14 – Salary Planning 48. 49. Next Level Approval Manager email id Edit Lock Salary Planning Edit 50. Final Approval Edit 51. Final level Approval Manager ID Edit 52. Final level Approval Manager Name Edit 53. Final Approval Date Edit 54. Business unit Approval required Edit 55. 56. 57. 58. Business Unit Head ID Business Unit Head Name Business Unit Approval Edit Business Unit Approval Date Edit Edit Edit This field is Enabled only when the field Approval at Next Level required=”Y” Populate from entity Employee based on Next level Approval Manager ID. Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. Default Value = “N” Valid values are Y or N A value “Y” indicates the final approval. Valid Values Y or N. Default Value = N This field is Enabled only when the field Final Approval =”Y” Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Approval =”Y” Populate from entity Employee based on Final level Approval Manager ID. Auto updated with System Date when field Final Approval = Y To input final approval date This field is Enabled only when the field Final Approval =”Y” Valid Values Y or N. Default Value =N Pick the Business Unit Head ID (Employee ID) from entity Employee Populate from entity Employee based on Final level Approval Manager ID. A value “Y” indicates the Business Unit approval. Valid Values Y or N. Default Value = N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. Version 600 LS Software confidential document - Copyright © Protected. Page 41 of 109 N C C N C D N C C D High Level Design (HLD) Module 14 – Salary Planning 2. When the end user clicks “Save” Button, a) The system should save the data to entity Employee Salary Revision. b) The system should update the field Balance Salary Revision Budget of entity Manager Salary Budget based on Reporting Manager ID (employee ID of Manager) Process Flow User interface Version 600 LS Software confidential document - Copyright © Protected. Page 42 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Employee Salary Revision Salary Revision Type Salary Revision Category Version 600 Purpose To revise employee’s salary. To get the Salary revision type e.g. Organization or Department To get the Salary revision category e.g. Significant achievement, annual appraisal, confirmation etc. LS Software confidential document - Copyright © Protected. Page 43 of 109 High Level Design (HLD) Module 14 – Salary Planning Salary Revision Cycle Employee Annual appraisal Salary Level Salary Revision Guideline Manager Salary Budget Sr. No. 14. Req. ID 14.7 To get the salary revision cycle e.g. Annual, half yearly, quarterly etc. To get employee details To get performance ratings To get salary range for particular grade in a level To get the salary revision guidelines. Percentage raise in salary is based on performance rating. To get the Salary budget of the Manager Requirement 14.7 Manager/End user should be able to do Annual/Half yearly etc. salary revision for all eligible employees as per the defined guidelines for grades at various levels with respect to performance rating of the individual. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “SALARY REVISION” Seq. No. 1. Field Name 2. Salary Revision Description Salary Revision Type ID 3. 4. 5. 6. 7. 8. Version 600 Salary Revision ID Salary Revision Type description Fiscal Period Start Date Fiscal Period End date Salary Revision Category ID Salary Revision Category Edit/ View Edit Edit Edit Edit Edit Edit Unit Particulars/ Validations/ Formulas Unique ID To uniquely identify Salary Revision To input salary revision description Pick the Salary Revision Type ID from entity Salary Revision Type. The salary revision types e.g. Organization, Division/Department etc. Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date To enter Fiscal Period End date Pick from entity Salary Revision Category. Data Type N C N C D D N For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. Annual Raise, Promotions, LS Software confidential document - Copyright © Protected. Page 44 of 109 C High Level Design (HLD) Module 14 – Salary Planning Confirmation, Significant Achievement etc. 9. Salary Revision Cycle ID View 10. Salary Revision Cycle View 11. Employee ID Edit 12. Employee Name View 13. Level ID View 14. Level Description View 15. Grade ID View 16. Grade Description 17. Division ID View 18. Division Description View 19. Subdivision ID View 20. Subdivision Description View 21. Current CTC View 22. Employee Salary Revision Date Last Salary Revision Date View Last Salary Revision Category ID View 23. 24. View Populate from entity “Organization” or “Department” based on value in the Field Salary Revision Type ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. From entity Employee extract all Employee code whose “Salary Revision Date” fall within the “Fiscal Period Start Date” and “Fiscal Period End date” Populate from entity “Employee” based on Employee ID Populate from entity “Employee” based on Employee ID Populate from entity “Level” based on “Level ID” Populate from entity “Employee” based on Employee ID Populate from entity “Grade” based on “Grade ID” Populate from entity “Employee” based on Employee ID Populate from entity “Division” based on Division ID. Populate from entity “Employee” based on Employee ID Populate from entity “Subdivision” based on Subdivision ID Populate from entity “Employee CTC” based on “Employee ID” Populate from entity “Employee” based on “Employee ID” Populate from field “Last Salary Revision Date” of entity Employee, based on Employee ID. Populate from field “Salary Revision Category ID” of entity Employee, based on Employee ID. For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. Version 600 LS Software confidential document - Copyright © Protected. Page 45 of 109 N C N C N C N C N C N D N High Level Design (HLD) Module 14 – Salary Planning 25. Last Salary Revision Category Description View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. C For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 26. Performance Rating View 27. Salary Level ID View 28. Level/grade Salary start Range Level/grade Salary end Range Salary Revision Guidelines ID Salary Revision Guidelines View 32. Percentage Raise Edit 33. Approving Manager ID View 34. Approving Manager Name View 35. Approving Manager Email ID View 36. Salary Budget View 37. Revised Level Edit 38. Revised Grade 29. 30. 31. Version 600 View View View Populate from field “Moderated Rating” of entity Employee appraisal based on “Employee ID” Populate from entity “Salary Level” based on “Level ID + Grade ID” Populate from entity “Salary Level” based on Salary Level ID Populate from entity “Salary Level” based on Salary Level ID Populate from entity “Salary Revision Guideline” based on Level ID + Grade ID Populate from entity “Salary Revision Guideline” based on “Salary Revision Guidelines ID” Populate from entity “Salary Revision Percentage” based on Salary Revision Guidelines ID +Performance Rating” “Salary Revision Guidelines ID” Populate Reporting Manager ID (Employee ID) of Employee from entity “Employee” based on employee’s Employee ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). N Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity Manager Salary Budget based on Approving Manager ID (Employee ID of Approving manager). Pick from the entity Level. Note: The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Pick from the entity Grade. Note: C LS Software confidential document - Copyright © Protected. Page 46 of 109 N N N N C N N C N C C High Level Design (HLD) Module 14 – Salary Planning 39. Revised CTC Edit The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Derived by computing i.e. Revised CTC = N ((Current CTC * Percentage Raise) + Current CTC) 40. Actual CTC increase Edit 41. Budget Lock View Compute the difference of (Revised CTCN Current CTC) Retrieved from entity Manager Salary Budget C based on Approving Manager ID (employee ID of Manager) Edit Valid values Y/N Derived after computing (Salary Budget - Actual CTC increase). 42. 43. 44. 45. 46. 47. Version 600 Balance Salary Budget Change Required Change details Next Level Approval Required Next level Approval Manager ID Next level Approval Manager Name Edit Edit Edit Edit Edit Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve) A value “Y” indicates a change is required. Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Change required=”N” Valid Values Y or N. Default Value = Y This field is Enabled only when the field Approval at Next Level required=”Y” Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approval at Next Level required=”Y” LS Software confidential document - Copyright © Protected. Page 47 of 109 N C M C N C High Level Design (HLD) Module 14 – Salary Planning 48. 49. Next Level Approval Manager email id Lock Salary Planning Edit Edit 50. Final Approval Edit 51. Final level Approval Manager ID Edit 52. Final level Approval Manager Name Edit 53. Final Approval Date Edit 54. Business unit Approval required Edit 55. Business Unit Head ID Edit 56. Business Unit Head Name Business Unit Approval Edit Business Unit Approval Date Edit 57. 58. Edit Populate from entity Employee based on Next level Approval Manager ID. This field is Enabled only when the field Approval at Next Level required=”Y” Populate from entity Employee based on Next level Approval Manager ID. Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. Default Value = “N” Valid values are Y or N A value “Y” indicates the final approval. Valid Values Y or N. Default Value = N This field is Enabled only when the field Final Approval =”Y” Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Approval =”Y” Populate from entity Employee based on Final level Approval Manager ID. Auto updated with System Date when field Final Approval = Y To input final approval date This field is Enabled only when the field Final Approval =”Y” Valid Values Y or N. Default Value =N Pick the Business Unit Head ID (Employee ID) from entity Employee Populate from entity Employee based on Final level Approval Manager ID. A value “Y” indicates the Business Unit approval. Valid Values Y or N. Default Value = N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Version 600 LS Software confidential document - Copyright © Protected. Page 48 of 109 N C C N C D C N C C D High Level Design (HLD) Module 14 – Salary Planning Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, a) The system should save the data to entity Employee Salary Revision. b) The system should update the field Balance Salary Revision Budget of entity Manager Salary Budget based on Reporting Manager ID (employee ID of Manager) Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 49 of 109 High Level Design (HLD) Module 14 – Salary Planning User interface Version 600 LS Software confidential document - Copyright © Protected. Page 50 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Employee Salary Revision Salary Revision Type Salary Revision Category Salary Revision Cycle Employee Annual appraisal Salary Level Salary Revision Guideline Manager Salary Budget Sr. No. 15. Req. ID 14.8 Purpose To revise employee’s salary. To get the Salary revision type e.g. Organization or Department To get the Salary revision category e.g. Significant achievement, annual appraisal, confirmation etc. To get the salary revision cycle e.g. Annual, half yearly, quarterly etc. To get employee details To get performance ratings To get salary range for particular grade in a level To get the salary revision guidelines. Percentage raise in salary is based on performance rating. To get the Salary budget of the Manager Requirement 14.8 The manager should be able to view the individual details (e.g. employee name, current department, current manager, grade, level, current CTC, last CTC revision date with reason) and be able to make changes to the revised salary by editing proposed percentage increase as per guidelines. The effect of change in percentage, should be visible against revised salary, actual increase, available budget, balance budget during individual salary revision process. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface. The fields highlighted in Red will appear in the header section The fields highlighted in Blue will appear in the detail section ENTITY = “SALARY REVISION” Seq. No. 1. 2. 3. Version 600 Field Name Salary Revision ID Salary Revision Description Salary Revision Type ID Edit/ View Edit View View Unit Particulars/ Validations/ Formulas Pick from entity Salary Revision Retrieve from entity Salary Revision based on Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID. The salary revision types e.g. Organization, Division/Department etc. LS Software confidential document - Copyright © Protected. Page 51 of 109 Data Type N C N High Level Design (HLD) Module 14 – Salary Planning 4. 5. 6. 7. Salary Revision Type description Fiscal Period Start Date Fiscal Period End date Salary Revision Category ID View View View Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date To enter Fiscal Period End date Retrieve from entity Salary Revision based on Salary Revision ID. C D D N For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 8. Salary Revision Category View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. Annual Raise, Promotions, C Confirmation, Significant Achievement etc. 9. Salary Revision Cycle ID View 10. Salary Revision Cycle View 11. Employee ID View 12. Employee Name View 13. Level ID View 14. Level Description View 15. Grade ID View 16. Grade Description View 17. Division ID View 18. Division Description View 19. Subdivision ID View 20. Subdivision Description View Version 600 Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. Retrieve from entity Salary Revision based on Salary Revision ID. All Employee codes whose “Salary Revision Date” fall within the “Fiscal Period Start Date” and “Fiscal Period End date” Populate from entity “Employee” based on Employee ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Level” based on “Level ID” Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Grade” based on “Grade ID” Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Division” based on Division ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Subdivision” based on Subdivision ID LS Software confidential document - Copyright © Protected. Page 52 of 109 N C N C N C N C N C High Level Design (HLD) Module 14 – Salary Planning 21. Current CTC View 22. Employee Salary Revision Date Last Salary Revision Date Last Salary Revision Category ID View 23. 24. View View Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Employee” based on “Employee ID” Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. N D N For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 25. Last Salary Revision Category Description View Retrieve from entity Salary Revision based on Salary Revision ID. C For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 26. Performance Rating View 27. Salary Level ID View 28. Level/grade Salary start Range Level/grade Salary end Range Salary Revision Guidelines ID Salary Revision Guidelines View 32. Percentage Raise Edit 33. Approving Manager ID View 34. Approving Manager Name View 35. Approving Manager Email ID View 36. Salary Budget View 37. Revised Level Edit 29. 30. 31. Version 600 View View View Populate from field “Moderated Rating” of entity Employee appraisal based on “Employee ID” Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Salary Revision Guidelines” based on “Salary Revision Guidelines ID” Retrieve from entity Salary Revision based on Salary Revision ID. Populate Reporting Manager ID (Employee ID) of Employee from entity “Employee” based on employee’s Employee ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). N Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity Manager Salary Budget based on Approving Manager ID (Employee ID of Approving manager). Pick from the entity Level. C LS Software confidential document - Copyright © Protected. Page 53 of 109 N N N N C N N C N C High Level Design (HLD) Module 14 – Salary Planning 38. Revised Grade 39. Revised CTC Edit Note: The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Pick from the entity Grade. Note: The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Derived by computing i.e. Revised CTC = C N ((Current CTC * Percentage Raise) + Current CTC) 40. Actual CTC increase Edit 41. Budget Lock View Compute the difference of (Revised CTCCurrent CTC) Retrieved from entity Manager Salary Budget based on Approving Manager ID (employee ID of Manager) 42. Balance Salary Budget Edit Valid values Y/N Derived after computing (Salary Budget - Actual CTC increase). 43. 44. 45. 46. Version 600 Change Required Change details Next Level Approval Required Next level Approval Manager ID Edit Edit Edit Edit Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve) A value “Y” indicates a change is required. Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Change required=”N” Valid Values Y or N. Default Value = Y This field is Enabled only when the field Approval at Next Level required=”Y” LS Software confidential document - Copyright © Protected. Page 54 of 109 N C N C M C N High Level Design (HLD) Module 14 – Salary Planning 47. 48. 49. Next level Approval Manager Name Next Level Approval Manager email id Lock Salary Planning Edit Edit Edit 50. Final Approval Edit 51. Final level Approval Manager ID Edit 52. Final level Approval Manager Name Edit 53. Final Approval Date Edit 54. Business unit Approval required Edit 55. Business Unit Head ID Edit 56. Business Unit Head Name Business Unit Approval Edit 57. Version 600 Edit Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approval at Next Level required=”Y” Populate from entity Employee based on Next level Approval Manager ID. This field is Enabled only when the field Approval at Next Level required=”Y” Populate from entity Employee based on Next level Approval Manager ID. Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. Default Value = “N” Valid values are Y or N A value “Y” indicates the final approval. Valid Values Y or N. Default Value = N This field is Enabled only when the field Final Approval =”Y” Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Approval =”Y” Populate from entity Employee based on Final level Approval Manager ID. Auto updated with System Date when field Final Approval = Y To input final approval date This field is Enabled only when the field Final Approval =”Y” Valid Values Y or N. Default Value =N Pick the Business Unit Head ID (Employee ID) from entity Employee Populate from entity Employee based on Final level Approval Manager ID. A value “Y” indicates the Business Unit approval. Valid Values Y or N. LS Software confidential document - Copyright © Protected. Page 55 of 109 C N C C N C D N C C High Level Design (HLD) Module 14 – Salary Planning 58. Business Unit Approval Date Edit Default Value = N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should return to previous screen. 2. When the end user clicks “Save” Button, a) The system should save the data to entity Employee Salary Revision. b) The system should update the field Balance Salary Revision Budget of entity Manager Salary Budget based on Reporting Manager ID (employee ID of Manager) Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 56 of 109 D High Level Design (HLD) Module 14 – Salary Planning User interface Version 600 LS Software confidential document - Copyright © Protected. Page 57 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Employee Salary Revision Salary Revision Type Salary Revision Category Version 600 Purpose To revise employee’s salary. To get the Salary revision type e.g. Organization or Department To get the Salary revision category e.g. Significant achievement, annual appraisal, confirmation etc. LS Software confidential document - Copyright © Protected. Page 58 of 109 High Level Design (HLD) Module 14 – Salary Planning Salary Revision Cycle Employee Annual appraisal Salary Level Salary Revision Guideline Manager Salary Budget Sr. No. 16. Req. ID 14.11 To get the salary revision cycle e.g. Annual, half yearly, quarterly etc. To get employee details To get performance ratings To get salary range for particular grade in a level To get the salary revision guidelines. Percentage raise in salary is based on performance rating. To get the Salary budget of the Manager Requirement 14.11 Manager/end user should be able to have a consolidated view of the salary planning for all the staff on the computer screen, to make required changes to percentage raise to keep the salary revision within the managers salary budget and complete the salary planning process ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user Interface Fields highlighted in red should be in the header section. Fields Highlighted in blue should be in the details section ENTITY = “SALARY REVISION” Seq. No. 1. Field Name 2. Salary Revision Description Salary Revision Type ID View Salary Revision Type description Fiscal Period Start Date Fiscal Period End date Salary Revision Cycle ID View 3. 4. 5. 6. 7. Version 600 Salary Revision ID Edit/ View Edit View View View View Unit Particulars/ Validations/ Formulas Extract all the Salary Revision ID from entity Salary Revision Retrieve from entity Salary Revision based on Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID. The salary revision types e.g. Organization, Division/Department etc. Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date To enter Fiscal Period End date Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. LS Software confidential document - Copyright © Protected. Page 59 of 109 Data Type N C N C D D High Level Design (HLD) Module 14 – Salary Planning 8. Salary Revision Cycle View 9. Division ID View 10. Division Description View 11. Subdivision ID View 12. Subdivision Description View 13. Employee ID View 14. Employee Name View 15. Level ID View 16. Level Description View 17. Grade ID View 18. Grade Description View 19. Salary Revision Category ID View Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Division” based on Division ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Subdivision” based on Subdivision ID Retrieve from entity Salary Revision based on Salary Revision ID. All Employee codes whose “Salary Revision Date” fall within the “Fiscal Period Start Date” and “Fiscal Period End date” Populate from entity “Employee” based on Employee ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Level” based on “Level ID” Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Grade” based on “Grade ID” Retrieve from entity Salary Revision based on Salary Revision ID. N C N C N C N For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 20. Salary Revision Category View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. Annual Raise, Promotions, C Confirmation, Significant Achievement etc. 21. 22. 23. Employee Salary Revision Date Last Salary Revision Date Last Salary Revision Category ID View View View Populate from entity “Employee” based on “Employee ID” Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. Version 600 LS Software confidential document - Copyright © Protected. Page 60 of 109 D N High Level Design (HLD) Module 14 – Salary Planning 24. Last Salary Revision Category Description View Retrieve from entity Salary Revision based on Salary Revision ID. C For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 25. Performance Rating View 26. Salary Level ID View 27. Level/grade Salary start Range Level/grade Salary end Range Salary Revision Guidelines ID Salary Revision Guidelines View 31. Percentage Raise Edit 32. Revised Level Edit 33. Revised Grade 34. Revised CTC Edit 35. Actual CTC increase Edit 36. Approving Manager ID View 37. Approving Manager Name View 38. Approving Manager Email ID View 39. Salary Budget View 28. 29. 30. View View View Populate from field “Moderated Rating” of entity Employee appraisal based on “Employee ID” Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Salary Revision Guidelines” based on “Salary Revision Guidelines ID” Retrieve from entity Salary Revision based on Salary Revision ID. Pick from the entity Level. Note: The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Pick from the entity Grade. Note: The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Derived by computing i.e. Revised CTC = N C N N C N ((Current CTC * Percentage Raise) + Current CTC) Version 600 Compute the difference of (Revised CTCCurrent CTC) Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Retrieve from entity Salary Revision based on Salary Revision ID. LS Software confidential document - Copyright © Protected. Page 61 of 109 N N N N High Level Design (HLD) Module 14 – Salary Planning 40. 41. 42. 43. 44. 45. 46. 47. 48. Version 600 Balance Salary Budget Budget Lock Approved Lock Salary Planning Next level Manager ID Next level Manager Name Next Level Manager email id Change Required Change details Edit View Derived after computing (Salary Budget - Actual CTC increase). Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve). Retrieved from entity Manager Salary Budget based on Approving Manager ID (employee ID of Manager) N C Edit Valid values Y/N This field is Enabled only when the field Change required=”N” N Edit Valid Values Y or N. Default Value = Y Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. M Edit Edit Edit Edit Edit Default Value = “N” Valid values are Y or N This field is Enabled only when the field Approval =”Y” Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. A value “Y” indicates a change is required. Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” LS Software confidential document - Copyright © Protected. Page 62 of 109 N C N C C High Level Design (HLD) Module 14 – Salary Planning 49. To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Approved =”Y” Next Level Approved C Valid Values Y or N. Default Value = Y 50. 51. 52. Final level Manager ID Final level Manager Name Final Level Approved Edit Edit Edit 53. Final Approved Date Edit 54. Business Unit Head ID Edit 55. Business Unit Head Name Edit 56. Business Unit Approved Edit 57. Business Unit Approval Date Edit This field is Enabled only when the field Final Next Level Approved =”Y” Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Next Level Approved =”Y” Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Next Level Approved =”Y” Valid Values Y or N. Default Value = N Auto updated with System Date when field Final Level Approved = Y To input final approval date This field is Enabled only when the field Final Level Approved = Y Pick the Business Unit Head ID (Employee ID) from entity Employee This field is Enabled only when the field Final Level Approved = Y Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Level Approved = Y Valid Values Y or N. Default Value =N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Version 600 LS Software confidential document - Copyright © Protected. Page 63 of 109 C N C N C N C High Level Design (HLD) Module 14 – Salary Planning Workflows 1. When the end user clicks “Cancel” Button, the system should return to previous screen. 2. When the end user clicks “Save” Button, a) The system should save the data to entity Employee Salary Revision. b) The system should update the field Balance Salary Revision Budget of entity Manager Salary Budget based on Reporting Manager ID (employee ID of Manager) Process Flow User interface Version 600 LS Software confidential document - Copyright © Protected. Page 64 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Employee Salary Revision Sr. No. 17. Req. ID 14.12 Purpose To view and revise all employee’s salary. Requirement 14.12 The manager/end user should be able view the actual salary budget, the balance of salary budget after salary revision. The balance salary budget may be negative (-ve) balance, if salary budget is not locked. Please refer Req. 14.13 ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface Version 600 LS Software confidential document - Copyright © Protected. Page 65 of 109 High Level Design (HLD) Module 14 – Salary Planning ENTITY = “MANAGER SALARY BUDGET” Seq. No. 1. 2. 3. 4. 5. Field Name Manager Salary Budget ID Manager Salary Budget Description Budget Year Edit/ View Edit Edit Edit Edit Edit 6. Job Title ID Manager Employee ID Manager Name 7. Division ID View 8. 9. Division Name Subdivision ID View View 10. Subdivision Name View 11. Salary Budget Edit 12. Balance Salary Budget Budget Lock Edit 13. View Edit Unit Particulars/ Validations/ Formulas Retrieve the From entity Manager Salary Budget based on Manager Employee ID Retrieve from entity Salary Budget on based on Manager Salary Budget ID To input the budget fiscal Year. E.g. Jan 2013-Dec 2013, or April 2013-March 2014 Pick the job title from the entity “Job title” Pick the Manager’s Employee ID from the entity “Manager Salary Budget” Populate from entity “Employee” based on Manager’s Employee ID Retrieve from entity Salary Budget on based on Manager Salary Budget ID Populate from entity Division Based on Division ID Retrieve from entity Salary Budget on based on Manager Salary Budget ID Populate from entity Subdivision Based on Subdivision ID Retrieve from entity Salary Budget on based on Manager Salary Budget ID Retrieve from entity Salary Budget on based on Manager Salary Budget ID Retrieve from entity Salary Budget on based on Manager Salary Budget ID Valid values “Y” or “N” To Lock the budget, so the salary revision planning does not exceed the allocated salary budget. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should return to the previous screen. Version 600 LS Software confidential document - Copyright © Protected. Page 66 of 109 Data Type N C C N N C C N C N N C High Level Design (HLD) Module 14 – Salary Planning Process Flow User interface Entities accessed Entity Name Manager Salary Budget Sr. No. 18 Req. ID 14.15A Version 600 Purpose To View the manager salary budget Requirement 14.15A The system should be able keep record of salary revision approval levels and approval details. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface The notification mails should contain the details highlighted in bold. LS Software confidential document - Copyright © Protected. Page 67 of 109 High Level Design (HLD) Module 14 – Salary Planning ENTITY = “SALARY REVISION APPROVAL HISTORY” Seq. No-. Field Name Salary Revision Approval ID Salary Revision ID Salary Revision Description Next Level Approval Manager ID Next Level Approval Manager Name Next Level Approval Manager Level ID Level ID Description Approval Date Change request Date Change details Edit/ View Edit Edit View Edit Edit Edit Edit Edit Edit Edit Unit Particulars/ Validations/ Formulas Unique ID (Auto generated) To uniquely identify Salary Revision Approval To input Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID To input the Next Approval Manager ID (Employee ID ) Populate from Entity Employee based on Next Approval Manager ID (Employee ID ) Populate from Entity Employee based on Next Approval Manager ID (Employee ID ) Populate from entity Level based on Level ID System updates this field with System Date System updates this field with System Date To record change details to the salary revision. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks the “View” Button in the dialogue box :The system should display the above data. 2. When the end user clicks the “Cancel” Button the system should exit back to the menu. Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 68 of 109 Data Type N N C N C N C D D M High Level Design (HLD) Module 14 – Salary Planning Dialogue Box Should display Dialogue box with the following content:“Salary Revision Approval History” Button “View” and “Cancel” User interface Entities accessed Entity Name Salary Revision Approval History Sr. No. 19. Req. ID 14.15B Version 600 Purpose To Record Salary Revision at different Approval levels. Requirement 14.15B The Approving Manager/end user should be able to state the completion of salary planning and approve the salary planning and send a notification message to Next Level Approval Manager The salary planning approval is usually done by employee’s Reporting Manager is also known as Approving Manager. Prior to approval the system should warn the LS Software confidential document - Copyright © Protected. Page 69 of 109 High Level Design (HLD) Module 14 – Salary Planning Approving manager that on approval, the Salary Planning will be locked and no further change will be allowed. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “SALARY REVISION” Seq. No. 1. Field Name 2. Salary Revision Description Salary Revision Type ID View View 6. 7. Salary Revision Type description Fiscal Period Start Date Fiscal Period End date Division ID 8. Division Description View 9. Subdivision ID View 10. Subdivision Description Approving Manager ID Approving Manager Name View 13. Approving Manager Email ID View 14. Salary Revision Cycle ID View 3. 4. 5. 11. 12. Version 600 Salary Revision ID Edit/ View Edit View View View View View View Unit Particulars/ Validations/ Formulas Extract all the Salary Revision ID from entity Salary Revision Retrieve from entity Salary Revision based on Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID. The salary revision types e.g. Organization, Division/Department etc. Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date To enter Fiscal Period End date Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Division” based on Division ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Subdivision” based on Subdivision ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. LS Software confidential document - Copyright © Protected. Page 70 of 109 Data Type N C N C D D N C N C High Level Design (HLD) Module 14 – Salary Planning 15. Salary Revision Cycle View 16. Employee ID View 17. Employee Name View 18. Level ID View 19. Level Description View 20. Grade ID View 21. Grade Description View 22. Salary Revision Category ID View Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. Retrieve from entity Salary Revision based on Salary Revision ID. All Employee codes whose “Salary Revision Date” fall within the “Fiscal Period Start Date” and “Fiscal Period End date” Populate from entity “Employee” based on Employee ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Level” based on “Level ID” Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Grade” based on “Grade ID” Retrieve from entity Salary Revision based on Salary Revision ID. N C N C N C N For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 23. Salary Revision Category View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. Annual Raise, Promotions, C Confirmation, Significant Achievement etc. 24. Current CTC View 25. Performance Rating View 26. Salary Level ID View 27. Percentage Raise Edit 28. Revised Level Edit 29. Revised Grade 30. Revised CTC Version 600 Edit Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Pick from the entity Level. Note: The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Pick from the entity Grade. Note: The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Derived by computing i.e. Revised CTC = LS Software confidential document - Copyright © Protected. Page 71 of 109 N V N N C C N High Level Design (HLD) Module 14 – Salary Planning ((Current CTC * Percentage Raise) + Current CTC) 31. Actual CTC increase Edit 32. Approved Edit 33. Last Salary Revision Date Last Salary Revision Category ID View 34. View Compute the difference of (Revised CTCCurrent CTC) Valid Values Y or N. Default Value = Y Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. N C N For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 35. Last Salary Revision Category Description View Retrieve from entity Salary Revision based on Salary Revision ID. C For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 36. Level/grade Salary start Range Level/grade Salary end Range Salary Revision Guidelines ID Salary Revision Guidelines View 40. Salary Budget View 41. Balance Salary Budget Edit 37. 38. 39. 42. 43. 44. Version 600 Lock Salary Planning Budget Lock Next level Manager ID View View View Edit Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Salary Revision Guidelines” based on “Salary Revision Guidelines ID” Retrieve from entity Salary Revision based on Salary Revision ID. Derived after computing (Salary Budget - Actual CTC increase). Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve). Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. N N N C N N C View Default Value = “N” Valid values are Y or N Retrieved from entity Manager Salary Budget based on Approving Manager ID (employee ID of Manager) C Edit Valid values Y/N This field is Enabled only when the field Approval =”Y” N LS Software confidential document - Copyright © Protected. Page 72 of 109 High Level Design (HLD) Module 14 – Salary Planning 45. 46. 47. 48. 49. Next level Manager Name Next Level Manager email id Change Required Change details Edit Edit Edit Edit Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. This field is Enabled only when the field N Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. A value “Y” indicates a change is required. C Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Change Required =”N” Next Level Approved C M C Valid Values Y or N. Default Value = Y 50. 51. 52. Final level Manager ID Final level Manager Name Final Level Approved Edit Edit Edit This field is Enabled only when the field Final Next Level Approved =”Y” Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Next Level Approved =”Y” C Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final D Next Level Approved =”Y” Valid Values Y or N. Default Value = N Version 600 N LS Software confidential document - Copyright © Protected. Page 73 of 109 High Level Design (HLD) Module 14 – Salary Planning 53. Final Approved Date Edit 54. Business Unit Head ID Edit 55. Business Unit Head Name Edit 56. Business Unit Approved Edit 57. Business Unit Approval Date Edit Auto updated with System Date when field Final Level Approved = Y To input final approval date This field is Enabled only when the field Final C Level Approved = Y Pick the Business Unit Head ID (Employee ID) from entity Employee This field is Enabled only when the field Final C Level Approved = Y Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final D Level Approved = Y Valid Values Y or N. Default Value =N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button, the system should save the data to entity Salary Revision. 3. The Buttons “Sent Next Level”, and “Revise”, should be disabled 4. When the end user clicks the “Approve” Button :The system should display warning message “Locks Salary Planning and Will not allow modification ……Continue Y/N) If “Continue = N”, return to the previous screen, if “Continue = Y” execute the below mentioned actions. a) The system should send an email notification to the Next level Approval Manager” b) The system should update the field Lock Salary Planning=”Y”. c) Make all the field viewable as long as the field Lock Salary Planning=”Y” d) Disable Button “Approve” Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 74 of 109 High Level Design (HLD) Module 14 – Salary Planning Version 600 LS Software confidential document - Copyright © Protected. Page 75 of 109 High Level Design (HLD) Module 14 – Salary Planning User interface Version 600 LS Software confidential document - Copyright © Protected. Page 76 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Salary Revision Sr. No. 20. Req. ID 14.17A Purpose To approve the Salary revision Requirement 14.17A The managers at different levels should be able to view approved salary planning details (emp. name, current salary grade, new salary grade, current salary, new salary, the percentage raise, the allocated budget, balance budget positive or negative balance) and if required should be able to request revision of salary. The system should send a notification to the Approving Manager requesting necessary change. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “SALARY REVISION” Seq. No. 1. Field Name 2. Salary Revision Description Salary Revision Type ID View Salary Revision Type description Fiscal Period Start Date Fiscal Period End date Salary Revision Cycle ID View 8. Salary Revision Cycle View 9. Division ID View 3. 4. 5. 6. 7. Salary Revision ID Version 600 Edit/ View Edit Unit Particulars/ Validations/ Formulas Data Type N View Extract all the Salary Revision ID from entity Salary Revision Retrieve from entity Salary Revision based on Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID. The salary revision types e.g. Organization, Division/Department etc. Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date View To enter Fiscal Period End date View Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. Retrieve from entity Salary Revision based on Salary N Revision ID. View LS Software confidential document - Copyright © Protected. C N C D D Page 77 of 109 High Level Design (HLD) Module 14 – Salary Planning 10. Division Description Subdivision ID View Populate from entity “Division” based on Division ID. C View N View 16. Subdivision Description Approving Manager ID Approving Manager Name Approving Manager Email ID Salary Budget 17. Budget Lock View Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Subdivision” based on Subdivision ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Retrieve from entity Salary Revision based on Salary Revision ID. Retrieved from entity Manager Salary Budget based on Approving Manager ID (employee ID of Manager) -. 18. Balance Salary Budget View View View View View 19. Employee ID View 20. Employee Name View 21. Level ID View 22. 23. Level Description Grade ID View View 24. 25. Grade Description Revised Level View Edit 26. Revised Grade Version 600 Valid values Y/N Derived after computing (Salary Budget - Actual CTC increase). N C C N C N Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve). Retrieve from entity Salary Revision based on Salary Revision ID. All Employee codes whose “Salary Revision Date” fall within the “Fiscal Period Start Date” and “Fiscal Period End date” Populate from entity “Employee” based on Employee ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Level” based on “Level ID” Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Grade” based on “Grade ID” Pick from the entity Level. Note: The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Pick from the entity Grade. Note: LS Software confidential document - Copyright © Protected. C Page 78 of 109 N C N C N C C C High Level Design (HLD) Module 14 – Salary Planning 27. Salary Revision Category ID View The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Retrieve from entity Salary Revision based on Salary Revision ID. N For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 28. Salary Revision Category View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. Annual Raise, C Promotions, Confirmation, Significant Achievement etc. 29. View 30. Performance Rating Salary Level ID 31. Current CTC View 32. Percentage Raise View 33. Revised CTC View 34. Actual CTC increase Approved View Compute the difference of (Revised CTC-Current CTC) N Edit This field is Enabled only when the field Change required=”N” C View Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Derived by computing i.e. Revised CTC = V N N N N ((Current CTC * Percentage Raise) + Current CTC) 35. 36. 37. 38. 39. 40. 41. Last Salary Revision Date Last Salary Revision Category ID View Last Salary Revision Category Description View Level/grade Salary start Range Level/grade Salary end Range Salary Revision Guidelines ID View Version 600 View Valid Values Y or N. Default Value = Y Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. N For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. Retrieve from entity Salary Revision based on Salary Revision ID. C For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. View View Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. LS Software confidential document - Copyright © Protected. Page 79 of 109 N N N High Level Design (HLD) Module 14 – Salary Planning 42. 43. 44. 45. 46. 47. 48. 49. Salary Revision Guidelines Lock Salary Planning Next level Manager ID Next level Manager Name Next Level Manager email id Change Required Change details View Edit Populate from entity “Salary Revision Guidelines” based on “Salary Revision Guidelines ID” Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. Edit Default Value = “N” Valid values are Y or N This field is Enabled only when the field Approval =”Y” Edit Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approved =”Y” Edit Populate from entity Employee based on Next level Approval Manager ID. This field is Enabled only when the field Approved =”Y” Edit Populate from entity Employee based on Next level Approval Manager ID. A value “Y” indicates a change is required. Edit Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Change Required =”N” Next Level Approved Valid Values Y or N. Default Value = Y 50. 51. Final level Manager ID Final level Manager Name Edit Edit This field is Enabled only when the field Final Next Level Approved =”Y” Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Next Level Approved =”Y” Populate from entity Employee based on Final level Approval Manager ID. Version 600 LS Software confidential document - Copyright © Protected. Page 80 of 109 C C M High Level Design (HLD) Module 14 – Salary Planning 52. Final Level Approved Edit 53. Final Approved Date Edit 54. Business Unit Head ID Edit 55. Business Unit Head Name Edit 56. Business Unit Approved Edit 57. Business Unit Approval Date Edit This field is Enabled only when the field Final Next Level Approved =”Y” Valid Values Y or N. Default Value = N Auto updated with System Date when field Final Level Approved = Y To input final approval date This field is Enabled only when the field Final Level Approved = Y Pick the Business Unit Head ID (Employee ID) from entity Employee This field is Enabled only when the field Final Level Approved = Y Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Level Approved = Y Valid Values Y or N. Default Value =N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button the system should save the data to entity Salary Revision 3. The Button “Approve” should be disabled 4. System should check the value in the field “Change Required” If the field Change Required = “Y” a) Disable the Button “Sent Next Level” b) Enable the Button “Revise” 5. When the end user clicks the “Revise” Button:a) The system should send an email notification to the Approving Manager with list of employees for change in Salary Revision. b) The system should insert a record in entity Salary Revision Approval History and update the fields as shown in the table below:Entity “SALARY REVISION APPROVAL HISTORY” Updated from Entity Salary Revision Seq. No. 1. Version 600 Field Name Salary Revision Approval ID Edit/ View Edit Unit Particulars/ Validations/ Formulas Unique ID (Auto generated) To uniquely identify Salary Revision Approval LS Software confidential document - Copyright © Protected. Page 81 of 109 Data Type N High Level Design (HLD) Module 14 – Salary Planning 2. 3. 4. 5. 6. Salary Revision ID Salary Revision Description Next Level Approval Manager ID Change request Date Change details Edit View Edit Edit Edit To input Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID Updated from field Next Level Approval Manager ID of Entity Salary Revision System updates this field with System Date Updated from field Change Detail of Entity Salary Revision Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 82 of 109 N C N D M High Level Design (HLD) Module 14 – Salary Planning Version 600 LS Software confidential document - Copyright © Protected. Page 83 of 109 High Level Design (HLD) Module 14 – Salary Planning User interface Version 600 LS Software confidential document - Copyright © Protected. Page 84 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Salary Revision Sr. No. 21 Req. ID 14.17B Purpose To review and raise change request. Requirement 14.17B The Managers at different levels should be able to view approved salary planning details (emp. name, current salary grade, new salary grade, current salary, new salary, the percentage raise, the allocated budget, balance budget positive or negative balance) and if no change is required Should be able to send it to next level of approval. A notification email should be sent to the next level approval. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface The notification mails should contain the details highlighted in bold. ENTITY = “SALARY REVISION” Seq. No. 1. Field Name 2. Salary Revision Description Salary Revision Type ID View Salary Revision Type description Fiscal Period Start Date Fiscal Period End date Salary Revision Cycle ID View 3. 4. 5. 6. 7. 8. Version 600 Salary Revision ID Edit/ View Edit Unit Particulars/ Validations/ Formulas View Extract all the Salary Revision ID from entity Salary Revision Retrieve from entity Salary Revision based on Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID. The salary revision types e.g. Organization, Division/Department etc. Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date View To enter Fiscal Period End date View Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. View Salary Revision Cycle View LS Software confidential document - Copyright © Protected. Data Type N C N C D D Page 85 of 109 High Level Design (HLD) Module 14 – Salary Planning 9. Division ID View 10. Division Description View 11. Subdivision ID View 12. Subdivision Description Approving Manager ID Approving Manager Name View 15. Approving Manager Email ID View 16. Salary Budget View 17. Budget Lock View 13. 14. 18. Balance Salary Budget View View View 19. Employee ID View 20. Employee Name View 21. Level ID View 22. Level Description View 23. Grade ID View 24. Grade Description View 25. Revised Level Edit Version 600 Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Division” based on Division ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Subdivision” based on Subdivision ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Retrieve from entity Salary Revision based on Salary Revision ID. Retrieved from entity Manager Salary Budget based on Approving Manager ID (employee ID of Manager) Valid values Y/N Derived after computing (Salary Budget - Actual CTC increase). Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve). Retrieve from entity Salary Revision based on Salary Revision ID. All Employee codes whose “Salary Revision Date” fall within the “Fiscal Period Start Date” and “Fiscal Period End date” Populate from entity “Employee” based on Employee ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Level” based on “Level ID” Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Grade” based on “Grade ID” Pick from the entity Level. LS Software confidential document - Copyright © Protected. Page 86 of 109 N C N C N C C N C N N C N C N C C High Level Design (HLD) Module 14 – Salary Planning 26. Revised Grade 27. Salary Revision Category ID View Note: The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Pick from the entity Grade. Note: The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Retrieve from entity Salary Revision based on Salary Revision ID. C N For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 28. Salary Revision Category View 29. Performance Rating View 30. Salary Level ID View 31. Current CTC View 32. Percentage Raise View 33. Revised CTC View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. Annual Raise, Promotions, C Confirmation, Significant Achievement etc. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Derived by computing i.e. Revised CTC = V N N N N ((Current CTC * Percentage Raise) + Current CTC) 34. Actual CTC increase View 35. Approved Edit 36. 37. Last Salary Revision Date Last Salary Revision Category ID View View Compute the difference of (Revised CTCCurrent CTC) This field is Enabled only when the field Change required=”N” Valid Values Y or N. Default Value = Y Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. N C N For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 38. Version 600 Last Salary Revision Category Description View Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. LS Software confidential document - Copyright © Protected. Page 87 of 109 C High Level Design (HLD) Module 14 – Salary Planning-. 43. 44. 45. 46. 47. 48. 49. Level/grade Salary start Range Level/grade Salary end Range Salary Revision Guidelines ID Salary Revision Guidelines View Lock Salary Planning Edit Next level Manager ID Next level Manager Name Next Level Manager email id Change Required Change details Next Level Approved View View View Edit Edit Edit Edit Edit Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Salary Revision Guidelines” based on “Salary Revision Guidelines ID” Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. N N C Default Value = “N” Valid values are Y or N This field is Enabled only when the field Approval =”Y” Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. A value “Y” indicates a change is required. Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Change Required =”N” Valid Values Y or N. Version 600 N LS Software confidential document - Copyright © Protected. Page 88 of 109 C M High Level Design (HLD) Module 14 – Salary Planning Default Value = Y 50. 51. 52. Final level Manager ID Final level Manager Name Edit Edit Final Level Approved Edit 53. Final Approved Date Edit 54. Business Unit Head ID Edit 55. Business Unit Head Name Edit 56. Business Unit Approved Edit 57. Business Unit Approval Date Edit This field is Enabled only when the field Final Next Level Approved =”Y” Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Next Level Approved =”Y” Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Next Level Approved =”Y” Valid Values Y or N. Default Value = N Auto updated with System Date when field Final Level Approved = Y To input final approval date This field is Enabled only when the field Final Level Approved = Y Pick the Business Unit Head ID (Employee ID) from entity Employee This field is Enabled only when the field Final Level Approved = Y Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Level Approved = Y Valid Values Y or N. Default Value =N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button the system should save the data to entity Salary Revision 3. The Button “Approve” should be disabled 4. System should check the value in the field “Next Level Approval Required” If the field Next Level Approval Required = “Y” a) Disable the Button “Revise” Version 600 LS Software confidential document - Copyright © Protected. Page 89 of 109 High Level Design (HLD) Module 14 – Salary Planning b) Enable the Button “Sent Next Level” 5. When the end user clicks the “Sent Next Level” Button:a) The system should send an email notification to the Next level Approval Manager for review and approval. b) The system should insert a record in entity Salary Revision Approval History and update the fields as shown in the table below:- Entity “Salary Revision Approval History” Updated from Entity Salary Revision Seq. No. 1. 2. 3. 4. 5. Field Name Salary Revision Approval ID Salary Revision ID Salary Revision Description Next Level Approval Manager ID Approval Date Edit/ View Edit Edit View Edit Edit Unit Particulars/ Validations/ Formulas Unique ID (Auto generated) To uniquely identify Salary Revision Approval To input Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID Updated from field Next Level Approval Manager ID of Entity Salary Revision System updates this field with System Date Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 90 of 109 Data Type N N C N D High Level Design (HLD) Module 14 – Salary Planning Version 600 LS Software confidential document - Copyright © Protected. Page 91 of 109 High Level Design (HLD) Module 14 – Salary Planning User interface Version 600 LS Software confidential document - Copyright © Protected. Page 92 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Salary Revision Sr. No. 22. Req. ID 14.18 Purpose To review and approve the salary revision. Requirement 14.18 System should be able to send a notification email to HR, and Business Unit Head, when the final authority approves the salary planning. On approval of the salary planning by final authority, a notification mail has to be sent to HR, Business Unit Head, approving manager, and to the immediate superior of the approving manager. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface The notification mails should contain the details highlighted in bold. ENTITY = “SALARY REVISION” Seq. No. 1. Field Name 2. Salary Revision Description Salary Revision Type ID View Salary Revision Type description Fiscal Period Start Date Fiscal Period End date Salary Revision Cycle ID View 8. Salary Revision Cycle View 9. Division ID View 3. 4. 5. 6. 7. Version 600 Salary Revision ID Edit/ View Edit Uni t Particulars/ Validations/ Formulas View Extract all the Salary Revision ID from entity Salary Revision Retrieve from entity Salary Revision based on Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID. The salary revision types e.g. Organization, Division/Department etc. Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date View To enter Fiscal Period End date View Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. Retrieve from entity Salary Revision based on Salary Revision ID. View LS Software confidential document - Copyright © Protected. Data Type N C N C D D Page 93 of 109 N High Level Design (HLD) Module 14 – Salary Planning 10. Division Description Subdivision ID View Subdivision Description Approving Manager ID Approving Manager Name View 15. Approving Manager Email ID View 16. Salary Budget View 17. Budget Lock View -. 18. Balance Salary Budget View View View View 19. Employee ID View 20. Employee Name View 21. Level ID View 22. 23. Level Description Grade ID View View 24. Grade Description View 25. Revised Level Edit Version 600 Populate from entity “Division” based on Division ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Subdivision” based on Subdivision ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Retrieve from entity Salary Revision based on Salary Revision ID. Retrieved from entity Manager Salary Budget based on Approving Manager ID (employee ID of Manager) Valid values Y/N Derived after computing (Salary Budget - Actual CTC increase). Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve). Retrieve from entity Salary Revision based on Salary Revision ID. All Employee codes whose “Salary Revision Date” fall within the “Fiscal Period Start Date” and “Fiscal Period End date” Populate from entity “Employee” based on Employee ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Level” based on “Level ID” Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Grade” based on “Grade ID” Pick from the entity Level. Note: LS Software confidential document - Copyright © Protected. Page 94 of 109 C N C N C C N C N N C N C N C C High Level Design (HLD) Module 14 – Salary Planning 26. Revised Grade 27. Salary Revision Category ID View The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Pick from the entity Grade. Note: The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Retrieve from entity Salary Revision based on Salary Revision ID. C N For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 28. Salary Revision Category View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. C Annual Raise, Promotions, Confirmation, Significant Achievement etc. 29. View 30. Performance Rating Salary Level ID 31. Current CTC View 32. Percentage Raise View 33. Revised CTC View View Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Derived by computing i.e. Revised CTC = V N N N N ((Current CTC * Percentage Raise) + Current CTC) 34. 35. 36. 37. 38. Version 600 Actual CTC increase Approved View Edit Last Salary Revision Date Last Salary Revision Category ID View Last Salary Revision Category Description View View Compute the difference of (Revised CTC-Current CTC) This field is Enabled only when the field Change required=”N” Valid Values Y or N. Default Value = Y Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. N C N For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. LS Software confidential document - Copyright © Protected. Page 95 of 109 C High Level Design (HLD) Module 14 – Salary Planning-. 43. 44. 45. 46. 47. 48. 49. Level/grade Salary start Range Level/grade Salary end Range Salary Revision Guidelines ID Salary Revision Guidelines View Lock Salary Planning Edit Next level Manager ID Next level Manager Name Next Level Manager email id Change Required Change details Next Level Approved View View View Edit Edit Edit Edit Edit Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Salary Revision Guidelines” based on “Salary Revision Guidelines ID” Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. N N C Default Value = “N” Valid values are Y or N This field is Enabled only when the field Approval =”Y” Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. A value “Y” indicates a change is required. Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Change Required =”N” Valid Values Y or N. Default Value = Y Version 600 N LS Software confidential document - Copyright © Protected. Page 96 of 109 C M High Level Design (HLD) Module 14 – Salary Planning 50. 51. 52. Final level Manager ID Final level Manager Name Final Level Approved Edit Edit Edit 53. Final Approved Date Edit 54. Business Unit Head ID Edit 55. Business Unit Head Name Edit 56. Business Unit Approved Edit 57. Business Unit Approval Date Edit This field is Enabled only when the field Final Next Level Approved =”Y” Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Next Level Approved =”Y” Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Next Level Approved =”Y” Valid Values Y or N. Default Value = N Auto updated with System Date when field Final Level Approved = Y To input final approval date This field is Enabled only when the field Final Level Approved = Y Pick the Business Unit Head ID (Employee ID) from entity Employee This field is Enabled only when the field Final Level Approved = Y Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Level Approved = Y Valid Values Y or N. Default Value =N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button the system should save the data to entity Salary Revision 3. The Button “Approve” should be disabled 4. System should check the value in the field “Final Approval” If the field Final Approval = “Y” a) The system should send an email notification to the HR manager Version 600 LS Software confidential document - Copyright © Protected. Page 97 of 109 High Level Design (HLD) Module 14 – Salary Planning b) The system should sent an email notification to the Approving Manager c) The system should sent an email notification to the Immediate Manager of the Approving Manager. [Note: In the entity “Employee”, the immediate manager of the employee is value in the field “Reporting Manager”] 5. If the field Business unit Approval required = “Y”, a) The system should send an email notification to the Business Unit Head. Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 98 of 109 High Level Design (HLD) Module 14 – Salary Planning User interface Version 600 LS Software confidential document - Copyright © Protected. Page 99 of 109 High Level Design (HLD) Module 14 – Salary Planning Version 600 LS Software confidential document - Copyright © Protected. Page 100 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Salary Revision Sr. No. 23. Req. ID 14.19 Purpose To review and approve the salary revision. Requirement 14.19 BU’s (Business Units) Should be able to send notification mail to HR when salary planning is completed for the BU. ***Please Note: The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface The notification mails should contain the details highlighted in bold. ENTITY = “SALARY REVISION” Seq. No. 1. Field Name Salary Revision ID Edit/ View Edit 2. Salary Revision Description View 3. Salary Revision Type ID View 4. View 5. 6. 7. Salary Revision Type description Fiscal Period Start Date Fiscal Period End date Salary Revision Cycle ID 8. Salary Revision Cycle View 9. Division ID View 10. Division Description View 11. Subdivision ID View Version 600 View View View Unit Particulars/ Validations/ Formulas Extract all the Salary Revision ID from entity Salary Revision Retrieve from entity Salary Revision based on Salary Revision ID Retrieve from entity Salary Revision based on Salary Revision ID. The salary revision types e.g. Organization, Division/Department etc. Populate from entity Salary Revision Type based on Salary Revision Type ID To enter Fiscal Period Start Date To enter Fiscal Period End date Retrieve from entity Salary Revision based on Salary Revision ID. For e.g. of Salary revision cycle are e Annual, Half yearly etc. Populate from entity “Salary Revision Cycle” based on Salary Revision Cycle ID. For e.g. like Annual, Half yearly etc. Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Division” based on Division ID. Retrieve from entity Salary Revision based on Salary Revision ID. LS Software confidential document - Copyright © Protected. Page 101 of 109 Data Type N C N C D D N C N High Level Design (HLD) Module 14 – Salary Planning 12. Subdivision Description View 13. Approving Manager ID View 14. Approving Manager Name View 15. Approving Manager Email ID View 16. Salary Budget View 17. Budget Lock View 18. Balance Salary Budget View 19. Employee ID View 20. Employee Name View 21. Level ID View 22. Grade ID View 23. Revised Level ID Edit 24. Level Description View 25. Revised Grade ID Version 600 Populate from entity “Subdivision” based on Subdivision ID Retrieve from entity Salary Revision based on Salary Revision ID. Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Populate from entity “Employee” based on Approving Manager ID (Employee ID of the Approving manager). Retrieve from entity Salary Revision based on Salary Revision ID. Retrieved from entity Manager Salary Budget based on Approving Manager ID (employee ID of Manager) Valid values Y/N Derived after computing (Salary Budget - Actual CTC increase). Note: If the Budget Lock is “Y” the system should warn the end user/manager when the Balance Salary Budget goes negative (-ve). Retrieve from entity Salary Revision based on Salary Revision ID. All Employee codes whose “Salary Revision Date” fall within the “Fiscal Period Start Date” and “Fiscal Period End date” Populate from entity “Employee” based on Employee ID Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Pick from the entity Level. Note: The Employee Level is Revised, only in case promotions etc., otherwise this field is populate with employees current Level. Populate from entity “Level” based on “Revised Level ID” Pick from the entity Grade. Note: LS Software confidential document - Copyright © Protected. Page 102 of 109 C N C C N C N N C N N C C C High Level Design (HLD) Module 14 – Salary Planning 26. Grade Description View 27. Salary Revision Category ID View The Employee grade is Revised, only in case promotions etc., otherwise this field is populate with employees current grade. Populate from entity “Grade” based on “Revised Grade ID” Retrieve from entity Salary Revision based on Salary Revision ID. C N For e.g. Annual Salary review, Promotions, Confirmation, Significant Achievement etc. 28. Salary Revision Category View Populate from entity “Salary Revision Category” based on Salary Revision Category ID. For e.g. C Annual Raise, Promotions, Confirmation, Significant Achievement etc. 29. Performance Rating View 30. Salary Level ID View 31. Current CTC View 32. Percentage Raise View 33. Revised CTC View Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. Derived by computing i.e. Revised CTC = V N N N N ((Current CTC * Percentage Raise) + Current CTC) 34. Actual CTC increase View 35. Approved Edit 36. Last Salary Revision Date View 37. Last Salary Revision Category ID View Compute the difference of (Revised CTC-Current CTC) This field is Enabled only when the field Change required=”N” Valid Values Y or N. Default Value = Y Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. N C N For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 38. Last Salary Revision Category Description View Retrieve from entity Salary Revision based on Salary Revision ID. C For e.g. Annual Raise, Promotions, Confirmation, Significant Achievement etc. 39. 40. Level/grade Salary start Range Level/grade Salary end Range Version 600 View View Retrieve from entity Salary Revision based on Salary Revision ID. Retrieve from entity Salary Revision based on Salary Revision ID. LS Software confidential document - Copyright © Protected. Page 103 of 109 N N High Level Design (HLD) Module 14 – Salary Planning 41. View 42. Salary Revision Guidelines ID Salary Revision Guidelines 43. Lock Salary Planning Edit 44. 45. 46. 47. 48. 49. Next level Manager ID Next level Manager Name Next Level Manager email id Change Required Change details View Edit Edit Edit Edit Edit Retrieve from entity Salary Revision based on N Salary Revision ID. Populate from entity “Salary Revision C Guidelines” based on “Salary Revision Guidelines ID” Note: This is field is updated by the system to “Y”, when the Approving manager, clicks the “Approve” Button. Default Value = “N” Valid values are Y or N This field is Enabled only when the field Approval =”Y” Pick the Next level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. This field is Enabled only when the field Approved =”Y” Populate from entity Employee based on Next level Approval Manager ID. A value “Y” indicates a change is required. Valid values Y or N Default = “N” This field is Enabled only when the field Change Required =”Y” To input the change details to the salary revision. Note: This field is input only be the next levels and not the approving manager. This field is Enabled only when the field Change Required =”N” Next Level Approved Valid Values Y or N. Default Value = Y 50. Final level Manager ID Version 600 Edit This field is Enabled only when the field Final Next Level Approved =”Y” LS Software confidential document - Copyright © Protected. Page 104 of 109 C M High Level Design (HLD) Module 14 – Salary Planning 51. 52. Final level Manager Name Final Level Approved Edit Edit 53. Final Approved Date Edit 54. Business Unit Head ID Edit 55. Business Unit Head Name Edit 56. Business Unit Approved Edit 57. Business Unit Approval Date Edit Pick the Final level Approval Manager ID (Employee ID) from entity Employee This field is Enabled only when the field Final Next Level Approved =”Y” Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Next Level Approved =”Y” Valid Values Y or N. Default Value = N Auto updated with System Date when field Final Level Approved = Y To input final approval date This field is Enabled only when the field Final Level Approved = Y Pick the Business Unit Head ID (Employee ID) from entity Employee This field is Enabled only when the field Final Level Approved = Y Populate from entity Employee based on Final level Approval Manager ID. This field is Enabled only when the field Final Level Approved = Y Valid Values Y or N. Default Value =N Auto updated with System Date when field Business Unit Approval = Y To input final approval date Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. 2. When the end user clicks “Save” Button the system should save the data to entity Salary Revision 3. The Button “Approve” should be disabled 4. System should check the value in the field “Business Unit Approved” If the field Business Unit Approved = “Y” a) The system should send an email notification to the HR manager stating the completion of salary revision planning process for the Business Unit. Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 105 of 109 High Level Design (HLD) Module 14 – Salary Planning User interface Version 600 LS Software confidential document - Copyright © Protected. Page 106 of 109 High Level Design (HLD) Module 14 – Salary Planning Entities accessed Entity Name Salary Revision Sr. No. 24. Req. ID 14.20 Purpose To review and approve the salary revision. Requirement 14.20 HR should be able to view the salary planning module, the budget allocated for salary planning and the budget balance remaining after allocation to all the department. ***Please Note: Version 600 LS Software confidential document - Copyright © Protected. Page 107 of 109 High Level Design (HLD) Module 14 – Salary Planning The end user should be able to input/modify values only for the “Field Names” which is marked as “Edit”. Any “Fields Names” highlighted in yellow should not be visible in the user interface ENTITY = “MANAGER SALARY BUDGET” Seq. No. 14. Field Name Budget Year Edit/ View Edit 15. Division ID Edit 16. Division Name View 17. Subdivision ID Edit 18. Subdivision Name View 19. Manager Employee ID Edit 20. Manager Name View 21. Manager Salary Budget ID Edit 22. Edit 23. 24. 25. Manager Salary Budget Description Job Title ID Salary Budget Balance Salary Budget 26. Budget Lock Edit Edit Edit Edit Unit Particulars/ Validations/ Formulas To input the budget fiscal Year. E.g. Jan 2013-Dec 2013, or April 2013-March 2014 Populate from entity “Employee” based on Manager’s Employee ID Populate from entity Division Based on Division ID Populate from entity “Employee” based on Manager’s Employee ID Populate from entity Subdivision Based on Subdivision ID Pick the Manager’s Employee ID from the entity “Employee” filtered on Job Title ID Populate from entity “Employee” based on Manager’s Employee ID Retrieved based on field Budget Year and Manager Employee ID from entity Manager Salary Budget Description of the Salary Budget Pick the job title from the entity “Job title” To input Salary Revision Budget System Computed field. This field shows the balance of Salary Budge, after salary revision. Valid values “Y” or “N” Default Value= “Y” To Lock the budget, so the salary revision planning does not exceed the allocated salary budget. Note: C = character, D= Date, N= Numeric, M=Memo, V= Variant Workflows 1. When the end user clicks “Cancel” Button, the system should discard the data. Process Flow Version 600 LS Software confidential document - Copyright © Protected. Page 108 of 109 Data Type C C N C N C N C N N N C High Level Design (HLD) Module 14 – Salary Planning User interface Entities accessed Entity Name Manager Salary Budget Version 600 Purpose HR to view budget allocated for salary planning and the budget balance remaining after allocation LS Software confidential document - Copyright © Protected. Page 109 of 109