Prevent usage of blocked customer in other objects

[DAcker]

Hi community,

it is the default that blocked customer cannot be used in other objects as tickets or opportunities.

But, do I have to maintain the status "blocked" manually? We have a ERP customer replication live, so every time blocking fields are maintained in ERP, there is no one that manually set the customer status to "blocked". Hence, if the customer have blocking fields maintained the status is still "active" and I still can use these customers in other objects.

There existis 4 blocking fields in the customer - overview (Oder Block, Delivery Block, Billing Block and Sales Support Block) and the same 4 fields in the customer - sales data.

Does the standard as well provide a process that when these fields are maintained the status is changed to "blocked"? (If the is a standard process, I do not want to bypass the standard ...)

Workaround: I test it to create a workflow setting the customer status in "blocked" if some data is maintained in the 4 blocking fields from account overview. This works fine even with the erp replication. But the blocking fields of the sales data are not considered...

Thanks & best regards,

Deborah

[manideepsatya]

Hello Deborah,

You can achieve this by doing a manipulation in middleware (when any block is true then set the lifecyclestatuscode accordingly) and restrict these accounts to be added into other documents by setting the queries.

Regards,
Manideep Satya