|
Tech Pool Lead | |
|---|---|
| Internal Tech Contact/Service Owner |
Extracting the Active and Inactive data of employees.
Document type (PO, SO, Sales/Vendor, invoice,Shipment, Bank Statement, Customs invoice, etc) | Employee details (both active and inactive employees) |
|---|---|
Transformation rules followed in this flow? | NA |
File drop method (Pull,Drop) | Drop |
Integration Flow | Source System | Production | Pre Production | Syensqo Website Target |
|---|---|---|---|---|
ZHR_GDU_SF_TO_SOLWEB_Confluence_PO2 | Address: https://api2.successfactors.eu | Address: mftisprod:22 | Address: mftispreprod:22 | googlebucket: gudsis-confluence |
Send Employees from SuccessFactors to Syensqo Website | Address: https://api2.successfactors.eu | Address: mftisprod:22 | Address: mftispreprod:22 | Googlebucket: gudsis_file_upload |
ZHR_GDU_SF_TO_SOLWEB_MailJet_PO2 | Address: https://api2.successfactors.eu | Address: mftisprod:22 | Address: mftispreprod:22 | Googlebucket: gudsisexport-cas-solvay-prod |
Requirement is to implement an integration flow which will retrieve relevant EC data Information from the Employee Central (SuccessFactors) system using SAP Cloud Platform middleware, transformed into the required format of the Target system to MFT folders from which it will be sent to Solweb Application.
Employee Central (Success Factors) >> SCPI >> MFT >> Solweb
.csv file is generated daily of size nearly 50k and contains of both active and inactive employees data.
The following user details will be updated:
Fields | Values |
|---|---|
USER | |
FirstName | |
lastname | |
displayname | |
Entitycode | |
Entitytext | |
Entitygroupcode | |
Entitygrouptext | |
SiteCode | |
SiteText | |
Countrycode | |
Countrytext | |
Userstatus | |
Usertype | |
companycode | |
orgunit | |
orgunitcode | |
INTRANETSERVICE | |
FUNCTIONALAREAID | |
FUNCTIONALAREANAME | |
JOBFAMILYID | |
JOBFAMILYNAME | |
JVNOONE | |
LEADERSLIVE | |
SAPUSERTYPE | |
CADRE | |
IT_ACCESS |
The interface works as a job, running periodically. At the end of the execution a CSV format data will be sent to the Syensqo Website.
Configurations to the execution periodicity are made here. This Interface runs daily Once on time in CET TimeZone.
| Header | Purpose |
|---|---|
| SAP_Sender | For Monitoring |
| SAP_Receiver | For Monitoring |
| SAP_MessageType | For Monitoring |
| Property | Purpose |
|---|---|
| ExcludedBusinessUnits | Used to exclude business units in SuccessFactors Query |
| IncludedEmailsFromExcludedBusinessUnits | Used to include users with provided email addresses from excluded business units in SuccessFactors Query |
This Groovy Script escapes the exchange properties used in SuccessFactors URL. This is needed to overcome limitation of SuccessFactors Adapter that the Adapter fails to escape ampersand (&) character.
Please note, Connection Details will be maintained centrally on SuccessFactors page.
| Tab | Section | Parameter | Value |
|---|---|---|---|
| Processing | Processing Details | Operation Details | Query (GET) |
| Processing | Processing Details | Resource Path | User |
| Processing | Processing Details | Query Options | $select=country,custom06,email,firstName,lastName,teamMembersSize,username,empInfo/isContingentWorker,empInfo/jobInfoNav/businessUnit,empInfo/jobInfoNav/customString4,empInfo/jobInfoNav/emplStatus,empInfo/jobInfoNav/businessUnitNav/externalCode,empInfo/jobInfoNav/businessUnitNav/name,empInfo/jobInfoNav/companyNav/externalCode,empInfo/jobInfoNav/companyNav/name,empInfo/jobInfoNav/customString5Nav/externalCode,empInfo/jobInfoNav/departmentNav/externalCode,empInfo/jobInfoNav/departmentNav/name,empInfo/jobInfoNav/divisionNav/externalCode,empInfo/jobInfoNav/divisionNav/name,empInfo/jobInfoNav/emplStatusNav/localeLabel,empInfo/jobInfoNav/jobCodeNav/externalCode,empInfo/jobInfoNav/jobCodeNav/name,empInfo/jobInfoNav/jobCodeNav/name_en_US,empInfo/jobInfoNav/locationNav/externalCode,empInfo/jobInfoNav/locationNav/name,empInfo/jobInfoNav/locationNav/locationGroupFlxNav/externalCode,empInfo/jobInfoNav/locationNav/locationGroupFlxNav/name,userIdOfEmployeeTimeNav/approvalStatus,userIdOfEmployeeTimeNav/loaActualReturnDate,userIdOfEmployeeTimeNav/startDate,userIdOfEmployeeTimeNav/timeType&$expand=empInfo,empInfo/jobInfoNav,empInfo/jobInfoNav/businessUnitNav,empInfo/jobInfoNav/companyNav,empInfo/jobInfoNav/customString5Nav,empInfo/jobInfoNav/departmentNav,empInfo/jobInfoNav/divisionNav,empInfo/jobInfoNav/emplStatusNav,empInfo/jobInfoNav/jobCodeNav,empInfo/jobInfoNav/locationNav,empInfo/jobInfoNav/locationNav/locationGroupFlxNav,userIdOfEmployeeTimeNav& |
| Processing | Processing Details | Custom Query Options | |
| Processing | Processing Details | Pagination | Server Snapshot-Based |
| Processing | Processing Details | Page Size | |
| Processing | Processing Details | Retry on Failure | |
| Processing | Processing Details | Process in Pages | |
| Processing | Processing Details | Timeout (in min) | 1 |
| Processing | Header Details | Request Headers | |
| Processing | Header Details | Response Headers |
SFTP Adapter is used to put the file in webMethods MFT.
| Tab | Section | Parameter | Value |
|---|---|---|---|
This Integration is designed to update the Active and Inactive EC users into the SOLWEB.
Configurations to the execution periodicity are made here. This Interface runs daily Once on time in CET TimeZone.
To get the EC data and filter out the Active users in EC.
The Message Mapping is used to map two different structures and getting the output in desired format. Here, we’re doing one to one mapping with our target data structure. Comparing the EC data with SOLWEB data.
Added new mapping expression for Intranet service to differentiate users with syensqo, solvay and solvay-zout.
Converting the xml payload into the csv format by giving the xpath and separating them by Semicolon.
One to One Mapping of required fields.
Converting the xml payload into the csv format by giving the xpath and separating them by Semicolon.
To send message to multiple routes simultaneously.
By using parallel Multicast, we’re sending the data to the SOLWEB Application directory.
