Oracle Communities

Oracle Analytics and AI

Child Item

FAW: Cancel Work Relationship actions in HCM are not reflected in FAW by Incremental Load process

Hi,

The seeded pipeline configuration for HCM is expected to bring all changes performed in Oracle Fusion HCM into FAW.

We have observed that when HR users perform "Cancel Work Relationship" action in HCM, these do not flow into FAW as part of the incremental changes run. This causes incorrect representation of HCM data in all the FAW Facts/Metrics and Visualizations as the "cancelled" data points continue to remain in FAW though they are removed in HCM.

An SR (SR 3-35282668129) was raised for the same and Oracle confirmed the only work around is to perform a Full Reset of the Workforce Management Functional Area.

The Cancel WR is a common Standard business operation for HR Business Users to handle various business needs. And, performing a Full Reset of the Functional area each time a Cancel WR is performed can be performance and maintenance issue. The expectation is that all changes performed in Fusion HCM using delivered functionality must be reflected in FAW. Hence, we request the Seeded incremental Data Pipeline process to handle the Cancel Work Relationship actions performed in Fusion HCM and reflect in FAW.

This will provide confidence to customers on the data available in FAW as a true representation of the Fusion HCM data.

Thanks,

Vijay

Find more posts tagged with

Under Review

FDI

Status: Under Review

Comments

Raghavendra Raghunath-Oracle

Hi @Vijay Sridharan Assignment actions like cancel work relationship and reverse terminations will be evaluated for enhancements.

Raghu

Vijay Sridharan

Thanks Raghavendra. Look forward for this being available soon in FAW.

Raghavendra Raghunath-Oracle

Hi @Vijay Sridharan This is taking longer than we expected due to various priorities. This is definitely in our roadmap. Can I request you and others on this thread to share your respective use cases. Cancel Work relationship can happen at any pint in time, not necessarily the 'no show' workers after hiring. For ex: There can be a compliance related mandate in a few legislations to wipe off the worker record including all of their data in HCM after the person is terminated (just an example). Similarly if you have any other use cases.

Thanks

Raghu

Vijay Sridharan

Hi Raghu,

Typically worker records (Pending worker/ CWK/ Emp) are created through Inbound integrations as well and in some cases customers have observed workers mapped to wrong Legal entities in the integration or change of LE between offer and actual hire time. Hence, they rely on cancel WR to make the updates in HCM.

I have requested our customers to also log their use cases. This is a very important scenario that needs to be addressed in the FDI Data Pipeline at the earliest.

Thanks,

Vijay

MandeepGupta

This will be a really great feature. Mostly the use cases are as covered by Vijay.

In case of no show, the New Hire WR is cancelled.
In case of wrong employment information which can't be corrected, WR is cancelled.
In case a worker is hired with an incorrect person type, we prefer to cancel the WR and create a new one with correct person type.

Thanks.

A.J.

This would be very valuable to my organization as well! We have similar use cases as those mentioned by others. While an incremental ETL process that would remove these cancelled records would be ideal, even if a flag could be added on the FDI record that identifies it as not found in HCM, we could then exclude those records at the report level. This would be better than having these records show up as currently active in our FDI data.

It is causing mistrust in the tool from our business users as they find these records!