In Commerce, prospect contact users can be commissioned (refer to 'Commerce User Management' for additional information). By definition, pricing information will not be available since a corresponding ERP ID for the prospect account will be missing. To overcome this and for companies to allow access to prospects to view product catalogs and pricing information, the following settings need to be done:
- The prospect account needs to be assigned a specific organization unit under the sales data of the account. This organization unit e.g. can be generic where all prospect accounts can be combined (also, national or regional org units for this matter can be created).
- Go to 'Administration' -> 'Organizational Unit' and select the respective org unit. In the following field, the dummy ERP Account ID for which pricing is available can be maintained:
During a pricing call in Commerce, the application will evaluate the user's related account. If this account has the prospect flag set to True and it does not have an ERP ID maintained, the dummy ERP ID in the aforementioned figure will be used to retrieve pricing data.
Pricing Cache Configuration
Users from the same account and same sales area can experience faster loading times as pricing info will be read from a global cache instead of a session cache. To optimize the overall response time of the Commerce application, a pricing cache can be configured.
- Enable the pricing cache via 'Administration' -> 'Master Data Management' -> 'SettingBoolean' and set 'SettingCommerceUsingGlobalCache' to 'Yes'. If set to 'Off', the session cache will be used instead which caches pricing information on a user level.
- Additionally, the cache size (for both, Global and Session cache) can be controlled via 'Administration' -> 'Master Data Management' -> 'SettingNumeric' where the following field 'SettingCommerceUsingPricingCacheSize' holds the cache size.
The following table holds the recommended cache sizes (actual cache sizes might differ based on the number of users, products, and other parameters and need to be adjusted on a case-by-case basis):
|Cache Type||Cache Size (Number of Products)|
Note: Once the cache sized has been changed, a server restart is required.
Analyzing and Optimizing Pricing Cache
Accessible via the SAP Cloud Platform Cockpit, the JMX Console offers three (3) methods to analyze and clean up the cache:
These methods are:
returns statistics of the products in the cache such as:
|cleanupCache||clears the cache|
|cleanupCacheForExpiredDate||clears the cache for products that have been in the cache for more than 24 hours|
These three methods are only available for the Global Price cache. The Session cache, since it is managed on a user level, will automatically adjust the size based on the products needed.