Understanding Appendix

Find all new features and enhancements for the release in the What's New Viewer on the SAP Help portal.

If you want more details on a topic, proceed as follows:

1. Navigate to the SAP Help portal and in the Search all drop-down list, enter SAP SuccessFactors Release Information.
2. From the drop-down list to the right of the SAP SuccessFactors Release Information title, select the appropriate release.
3. Select What’s New Viewer.
4. Select the filters as required to view the topic.
5. If the topic contains more information, select See more.
6. Under the Related Information section, locate further details on the topic.

This is an ODATA function import getWorkflowPendingData which allows customers to extract the workflow pending data for person and employment entities. Previously, it was available as beta only. Now the beta API is enhanced to be available as public. For all the customers using beta API, please change the endpoint URL. This API provides access to pending data for workflow requests. To get further information about the API and its limitation, please refer to the help document.

This is a new API which will allow customers and partners to access the workflow pending data. Some business cases are: document generation, workflow approval extension app using cloud platform, etc.

Read ODATA admin permission

Along with support for entities like PerEmail, PerPhone, PerAddressDEFLT, and EmpJobRelations, OData API now supports the following entities to handle deleted objects for expanded entities: PerNationalId, EmpPayCompNonRecurring, PerEmergencyContact, and EmpWorkPermit.

The standard behavior in Employee Central OData API queries is to ignore any records that have been deleted. With the handling of deleted expanded entities you have the chance to capture the completely deleted object in an last modify query.

Enable "Consider Deletion of Expanded Entities As A Change" switch in Manage Employee Central Settings

You can filter the custom string fields custom-string1, custom-string2, and custom-string3 when querying the Employee Central OData APIs PerPerson and EmpEmployment.

In case you use these custom strings to store external system ID, you can query the entity records with filters rather than fetch all the records, which possibly saves time during a data sync between SAP SuccessFactors HXM Suite and other systems.

Now, you can filter the custom-string1, custom-string2, and custom-string3 fields when you query these entity records.

Previously, the custom string fields in PerPerson and EmpEmployment weren’t filterable.

None

You can use the datetime fields seniorityDate, originalStartDate, and benefitsEligibilityStartDate as filters when querying the Employee Central OData API EmpEmployment.

You can use these datetime filters to query the entity records that meet date-related requirements. It can be used to select employees who are eligibile for benefits such as long-service awards.

Now, you can filter the seniorityDate, originalStartDate, and benefitsEligibilityStartDate fields when you query the EmpEmployment entity records.

Previously, the datetime fields in EmpEmployment weren’t filterable.

None

After the server migrates to UTC, the date time fields lastModifiedOn and createdOn of Employee Central OData entities will represent date information in UTC time.

We built this feature to keep date and time information consistent after the server migrates to UTC.

In the current version, the fields lastModifiedOn and createdOn represents date information in UTC time.

In the previous version, the fields represented date information in the server's time zone.

None

A new property effectiveLatestChange is now available in the OData API EmpJob.

As EmpJob supports multiple changes per day (MCPD), you can use this property to filter the record that is last updated on a day in date range queries (with fromDate and toDate parameters).

We built this feature to help customers to locate the latest records of MCPD entities in date range queries.

In the current version, the effectiveLatestChange property is available in the EmpJob API.

1234567891011121314
{
                "__metadata": {
                    "uri": "https://<api-server>/odata/v2/EmpJob(seqNumber=1L,startDate=datetime'2001-02-01T00:00:00',userId='rjones1')",
                    "type": "SFOData.EmpJob"
                },
                "userId": "rjones1",
                "startDate": "/Date(980985600000)/",
                "effectiveLatestChange": true,
                "createdBy": "admin",
                "lastModifiedBy": "admin",
                "event": "2289",
                "eventReason": "HIRNEW"
                ...
            }

In the previous version, EmpJob didn't have this property.

We added the entityOID property to the OData APIs FOCostCenter and FOCompany to store the One Domain Model (ODM) object ID of their corresponding MDF objects.

We made this enhancement because entityOID is required as a unique identifier for MDF records in ODM.

In the current version, you can get entityOID in FOCostCenter and FOCompany.

12345678910111213
{
                "__metadata": {
                    "uri": "https://<api-server>/odata/v2/FOCompany(externalCode='1510',startDate=datetime'1970-01-01T00:00:00')",
                    "type": "SFOData.FOCompany"
                },
                "externalCode": "1510",
                "startDate": "/Date(0)/",
                "country": "JPN",
                "lastModifiedDateTime": "/Date(1628256460000+0000)/",
                "endDate": "/Date(253402214400000)/",
                "createdDateTime": "/Date(1577751493000+0000)/",
                "entityOID": "e18bcfdb-3bb8-482f-ba4a-74789cf66230",
                ...}

In the previous version, the property was not available in FOCostCenter and FOCompany.

We enhanced the EmpEmployment OData API to enable navigation to the OnboardingInfo MDF OData API. We built this feature to support rehire with old employment details

123456789101112131415161718192021222324252627
{
    "__metadata": {
      "uri": "https://<api-server>/odata/v2/EmpEmployment(perso‍nIdExternal='HQ0001',userId='HQ0001')",
      "type": "SFOData.EmpEmployment"
     },
     "personIdExternal": "HQ0001",
     "userId": "HQ0001",
     ...
     "onboardingInfoNav": {
          "__metadata":{
            "uri": "https://<api-server>/odata/v2/OnboardingInfo('06BD')",
            "type": "SFOData.OnboardingInfo"
          },
          "externalCode": "06BD",
          "processStatus": "NOT_CREATED",
          "processHireStatus": "NOT_STARTED",
          "targetDate": null,
          "onboardingStableId": null,
          "processSubType": "REHIRE_OLD_EMPLOYMENT",
          "processType": "ONBOARDING",
          "user": "HQ0001",
          "userNav": {
            "__deferred":{
              "uri": "https://<api-server>/odata/v2/OnboardingInfo('06BD')/userNav"}
            },
      },
}

We added the mdfSystemRecordId property to some Metadata Framework (MDF) Foundation Objects (FO) OData APIs. MDF FOs, also known as migrated FOs, refer to the Employee Central FOs that have been migrated to MDF. We built this feature to align MDF FO OData APIs with MDF OData APIs, as all MDF OData APIs contain this property.

The impacted MDF FO OData APIs are as follows:

FOBusinessUnit, FOCompany, FOCostCenter, FODepartment, FODivision, FOJobCode, FOJobFunction, FOPayGroup

In the current version, you can get entityOID in FOCostCenter and FOCompany.

123456789101112
{
                "__metadata": {
                    "uri": "https://<api-server>/odata/v2/FOCompany(externalCode='1510',startDate=datetime'1970-01-01T00:00:00')",
                    "type": "SFOData.FOCompany"
                },
                "externalCode": "1510",
                "startDate": "/Date(0)/",
                "country": "JPN",
                "lastModifiedDateTime": "/Date(1628256460000+0000)/",
                "lastModifiedBy": "v4admin",
                "mdfSystemRecordId": "4DE9547935524902A1B016C8C36A7A68",
                ...}

We added the property employmentId to OData API EmpEmployment to identify an employment record.

We made this enhancement to offer you a new way of consuming data in EmpEmployment.

In the current version, the property employmentId is available in OData API EmpEmployment.

12345678910111213141516171819202122232425
{
    "d": {
        "results": [
            {
                "__metadata": {
                    "uri": "https://<api-server>/odata/v2/EmpEmployment(personIdExternal='HQ0001',userId='HQ0001')",
                    "type": "SFOData.EmpEmployment"
                },
                "personIdExternal": "HQ0001",
                "userId": "HQ0001",
                "hiringNotCompleted": false,
                "isECRecord": true,
                "lastModifiedDateTime": "/Date(1582694474000+0000)/",
                "serviceDate": null,
                "endDate": null,
                "bonusPayExpirationDate": null,
                "createdDateTime": "/Date(1582694468000+0000)/",
                "employmentId": "115",
                ...
            }
        ]
    }
}

 

You can now use the property isEarning as a filter when you query OData API FOPayComponent.

We made isEarning filterable so that you can get a list of earnings or deductions only.

In the current version, the property isEarning is filterable. For example, you can get a list of earning records through this request: https://<api-server>/odata/v2/FOPayComponent?$filter=isEarning eq true&$format=json.

In the previous version, the property isEarning wasn't filterable.

We made the property issueDate part of the composite business key in OData API EmpWorkPermit.

With this enhancement, EmpWorkPermit now has the following key properties:

• country
• documentType
• documentNumber
• userId
• issueDate

Now, if you want to query a work permit by business key, you must include issueDate in the key predicate. For example, https://<api-server>/odata/v2/EmpWorkPermit(country='44',documentNumber='DF112345DD-A',documentType='9944',issueDate=datetime'2014-05-12T00:00:00',userId='HuJoyce').

Please review the usage of OData API EmpWorkPermit in your organization and make adjustments accordingly.

If you want to delay adopting this feature, you can go back to all the original behaviors (except the one specified in the following note) by selecting Exclude Issue Date from Work Permit Business Keys in OData API EmpWorkPermit under Admin Center Company System and Logo Settings. After you change this option, remember to refresh OData API metadata before using EmpWorkPermit.

You can now import picklists and picklist values from Employee Central to the SAP S∕4HANA system by using OData query.

A new integration package SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: Generic Data in SAP Cloud Integration is provided. This package contains the integration flow Replicate Generic Data from SAP SuccessFactors Employee Central to SAP ERP or SAP S/4HANA Using the OData API, which you can use to replicate entities such as picklists from Employee Central into the SAP S∕4HANA system. A new report in the SAP S/4HANA system is now available to use this integration flow and import the picklists and picklist values from Employee Central into the SAP S/4HANA system. You can use the imported picklists and picklist values in SAP S∕4HANA when defining value mappings in Customizing to map Employee Central field values to the values of SAP S∕4HANA fields.

Support package 02 of the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on must be installed in your SAP S/4HANA system.