Request Processing the automatic creation, based on a request, of active documents according to set rules, which will change the stock of goods as a result of business activities (sale, production, procurement).

Manually created requests and those imported from r_keeper are processed identically.

For correct processing of sales (i.e., requests), we recommend performing actions in the following sequence:

  1. Estimated Consumption for a request or a group of requests.
  2. Correcting errors.

  3. Making changes to the document flow or dictionaries to prevent the formation of "compensated entries," if required by the organization's business model.

  4. Generating child requests or a tree of child requests, if required by the organization's business model.

  5. Creating delivery notes for child requests, if required by the organization's business model.

  6. Creating delivery notes for sales requests.
  7. Steps 5 and 6 can be replaced by a single function – Create Delivery Notes for the Request Tree, if the organization's business model allows for this method of request processing.