Hi:

If you don’t want to make any specific development, the only thing I can think about this issue is to use an access code. The worst thing about access codes: they need a lot of admin work.

If you decide to make a specific development, you could create a field in the BANK table with the name ENAFLG, and also add this field in the screen (BAN0, BAN1... whatever). This field corresponds to an active/inactive checkbox. As the BANK table is managed by an object (BAN) and there is a data type associated to the BAN object, you will get the BAN type fields to do the following:

1. The standard selection window for the object called by the selection key will automatically filter inactive records.
2. An error message will prevent the direct entry by its inactive key code.

It seems very simple... but I don't know if there may be "collateral effects"... it will have to be tested in a test environment.

Hi:

If you don’t want to make any specific development, the only thing I can think about this issue is to use an access code. The worst thing about access codes: they need a lot of admin work.

If you decide to make a specific development, you could create a field in the BANK table with the name ENAFLG, and also add this field in the screen (BAN0, BAN1... whatever). This field corresponds to an active/inactive checkbox. As the BANK table is managed by an object (BAN) and there is a data type associated to the BAN object, you will get the BAN type fields to do the following:

1. The standard selection window for the object called by the selection key will automatically filter inactive records.
2. An error message will prevent the direct entry by its inactive key code.

It seems very simple... but I don't know if there may be "collateral effects"... it will have to be tested in a test environment.