UBS Dividend Equivalent Interface Design
UBS Dividend Equivalent Interface Design
Inbound Interface
Technical Design Document
09/14/2017 Ian Abastillas 0.3 Update Error Log and Error Log Email Sections
09/18/2017 Ian Abastillas 0.4 Add Current File initial processing for Boomi.
The purpose of this document is to provide a detailed functional design of the interfaces required for Project
HeRO, the TI HCM Cloud Implementation Project.
Interface Details
SR# 63
Short Title Dividend Equivalent Feed from UBS
Description Dividend Equivalent Feed from UBS
Interface Type Inbound
Integrating Application UBS
2. Integration Method
This section provides the details on the methods and impacted business objects on where the data will be
loaded.
Integration Method
3. Extract Definition
This section will identify the User Entity associated with the data group of this extract. A reference to the
common data category superset document is also provided.
Use $ApacheDate from Input File as the value for the criteria.
Processing Type Full
PERSON_NUMBER,COST_CENTER,ROE
0000616,003,1
0002771,003,1
0006120,003,1
0011451,003,1
4. Assumptions
This section details out the set of assumptions captured for this interface that will serve as a guide for the
scope and limitations of the integration.
# Assumption(s)
1 The Dividend equivalent payments file provided by UBS is pipe delimited and the payment amount is
in USD for all employees.
2 The integration will need to determine if it is a US employee or not.
a. The load will contain Active, Terminated, & Leaves. The dividend is to be paid for all
employees loaded.
b. Processing of US payroll on cycle or off-cycle should not affect the integration as long as
element are loaded
3 For non-US employees, amount will be converted from USD to the user’s local currency and load into
the countries corresponding element.
If the integration cannot convert, then it should not load the Non US employees but should instead
parse out the data and log or save into a file that can be emailed to the equity team. The file needs to
include the employees current currency and country.
a. Non-U.S. payouts are converted to local currency based on the employee’s current payroll
currency and a 12/1 ROE unless local country rules require the use of an ROE per that
countries bank.
4 The summary report should be generated for finance in USD and local currency.
EmployeeID
Country
Amount in USD
This section will contain the details on how the PBL Input file template should be created. It will also
contain
Notes:
(1) All discriminators that fall under one Business Object should be contained on one PBL Template (.dat) file.
Filename should be the Business Object name (i.e. [Link]).
(2) Zip file must contain all the Business Object files
This is the Current Input File layout of Dividend Equivalent Payments in Pipe Delimited that was
provided by UBS and amount is in USD.
- Expat Flag
- Current/Work Currency
- Current/Work Country
Field Max
Field Format Oracle Field Comment
# Length
HDR|TXN|001|MMDDYYYY|[Link]|DVDN
Header
D
Person
1 Emplid Alphanumeric 10
Number
Payment
3 Numeric No max
Amount
Y or N; Y =
4 Expat Flag Alphanumeric
expat
Employees
Employee
current
5 Current Alphanumeric
Currency
Currency
Code
Employees
Employee
current
6 Current Alphanumeric
country
Country
location
TRL|TXN|001|MMDDYYYY|[Link]|DVDND
Footer
|# records|total $ amount
Header Records
1 - $LineID ‘HDR’
2 - $Company ‘TXN’
3 - $CompCd ‘001’
4 - $TrnDate --
5 - $TrnTime --
6 - $DistribName ‘DVDND’
Detail Records
1 - $Emplid --
2 - $Name --
4 - $ExpatFlg --
5 - $EmplCurr --
6 - $EmpCountry --
Footer Records
1 - $LineID ‘TRL’
2 - $Company ‘TXN’
3 - $CompCd ‘001’
4 - $TrnDate --
5 - $TrnTime --
6 - $DistribName ‘DVDND’
7 - $RecCnt --
8 - $TotalAmt --
1 - $Enplid --
2 - $Division --
3 - $Country --
4 - $AmtUSD --
5 - $AmtLoc --
b. Boomi will add new field (Transaction Date from Input File) at the end of each detail records.
c. Boomi will Generate new file and will be broken down by Country.
d. Boomi will add new field $ApacheDate (value from apache card, ‘YYYYMMDD’ format) after
$TrnDate.
1 - $Emplid --
2 - $Name --
3 - $PayAmt --
4 - $ExpatFlg --
5 - $EmplCurr --
6 - $EmpCountry --
7 - $TrnDate --
8 - $ApacheDate --
Delimiter N/A
Vendor Input File Validate each Detail Records based on below criteria
IF $ExpatFlg = ‘N’
AND $EmpCountry <> ‘ISR’
AND $EmplCurr <> ‘USD’ THEN
Retrive the value from BI Report using $ApacheDate
to determine the exchange rate and use it with $PayAmt to
convert the value to Local Currency Amount.
*Note:
The BI Report includes a criteria to pull data when ROE (rate of
exchange) date is the same with the apache date. If this
condition is not satisfied, the BI Report will not return any
data. Boomi needs to identify this scenario and trigger email
notification stating that there is no ROE loaded for the day.
(See the second email details under the email notification
section for details)
UDT structure:
General
Validation
Create Element
Hardcoded Value: Create Element Entry
Entry
Derived Use $Emplid from vendor file to pull Assignment ID from the
Assignment
TI_GET_ASSIGNMET_NUMBER value set as of the apache date which is
Number
included in fast formula.
EffectiveEndDate Derived Null - This will be auto populated with the pay period end date.
The element name will be retrieved based on Assignment Home Country Code.
Use $Emplid from vendor file to pull Assignment Employee Salary Code
then evaluate
If value is ‘USD’
The details of the summary report below will be retrieved from the New Input File broken down by
Country and Division. The summary report should be generated for finance in USD and Local Currency.
Boomi will use BI Report to pull the details of Cost Center to be use on this Summary Report.
Employee ID
Country
Amount in USD
Transformation/Business Logic
HCM Cloud
Vendor Layout Extract Field Data
Attribute Extract Filter Criteria
Transformation
This section will define the mappings, transformations and/or details of the Error log and email notification
to be sent. This will be done by Fast Formula in HCM.
Filename N/A
Header Records
LineID Derived
Retrieve value from $LineID in the input file.
Company Derived
Retrieve value from $Company in the input file.
CompCd Derived
Retrieve value from $CompCd in the input file.
TrnDate Derived
Retrieve value from $TrnDate in the input file.
TrnTime Derived
Retrieve value from $TrnTime in the input file.
DistribName Derived
Retrieve value from $DistribName in the input file.
Detail Records
Emplid Derived
Retrieve value from $Emplid in the input file.
Name Derived
Retrieve value from $Name in the input file.
PayAmt Derived
Retrieve value from $PayAmt in the input file.
ExpatFlg Derived
Retrieve value from $ExpatFlg in the input file.
EmplCurr Derived
Retrieve value from $EmplCurr in the input file.
EmpCountry Derived
Retrieve value from $EmpCountry in the input file.
Footer Records
LineID Derived
Retrieve value from $LineID in the input file.
Company Derived
Retrieve value from $Company in the input file.
Criteria Transformation
Email Trigger
When annual file is received and processed
Email From
[Link]@[Link]
Email To
soauditors@[Link]
Email CC
N/A
Value is “Inbound Process
Subject
ZUBSDE_TI_PBL_LOAD_AND_TRANSFER_BATCH Completed”
Attachment File
N/A
Name
Email Body
In Order to access process output and logs - kindly refer to
the procedure document
[Link]
[Link]?id=/sites/hroperations/hero/Technology/Integr
Criteria Transformation
Email To
esppadmin@[Link]
Email CC
compsys@[Link]
Subject Dividend Equivalent Payments feed - no match on ROE date.
Attachment File
N/A
Name
Criteria Transformation
Email Trigger
When annual file is received and processed
Email From
[Link]@[Link]
Email To
soauditors@[Link]
Email CC
N/A
Subject
Annual Dividend Equivalent Summary Report
Attachment File
Name DEQ_PBLSummary.txt
Email Body Attached is the summary report for Annual Dividend Equivalent
load.
9. Execution
Execution Details
Frequency Annual
Transformation
TI_ ZUBSDE _BATCH_LOAD_FF
Formula
SFTP Parameters/Details
Vendor Private Key TBD – PGP Key to be provided by the client team
Vendor Point Of
TBD
Contact
ID Source Title Item Description Work stream Owner Date Due Status Updates/Next
Type Create Date Steps
d
DDMM Initials:
Action Verb
(Newest Updates at
Top)
N/A
This section will include any relevant testing scenarios that needs to be accounted for during Test phases.
1 Load Required attributes and needed Business Successfully loaded attributes required and
Objects business objects needed
2 Validate that the input file is successfully Input Data are loaded successfully in Fusion.
processed by the middleware and is loaded
successfully into Fusion.
3 Verify that the integration is able to insert new New Data are being inserted successfully into
Data into Fusion. Fusion.
4 Verify that the integration is able to Update Existing Data are being updated successfully into
existing data into Fusion. Fusion.