Skip to Content
Product Information
Author's profile photo Andrew Kuhn

Must Know New Features for EC in 1H 2022

With every release, there are important features and changes to the user experience that both Employee Central administrators and employees will need to be aware of. For the 1H 2022 release, we have consolidated a list of features that are “Must Know” items for Employee Central Core, Time Off, and Global Benefits. All of the features listed below will also include links to related information that will provide additional details regarding that specific feature.

Please also review other release related information at SAP SuccessFactors Release Information as well as specific features coming in the 1H 2022 Release in the What’s New Viewer.

 

Centralized Services

Feature Name Reference Number Configuration Type
Updates to Centralized Services ECT-191421 Universal

We have introduced universal support for some of the Centralized services entities. These entities are no longer governed by the configuration option.

The supported Centralized services entities are:

  • Address History UI Save
  • Global Information History UI Save
  • Personal Information History UI Save
  • Job Relationship Imports
  • Job Information History Imports – includes Pension Payout validation.

Note: The Job Relationship Imports and Job Information History Imports services are applicable to data imports initiated from the Import Employee Data page or APIs.

With this enhancement, you have access to the supported Centralized services entities by default. Please do review the blog below to get more information on all the Centralized Services features in this release.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Compensation Information Imports ECT-133297 Admin Opt-out

Centralized services support Compensation Information data imports in Incremental Load mode and in Full Purge mode. These services are applicable to data imports initiated from the Import Employee Data page or OData APIs.

Compensation Information data imports on Centralized services come with the following benefits:

  • Enhanced and more detailed error message handling
  • Identical record suppression: If identical records are included with the import, the system executes rules for compensation information to see if there are any changes to compensation and recurring pay component data. If there are changes, then they are saved in the system.
  • Support for business rules: Compensation Information supports execution of business rules against fields marked as not to be overwritten in your import template.
  • Forward propagation

The following data validations are introduced:

  • Association Validation: To check the associations between the various Foundation Objects and Generic Objects, and verify if the data you’ve entered in your import file are correct. If any discrepancies are found, they must be resolved before data can be imported.
  • Duplicate Record Validation: To check if there are multiple records in your import file with same data.
  • Sequence Number Validation: To check if a sequence number is entered when importing multiple records for a user with same event dates. All such records must have a sequence number for the data import to be successful.
  • Validation on forward propagated data: If there are any errors during data propagation, errors are shown in the Imports UI or in the job response.

The setting for this feature is Company System and Logo Settings > Enable Centralized Services for Compensation Information. This setting is applicable for Compensation Information imports initiated from the Employee Data Imports page or OData APIs.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Recurring Pay Component Imports ECT-133297 Admin Opt-out

Centralized services support Recurring Pay Component data imports in Incremental Load mode and in Full Purge mode. These services are applicable to data imports initiated from the Import Employee Data page or OData APIs.

Recurring Pay Component data imports on Centralized services comes with the following benefits:

  • Enhanced and more detailed error message handling
  • Identical record suppression: Only changes to the pay component data being imported are checked (whereas the Compensation Information import checks the data for both compensation information and pay components).
  • Support for business rules
  • Employee data deletion: Data imports for deleting employee data now go through a series of checks to ensure data integrity, and prevent inconsistencies.
  • Forward propagation

The following data validations are introduced:

  • Association Validation: To check the associations between the various Foundation Objects and Generic Objects, and verify if the data you’ve entered in your import file are correct. If any discrepancies are found, they must be resolved before data can be imported.
  • Duplicate Record Validation: To check if there are multiple records in your import file with same data.
  • Sequence Number Validation: To check if a sequence number is entered when importing multiple records for a user with same event dates. All such records must have a sequence number for the data import to be successful.
  • Validation on forward propagated data: If there are any errors during data propagation, errors are shown in the Imports UI or in the job response.

The setting for this feature is Company System and Logo Settings > Enable Centralized Services for Recurring Pay Component Information. This setting is applicable for Recurring Pay Component imports initiated from the Employee Data Imports page or OData APIs.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Global Assignment Imports ECT-163304 Admin Opt-out

Centralized services support Global Assignments data imports in Incremental Load mode and in Full Purge mode. These services are applicable to data imports initiated from the Import Employee Data page or OData APIs.

Global assignments data imports on Centralized services provides these benefits:

  • Enhanced and more detailed error message handling
  • Identical record suppression

The following data validation is introduced:

  • Validate the Global Assignment Start Date with the Home Employment

When importing the Global Assignment record, the system checks whether there is an active job information record, as of the global assignment start date and either successfully imports the global assignment record or throws a validation, meaning that the import fails.

The status of the Job Information record, as of the global assignment start date, cannot contain any of the following statuses: Termination, Retired, or No Show.

The setting for this feature is Company System and Logo Settings > Enable Centralized Services for Global Assignments.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Termination Details Imports ECT-163307 Admin Opt-out

Centralized services support Termination Details data imports in Incremental Load mode and in Full Purge mode. These services are applicable to data imports initiated from the Import Employee Data page or OData APIs.

Termination Details data imports on Centralized services come with the following benefits:

  • Enhanced and more detailed error message handling
  • Identical record suppression
  • Support for business rules
  • Forward propagation (Job Information)

The following data validations are introduced:

  • Person ID External validation
  • Event Reason validation
  • End Date validation
  • User ID validation
  • Foundation Object/Generic Object/Worker/Picklist field validation
  • Attachment validation
  • Position Status validation
  • Multiple Incumbents validation

There are a few behavior changes from legacy imports:

  • Rules:
    • onChange rules for Job Information as source element are supported only with Basic rule scenario.
    • onSave rules with Job Information as source element and Job Information as the target element are supported with Basic rule scenario.
  • Cross-entity rules:
    • Employment Information as Source Element:

Cross-entity rules where Employment Information is the source element with Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as the target element are no longer possible. Using the Cross-Entity Rules or Basic rule scenario, rules with Employment Information as the source element to Job Information as the target element are supported.

    • Job Information as Source Element:

Cross-entity rules where Job Information is the source element with Employment Information, Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as the target element are supported using the Cross-Entity Rules rule scenario.

  • Follow-Up Processing in Position Management:
    • The follow-up processes in Position Management are now triggered after the Termination Details import. These processes run in the background. Please check the system emails for errors after you’ve run the Termination Details import.

Configuration Requirements

The setting for this feature is Company System and Logo Settings > Enable Centralized Services for Termination Details (Applicable only for data imports from UI and API). This setting is applicable for Termination Details imports initiated from the Employee Data Imports page or OData APIs.

The Termination Details import on Centralized services is supported only for standard employment and concurrent employment records. If global assignments or pension payouts are activated in your system, the setting is not available in your system.

Please Note: This feature will be Admin Opt-out in Preview, however will be Admin Opt-in during the Production Release.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Saving Changes on History UI of Compensation Information and Recurring Pay Components ECT-166844 Admin Opt-out

Centralized services now support saving changes on the History UI of Compensation Information.

Centralized services come with the following benefits:

  • Enhanced and more detailed error message handling
  • Higher data quality by introducing new validations
    • When editing the history, audit fields are set for the recurring pay component only when a change is made to that specific pay component (including rules and calculations).
  • Forward propagation
  • Identical record suppression
  • Employee data deletion

Please Note: This feature will be Admin Opt-out in Preview, however will be Admin Opt-in during the Production Release.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Saving Changes on the History UI of Job Information ECT-174601 Admin Opt-out

Centralized services now support saving changes on the History UI of Job Information.

Time Off is now supported, which means that this is a new feature for customers using Time Off. We recommend you review the information provided for this feature in the previous release.

Changes to records for contingent workers are now saved on the History UI.

The system now also performs the following validations when you insert or edit an employee’s Job Information History record:

  • Position Status Validation
  • Multiple Incumbents Validation
  • Full-Time Equivalent (FTE) Validation

Previously, the system didn’t execute position, incumbent, or FTE validations when editing an employee’s Job Information History. No error message was shown.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Saving Changes on the History UI of Job Relationships ECT-161806 Admin Opt-out

Centralized services now support saving changes on the History UI of Job Relationships.

Job Relationships History UI on Centralized services comes with the following benefits:

  • Forward propagation
  • Identical record suppression
  • Enhanced and more detailed error message handling
  • Higher data quality by introducing new validations, for example:
    • To ensure that the start date is not before the first Job Information Hire record.
    • To ensure that active employees don’t have inactive related users on the start date of the new Job Relationships record, an error message is raised. To ensure that active employees don’t have inactive related users during the validity of the new Job Relationships record, a warning message is raised.

The setting for this feature is Company System and Logo Settings > Enable Centralized Services to Save Changes on the History UI of Job Relationships.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Saving Changes on Editing UI of Employment Details ECT-184660 Admin Opt-out

Centralized services now support changes made to an employee’s employment record when changes are made in the Manager Self-Service Take Action > Employment Details menu as well as from Edit action on the block.Saving changes on the Editing UI of Employment Details on Centralized services comes with the following enhancements:

  • Stricter data validations
  • Identical record suppression

There are a few changes from legacy behavior:

  • Cross-entity rules:
    • Employment Information as Source Element:

For active users, cross-entity rules with Employment Information as the source element and Job Information, Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as the target element are no longer supported.

For inactive or terminated users, using the Cross-Entity Rules or Basic rule scenario, rules with Employment Information as the source element to Job Information as the target element are supported. Cross-entity rules where Employment Information is the source element with Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as the target element are no longer possible.

    • Job Information as Source Element:

For inactive or terminated users, cross-entity rules where Job Information is the source element with Employment Information, Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as the target element are supported using the Cross-Entity Rules rule scenario.

    • Workflows:

With Centralized services, after workflow approval for active users, a new Job Information record is created, whereas previously, only an Employment Information record was updated.

The setting for this feature is Company System and Logo Settings > Enable Centralized Services to Save Changes on the Editing UI for Employment Details.

Centralized services offer consistent and robust validations that improve data integrity of Employment Details.

Please Note: This feature will be Admin Opt-out in Preview, however will be Admin Opt-in during the Production Release.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Saving Changes on Editing UI of Addresses ECT-175888 Admin Opt-out

Centralized services are now enabled by default to support saving changes on the Editing UI of Addresses in People Profile.

Saving changes on the Editing UI of Addresses on Centralized services comes with the following enhancements:

  • Forward propagation of data is supported when you insert a new record.
  • Deletion on the Editing UI triggers business rules and workflows.
  • When you delete records with a certain start date, deletion will be propagated to future records until one of the future records has a field value that is different from the original field value.
  • If you update or delete a record in the block, it doesn’t affect the “last modified date” and “last modified by” information of other records.

Centralized services offer consistent and robust validations that improve data integrity of address information.

Please Note: This feature will be Admin Opt-out in Preview, however will be Admin Opt-in during the Production Release.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Saving Changes on Editing UI of National ID ECT-147146 Admin Opt-out

Centralized services are enabled by default to support users editing and saving national ID information in People Profile.

Centralized services offer consistent and robust validations that improve data integrity of national ID information.

Related Information:

 

Centralized Services

Feature Name Reference Number Configuration Type
Centralized Services Support Saving Changes on Editing UI of Personal Information and Global Information ECT-175811 Admin Opt-out

Centralized services are now enabled by default to support saving changes on the Editing UI of Personal Information and Global Information blocks in People Profile.

Saving changes on the Editing UI of Personal Information and Global Information on Centralized services comes with the following enhancements:

  • Forward propagation of changes in field values is supported when you edit records.
  • When you delete records of Global Information with a certain start date, deletion will be propagated to future records until one of the future records has a field value that is different from the original field value.
  • If you update or delete a record of Global Information in the block, it doesn’t affect the “last modified date” and “last modified by” information of other Global Information records.

This enhancement helps ensure data integrity and prevent inconsistencies.

Related Information:

 

HRIS Sync

Feature Name Reference Number Configuration Type
Updates to HRIS Sync ECT-176402 Universal

We have redesigned HRIS Sync. Previously, HRIS Sync job synced data based on each entity for all user IDs. Now, the data is synced for all entities based on each user ID.

Along with the redesign, we have made the following enhancements:

  • The HRIS Sync job runs in a shorter time frame.
  • View Details for the job provide more relevant data when the HRIS Sync job runs.
  • If you remove an e-mail address from Employee Central by importing data, the e-mail address is removed from the Employee Profile.
  • Date of Birth field now syncs when rehiring a contingent worker.

This redesign improves the performance of HRIS Sync job.

Note: that the settings for Select the entities required for sync. in HRIS Sync job configuration are ignored when running the job. We sync all entities for a user ID.

Related Information:

 

Hire/Rehire – Contingent Workers

Feature Name Reference Number Configuration Type
Configurable New Hire Templates Now Available for Contingent Workers ECT-176928 Admin Opt-in

You can now make use of configurable hire templates when hiring contingent workers. Previously these templates were only available for hiring internal employees.

Note: When configuring a hire template for contingent workers, only the Employee Central HRIS elements applicable for person type Contingent Worker and the WorkOrder MDF object are supported.

A hire template is a collection of steps (pages), where each step is a group of blocks. You can freely add, remove, and rearrange the order of the blocks in order to flexibly configure the hiring process so it better fits the business needs in different countries/regions and/or for a different workforce.

Related Information:

 

Manage Pending Hires

Feature Name Reference Number Configuration Type
Position Follow-Up Processes Triggered for Internal Hires in Manage Pending Hires Tool ECT-188755 Admin Opt-in

When processing a pending internal hire, three additional position follow-up processes are now triggered in addition to the hierarchy adaptation and ToBeHired adaptation.

The position follow-up processes that are now also triggered are:

  • Position reclassification (Job2Pos sync)
  • Position transfer
  • Position matrix to job relationship synchronization

When changing position for an internal hire and depending on how Job Information to Position synchronization is defined, reclassification and transfer processes are triggered.

This change makes the hiring process for internal hires similar to the hiring process for a new employee.

Configuration Requirements

  • Set the following from Position Management Settings to ‘Yes’.
    • Search for Position in Position Reclassification
    • Search for Position in Position Transfer
  • In Position Management Settings, for Synchronize Position Matrix Relationships to Job Relationships of Incumbents, set a value other than ‘Never’.
  • Go to Manage Organization, Pay, and Job Structures. Search for Event Reason you use for internal hires. Edit the Event Reason to set Follow-Up Activity in Position to Position Reclassification or Position Transfer.
  • Create rule in Position Management SettingsSynchronization > Rule for Synchronizing Job Information to Position.

Related Information:

 

Check Tool

Feature Name Reference Number Configuration Type
Critical Check Tool Checks that Require Action TLS-24210 Universal

Every release, we add new checks to the check tool to help you find and solve potential configuration issues in your system. We want to draw your attention to those new checks that assist you in detecting and fixing data and configuration issues. These issues can disrupt your business processes if the checks aren’t run now.

New checks might detect issues you hadn’t been aware of beforehand. Therefore, we recommend that you run all checks for the application areas you’ve enabled at the beginning of a release and fix any issues. For a complete list of all checks available, you can export a list from the check tool itself.

Area Title

Check ID

Why Run It Now

Emergency Contact

EmergencyContactNoDuplicateBusinessKeys
EmergencyContactNoEmptyBusinessKeys

We’ll implement business key validation for Emergency Contacts in the upcoming releases. To avoid data maintenance failure in the future, we recommend that you check the data and fix issues before the change happens.

Association

MissingFieldCriteriaCheck
ExistingFieldCriteriaCheck

If two foundation (or generic) objects are associated with each other, correct input help is shown in the UI, for example, the Job Information History UI. For example, suppose that “Department” is associated with “Division”. Once the user selects a division in the UI, the input help for department should filter only those departments that belong to the (already selected) division. This input help only works if the field criteria is configured correctly in the Succession Data Model. In the above example, if the field criteria of the department field is configured correctly.

These two new checks ensure that field criteria are correct so that the filtering works. There are 2 possibilities for errors: Field criteria exists but is incorrect OR field criteria is missing completely. In case of incorrect field criteria, the filtering simply doesn’t work. If field criteria is missing, then “implicit filtering” might happen, meaning the input help reverses the association direction. In the above example, a missing field criteria would imply that the choice of the department determines the division. This implicit filtering can lead to inconsistent data.

Job Information

JobInfoInconsistentEndDateCheck

Inconsistent end dates break business processes. For example, the Job Information block in the People Profile is shown as empty (no data) if there’s no record with a high date (Dec 31, 9999), this can make businesses processes fail. In cases where several records in a user’s history have a high date, unexpected system behavior can occur, like positions being shown as overstaffed, and so on.

We’ve merged 3 end-date checks into 1 check. These checks are no longer listed:
– CheckLatestJobInfoHighDate
– JobInfoStartDateHigherThanEndDate
– JobInfoMultipleHighDate

If the check returns issues, a quick fix is offered for the system to automatically correct the issues for you.

Work Permit

WPWithDuplicateBusinessKeys
WPWithEmptyBusinessKeys

Work permit records must be uniquely identified by business keys. These two checks, first released in 1H 2021, are used to find work permits with duplicate or empty business keys and guide your efforts to correct them. In 1H 2022, we enhanced the two checks and made the Issue Date field part of a business key. This ensures that work permits with identical Country, Document Type, Document Number, and User ID but different Issue Date values are treated as valid data and excluded from check results.

We’re moving work permits to Centralized services. To ensure that you take full advantage of Centralized services and your system works smoothly, you have to clean up invalid work permit data.

Configuration Requirements

Apart from the check tool, you also must have enabled the applications for which you want to run the checks. For example: Employee Central.

Role-Based Permission Prerequisites

You have the following Administrator > Check Tool permissions:

  • Access Check Tool
  • Allow Configuration Export
  • Allow Check Tool Quick Fix

Related Information:

 

Alerts

Feature Name Reference Number Configuration Type
Alerts on the Latest Home Page ECT-161925 Universal

Directly from the latest home page, users can learn about upcoming events generated using EC Alerts.

Employee Central and MDF alerts appear as glance-friendly cards in the For You Today section. They serve as timely reminders of approaching events, such as expiration of documents or employee data changes. Users can dismiss these cards temporarily by choosing Remind Me Tomorrow or permanently by choosing Done.

Home page users want their most urgent, pending tasks to appear on the home page. These new cards keep them notified about matters they need to take care of and allow them to plan early.

Related Information:

 

Time Off

Feature Name Reference Number Configuration Type
Termination End Handling Process in Time Off TIM-10196 Admin Opt-in

It’s now possible to automatically clean up an employee’s Time-Off-related data that exists after the termination date.

If the employment of an employee is terminated and the employee is rehired in the same accrual period, the termination end handling process ensures that the employee receives the correct amount of leave accruals upon rehire. The termination end handling process cleans up Time-Off-related data, such as absences, accruals, time accounts, and time account postings that exist after the termination date. An alert is raised if the termination end date is changed to a past or future date. In addition, you see a warning message if you change the Termination End Handling configuration.

By adding this feature, we’re fixing issues related to termination and rehire processes. The enhancement comes from two Customer Community Ideas.

Role-Based Permission Prerequisites

Before you can start to configure, you need to assign the permissions for the MDF objects related to Termination End Handling Configuration. See the Role-Based Permissions Required for Termination End Handling documentation for details.

Related Information:

 

Time Off

Feature Name Reference Number Configuration Type
Harmonization of Child Node Creation for Countries with Linking and Non-Linking Absence Scenarios TIM-20851 Universal

We’ve harmonized the creation of country extension node during absence creation for all countries where the linking and non-linking of absence functionality is supported for Employee Time scenarios.

Note: For Germany, there are certain time type configuration, like time type with sick pay date calculation and other than sick pay date calculation.

  • For time type with sick pay date calculation, the default values are provided in the mandatory fields. If the duration of continued sick pay period is not “NULL” in time type Germany and the absence created from ESS, the child node is created and the default values for the country extension is automatically filled using the time type configuration with defaulting logic. However, these default values are not visible in the ESS screen.
  • For time type other than sick pay date calculation, default values are not maintained for the absence created.
  • For time type with sick pay date calculation, if you don’t maintain the continued sick pay fields, then the system calculates the values automatically for Import and APIs.

This enhancement makes it easier for administrators to perform a dummy action on absences created from ESS, Manage Data, and Imports.

Related Information:

 

Time Off

Feature Name Reference Number Configuration Type
Concurrent Absences in Time Management TIM-18987 Admin Opt-in

You can now record an absence that overlaps, either fully or partially, with another absence.

For example, an employee has created an absence, “Vacation,” from December 20, 2021, to December 31, 2021. Unfortunately, the employee falls ill during vacation. They can now create another absence, “Sickness” that starts on December 23, 2021, with an undetermined end date. The two absences are concurrent because parts of the “Vacation” absence overlap with the “Sickness” absence.

The feature is generally available for all countries/regions, but is only fully tested for the United Kingdom, the Netherlands, and Spain. Check the end-to-end impact when implementing this feature to cover other use cases.

Configuration Requirements

There’s a new field for the Collision Resolution Action with value Allow Concurrent Records, on the Time Management Collision Resolution object. The field is editable by default. You need to configure the time types to allow concurrent absences. Please refer to Time Management Collision Resolution for more information.

Related Information:

 

Time Off

Feature Name Reference Number Configuration Type
Migration to Reimagined Home Page Within 1H 2022 Release – Team Absence Calendar TIM-18954 Universal

You can now grant permission to access the team absence calendar for certain user groups.

This permission is user-based and not based on a target population. For example, you can decide to allow only managers to access the team absence calendar.

We’re adding this permission because we’ve introduced a new quick card, View Team Absences for the latest home page. The quick card respects this permission to allow specific managers and employees to access the team absence calendar user interface. With the latest home page, the team absence calendar is now also accessible to employees directly from the home page. For more details, refer to the related link, More Quick Actions on the Latest Home Page.

Role-Based Permission Prerequisites

You have permission to Admin Center > Manage Permission Roles > Time Management User Permissions > Access Team Absence Calendar

Related Information:

 

Time Off / Time Sheet

Feature Name Reference Number Configuration Type
Changes to Time Management Quick Approval Cards TIM-27365 Universal

We’ve changed the number of fields shown on the Time Sheet quick approval card. Additionally, Time Off and Time Sheet quick approval cards now respect the Administrator Permissions > Manage Workflows > Prevent Quick Approval of Workflow permission.

These changes were made so that the experience of Time Management quick approval cards is consistent with the experience of other quick approval cards on the latest home page.

The Time Sheet quick approval card now only shows up to five fields. PeriodPlanned Working Time, and Recorded Working Time are always shown. AllowancesOn-Call TimesWorking Time Account, and Absences are only shown under certain conditions.

Now, when you select the Administrator Permissions > Manage Workflows > Prevent Quick Approval of Workflow permission, the approval buttons on the Time Off and Time Sheet are hidden.

Related Information:

 

Time Sheet

Feature Name Reference Number Configuration Type
Additional Functionality on the New Time Sheet UI and New URL TIM-23195 Universal

The new Time Sheet UI now supports required custom fields for allowances and field criteria for a number of scenarios. The URL of the new Time Sheet UI has also changed.

Here’s a screenshot of the new Time Sheet UI, where the new functionality is now available:

We added this functionality because many customers use custom fields and field criteria on the old Time Sheet UI. The URL has changed because of technical reasons.

Configuration Requirements

The URL of the new Time Sheet UI has changed to www.<placeholder>.com/xi/ui/attendancerecordingui/pages/sap/sf/attendancerecordingui/timesheet/index.xhtml. Make sure that you use the new URL for Time Sheet custom tiles. Custom tiles that use the old URL will stop working.

Related Information:

 

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Paco Adrian Paul Pascua
      Paco Adrian Paul Pascua

      As always awesome content Andrew Kuhn  very helpful.

      Author's profile photo Shraddha Soni
      Shraddha Soni

      Where can we raise the  bug found in SAP Release feature.

      Author's profile photo Andrew Kuhn
      Andrew Kuhn
      Blog Post Author

      Hi Shraddha,

      Please contact support via the SAP Support Portal to raise any concerns or issues you find.