Difference between revisions of "StockItem ItemPacksIndex"

From SkySuite Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
+
<!-- Note to Page Author: Please update the tables to use real tables instead of images, see https://www.mediawiki.org/wiki/Help:Tables -->
Please use our [[Tips and Tricks]] page for understanding how the SkySuite portal works and how to navigate faster and easier.
+
{{Tips and tricks}}
  
 
__TOC__
 
__TOC__
  
<H1>Stock Item Packs</H1>
+
=Stock Item Packs=
 +
==Item Pack Levels - Introduction ==
  
<h2>Item Level</h2>
+
Level 1 of an item pack structure is always the stocking unit and every item must have a Level 1 pack record. Typically this is an "Each/Piece" but it could be a box or carton. It is important to note that all stock quantities are reported in the stocking unit (Level 1) and these quantities cannot be decimals which means that if you set your stocking unit to a box then you will not be able to issue or receive in eaches.
  
Firstly at Item Level you must define all the possible pack sizes against the item below, see example for Napkins, this comes/has come in 4 different pack sizes 320, 500, 750 or 1,000. In such a case the Stocking unit must be EA (Eaches) then we will have 5 Packs under this as below;
+
The next level up we need to define all the possible pack sizes for the item, see example below which shows an item that can come in 4 different pack sizes 320, 500, 750 or 1,000. In this case the Stocking unit is EA (Eaches) so we will have 5 Packs (1 Level-1 and 4 Level-2) for the item. Because we have 4 different Level-2 alternatives we give each one a structure code (key). A to D in the example below
  
 
[[File:Item_Packs_1.PNG|500PX]]
 
[[File:Item_Packs_1.PNG|500PX]]
Line 19: Line 20:
 
  6 BX/1000’s on a Pallet
 
  6 BX/1000’s on a Pallet
  
Then this would be created as;
+
Then the Pallets would be created as Level-3 packs;
  
 
[[File:Item_Packs_2.PNG|500PX]]
 
[[File:Item_Packs_2.PNG|500PX]]
  
When the above table is created in SkyLog you must identify one of the above structures as a default for issue but this is only used if there is no default at the Station Level see below.
+
When the above table is created in SkyLog you must identify one of the above packs as a default for issue but this is only used if there is no default at the Station Level see below.
 
 
 
 
<h2>Issuing out</h2>
 
  
It is possible in SkyLog to define a default issue pack size for each station/Item and also you define which stations are supplied by which stations.  
+
==Issuing out==
 +
It is possible in SkyLog to define a default issue pack size for each station/Item and also you define which stations are supplied by which warehouses.  
  
<U>Example</U>
+
===Example===
 +
If you have Coke that is supplied to the LIM warehouse in Boxes of 24 and supplied to the SAL warehouse in Boxes of 12 then you would set the default unit of issue for all the LIM supplied stations to 24 and for all the SAL supplied stations to 12. Although you would have also a default at Item level (see above) this will only be used if there is no default at the Station level. What then happens is any suggested quantity is rounded to the multiples of 24 for the LIM stations but to quantities of 12 for the SAL stations thus avoiding having the warehouse having to open boxes or manually round the quantities up or down.
  
If you have Coke that is supplied to LIM in Boxes of 24 and supplied to SAL in Boxes of 12 then you would set the default unit of issue for all the LIM supplied stations to 24 and for all the SAL supplied stations to 12. Although you would have also a default at Item level (see above) this will only be used if there is no default at the Station level. What then happens is any suggested quantity is rounded to the multiples of 24 for the LIM stations but to quantities of 12 for the SAL stations thus avoiding having the warehouse have to open boxes or manually round the quantities on their end.  
+
Now let's consider an example where there is mixed pack sizes in one warehouse because say you changed supplier. In this case you would have to leave all or some stations to use the old pack size until the inventory was depleted then switch over the default once all the old stock was burned off. The only other alternative would be to repack the old inventory to the new pack size.
  
Now lets consider an example where there is mixed pack sizes in one warehouse because say you changed supplier. In this case you would have to leave all or some stations to use the old pack size until the inventory was depleted then switch over the default once all the old stock was burned off. The only other alternative would be to repack the old inventory to the new pack size.
+
==Purchasing==
 
+
For each supplier of an item you can specify a different purchasing unit per warehouse so for example we could have
<h2>Purchasing</h2>
 
 
 
For each supplier of an item you can specify a different purchasing unit per warehouse so in the case of the Napkins where we could have
 
  
 
[[File:Item_Packs_3.PNG|500PX]]
 
[[File:Item_Packs_3.PNG|500PX]]
Line 44: Line 41:
 
In the above example all PO’s for J.J. REPRESENTACIONES Y SERVICIOS S.R.L.  would be rounded to 500 while all PO’s for AQL SOLUCIONES INTEGRALES S.A. would be rounded to 320 and PO’s for CEK DE GUATEMALA would be rounded to either 320, 750 or 1000 depending on what Warehouse they were for.
 
In the above example all PO’s for J.J. REPRESENTACIONES Y SERVICIOS S.R.L.  would be rounded to 500 while all PO’s for AQL SOLUCIONES INTEGRALES S.A. would be rounded to 320 and PO’s for CEK DE GUATEMALA would be rounded to either 320, 750 or 1000 depending on what Warehouse they were for.
  
Note that it is not possible have a mixture of Purchasing units defined for the same supplier/warehouse combination so if you have the situation where CEK DE Guatemala supplies in boxes of 1000 and 750 to SAL we need to stop that.
+
Note that it is not possible have a mixture of Purchasing units defined for the same supplier/warehouse combination.
 
 
<h2>Consequences/Actions</h2>
 
 
 
1. For those items where the pack quantities are so varied the Stocking Unit in Oracle must be Eaches it cannot be a Box
 
2. In the warehouse there should be a chart/paper on the location that explains the conversion form eaches to the box in order to eliminate the warehouse picking too much (i.e. assuming the qty is in boxes when in fact it is eaches). They will need to make a manual calculation ito convert. This step can be eliminate when proper units are implemented in Oracle because then SkyLog can send the quantities in the correct unit of issue rather than eaches.
 
3. We need to go back to those suppliers that are shipping to the same warehosu ein different pack sizes and enforce a consisitency
 

Latest revision as of 12:57, 11 February 2022

Please use our Tips and Tricks page for understanding how the SkySuite portal works and how to navigate faster and easier.


Stock Item Packs

Item Pack Levels - Introduction

Level 1 of an item pack structure is always the stocking unit and every item must have a Level 1 pack record. Typically this is an "Each/Piece" but it could be a box or carton. It is important to note that all stock quantities are reported in the stocking unit (Level 1) and these quantities cannot be decimals which means that if you set your stocking unit to a box then you will not be able to issue or receive in eaches.

The next level up we need to define all the possible pack sizes for the item, see example below which shows an item that can come in 4 different pack sizes 320, 500, 750 or 1,000. In this case the Stocking unit is EA (Eaches) so we will have 5 Packs (1 Level-1 and 4 Level-2) for the item. Because we have 4 different Level-2 alternatives we give each one a structure code (key). A to D in the example below

500PX

Let’s make this a bit more complicated and say we have Pallet Configurations also defined and there are;

20 BX/320’s on a Pallet
12 BX/500’s on a Pallet
10 BX/750’s on a Pallet
6 BX/1000’s on a Pallet

Then the Pallets would be created as Level-3 packs;

500PX

When the above table is created in SkyLog you must identify one of the above packs as a default for issue but this is only used if there is no default at the Station Level see below.

Issuing out

It is possible in SkyLog to define a default issue pack size for each station/Item and also you define which stations are supplied by which warehouses.

Example

If you have Coke that is supplied to the LIM warehouse in Boxes of 24 and supplied to the SAL warehouse in Boxes of 12 then you would set the default unit of issue for all the LIM supplied stations to 24 and for all the SAL supplied stations to 12. Although you would have also a default at Item level (see above) this will only be used if there is no default at the Station level. What then happens is any suggested quantity is rounded to the multiples of 24 for the LIM stations but to quantities of 12 for the SAL stations thus avoiding having the warehouse having to open boxes or manually round the quantities up or down.

Now let's consider an example where there is mixed pack sizes in one warehouse because say you changed supplier. In this case you would have to leave all or some stations to use the old pack size until the inventory was depleted then switch over the default once all the old stock was burned off. The only other alternative would be to repack the old inventory to the new pack size.

Purchasing

For each supplier of an item you can specify a different purchasing unit per warehouse so for example we could have

500PX

In the above example all PO’s for J.J. REPRESENTACIONES Y SERVICIOS S.R.L. would be rounded to 500 while all PO’s for AQL SOLUCIONES INTEGRALES S.A. would be rounded to 320 and PO’s for CEK DE GUATEMALA would be rounded to either 320, 750 or 1000 depending on what Warehouse they were for.

Note that it is not possible have a mixture of Purchasing units defined for the same supplier/warehouse combination.