Skip to main content

Create Staging Area

Important: Importing source and stage templates is mandatory for creating source system and staging area, respectively.

Note: All the steps described for creating the staging area are applicable for both SAP HANA and SQL Server databases.

To create staging area

  1. Select the Create Staging Area button in the Templates page. Enter the appropriate details.

    The Show Details option is disabled if only one version of the template is available. The scenario when more versions are available is explained in the Upgrade Version chapter.

  2. Select Save. Only after the save is successful, the Connection and Deployment tabs will be enabled.
  3. Go to the Connection tab and enter the appropriate details to connect to the staging database.
  4. If the application has an existing connection saved, you can select it using the Existing Connection drop-down menu.

  5. Select Test Connection to test if the connection can be established successfully. When the connection is successful, the connection details are saved successfully, irrespective of Save being selected.

  6. Use the Deployment tab to select the required objects and deploy them to the staging database. Refer to the Appendix for a list of database objects for Oracle E-Business Suite.

    Important: For SAP HANA as the staging database, you must run the virtual_source_tables.sql file placed in the SCT\Stage\HANA folder. Refer to the Set Up Staging Database in SAP HANA section in the Set Up Staging Database chapter.

    • Sync: Use the Sync option if you have made changes to database objects (tables, views, procedures, functions) by:
      • Directly modifying the object in the database.
      • Dropping and recreating the object with customizations.

      Perform the following steps:

      1. Select Sync in the Deployment tab to view differences between the database and template definition.
      2. In the Sync View panel, sync default and custom objects.
        • Default tab - Displays objects that are a part of the template.

        • Custom tab - Displays objects that are not a part of the template.

        The grid displays the following columns:

        • Name - Displays the object name.
        • Type - Displays the type of object. Click the header to group objects by type.
        • Status - Displays the status of the custom objects.
          • New - Objects that are not a part of the application.
          • Existing - Objects that are a part of the application.
          • Modified - Synced objects that have been modified in the database.
          • Deleted - Synced objects that have been deleted in the database.
          • Error - Objects that encountered an error during sync.
        • Category - Displays the supported categories for custom objects. Select the appropriate category to map the object or select None from the drop-down list. This is a required field to sync the selected objects.
        • Changes - Displays None to indicate no modifications, View to review the object definition, and Queued to indicate pending sync.
      3. Select Refresh to fetch the latest data from the database and update the table with the most recent changes.
      4. Filter the objects by:
        • All - Displays all deployed objects present in the database.
        • Modified - Displays all deployed objects that are directly modified in the database.
      5. Select View for each modified object to review a line by line comparison of the object definition. For new custom objects, this action only displays the database modifications.

      6. Select Delete to remove objects from the application that have been deleted in the database.
      7. Select only the required objects in the grid and then select the Include Dependencies checkbox if you want to sync dependents for the selected objects.
      8. Select Sync. The template object definition is overridden by the corresponding database definition, thus syncing the database with the management console.
      9. Syncing new or deleted custom objects requires a version upgrade which reloads the data, select Continue in the confirmation pop-up to proceed. The custom version is reflected in the Overview tab.

        10. Note: Directly synchronizing database changes in higher environments is not recommended due to potential environment mismatches. Instead, make the changes in the development environment and propagate them to higher environments using export and import processes.

      10. For source systems using the source-independent single data load job, the Customizations Detected pop-up displays. Select one of the following actions and then select Proceed:
        • Synchronize - This will override the current definition with the one from the underlying data services.
        • Preserve - This will deploy the current definition to the data services and to all other instances associated with the same DI Server.

      Perform the following steps to undo the most recent sync and revert to a previous sync definition:

      1. In the Deployment tab, select the Revert action for the synced objects.

      2. In the Synced Definitions panel, select View for each object to compare the definitions.
      3. Select the required objects and then select:
        • Revert - to revert to a previous sync definition.
        • Revert to Template - to revert the object definition to template definition.

        Note: Tables, synonyms, and procedures are not supported for revert. However, reverting synced tables can be supported by enabling a flag in the appsettings file.


      4. If the selected object is a table, a warning will prompt you to confirm whether the table can be dropped. Select Continue.
      5. A success message for revert completion displays.

        Note: The revert operation is only finalized once the object has been redeployed.

    • Compare: Use this option to compare definitions for reconciled objects.
    • Generate Scripts: Use the Generate Scripts option to customize and download scripts in the .sql format. This gives you an option for traditional installation if the use of Management Console is restricted.

      The scripts are downloaded as a zip file which contains a batch file along with a sql script for the source system.

    • Deploy: Select the objects and select Deploy to run the object definition to the configured database. It then updates the object status from Queued to Deployed/Error based on the response.
    • Show Logs: Use Show Logs to display all the logs pertaining to the deployment feature. The deployed object status, name, any details, and date and time of the deployment are displayed.
    • Include Dependencies: Select a few objects and then select the Include Dependencies checkbox to select all the dependent objects of the initially selected objects. Use this feature to select all the dependent objects if there is a lack of clarity about the dependencies.

Note: Downgrading to a previous version is not supported.

Was this article helpful?

We're sorry to hear that.