The cases that you should treat as a support incident are when a partner contacts Product Support regarding a platform with slow performance or when a partner requests information on how to customize the backoffice. These cases indicate that there might be a problem with the standard functionality of SAP Commerce Cloud or that the partner needs guidance on how to use the product features. The other cases are not support incidents because they involve custom solutions or architectural aspects that are beyond the scope of Product Support

You can assign the session to an admin user or any member of the admingroup to run a FlexibleSearchService query without restrictions. These users have the ROLE_ADMIN assigned to them, which allows them to bypass any restrictions applied to other users or user groups.

You can resolve the performance issue with DefaultStockService by implementing a CronJob that will clean the StockLevelHistoryEntry table according to customer business needs and by suggesting an improvement by creating a maintenance request for the customer. The CronJob can help reduce the size of the table and improve the query performance. The maintenance request can help inform SAP about the issue and request a possible enhancement or fix. You should not delete the content of the table directly from the database, as this may cause data inconsistency or loss. You should not run Cleanup Type System in the SAP Commerce Administration Console, as this will not affect the StockLevelHistoryEntry table.

The steps that you should do before you report incorrect software behavior to SAP (third-level support) are documenting the complete technical environment information of the system where the incident occurred and reproducing and validating the problem on the standard out-of-the-box SAP Commerce. These steps are necessary to provide SAP with enough information to analyze and resolve the issue and to ensure that the issue is not caused by customizations or extensions. Reference: 2

The properties that you can set to use Service Layer Direct are setting the sld.enabled modifier to True in the ImpEx file and setting persistence.legacy.mode and servicelayer.prefetch to False in the local.properties. Service Layer Direct is a feature that allows the service layer to interact with the persistence layer more efficiently and use fewer resources. It can be enabled on an as-needed basis in your Java code or when invoking ImpEx. You do not set persistence.legacy.mode to False in core-spring.xml, as this is not a valid configuration file for this property. Reference: 2