A. by transaction OXK1:
In customizing transaction 'OXK1' you can see which screens are available and in which order they are selected by the program.
This transaction also allows to add customer-defined screens, to change the priorities and to de-activate standard screens.
Create yourself a screen with all the fields you would like to see, and assign it in OXK1. Set the priority key so that program would choose your screen rather than the standard screens.
The system searches for the suitable subscreen according to the following strategy:
First, it searches for subscreens containing all the account assignment fields required. If there is more than one, it selects the one with the highest priority.
If this is unsuccessful, the system then looks for subscreens containing all of the obligatory fields, or as many of them as possible. The subscreen contains the obligatory fields.
If two subscreens contain the same number of obligatory fields, then the one containing the required account assignment fields is selected. If there is still more than one, the selection is made according to the priority.
Please see the following SAP KBA notes as reference for MB21 manipulation with OXK1 subscreens:
2027255 - Reservation creation, goods issue posting can be saved without an account
1534888 - Cost Center displays in wrong place of MB1*, MB2*
1860048 - Missing Account Assignment fields in MB1A
B. by user exit or BADI
Enhancement to manipulate reservation data is MBCF0007 and the user exit is EXIT_SAPMM07R_001.
MBCF0007 Customer function exit: Updating a reservation
MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0011 Read from RESB and RKPF for print list in MB26
There is a BADI as well:
MB_RESERVATION_BADI MB21/MB22: Check and Complete Dialog Data
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.