Levi's migrated from Hyperion FDM Classic to FDMEE and learned several lessons during the process. Key aspects of the migration included transforming import scripts, simplifying mappings between dimensions, and moving historical data. Levi's also began using DRM to centrally manage brand and cost center hierarchies between Essbase and FDMEE for improved data alignment. The migration helped address prior pain points around complex mappings and inconsistencies while reducing reliance on IT resources.

2. How To Migrate to FDMEE and Not
Die Trying – Levi’s Knows
Chris Chong – Levi’s Strauss & Co.
Joy Hsu – Independent Consultant

3. Safe Harbor Statement
The following is intended for information purposes only on behalf of Levi and
Strauss, and may not be incorporated into any contract. It is not a commitment to
deliver any services or functionality, and should not be relied upon in making
purchasing decisions. This provides no warranties with respect to the offerings
described within. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of
Oracle.
3

4.  Christopher Chong
● Systems Manager at Levi Strauss & Co.
● Expertise in FDM, FDMEE, DRM, HFM and SAP
 Joy Hsu
● Hyperion Financial Close Solution Architect
● Technical expertise in FDMEE, FCM, HFM and HTP
● Functional expertise in financial close process
Who are we?
4

5. Show your hands!
 Currently have FDM Classic?
5

6. Agenda
 Levi’s Environment
 Jumping through hoops
● FDM Challenges and Pain Points
● FDMEE Architecture
● FDM to FDMEE Transformation
 Lessons Learned
6

7.  GL Systems:
● 3 SAP instances (6.01 and 6.04)
● Multiple Non-SAP GL systems
 Hyperion Applications:
● Data Relationship Management (DRM)
● FDMEE
● Hyperion Financial Management (HFM)
● Hyperion Tax Provisioning (HTP)
● Essbase
Levi’s Environment

8. JUMPING THROUGH HOOPS
8

9.  FDM Challenges and Pain Points
 FDMEE Architecture
 FDM to FDMEE Transformation
● Historical Data
● Scripts
● Locations
● Mappings
Step 1 – 2 – 3

10. FDM Challenges and Pain Points
 FDM environment contained detailed import
scripts that integrated a Data Warehouse
staging area for the USA and European entities
– 2 hours process
 Complex entity dimension and mappings
 Inconsistency (Cost Center and Brand)
between HFM and Essbase
 FDM Mappings heavily rely on IT Dept

11. Addressing the Challenges
 Simplification is what we used to address pain points

12. FDMEE Architecture
12

13. FDM to FDMEE Transformation
 Scripts and Import format stats:
● Classic FDM: 39 imports scripts & 14 import formats
● FDMEE: 18 import scripts & 17 import formats
 Locations: 76 file locations/ 8 JE locations
 Mappings: new HFM dimensions
 Data: 2 years HFM historical data and 3 parallel testing

14. Transformation - Dimensionality
Old HFM Example New HFM Example
1 Entity DLC10L 1 Entity DE278
2 Cost Center Opex Selling
3 Segment Europe
2 GL Account 620000 4 G/L Account 620000
5 Account NIOpexSell
3 Scenario Actual → 6 Scenario Actual
4 Period May → 7 Period May
5 Year 2012 → 8 Year 2012
6 View YTD → 9 View YTD
7 Value Entity Currency → 10 Value Entity Currency
8 ICP [ICP None] → 11 ICP [ICP None]
9 Brand DOCKERS → 12 Brand DOCKERS
13 BSFlows CLO
14 Audit Trail Load

15. HISTORICAL DATA
DRM

16. Transformation - Dimensionality
Old HFM Example New HFM Example
1 Entity DLC10L 1 Entity DE278
2 Cost Center Opex Selling
3 Segment Europe
2 GL Account 620000 4 G/L Account 620000
5 Account NIOpexSell
3 Scenario Actual → 6 Scenario Actual
4 Period May → 7 Period May
5 Year 2012 → 8 Year 2012
6 View YTD → 9 View YTD
7 Value Entity Currency → 10 Value Entity Currency
8 ICP [ICP None] → 11 ICP [ICP None]
9 Brand DOCKERS → 12 Brand DOCKERS
13 BSFlows CLO
14 Audit Trail Load

17. Entity/GL Account
Is currententityanexception
associatedwithUS200 mappings
(listattached)*?
CorrespondingAccounts andGL
Accounts will be tagged with a
Cost Center (eg. 30L->OpexAdv)
Yes
No
Doesthe Entityname include
a Cost Center?
No
Cost Center = Opexdiff (OpexNo Function)
Doesthe GL Accountfall
within600000-684899? Cost Center = None
Yes
No
Yes
Cost Center Exceptions map
accordingto list*
Cost Center Mapping Logic
* List of Exceptions
A
B
C
D

18.  CASE
 WHEN (DATEPART(YEAR, PERIODKEY) * 100 + DATEPART(MONTH, PERIODKEY) <
201212) AND Entity LIKE '%INPUT' AND (Account LIKE '6050%' OR Account LIKE '6055%')
THEN 'OpexAdm‘
 WHEN UD1 BETWEEN '600000' AND '684899' THEN
 CASE
 WHEN EntityX IN ('US200') THEN
 CASE
 WHEN Entity IN ('TDZNC40L','TTC40L','USC40L','VTC40L') THEN 'OpexDist'
 WHEN Entity IN ('TDZNC10L','TTC10L','USC10L','VTC10L') THEN 'OpexSell'

 ELSE
 CASE Left(Right(Entity, 3), 2)
 WHEN '10' THEN 'OpexSell'
 WHEN '20' THEN 'OpexMktg'
 WHEN '30' THEN 'OpexAdv'
 ELSE 'OpexDiff' .
Cost Center Mapping – SQL Script
(Partial scripts)

19. Cost Center Mapping – Historical Data
Old HFM
Entity
New HFM
Cost Center
EUINPUT - LSE EUR Pre Adjustments None
EUC00L - LSE - Total Cost Centers None
EUC10L - LSE - Selling OPEX Selling
EUC20L - LSE - Marketing OPEX Marketing
EUC30L - LSE - Adv. & Promo. OPEX Advertising
EUC40L - LSE - Distribution OPEX Distribution
EUC50L - LSE - Administration None
EUC51L - LSE - Finance OPEX Finance
EUC52L - LSE - Human Resources OPEX HR
EUC53L - LSE - Other Admin. OPEX Other Admin
EUC60L - LSE - Info. Resources OPEX Info Resources
EUC70L - LSE - Operations OPEX Operations
EU001L - LSE EUR None
 Mapping Result:

20. FDM vs. FDMEE
Scripts

21. Transformation - Import Scripts
Location FDM FDMEE
LSA USA Import script was customized to
retrieve data from Data Warehouse
staging area then imported to FDM.
In total 356 lines of code were written
for this entity
Removed custom import scripts and
adopted simplified comma delimited
import format with a few expression
scripts
LSE Europe Import script was customized to
retrieve data from Data Warehouse
staging area then imported to FDM.
In total 354 lines of code were written
for this entity
Removed custom import scripts and
adopted simplified comma delimited
import format with a few expression
scripts
Asia Pacific Delimited style of import format was
implemented since data file loads
were manual. Two custom
expression import scripts were used
to map brand and entity
Delimited style was preserved and
modified to accommodate the new
dimensionality and the expression import
scripts were converted to JYTHON

22. Transformation - Entity Dimension
FDM Classic
 Data Warehouse scripts for the USA and Europe
dynamically determined the source entity based on the
following factors:
FDM USA Import Script
A. Does a cost center exist in the line item/record
B. If a cost center does exist in the record & it is
Explicitly mapped OR the cost center is mapped with a
LIKE map, then the cost center is the source entity
C. If a cost center exist but B does not apply, then the
cost center node is the source entity
D. If no cost center exists, use the profit center as the
source entity
 This was necessary because the cost center hierarchy
was within the entity hierarchy
FDMEE
 Data Warehouse scripts for the USA and Europe have
been removed
 Since the cost center dimension was removed from the
entity hierarchy and broken out in a separate dimension,
a simple field number import format is now being used
USA Import Script

23. FDM Classic Entity Script Details
 FDM Script Cost Center Entity Determination
 FDM Entity Cost Center Like Mapping Table

24. FDM Classic Entity Script Details
 FDM Script Profit Center Entity Determination
 FDM Entity Profit Center Entity Like Mapping Table

25. Example – Entity Import Result
FDM Classic
 Source entity 200_P31001 is determined by Data
Warehouse import script
FDMEE
 Entity mapping is simplified 1 to 1 mapping,
200 to US200

26. Transformation - Expression Scripts
 Import format expression scripts were modified using JYTHON. The majority of Levi’s
source files are derived from SAP. The load file example can be used as a guide for the
next two slides.
Example: Load File for Entity 258
Column 1 Column 2 Column 3 Column 4 Column 5 Column 6 Column 7 Column 8
Entity GL Account GL Account Function InterCo Profit Center Cost Center Amount
258 6720 672030 8 31001 2580831 55917.45
258 6720 672030 15 39001 2581508 1210.32
258 6720 672030 18 38001 2581826 60677.16
258 6720 672030 18 38001 2581827 85519.19
258 6720 672030 18 38001 2581836 34178.68
258 6720 672030 18 38001 2581837 95277.32
258 6720 672030 18 38001 2581838 92504.03

27. Expression Scripts
FDM Classic (VB)
 Script Name: BaanEntity.uss
 Purpose: If there is a cost center in the file capture
it as Entity, otherwise use company code
 FDM source entity result
FDMEE (JYTHON)
 Script Name: BaanEntity.py
 This is now used for the Cost Center dimension
since cost center and entity were split
 FDMEE source cost center result

28. Expression Scripts
FDM Classic (VB)
 Script Name: SAPBrand__GBR.uss
 Purpose: Use a combination of cost center “.”
and second digit of profit center to capture Brand
 FDM source Brand result
FDMEE (JYTHON)
 Script Name: SAPBRAND_GBR.py
 Only for Singapore
 FDMEE source Brand result
Same Logic

29. Transformation - Expression Scripts
 Import format expression scripts were modified using JYTHON. The example import file is
from a non SAP entity. The load file example can be used as a guide for the next slide.
Example: Load File for Entity 269
Column 1 Column 2 Column 3
Entity/Cost Center GL Account Amount
269 100000 165893.31
269 120000 651925.37
269 121000 -3894
0269CC101 675000 -2282
0269CC200 600490 0
0269CC200 610000 11737.58
0269CC200 610005 -81.22
0269CC200 610010 3202.04

30. Expression Scripts
FDM Classic (VB)
 Script Name: BaanAccount.uss
 Purpose: If cost center is non-numeric then
import account as is, if cost center is numeric,
then append a TB to the front of the account
 FDM source account result
FDMEE (JYTHON)
 Script Name: BaanAccount.py
 The new script does the same
 FDMEE source account result

31. DRM AND FDMEE
31
DRM
FDMEE

32. DRM Background
 DRM was implemented in Q4 of 2013 to manage cost
center and profit center hierarchies for Levi’s 17
Essbase cubes
 As part of the 2014 HFM upgrade it was agreed upon to
leverage DRM for the Brand and Cost Center
dimensions for FDMEE mapping

33. Benefits of DRM and FDMEE
 Benefits:
● Centralized hierarchy/change management
● Improved cost center and brand dimension data
alignment between Essbase and HFM
● Single source of hierarchies and properties

34. DRM Brand Mapping Setup
 The ProfitCenter_LSCO hierarchy is used as the basis
for exporting brand mappings to the SQL staging
tables.
 The staging tables are used for FDMEE mappings
Profit Center
Hierarchy

35. DRM Brand Mapping Setup
 In Levi’s instance of DRM, cost center placement in the hierarchy determines the
brand mapping
 In the example below, cost center C100087 has a brand description (BrandDescr)
of Levis
 BrandDescr is determined by the CCBrand via the GlobalBrandDescr lookup
table

36. DRM Brand Mapping Setup
 The GlobalBrandDescr lookup table is used to
determine brand for cost centers. Since the CCBrand is
10 the brand is Levis

37. DRM Cost Center Mapping Setup
 The ProfitCenter_Function hierarchy is used as the
basis for exporting cost center function mappings to the
SQL staging tables.
 The staging tables are used for FDMEE mappings
ProfitCenter_Function
Hierarchy

38. DRM Cost Center Mapping Setup
 In Levi’s instance of DRM, cost center placement in the ProfitCenter_Function
determines the functional category mapping
 In the example below, cost center C100087 has a function description
(CCFunctionCategory) of OPEXADV
 The cost center category OPEXADV is determined by the CCFunctionCategory
derived formula

39. DRM Cost Center Mapping Setup
 The CCFunctionCategory formula property references the property
LSCO.FunctionCategory and is used to determine the cost center to function
mapping
 If the node is a CostCenter and resides in the ProfitCenter_Function hierarchy,
then return the FunctionCategory hierarchy node property value. If the conditions
are not met, return “OPEXDIFF”

40. DRM Cost Center Mapping Setup
 As a result, the CCFunctionCategory is populated with the OPEX category assigned
in FunctionCategory property which is OPEXADV

41. DRM Cost Center Mapping Setup
 The FunctionCategory formula property determines cost center to function
mappings by looking at the ancestor of the cost center and derive relevant
properties
 If the node is a leaf and resides in the ProfitCenter_Function hierarchy, then look for
the ancestor with where the EPMA.Export = True. If the conditions are met, return
the EPMA.MemberName property of the ancestor. If the conditions are not met,
return <blank>.

42. DRM Cost Center Mapping Setup
 FunctionalCategory is assigned if the EPMA_Export is True
 If true return the EPMA Member Name

43. DRM Export to Staging
 External connection FDMEEStaging was created to be used for the following
exports:
 FDMEEStaging external connection detail
Export Name Description Target Table
FDMEE_GLBrand_Map_l exports branded and non branded GLAccounts SQL table Map_Brand_HFM
FDMEE_CC_Map_l exports cost center maps to SQL table Map_CostCenter_HFM
FDMEE_CC_Map_ll exports cost center maps to SQL table Map_CostCenter_HFM

44. DRM Export to Staging
 An export property called CCPCSQL_Export was created to filter for nodes that
should exported to the mapping staging tables

45. DRM Export to Staging
 An FDMEE_MAP_Export book was create to populate the SQL Staging tables
used for FDMEE brand and cost center mapping

46. DRM Staging Table
 The exports populate the Map_Brand_HFM and Map_CostCenter_HFM SQL
staging tables
Database Name

47. DRM Staging Table
 Database Columns within the staging tables are assigned by the exports FDMEE_CC_Map_l
and FDMEE_CC_Map_ll exports
 The target tab determines the column names

48. FDMEE Cost Center Mapping
 FDMEE SQL mapping script connecting to HYUSPXI01 database table
Map_CostCenter_HFM
 Map_CostCenter_HFM detail
DB name + staging table

49. FDMEE Brand Mapping
 FDMEE SQL brand mapping script connecting to HYUSPXI01 database tables
Map_CostCenter_HFM and Map_Brand_HFM
 Brand uses a combination of Map_Brand_HFM and Map_CostCenter_HFM to
map
DB name + staging table

50. LESSONS LEARNED
50
FDM
FDMEE
DRM
SQL/Jython

51. Lessons Learned
● Identify process pain points
● Maturing from IT centric to
Finance user centric
● Communicate with the entire
team throughout the project
● FDMEE Mapping - do not
under-estimate data
validation effort – TEST!
● Timeline – 7 months
(HFM+FDMEE), 2-3 months
for FDMEE
● DRM and FDMEE integration
● Data load rule for different
applications
● VB Script to SQL/Jython
● Train the trainer model –
regional super users
● FDMEE Excel Export (bug)
● Unable to lock POV (fixed in 520
patch)
● Limitation - Change target
application in FDMEE
51

53. Please complete the session evaluation
We appreciate your feedback and insight
Chris Chong – cchong1@levi.com
Joy Hsu – imjoyhsu@yahoo.com