Production Booking using QAD EE

Challenges

Production Backflush was not creating transactions in a sequential manner when executed by more than one user simultaneously. Inventory transactions created before the session got frozen were not getting rolled back even after killing the session, thus it created inventory mismatch between physical vs QAD.

• Program should have the capability to get executed by more than one user at a-time
• Program should be executed either in batch mode or in manual mode without user session getting frozen
• If the session got killed abruptly, program should have capable to reprocess remaining backflush transaction by itself automatically

Application Modules:

• Users abruptly closed Backflush transaction which caused the Backflush missing transactions
• Developed a new control to identify user who tried to terminate the session and email the details to local IT team
• Automate batch job to re-process the partial transactions created due to session closed abruptly

Our Solution

• Implemented a process to control that to allow the backflush transaction one at a time, other backflush transaction request will be kept in queue to process until the previous request get completed
• Automated a process that the program would identify missing backflush transaction on its own and re-process the same
• Used QXTEND technology to automate backflush transaction process to run in batch mode

Technological Inputs:

• .Net – Frontend
• Progress 4gl – Backend
• Qxtend – Used for Interface
• Integrated Customization Toolkit (ICT) – Used to trigger emails

Key Benefits

• Multiple user can run the backflush transaction program concurrently
• Automatically identify the backflush transaction which were abruptly closed and re-process the same
• Manual interaction has been reduced by running backflush transaction program in batch mode

Significant Achievements:

• Transactions are running in sequential and easy to reconcile the inventory.
• Missing transactions are automatically reprocessed through batch.
• There is no screen freeze issue when multiple users login.
• Program is also running in batch mode and less manual intervention.