Customer gets singleton select error in payroll build and error references Job Manager job

Customer gets singleton select error in payroll build and error references Job Manager job

If you look at the releases for the job steps referenced in the message, there are duplicate releases on the step.   


Using the job number in the Client Payroll Manager error message, get the job release ID number from Navision. It’s normally one of the most recent releases for the job.

Using DB Explorer, type in the following SQL query

     Select * from t$_job_release_step_detail where job_release_id = [release id]

If you look at the job _step_Id column, you should see duplicate job step IDs with different job step release IDs. One set needs to be deleted.

In Navision, look at the steps and see which job step release IDs are correct.

On the query, note which job step release IDs that need to be deleted.

In the T$job_step_release_ID table, delete the extra IDs. (You cannot delete from the query unless you change their settings to Live Query. )

If the steps in Navision do not have a job step release ID, pick one set of IDs to keep and delete the others. Then run the single job sync SQL and, when integration is finished, the cleanup SQL. (SQLs are out in U:BJIntegration Helpers. The single job sync SQL has six places where the job ID must be entered, so see BJ, Jan, or John H if you are unsure how to run it.)

Update: There is a new SQL statement available that will show all duplicates so you can take care of them at one time. The statement is

 Select    Job_id,    Job_step_id,    Job_release_id,    Count(*) as number_of_instances From t$job_release_step_Detail Group by     Job_id,   Job_step_id,   Job_release_id   Having count(*) >1  or        Job_id is null or        job_step_id is null or        job_release_id is null

Additional Comments

BJ thinks this was caused when steps were copied in 3.6 and the step release IDs were duplicated. This bug was fixed in 4.0. BJ is watching it to see if it happens on any releases created since 4.0 was installed. 

Affected Versions

Financial Manager 4.0 (and possibly 3.6 SP9) and Rehab Management 7.1 or later (possibly also 7.0)

Scroll to Top
Skip to content