Configuring Admin Data
To configure Oracle Utilities Work and Asset Cloud Service admin data setup for the integration:
1. Login to Oracle Utilities Work and Asset Cloud Service.
2. Navigate to External System.
Define the External System representing the Oracle Human Capital Management Cloud. This is used by Employee, Job, and Employee Absence Integrations.
3. Navigate to Country.
Define a Country code that will be used within the Employee address information.
4. Navigate to Business Unit.
Define Business Unit(s) used within the Employee integration.
5. Navigate to Inbound Web Service (IWS).
The following REST IWS are delivered for this integration:
W1-Craft
W1-EmployeeSynchronization
W1-Leave
The full URI Component for the REST web service is configurable.
Refer to Oracle Utilities Work and Asset Cloud Service documentation for instructions about the one-time setup.
6. Navigate to Master Configuration > HCM Integration Master Configuration.
This is used by Job(Craft) and Employee Absence(Leave) sync integrations.
a. In the Main section, define the Oracle Human Capital Management External System created in Step 2.
b. Defines a Key Reference Mapping keyed by Maintenance Object to find existing integration records. Create a row for the Resource Type Maintenance Object used for JobSync Integration and create another row for the Employee Unavailability Maintenance Object for Absence SyncIntegration.
For reference, refer to the following table.
Maintenance Object
Business Object
Ongoing Sync Key Reference View
Identifier Type
W1-EU
(Employee Unavailability)
W1-LeaveInt (Leave)
W1_ON_EU_VW
(Employee Unavailability View)
W1EI
W1-RESRCTYPE (Resource Type)
W1-Craft (Craft)
W1_ON_CRAFT_VW
(Ongoing Sync Key Craft View)
W1EI
c. In Accounting Information, define Regular and Premium Expense Codes to use as defaults within the Job Integration.
7. Navigate to Master Configuration > Seeder Sync Request Master Configuration. This is used by Employee sync integration.
a. Create a row for the Oracle Human Capital Management External System and Employee Maintenance Object (MO): W1-EMP for Employee Sync Integration.
b. Defines the Ongoing Sync Request BO that will process the integration record and the Ongoing Sync Key Reference View to find existing integration records.
For reference, refer to the table below:
Maintenance Object
Business Object
Ongoing Sync Key Reference View
Identifier Type
W1-EMP (Employee)
W1-OngoingSync
RequestEmployee
(Employee Ongoing Sync Request)
W1_ON_EMPLOYEE_VW (Ongoing Sync Key Employee View)
W1EI
8. Navigate to Master Configuration > Master Data Synchronization Master Configuration.
a. This Master Configuration is used to update External IDs with IDs used within Oracle Utilities Work and Asset Cloud Service. Create a row for the Employee FK Ref and Oracle Human Capital Management External System that references the Employee Ongoing Sync Key Reference View.
For reference, refer to the table below:
FK Reference
Ongoing Sync Key Reference View
External System
Identifier Type
W1-EMP (Employee)
W1_ON_EMPLOYEE_VW (Ongoing Sync Key Employee View)
HCM External System created in Step 2
W1EI
9. Navigate to Business Object.
SOA-based ERP integrations required positive/negative acknowledgment messages to be returned to the ERP system. These are not needed for the Oracle Application Cloud - HCM integrations.
On the Employee Ongoing Sync Request Business Object, inactivate the following lifecycle algorithms. To inactivate the algorithm, add an Option within the Status with an Inactive Algorithm Option Type and the name of the algorithm within the Value field.
a. Synchronized (SYNCHRONIZED) Status - Create Positive Acknowledgment for ERP (W1-CPOSAERP)
b. Negative Acknowledgement Sent (NEG-ACK-SENT) Status - Create Negative Acknowledgement (W1-CRENEGACK)
c. Navigate to User.
User records: Employee records will be matched against any existing Oracle Utilities Work and Asset Cloud Service User record. The User and Employee records must match on First Name, Last Name, and Email Address (if Email Address is sent with the employee record and exists on the User record).