To perform order-related postings, you must first create so-called "planned posting" (1). After entering all necessary posting data, the posting (3) must be executed. "Planned postings" have the following purpose:
- Division of tasks within a company (e.g. work preparation enters data, production personnel performs postings).
- Certainty in automated processes. Events in automated processes occur only once and never again (e.g. a dosage cannot be repeated again). If transaction errors or database problems occur in the background, you might lose information. To prevent this from happening, workflow nodes always first set up "planned posting" in the background before they are executed. Thus, these open transactions can be manually reposted in the event of an error.
Procedure for manual posting:
- Press the "New Posting" button (1).
- Selection of the newly created row in the posting list (2). Below this, a small form area is visible, which you must fill with the necessary posting data.
- Press the "Post line" button (3), to trigger the transaction*.
Effects of a withdrawal posting
A successful transaction causes the following:
- Stock reduction in the warehouse if a positive number has been entered as a posting quantity. A negative number is a stock increase. The stock fields of the following entities or tables are updated: Quantum, material, bin, lots, BOM, company (client).
- The statistical "Outward stock" fields of the corresponding entities/tables are updated.
- A new stock movement record is created, which is displayed in the posting history.
- One or more "stock movements of quantums" are created.
- The actual quantities fields of this material position and the parent material positions are updated.
- The planned posting is deleted.
Important note!
If you have a mistake in your posting or something else has gone wrong and you want to correct the posting again, always carry out the posting here and not in the warehouse management. Otherwise your statistics will not be correct! The rule applies: all activities that can be assigned to a business process (production, picking, goods receipt, goods issue...) should also be posted in the relevant business object!
* Transaction: A transaction in computer science is a sequence of program steps, which are considered a logical entity, because they leave the data in a consistent state after error-free and complete execution. Transactions provide an "all-or-nothing" proposition, stating that each work-unit performed in a database must either complete in its entirety or have no effect whatsoever.