Manage Reservations

Description

Use this program to manage reservations.
You can process reservations with selected account assignments. Limit the latter on the selection screen by entering an interval of reservation numbers.

The base date exerts an influence on the selection. Only those reservations whose headers contain a base date that is earlier than or equal 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 for NUMBER OF DAYS are defined for each plant in table T159L.

You can make the following pre-settings for the start of this program by 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 date earlier than or equal to the selected base date. Those reservations that 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 all reservation items. You process this in the same way as the list of reservations.

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

Requirement

You can only carry out this program if you have authorization for the activities 65 (reorganize) and 70 (manage) in the authorization objects Reservations: movement type (M_MRES_BWA) and Reservations: plant (M_MRES_WWA).

If all items for a reservation can be deleted, the system suggests the whole reservation for deletion.

If only individual reservation items can be changed, the system suggests only these items.

Output

Use the fields 'Log' and 'Issue log' to decide whether a log is to be issued 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 blocked from other transactions, it always issues an error log with the reservations 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 will check whether all the items of a reservation can be deleted. This is the case if the requirement date of the reservation item is earlier than the date calculated from 'base date - number of days'.

If the indicator 'Only closed items' has been set, the reservation item must, 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 entire reservation will be physically deleted. If this is not the case, those items that have fulfilled the deletion criteria will be marked with a deletion 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 the reservation 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. This can 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 no lock entries for reservations exist (regardless of whether these are suggested for change or not).
You should only choose the 'Do not block reservations' option if you have ensured that no one can make changes to manual reservations when the program is being run (using the function Change reservations or Goods movements with reference to reservations).