In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Using Reason Codes
    Reason codes are used in security functions, sales quotes, sales order maintenance, purchase order returns, shop floor reporting, repetitive reporting, and the Product Change Control (PCC) module. They are also used if you have enabled change tracking and in several optional modules, such as WIP Lot Trace, Electronic Signatures, and Shipment Performance. Add other custom uses as needed.

    Reason Codes Maintenance (36.2.17)
    Use codes of type User_Act for the Active Reason field in User Maintenance (36.3.1) and the Auto-Deactivation Reason field in Security Control (36.3.24).
    Use codes of type ESIG to indicate why a user is authorizing the data in an e-signature enabled program.
    Use codes of type QUOTE in the Reason Lost field of sales quotations.
    Use codes of type DOWN or DOWNTIME in the Reason field of labor feedback programs (17.1–17.4).
    Use codes of type ORD_CHG to associate changes made in Sales Order Maintenance to order detail, such as a change to the order line quantity or due date. See Tracking Changes.
    Use codes of type DOWN, DOWNTIME, REJECT, REWORK, ADJUST, and SCRAP for reporting in Repetitive and Advanced Repetitive programs. Use these same codes with the optional
    manufacturing WIP Lot Trace module.
    Codes used in the PCC module are user-defined. They specify severity levels related to approval of change documents.
    Use codes of type SHIPQTY and SHIPTIME with the PRO/PLUS Shipment Performance module. See User Guide: PRO/PLUS.
    Use codes of type RTV (return to vendor) to define reasons entered in Purchase Order Returns (5.13.7).
    Generate reports on downtime organized by reason code using the Downtime by Reason Report (17.17).