Study Discussion Post: Design of Financial/Invoicing Software Database

shimaly

Now I am designing a small sales software database, and I have encountered some problems. I hope you can take care of it. Pay more attention to this post. I will organize it later to facilitate beginners to learn. Questions will be raised one by one, thank you!

Question 1:
    [Problem with statement design]
    Description: Settlement of the detailed data of the inbound and outbound slips. In the settlement process, the flush back documents are involved. For example, the flush back of the inbound slips. The reason is that there are two types of inbound slips: temporary storage and formal storage, and temporary storage. After the settlement of the document, it is flushed back according to the settlement quantity, and a formal receipt document is generated. Examples are as follows:
    Storage receipt (NO0001), variety (K01), quantity (100), unit price (5 yuan), method (temporary), date

    Outbound slips, multiple sheets, record the variety, quantity, etc. outbound. The operation is as follows:

    <1>At the time of settlement, if the quantity of K01 is 50, then generate a redemption order (NO0002), type (K01), quantity (-50), unit price (5 yuan), method (temporary), date

    <2>Generate an official receipt (NO0003), variety (K01), quantity (50), unit price (5 yuan), method (official), and date

    <3>Maintain the settlement table of customer commodity types: modify the number of merchants' types (not directly processed when leaving the warehouse, and will be processed until settlement)


    The general process of settlement is as above. Of course, it is a little more complicated, that is, the settlement quantity of one settlement statement has to be flushed back to multiple warehouse receipts (because it involves batch issues, it is more complicated and will not be discussed for the time being)

    Question: Do the above actions when generating a statement. If this statement is invalid, how to roll it back? How do regular designers deal with this kind of problem? Affairs? How to design?

lay1307

Your problem should not be difficult to solve, generally in ERP or MIS system you have encountered this situation! Under normal circumstances, solving such problems is mainly solved in the design of the table structure. For example, when you mentioned the "settlement statement voided", when the database is processed, a field "whether voided" is generally added for identification. In the settlement, the field can be included in the WHERE statement.
In addition, you should add a field for the batch of goods in or out of the warehouse in your table structure to facilitate judgment and use in settlement.

821105

Generally, there is a "red flush" method in finance, that is, invalid documents are not deleted but marked as a red flush. In calculation or statistics, the red flushed data is not operated.
You only need to add such a marked field (marked column) to the table.