Description
Use this program to manage reservations.
You can process reservations with selected account assignments. Limitthe latter on the selection screen by entering an interval ofreservation numbers.
The base date exerts an influence on the selection. Only thosereservations whose headers contain a base date that is earlier than orequal to this date are taken into account.
Furthermore the computation of the NUMBER OF DAYS for 'deletion' or'allow movement' is carried out using this base date. The values forNUMBER OF DAYS are defined for each plant in table T159L.
You can make the following pre-settings for the start of this programby means of the appropriate entries in table T159L:
Report name BatIn Log
RM07RVER X X

• If you have placed a checkmark against the field "BatIn", the program
starts in a test run. In each case (regardless of the indicator 'Log'),the system will produce a list of all reservations having a base dateearlier than or equal to the selected base date. Those reservationsthat are to be changed can then be selected using the select functions.You can then initiate the changes to the data base by pressing F11.
The menu option 'Goto -> Reservation items' gives you a list of allreservation items. You process this in the same way as the list ofreservations.

• If the field 'BatIn'/'Test run' is initial, the data base changes are
made immediately.

Precondition
You can only carry out this program if you have authorization for theactivities 65 (reorganize) and 70 (manage) in the authorization objectsReservations: movement type (M_MRES_BWA) and Reservations:plant (M_MRES_WWA).
If all items for a reservation can be deleted, the system suggests thewhole reservation for deletion.
If only individual reservation items can be changed, the systemsuggests only these items.

Output
Use the fields 'Log' and 'Issue log' to decide whether a log is to beissued in the event that the data base is changed immediately ('BatIn'/'Test run' is initial).
If the system finds that the reservations to be changed are blockedfrom other transactions, it always issues an error log with thereservations that are not to be blocked.
For the blocked reservations, you must start the report again.

Example


• Delete reservation:

-------------------
Select the parameter 'Set deletion indicator/delete'. The system willcheck whether all the items of a reservation can be deleted. This isthe case if the requirement date of the reservation item is earlierthan the date calculated from 'base date - number of days'.
If the indicator 'Only closed items' has been set, the reservation itemmust, in addition, either have been completely issued/withdrawn(quantity < = quantity withdrawn) or marked with the 'final issue'indicator.
If all items of a reservation are marked as deleted, the entirereservation will be physically deleted. If this is not the case, thoseitems that have fulfilled the deletion criteria will be marked with adeletion indicator. However, the reservation will remain in the system.

• Allow goods movement:

---------------------
Set the indicator 'Allow goods movement'.
Provided that the requirement date lies within the period 'base date +number of days' the indicator 'Movement allowed' will be set in thereservation item.

• Lock mode:

-----------
You can decide which lock modus you want to choose.
The 'Block reservations individually' option is suggested, that is,only the reservations that are actually changed are to be blocked. Thiscan result in a number of lock entries.
To avoid this, you can select the 'Block table of reservations' option.This means, however, that the update can only be carried out when nolock entries for reservations exist (regardless of whether these aresuggested for change or not).
You should only choose the 'Do not block reservations' option if youhave ensured that no one can make changes to manual reservations whenthe program is being run (using the function Change reservations orGoods movements with reference to reservations).