FREQUENTLY ASKED QUESTIONS

For questions about system requirements, deployment options and installation, please visit our Installation Guide.

Distribution

---

My invoice run for an order does not print. I get a blank screen. The order has been shipped confirmed and if I query the order up in order entry it is at the proper shipped confirmed status?

If the order is at a shipped confirm status, the most likely cause is that the invoice date entered on the invoice run (oe2500) is outside of the period that the order was shipped confirmed in. The date entered at invoice print must be in the same period and must be equal to or greater then the shipping date.

When I go to re-print an invoice it comes up with a blank screen?

The invoice date entered on the invoice run (oe2500) must be the same as the original invoice date.

Manufacturing

---

The Planned Orders Due for release (rp1700) includes all orders both firm and suggested from the MPS (pp2100). I thought it would only create work orders from the suggestions I firmed up?

Firming a suggestion in the MPS (pp2100) simply flags this line item and qty to NOT be deleted the next time the MRP explosion (rp0100) is run. The qty is firm and is considered in the next explosion as being completed on the line item's dates.

The planned orders due for release (rp1700) will analyze and create Work Orders for ALL suggestions AND Firmed suggestions based upon the current state of the MPS (pp2100).

When deleting suggested work orders prior to running rp1700 make sure you have committed/saved in the MPS.

Note also that rp1700 can be run WITHOUT creating work orders. Make sure the ‘Create Work Orders’ flag is unchecked. The report can the be used to verify what work orders will be created. It can then be run again with ‘Create Work Orders’ checked to actually create the work orders.

Note also that if sub-jobs are present then deleting the suggested top job in the MPS (pp2100) WILL NOT delete the underlying suggested sub-jobs for the items components.

I confirmed a portion of a job using Automatic Job Confirmation - pc5200. By accident I also finalized the job. At a later time I needed to confirm more quantity for the job so I used the Manual Job Confirmation - pc5100 to undo the finalizaition (final flag) of the transaction. Using Automatic Job Confirmation - pc5200, I then confirmed more quantiy of the item for the job. Upon completion, the system confirmed the quantity of the finished good but there was no inventory reduction for the raw materials used for the item?

Care should be taken in “Finalizing” a job using Automatic Job Confirmation - pc5200. All sub-component material usages created will be finalized automatically. Automatic Job Confirmation - pc5200 will not process lower level components of a work order if the status of these components is ‘done’ (final)

In the event that the final flag was set incorrectly using this application the procedure to follow is: To use Manual Job Confirmation - pc5100 to first reverse the final flag of the top job and then using Material Usage Correction - pc3600, reverse all the issues that were done with final flag set by deleting all transaction records. The material issues would then be re-done using Manual Material Usage - pc3100 but this time the final transaction flag would not be set. Alternatively, Manual Job Confirmation - pc5100 could be used to DELETE the confirmation of the top job, then after using Material Usage Correction - pc3600 to reverse/remove the material usage transactions, the Automatic Job Confirmation - pc5200 used again to confirm the total units for the job.

If this procedure is not followed and only the final flag is re-set using Manual Job Confirmation - pc5100 and then a further confirmation of product is done using Automatic Job Confirmation - pc5200, the underlying components of the job will NOT have their respective inventories relieved.