Personalization refers to changes that a user can make to certain artifacts in the ERP Cloud application on the user interface. These changes can be made to apply for a specific user or for all users accessing the applications. Personalization can be used to change properties of fields such as changing its width. A user can also redesign multiple aspects of using a composer-based personalization. Personalizations are done using the sandbox; all the changes done through personalization remain only to the user who has the activated sandbox, until the sandbox is published, and it will not be visible to any other user.
For example, a user can rearrange certain objects on a page, add and remove designated content, or save queries. A user can add other content to this page or change the order of the current content.
Personalization can also be done on the basis of roles and users. For example, a field on a form can be made visible only to users having a specific role. Expression language can be used to perform user- or role-based personalizations.
Groovy scripts can also be used to perform personalizations for different objects on ERP cloud pages.
Clients require an approval workflow for payments. Hence, there is a requirement for two sets of users in Payment Workflow (given below):
· Payment Creators: Employees who can only create a Payment Process Request (PPR) but cannot authorize it for final payment
· Payment Approvers: Employees who can only authorize the PPR created by Payment Creators but not create PPRs
· Oracle does not support payment approval workflows
· Job roles available in Oracle:
- Accounts Payable (AP) Supervisor: Can create a PPR and authorize it
- AP Manager: Can edit/stop/authorize the PPR submitted by the AP Supervisor
According to client requirement, the AP Supervisor should only create the PPR and not authorize it, but seeded AP Supervisor role has the access to authorize PPR.
Reimbursement currency selection on the expense report should be enabled only for one user in the company. It should be read only for the rest of the users in the company.
Oracle either allows reimbursement currency selection to be enabled for all the employees or none of the employees in the organization.
A bulk of asset addition transactions are created through interface with payables module or project module and these transaction are approved in their respective origination system, so can do without approval in the fixed asset module. However, the client needs transactions such as financial adjustments—cost changes, asset life changes, and depreciation method changes—to be approved before being completed in the system.
There is no approval workflow capability delivered out of the box for any of the fixed asset transactions.
Payables ( Note this is delivered functionality in R13)
Create a custom role which is a duplicate of AP Manager Role. On the Review Proposed Payments Screen (Payment Authorization Screen), hide the “Review Proposed Payment” button for payment creators via role-based personalization. This button will only be visible to Payment Approvers/users assigned to the custom AP Manager role.
User-based personalization using expression language is used to make the Reimbursement Currency selection enabled only for one user in the company who is part of the top management.
Role-based personalization, along with groovy scripts, is used to customize the asset transaction pages to simulate a simple two-step approval process.
Role-based personalization: A custom role is created based on seeded AP Manager Role. On the Review Proposed Payments Screen (Payment Authorization Screen), the “Review Proposed Payment” button is hidden for payment creators via role-based personalization. This button will only be visible to Payment Approvers/users having custom AP Manager role.
Hide the Review Proposed Payment Button for Payment Creators and make it visible only to the Payment Approvers.
“Review Proposed Payment” screen as visible to Payment Approver. “Resume Payment Process” button is enabled.
“Review Proposed Payment” screen as visible to Payment Creator. “Resume Payment Process” button is disabled.