Candidate candidacy status in HRP5133 table and On portal is different.

[former_member813945]

Hi,

We have implemented E-recruitment EHP6 (SP11). We are facing unseen scenario wherein, the candidate application status is not getting changed from IN Process to Rejected in REJECTION Process in HRP5133 table. However, on portal it shows Status Rejected and Process Rejection.

In Rejection process we have the Rejection activity. This is the standard activity.

In assignments of activity types to object types, for Rejection activity ND and NE objects are also assigned.

For any further information, pls let us know.

Regards,

Sarika Mansukh

[Former Member · Accepted solution]

Hi Sarika

It is a status changing step.So please check if you have maintained the IMG step "Assign a status to status -changing activity" to NE and ND  in the table  V77RCF_ACT2STAT.

Hope this helps

Regards

Selvia

[former_member813945 · Accepted solution]

Hi Selvia,

Thanks for your reply.

In table V77RCF_ACT2STAT the Rejection activity is already maintained for NE and ND objects still i am facing this issue.

PLease check below config for your information.

Regrds,

Sarika M

[Former Member · Accepted solution]

Hello Sarika,

When a recruiter creates any status change activity, it updates the NE object and the entry is stored in HRP5133 table. The data which is viewed by the candidate is the status of ND object pulled from HRP5132 table (and offcourse these are related objects).

There is a standard workflow which updates the status (Status Change workflow (ERCStatusChg_2)). This workflow is responsible for making the required status changes. Please check if this is working as expected.

Hope this helps.

Regards,

Sarvesh Hasija

[former_member813945 · Accepted solution]

Hi Sarvesh,

Thanks for your responce.

The issue has been resolved this reason was ERCActCrea_2 workflow was deactivated. Hence, the application status (ND) was not getting changed.

Thanks!

Regrds,

Sarika Mansukh

[Former Member · Accepted solution]

Great to know that the problem has been fixed. Please close the thread specifying this has been resolved