Creating a Planning Application Shell

  To create a Planning application shell:

  1. Launch Shared Services Console and log in as the user who is provisioned with the appropriate Lifecycle Management roles.

  2. In Shared Services Console, expand Application Groups and select a Planning application.

  3. In the Artifact List tab, complete the following steps:

    • Expand Configuration, Properties and select Application Definition.xapr.

    • Select the artifacts to migrate.

  4. Click Define Migration and enter the requested information in the Migration Wizard. When you get to the Migration Summary dialog box, click Save Migration Definition.

  5. Open the Migration Definition file. In the Options section, do the following:

    • Add an option to create an application shell:

      <optionInfo name="operation" value="create"/>

    • Enter these data source properties:

      • Datasource Name

      • Datasource Description

      • DB Type

      • DB Server

      • DB Server Port

      • DB Database

      • DB Connection URL (optional)

      • DB Username

      • DB Password

      • OLAP Server

      • OLAP Username

      • OLAP Password

      • Unicode Mode

    The following is a sample Migration Definition File showing the option to create the application shell and the data source properties:

    <Target connection="AppConnection1">
     <Options>
          <optionInfo name="operation" value="create"/>
          <optionInfo name="Datasource Name" value="PlanningDS"/>
          <optionInfo name="Datasource Description" value=“Planning App1 DS"/>
          <optionInfo name="DB Type" value="Oracle"/>
          <optionInfo name="DB Server" value="OraServer1"/>
          <optionInfo name="DB Server Port" value="1521"/>
          <optionInfo name="DB Database" value=“PlanningDS"/>
          <optionInfo name="DB Connection URL" value="jdbc:oracle:thin:@oraserver1.oracle.com:1521:ORCL" />
          <optionInfo name="DB Username" value="Ora User"/>
          <optionInfo name="DB Password" value="password"/>>
          <optionInfo name="OLAP Server" value="EssServer1"/>
          <optionInfo name="OLAP Username" value="admin"/>
          <optionInfo name="OLAP password" value="password"/>
          <optionInfo name="Unicode" value="true" />
     </Options>
</Target>

  6. Save the changes to the Migration Definition File.

  7. Execute the migration using the command line utility utility.bat found in EPM_ORACLE_INSTANCE/bin as follows:

    utility.bat <Migration Definition File Name>

Note:

The Application Name defined in the Migration Definition File and the Application Definition.xpad file must be the same.

Note:

The Planning application properties that are exported as part of the application are: Application Name, Application Description, Application Type (General, PSB, Sample), Shared Services Project, Calculation Module, Planning Instance/Cluster Name, Calendar Type, Time Period Prefix, Periods in Year, FY Start Year, FY Start Month, Weekly Distribution, Total Years, Multiple Currency, Default Currency, ValidForPlan1, Plan1Name, ValidForPlan2, Plan2Name, ValidForPlan3, Plan3Name, ValidForWorkforce, PlanWorkforceName, ValidForCapex, PlanCapexName and PSBWorkforceModel.

Tip:

To migrate a Planning application with security artifact, planning unit hierarchy, and user preference settings, create a blank application shell by selecting the Application Settings artifact; then, manually import the User Provisioning and Planning artifacts.