Entries that can be deleted
When the business case requires the possibility of deleting entries, we can make the auditability less strict. We still need code to create the entries, but if they are not used for accounting purposes, users have the option of deleting them again, or changing the contents.
An example of this can be found in Relationship Management, in the following diagram:
Temporary tracking buckets
In some cases, we need tables to track data during the existence of a Document or Process in the system. We can use Entry Pattern for this in combination with a set of Codeunits that ensure data integrity, and ensure having contracts to the application areas where the data is required.
An example of implementing entries can be found in the application area Reservation Entries. Each application area, such as Sales or Purchase has a Codeunit entry for the Reservation Engine. The Reservation Engine consists of three Codeunits. The following diagram explains the structure:
...
