Skip to main content
Skip table of contents

Troubleshooting - PO

  1. When problems are encountered with printer setup, verify the Escape Sequence common code (POPO/ESCAPES) is set up when the printer is initialized. Note that the line printer must also be defined; see NULP/XXX where XXX is the printer.
  2. When incapable of printing a PO Range using POPO, common code POPO/RANGE needs to be set up or verified. Note that printing forms may require additional codes. Escape sequences may impact the display of the second and additional POs. See common code POPO/ESCAPES with printer's escape sequences. Printer must also be defined using common code NULP/XXX where XXX is the printer.
  3. To verify that the default date on the PO format will be in the format of your choice, verify common code POPO/DATES.
  4. To instruct the system to print the value entered in the Catalog # field as the first line of the item description, add common code POPO/CATALOG.
  5. To print account and dollar amount summary information on a PO, common code POPT/PRINTXX (section "Print Account Summary Page with PO") may be entered.
  6. Requisition codes are user-defined codes that can be assigned to any PO as necessary. They are especially helpful when printing information into pre-printed fields. See the following example for FOB.
  7. To tag a Purchasing Vendor inactive, check the "No PRs" box under Vendor Security on the Vendor Tab of the Person/Entity Information (PEUPPE) page.
  8. If a Purchasing Vendor (PE ID) should never have a Purchase Order printed, check the "No POs" box under Vendor Security on the Vendor Tab of the Person/Entity (PEUPPE) page.
  9. If the user would like to encumber funds and perform budget checking at data entry time, common code POEN/PR must exist.
  10. PO format default will not change by altering only the PO General Information (POUPGN) page; you must also change the Job Dialogue (NUUPJBQS, Question No. PO0D) .
  11. If printing or selecting on information that contains a dash ( - ), put the selection in quotes (i.e., "XX-XX").
  12. To adjust an incorrect receipt amount in receiving (POUPRC), use a negative number (i.e., -90).
  13. When a PO is created through Purchasing and it was not fully dis-encumbered through Payment Processing and the remainder needs to be relieved, the dis-encumbrance MUST take place through the Purchasing utility POMADExx in the following order: 1) POMADECS - Create Select File, 2) POMADERS - Report of entries, 3) POMADEUS - Update POs from Select File.
  14. A proof of Purchase Requests prior to printing can be generated in the form of a Purchasing Worksheet.
  15. If the Purchase Order and Invoice to be paid in Accounts Payable differ due to GL Account Number or Vendor ID, it is highly recommended that the Purchase Order be changed in Purchasing and reprinted. If the Purchase Order and Invoice to be paid in Accounts Payable differ due to dollar amount differences, the adjustment(s) can be made in Accounts Payable. The changes will be made on the Invoice record, to the Qty #Product @Unit Price and Inv Amt field.
  16. If encumbered amounts in the general ledger appear incorrect, a Re-compute, GLUTDICP to include encumbered amounts should be run.
  17. The PO Number, not the Purchase Request Number, must make a reprint of a Purchase Order.

Common Messages from PORERP

If there is a problem in the PORERP report, run an EN and a PO report to look at the details. ENREDR is a good "debug" report if you want to see all of the EN details for a specific PO/PR.
Report comments include:

  • Cancelled PO/PR with encumbrances
  • Disencumbered PO/PR with encumbrances
  • Fully paid PO/PR with encumbrances — There is an open encumbrance, but the PO/PR is cancelled, disencumbered, or fully paid.
  • Closed in encumbrance — Closed in ENDB but open in PODB.
  • No encumbrance references found — No EN records for this PO/PR were found.
  • Mixed types in encumbrance — The ens-status-mstr does not match the EN details as far as whether the EN is open or closed (possibly need to run ENUTCP)
  • Encumbered amount > purchasing — The total amount for this PO/PR in poi-item-dtl is less than the total EN/DE amount in the en-dtl.
  • Purchasing amount > encumbered — The total amount for this PO/PR in poi-item-dtl is larger than the total EN/DE amount in the en-dtl.






















JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.