Forum

Helping a sister company on SuccessFactors Employee Central. Their onboarding integration is triggered by the 'Rehire' Intelligent Services event, and for rehires it fires twice — so the downstream system creates two records. Single hires are fine. Looks like the rehire is generating both a 'Rehire' and a 'Hire' event, or the same event twice with different effective dates. Anyone seen this?

We have position management switched on. HR creates positions, but Finance edits the budget and cost center on them directly in the system because they own the org budget. Predictably, positions drift — titles that don't match the job, FTE that doesn't match the budget line, vacancies that Finance closed but HR still recruits against. I don't think the answer is 'take Finance's access away'. How have people drawn this line cleanly?

Mid-project on EBS R12 to Fusion. We're initializing balances as of go-live and loading open element entries. The recurring entries load fine, but anything with a retro impact from before go-live isn't reflected — so the first Fusion payroll under-recovers on a few loans and over-pays on a couple of allowances that had a backdated increase in EBS. Are people loading a separate retro adjustment element for the pre-go-live delta, or is there a cleaner way through balance init?

Finance and HR argue about headcount every month because the number in the BI warehouse is 30-40 off from the core HR system. The warehouse loads from a nightly extract. When I reconcile, the drift is always a mix of: employees on unpaid leave, employees pending a future-dated termination, and a few contingent workers. Everyone counts these differently. Before I go define 'headcount' for the fourth time — is there a standard the GCC crowd actually agrees on?

Monthly WPS SIF upload rejected. Bank says the employee count and total don't match their register. Our payroll register is correct. Diffing the SIF against the bank's expected list, three employees are on the bank side that we terminated last month, and two new joiners are missing from the bank side. So it's a sync gap between our HR system and the bank's MOL register, not the SIF format. How are people keeping that register in sync without doing it by hand every month?

Transfer workflow with a conditional approver — 'if the target entity differs from the source entity, add the target entity HR head'. Works for moves within a country. For cross-entity moves the step resolves to nobody and the request just sits there. The target entity HR head role is definitely assigned. Feels like the condition is reading the source context, not the target.

Our Hire BP has a conditional 'Request Compensation Change' step gated on a calculated field that checks the job profile's compensation grade. For one supervisory org it never fires, even though the grades are populated. Same job profiles work fine elsewhere. I've checked the condition rule, the security groups on the step, and the org's staffing model. Stuck.

We run a small GB population off the same Fusion instance as our GCC entities. Every cycle a handful of employees are 1p off on net pay versus the parallel run. It's always the same shape — someone with a mid-period rate change and a percentage-based deduction. I suspect the order of the deduction fast formula relative to the proration formula. Has anyone nailed down whether it's a rounding rule on the element or the formula itself?