INV - Inventory
Meta process
graph LR; %% Nodes A(INV<br>Inventory) B(INV-0010<br>Define inventory date) C(INV-0020<br>Create inventory) D(INV-0030<br>Determine target quantities) E(INV-0040<br>Capture counted quantities) F(INV-0050<br>Check and release inventory) G(INV-0060<br>Post inventory result) %% Flow A -.- B linkStyle 0 stroke:#ffffff B ==> C C ==> D D ==> E E ==> F F ==> G %% Classes class A btProcessTitle class B,C,D,E,F,G btProcessActive
The process describes inventory by means of an inventory order or the inventory journal. It includes inventory date management, determination of inventory target quantities, handling of differences, and inventory-affecting posting.
The recording of counted quantities is described in a separate process.
INV-0010 - Define inventory date
Using date management, inventory can be planned and controlled (in terms of time and personnel). In step 1, the inventory date is defined per warehouse location/branch. When delimiting the target quantities, the inventory cutoff date and also the cutoff precision are of great importance. In addition to the count date, this is also the date on which the inventory correction becomes effective. Inventories can be carried out as full inventory counts and also as inventory reconciliations. For support, article and brand filters can be used to influence which items are to be counted.
INV-0020 - Create inventory
An inventory order can be created or the inventory can be prepared via the inventory journal. In addition, inventory data can be imported via EDI using the INVRPT message type.
Incoming processes:
INV-0030 - Determine target quantities
On the cutoff date, the expected target quantities are also determined and displayed. If there is a large number of items, these can be split across several inventory orders / inventory dates. (see date management, item and brand filters).
Outgoing processes:
INV-0040 - Capture counted quantities
To determine inventory differences, the counted quantities are imported. This is done either by reading inventory files in the inventory order (as capture), by manual entry of the quantities, or by entering the inventory quantity in the inventory journal.
Incoming processes:
INV-0050 - Check and release inventory
The differences between the counted and expected quantities are shown as inventory differences and can additionally be printed in the difference document. Inventory differences are shown not only as quantities but also as values (cost value and sales value) depending on the sales and goods receipt quantity. These differences must be analyzed and made transparent. The following kinds of differences can occur: check transfer documents (transfer receipt/issue not posted); goods receipt not posted; DESADV not processed; theft, shrinkage, etc..
INV-0060 - Post inventory result
A completed inventory order or the capture in the inventory journal can finally be posted. By posting, the quantities managed by the application are adjusted to the captured actual quantities. This creates entries which on the one hand correct the inventory in the system (item ledger entries, value entries, and for bin-managed warehouse locations also bin entries) and on the other hand document the inventory process (inventory entries).
Instances
INV-INO - Inventory with inventory order
graph LR; %% Nodes A(INV-INO<br>Inventory with Inventory Order) B(INV-INO-0010<br>Define inventory date) C(INV-INO-0020<br>Create inventory) D(INV-INO-0030<br>Determine target quantities) E(INV-INO-0040<br>Capture counted quantities) F(INV-INO-0050<br>Check and release inventory) G(INV-INO-0060<br>Post inventory result) %% Flow A -.- B linkStyle 0 stroke:#ffffff B ==> C C ==> D D ==> E E ==> F F ==> G %% Classes class A btProcessTitle class B,C,D,E,F,G btProcessActive
The process describes carrying out inventory by means of an inventory order. It includes inventory date management, determination of inventory target quantities, inventory counting, handling of differences, and inventory-affecting posting. The inventory order describes the scope of the inventory to be carried out. It can be created manually or, as described, automatically on the basis of inventory date management.
INV-INO-0010 - Define inventory date
The list of inventory dates provides an overview of all inventories currently in progress with status values for the inventories. When the inventory date is confirmed, the status changes and thereby the release for further inventory processing steps described below takes place. First, the inventory date is defined per warehouse location/branch. The cutoff precision indicates to which posting date the correction is to be applied later (evening = count date or morning = day before the count). One inventory order is created per inventory date line. If there is a large number of items, these can be split across several inventory orders / inventory dates.
INV-INO-0020 - Create inventory
On the cutoff date, the inventory order is created. The inventory order describes the scope of the inventory to be carried out. It can be created manually or, as described, automatically on the basis of inventory date management. It consists of an inventory order header and any number of inventory order lines. In addition, article and brand filters can be used to influence which items are to be counted. In the inventory order itself, the scope of the inventory is influenced by the set filters (e.g. brand, merchandise group, season, or similar).
Incoming processes:
INV-INO-0030 - Determine target quantities
The expected target quantities are determined and displayed at SKU level in the form of inventory order lines, and the status of the inventory date is changed. The positions represent the book inventory of the system on the cutoff date, taking into account the previously set article filters. Since counting and inventory processing may take place at different times, an update of the target quantities (e.g. after subsequent posting of goods receipts) can improve the inventory result. Functions are available in the inventory order to update the target quantities.
Outgoing processes:
INV-INO-0040 - Capture counted quantities
To determine inventory differences, the counted quantities are imported. This is done either by reading inventory files in the inventory order (as capture) or by manual entry of the quantities (e.g. creation and printing of a capture document, manual count, documentation in the printout, and later transfer into the system).
Incoming processes:
INV-INO-0050 - Check and release inventory
The differences between the counted and expected quantities are shown as inventory differences and can additionally be printed in the difference document. Differences can be both positive and negative. This means that in order to adjust the system inventory to the counted inventory, both increases and decreases may be necessary. When all captures of an order are complete, the order itself can also be completed and released. To make corrections, the inventory order can be reset from status “Completed” to status “Open”. Corrections should be made as far as possible in the form of “correction captures”. All captures for an SKU are netted in the inventory order. Correcting quantities can therefore also be negative.
INV-INO-0060 - Post inventory result
A completed inventory order can finally be posted. By posting, the quantities managed by the application are adjusted to the captured actual quantities. This creates entries which on the one hand correct the inventory in the system (item ledger entries, value entries, and for bin-managed warehouse locations also bin entries) and on the other hand document the inventory process (inventory entries). Furthermore, the inventory order is archived and remains available later with all captures and postings for traceability.
INV-IWS - Inventory via journal
graph LR; %% Nodes A(INV-IWS<br>Inventory via Journal) B(INV-IWS-0010<br>Define inventory date) C(INV-IWS-0020<br>Create inventory) D(INV-IWS-0030<br>Determine target quantities) E(INV-IWS-0040<br>Capture counted quantities) F(INV-IWS-0050<br>Check and release inventory) G(INV-IWS-0060<br>Post inventory result) %% Flow A -.- B linkStyle 0 stroke:#ffffff B ==> C C ==> D D ==> E E ==> F F ==> G %% Classes class A btProcessTitle class B btProcessInactive class C,D,E,F,G btProcessActive
The process describes carrying out inventory via the inventory journal.
INV-IWS-0020 - Create inventory
The standard inventory journal is used for the inventory. A new or existing entry is created or modified, from which the inventory list per warehouse location is generated. Additional filters (e.g. at item level) are possible for generating the inventory list.
Incoming processes:
INV-IWS-0030 - Determine target quantities
When the inventory journal is created, the target quantities are automatically determined. The creation of the inventory journal should take place promptly before posting. Any corrections carried out (e.g. subsequent goods receipt or transfer) that affect the expected quantities should lead to the journal being recreated and thus to the target quantities being determined again.
Outgoing processes:
INV-IWS-0040 - Capture counted quantities
To determine inventory differences, the counted quantities are imported. This is done either by import or by manual entry of the quantities and entry of the inventory quantity in the inventory journal.
Incoming processes:
INV-IWS-0050 - Check and release inventory
The differences between the counted and expected quantities are shown as inventory differences and can additionally be printed in the difference document. Inventory differences are shown not only as quantities but also as values (cost value and sales value) depending on the sales and goods receipt quantity. In the case of incorrect captures, these are corrected directly in the journal.
INV-IWS-0060 - Post inventory result
After completion of capture in the inventory journal, it can finally be posted. By posting, the quantities managed by the application are adjusted to the captured actual quantities. This creates entries which on the one hand correct the inventory in the system (item ledger entries, value entries, and for bin-managed warehouse locations also bin entries) and on the other hand document the inventory process (inventory entries).
INV-EDI - Inventory via EDI
graph LR; %% Nodes A(INV-EDI<br>Inventory via EDI) B(INV-EDI-0010<br>Define inventory date) C(INV-EDI-0020<br>Create inventory) D(INV-EDI-0030<br>Determine target quantities) E(INV-EDI-0040<br>Capture counted quantities) F(INV-EDI-0050<br>Check and release inventory) G(INV-EDI-0060<br>Post inventory result) %% Flow A -.- B linkStyle 0 stroke:#ffffff B ==> C C ==> D D ==> E E ==> F F ==> G %% Classes class A btProcessTitle class B btProcessInactive class C,D,E,F,G btProcessActive
The inventory results for an area located on the customer side are read in and processed via a corresponding INVRPT to determine the inventory.
INV-EDI-0020 - Create inventory
The inventory order is created automatically when the INVRPT is imported.
Incoming processes:
INV-EDI-0030 - Determine target quantities
The target quantities are determined automatically during import and are found in the lines of the inventory order.
Outgoing processes:
INV-EDI-0040 - Capture counted quantities
The inventory capture is created automatically based on the counted quantities transferred in the INVRPT.
Incoming processes:
INV-EDI-0050 - Check and release inventory
The differences between the imported and expected quantities are shown as inventory differences and can additionally be printed in the difference document. The inventory order is completed. To make capture corrections, the inventory order can be reset from status “Completed” to status “Open”.
INV-EDI-0060 - Post inventory result
A completed inventory order can finally be posted. By posting, the quantities managed by the application are adjusted to the captured actual quantities. This creates entries which on the one hand correct the inventory in the system (item ledger entries, value entries, and for bin-managed warehouse locations also bin entries) and on the other hand document the inventory process (inventory entries). Furthermore, the inventory order is archived and remains available later with all captures and postings for traceability.