3
Most read
4
Most read
6
Most read
Loading Smart Lists using FDMEE
Ray Fevrier
Data Integration Team
March 18, 2016
Confidential – Internal/Restricted/Highly Restricted Slide 2
Smart Lists in VisPlan Application
Account Member in
VisPlan
Smart List Value
Associated with the
Account
• Our sample has two data columns or Smart Lists:
– Depreciation Method
– Depreciation Convention
• Keep in mind, FDMEE can only handle one data column at a time
• Smart List textual value have to be converted to a number prior to load (i.e.
SLN = 1)
Confidential – Internal/Restricted/Highly Restricted Slide 3
Sample Data
• In FDMEE, add a dimension
for each Smart List values
• Under Data Table Column
Name, assign a UD number
to each dimension
• Assign a sequence number to
the SL dimensions to ensure
they get process first by
FDMEE
Confidential – Internal/Restricted/Highly Restricted Slide 4
FDMEE – Target Application Settings
Under Expression,
assign a dummy value
to both the Account
and Amount field to
prevent FDMEE from
erroring out
Confidential – Internal/Restricted/Highly Restricted Slide 5
FDMEE – Import Format Settings
Confidential – Internal/Restricted/Highly Restricted Slide 6
FDMEE - Location
• Under the Account dimension,
create a separate SQL mapping for
each SL value
• Match each script to a Data Load
Rule (once you have created the
DLR), that way each DLR will only
run a specific script
Confidential – Internal/Restricted/Highly Restricted Slide 7
FDMEE – Data Load Mapping Settings
Set AMOUNTX to the
mapped/target value of the
SL dimension (UD19X…)
Create an explicit
mapping for each SL
dimension with the SL
Name in the source
column and the SL ID in
the target
Confidential – Internal/Restricted/Highly Restricted Slide 8
FDMEE – Data Load Mapping Settings (Cont’d)
• Create a Data
Load Rule (DLR)
for each SL
value
• The DLRs are
exactly the
same, their
purpose is to
allow FDMEE to
process the file
as many time as
needed
Confidential – Internal/Restricted/Highly Restricted Slide 9
FDMEE – Data Load Rule Settings
Confidential – Internal/Restricted/Highly Restricted Slide 10
Execute the Data Load Rule
• The SQL script
hardcoded the
Account member
and converted SL
from a textual to a
numerical value
Confidential – Internal/Restricted/Highly Restricted Slide 11
FDMEE – Data Load Workbench
• SmatView retrieve
before and after the
data load
Confidential – Internal/Restricted/Highly Restricted Slide 12
Et Voila…

Loading Smartlists into PBCS using FDMEE

  • 1.
    Loading Smart Listsusing FDMEE Ray Fevrier Data Integration Team March 18, 2016
  • 2.
    Confidential – Internal/Restricted/HighlyRestricted Slide 2 Smart Lists in VisPlan Application Account Member in VisPlan Smart List Value Associated with the Account
  • 3.
    • Our samplehas two data columns or Smart Lists: – Depreciation Method – Depreciation Convention • Keep in mind, FDMEE can only handle one data column at a time • Smart List textual value have to be converted to a number prior to load (i.e. SLN = 1) Confidential – Internal/Restricted/Highly Restricted Slide 3 Sample Data
  • 4.
    • In FDMEE,add a dimension for each Smart List values • Under Data Table Column Name, assign a UD number to each dimension • Assign a sequence number to the SL dimensions to ensure they get process first by FDMEE Confidential – Internal/Restricted/Highly Restricted Slide 4 FDMEE – Target Application Settings
  • 5.
    Under Expression, assign adummy value to both the Account and Amount field to prevent FDMEE from erroring out Confidential – Internal/Restricted/Highly Restricted Slide 5 FDMEE – Import Format Settings
  • 6.
    Confidential – Internal/Restricted/HighlyRestricted Slide 6 FDMEE - Location
  • 7.
    • Under theAccount dimension, create a separate SQL mapping for each SL value • Match each script to a Data Load Rule (once you have created the DLR), that way each DLR will only run a specific script Confidential – Internal/Restricted/Highly Restricted Slide 7 FDMEE – Data Load Mapping Settings Set AMOUNTX to the mapped/target value of the SL dimension (UD19X…)
  • 8.
    Create an explicit mappingfor each SL dimension with the SL Name in the source column and the SL ID in the target Confidential – Internal/Restricted/Highly Restricted Slide 8 FDMEE – Data Load Mapping Settings (Cont’d)
  • 9.
    • Create aData Load Rule (DLR) for each SL value • The DLRs are exactly the same, their purpose is to allow FDMEE to process the file as many time as needed Confidential – Internal/Restricted/Highly Restricted Slide 9 FDMEE – Data Load Rule Settings
  • 10.
    Confidential – Internal/Restricted/HighlyRestricted Slide 10 Execute the Data Load Rule
  • 11.
    • The SQLscript hardcoded the Account member and converted SL from a textual to a numerical value Confidential – Internal/Restricted/Highly Restricted Slide 11 FDMEE – Data Load Workbench
  • 12.
    • SmatView retrieve beforeand after the data load Confidential – Internal/Restricted/Highly Restricted Slide 12 Et Voila…