Fusion Global Payroll: What are the Implications of Changing Payroll License Parameter?
(Doc ID 1937068.1)
Last updated on JULY 27, 2023
Applies to:
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.18.02.0 to 11.13.18.02.0 [Release 1.0]Oracle Fusion Global Payroll Cloud Service - Version 11.13.20.01.0 and later
Oracle Fusion Global Payroll - Version 11.12.1.0.0 and later
Oracle Fusion Global Human Resources - Version 11.12.1.0.0 and later
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.20.01.0 and later
Information in this document applies to any platform.
Goal
Currently implementing HR only for the countries GB, DE, FR, IE, NO, US, AU, SG & HK for our client.
The Payroll License parameter is therefore set to HR_ONLY.
This implementation includes the configuration of Elements.
What are the implications of the Payroll License parameter being set to HR_ONLY if the client decides for example to implement Fusion Payroll at some point in the future? Assuming the Payroll License parameter would then be set to PAYROLL, would the elements need to be dropped and recreated or would Oracle provide the means to make this transition seamless?
Similarly what would be the implications if Oracle developed a Payroll Interface for the non-US countries at some point in the future and the client wished to implement this interface? Assuming the Payroll License parameter would then be set to PAYROLL_INTERFACE, would the elements need to be dropped and recreated or would Oracle provide the means to make this transition seamless?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |