2555699 - EC Field with maximumFractionDigits is not being respected when information migrated to Odata API or Running Report

•  Customer created a custom-double field and set the "maximumFractionDigits" to be a specific number, for instance "2". When saving data like 1000,4533 in that custom field, the Job Information portlet shows the 1000,45 value in the new record. However when checking information in Ad Hoc or OData API, the result for that field will be the complete value, for our example it should appear 1000,4533.

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 - All Versions

1.  Go to Job Information portlet
2.  Insert a New Record and edit the custom double field you have created, insert the value 1000,4533 and hit save
3.  Go to the new record the system created, you will see that the value of that field is 1000,45. This is correct because you set the maximumFractionDigits to be "2". So the portlet should show only two decimals
4.  Run ad Adhoc Report or Check the data in OData API, it will appear 1000,4533 and not 1000,45. The system is not respecting the maximumFractionDigits value.

See

Under compensation

<hris-element id="compInfo">

<label>Compensation Information</label>

<hris-field id="custom-double11" visibility="both" maximumFractionDigits="2">

    <label xml:lang="en-DEBUG"> SAP_Actual Annualized Salary </label>

      <label xml:lang="en-US"> SAP_Actual Annualized Salary </label>

    </hris-field>

Update or make a change

Result:

• Expected Behavior: should round as per  <hris-field id="custom-double11" visibility="both" maximumFractionDigits="2"
• Actual Behavior: compensation: <hris-field id="custom-double11" visibility="both" maximumFractionDigits="2" round value to 2 but in report is rounding to 3

•  It is an expected behavior in Odata API and Ad Hoc. For now, Odata API expose data in database directly and it do not change the data base on the maximumFractionDigits configuration in data model.

• This is currently working by design. The only workaround is to create a rule that will round the value that you are entering and will not allow you to save more than the decimals you specify in the maximumFractionDigits  configuration. For create this rule, please contact your Implementation Partner.
• Consider that SAP Support do not create Business rules, this is an Implementation Request.

Note:

This is expected behaviour, adhoc report: example: 2336732 - Pay Component Groups or Annualized Salary Missing Data in Ad Hoc Reports) is retrieving the data from the Database and is not formatting as the comp info UIs are. Hence in adhoc and for custom double fields: (<hris-element id="compInfo">     <label>Compensation Information</label><hris-field id="custom-double11" visibility="both" maximumFractionDigits="2 ) , the exact number of decimal will be shown.

FAQ - Additional Information

Q) Where can I find information on this from the Guides?

A) Guide: Business Rules Implementation Guide

Chapter: Round

A) Guide: Implementing Employee Compensation Data in Employee Central

Chapter: Pay Component

• 2879853 - Pay Component and Calculated Amount Rounding
• 2459176 - Cannot round Pay Component Group Values
• 2193766 - Numeric values in Compensation Information for employees are truncated to 2
• 2537783 - How To Change Decimal To Integer
• 2796879 - How To Run An Adhoc Report for Pay Component Group Name or Pay Component Group ID
• 2336732 - Pay Component Groups or Annualized Salary Missing Data in Ad Hoc Reports
• 2280229 - What is an Implementation request in Employee Central?
• 2287005 - Configuration Changes - Scope of Product Support for Employee Central

Employee Central, maximumFractionDigits, Odata API, Decimals, Pay Component , KBA , LOD-SF-EC-JOB-UI , History UI & MSS UI , LOD-SF-EC-CMP-RUL , Business Rules , LOD-SF-EC-REP , Reporting Data (EC core only) , LOD-SF-EC-CMP-UI , History or MSS UI , Problem