Prevent of using limit order with certain acc. assignment category

[Former Member]

We have in total 4 different account assigment categories. One of them (Asset with GR - Y in the backend) we do not want it to be used in combination with a limit order.

So in the backend we did NOT maintain the combination between item category B and acc. assign cat Y.

But users then still can make the PO which will end up in error "Combination item category B/acc. assignment Y not defined" , as stated before this is OK want we would expect.

But is there any way to even prevent the user to make in SRM a limit order with acc assigment cat Asset / Y

[Former Member · Accepted solution]

You could manage by implementing the BBP_DOC_CHECK_BADI for your order (BUS2201).

[Former Member · Accepted solution]

Since its Item level validation BBP_ITEM_CHECK_BADI for object type BUS2121 will be more effective..

Thanks!!

Bharath

[Former Member · Accepted solution]

thx,

so we need to build a custom check. It is not like in backend you can configure which combinations are valid .

Martijn

[Former Member · Accepted solution]

No we canu2019t achieve this through configuration as we do for account assignment category in R/3..

Thanks!!

Bharath