Exclude blocked (or marked for deletion) customers from appearing in future transactions

[krzysztofacc]

Dears,
The case is that I have a customer who has a lot of Ship-to assigned, and I need to block/delete a few of them so they are not visible when processing (new) Sales orders.

I blocked them and marked them for deletion (using XD05 and XD06 for all areas, etc.), but when creating a Sales order, I still see them in the 'Partner selection' pop-up when choosing the Ship-to address for that customer. The correct error message appears when I select one of them ("There is an order block for customer..."), but they are still visible on the list, which causes confusion for other users.

How can I process these customers/Ship-to to exclude them from being visible in future sales documents?
(SAP ECC 6.0 Enh Pack 5)

P.S. I know there is an available transaction to completely remove customers (OBR2), but this should be a last resort, used only if there are no other options and no open transactions.

Reagrds
Krzysztof

[Karine45Folk]

Dear Krzysztof, Blocking or marking Ship-to customers for deletion (XD05/XD06) in SAP ECC prevents processing, but it doesn't hide them from the 'Partner selection' pop-up in sales orders. To achieve this, your most robust solution is to implement a User Exit or Business Add-In (BAdI), such as centura health login within MV45AFZZ, to add custom ABAP code that filters the F4 help results and excludes these blocked or deleted Ship-to partners from the list presented to users.

[Lakshmipathi]

There is no standard provision to address this. As suggested, you can consider user exit but instead of hard coding the Ship-Tos, what you can do is to add such of those Ship-Tos in TVARVC table along with order type or document type. With this, via mv45afzz, as and when new sale orders are created, system, in the backend, should cross check this table and if the Sold-To combination is same, then, should hide the corresponding Ship-Tos. By doing so, even the Business users can add more Ship-Tos via SM30 and no need to depend on ABAP team for code change