Ansicht
Dokumentation

OHAGOSP001B03 - Employee "go live" date definition

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

In this step you define the "go live" dates for your various employee groups.

The feature GLIVE allows the selection of a specific date when an employee should be considered as LIVE on the new Absence Evaluation functionality. Before the Go-Live date, Absence Evaluation history in the payroll structure COVER will not be generated (neither during payroll, Absence entry (2001) nor during reporting.)

On and After the Go-Live date Absence Evaluation history in the payroll structure COVER will be generated.

This implies Go-Live dates can be any valid date from 01.01.1800 to 31.12.9999. Obviously in most cases the date chosen will normally be reasonably close to the current system date.

IMPORTANT: the dates are entered in the format YYYYMMDD.

Using Absence Subtype in your decision tree is NOT advised. The problems with making the feature absence subtype specific are not obvious, but do limit the completeness of this solution. In ALL conversion programs, you are advised to keep your processing as simple as possible. Manual amendment to a few records is better than bending the conversion routines, which will make them slower, more prone to errors and more complex to understand exactly how the converted data got where it did.

Absences cannot overlap in the new Absence Evaluation solution, so there should be no need to ever have two Go-Live dates for one employee.

[You may wish to specify that an employee's Maternity absence Go-Live date is 01.01.2006 and an employee's Sickness absence Go-Live date is 01.10.2005. This could be because the employee has been on maternity leave from 01.07.2005 to 01.01.2006 and the rest of the employee's grouping has a Go-Live date of 01.10.2005. The Maternity record should be split in P2001 as two Maternity Records using the correct absence subtypes to support the old and new solutions, then the 01.10.2005 Go Live date can be used as normal.

Alternatively, the Go Live date for the employee can be extended to after the maternity has finished, then the 01.01.2006 Go Live date can be used.]

If two Go Live dates are derived for an employee due to an organisational change or similar during their absence history, then the LATEST is used. That is, the employee goes "live" only after allof their organisational assignments have gone "live". A warning will be issued if this occurs.

Also if an employee's LATEST Go Live date spans an infotype 2001record, then he or she will be rejected by the conversion routine and payroll and generate infotype 2001errors.

If all of your employees in Great Britain are "Going-Live" on the 1st January 2006, then decision tree should make a decision on MOLGA being 08, and if it is 08, then the return value should be 20060101.

Vendor Master (General Section)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3004 Date: 20240523 Time: 192415     sap01-206 ( 73 ms )