When processing a request, the system creates delivery notes to change the quantitative balances of goods. The types of delivery notes created depend on many parameters.
Imported external requests
Imported external request — a document loaded from r_keeper. In its properties, it has the "Imported" flag and the request type "External".
For this type of request, the mandatory generated delivery note is the "Expenditure Delivery Note". Using this delivery note, goods from the request will be written off from the request's department.

The "Expenditure Delivery Note" can be replaced by an "Internal Sale" delivery note if the "Create Internal Sale for internal correspondents" flag was set during write-off and the correspondent-recipient of the request is matched with a department.

If routes are defined for goods from the request, then in addition to the "Expenditure Delivery Note", receipt delivery notes specified in the routes of the goods from the request will be generated. The types of documents created are determined in the routes depending on the department or sale location — these are "Assembly", "Internal Transfer" or "Receipt Note".
When creating "Receipt Notes", supplier price lists can be used to determine prices in the created documents. Or prices can be inserted based on the last receipt prices. Depends on: user rights to work with receipt prices, maintaining supplier price lists in the database, and whether the setting "Use Price Lists" is set.
If the "Routes" tab is not filled out for goods from the request, then the presence of the "Produce" flag in the goods cards will be analyzed. This property is checked by enterprises.

If the flag is set, i.e., the goods need preliminary preparation, then for the production of the goods, an "Assembly" ("Complectation") delivery note, responsible for the "production" of goods in r_k StoreHouse Pro, will be created before the formation of the "Expenditure Delivery Note".
If the flag is not set, i.e., the goods do not require preparation, then for such goods only an "Expenditure Delivery Note" will be created.
If the request contains services, then a "Receipt Payment Document" will be created for the total amount of all services in the request. The amounts will be distributed according to the VAT rates specified in the request for services.
One request can contain goods with different properties. In this case, all necessary types of delivery notes for the complete processing of the request for all goods in the request will be generated for the request.
External request created manually
The method of processing and creating delivery notes for external requests created manually is identical to working with imported external requests.
Return
Return — a request, most often imported from r_keeper, for processing returns/container buybacks.
When processing a return request, the following are generated:

  • "Receipt Note" for the department specified in the "Title" of the request.

Returned goods are posted at COST PRICE. By default, the cost for receipt is taken using FIFO (price of the last non-written-off receipt).
Nevertheless, the system allows setting other rules for calculating the cost for the receipt of returned goods (by weighted average cost or by LIFO).
To define the cost calculation method, make the setting CmpCostType = 0 (FIFO); 1 (Last Receipt); 2 (Average Price). in the SH.INI file.

This setting does not affect the method of cost formation during write-off. It only affects the calculation of the cost price in a set and the formation of the receipt price when processing returns.

If this item is not in the file, then add it.

[sh]
; How to calculate the cost price of a set (0-FIFO 1-Last 2-Remns)
CmpCostType = 0 (1 or 2)

  • «Расходный платежный документ» - документ формируется для фиксации отпускной суммы возврата/выкупа, т.к. в «Приходной накладной» указывается только себестоимость возврата/выкупа.

Internal Request
Internal Request — a request issued by a department for the supply or production of goods. The supplier can be either the department that created the request or another department (if creating subsidiary requests is not required).

For internal requests, "Delivery Notes" are NOT issued.

Internal requests are processed according to the routes defined for the goods in the request. The types of documents created are determined in the routes depending on the department or sale location – these can be "Assembly" ("Complectation"), "Internal Transfer," or "Receipt Note."
When creating "Receipt Notes," supplier price lists can be used to determine prices in the created documents. Alternatively, prices can be inserted based on the latest receipt prices. This depends on: user rights for working with receipt prices, the maintenance of supplier price lists in the database, and whether the "Use Price Lists" setting is enabled.
Also, an internal request can be processed without a route if the goods in the request have the "Produce" flag set and a defined set. When processing such a request, an "Assembly" ("Complectation") document will be created.
Child Request
Child Request – a document automatically created based on an external, internal, or another subsidiary request, for processing the production chain according to defined routes.
The types of documents created are determined solely by the routes depending on the department or sale location – these are "Assembly" ("Complectation"), "Internal Transfer," or "Receipt Note."
When creating "Receipt Notes," supplier price lists can be used to determine prices in the created documents. Alternatively, prices can be inserted based on the latest receipt prices. This depends on: user rights for working with receipt prices, the maintenance of supplier price lists in the database, and whether the "Use Price Lists" setting is enabled.