In the latest SAP SuccessFactors People Profile, administrators often encounter a discrepancy where the Amount and Percentage fields are visible in the Full Profile view mode for Recurring and One-Time Payment portlets but remain hidden in Edit mode or the Business Configuration UI (BCUI). This behavior is a deliberate design choice within the universal profile experience to improve data clarity for end-users while maintaining a streamlined configuration model in the backend.
As of the 1H 2026 release, the latest People Profile view experience is universal and cannot be disabled https://userapps.support.sap.com/sap/support/knowledge/en/3527163. This transition consolidates employee data into a single Full Profile view, which introduces specific UI behaviors for compensation-related data that differ from legacy profile configurations. Understanding how the system maps the underlying 'value' field to these UI-specific labels is essential for accurate troubleshooting and system validation.
Understanding the Amount and Percentage Field Logic
The primary cause for the perceived discrepancy in field visibility is the consolidation of data fields between the database and the user interface. In the Business Configuration UI (BCUI), SAP SuccessFactors uses a single field labeled 'value' to capture both monetary amounts and percentage figures for pay components. While only this 'value' field is enabled and configured in the backend, the latest People Profile dynamically renders two distinct labels—Amount and Percentage—in the Full Profile view mode to enhance the user experience https://userapps.support.sap.com/sap/support/knowledge/en/3527163.
This dual-label display in view mode is intended to provide immediate context to the user regarding the nature of the pay component. For example, if a pay component is defined as amount-based, the UI displays the data under the Amount label. Conversely, if the component is percentage-based, it appears under the Percentage label. Because these labels are UI-driven representations of the single 'value' field, they do not exist as independent, enableable fields within the BCUI or the Edit mode of the portlet.
Implementation and Validation for Administrators
Solution architects and administrators should recognize that this behavior is classified as expected system behavior and does not require a configuration fix. When validating the visibility of Recurring Pay Components or One-Time Payments in the Full Profile, the focus should remain on the configuration of the 'value' field. If the 'value' field is correctly enabled in the BCUI, the system will automatically determine which label (Amount or Percentage) to display in the Full Profile view based on the pay component's underlying definition.
It is important to note the rollout timeline for these experiences. While the Full Profile view became universal in 1H 2026, the Full Profile Edit and History experience for Compensation Information was introduced as an opt-in feature during the same period https://userapps.support.sap.com/sap/support/knowledge/en/3527163. Administrators should verify their current release version and opt-in status when troubleshooting why certain fields appear differently in Edit mode versus View mode. If a field is missing in Edit mode but visible in View mode, it is likely because the UI is splitting the 'value' field into user-friendly labels that are not supported in the current editing interface.
Next Steps for Profile Management
To ensure consistency across the latest People Profile, administrators should audit their pay component configurations to ensure the 'value' field is properly permissioned and enabled. Since the latest People Profile mobile experience mirrors the web experience, these UI behaviors will generally be consistent across both platforms. If discrepancies persist beyond the 'value' field mapping, administrators should refer to the latest migration documentation to ensure all HRIS-based elements have transitioned correctly to the new Full Profile architecture.
No comments:
Post a Comment