Deleting master data
Note from Hypersoft: Due to relatively limited other POS systems such as cash registers, which can only record and store accounting data to a limited extent, legislators have required change records in the systems. The background to this is that such a system, for example, only stores the item bookings, but the prices (including VAT) are stored in the system. and other fiscal information) from the current master data record. This allows you to change the evaluation of posting data by changing the master data at a later date and to control it in a different way than when you settle sales.
Since Hypersoft stores all relevant data as it is created and even stores data such as original price in relation to a discount price, and also that a manager with his extended permissions for an operator canceled with each record stored, the additional records of changes from our point of view and the auditors with whom we discussed this is obsolete for Hypersoft. By transferring the master data to the transaction data, the information is completely derived from each saved posting data record. Changes are also saved in a traceable manner by means of offsetting entries.
In addition, we also offer an item change report so that you can also answer this demand positively. As a result, we do not offer all change logs for all master information, because as described above even every single booking record contains this information for ease of use (and therefore does not have to be compared with change logs).
You have the option of deleting item data or deactivating it for sales, for example. In the booking journal of the POS system, a copy of the item text and the essential information such as the original price at the time of the booking is saved with each booking. In addition, changes and deletions are saved in the item change report. If you still do not delete the items, you keep the master record additionally available. For example, you can work with groups and move items that are no longer required to a suitable group.
Warning against incorrect modification and deletion...
The item master of the controller is actively linked to the item data of the sales points and warehouses, and the items can also be interdependent. When deleting items with stock (if larger than 8 decimal places), a corresponding warning message is issued.
You can create an item change report because almost every change is logged in the item master.
Please note that any changes you make to master data at a later date may have unwanted effects on your site data. Example: You change settings in the units that have been assigned items that are already in ingredient lists of recipes. This can also change the recipes involved. The same applies to all evaluations and calculations based on it.
You should not delete items if they have been used for postings, as these postings could otherwise be missing from your evaluations or incomplete. You can rename the items and assign the item types differently. For example, for an item that is no longer to be sold, you can remove the Sold property.
You should only use the conversion of items if you do not change any relevant data. If you remove a base item from the point of sale, it continues to be posted correctly and is also displayed correctly in all evaluations. In other words, it retains this storage location. Only in the control record would this item no longer be displayed.
Product groups, price level, loss reasons, cancellation reasons
We recommend that you do not delete this variable (if it has been used). In the posting journal, the so-called ID of the variable is stored, but not the corresponding text. After deleting the affected variable, you can still see that you have posted to a loss, for example, but you cannot read the name of the reason for the loss. It is also possible to use a previously used ID with a new term after deleting the term. We therefore prevent these variables from being deleted. However, you can rename them: For example, you can rename the reason for the loss inventory difference as the former_inventory_difference.
Supports from the system...
When price levels and loss reasons are deleted, the system checks whether they have already been used (posted). If yes, the corresponding entry is not deleted and there is a corresponding message. Therefore, price levels and reasons for loss cannot be deleted in head offices (since a data check of all clients and locations cannot yet be carried out from there).
Further documentation:
Hypersoft procedure for zeroing
Deactivate or delete merchandise categories
Back to the parent page: Limitations and methods