below reply to your queries-
there a way to have multiple BefImport scripts (like we could do with regular Import scripts in Classic)...or can we somehow have multiple FDM applications (like in Classic) rather than them all being in one place? -- Yes Create the seperate locations and attach the same script that you have created to locations and restrict in seperate location the data only for particular Year or CostCenters.
You can see your validation errors by only pressing import. Is this a default setting or something you can turn off and go back to import and validating seperately? - Validation in fdmee is slightly different from FDM classic , In oder o check Validation is working or not go to particular fdm location and add explicit mapping instead of "*" and check.
let us know if that ok or you need more information.
We have successfully created two Jython scripts that grab data from 3rd party sql databases and populate the AIF tables and successfully import, validate and export. These are housed in the BefImport event script. Since we pull data from multiple source databases (EBS, HFM, Accpac, SUN, etc.), will our BefImport event script just keep growing as we add new connections and queries? Or is there a way to have multiple BefImport scripts (like we could do with regular Import scripts in Classic)...or can we somehow have multiple FDM applications (like in Classic) rather than them all being in one place?
You can only have one BefImport Script. If you are using Open Interface Adapter, you could also have separate ODI projects for each source so you don't need the BefImport.
FDMEE and FDM are different regarding integration scripts. In FDMEE, the integration script is replaced by either ODI process or BefImport Script.
There would be another option to have separate scripts. You can have 1 BefImport event script which calls external functions built in other scripts. In that way you could have BefImport_HFM.py, BefImport_EBS.py,... and the original BefImport.py. This last script would call the different functions in the other scripts based on your source.
Also, I have noticed that importing data into FDMEE seems to run the validation at the same time. You can see your validation errors by only pressing import. Is this a default setting or something you can turn off and go back to import and validating seperately? Not sure if I like or dislike but just want to know my options.
They are executed in one shot. You can then execute validate separately without import. But anytime you click Import, then Validate is executed.
You can add to your event script something like:
# Using an external library
except Exception, err: fdmAPI.logInfo("Error importing functions module:" + str(err))
functions is the name of the file (functions.py in event folder)
and then call your function:
Great thx Francisco. It worked. We were able to call a function in script 2 from script 1. We are now looking at our Before Import script and seeing that we will most likely need to pass the fdmAPI session from script 1 to script 2. The reason we say this is because we need to do an fdmAPI.execute DML statement to update the AIF table while looping through our recordset in script 2. A simple example of what we are talking about is shown below:
This would fail because Script2 doesn't have access to the fdmAPI session.
Thank you once again....your help is greatly appreciated.
Thx Francisco, however this isn't working for us.
When we run what you have provided, we get the error 'printTest() takes no arguments (1 given)'. Any ideas?
Would we not have to manually initialize the FDM such as mentioned in the Admin Guide (code below)? It doesn't seem like script 2 would know what FDMAPI is by just passing it as a parameter. Would we not need to add something like below to Script #2...or Script #1?
import java.math.BigDecimal as BigDecimal
import java.sql as sql
import com.hyperion.aif.scripting.API as API
fdmAPI = API()
conn = None
conn = sql.DriverManager.getConnection(r"jdbc:weblogic:sqlserver://servername:port;databaseName=db_FDMEE; loadLibraryPath=D:\Oracle\Middleware\wlserver_10.3\server\lib",username, password)
fdmAPI.logInfo("SUCCESS CONNECTING TO DB")
#fdmContext = fdmAPI.initContext(BigDecimal(1720))
We think we're close but we're stuck on this.
Any help is greatly appreciated.
Did you initially define printTest with no parameters.
That error is saying that you are passing one parameter and that was not expected.
your real issue is that your old function is loaded to the system path. If you change your second script after is added to the system path by 1st script, you will have to restart FDMEE service in order to add the 2nd script to
the system path again. Then your function with one parameter will be available and you can pass fdmAPI object to it.
So restart and it will work.