Com a release 2021R1 foi criado um ponto de entrada que permite bloquear uma saída de stock com data anterior. Como sabem, este tipo de movimentos podem levar a discrepâncias na valorização de stock e este ponto de entrada permite bloquear a realização deste tipo de movimentos.
Detalhe do que pode ser encontrado no help-online sobre o ponto de entrada:
CONTROL_BACKDATE: authorize backdated stock issues
This entry point is used to check if a backdated stock issue is authorized. The control is applied to the existing stock on a relevant date. This is a blocking control.
This control has been implemented to meet several requirements:
- Keep a chronological order: It is not possible to issue a product on a given date if this product was not in the stock on that date.
- Maintain consistency in stock movements regarding lot entry and issue
- Avoid beginning the stock movements of new products with a negative stock value
- Stock on the receipt date/effective date (earlier than the current date) must exist for the product-site, lot and sublot, requested quantity and serial number (which determines the stock line). All the other characteristics, such as location, status, packing unit, conversion factor, user 1 and 2 areas as well as the LPN number, that are available on the stock line, are considered to determine the available stock. If there is no available stock, a blocking control prevents you from creating the document.
- In the stock journal, a control is applied to the stock movements already performed between the current date and the entered date (earlier than the current date) to prevent stock to be issued for this product on a date earlier than the last sock issue for that same product (same site, lot, sublot, serial number).
Prerequisites
- Concerning Product management (GESITM), negative stock is prohibited (the Stock < 0 authorized check box is cleared).
- No negative stock is managed for the product.
Activation
In this entry point, enter the following instruction:
Call BACKDATE From STKMAJCTL
Limitations
Stock movements corresponding to a Lot modification document (VCRTYP = 35) are considered. Effectively, the corresponding issue flow is identified as a Miscellaneous issue (TRSTYP=2). This is normal behavior for lot renumbering/mixing but it serves no purpose for characteristic changes (except potency) and lot user custom fields. This has no consequences on the calculation of the stock on the effective date. On the other hand, it will block the update if a movement relating to characteristic changes or lot user custom fields is later than the effective date entered.