Adding systems

AD
DM

A system is one of the following:

  • Data source - A source system that Network MDM receives data from. Network MDM relies on various data sources to provide verified, reliable records and relationships.

    When you define a system, you determine the treatment of data from this source. In addition to determining the visibility and usage data from the source, you can also define a source as a third-party data provider.

  • Downstream system - A system that receives data from Network MDM.

Anytime data is loaded into Network MDM or sent from Network MDM, a system must be defined.

Third-party systems

If the data will be mastered by a third-party data provider, add a third-party master system . For details, see Add third-party systems.

Add a system

  1. In the Admin console, click System Interfaces > Systems.

  2. Click Add System.

  3. Type a Name and Description.

  4. Type - Identify the system as one of the following types:

    • Concur®
    • Custom (default)
    • Veeva CRM
    • Veeva Nitro
    • Veeva Vault

  5. Icon - Add an icon to help identify the system (optional).

    Click Select Icon and choose an icon from the library.

  6. Proprietary or Restricted - These settings apply to locally managed data. Select the setting if it applies to the data for this system.

    • Proprietary

      The proprietary flag applies to data change requests only. Defining local data as proprietary ensures that add and change requests that are submitted through the Network MDM API will not be sent to Veeva OpenData.

      Proprietary settings are tracked by system rather than field.

      For more information about the behavior of proprietary data, see Sources of data.

    • Restricted

      When a system is defined as restricted, data loaded from that system cannot be viewed in data lineage. The field values that were loaded by the restricted source system are hidden so users cannot see and compare the values between the sources that contributed to the record. This protects data agreements with third-party vendors.

      If this setting value is No, restricted data is treated like regular (non-proprietary) data.

      For more information about the behavior of data for restricted systems, see Sources of data.

  7. Third party master - Select if the data will be externally managed and stewarded by a third-party data provider.

    Note: This only applies if DCRs should be routed to a third party for external resolution of the DCRs.

    When this setting is selected, the following behavior occurs:

    • Record ownership - Records loaded using this system will be owned by the third-party master. In the Network MDM UI, third-party master data is identified by blue icons and fields.

    • Data change requests (DCRs) - Changes to data are assigned to this system within Network MDM. DCRs must be exported to the third party using the API or a target subscription.

      Changes are never routed to Veeva OpenData or to local data stewards for processing.

    If the source is a third-party master, additional configuration settings are required. See Add a third-party master system

    Note: Systems that are not defined as a Third Party master are considered local. Updates to local data are sent to customer data stewards for processing.

    For more information about the behavior of third-party mastered data, see Integrating with third-party systems.

  8. Unmerge ability - Set the desired behavior when unmerging records for this system.

    • Unmerge and retain source keys - Unmerge records by copying everything, including the source keys, from the record.

      This the standard behavior for systems that support unmerge.

      Note: Unmerge can only restore affiliations that were loaded with a custom key.

    • Do not unmerge - Do not allow records for this system to be unmerged.

    • Unmerge without source keys - Unmerge records by copying everything except the source keys from the record.

    Considerations for CRM systems

    This option must be set to Do not unmerge (do not allow unmerging of records) or Unmerge without source keys (which effectively unmerges records by copying everything except the source keys from the record).

  9. Save your changes.

When you load or export data, select this system so these settings are applied to the data.

Rank the system for source survivorship

New systems are added to the Source Rankings page without a rank. Rank the source to define its trust level for source survivorship when records and fields are updated or merged.

Unranked sources are treated lower than any ranked source, but they are treated equally among themselves.

Note: Not required for third-party master systems. The third-system supersedes all sources for a country.

For more information, see Configure source rankings.

Viewing systems

All defined systems display on the Systems page (System Interfaces).

You can sort the systems using any of the columns in the table. If you sort the systems, the order of systems is retained for you the next time you access the page.

Tip: For systems that are rarely or no longer used, assign a "Z" to the description so those systems remain at the bottom of the list.

Job Impact Dashboard

After a system is created and is used to load data, you can click the Job Impact Dashboard button to understand the records that have been added or changed by subscriptions used by the system.

Filters

When the Job Impact Dashboard opens, the following filters are automatically applied:

  • Subscriptions - Subscriptions used by the system to load or change data.

    For example, source subscriptions, data maintenance subscriptions, and Data Updater jobs.

  • Time Period - Last 7 days.

  • Start Date - The date seven days ago.

  • End Date - Today's date.

For detailed information, see Job Impact Dashboard.