Documents generated from IO

Generating WM- from IO

A WM- generated from an IO allows for releasing items from a source warehouse to a target warehouse.

It is possible to generate a WM- in a center, in which to WM- document type the warehouse being a source warehouse on a confirmed IO document is assigned.

The features selected on an item/subitem of an IO are included, with a possibility of editing them on the generated WM-. It is possible to generate many WM- documents to one IO:

  • the quantity in a WM- document can be decreased/increased in relation to the quantity in an IO
  • while generating a WM- document, the system checks the quantity which has already been “released” with other WM- generated from the IO – if WM- documents have already been generated for all items included in the order, then the system blocks generation of another WM- and displays an appropriate message; otherwise, it generates another WM- for quantity remaining to be executed on the IO
Note
If in a WM- generated from an IO an item gets deleted and added again, the association between that item in the WM+ and the item in the IO will not be recreated.

A WM- document generated from an IO document is visible in the list of warehouse movements in the center issuing the IO and, in the centers, who own the source or the target warehouse indicated in the WM-.

Generating WM+ from IO 

A WM- generated from an IO allows for releasing items from a source warehouse to a target warehouse.

It is possible to generate a WM+ to a WM- in a center, in which to WM+ document type the warehouse being a target warehouse on a confirmed target IO document is assigned.

When generating a WM+ “purchase reservations” are processed, which were generated during the first confirmation of an IO.

Except for generating a WM+ from the level of the list of IO to a document from which a WM- was previously generated, the system enables also the standard method of generating WM+, from the level of the list of WM-.

In case many WM- documents were generated from an internal order and they are not yet associated with WM+ documents, then, when trying to generate a WM+ from the level of an internal order, the system displays a list of WM- documents associated with a given IO and allows a user to decide to which WM- the WM+ should be generated.

If many WM- documents were generated from an internal order, but to all of them, except for one, WM+ documents were generated, then the system immediately generates a WM+ to that WM-.

Generating PO from IO

A PO is generated from an IO to the source warehouse specified in the IO. It allows for handling a situation when there are insufficient resources in a warehouse from which one of the centers wants to order an item.

The system allows for generation of a PO from the center in which to PO document type the warehouse being the source warehouse on an IO document is assigned and if IO status is Confirmed.

Such generation is performed according to the same rules as generation of a PO from a SO. After the system is started, it displays a generation optimization window in which a user must decide whether all items from the source IO are to be included in the PO or only those not yet executed.

When generating a PO from an IO, the system also includes the features selected for items/subitems on the IO along with a possibility of editing them on the generated PO.

 

Czy ten artykuł był pomocny?