| Front page › Concepts › Branches | Search |
At its top level the library is organized into branches. Per definition, the branches comprise the top level of the location hierarchy - just under the municipality. Thus all other locations are a subdivision of the branches. (See an example of the hierarchy under locations). In certain areas branches are a special type of location but function also as a “common” location in relation to e.g. registering the distribution of items.
The branches are transmitted to IMMS from the LMS and list the overall potential distribution of items, transport units, and locations in IMMS.
Since the LMS defines the branches, it is not possible to edit/create them in IMMS. However, it is possible to indicate in IMMS whether or not an individual branch is active in IMMS. If a branch is inactive, it is hidden in IMMS (e.g. in lists of options in the web client). This is typically used for branches that have been transferred from the LMS but are not actually in use.
Users are also given access/permissions to perform specific actions in IMMS on the branch level.
Each branch has a property that determines whether or not the branch is included in IMMS. Typically, branches are included in IMMS when transferred from the LMS, but it is possible to change this manually so that the branch is kept outside of IMMS.
Please note: If a branch is not active in IMMS, it cannot be included in IMMS.
If a branch is not included in IMMS, it affects the intelligent distribution algorithm’s treatment of the branch:
Refer otherwise to the “Fixed item never on media hotel” branch parameter.
If a branch is not included in IMMS, it also means that items with a fixed relationship to the branch are not included in IMMS. Furthermore, this has a bearing on automatic life cycle management and certain reports, among others.
Please note: Modifying whether or not a branch is included in IMMS can potentially affect quite a few items.
For this reason, it is not immediately recalculated whether the items are included in IMMS since this can cause long delays and bog down the system.
Recalculations are run in the time frame defined by the two system parameters “Start time of the time-window for activation of branch configurations" and "Branch configuration activation time window end”.
A branch can be closed for a period via the Web Client. If the branch is closed, a start date must be set, and an end date can be set. Start date and end date are both included in the closed period.
In the period where the branch is closed, items are not assigned to the branch. Likewise, replenishment orders are not generated by the automatic replenishment routine, weeding orders are not generated by the automatic life cycle management, and error correction orders are not generated by the automatic error correction of misplaced items routine for the branch.