3132021 - Effective Dated Time Profile - 2H 2023

• Effective-Dated Time Profile feature allows users to make effective-dated changes to the Time Profile object, such as adding or removing time types on a certain date.
• Instead of creating a new time profile and adding an effective-dated entry in the job information of the employee, you can do the change only once in the Time Profile object for all users assigned to that time profile.
• Effective dating ensures that there is no time gap between records and enables you to track historical data accurately.
• From 2H 2023, all Time Profiles will be effective dated by default. (Refer What's New Viewer)

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors Employee Central - Time Off

Important Notes

After the migration to effective-dated Time Profile, the following changes are done automatically:

• The effective dated setting for the Time Profile object will be changed from None to Basic.
• Role-based Permissions are migrated. View permission will be migrated to View History and View Current. Edit permission will be migrated to Create, Correct, Insert and Delete. 
• The effective-dated start date of the Time Profile object is set to editable and will show January 1 1900 for all existing Time Profiles.
• The effective status of the Time Profile object is set to editable.

Mandatory manual steps

API change

• A non-effective dated object only includes externalCode as the key property for the OData V2 API. With the transition to Basic Effective Dating, this structure changes and the key property becomes both the externalCode and effectiveStartDate for the object.
• We do not recommend using the previous OData V2 API syntax with only the key property as externalCode to read data (GET), because it will fail when the object has Effective Dating Basic.
• To ensure a smooth transition for custom integrations built that read using the OData V2 APIs on these objects, the following is required:
  • Adapt OData V2 APIs (GET) built on the Time Profile and Work Schedule objects which use only the key property in the syntax to read the data with the $filter syntax, by First Half 2023 Release.
• If you do not use the key syntax for read APIs, there are no issues, and no adjustments are required.  Please read the 'How to Adapt APIs' section to verify this.

Determine Whether You Are Impacted

1. Are there any custom integrations built for read scenarios using APIs using only the key syntax on  the Time Profile object?
2. Do you have plans to build custom integrations for read scenarios using the Time Profile  object?
3. For a new implementation, please use the APIs as per the 'How to Adapt APIs' section below:

Based on your response, please plan to adjust your APIs as described below.

How to Adapt APIs?

• Analyze the custom integration you have built on the Time Profile object for the read scenarios using GET OData calls which use the key syntax.
• Please refer to the following customer community page for more details.

Important Topics To Take Care

Import Template

• As the Time Profile is now effective-dated, the import template ("Import and Export Data") is changed. With effective dating the new field "mdfSystemEffectiveStartDate" is added to the template. This means that, if you want to import Time Profiles, you have to download the current version of the import template.

• This means that, if you want to import Time Profiles, you have to download the current version of the import template as shown below and use this template to prepare the import files:

  

Instance Sync

• If the Instance sync tool is used, then it must be ensured that both the source and target systems have the same settings for "Effective Dating" in the Time Profile object.
• For example: If the Time Profile object is set with Effective Dating as "Basic" in the source system by means of the Upgrade Center task, then the following must be ensured in the target instance:

1. 1. First, the upgrade center task must be successfully executed in the target system.
   2. Only afterward should the instance sync be triggered from the source instance.

• If you don't follow the above process, then Instance Sync will fail and it will not be possible to copy Time Profile using the tool.

Instance Refresh

• For any issues related to Instance Sync or Instance Refresh, please raise a case to support in the component LOD-SF-PLT

Reports

If you have built a custom report using SAP Analytics Cloud (SAC) and have in the report's output the Time profile's name or code being shown, then please note the following:

1. 1. Go to the report and click on ‘Edit’
   2. Select Edit Data Source
   3. Click on ‘Finish’
   4. Save the report once again and
   5. Execute the report to fetch proper results.

The above steps help rebuild the schema of the report and takes into account the effective dated nature of the Time Profile.

NOTE: For any issues with the SAC report, please raise a case to support in the component LOD-SF-ANA.

What Is Not Supported?

• Effective dating is not supported for standard leave of absence (LOA), only Time Profile with external code LEAVE_OF_ABSENCE_PROFILE. This means you are not allowed to create multiple records on this Time Profile. In addition, 1st January 1900 will always be set as the effective start date.
• If you use Time Account Types with flexible account start date, you have to be careful: A Time Type referring to a Time Account Type with flexible account start date can only be assigned once to the Time Profile. You cannot remove it and assign it again if there are already Time Accounts created (this means the specific object Time Account Type Date Reference exists) for a user for this Time Account Type. Please keep in mind that activating a deactivated slice on the Time Profile is handled the same way as adding Time Types.

Limitations

In the check tool, while using parameters, the following limitations currently exist:

• If a new time slice is inserted to the Time Profile object results into removal of a time account type associated with a payout, wherein there is a balance pay available for employees, then the system doesn’t notify of such records to the admin performing the change. The list  of time account postings that exist erroneously for a user can be determined from the check tool check: “Only time account postings that match the assignment period of the respective time account type exist for a user" .

FAQ

Q. "Please trigger a recalculation” warning message is shown. Why should I trigger a recalculation manually in case I remove a Time Type with a Time Account Type or I set the Time Profile to inactive?

A. In both scenarios, the assignment period of a Time Account Type to an employee is shortened. This means, the employee is no longer eligible for accruals from the removal date onwards. The eligibility directly impacts the calculation of accruals and therefore the accruals need to be recalculated. Refer handbook on using Time Management Recalculation Event object to recalculate absences, accruals etc.

Q. If I assign a time type to time profile effective from a future date, can I use the time type to apply leaves?

A. Yes, on selecting a start date of the leave request as the future date(or any date after), the respective time type will be present.

What's New Viewer:

• TIM-39466: Update to Effective-Dated Time Profile

Handbooks:

• Effective-Dated Time Profile
• Validation Checks On Changes to Effective-Dated Time Profile
• Time Profile
• Creating a Time Profile
• Time Management Recalculation Event

Customer Community:

• General Availability of Effective Dated Time Profile Opt-in Second Half 2023 - Innovation Alert

TIM-29244, Time off, effective dated, time profile, 2H 2022, b2211, 1H 2023, b2305, 2H 2023, b2311, Please trigger a recalculation, TimeProfileActiveAtJobInfoAssignment, AbsencesWithInconsistentTimeTypes, Only time account postings that match the assignment period of the respective time account type exist for a user, ErroneousTimeAccountDetailsOutsideAssignmentPeriod, TIM-39466 , KBA , LOD-SF-EC-TIM-JOB , Time Management in Job Info - Records & Objects , Product Enhancement