# PeopleSoft Process Scheduler RUNSTATUS Values and Report Manager Tables > Source: https://netray.co/tools/peoplesoft-process-scheduler-runstatus-tables-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Decode PSPRCSRQST run statuses, read distribution statuses, and find the Process Scheduler and Report Manager tables to query when a report will not post. ## Category oracle ## Erp Oracle PeopleSoft ## Audience - PeopleSoft administrator - PeopleSoft developer - Batch operations ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Row type **Key:** kind **Type:** text #### Value / table **Key:** value **Type:** text #### Name **Key:** name **Type:** text #### Meaning / contents **Key:** meaning **Type:** text #### Troubleshooting tip **Key:** tip **Type:** text **Rows:** #### Cancel **Kind:** RUNSTATUS **Value:** 1 **Meaning:** Cancel requested for the process **Tip:** Should move to Cancelled; if stuck, check the scheduler server is running #### Delete **Kind:** RUNSTATUS **Value:** 2 **Meaning:** Delete requested for the request **Tip:** Removed by the scheduler on its next cycle #### Error **Kind:** RUNSTATUS **Value:** 3 **Meaning:** Process ended with an error **Tip:** Open Message Log and trace or log files in Process Monitor details #### Hold **Kind:** RUNSTATUS **Value:** 4 **Meaning:** Request held by a user **Tip:** Restart from Process Monitor to release it #### Queued **Kind:** RUNSTATUS **Value:** 5 **Meaning:** Waiting for a Process Scheduler server **Tip:** Long queues: check server status, max concurrent per process type and server definition #### Initiated **Kind:** RUNSTATUS **Value:** 6 **Meaning:** Server has started the process **Tip:** Stuck in Initiated often means the program failed to start; check the server log #### Processing **Kind:** RUNSTATUS **Value:** 7 **Meaning:** Process is running **Tip:** Long running: check database sessions for the process instance #### Cancelled **Kind:** RUNSTATUS **Value:** 8 **Meaning:** Process was cancelled **Tip:** Rerun from the run control page if needed #### Success **Kind:** RUNSTATUS **Value:** 9 **Meaning:** Process completed successfully **Tip:** Distribution status shows whether output reached Report Manager #### Not Successful **Kind:** RUNSTATUS **Value:** 10 **Meaning:** Process ended without success **Tip:** Check message log; often an Application Engine or SQR return code #### Posted **Kind:** RUNSTATUS **Value:** 11 **Meaning:** Output posted to Report Manager **Tip:** Viewable in Report Manager by authorised users #### Unable to post **Kind:** RUNSTATUS **Value:** 12 **Meaning:** Output could not be transferred to the report repository **Tip:** Check report node URL, credentials and the distribution agent log #### Resend **Kind:** RUNSTATUS **Value:** 13 **Meaning:** Repost of output requested **Tip:** Used after fixing the report node #### Posting **Kind:** RUNSTATUS **Value:** 14 **Meaning:** Output transfer in progress **Tip:** Stuck in Posting: check PSDSTSRV is running on the scheduler domain #### Content Generated **Kind:** RUNSTATUS **Value:** 15 **Meaning:** Output files generated, awaiting posting **Tip:** Distribution agent should pick it up #### Pending **Kind:** RUNSTATUS **Value:** 16 **Meaning:** Waiting on a prior item, for example in a job **Tip:** Check the job or the dependency #### Success With Warning **Kind:** RUNSTATUS **Value:** 17 **Meaning:** Completed with warnings **Tip:** Review the message log before treating as clean #### Blocked **Kind:** RUNSTATUS **Value:** 18 **Meaning:** Blocked by a mutually exclusive process or limit **Tip:** Check process definition mutually exclusive settings and concurrency limits #### Restart **Kind:** RUNSTATUS **Value:** 19 **Meaning:** Restart requested for the process **Tip:** Application Engine restarts from the last committed checkpoint #### Not Posted **Kind:** DISTSTATUS **Value:** See PSXLATITEM **Meaning:** Output not delivered to the report repository **Tip:** Check report node and PSDSTSRV log; repost once fixed #### Posted **Kind:** DISTSTATUS **Value:** See PSXLATITEM **Meaning:** Output in the report repository **Tip:** If users cannot open it, check report folder and distribution list #### Generated **Kind:** DISTSTATUS **Value:** See PSXLATITEM **Meaning:** Output created on the server **Tip:** Posting has not completed yet #### N/A **Kind:** DISTSTATUS **Value:** See PSXLATITEM **Meaning:** Process produces no output to distribute **Tip:** Normal for many Application Engine programs #### Process request **Kind:** Table **Value:** PSPRCSRQST **Meaning:** One row per request: PRCSINSTANCE, JOBINSTANCE, PRCSTYPE, PRCSNAME, OPRID, RUNCNTLID, RUNDTTM, RUNSTATUS, DISTSTATUS, SERVERNAMERQST, SERVERNAMERUN, BEGINDTTM, ENDDTTM **Tip:** Main table behind Process Monitor; query it for status and duration #### Process queue **Kind:** Table **Value:** PSPRCSQUE **Meaning:** Queue entries used by Process Scheduler servers, keyed by PRCSINSTANCE **Tip:** Should stay in step with PSPRCSRQST; mismatches show as stuck requests #### Process parameters **Kind:** Table **Value:** PSPRCSPARMS **Meaning:** Command line, working directory and output parameters per PRCSINSTANCE **Tip:** Shows the exact command a process was given #### Process Monitor list view **Kind:** Table **Value:** PS_PMN_PRCSLIST **Meaning:** View used by the Process Monitor process list **Tip:** Same data as the Process Monitor grid #### Report Manager content list **Kind:** Table **Value:** PS_CDM_LIST **Meaning:** One row per output content: PRCSINSTANCE, CONTENTID, DISTSTATUS and report details **Tip:** Join to PSPRCSRQST on PRCSINSTANCE to find unposted output #### Report files **Kind:** Table **Value:** PS_CDM_FILE_LIST **Meaning:** Individual files (report, log, trace) for each content ID **Tip:** Lists the files the distribution agent tried to transfer #### Report distribution list **Kind:** Table **Value:** PS_CDM_AUTH **Meaning:** Users and roles authorised to view each report **Tip:** Users missing from this cannot see the report in Report Manager #### Report node **Kind:** Table **Value:** PS_CDM_DIST_NODE **Meaning:** Report node definitions: URL, transfer protocol and connection details **Tip:** Wrong URL or credentials here is the most common cause of unable to post #### Process definition **Kind:** Table **Value:** PS_PRCSDEFN **Meaning:** Process type, name, server and output settings, recurrence, mutual exclusion **Tip:** Check here when a process runs on the wrong server or never starts #### Process definition components **Kind:** Table **Value:** PS_PRCSDEFNPNL **Meaning:** Components (run control pages) from which a process can be run **Tip:** If a process is missing from a run control, check this table #### Job definition **Kind:** Table **Value:** PS_PRCSJOBDEFN **Meaning:** Job header for multi-process jobs **Tip:** Use with PS_PRCSJOBITEM to see job steps #### Job items **Kind:** Table **Value:** PS_PRCSJOBITEM **Meaning:** Processes inside a job and their order **Tip:** Pending items usually wait on an earlier job item #### Recurrence definition **Kind:** Table **Value:** PS_PRCSRECUR **Meaning:** Recurrence schedules used by process and job requests **Tip:** Check when a recurring process stops scheduling #### Server definition **Kind:** Table **Value:** PS_SERVERDEFN **Meaning:** Process Scheduler server settings: sleep time, heartbeat, max API aware, operating system, distribution node **Tip:** Check the distribution node assigned to the server #### Run control **Kind:** Table **Value:** PS_PRCSRUNCNTL **Meaning:** Run control IDs by OPRID and RUNCNTLID **Tip:** Process-specific parameters live in the application's own run control records **Notes:** RUNSTATUS values are stored as characters in PSPRCSRQST.RUNSTATUS. Confirm all values on your database with: SELECT FIELDNAME, FIELDVALUE, XLATLONGNAME FROM PSXLATITEM WHERE FIELDNAME IN ('RUNSTATUS', 'DISTSTATUS') ORDER BY FIELDNAME, FIELDVALUE. Distribution status codes are shown by name only; read their numeric values from that query. PSDSTSRV is the distribution agent server process in the Process Scheduler domain. ## Content **Intro:** This reference decodes PeopleSoft Process Scheduler run statuses and distribution statuses and lists the Process Monitor and Report Manager tables to query when processes stall or reports will not post. It applies to PeopleTools 8.5x and 8.6x. **Sections:** #### How to use it **Body:** Filter by row type. RUNSTATUS rows decode PSPRCSRQST.RUNSTATUS, the value behind the Process Monitor status column. DISTSTATUS rows explain distribution status, which tracks whether output reached the report repository. Table rows tell you where to look next. A useful habit is to keep two saved queries: one listing requests in Error, Not Successful or stuck in Initiated or Processing for more than an hour, and one listing successful requests whose output did not post. Export the table to keep beside those queries. **Bullets:** - Run status tells you how the process ended - Distribution status tells you if the output arrived - Always check both when users say a report is missing #### How Report Manager posting works **Body:** When a process finishes, the Process Scheduler writes output and log files to its output directory and the distribution agent (PSDSTSRV) transfers them to the report repository through the report node defined for the server, using HTTP or HTTPS to the web server's report repository servlet, or FTP or XCOPY in older set-ups. PS_CDM_LIST and PS_CDM_FILE_LIST track the content and files, and PS_CDM_AUTH holds who can view them. Report Manager shows posted content; Process Monitor shows the request and its statuses. #### Worked example: reports not posting **Body:** Users report that SQR output stopped appearing in Report Manager after a web server change. Process Monitor shows Success with distribution status Not Posted. A query joining PSPRCSRQST to PS_CDM_LIST on PRCSINSTANCE confirms 140 unposted contents since the change. The distribution agent log shows HTTP 404 from the report repository URL. The report node in PS_CDM_DIST_NODE still pointed to the old host name. After updating the report node through the Report Node Definition page and restarting the scheduler domain, outputs were reposted from Process Monitor. #### Gotchas **Body:** Do not update PSPRCSRQST status directly in production except as a documented last resort; use Process Monitor actions so PSPRCSQUE stays consistent. A process stuck in Queued usually means no server is running for that process type or concurrency limits are reached, not a broken program. Blocked is often mutual exclusion configured in the process definition. Purging old requests with the delivered purge process keeps these tables and the report repository from growing without limit. **Bullets:** - Check server status before blaming the program - Use the delivered purge for old requests and reports - Report node changes need a scheduler restart to take effect **Cta:** If you want your operations team to ask which jobs failed overnight and why in plain English, answered from your PeopleSoft database on your own servers, we can set that up. **Faq:** #### Which tables are behind the PeopleSoft Process Monitor? **Answer:** PSPRCSRQST holds one row per process request with status, user, run control, server and timings. PSPRCSQUE is the queue the servers use, PSPRCSPARMS holds command parameters, and PS_PMN_PRCSLIST is the view behind the process list. Report output is tracked in PS_CDM_LIST and PS_CDM_FILE_LIST. #### Why are PeopleSoft reports not posting? **Answer:** Most often the report node is wrong: an outdated URL, credentials or protocol in the report node definition. Other causes are PSDSTSRV not running, the web server report repository path not writable, or files too large for the transfer. Check distribution status, then the distribution agent log in the scheduler domain. #### What is a report node in PeopleSoft? **Answer:** A report node defines how the distribution agent transfers output from the Process Scheduler server to the report repository: the URL of the report repository servlet, the transfer protocol and login details. Each Process Scheduler server definition names its distribution node. Its data is stored in PS_CDM_DIST_NODE. #### What does RUNSTATUS 9 mean in PSPRCSRQST? **Answer:** RUNSTATUS 9 is Success: the process completed. It does not mean the output was delivered, which is tracked separately in distribution status. Other common values are 3 Error, 5 Queued, 7 Processing, 10 Not Successful and 17 Success With Warning. Confirm values in PSXLATITEM for your release. ## Search terms peoplesoft process monitor tables, peoplesoft report manager tables, peoplesoft reports not posting, peoplesoft report repository, peoplesoft report node, psprcsrqst runstatus values, peoplesoft process scheduler tables, peoplesoft diststatus --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json