What are the business objectives for moving payroll processing out of your primary JDE instance?
Have you encountered any nasty surprises?
How are you moving data back and forth across tenants before and after payroll processing - SQL queries?
FYI our goal is to integrate JDE-E1 in near real-time with a cloud HCM system. So we're hoping a separate instance for payroll processing may help us i) circumvent Employee Master lock-down and ii) incrementally decouple benefits and allowances DBA's over time. Thanks, Paul
- 1 Posts
- 172 Views
Avoiding pay run record locking with separate Payroll-only JDE-E1 instance
Anyone heard of using a separate JDE-E1 instance for processing payroll? I understand at least some JDE clients do this and would appreciate clarification on any of the following...