/
Purchase Orders not Auto-Posting

Purchase Orders not Auto-Posting



Description of Issue

Purchase Orders are not Auto-Posting, stuck in released



Context
  • Munis 

  • Requisitions

  • Purchase Order Entry 



Cause

When users receive any warning or error when converting requisitions to Purchase Orders, Purchase Orders will not automatically post if selected to do so. The message in this instance was All report file names have been used on this system in the range: poentpst0001.txt to poentpst9999.txt . In order to prevent the error, the older reports need to be deleted to make room for new ones.



Resolution

Mass Deleted poentpst report file names 0001-9999 in Saved Reports

  1. Go to Saved Reports under Departmental Functions > Saved Reports

  2. Search for *poentpst* under Report File Name 

    1. be sure to include asterisks as a wild card indicator

  3. Select Mass Delete Reports

    1. Select All and Accept



Additional Information




Related content

How to post a PO batch - purchase order stuck in status 5 released
How to post a PO batch - purchase order stuck in status 5 released
More like this
PO Auto Posting is failing, error returned during manual post
PO Auto Posting is failing, error returned during manual post
More like this
Error was encountered updating work orders tied to posting POs
Error was encountered updating work orders tied to posting POs
More like this
poentpst Unable to Print You do not have access to the selected Tyler Forms job code
poentpst Unable to Print You do not have access to the selected Tyler Forms job code
More like this
Execute delete podetail 28 error when posting Purchase Order Change Orders
Execute delete podetail 28 error when posting Purchase Order Change Orders
More like this
Auto Posting Purchase Orders failing if buyer is set to require Commodity Codes on transactions
Auto Posting Purchase Orders failing if buyer is set to require Commodity Codes on transactions
More like this