ArticlesPS Cloud Process Troubleshooting Guide

When there is a problem, identified through this process or in the next section, then the next section details what to look for and a guide as to how to fix.

All versions

Transaction Deltas and Error Handling

Review App Logs based on below [A count or list view of these could be added to an Admin Workspace]. If Apex class - ActualsCalculateDeltaBatch [ACDB] encounters an error that it can “catch” (typically anything other than a Salesforce platform governor limit error), it creates an App Log record related to Actuals (Origin field on App Log) with a Level value of 6.  In this case, that particular batch (default 200 records) fails and those Transaction Deltas go un-processed but other batches continue. 

ACDB also creates an App Log record related to Actuals with Level 5 when it first starts, and deletes it when done.  This is a control record and if ACDB hits an uncatchable error such as a Salesforce platform governor limit error, then the entire process usually ends, with the only tell-tale sign of the error being the remaining Level 5 App Log that ACDB did not have time to delete before exiting un-gracefully. In itself, the failing of one of these jobs is not in itself an issue - as the TDs should be processed in the next job. If the job repeatedly fails though, then investigation is needed. 

Actuals and Time Periods

PSA creates separate Actuals records for different Time Periods. So for example, if a Timecard contributes amounts and hours to Project Actuals, it may do so for Actuals records corresponding to a week, a month, a quarter, a year, and to the catch-all Perpetual Time Period.  In fact, if the Timecard spans a month or quarter boundary (or the boundary of any Time Period configured for Actuals roll-up), it may contribute to 2 Project Actuals records for each of those Time Period types, each corresponding to the part of the Timecard that overlaps with the dates of the Time Period.

PSA uses the Transaction date field to determine which Time Period each piece of data belongs to. Other than SF reporting, the other view for these Actuals for time periods is on the Regions, Practices, Groups, Projects and Resource records. The Apex job, RPGPR Maintenance batch, should be scheduled to update “Current Time Period” on PSA Regions, Practices, Groups, Projects and Resources. This determines which slice of the Actuals are shown on the record page. For example, the recommended Time Period for a Project is ‘All TIme Periods’ [Perpetual] so the entire Project numbers can be viewed/are visible on the project. This can be manually forced by checking the ‘update current time period’’ checkbox on the record, which updates only for the chosen record.

What time period is set as the current time period on these objects is defined in the Config Group - ‘Actuals Types’ i.e The Project is defined as below.

In scenarios where the Time Period is set to monthly, typically for example on a Resource where you are interested in the values for the current month, then this needs to be set up so the time periods are updated as the month changes. [Note: This can be done manually via the ‘update current time period’ checkbox and saving. ]

This can be automated via the PSA Admin Tab > RPGPR Maintenance Batch as below.

AppLogDeleteBatch

Scheduled job to delete PSA Core App Logs (which record in progress or error conditions for PSA processes such as Billing, Actuals and Estimates vs Actuals). Recommend using App Log Cleanup Job section of PSA Admin tab/page to run or schedule this.

Apex Errors

When PSA/SF hits an error, an Apex error message may be created. These are sent to a shared/central inbox at Certinia, and also to specified customer email addresses [needs configuring] 

How to change/view who receives Apex exception mails?

• Lightning Experience: Gear Icon > Setup > Quick find > Apex Exception Email
• Salesforce Classic: Setup > Quick find > Apex Exception Email

These should be reviewed regularly and any corrections that are required should be made. Some common Apex errors are seen below: