Hi,
We have fixed Time, Fixed resource tasks and then its assigned to the engineer. Next after few second its noted the job is uncomitted.
These engineers do not use Mobile and there is no Commit rule or any at the moment. Why PSO uncommit these manually allocated jobs?
Is there a way atleast we ca get a reason for this behavior?
First Committed
Then PSO uncommit it again.
Thanks
KM
Best answer by Sachitra_W
Hi
PSO does not directly uncommit activities that are already committed in the schedule; however, it can suggest that the external application perform the uncommit. This behaviour is handled by the DSP (Schedule Dispatch Service), which may recommend uncommitting an activity based on configured commit rules (for example, when the LogoffUncommit parameter is set to true and if the resource is logged off). To explain, the DSP does not update activity statuses directly in the database. Instead, it generates Suggested_Dispatch records in the output plan to indicate which activities should be committed or uncommitted. If the external application accepts this suggestion, it will then send a change file back to PSO to carry out the uncommit.
In your case, since you mentioned that no commit rules are configured, it is still possible that default rules are active. (For example, the LogoffUncommit rule typically defaults to 30, meaning the DSP may automatically suggest uncommitting activities in status 30 (Committed) when a resource logs off.)
To verify this, you can check whether the DSP service (not DSE) is generating a PLAN CHANGE file in the PSO audits few minutes after the manual change. If the DSP is suggesting the uncommit, you should see a corresponding Suggested_Dispatch record for the activity with a status_id of 0.
If the DSP is suggesting the uncommit even without commit rules, this may indicate an issue within PSO and should be reviewed by the IFS Support team.
However, if the uncommit occurs without any Suggested_Dispatch from PSO, it is more likely that the behaviour originates from the external application, where the external application is sending the uncommit request to PSO independently. In that case, further investigation should be carried out on the integration side.
Best regards,
Sachitra
+6Hi
PSO does not directly uncommit activities that are already committed in the schedule; however, it can suggest that the external application perform the uncommit. This behaviour is handled by the DSP (Schedule Dispatch Service), which may recommend uncommitting an activity based on configured commit rules (for example, when the LogoffUncommit parameter is set to true and if the resource is logged off). To explain, the DSP does not update activity statuses directly in the database. Instead, it generates Suggested_Dispatch records in the output plan to indicate which activities should be committed or uncommitted. If the external application accepts this suggestion, it will then send a change file back to PSO to carry out the uncommit.
In your case, since you mentioned that no commit rules are configured, it is still possible that default rules are active. (For example, the LogoffUncommit rule typically defaults to 30, meaning the DSP may automatically suggest uncommitting activities in status 30 (Committed) when a resource logs off.)
To verify this, you can check whether the DSP service (not DSE) is generating a PLAN CHANGE file in the PSO audits few minutes after the manual change. If the DSP is suggesting the uncommit, you should see a corresponding Suggested_Dispatch record for the activity with a status_id of 0.
If the DSP is suggesting the uncommit even without commit rules, this may indicate an issue within PSO and should be reviewed by the IFS Support team.
However, if the uncommit occurs without any Suggested_Dispatch from PSO, it is more likely that the behaviour originates from the external application, where the external application is sending the uncommit request to PSO independently. In that case, further investigation should be carried out on the integration side.
Best regards,
Sachitra
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
