by Doug Correa | 10 23, 2015 | EPM, FDM, FDMEE
Tip 5 – Scheduling a Job with Batch Processing Anyone familiar with FDM Classic knows the power of Batch Loader. Batch Loader is used to automate data loads. With FDM Classic, you had to use the Windows clients, FDM Workbench and FDM Task Manager, to create and schedule batch jobs, respectively. With FDMEE, setting up and executing a batch job is way easier. You simply use the Batch Definition component to build your job and then you use the Batch Execution component to execute and/or schedule the batch. That’s it. ...
by Doug Correa | 10 23, 2015 | EPM, FDM, FDMEE
Tip 4 – Using Lifecycle Management Want to save a file back up of FDMEE for disaster recovery purposes? Need to synchronize your FDMEE apps across environments? FDMEE makes this easy with Lifecycle Management. Lifecycle Management – commonly referred to as “LCM” – provides a mechanism for migrating application content across environments and even operating systems. You can access Lifecycle Management via Shared Services. In Shared Services, navigate to your FDMEE application. Select your FDMEE application to display a list of migration artifacts. Choose your artifacts and click the Export button to name and generate your LCM package. When the export is complete, your LCM package (a collection of XML files) will appear in the File System group in Shared Services. From there, you can download the LCM zip file to a network share. ...
by Doug Correa | 10 23, 2015 | EPM, FDM, FDMEE
Tip 3 – Downloading Metadata Using the Excel Interface Let’s face it. Analyzing data in an application interface can sometimes be cumbersome. Sometimes it’s just easier to do it in Excel. FDMEE comes with a rich reporting framework that allows you to export data to PDF and Excel. But occasionally you’d rather dispense with all of the reporting formatting and just have the data. Or, maybe there isn’t a report for the exact thing you want to review. Enter the Excel Interface component. Using the Excel Interface component you can download just about any metadata item in FDMEE. The Entity Type drop down list (yes, it’s a weird name) gives you a pre-defined list of objects you can download to Excel. Go to Setup > Integration Setup > Excel Interface and try it out. ...
by Doug Correa | 10 04, 2015 | EPM, FDM, FDMEE
Over the past month, Oracle has released a couple of key patch set exceptions (PSEs) for FDMEE 11.1.2.4, PSE 21444040 and PSE 21819491. What are Patches? A patch is a small collection of files copied over an existing software installation. There are 4 types of patches – Patch Set Exception (PSE), Patch Bundle, Critical Patch Update (CPU), and Patch Set Update (PSU). Oracle provides infrastructure resources with the “OPatch Utility for applying interim patches. For more information about how patch types differ and how they are applied, see Fusion Middleware Patching Guide. The attached screenshot below shows a breakdown of the defects fixed in FDMEE 11.1.2.4 PSEs 21444040 and 21819491. Right away, you can see that 9 out of the 10 fixed defects address issues with HFM. No surprise there. HFM Release 11.1.2.4 was re-written from the ground up to achieve independence from the Microsoft platform. (For details on the new HFM, see Henri Vilminko’s post, Say Hello to HFM 11.1.2.4.) So, if you’re using FDMEE with HFM Release 11.1.2.4 you almost certainly want to apply these patches. Additionally, if you’re in this camp you absolutely want to install two patch set updates to HFM 11.1.2.4, PSU 100 and PSU 101. Both patch set updates fix a major number of defects in HFM. If you’re implementing FDMEE 11.1.2.4 or your company is already live on 11.1.2.4, please pass along feedback. The Oracle development team relies heavily on user feedback to improve the...
Recent Comments