New Tables Added in the Person Schema for Reporting the Emergency Contact Address Details
To include the address details of emergency contacts in your story, use the emergency contact address and the emergency contact (Country/Region-Specific) address-related tables that can be accessed from the emergency contact table.
The new tables enable you to report the address of the emergency contact that the employees have added to the emergency contact section in Employee Profile.
Role-Based Permission Prerequisites
To view the emergency contact data in stories, grant the emergency contact-related permission in the HR Information section under User Employee Data in role-based permissions.
Configuration Requirements
We recommend that you update all the stories that report the address details of emergency contacts. If you're reporting the address details of emergency contacts using the columns from the home address and the country/region-specific home address-related tables, when you run the story, the columns appear blank. To fix the story,
- If you've selected columns (fields) from the home address and the country/region-specific home address-related tables to report the address information of emergency contacts, update your queries to select similar columns (fields) from the new emergency contact address and the emergency contact (Country/Region-Specific) address-related tables.
- Next, update the story widgets to use columns from the updated data source.
What's Changed
How It Looks Now
In the current version, you can go to the newly added emergency contact address and the emergency contact (Country/Region-Specific) address tables from the emergency contact table for reporting.
How It Looked Before
In the previous version, you could go to the home address and the country/region-specific home address tables from the emergency contact table for reporting the address details of emergency contact. The existing stories with the address details columns that are selected from the home address and the country/region-specific home address tables appear blank.
Also, you can no longer go to the home address and the country/region-specific home address tables from the emergency contact table.
Technical Details
| Reference Number | ECT-211612 |
| Product |
|
| Module |
|
| Feature |
|
| Action | Recommended |
| Enablement | Automatically on |
| Link to Demo | |
| Lifecycle | General Availability |
| Type | New |
| Major or Minor | Major |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2024-05-17 |
| Latest Document Revision | 2024-04-12 |
Related Information
Reporting of Planned Working Time with Story Reports
You can now create a Story report with the planned working time data.
The Planned Working Time table in the Time Management schema allows you to create reports on the planned working time of the employees for specific periods, considering the work schedule information, temporary time information, and holidays.
The Planned Working Time table includes the following fields:
Note
In the following table, Start Time, End Time, Flextime Bandwidth Time, and Night Shift Bandwidth Time are all fields of String-Type and are applicable only for Clock Time users.| Field Name | Description |
|---|---|
| Start Date | The date on which the user or employee has to start working for this planned working time record |
| End Date | The date on which the user or employee has to stop working for this planned working time record. In the case of cross-midnight, this could be Start Date + 1 day. In all other cases where cross-midnight is false, it's always the same as Start Date. |
| Start Time (24-hour) | Start time in a 24-hour format based on the following:
|
| End Time (24-hour) | End time in a 24-hour format based on the following:
|
| Start Time (AM/PM) | Start time in a 12-hour format based on the following:
|
| End Time (AM/PM) | End time in a 12-hour format based on the following:
|
| Planned Working Time (in hours) | This is the actual planned working time based on the following:
|
| Is Non-Working Day | Indicator for off days ( for example, weekly off) based on the work schedule or the temporary time information. |
| Is Cross-Midnight | Indicator to show if an entry is cross-midnight. This flag is set to true, only if scheduled working time for that particular day spans across midnight. |
| Flextime Bandwidth Start Time (24-hour) | Flextime Bandwidth start time in a 24-hour format based on the work schedule configured in the employee job information page. |
| Flextime Bandwidth End Time (24-hour) | Flextime Bandwidth end time in a 24-hour format based on the work schedule configured in the employee job information page. |
| Night Shift Bandwidth Start Time (24-hour) | Night Shift Bandwidth start time in a 24-hour format based on the work schedule configured in the employee job information page. This field is applicable only for cross-midnight scenarios. |
| Night Shift Bandwidth End Time (24-hour) | Night Shift Bandwidth end time in a 24-hour format based on the work schedule configured in the employee job information page. This field is applicable only for cross-midnight scenarios. |
| Flextime Bandwidth Start Time (AM/PM) | Flextime Bandwidth start time in a 12-hour format based on the work schedule configured in the employee job information page. |
| Flextime Bandwidth End Time (AM/PM) | Flextime Bandwidth end time in a 12-hour format based on the work schedule configured in the employee job information page. |
| Night Shift Bandwidth Start Time (AM/PM) | Night Shift Bandwidth start time in a 12-hour format based on the work schedule configured in the employee job information page. |
| Night Shift Bandwidth End Time (AM/PM) | Night Shift Bandwidth end time in a 12-hour format based on the work schedule configured in the employee job information page. |
| Work Schedule External Name | Name of the Work Schedule. |
| User | The User object (link to an already existing reportable object) has the Display Name, External Person ID, First Name, Last Name, and User ID. |
| Is Holiday | Is Holiday will be set to true, if the Holiday Calendar assigned to this user has this particular day as a holiday. |
| Original Planned Hours | Planned hours as per the work schedule configured in the employee job information page. |
| Record Status | This field though available isn't applicable for generating a Story report with planned working time. |
We've made this enhancement to include the actual planned working time in the Story report. This enables users to create individual reports whether internally for tracking planned working time, making them available to the affected employees or for reporting to external parties or government organizations.
Configuration Requirements
Perform the following steps:
Note
Perform these configuration steps only if you've not enabled Time Off earlier.- Run the MDF sync DB changes job from Provisioning. The Job Type is MDF Object Definition To DB SYNC . As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
- Run the Save Changes to Reporting Config job from Provisioning. The Job Type is called Save Changes To Report Configuration Object Job.
- Check if the Planned Working Time object appears in Configure Object Definitions.
Role-Based Permission Prerequisites
Ensure you have the View permission for User → Time Management Object Permissions → Planned Working Time.
What's Changed
How It Looks Now
In the current version, the fields of planned working time are reportable with Story reports.
Technical Details
| Reference Number | TIM-41808 |
| Product |
|
| Module |
|
| Feature |
|
| Action | Info only |
| Enablement | Customer configured |
| Link to Demo | |
| Lifecycle | General Availability |
| Type | New |
| Major or Minor | Major |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2024-05-17 |
| Latest Document Revision | 2024-04-12 |
Related Information
Locale-Specific Formats for Date, Time, and Numbers Are Now Supported in Stories
The date, time, and number formats in stories are now locale-specific, which means that the formats correspond to the language you select in the SAP SuccessFactors application.
Note
This enhancement isn't available for the Preview release. It'll be available on the Valid as Of date mentioned in the technical details table.Each language has a predefined format for date, time, and numbers. Lets understand how the formats appear in different languages:
Different Locale and the Predefined Formats for Date, Time, and Numbers
| Language | English (US) | German |
|---|---|---|
| Date | Mar 1, 2024 | 01.03.2024 |
| Time | 4:15:30 PM | 16:15:30 |
| Number | 12,345,678.12 | 12.345.678,12 |
Previously, the date, time, and numbers appeared only in the default format (English US).
This enhancement is from a Customer Community Idea #283597.
Technical Details
| Reference Number | AYT-54292 |
| Product |
|
| Module |
|
| Feature |
|
| Action | Info only |
| Enablement | Automatically on |
| Link to Demo | |
| Lifecycle | General Availability |
| Type | New |
| Major or Minor | Major |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2024-05-17 |
| Latest Document Revision | 2024-04-19 |
Related Information
Invalidation of Stories Due to Changes in the Schema (Tables or Columns) Used in the Story
When there are changes made to a table or a column in a schema, stories using that table or column can get impacted and would appear as invalid on the Report Center page.
Note
This enhancement isn't available for the Preview release. It'll be available on the Valid as Of date mentioned in the technical details table.If tables or columns within a schema are modified or deleted (for example, by using Configure Object Definitions), these changes can break a story. With this enhancement, such stories are rendered as invalid. Users who have edit permissions for the story can update it to resolve the issues.
Automatic invalidation of stories prevents users from running stories with potential issues.
What's Changed
How It Looks Now
When a story becomes invalid, you can no longer run it. A cross icon in red appears as a visual indicator against the story on the Report Center page. The hover text for the icon elaborates the issue and suggests the next steps to resolve it. You can run the story only after the issue is resolved.
How It Looked Before
In the previous version, there was no such validation. In spite of changes to the schema on which the stories were built, the stories appeared valid. On running the story, you encountered one or more issues.
Technical Details
| Reference Number | AYT-48892 |
| Product |
|
| Module |
|
| Feature |
|
| Action | Info only |
| Enablement | Automatically on |
| Link to Demo | |
| Lifecycle | General Availability |
| Type | New |
| Major or Minor | Major |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2024-05-17 |
| Latest Document Revision | 2024-04-12 |
Related Information
Quick Fix Guide for Imported Stories
Query Validation Checks Available in Query Designer of Story Reports
Availability of New Reporting Usage Data Schema in Story Reports
You can now report the usage of Table and Tiles and Dashboard using the new Reporting Usage Data schema in Story reports.
The Reporting Usage Data schema has the following primary tables:
- All Report Information
- Table Report Details
- Tiles and Dashboard Details
The schema also contains other tables that enable you to retrieve the report generation and sharing data. The report generation data can be retrieved for the previous 12 months from the current date. You can also report the number of available Tile-Based Dashboards.
The usage-related information for Table and Tiles and Dashboard, which the Reporting Usage Data schema offers, helps you plan your transition to Story reports. This enhancement is from a Customer Community Idea # 250479.
Role-Based Permission Prerequisites
To view the Reporting Usage Data schema in the Available Data section of Query Designer, enable the User Report Permissions Create Story permission.
To view the data retrieved from the Reporting Usage Data schema, enable the Administrator Manage Dashboard/Reports Story Admin permission.
Technical Details
| Reference Number | AYT-54793 |
| Product |
|
| Module |
|
| Feature |
|
| Action | Info only |
| Enablement | Automatically on |
| Link to Demo | |
| Lifecycle | General Availability |
| Type | New |
| Major or Minor | Major |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2024-05-17 |
| Latest Document Revision | 2024-04-12 |
Related Information
Deprecation of Canvas Reports for Transactional Reporting
Canvas reports for transactional reporting (Detailed reporting and Advanced reporting) will reach End of Development on November 17, 2023 and will be Deleted on November 21, 2025. This deprecation announcement has been withdrawn.
Note
We're rolling back the deprecation announcement for Canvas reports, because the current deprecation plan has been put on hold. Continue to use Canvas reports while staying up-to-date as the deprecation plan adapts to our shared needs.
We have left the topic so that you can see what was planned but that we removed it. That includes the technical details, including the Valid as Of date, so that you can see when it was originally planned.
Key Dates
Future dates are subject to change.
| Milestone | Date | Definition |
|---|---|---|
| End of Development | November 17, 2023 | The deprecation milestone after which SAP stops enhancing a product or part of a product. You can continue to use the software, but you should begin planning for a time when it will no longer be available for use. We still fix high-priority bugs. |
| End of Maintenance | November 21, 2025 | The deprecation milestone after which SAP does not fix bugs or deliver patches for the software. SAP continues to answer your how-to questions. We strongly encourage you to adopt an alternative method for your business scenario. |
| Deleted | November 21, 2025 | The deprecation milestone when a feature is no longer available for productive use. You should now be using an alternative method for your business scenario. |
Deprecation Details
As the logical next step for achieving our vision of making Stories in People Analytics the go-to solution for all your reporting needs, we are deprecating Canvas reports for transactional reporting (Detailed Reporting and Advanced Reporting).
Additional Resources
For more information, refer to the SAP SuccessFactors Customer Community Blog.
- For tips and assistance on planning the transition, refer to the community blog, Usage Statistics of Table and Canvas Reports to Plan Transition to Stories.
Technical Details
| Reference Number | AYT-53648 |
| Product |
|
| Module |
|
| Feature |
|
| Action | Info only |
| Enablement | Automatically on |
| Link to Demo | Not Applicable |
| Lifecycle | Deprecated |
| Type | Changed |
| Major or Minor | |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2025-11-21 |
| Latest Document Revision | 2024-04-19 |
Change History
| Date | What Changed | Reason |
|---|---|---|
| October 13, 2023 | Initial publication. | |
| October 27, 2023 | We updated the topic to indicate that Canvas reports is being deprecated for transactional reporting. | Canvas reports for transactional reporting (Detailed reporting and Advanced reporting) is being deprecated. Canvas reports will continue to be available for Workforce Analytics. |
| February 16, 2024 | We've updated the topic to include the link to the blog "Usage Statistics of Table and Canvas Reports to Plan Transition to Stories" in the Additional Information section, | Stories is the main, suite-wide reporting tool. This blog discusses ways in which you can prioritize and plan your transition to stories. |
| April 19, 2024 | We've rolled back the deprecation announcement for Canvas reports. | Currently, the deprecation plan for Canvas reports has been put on hold. |
Deprecation of Table Reports
Table reports will reach End of Development on November 17, 2023 and will be Deleted on November 21, 2025. This deprecation announcement has been withdrawn.
Note
We're rolling back the deprecation announcement for Table reports, because the current deprecation plan has been put on hold. Continue to use Table reports while staying up-to-date as the deprecation plan adapts to our shared needs.
We have left the topic so that you can see what was planned but that we removed it. That includes the technical details, including the Valid as Ofdate, so that you can see when it was originally planned.
Key Dates
Future dates are subject to change.
| Milestone | Date | Definition |
|---|---|---|
| End of Development | November 17, 2023 | The deprecation milestone after which SAP stops enhancing a product or part of a product. You can continue to use the software, but you should begin planning for a time when it will no longer be available for use. We still fix high-priority bugs. |
| End of Maintenance | November 21, 2025 | The deprecation milestone after which SAP does not fix bugs or deliver patches for the software. SAP continues to answer your how-to questions. We strongly encourage you to adopt an alternative method for your business scenario. |
| Deleted | November 21, 2025 | The deprecation milestone when a feature is no longer available for productive use. You should now be using an alternative method for your business scenario. |
Deprecation Details
As the logical next step for achieving our vision of making Stories in People Analytics the go-to solution for all your reporting needs, we are deprecating the legacy reporting tool, Table reports.
Additional Resources
For more information, refer to the SAP SuccessFactorsCustomer Community Blog.
- For tips and assistance on planning the transition, refer to the community blog, Usage Statistics of Table and Canvas Reports to Plan Transition to Stories.
Technical Details
| Reference Number | AYT-53648 |
| Product |
|
| Module |
|
| Feature |
|
| Action | Info only |
| Enablement | Automatically on |
| Link to Demo | Not Applicable |
| Lifecycle | Deprecated |
| Type | Changed |
| Major or Minor | |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2025-11-21 |
| Latest Document Revision | 2024-04-19 |
Change History
| Date | What Changed | Reason |
|---|---|---|
| October 13, 2023 | Initial publication. | |
| February 16, 2024 | We've updated the topic to include the link to the blog "Usage Statistics of Table and Canvas Reports to Plan Transition to Stories" in the Additional Information section, | Stories is the main, suite-wide reporting tool. This blog discusses ways in which you can prioritize and plan your transition to stories. |
| April 19, 2024 | We've rolled back the deprecation announcement for Table reports. | Currently, the deprecation plan for Table reports has been put on hold. |
Deprecation of Classic Reports
Classic reports will reach End of Development on November 17, 2023 and will be Deleted on November 22, 2024.
Key Dates
Future dates are subject to change.
| Milestone | Date | Definition |
|---|---|---|
| End of Development | November 17, 2023 | The deprecation milestone after which SAP stops enhancing a product or part of a product. You can continue to use the software, but you should begin planning for a time when it will no longer be available for use. We still fix high-priority bugs. |
| End of Maintenance | November 22, 2024 | The deprecation milestone after which SAP does not fix bugs or deliver patches for the software. SAP continues to answer your how-to questions. We strongly encourage you to adopt an alternative method for your business scenario. |
| Deleted | November 22, 2024 | The deprecation milestone when a feature is no longer available for productive use. You should now be using an alternative method for your business scenario. |
Deprecation Details
As the logical next step for achieving our vision of making Stories in People Analytics the go-to solution for all your reporting needs, we are deprecating the legacy reporting tool, Classic reports.
Additional Resources
For more information, refer to the SAP SuccessFactorsCustomer Community Blog.
Technical Details
| Reference Number | AYT-53648 |
| Product |
|
| Module |
|
| Feature | Classic Reports |
| Action | Info only |
| Enablement | Automatically on |
| Link to Demo | Not Applicable |
| Lifecycle | Deprecated |
| Type | Changed |
| Major or Minor | |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2024-11-22 |
| Latest Document Revision | 2023-10-13 |
Change History
| Date | What Changed | Reason |
|---|---|---|
| October 13, 2023 | Initial Publication |
Deprecation of Tiles and Dashboard Reports
Tiles and Dashboard reports will reach End of Development on November 17, 2023 and will be Deleted on November 21, 2025.
Key Dates
Future dates are subject to change.
| Milestone | Date | Definition |
|---|---|---|
| End of Development | November 17, 2023 | The deprecation milestone after which SAP stops enhancing a product or part of a product. You can continue to use the software, but you should begin planning for a time when it will no longer be available for use. We still fix high-priority bugs. |
| End of Maintenance | November 21, 2025 | The deprecation milestone after which SAP does not fix bugs or deliver patches for the software. SAP continues to answer your how-to questions. We strongly encourage you to adopt an alternative method for your business scenario. |
| Deleted | November 21, 2025 | The deprecation milestone when a feature is no longer available for productive use. You should now be using an alternative method for your business scenario. |
Deprecation Details
As the logical next step for achieving our vision of making Stories in People Analytics the go-to solution for all your reporting needs, we are deprecating the legacy reporting tool, Tiles and Dashboard reports.
Additional Resources
For more information, refer to the SAP SuccessFactorsCustomer Community Blog.
Technical Details
| Reference Number | AYT-53648 |
| Product |
|
| Module |
|
| Feature |
|
| Action | Info only |
| Enablement | Automatically on |
| Link to Demo | Not Applicable |
| Lifecycle | Deprecated |
| Type | Changed |
| Major or Minor | |
| Business Process Variant |
|
| Software Version |
|
| Valid as Of | 2025-11-21 |
| Latest Document Revision | 2023-10-13 |
Change History
| Date | What Changed | Reason |
|---|---|---|
| October 13, 2023 | Initial Publication |