Symptom
After a user manually updates their fixed values in the My Purchase Requisitions - New app, the system does not consistently apply the updated values when creating a new material or catalog item. Instead, the system often retains and applies the fixed values that were set prior to the manual change. This leads to incorrect or outdated user data being populated in new requisitions, without any error messages or warning indicators.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Manually change user fixed values in the My Purchase Requisitions - New app.
- Create a material item or catalog item.
- Observe that the system does not always adopt the user fixed values correctly, often using the data before the manual change.
Cause
The issue is caused by a caching mechanism implemented in the underlying framework to minimize database calls to the backend system. This cache can lead to inconsistencies in the My Purchase Requisitions - New app, as it may not always immediately reflect the latest user fixed values updated through the Default Settings for Users app. As a result, outdated values may be applied when creating new material or catalog items.
Resolution
To ensure that the latest user fixed values are correctly applied in the My Purchase Requisitions - New app, follow one of the steps below:
-
Use the Default settings for users app, accessible from the profile button in the top-right corner, to make changes to user fixed values.
-
After making changes, navigate back to the home screen and then reopen the My Purchase Requisitions - New app to bypass any caching issues.
-
Alternatively, log out and log back in before using the app to ensure the updated values are loaded correctly.
Keywords
user fixed values, purchase requisitions, cache mechanism, inconsistent transfer, approval procedures, company codes, cost centers, sap s/4hana cloud, self-service requisitioning, fiori Ui, buffer issue, debugging session. , KBA , MM-PUR-REQ-SSP-2CL , Fiori UI for Self Service Procurement (Public Cloud) , Problem
SAP Knowledge Base Article - Public