SAP ABAP IMG Activity OHAGB_SA601 (Solution Changeover Date: GBSxP Phase II)
Hierarchy
☛ SAP_HRCGB (Software Component) Sub component SAP_HRCGB of SAP_HR
   ⤷ PY-GB (Application Component) United Kingdom
     ⤷ PC08 (Package) HR accounting: GB
IMG Activity
ID OHAGB_SA601 Solution Changeover Date: GBSxP Phase II  
Transaction Code S_AC0_52000157   (empty) 
Created on 20041119    
Customizing Attributes OHAGB_SA601   Solution Changeover Date: GBSxP Phase II 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAGB_SA601    

Use

In the process of migrating to the new GBSxP Phase II absence processing solution, you must define changeover dates for each of your employee groups. You maintain feature GBCHG to achieve this.

You must define changeover dates for each of the specific solution types that you wish to migrate, where the migration to GBSxP Phase II is controlled by this feature.

The solutions that have been changed are defined by the decision field CHGTY. The solutions that have changed for GBSxP are as follows:

  • 001 New QDP Solution
  • 002 New Changes across End-of-Year Solution

Activities

001 New QDP Solution (GBSxP Phase II)

The new QDP solution is activated by setting the return value of feature GBCHG to a date after which you wish feature GBQDP to be used to derive the employee's SSP Qualifying Day Pattern (QDP).

From this date onwards, whenever an employee's QDP is derived, it will be derived using feature GBQDP.

002 New Changes across End-of-Year Solution (GBSxP Phase II)

The new Changes across End-of-Year solution is activated by setting the return value of feature GBCHG to the start of the financial year (06.04.YYYY) from which you wish payroll function GBSXP to handle changes across End-of-Year.

From this date onwards, whenever SxP amounts are changed retrospectively across a Tax Year, GBSXP will handle the differences and store them in table MSAX.

Note:

At present, feature GBCHG is only used as part of the migration to GBSxP Phase II absence processing. However, it may include other payroll solutions at a later date.

Therefore, this customising step resides in a generic location in the Great Britain Payroll IMG. You access this step under: Tools -> Define Solution Changeover Date.

Further Information

  • For each of your employee groups, you must define a changeover date for each of the new solutions that are controlled by this feature. The decision field CHGTY is mandatory and should be defined at the highest level of the decision tree. The changeover date must be in the format DD.MM.YYYY.
  • Feature GBCHG is delivered with each changeover date set to 31.12.9999. Therefore, the new solutions will not be activated by default. Instead, SAP delivers feature GBCHG with the changeover date set to 31.12.9999 to ensure that you activate this function via a customising change.
  • If you have activated GBSxP Phase II and an "SSP'able" absence is processed by the payroll function GBSXP, then the employee is rejected from payroll if the date specified is not in the correct format.

    Even if you activate GBSxP Phase II, the new QDP functionality will not automatically be activated as the return value date is pre-delivered as 31.12.9999 in this release, as noted above.

  • In the higher releases 5.00 and 6.00 (ERP 2004 and 2005 respectively), the return value for CHGTY 001 in feature GBCHG is delivered as 01.01.1800. This ensures that the QDP solution is active immediately for any new SAP customer. However, any customers upgrading to these two releases will retain the settings for this feature from their previous release.
  • In all releases, the return value for CHGTY 002 in feature GBCHG is delivered as 31.12.9999. This ensures that you must modify this return value to 06.04.YYYY (where YYYY is 2006 or later) when you implement GBSXP Phase II.
  • If you have activated GBSxP Phase II but have not customised the return value of the feature as 06.04.YYYY (where YYYY is 2006 or later), then as the employee is processed by the payroll function GBSXP, then the employee is rejected from payroll as the date specified is not in the correct format.

Example

001 New QDP Solution (GBSXP Phase II)

Scenario 1:

You implement SAP for the first time and wish to load SSP historical absences and convert them using the program RPLABSG0_SXP_OXP_CONV. You set the change-over date to a date early enough to ensure that all historical sicknesses are processed using the new QDP tables solution (that is, you will use feature GBQDP immediately). Therefore, you set this date to 01.01.1800.

Scenario 2:

You are a long-term SAP customer and have no intention of loading SxP historical absences or converting them using the program RPLABSG0_SXP_OXP_CONV. However, you do not want to historically switch to the new QDP solution as this may highlight differences during retroactive payrolls. Therefore, you only wish to start using the new QDP solution from a specific date.

In this situation, you simply set the return value of the feature for all your employee groups to the same date, that is, the start date of any month following your current payroll period.

002 New Change Across End of Year Solution (GBSXP Phase II)

Scenario 1:

You are implementing GBSxP Phase II for the first time (either during an upgrade, initial implementation or a part of a planned migration) and receive the following error message in payroll informing you that an incorrect return value has been specified.

"Return Value 31.12.9999 is not in the format 06.04.YYYY (Feature GBCHG)"

Scenario 2:

You implemented GBSxP Phase II previously (either during an upgrade, initial implementation or a part of a planned migration) and receive the following error message in payroll informing you that an incorrect return value has been specified.

"Return Value 31.12.9999 is not in the format 06.04.YYYY (Feature GBCHG)"

In either of these scenarios, you must set the return date to the start of the NEXT financial year.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
OHAGB_SA601 GB United Kingdom
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHAGB_SA601 0 HLA0009562 Absences 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20050428 
SAP Release Created in