• They don't have an impact on target application
• We can define a #SQL mapping to copy our target values into other source dimension values including the lookup dimension itself
• We can define the order in which the lookup dimension mapped

1. Source ERP account "10100" has been mapped to "Price"
2. "Price" has been copied to source HFM Account
3. Product has been mapped using source Product and HFM Account

1. Map HFM Account to SAP Account
2. Copy SAP Account to source SAP IFRS
3. Map SAP IFRS based on SAP Accounts

Let's see the workflow:

As you can see, we have now copied the SAP Account into another dimension rather than the lookup. That allows us to create our Explicit mappings using SAP accounts in a very easy way.

# Import Section
try:
fromxml.etree.ElementTreeimportiterparse
importcsv
importos
fdmAPI.logInfo("Modules successfully imported")
exceptImportError,err:
fdmAPI.logFatal("Error importing libraries: "%err)

# Get Context details
inboxDir=fdmContext["INBOXDIR"]
locName=fdmContext["LOCNAME"]
fileName=fdmContext["FILENAME"]
loadId=fdmContext["LOADID"]

# XML File
xmlFile=os.path.join(inboxDir,locName,fileName)
fdmAPI.logInfo("Source XML file: %s"%xmlFile)

# CSV file will be created in the inbox folder
csvFilename=fileName.replace(".xml",".csv")
csvFilepath=os.path.join(inboxDir,locName,csvFilename)

# To avoid blank lines in between lines: csv file 
# must be opened with the "b" flag on platforms where 
# that makes a difference (like windows)
csvFile=open(csvFilepath,"wb")
fdmAPI.logInfo("New CSV file: %s"%csvFilepath)

try:
# Writer
writer=csv.writer(csvFile,delimiter=';',quoting=csv.QUOTE_NONNUMERIC)
exceptException,err:
fdmAPI.logDebug("Error creting the writer: %s"%err)

• We just want to capture start tags so we only capture start event in iterparse
• We can include event in the for statement for debugging purposes (we can print how the XML file is read)
• Property tag returns the XML node name (<entity>...)
• Property text returns the XML node text (<entity>EastSales</entity>) 
• We know amount is the last XML tag so we will write the CSV line when it's found
• The CSV writer generates the delimited line from list of node texts (row)

try:
# Iterate the XML file to build lines for CSV file
for(event,node)initerparse(xmlFile,events=['start']):

# Ignore anything not being dimension tags
ifnode.tagin["data","dataRow"]:
continue

# For other nodes, get node value based on tag
ifnode.tag=="entity":
entity=node.text
elifnode.tag=="account":
account=node.text
elifnode.tag=="icp":
icp=node.text
elifnode.tag=="custom1":
c1=node.text
elifnode.tag=="custom2":
c2=node.text
elifnode.tag=="custom3":
c3=node.text
elifnode.tag=="custom4":
c4=node.text
elifnode.tag=="amount":
amount=node.text

# Build CSV row as a list (only when amount is reached)
ifnode.tag=="amount":
row=[entity,account,icp,c1,c2,c3,c4,amount]
fdmAPI.logInfo("Row parsed: %s"%";".join(row))
# Output a data row
writer.writerow(row)

exceptException,err:
fdmAPI.logDebug("Error parsing the XML file: %s"%err)

# ********************************************************************
# Replace source file in FDMEE tables
# ********************************************************************

# Table AIF_PROCESS_DETAILS
sql="UPDATE AIF_PROCESS_DETAILS SET ENTITY_NAME = ? WHERE PROCESS_ID = ?"
params=[csvFilename,loadId]
fdmAPI.executeDML(sql,params,True)

# Table AIF_BAL_RULE_LOADS
sql="UPDATE AIF_BAL_RULE_LOADS SET FILE_NAME_STATIC = ? WHERE LOADID = ?"
params=[csvFilename,loadId]
fdmAPI.executeDML(sql,params,True)

# Table AIF_PROCESS_PERIODS
sql="UPDATE AIF_PROCESS_PERIODS SET IMP_ENTITY_NAME = ? WHERE PROCESS_ID = ?"
params=[csvFilename,loadId]
fdmAPI.executeDML(sql,params,True)

# -------------------------------------------------------------------
# Add library path to sys.path
# -------------------------------------------------------------------
importsys
importos.pathasosPath

# list of jar files
listPBJdep=["pbj-pbcs-client-1.0.3-SNAPSHOT.jar"]

# Add jars
pbjDepPath=r"E:\PBJ\uber_jar"
# Debug
fdmAPI.logInfo("Adding PBJ dependencies from %s"%pbjDepPath)
forjarinlistPBJdep:
pbjPathJar=osPath.join(pbjDepPath,jar)
ifpbjPathJarnotinsys.path:
sys.path.append(pbjPathJar)
fdmAPI.logDebug("PBJ dependency appended to sys path: %s"%jar)

# -------------------------------------------------------------------
# Import section
# -------------------------------------------------------------------
fromcom.jasonwjones.pbcs.client.implimportPbcsConnectionImpl
fromcom.jasonwjones.pbcsimportPbcsClientFactory
fromcom.jasonwjones.pbcs.client.exceptionsimportPbcsClientException
importtime

try:
# Your code...    
exceptPbcsClientException,exPBJ:
fdmAPI.logInfo("Error in PBJ: %s"%exPBJ)
exceptException,exPy:
fdmAPI.logInfo("Error: %s"%exPy)

# -------------------------------------------------------------------
# Credentials
# -------------------------------------------------------------------
server="fishingwithfdmee.pbcs.em2.oraclecloud.com"
identityDomain="fishingwithfdmee"
username="franciscoamores@fishingwithfdmee.com"
password="LongliveOnPrem"

# Create client
clientFactory=PbcsClientFactory()
fdmAPI.logInfo("PbcsClientFactory object created")
client=clientFactory.createClient(connection)# PbcsClient
fdmAPI.logInfo("PbcsClient object created")

# Upload metadata file to PBCS Inbox
csvFilepath=r"E:\FDMEE_CC\FDMEE_CostCenter.csv"
client.uploadFile(csvFilepath)
fdmAPI.logInfo("File successfully uploaded to PBCS Inbox")

# Set PBCS application
appName="DPEU"
app=client.getApplication(appName)# PbcsApplication

# Execute Job to import new metadata (Cost Center)
result=app.importMetadata("FDMEE_Import_CC")# PbcsJobLaunchResult
fdmAPI.logInfo("Result: %s "%result)

# Check Job Status and loop while executing (may add timeout)
jobStatus=app.getJobStatus(result.getJobId())# PbcsJobStatus
fdmAPI.logInfo("Job status: %s "%jobStatus)
statusCode=jobStatus.getStatus()

while(statusCode==-1):
time.sleep(10)# sleep 10 seconds
jobStatus=app.getJobStatus(result.getJobId())# PbcsJobStatus
fdmAPI.logInfo("Job status: %s "%jobStatus)
statusCode=jobStatus.getStatus()

# Show Message
ifstatusCode==0:
fdmAPI.showCustomMessage("New Cost Centers added!")
else:
fdmAPI.showCustomMessage("Some errors happened! %s"%jobStatus)

• Kscope17 was a great event as always. It's a very good opportunity for us living on the other side of the pond. Meeting lot of people, partners, customers is always great. San Antonio was impressive. I spent one day visiting the city with my colleague Henri (The Finnish Hyperion Guy). We had sun and rain. And what do you when it's raining? Shopping! In addition, I got the "EPM Data Integration Top Speaker" award! That was awesome. I didn't expect it so I can only say thanks to all the community. 

• Heading to large family. This is an easy one: if all goes fine, next year we will be 2 more in the family :-)
• New apartment. I've been very busy assembling IKEA furniture. For those would would like visiting Malaga (Spain), we bought a new apartment for rental. Feel free to visit it!

• Configuration of UDA (Part 1, Part 2, Part 3)
• SAP HANA On-premises Integration (Part 1, Part 2, Part 3)
• SAP HANA Cloud Integration

• Source System with an ODI context assigned
• Source Adapter
• Source Period Mappings
• Import Formats
• Location and Data Load Rule

• Manually in ODI
• Data Server
• Physical Schema
• Context
• Generated in ODI from FDMEE
• Datastore for Table/View definition
• Package and Interface
• Scenario for the Import Format

• Migrating across environments. LCM doesn't migrate the ODI objects. Besides, you can't do a native ODI export/import. FDMEE has been designed to have the same ODI repositories' ID across environments so the export/import objects will fail.
• Apply patches. Some patches may require to re-import some default ODI objects for ODI. This will probably delete the objects you generated from FDMEE.
• Changes in Tables/Views. Think about adding a new column to a Table/View. You have to re-import table definition again, regenerate the package and interface, adjust the Import Format and regenerate the ODI scenario

1. Create a DB Link (Oracle)/Linked Server (SQL Server) from FDMEE database server to the source database server
2. Create a view in FDMEE database. This view has an additional column for the source database. It queries the source views using remote queries (Ex: OPENQUERY in SQL Server) which perform quite well as they leverage the source DB engine
3. Configure UDA in ODI
4. Configure UDA FDMEE
5. In addition to the required parameters, define an additional one for the column having the source database

• ERP data / Supplemental data
• Statutory accounts / IFRS16 accounts

1. DLR GL_DATA loads actual data in Replace mode for Entity NY, Period Mar-2019
2. DLR IFRS16_DATA loads actual data in Replace mode for Entity NY, Period Mar-2019

• User for GL data:IntegrationUser_INP_FDM
• User for IFRS16 data: IntegrationUser_IFRS16_FDM

1. Create the security classes in HFM: C4_INP_FDM and C4_IFRS16_FDM
2. Activate the security class for Custom4 (App settings in HFM metadata)
3. Assign the security classes to the Custom4 members: INP_FDM and IFRS16_FDM
4. Assign role Default to the global user so he shows up in the matrix below
5. Assign user access to the security classes

1. As a starting point, we load the GL data with Replace Mode. Data is loaded to Custom4 member INP_FDM


The HFM data form shows the right data being loaded:
2. After loading GL data, we input value 500 manually (Custom4 member INP):
3. Finally, we load IFRS data in Replace mode:

• If you run the data load rule manually, you can select Replace mode as there is no functionality to hide load methods. To avoid that issue, you can always have a BefLoad script which checks the export mode before loading data. 

• As you are loading with the global user, that's the user you see in the HFM Audit.
• The solution applies to many different requirements. For example, we had a customer with different security requirements at HFM scenario level. In that solution, we used global users at category level.
• Consider location security. If user A has access to location A, note that the HFM security applied will be the one for the global user and not for user A. Therefore, if user A tries to load data for an entity that he has not access in HFM but the global user has, then data will be loaded for that entity. As a good practice, I usually build a control when locations/data load rules are defined for unique entities. In this way, I prevent users loading data for other entities, especially when they can manipulate the source files :-)

• Get the HFM Process Management details (Review Level for the different phases)
• When Soft Close, be able to compare new data set against last data set loaded. That will monitor all data load changes
• Auto-map missing mappings so the workflow can be completed
• Auto-map for invalid HFM intersections and identify the CANNOT WRITE intersections (Soft Close)
• Keep audit in FDMEE so missing mappings and invalid intersections can be easily filtered in the Data Load Workbench
• Send email notification with detailed results 

• We get the HFM Process Management details before data is loaded into HFM
• We perform the data monitoring after data is loaded into HFM

• How to get the HFM Process Management details
• SQL Query to get data differences (new, updated, or deleted data)

# ***************************************
# ODI 12c Password Decrypter
# ***************************************

'''
	ODI 11g Code
	--------------------------------------------
	# Import ODI API class
    from com.sunopsis.dwg import DwgObject
	# Decrypt pwd
	connPwdDec = DwgObject.snpsDecypher(connPwdEnc)

	Execution in ODI 12c
	--------------------------------------------
	Traceback (most recent call last):
	File "<string>", line 529, in executeJythonScript
	File "\\WIN19\EPMSHARE\FDMEE/data/scripts/custom/odi12c_decrypy_pwd.py", line 20, in <module>
    connPwdDec = DwgObject.snpsDecypher(connPwdEnc)
	TypeError: snpsDecypher(): expected 2 args; got 1

	Cause
	--------------------------------------------
	Function (depecreated) is defined as:
	public static String snpsDecypher(String pPass, OdiInstance pOdiInstance)

'''

# Import libraries
fromoracle.odi.core.configimportMasterRepositoryDbInfo
fromoracle.odi.core.configimportOdiInstanceConfig
fromoracle.odi.core.configimportPoolingAttributes
fromoracle.odi.core.configimportWorkRepositoryDbInfo
fromoracle.odi.coreimportOdiInstance
fromcom.sunopsis.dwgimportDwgObject

fromcom.hyperion.aif.utilimportRegistryUtilCore
fromcom.hyperion.hit.registryimportDBTypeComponentImpl
fromcom.hyperion.hit.registryimportComponentType

# Encrypted password (you can get it from ODI SNP tables as you would do in 11g)
connPwdEnc="xxxxxxxxxxxxxxxxxxxx"

# Get MR Connection details
# ----------------------------
aifDbComponent=RegistryUtilCore.getAIFDatabaseComponent()
jdbcDriver=aifDbComponent.getPropertyValue("dbJDBCDriverProperty")
jdbcUrl=aifDbComponent.getJdbcUrl()
jdbcUserName=aifDbComponent.getUserName()
jdbcPwd=aifDbComponent.getPassword()
fdmAPI.logInfo("Jdbc Driver ->"+str(jdbcDriver))
fdmAPI.logInfo("Jdbc Url -> "+str(jdbcUrl))
fdmAPI.logInfo("Jdbc User -> "+str(jdbcUserName))
fdmAPI.logInfo("Jdbc Pwd -> "+str(jdbcPwd))

# Create MR/WR Info
# ----------------------------
workRep="FDMEE"
masterInfo=MasterRepositoryDbInfo(jdbcUrl,jdbcDriver,jdbcUserName,jdbcPwd,PoolingAttributes())
workInfo=WorkRepositoryDbInfo(workRep,PoolingAttributes())

# Create ODI instance
# ----------------------------
odiInstance=OdiInstance.createInstance(OdiInstanceConfig(masterInfo,workInfo))

# Decrypt password
# ----------------------------
connPwdDec=DwgObject.snpsDecypher(connPwdEnc,odiInstance)

# Log decrypted password
fdmAPI.logInfo("Jdbc Decrypted Pwd -> "+str(connPwdDec))

# Destroy objects
odiInstance.close()