Deploying an Enterprise Journal Template

After you create an Enterprise Journals template, you can deploy it to a pending or open Journal Period. You can also redeploy a previously deployed template.

Deploying Enterprise Journal templates creates recurring journals associated with the template for the selected period. It also allows you to create Ad Hoc journals using the deployed template(s).

Note:

Redeploying the template due to changes in the approval paths for ad hoc users won't affect the workflow of existing journals, which are already in progress.

To deploy a journal template, you must be a Service Administrator or Power User.

You can also deploy a journal template using the EPM Automate deployEJTemplates command. See Working with EPM Automate for Oracle Enterprise Performance Management Cloud.

To deploy a journal template:

  1. On the Home page, click Application, and then click Enterprise Journals.
  2. Click the Journal Templates tab on the left.
  3. From the Actions menu, click Deploy.
  4. From Journal Period, select the period to which the journal will be deployed and click OK.
  5. Click Deploy.
  6. The Deploy Information dialog is displayed that shows all the journals related to the period.
    • The following options are available:
      • Create- Displays a count of all journals which will be created during deploy and re-deploy.

      • Reset - Displays a count of all journals which will have their workflow reset to Preparer (clearing any updates to questions or attributes). Any data entered into the journal will be retained only if there are no changes to key attributes.

      • Refresh - Displays a count of all the journals that will be refreshed based on the changes made to the journal template. Any change in the properties of the template attributes (such as default value, formatting, calc, validation) will be reflected on the journals.

      • Delete - For Un-deploy and Re-deploy, displays a count of all journals that will be deleted.

    • On a redeploy, when there are any changes to the template:

      • Reset: When you change any property on a template except adding new recurring Journals, the Reset option:
        • Displays a count of all journals which will have their workflow reset to Preparer
        • Any data entered within the journal header or detail sections will be retained
        • Questions will be updated and any answers will be cleared
        • Any comments will be deleted
      • Refresh: When you complete editing the template attributes and the attribute properties have changed, the Refresh option:
        • Will update the journals with the latest formatting properties for the attributes, validations and calculations
        • Instructions, Questions, and Comments will be retained
    • If you are redeploying a journal template, the system displays these options:

      • Reset all workflows - If you select this option, any data entered in the journal will be retained, but all other workflow items, such as comments, will be reset. If you have made changes to the key attributes (add, remove, edit), existing data is also deleted.
      • Delete Ad-hoc Journals – If you select this option (default), any user created ad-hoc journals will be deleted. If you have not selected this option, any user created ad-hoc journals will be refreshed or reset.
  7. Click Deploy.
  8. From the Deploy confirmation prompt, click Yes.
  9. After the deployment is completed, a confirmation dialog box indicates the total number of journals successfully deployed.
    For journals that were unsuccessfully deployed, the names are displayed with the error information.

    Note:

    Delete of recurring journals: Redeploying the journal template for a journal period is successful as long as at least one journal is not in posting status "post in progress" or "posted" for a particular period. If a journal is already posted for a journal period, redeploying the template gives an error that "Journal is already posted so journal template cannot be redeployed". Recurring journals that are force closed can be deleted by redeployment process, as long as no journals are successfully posted to the same journal period.