...
If necessary, you can open any version of the set for viewing. To do this, position the cursor in the required line and use the Open set context menu item.
Info |
---|
Filling in the |
...
Set versions |
...
tab is available through group operations for the selected goods group |
...
. |
...
Special Feauters of Processing Set versions Parameter
In all Store House documents that work with kits (bids, kits, collation lists), the relationship between the product and the kit sets — requests, complectations, collation statements — the link between the goods and the set is stored in the document itself. Relationships are The link is defined when documents are created.
A bundle set and its version can be defined in the documents:automatically
- Automatically based on the created goods settings
...
...
- Manually by the user when creating a document, from the list of available
...
- sets in the
...
- goods card.
If an item the goods with a kit is set are directly involved used in production documents, then a link to the kit set is stored in these documents. That allows you to edit editing the product goods card on the "Kit Set versions" tab without restrictions.
Already created documents will work according to previously defined rules, new documents will work according to newly created rules.
If products the goods with kits sets are used as " semi-finished products", i.e. are not directly included in production documents, but work as components of other sets with the “Produce” Produce flag, then in production documents there is no reference to sets of such goods, which . It leads to the need to store the history of changes in the rules for the work of semi-finished products on in the goods cards of goods of these these semi-finished products.
For such goods, changing work kits sets or kit set versions on the "Kit Set versions" tab is available only in for the period for which documents have not yet been issued. If you try to make changes in the period for which documents have already been created, the system will display a an error message.
The system always allows you to add adding a new enterprise and a zero period of the basic set version to the product card of the goods for which documents were drawn upcreated, in order to be able make it possible to enter a new period to change for changing the working conditions of the productgoods.
Write-
...
Off
The "Write-off" tab is filled in for goods subject to write-off through the documents "Application" - consumption of dishes. Those. You Request documents — dishes expenditure. So you determine from which department the goods will be written off when they are sold.
Info |
---|
The parameters listed |
...
on this tab are optional. |
To determine the division of department for the goods write-off of goods, fill in the "Write-off" tab.
On this tab, there is are also the concept of "Default" and "Exceptions" By default and Exceptions concepts.
If the Store House StoreHouse program is used for one small enterprise, where write-offs occur for each product every goods from one divisiondepartment, without variations, then it is enough to fill in the “Write Write off by default” default value.
For example, an enterprise has two divisions (departments — Bar and Kitchen). If dishes are written off at the place of preparation (— salads from the kitchen, drinks from the bar ), — then for such enterprises, only the “Write Write off by default” default values are filled in on the product cards.
To assign a " default " write-off unitdepartment:Position
- Place the cursor in the
...
- Write off by default
...
- line
- Click on
...
- the button to
...
- open the Departments reference and select the required department
- You can also enter a part of the department name
...
- in the field, and a drop-down list will offer a choice of departments that meet the specified search conditions. Select the
...
- required department with the left mouse button or use the
...
- arrow buttons to move the cursor through the list and press the
...
- Enter
...
- key to select the
...
- department.
If the Store House StoreHouse program is being used for a chain of businesses enteprises or a business an enterprise with a large number of sale locations (— for example, two or more bars ), — then you must complete should fill in the Location Exceptions areaby sale locations fields.
The list of places of sale locations is specified in the directory "Places of sale" reference. This directory reference can be filled in manually or can be imported from R-Keeper.r_keeper.
Info |
---|
If |
...
StoreHouse is supposed to work in conjunction with |
...
r_keeper, then the places of sale must be unloaded from |
...
r_keeper and the connection between the place of sale |
...
imported from r_keeper and the department must be indicated on the |
...
Write-off tab for the sake of a correct write-off. |
In the " Exclusions by places of sale " locations field, list all bundles links of places of sale and divisions departments for organizing write-offs.
For example: one Coffee Americano menu item "Coffee Americano" can be sold in the bar on the 1st floor of restaurant 1 and in the bar on the 2nd floor of restaurant 1, as well as in the bar of restaurant 2.
To organize the correct write-off, it is necessary to specify all the conditions for writing off the goods from certain departments, depending on the these goods place of sale of this product.
To add a new department exclusion entry:
- Click in the table value area
...
- in the
...
- Exceptions by sale locations field
- Press the
...
- Insert
...
- or
...
- ↓
...
- key. You can also use the Add line context menu item or the Add line item of
...
- the Edit main menu item
...
- In the
...
- Sale location column, select a value from the Places of sale dictionary
...
- In the
...
- Departments column, select the warehouse from the
...
- Departments dictionary, from which the goods will be written off when they are sold
...
- at the specified place of sale
...
- If
...
- needed, repeat the above steps as many times as necessary
...
- Save the document
...
- by the Save document item of the main menu
...
- Document item or the
...
- button on the toolbar
...
- .
When filling in the “WriteWrite-off” off tab, the division department for write-off will be automatically displayed in applicationsrequests.
Info |
---|
Filling in the |
...
Write-off |
...
tab is available through group operations for the selected goods group |
...
. |
Routes
A route is a document flow automatically created on the basis of an applicationa request, leading to placing the posting of goods to a at the department for the possibility of further sale of goods.
Routes make It makes sense to use in routes at enterprises with production unitsdepartments, the implementation of which does not occur directlydo not serve as direct sale locations.
Routes are created for goods that are "ordered" at the production departments by the sales departments.
- The parameters listed in this tab are optional
...
- For goods whose sale fits into the
...
- Complectation + Delivery note scheme, filling in the
...
- Routes
...
- tab is NOT REQUIRED.
Example of creating a route:
There is a separate division "department — Confectionery Shop ", — which produces desserts for a chain of restaurants. Desserts are sold in establishments restaurants without additional preparation. Restaurants create requests for to the " Confectionery Shop " about the need to supply for certain desserts. "The Confectionery Shop " collects all applications requests and performs group processing of documents for the total production of desserts. NextThen, desserts are sent to restaurants.
To be able to process such a production process, it is necessary to organize “Routes” create Routes on the dessert product goods cards.
"Routes " can form three types of incoming receipt documents: incoming invoicesreceipt notes, internal transfers and pickingcomplectations.
"Default route" - routes — in this field, you must should specify the type of document that accounts for filing the product "goods by default " and the counterparty that supplies this productthese goods.
"Document type" - — select the document type of document for registering the receipt . Invoice invoice (mon), Internal movement (vp), Completion (k).
"Contractor" - — receipt note (r/n), internal transfer (i/t), complactation (s/c).
Counterparty — in this field, specify the supplier of the goods. This can be either an external supplier (for receipts) — for receipt notes — or in-house departments (— for picks complectations and internal transfers).
In the example ", the Cheesecake " is being prepared by "Pastry the Confectionary Shop". The document of preparation Complectation is the production document "complete set". Therefore, “k” and the counterparty “Confectionery shop” are selected in the “document type”s/c is selected as a document type and Confectionery Shop — as a counterparty.
Next, it is necessary to describe the method of transferring the prepared desserts to the points of sale locations.
“Exceptions by departments” – in this part of the window, you can fill in the differences according to the method of receipt of goods, depending on the departments.
If you want to separate two processes (production and movement), then you need to create exceptions in the routes.
Separation of processes may be required when the production unit collects all requests and organizes a common production document. And then, using different documents, he moves the prepared goods to specific divisions
...