For activation of the customer exit, a project with this extension (MWMRP003) must be created using Transaction CMOD. The coding of the customer exit must be stored in the include ZXLRPU03.

The customer exit is called up on the screen immediately before list output. At this point, all the quantity calculations have been made. All relevant information is passed on to Table T_LRPL. The replenishment quantity calculated by the system is stored in the field OFMNG. From a technical point of view, all fields of the table can be changed. However, we only recommend changes to the fields LGORT and OFMNG.

The data changed by the customer exit can be seen in foreground processing in the list output. In background processing, TR creation takes place with the data changed by the customer exit.

If the request quantity was reduced by the customer exit, the following situation can occur in foreground processing. Example: the customer exit reduces the quantity from 10 to 9 pcs. The user presses the function key "Staging" on the list output screen. Within the program, a TR item is created in the internal tables for 9 pieces. Before the list output is created again, the system calculates the replenishment quantity. Here, this internal item is already taken into consideration. In the above constellation, the standard program proposes again a replenishment quantity for 1 piece. If the user were to choose the function key for "Save" in the present situation, the system would create a transfer requirement item for 9 pieces. With the function key "staging", again an internal item for 1 piece would be created. When you save the data later on, the system would accumulate these two items into one item of 10 pieces. To prevent this, you should - when you reduce the requested quantity, for example - increase the same quantity in the field VERME.

As a rule, it is thus possible to delete items in the internal table
Function/Program:

• EXIT_RLLNACH1_003: User Exit for Changing TransReqmts Generated from Replenishment Report