Warehouse

   

 

 Warehouses, or outlets, or both, generally speaking, there may be several. At any warehoused goods may enter in the books, any spend from one warehouse to another pass. All the movement of goods reflects the user in the overhead, receipt, account for the transfer. Form of consignment in the program as close to the standard form, so the issue will not cause who knows how to fill out the form on the invoice, the invoice and will be able to enter into the system. The special features include the following:

 

1.Base stock, its core - a roster of products. What is meant by the register of goods (storage registry)? This table, which stores the data of this type:
What goods store
In what quantity
For some purchase price
At what retail price

 

2.System implements two different storage models. Work on one of them is selected by setting the switch in the parameters of the system. The first storage model that is called a classic. Each item is a separate line registry. If there were several shipments of goods to different purchasers' prices, then these purchases in the register of goods are allocated in separate lines. If the purchase price in different shipments of this product are identical, the new registry entry is not created simply by increasing the number of existing registry entries to this product with the same purchase price. The second warehouse model realizes the algorithm works on weighted average prices (sometimes the term "On average prices). How does it work? For each product its own registry entry is created, as in the previous model. But unlike the classical algorithm, all the new supply of the goods fall into the same registry entry, quantity is summed, and the purchase price converted at the weighted average algorithm. Do not want to write the formula, it is boring. I think that would be understandable if explained as follows. Suppose, bought 04/28/2008 100 kg of bananas to 3.10 p. per 1 kg. 30/04/2008 bought another 80 kg, but at 3.20 p. per 1 kg. Thus, in the registry entry from the first purchase is added to another 80 kg, the remainder of bananas in stock will be 100 80=180 kg, the question is how to calculate the purchase price for the registry entries. The solution is quite simple. It is necessary to calculate the total sum of the two purchases, and divide it by the number of pounds purchased. Thus we obtain the average purchase price (100 * 3.10 +80 * 3.20)/(100 +80)=3.144444444 p. per 1 kg. This price is long Do not be fooled, the machine thinks these things are easy and simple. When is preferable to use a weighted average model? For very large range and large volume of transactions. Better suited for food, especially of loose. To work with technology, electronics, consumer, with expensive items, where the slope is made on piece-operation, better use of the classical model.

 

3.Another feature is the ability to enter the retail price directly with posting of the goods. The storage software pricing mechanism has traditionally paid little attention. There is a common situation when the retail price specified in the sale, at best, it may be marked in the directory. Changes in retail prices could not fixed, does not affect the warehouse, to assess the earnings and profit margins, it can be modified only by already sold. Any user can change the retail price of the handbook, with no document to this change of system will not be formed. Track changes in the retail price in full is impossible, only possible to assess these changes in the goods sold, but such information will not be complete. To avoid such problems when designing the system was taken a few solutions. First, keep track of the retail price for each product for all warehouse operations. Second - all the changes the retail price fixing in the acts of the revaluation. And the third - to automate the work with the retail prices. What is meant by maximum automation? Since the retail price is already laid for posting of the goods (that can later be changed in the act of revaluation), then we can automatically calculate the price with respect to the purchase price using the value of trade margins of the system parameters, the user can immediately change as the trade mark, and automatically calculated value of the retail price. With the consumption of commodity retail price is substituted into the invoice automatically, the user can change it. When shipped this bill will be automatically created the act of revaluation, which will reflect the change of retail prices. In addition, the user can change the retail price directly to the entire registry entries on this product, creating a new act of revaluation. Thus two problems are solved. First, achieved complete freedom when dealing with retail prices (there are no restrictions, no need to specifically perform some action), and secondly, the changes of retail prices will be fixed. Now it is possible to form a turnover balance sheet and similar reports, indicating the speed, not only in purchasing but also in retail prices.

 

4.Principle of reversibility. All user actions are reversible. The special features of the input document should also include the principle of (approved) - deferred instrument. When you enter a new document (Invoice, the act of revaluation, etc.), it automatically gets the status of the pending document. Until the document is approved, you can change it, you can remove it. No power such document has not. For what would have been changes in the warehouse according to the document, it needs to be undertaken (to approve). For example, if you type Invoice in its list of specified goods to its debit, what would those goods in a warehouse pending. It's like a stamp and signature. When you click on "hold", the goods of the consignment is transferred to the register of goods. Once a bill has been completed, change it anymore. In order to make changes to the bill, you need to roll back, after this bill gets the status of pending, you can make changes.

 

5.Temporary transparency. Any change in the state warehouse, any movement of goods in a warehouse registered in the log of operations indicating the date of the transaction. Thus fixed, not only the current state of the warehouse are recorded as the changes over time. With such data it is easy to get the state of the warehouse at any one time. Statement of balances can be obtained at any date, a report on the implementation can be obtained for any period. This is true for all other reports. Thanks to the proper organization of data in a database of its kind carried out very quickly.

 

6.Much attention is paid to usability. When designing a system task was as easy as possible user experience, as easy as possible development of a system as close to the natural actions of the user. All that the user needs to work, shall be kept on hand, must be clear and easy to use. Much attention has been paid to the so-called hidden automation when the system takes a number of absolutely necessary action without user intervention. For example, when changing the retail price when the goods are shipped automatically creates an act of revaluation, while shipments are automatically rolled back, rolled back the act of revaluation. The user does not necessarily create and carry out an act of revaluation manually. The system will automatically perform these steps if necessary.