2576266 - Error while executing an iFlow in CPI: "Edm Exception: edmx parsing failed. name pattern not valid"

You notice the following error while executing an iFlow in CPI:

ERROR:

com.sap.gateway.core.ip.component.odata.exception.OsciException: Request Payload Parsing Failed for one of the reason: (1) Either the OData metadata content available in the server is outdated OR (2) The request payload seems to be incorrect. Error Details : Edm Exception: edmx parsing failed., org.apache.olingo.odata2.api.edm.EdmException: 'Background_VarPayEmpHistData-LTAP' name pattern not valid

• SAP SuccessFactors
• SAP Cloud Platform Integration

• The root cause for this error is that there is an entity with name "Background_VarPayEmpHistData-LTAP" which has special character hyphen "-" .
• As per the OData specification entityset, association & properties should not contain special characters. From an OData prospective, SAP cannot support such scenarios, i.e. the entity name should follow the standards as explained in the specification.
• Here is the specification: https://msdn.microsoft.com/en-us/library/dd541274.aspx

Follow the below steps:

1. Rename the entity without the hyphen to get the issue resolved. For example you can rename entity name to Background_VarPayEmpHistData_LTAP.
2. To fix this, please coordinate with your implementation partner to have this field renamed.
3. Please note that before making the above mentioned changes, you need to back up all the data related to this background element since it will be removed after changing the ID.
4. If there are other mappings related to the erroneous field, you will also need to remap those.
5. It is recommended that you perform such change on BCUI (Manage Business Configuration) and afterwards run the Synchronize Business Configuration job, as per KBA 
   2231503 Synchronize Business Configuration Job Configuration via Scheduled Job Manager.
6. Once done, kindly perform a metadata refresh as per KBA 2171588.
7. If after performing all above steps, the Background Element name is still the same, you must perform these changes on the (Succession) Data Model, located on Provisioning. And again, after performing this change, you should perform a metadata refresh as per KBA 2171588.

• 2171588 - SuccessFactors: OData API Metadata Refresh and Export
• 2231503 Synchronize Business Configuration Job Configuration via Scheduled Job Manager

com.sap.gateway.core.ip.component.odata.exception.OsciException, Edm Exception: edmx parsing failed, org.apache.olingo.odata2.api.edm.EdmException, HCI, iFlow, CPI , KBA , LOD-SF-INT-CPI , Standard SF to 3rd Party CPI (HCI) Content , LOD-SF-INT , Integrations , LOD-SF-INT-CPI-TPI , Standard SF to 3rd Party Integration using CPI , LOD-SF-INT-CPI-ERP , Standard SF to SAP ERP or S/4HANA Integration using CPI , Problem