Create / Import new Locations
New Location Structure:
Physical locations represent warehouses and their hierarchical structure. These are generally the locations that are managed by traditional stock management systems.
Partner locations represent your customer’s and supplier’s stocks. To reconcile them with your accounts, these stores play the role of third-party accounts. Reception from a supplier can be shown by the movement of goods from a partner location to a physical location in your own company. As you see, supplier locations usually show negative stocks and customer locations usually show positive stocks.
Virtual locations as counterparts for production are used in manufacturing operations. Manufacturing is characterized by the consumption of raw materials and the production of finished products. Virtual locations are used for the counterparts of these two operations.
Inventory locations are counterparts of the stock operations that represent your company’s profit and loss in terms of your stocks.
First it requires to prepare CVS import files, currently we use 4 level structure which follows as : Country, zone, organisation unit, location.
Country Level Import CSV
Import Country level first
Example Table
id | code | chained_location_type | chained_auto_packing | name | usage | Stock Location Level | Company | Parent Location | Organisation Unit |
---|---|---|---|---|---|---|---|---|---|
stock_rwanda_location_1 | RW | None | Manual Operation | Rwanda | View | Country | Bboxx Capital Rwanda |
Example csv file: stock.location.top.level.csv
Zone Level Import CSV
Please note that Parent Location has to exist in database
id | code | chained_location_type | chained_auto_packing | name | usage | Stock Location Level | Company | Parent Location |
---|---|---|---|---|---|---|---|---|
stock_zone_location_1 | K | None | Manual Operation | Kigali Central | View | Zone | Bboxx Capital Rwanda | Rwanda |
Example csv file: stock.location.second.level.csv
Organisation Unit Level Import CSV
Please note that both Parent Location and Organisation Unit has to exist in database
id | code | chained_location_type | chained_auto_packing | name | usage | Stock Location Level | Company | Parent Location | Organisation Unit |
---|---|---|---|---|---|---|---|---|---|
rwanda_stock_shop_1 | 30A | None | Manual Operation | Kigali | View | Organisation Unit | Bboxx Capital Rwanda | Rwanda | Kigali |
Example csv file: stock.location.third.level.csv
Location Level Import CSV
id | code | chained_location_type | chained_auto_packing | name | usage | Stock Location Level | Company | Parent Location |
---|---|---|---|---|---|---|---|---|
stock_shop_location_10 | MK | None | Manual Operation | Marketing | Internal Location | Location | Bboxx Capital Rwanda | Kigali |
stock_shop_location_11 | TI | None | Manual Operation | Replacement in | Internal Location | Location | Bboxx Capital Rwanda | Kigali |
stock_shop_location_12 | CI | None | Manual Operation | Connectivity Investigation from replacement | Internal Location | Location | Bboxx Capital Rwanda | Kigali |
stock_shop_location_13 | RI | None | Manual Operation | To repair In | Internal Location | Location | Bboxx Capital Rwanda | Kigali |
stock_shop_location_14 | MS | None | Manual Operation | Main Stock (For sale) | Internal Location | Location | Bboxx Capital Rwanda | Kigali |
stock_shop_location_15 | LT | None | Manual Operation | Lost | Internal Location | Location | Bboxx Capital Rwanda | Kigali |
Example csv file: stock.location.forth.level.csv
Column Name | Explanation |
---|---|
id | A unique identifier must be unique in the whole stock location table (Otherwise it will replace old record) |
code | Identifier of location used internally to identify specific locations |
chained_location_type | Determines whether this location is chained to another location, i.e. any incoming product in this location None: No chaining at all form of the Partner that is specified in the Picking list of the incoming products. |
chained_auto_packing | This is used only if you select a chained location type.
Manual Operation: the stock move has to be validated by a worker. Automatic No Step Added: the location is replaced in the original move. |
name | Name of the location |
usage | Supplier Location: Virtual location representing the source location for products coming from your suppliers                       View: Virtual location used to create a hierarchical structures for your warehouse, aggregating its child locations ; can't directly contain products                       Internal Location: Physical locations inside your own warehouses,                       Customer Location: Virtual location representing the destination location for products sent to your customers                       Inventory: Virtual location serving as counterpart for inventory operations used to correct stock levels (Physical inventories)                       Procurement: Virtual location serving as temporary counterpart for procurement operations when the source (supplier or production) is not known yet. This location should be empty when the procurement scheduler has finished running.                       Production: Virtual counterpart location for production operations: this location consumes the raw material and produces finished products |
Stock Location Level | Possible options right now: Country Zone Organisation Unit Location |
Company | Company name. |
Parent Location | Its a relationship field to link another location which would be parent. |
Organisation Unit | Name of the organisation this location is linked (Usually needed only on 3 level) |
How to import in ERP
Go to Stock Move tool → Location and then click Import
Once clicked import click browse to upload a file:
After file is uploaded click validate to check if everything is fine
After that if validation is successful click import to import. If its not successful read error message