Apurva Tripathi – Page 29 – PeopleSoft Tutorial
Apurva Tripathi

Author Archives: Apurva Tripathi

Apurva is a PeopleSoft consultant and a big advocate of everything PeopleSoft. He is also a technology enthusiast and loves learning and implementing newer and open source technologies. He spends his spare time updating this blog and likes to read books on self help and productivity.

How the Integration Broker Handles Incoming Requests (Understanding PeopleSoft Integration Broker Part 2)

Let’s discuss how the integration broker handles incoming requests. It is assumed that you’ve already read the Part 1 of this series – Understanding PeopleSoft Integration Broker.  There is a series of events which happen when a PeopleSoft Integration Broker receives incoming requests. 1) When a request is received by a Listening Connector, the first […]

Continue reading
1

Understanding PeopleSoft Integration Broker – Introduction (Part 1)

PeopleSoft Integration Broker can be daunting for those who are new to Integration Broker and hence, this post has been written with the intend of helping those who want to learn PeopleSoft Integration Broker. Skills for understanding PeopleSoft Integration Broker are PeopleTools, PeopleCode and Application Engine are a must. Additional experience in XML, SOAP, HTTP, […]

Continue reading
3

How to Find PeopleSoft Processes/PSJobs in a Recurrence

Do you want to find out all processes and jobs running under a particular recurrence? Use this SQL below: SELECT process_job_name,  description, recurname FROM   ps_prcsrecur a, (SELECT p.prcsname  AS Process_Job_name, p.descr     AS Description, p.recurname AS recurname FROM   ps_prcsdefn p UNION SELECT jp.prcsjobame AS Process_Job_name, (SELECT j.descr FROM   ps_prcsdefn j WHERE  j.prcsname = jp.prcsname) AS Description, jp.recurname AS recurname FROM   ps_prcsjobdefn j,  ps_prcsjobitem jp WHERE  j.prcsjobname = jp.prcsjobname) b WHERE b.recurname = a.recurname AND a.recurname = :1 ORDER  BY 1

Continue reading

Query result set too large, (124,87). Result of (SQL Fetch) is over the maximum result size specified for the application server.

One of the common errors encountered while running a PSQuery is: “Query result set too large, (124,87). Result of (SQL Fetch) is over the maximum result size specified for the application server.“ As the error message suggests, this error has been caused due to huge result size, which the application server is unable to render […]

Continue reading
>