Hi,

I can think of:

1. Make ‘Customer Part No’ field mandatory in customer order line and then configure it in Sales Part Cross Reference for the customers that can use related sales parts. Error raised when trying to save order line and Customer Part No is empty would warn sales person to not use such part
2. Create a custom field in Sales Part Cross Reference to indicate that such sales part is not usable for this customer (or either insert a ‘dummy’ Customer Part No to indicate that condition). Then, create a custom event triggered when creating new line that raises the desired error message if such custom field or Customer Part No has the value for ‘not usable’.

Both options need to use Sales Part Cross reference, as it’s the natural window to relate Sales Part with Customer, but perhaps you can establish naming conventions for ‘usable’ or ‘non usable’ sales parts that could also be used in custom event to trigger the error. This, would then imply more code in PL/SQL block of event action.

Regards,

Pilar