nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

HCM (Empower) deletes are not being propagated to the ADW/FAW

JDCal

When we cancel a new employee's employment status when they do not come on board, we are finding that the cancelations are not being propagated to ADW/FAW. This is not an employee who has started and been terminated, but it is one who was hired but decided not to come onboard after accepting the position. We will cancel the employee's payroll, benefits, etc. before cancelling his/her employment status. We have tried using the Classic and Responsive UIs in the process but have issues with both via testing.

Any ideas on how this process should work and what we could do differently?

Thanks

Find more posts tagged with

HCM

FDI Back End

FDI Front End

HCM Analytics Content

FDI

Accepted answers

Sumanth V -Oracle

@JDCal - Please confirm if the use case is as below:
If an employee accepted offer from XYZ org and did not join office then his
record is termed as cancelled work relationship in fusion. Those records are
deleted in fusion. FAW keeps those records as active employee. Only Reset the
HCM modules is a solution for them.

Cancel work relationship will purge records from source and it won't get reflected in DW. Current possible workaround is to reload data for the specific functional area. Please refer the below document for details on same:
https://docs.oracle.com/en/cloud/saas/analytics/24r2/fawag/reload-data-data-pipeline.html

All comments

Sumanth V -Oracle

JDCal

Thank you Sumanth. I will review the documentation. That was my fear that was the functionality. I have an SR currently open with Oracle.

Orange

Thanks @JDCal and @Sumanth V -Oracle. Interesting read. Resetting the entire data warehouse to reload the data of all subject areas is quite a big burden. Perhaps technically, resetting the warehouse is the only way, but it's not pragmatic to do this frequently. I'm looking forward to hearing the feedback from Oracle Support on the SR. Kindly keep us posted, JDCal.

JDCal

Yes, so true! That is what we have been doing for a while and it takes around 3 days to reset/refresh. I will update this thread once we get a final Sr determination on this issue. There has to be another way!

Ashish-Oracle

@JDCal As per @Sumanth V -Oracle's suggestion reloading the specific functional area ie. HCM Workforce Management should be enough here instead of the complete Reset warehouse operation. Have you tried that already and it does not help?