Ansicht
Dokumentation

MWMRP004 - User Exit for Replenishment using RLLNACH4

MWMRP004 - User Exit for Replenishment using RLLNACH4

ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

With this customer exit it is possible to change the transfer requiremen ts to be created by the replenishment report RLLNACH4. In particular, this customer exit has been created to change the storage location of the transfer requirement if you manage the stocks of several storage locations in one warehouse number.

To activate the customer exit, you must first create a project with thie enhancement (MWMRP003) using Transaction CMOD. The coding of the customer exit must be stored in the include ZXLRPU04.

The customer exit is called up immediately before list output on the screen. At this point, all the quantity calculations have taken place. All the relevant information is passed to table T_LRPL. The field for the storage bin (LGPLA) is always set to initial value. The replenishment quantity determined by the system is in the field OFMNG. Technically, it is possible to change all the fields in the table. However, we recommend that you only change the fields LGORT and OFMNG.

The data changed by the customer exit is already visible in the list if you are in foreground processing. In background processing, the TR is created with the data changed by the customer exit.

If the requirement quantity has been reduced by the customer exit, the following type of situation can arise: the customer exit reduces the quantity from 10 to 9 pieces. The user presses the pushbutton "Staging" on the list screen. Within the system, a TR item is created in the internal tables for 9 pieces. Before a new list is created, the system calculates the replenishment quantity, taking this internal item into account. In this situation, the standard program would propose a new replenishment quantity of 1 piece. If the user would now press the pushbutton "Save", the system would create a transfer requirement item of 9 pieces. If the user pressed the pushbutton "Staging, again the syst em would create an internal item of 1 piece. If saved to the database, these two items would be accumulated to an item for 10 pieces. To preven t this from happening, you shoud increase the field

VERME by the same amount when you reduce the requirement quantity.

As a rule, it is possible to delete and create items in the internal table. Before transfer requirement items are created, the table entries are subjected to a plausibility check.






PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 2450 Date: 20240426 Time: 054144     sap01-206 ( 84 ms )