Understanding Transaction Processing

Transaction processing ensures data integrity for specific programs and tables. If a transaction results in a database error or failure of a server while the system is committing inventory to the database, all table updates that are related to the transaction must be rolled back from the database to maintain data integrity. Transaction processing enables the system to store data in a queue until a commit command is issued, at which time the data is moved to the corresponding table.

The system creates boundaries for each process that is covered by transaction processing. The transaction boundary includes all data elements that constitute an outbound inventory transaction. When a failure occurs, the system generates a work flow message stating that the system resets to its original state before the failure occurred.

The Item Location File table (F41021) reflects on-hand and committed quantities of items by branch/plant, location, and lot/serial number. Maintaining the F41021 table accurately is extremely important. Transaction processing ensures that you do not commit items to an outbound inventory order before having a valid, processed order. If an item or order is held up for any reason, the system does not commit the order.

Transaction processing works with these programs during sales update:

• Sales Order Entry (P4210)

• Shipment Confirmation (P4205)

• Backorder Release (P42117)