|
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) |
|---|---|
Flow type (inbound/outbound) | Outbound |
Transformation rules followed in this flow? | NA |
File drop method (Pull,Drop) | Drop |
Iflow name | Source system | Production | Pre Production | SOLWEB Target |
|---|---|---|---|---|
ZHR_GDU_SF_TO_SOLWEB_Confluence_PO2 | Address: https://api2.successfactors.eu | Address: mftisprod:22 | Address: mftispreprod:22 | googlebucket: gudsis-confluence |
ZHR_GDU_SF_TO_SOLWEB_Solweb_PO2 | 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 IFLOW which will retrieve relevant EC data Information from the Employee Central (Success Factors) 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 SOLWEB Application.
This chapter aims to describe some advanced sections of API development. Basic topics won’t be explained as they are understandable by a CPI technician.
The SOLWEB Interface is has three integration flows:
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.
Message Mapping 1
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.
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.
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.
