Keeping up with EPM Cloud

In the past, when data load jobs needed to be scheduled in EPM, there were two main options; Batches or EPM Automate scripts. Now however, there is a third option of the new Pipeline functionality which was released as part of the new Data Integration interface in June 2023. Pipelines are set to replace the existing Batch functionality currently available in Data Management, that will soon be decommissioned by Oracle. While it’s always exciting when Oracle release new functionality, it can be hard to keep up sometimes – this switch however is one that is definitely worth the effort! This blog will tell you all about the differences between the old Batch functionality, existing EPM Automate scripting and the new Pipelines, and why it’s worth making the switch to Pipelines as soon as possible. 1. Batches   Let’s start with Batches. If you’ve not used them before, Batches are defined and scheduled within data management and are a way to schedule a range of data management load ...

As I recently discovered when trying to upload an Application Snapshot from my client's Production environment to my client's Test environment, once an Application Snapshot gets too large you will receive the below error when attempting to upload the snapshot through your browser: The file I was attempting to upload was around 4GB but I am unsure of the official size limit for uploading files through your browser. However, as your application is used over time it will continue to grow and, before you know it, your snapshot size will have reached this limit (whatever it may be!) To get around this issue, we can use the EPM Automate command UploadFile. The UploadFile command is used to upload a file from your local computer to the PBCS server. The file being uploaded could contain data, metadata, other application artefacts or be an entire Application Snapshot backup. The syntax for using the UploadFile command in a batch file is as follows: Call epma...