A Step-by-Step Integration Walkthrough
Introduction
Employee onboarding in large organizations requires seamless coordination between HR systems, identity platforms, and IT teams. This blog explains a real-time Employee ID and User Account creation process implemented using Oracle Fusion HCM, a 3rd-party system, and the IT Service Desk.
The flow described below is implemented exactly as designed, without changing any steps, and covers how employee data is fetched, validated, and provisioned for system access.
Step 1: Fetch New Hire and Transferred Employee Records
The process begins when a new hire or transferred employee is created in Oracle Fusion HCM.
A 3rd-party integration is configured in the test instance. The 3rd-party system calls a BI Publisher SOAP API exposed by Oracle Fusion HCM to fetch employee details and create the corresponding employee record in their system.
Integration Details
- Employee ID: 30007155
- Employee Name: Muhammad Umar Malek
API Details
- URL:
https://ekjy-test.fa.em2.oraclecloud.com/xmlpserver/services/ExternalReportWSSService?WSDL - Authorization: Authorization details must be provided
Sample SOAP Request Payload
<soap:Envelope xmlns:soap=”http://www.w3.org/2003/05/soap-envelope”
xmlns:pub=”http://xmlns.oracle.com/oxp/service/PublicReportService”>
<soap:Header/>
<soap:Body>
<pub:runReport>
<pub:reportRequest>
<pub:reportAbsolutePath>
/Custom/Human Capital Management/SOAIS
REPORT/Login_ID_Creation/integration_report.xdo
</pub:reportAbsolutePath>
<pub:sizeOfDataChunkDownload>-1</pub:sizeOfDataChunkDownload>
</pub:reportRequest>
</pub:runReport>
</soap:Body>
</soap:Envelope>
Outcome:
The 3rd-party system successfully retrieves new hire and transferred employee records from Oracle Fusion HCM.
Step 2: Employee Alias Generation and Validation
For each employee record received:
- The system generates a unique Employee Alias
- The alias is validated against:
- LDAP
- SAP R/3
- Oracle systems
If the alias already exists, a new alias is generated until a unique value is obtained.
IT Service Desk Role
- IT Service Desk users log in to their portal
- They can view all pending employee records
- This provides visibility into employees awaiting ID creation
Outcome:
A validated and unique Employee Alias is finalized for the employee.
Step 3: Email ID Creation and Fusion User Account Creation
Once the alias is finalized:
- The 3rd-party system generates the official email ID based on the employee’s Business Unit
- After email creation, a request is sent to Oracle Fusion to create the user account using the SCIM API
Create User Account in Fusion
- URL:
https://ekjy-test.fa.em2.oraclecloud.com/hcmRestApi/scim/Users - Method: POST
Sample Request Payload
{
“schemas”: [
“urn:scim:schemas:core:2.0:User”
],
“active”: true,
“userName”: “SUMAN.NAIYA2”,
“password”: “abcdefg@123”,
“emails”: [
{
“primary”: true,
“value”: “sumannaiya949@testessar.com”,
“type”: “W1”
}
],
“displayName”: “SUMAN NAIYA2”
}
Sample Response (Excerpt)
{
“id”: “418F4DF1CEBE909CE0638E3C12ACB014”
}
Important:
The response contains a GUID, which uniquely identifies the user account in Oracle Fusion.
Outcome:
Oracle Fusion user account is successfully created.
Step 4: Link User Account with Newly Hired Employee
In the final step, the created user account is linked to the employee’s person record in Oracle Fusion HCM.
The GUID received in Step 3 is used to associate the user account with the Person ID.
API Details
- URL:
https://ekjy-test.fa.em2.oraclecloud.com/hcmRestApi/resources/11.13.18.05/userAccounts/418F4DF1CEBD909CE0638E3C12ACB014 - Method: PATCH
Sample Request Payload
{
“PersonId”: “300000336579000”
}
- New Hire Person ID: 300000336579000
Outcome:
The user account is successfully linked, enabling the employee to log in to Oracle Fusion.
5. Logical Flow Explanation (Block Diagram)
- Oracle Fusion HCM creates a New Hire or Transfer employee
- BIP SOAP API exposes employee data
- 3rd Party System processes the data and generates a unique alias
- Alias validation loops internally until uniqueness is achieved
- IT Service Desk views pending employee records
- Official Email ID is generated
- SCIM API creates the Fusion user account
- User GUID is received
- User account is linked to the Person ID
- Employee login access is enabled
Conclusion
This Employee ID creation process ensures a controlled, secure, and automated onboarding flow by integrating Oracle Fusion HCM with a 3rd-party system and IT Service Desk. By strictly following the defined steps, organizations can ensure consistent identity creation, reduced manual intervention, and faster employee access to enterprise systems.
