Document 1176105.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.

E-RD: Upgrade to PT 8.50, PSJobs Tied To Recurrences Are Stuck in Posting Status. (Doc ID
1176105.1)

In this Document

Symptoms
Changes
Cause
Solution
References

APPLIES TO:

PeopleSoft Enterprise PT PeopleTools - Version 8.50 and later

Information in this document applies to any platform.

SYMPTOMS

PSJob tied to recurrences or scheduling jobs of processes on future dates are stuck in Posting status.

CHANGES

After upgrading to PT 8.50, PSJobs (usually tied to a recurrence) are sometimes stuck in the Posting Status.

This issue is caused by Bug:11626820 - Expiration Date for job item running with recurrence is being set incorrectly
causing report instance to be purged too soon.

Bug 11626820 is related to code changes for Bug 11446113 and 11464676.

From Bug 11626820 per development: Fixed in 8.51-02 and 8.50-13.

CAUSE

PT 8.50 introduces four new fields for Retention Days.

1) PeopleTools, Process Scheduler, Jobs (eg. 3SQR), Job Definition.

2) PeopleTools, Process Scheduler, Process, Process Definition. For example, XRFWIN.SQR.
3) PeopleTools, Process Scheduler, Process Types, Type Definition. For example, PSJobs for Windows and Oracle.
4) Run Control - Process Request Page, after selecting a process, click on the Distribution hyperlink

The default value for Retention Days is zero, except for the run control.

The problem is the Process Scheduler code is incorrectly calculating the Expiration Date.

When a PSJob tied to a recurrence or is manually scheduled to run on future dates, rows for the PSJob are inserted into
the PSPRCSQUE and PSPRCSRQST and PS_CDM_LIST tables.

According to development, the PT_RETENTIONDAYS in PSPRCSQUE and PSPRCSRQST are not being set consistently with
process jobitem (process which is part of a job). This probably contributes how the expiration date is initialized in
PS_CDM_LIST table.

1 of 3 9/4/2023, 12:51 PM
Document 1176105.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

The expiration date is determined by adding the retention days from the date on which the report was generated.

The process scheduler is sometimes calculating the expiration date = Run Date + 0 and the PRCSYSPURGE, which is
usually run daily at 1 am, will remove rows from the PS_CDM_LIST table if the value in the EXPIRATION_DATE is incorrect
(ie. set to the Run Date).

The process scheduler will process the PSJob, and the individual processes will run to success, but the Distribution Agent
will not post the results since the rows have been removed from the PS_CDM_LIST table by the daily purge.

There is no workaround or SQL that can be run at this point to correct PSJobs that have been removed from
the PS_CDM_LIST table.

NOTE: this behavior is NOT restricted to PSJobs using recurrences. This behavior can also occur with ANY process run
using a future date/time and the expiration date is incorrectly calculated causing the PRCSYSPURGE to remove the process
from the PS_CDM_LIST table.

SOLUTION

A resolution is available in PeopleTools 8.50.13 Update ID [845876] / Bug ID [11626820].

Please review Knowledge Document “How to Download PeopleSoft Bundles and Fixes from My Oracle Support” (Doc ID
1432368.1) for further details.

The workaround is to populate the Retention Days field as the process scheduler code intermittently does not
correctly calculate the EXPIRATION_DATE in the PS_CDM_LIST table.

PeopleTools, Process Scheduler, Jobs (eg. 3SQR), Job Definition. Override Process Retention Day: check and Retention
Days: 7 <= or whatever the value is for Retention Days for your company.

Note: Reference E-PRCS: Changes to Recurring JobSets, PSJOBs, Processes not taking effect. (Doc ID 660576.1) for the
steps to properly modify PSJobs since this is a cache-based feature.

PT 8.50 Process Scheduler PeopleBook for retention days:

Submitting and Scheduling Process Requests > Setting Report Distribution

Using Report Manager > Understanding the Purge Reports Process
Defining PeopleSoft Process Scheduler Support Information

Procedural Workaround:

1) Update tables PS_PRCSRUNCNTLDTL, PS_PRCSDEFN, and PS_PRCSTYPEDEFN where PT_RETENTIONDAYS=0 to the

same value presently in PS_PRCSSYSTEM.PT_RETENTIONDAYS.

Example: If PS_PRCSSYSTEM.PT_RETENTIONDAYS = 7, then update the 4 other tables to "7".

This will cause the EXPIRATION_DATE to be calculated correctly.
Example SQL: <leaves in place any non-zero values>

SQL> Update PS_PRCSRUNCNTLDTL set PT_RETENTIONDAYS = 7 where PT_RETENTIONDAYS = 0;

SQL> Update PS_PRCSDEFN set PT_RETENTIONDAYS = 7 where PT_RETENTIONDAYS = 0;
SQL> Update PS_PRCSTYPEDEFN set PT_RETENTIONDAYS = 7 where PT_RETENTIONDAYS = 0;
SQL> Update PS_PRCSJOBDEFN set PT_RETENTIONDAYS = 7 where PT_RETENTIONDAYS = 0;

2) Restart the process scheduler after making these changes and clear the cache.

3) Cancel and resubmit any processes using recurrences which are in QUEUED status.

2 of 3 9/4/2023, 12:51 PM
Document 1176105.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Note: The only known workaround for NESTED PSJOBS is to replace the sub-PSJobs with processes.

Still have Questions?

To discuss this information further with Oracle experts and industry peers,
we encourage you to review, join, or start a discussion in the
MyOracle Support PeopleTools PSFT Community

REFERENCES

BUG:11626820 - PSFT 2007578000-EXPIRATION DATE FOR JOB ITEM RUNNING WITH RECURRENCE IS BEING SE
BUG:11446113 - PSFT 1666530000-OLD RECORDS NOT PURGING FROM PS_CDM_LIST IF NO EXPIRATION DATE
BUG:11626819 - PSFT 2007578000-EXPIRATION DATE FOR JOB ITEM RUNNING WITH RECURRENCE IS BEING SE
Didn't find what you are looking for?

3 of 3 9/4/2023, 12:51 PM