Skip to main content

Create Source System

Important: You must run the user or database creation scripts before configuring an instance in the Management Console. For example, for Oracle E-Business Suite, run the script at <SetupFolder>\Transaction Replication 9.0\SourceConnect 9.0 Management Console\Prerequisites\EBS\Scripts\DB_Script_Auto.sql with appropriate inputs.

This section describes the procedure of creating a source system.

To create a source system

  1. On the Templates page, select Actions > Create Source System. 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, Deployment, and Data Pipeline tabs will be enabled.
  3. The Connection tab allows you to enter all the required details to connect to the source or stage database. Enter the appropriate details. Some fields are mandatory, while others are optional. When the optional fields are left blank, certain database objects that rely on these fields will be skipped during deployment. This setup allows you to install specific functions as needed, providing moderated access and eliminating the requirement for full-access source system suite credentials. Note that this may limit access to features like SyncBack, Drilldown, and AVL.

    The following screenshot displays details for the Oracle E-Business Suite source system. You can either select Direct to enter the server details manually or select TNS to choose any of the TNS values from the drop-down menu. The available fields vary depending on the source system.

    To connect to Oracle NetSuite, complete the ODBC configuration with the following required fields:

    • DSN: Select a NetSuite-specific connection from the dropdown list.
    • User Name: Enter the user name.
    • Password: Enter the password.

    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.

    The Existing Connection drop-down menu appears only if the application has saved connections, allowing you to select an existing connection from the list for use.

    If you save the connection without entering the optional fields, the following pop-up displays. Click Save to proceed.

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

    Note: The database objects that were skipped due to the optional fields being left blank in the Connection tab display the Skipped status. These objects may need to be deployed later with the assistance of a Database Administrator (DBA) to ensure full functionality.

    • 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.

    • Logs: Use 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.

  5. Go to the Data Pipeline tab. You can use this tab to deploy all the ETL projects into the SAP Data Services from the Management Console.

  6. To download one or more projects, select the project(s) and then select Download. The Download option acts as an alternative for deploying the ETL projects into the SAP Data Services. The scripts are downloaded in zip format. You have the option to directly import scripts into the SAP Data Services if you so desire.

  7. Select a Data Integration Server and then select Save. The other options become available only on a successful save.
  8. Select Sync to apply any changes made in SAP Data Services, such as adding or modifying a datastore, to the application. The Sync View panel retrieves the entire project hierarchies from the repository associated with the linked Data Integration Server. Note that no hierarchy is displayed in the table for ETL projects or components with a status of New. The hierarchy will be updated only after they are synced to the application. For more details, refer to the Sync function documentation above.

    Note: The Passphrase column is required to sync project-type objects.

  9. Select one or more projects that you want to deploy to SAP Data Services, enter the passphrase that was used when the project was exported, and select Deploy.

  10. If successfully deployed, you can then select the Datastore Configuration option to deploy the datastores from the Management Console. The Datastore Mapping Configuration window appears.

    Note: The data stores hold the connection details required for running the jobs during data transfer.


  11. On selecting the info icon for a datastore, you can view all the projects and jobs that are utilizing the datastore.
  12. Select the Aliases option to configure an alias value that can be utilized while running the jobs.
  13. Select the Connection that you want to map to your datastore(s) and select Deploy.
  14. The data stores are successfully deployed implying that the connections are updated in the underlying SAP Data Services. When the jobs are triggered in future, the updated connection details will be used for those jobs.

Note: Downgrading to a previous version is not supported.

Was this article helpful?

We're sorry to hear that.