Hello All,
With our recent upgrade to the Multi-Tenant M3 Cloud system we've had quite the teething issues with the outputs from Infor Document management.
Some issues relating to trying to replicate the previous StreamServe scripting within xQuery, ION, etc but some that has been completely out of our control.
A process that has only come to light in the past few months has been with our Order Confirmation documents.
If you are not aware, after an order has been placed with the M3 system (OIS100) upon leaving the lines (OIS101) and progress to completing the order a batch job will automatically start the Order Confirmation printout. This will be emailed to the customer (If setup in CRS945) and also the user (if setup in MNS205).
A thing we are noticing with any orders that are entered in via the API OIS100MI the order confirmation will print out quite quickly in comparison to a manually entered order. It appears due to the timing of the order confirmation printing when the document is received by the customer the products that they have ordered are displayed not in stock. We are using a standard field from the OOLINE table within our document 'Remaining Quantity - OBRNQT'. At the time when the order confirmation has printed the remaining qty will match the exactly what the customer has ordered (Order Qty). We think this is because of the allocation job did not complete until after the confirmation has been printed.
When printing the order confirmation 1 second later the correct remaining qty will display.
At the moment we don't have a work around, it's only happening for our API entered orders; EDI and Order portal. Infor have stated this is standard functionality but it has only recently become and issue.
How is everyone handling their order confirmations?
Have we designed them incorrectly, the basis of ours is meant to display what can be supplied to the customer. Because we work in a fast stock moving environment.
Please let me know;
Thanks,
John
