Create, Edit, and Monitor Replication Packages

Replication Package Guidelines

• Security replication packages must be executed sequentially as parallel execution is not supported.
• Static tables such as FND Calendar public view objects (PVOs) or FLEX PVOs must not be combined with regular PVOs in the same package, as incremental loads are not supported for these tables.
• Replication packages that contain static tables cannot have the scheduler enabled for incremental loads.

Create or Edit a Replication Package

To create or edit a replication package, sign in to Angles Hub and perform the following:

1. Select Replication. The Replications page is displayed.

2. To create a new replication package, select Create Package.

   To edit a replication package, select the ellipsis icon of the replication package you want to edit. A dropdown menu is displayed. Select Edit Replication.

   The replication page is displayed. Following tabs are displayed:

   1. Information

   2. Scheduler

   3. Configuration

   4. Content

    

   Important: A question mark icon is available on each tab to display guidance on what information is required for that step.

3. On the Information tab, enter the replication name and an optional description. Select the Source Connection (the system where the data originates), the Target Connection (the destination where the data will be replicated), and the Target Schema (the schema within the target system where the data will be stored).

   If the source connection is Oracle Cloud Applications (OCA), enable the Enable Security Packages option to include security-related data in the replication, then select Next.

   Note: When Enable Security Package is selected, the source schema is set to External in the Configuration tab, and only security-specific PVOs such as Business Unit and GL Segment are available for selection.

4. On the Scheduler tab, enable the scheduler to allow the replication package to run automatically based on a defined schedule. If the scheduler is not enabled, the package will need to be triggered manually each time.

   • The Replication System Clock displays the current time settings of the replication server. All scheduled times are based on this clock, so it is important to review these settings before configuring a schedule to ensure replication runs at the intended time.

     The following details are displayed:

     • Time Zone: Indicates the time zone configured on the replication server, such as (UTC) coordinated universal time.

     • Display Name: Indicates the full name of the configured time zone, such as UTC.

     • UTC Time: Indicates the current date and time in UTC.

     • Replication Local Time: Indicates the current local time on the replication server.

     • Offset (Minutes): Indicates the difference in minutes between the server time zone and UTC.

     • Daylight Saving: Indicates whether daylight saving time is currently active for the configured time zone.

      

   • Select Scheduler to configure the schedule and provide the following details.

     The available fields vary based on the frequency selected. Only the fields relevant to the chosen frequency will be displayed.

     • Frequency: Indicates how often the replication runs. Options include Hourly, Daily, Weekly, and Monthly.
     • Time: Indicates the specific time at which the replication should run.
     • Every N hours: Indicates the interval between runs when the frequency is set to Hourly. For example, selecting Every 1 Hour runs the replication every hour.
     • Minutes: Indicates the minute within the hour at which the replication starts.
     • Day: Indicates the specific day on which the replication should run.
     • Repeat: Indicates the days on which the schedule repeats, such as every day or weekdays (Monday to Friday).
     • Exclusion Window: Indicates whether scheduled runs should be skipped during night hours. Useful for avoiding replication during off-peak or maintenance windows.

   Alternatively, select CRON Expression to define the schedule using a cron expression directly. This is recommended for advanced scheduling requirements (for example, every 15 minutes between 8:00 AM and 6:00 PM on weekdays only, or at 11:59 PM on the last day of every month). The generated CRON expression is displayed at the bottom of the screen, reflecting the current scheduler settings.

   Note: The Update Schedule option allows the schedule to be updated without triggering initialization or a full load, which is useful when only schedule-related changes are needed without altering the rest of the package configuration. This option is only available when editing an existing package and will not be visible during package creation.

5. On the Configuration tab, select the source schema (which contains the tables to be replicated) and select the tables you want to replicate to the target, then select Next.

6. On the Content tab, review the schema and table overview to confirm the selections and select Save Package.

   Note: To refresh a single table independently without triggering a full load for the entire package, enable Custom Table Refresh, select the desired table, and click Refresh. This option is only available when editing an existing package and will not be visible during package creation.

Initialize and Manage Replication Packages

To initialize and manage a replication package, sign in to Angles Hub and perform the following:

1. Select Replication. The Replications page is displayed.

2. To perform a full load, select Initialize for the replication package you want to initialize.

   Note: If needed, the initialization can be paused at any point during the process by selecting Pause. To continue from where it was paused, select Resume. These options are available only when the scheduler is enabled.

3. To perform an on-demand full load on an already initialized package, perform the following:

   1. Select Pause to pause the package.

   2. Select the ellipsis icon and select Full Replication Refresh from the dropdown. The full data load is performed again.

      Note: The Full Replication Refresh option is available for both scheduler-enabled and scheduler-disabled packages, once the initial full load is successfully completed. Security packages always perform a full load, regardless of the CDC settings.

    

4. To perform an on-demand incremental load, perform the following:

   1. Select Pause to pause the package.

   2. Select the ellipsis icon and select Incremental Replication Refresh from the dropdown. Only the changed (CDC) records since the last run are replicated to the target.

      Note: The Incremental Replication Refresh option is visible only when a scheduler (cron expression) is enabled and the initial full load is successfully completed. It is not available for packages with the scheduler disabled.

    

5. To edit or delete a replication package, select the ellipsis icon of the required package. A dropdown menu is displayed.

   1. Select Edit Replication to edit the replication package.

   2. Select Delete Replication to delete the replication package.

    

View Logs

To view replication logs, sign in to Angles Hub and perform the following:

1. Select Replication. The Replications page is displayed.

2. Select View Logs for the replication package you want to view replication logs. The logs page is displayed with the following details:

   1. The logs can be filtered by From Date, To Date, and Status to narrow down the results. A Search option is also available to look up specific log entries. To retrieve the latest log entries, select Refresh Logs. To fetch the complete log history, enable the Fetch All Logs option.

   2. The log entries are displayed in a table with the following columns:

      1. Log: Indicates the type of log entry, such as Info, Warning, or Error.

      2. Detail: Indicates a description of the log event, such as the status of the replication job or any actions performed.

      3. Date: Indicates the date and time at which the log entry was recorded.