In CCB 2.9.0.1.1, there is a base batch C1-CSRMP (Customer Service Request Periodic Monitor Process). This batch is unable to complete CS Requests when the related Premise has more than 50 characteristics.
We raised a Product SR and were informed that there is no enforced UI limit preventing users from adding more than 50 Premise characteristics, because the data model supports them and they are considered valid. However, batch processes such as C1-CSRMP are subject to strict architectural and technical constraints. These processes were designed with defined scalability boundaries related to memory allocation, object loading, and batch framework performance. When a Premise accumulates a high number of active characteristics, the volume of data that must be loaded and evaluated exceeds those thresholds, and the batch engine cannot reliably process the record.
Our client has approximately 30K Premises with more than 50 characteristics. When Start/Stop/Transfer is requested for these Premises, C1-CSRMP is unable to transition the CS Request from “Waiting for Completion” to “Complete.” In the batch run tree, it throws the following error:
Customer Service Request Premise (%1) cannot be updated or deleted because its parent does not allow update/delete.
Message Numbers: 11131, 11326
While this does not impact core functionality, it results in unnecessary reprocessing of these CS Requests during each batch run and repeated errors in the batch run tree. The error count has grown to 600+ in the last three months.
We would like Product to review this behavior and consider it as an enhancement request.
Any feedback or suggestions would be appreciated. Thank you.