Create and Manage Public View Objects (PVOs)

A Public View Object (PVO) is a metadata representation of a data table from Oracle Cloud Applications (OCA) stored in Angles Hub. PVOs serve as the foundation for data replication to target databases in Angles Hub. They can be customized (for example, excluding columns, adding prefixes, or modifying primary keys), refreshed to reflect source system changes, and uploaded back to synchronize customizations with the source system.

To create Public View Objects (PVOs), sign in to Angles Hub and perform the following:

2. Select Connection Manager. The Connections page is displayed.
2. Select the dropdown icon next to the Oracle Cloud Applications (OCA) connection for which you want to add a PVO, and select Manage PVOs. The Manage PVOs page is displayed.

3. Select Actions and select one of the following options:

   1. Add PVO: To add a single PVO, select Add PVO, provide the following details, and select Extract Metadata.

      1. Data Store Name: Enter the name of the subject area or analytics module as it appears in your Oracle Cloud Applications (OCA) environment. For example, Oracle Financial Analytics or Business Analytics.

      2. Table Name: Enter the name of the specific table within the data store that you want to extract and replicate to the target. This is the actual table name as it exists in the OCA environment. For example, Customer Account or Customer Name.

      3. Prefix: Enter an optional prefix to be added to the table name in the target database. This Manage PVOs is useful to differentiate or categorize tables when they are replicated to the target schema. For example, AP (Accounts Payable) or GL (General Ledger).

      4. Offerings: Select the specific subset or product within the selected module from which you want to extract PVOs.

      5. Modules: Select the functional area or category within Oracle Cloud Applications from which you want to extract PVOs.

      6. Schema: Select the schema where the data needs to be stored.

      Clicking Extract Metadata retrieves the PVO metadata from OCA and stores it in the Hub. The PVO details are persisted in the PublicViewObject table and column metadata in the PublicViewColumn table of the OCA Data Management service.

   2. Add Bulk PVO: To add multiple PVOs at once, select Add Bulk PVO, provide the following details and select Extract Metadata.

      1. Offering: Select the specific subset or product within the selected module from which you want to extract PVOs.

      2. Ship Content: When Ship Content is selected, the shipped (default) PVO metadata without any customizations is extracted from OCA for all PVOs in the selected offering. When unchecked, the customized PVO metadata—including custom columns, modified primary keys, and other OCA-level customizations—is extracted for all PVOs in the selected offering.

   3. Bulk Upload: To bulk upload the customized PVOs, select the required PVO configurations from the list, then click the Actions dropdown menu and select Bulk Upload to export and sync them to OCA in one operation. This operation uploads customized PVO metadata for multiple PVOs from Angles Hub to OCA.

   4. Bulk Refesh: To bulk refresh the PVOs, select the required PVO configurations from the list, then click the Actions dropdown menu and select Bulk Refresh to reload and update them from the source data model in one operation.

      This operation retrieves the shipped PVO metadata from OCA for multiple PVOs and updates the corresponding metadata in Angles Hub.

Modify PVOs

To create Public View Objects (PVOs), sign in to Angles Hub and perform the following:

2. Select Connection Manager. The Connections page is displayed.
2. Select the dropdown icon next to the OCA connection for which you want to add a PVO, and select Manage PVOs. The Manage PVOs page is displayed.

Under Actions, select the edit icon of the PVO you want to edit. A page with the following options is displayed:

1. Overview: Make the required changes and select Save.

   • Table Name: Indicates the name of the PVO being configured.

   • Schema: Indicates which database schema contains the PVO.

   • DataStoreName: Indicates the complete path/location of the PVO in the data model.

   • Description: Indicates what the PVO is used for (documentation/purpose).

   • Prefix: Indicates an optional prefix to be added to PVO field names.

   • IsEffectiveDateDisabled: Indicates whether date-based versioning of PVO records is turned on or off.

   • PVOType: Indicates the type of PVO, such as Standard, Custom, or Extended.

   • Modules: Indicates which functional modules, such as XLA, GL, or AP, this PVO applies to.

   • Offerings: Indicates which product offering, such as FIN, HCM, or SCM, this PVO belongs to.

   • Grouping: Indicates which ledger level, such as XL1 or XL2, this PVO is grouped under.

   • Customization Type: Indicates whether the PVO has custom modifications applied, such as None, Custom, or Extended.

   Click the Upload button to export the customized PVO configurations to OCA.

2. Columns: Use the Columns tab to view and manage the fields in the PVO. The tab displays a list of all columns with their name, description, and data type. For each column, you can designate its role in the PVO.

   Select Primary Key to mark a column as a primary key, or select Exclude Column to prevent a column from being processed during PVO operations.

   Click Save after making the required changes.

   Click the Upload button to export the customized PVO configurations to OCA.

3. Indexes:

   Indexes are database structures that organize and filter your data by specific columns and conditions to improve query performance and speed up data retrieval. Use the Index tab to view and manage indexes for your PVO. The Index tab displays all indexes with their name, columns, and filter conditions applied. You can update, enable, disable, or drop indexes without interrupting replication. When you create an index, it is created in the target database after the replication task completes and the data is successfully loaded to Snowflake or OADW. During each replication run, Angles Hub automatically disables indexes before insertion for faster data loading, then re-enables them after replication completes. Any changes you make to indexes after replication is done, such as updates or drops, will be handled during the next replication run without requiring manual intervention or stopping replication.

   To add an index, perform the following:

   1. Select Indexes > Add Index. The Create Public View Index window is displayed.

   2. In Index Name field, enter a descriptive name to identify your index.

   3. A Column Name dropdown is displayed. Select the column you want to include in the index from the available options. You can add multiple columns by selecting Add Column again for each additional column.

   4. To remove a column, Select the red delete button in the Action column.

   5. To filter the data in your index, select Add Condition. A condition row is displayed.

   6. Provide the following details:

      • Column: Indicates the column you want to filter on from the dropdown.

      • Operator: Indicates the comparison operator (for example, equals, greater than, contains) from the Operator dropdown.

      • Value: Indicates the value to filter by in the Value field.

      • Next Condition: If you are adding multiple conditions, select how conditions should be combined:

        • AND: Select this to require that ALL conditions must be true. For example: "Column A equals X" AND "Column B equals Y" returns records where both conditions are met.

        • OR: Select this to require that ANY condition can be true. For example: "Column A equals X" OR "Column B equals Y" returns records where at least one condition is met.

        • No Condition: Select this if this is your only filter or you have added all necessary filter conditions.

          To add another condition, the next row will appear automatically. To remove a condition, click the red delete button in the Action column.

      Repeat this step for each additional filter condition you want to apply.

   7. Select Save to create the index.

To delete an index, click the ellipsis icon under the Action column and select Delete from the pop-up menu. The system will then display options based on whether the index has already been created in the target database. If the index is already created in the target database, select Mark it for Drop. The index status will change to Pending drop and will remain visible on the index page until the next replication run. During the next replication run, the index will be dropped from the target database. Once replication completes, the index will be automatically deleted from the UI. If the index has not yet been created in the target database, selecting Delete will immediately remove the index from the index page without requiring a replication run.

Edit, Upload, Refresh, and Delete PVOs

To edit, upload, refresh, and delete a PVO, sign in to Angles Hub and perform the following:

1. Select Connection Manager. The Connections page is displayed.

2. Select the dropdown icon next to the Oracle Cloud Applications (OCA) connection for which you want to manage a PVO, and select Manage PVOs. The Manage PVOs page is displayed.

3. To edit a PVO, select the required PVO and select the Edit icon in the Actions column.

4. To upload a customized PVO to OCA, select the required PVO from the list and select the Upload icon in the Actions column. This uploads the customized PVO metadata from Angles Hub to OCA and updates the corresponding PVO definition in Oracle Cloud. For example, if a PVO initially contains 50 columns with 1 primary key, and you customize it in Angles Hub by excluding 10 columns and modifying the primary key configuration, clicking Upload will push these customizations to OCA, ensuring the PVO metadata in Oracle Cloud remains synchronized with your changes in Angles Hub.

5. To refresh a PVO and reflect the latest changes from the source data model, select the required PVO and select the Refresh icon in the Actions column. Clicking Refresh icon retrieves the shipped PVO metadata from OCA and updates the corresponding PVO metadata in Angles Hub, replacing any previous customizations with the default definition. This is useful when you need to restore a PVO to its original state.

6. To remove a PVO from Angles Hub, select the required PVO and select the Delete icon in the Actions column.