...
This problem occurs when the Price Setting Type (PLPGTT) configuration is either formatted incorrectly or missing. The first step is to be sure that you are working on a PL/LPG of the correct type. If this is the case, check its configuration on the Price Setting Types page and correct it accordingly.
Refer to https://pricefx.atlassian.net/wiki/spaces/UDEV/pages/4354605149/Technical + User + Reference+PLIS#Configuration-in-PLPGTT for more details.
...
Error during Calculation with Keywords: “javaheap” “vmem”, “memory” or without Message
...
Error during the Run calculation: This means that the Optimization Engine did not have enough resources. This can be solved by asking the support to increase the RAM allocation for the OE. More information on this issue is available at https://pricefx.atlassian.net/wiki/spaces/UDEV/pages/2812149872/OE+Troubleshooting#Error-during-the-Run-calculation-with-keywords%3A-%E2%80%9Cjavaheap%E2%80%9D-%E2%80%9Cvmem%E2%80%9D%2C-%E2%80%9Cmemory%E2%80%9D OE Troubleshooting.
Error during the aggregating step: This step basically joins big SQL queries. The size of the transaction DM and of the Price List used can lead to massive queries running out of memory. Unfortunately, the solution here is not as easy as in the previous one and needs to optimize the queries themselves (like breaking the aggregating step into several phases, for example). If these modifications are insufficient, please contact the Pricefx Performance Team (/wiki/spaces/PERF/pages/1866104837) to improve the most critical queries and operations.
...