Defining profiles

In general, profiles need to be defined by the enterprise (organization) that owns the data in the TableGroup for which the profile is being defined.

For example, consider the following scenarios:

  • Simple scenario – If you have an enterprise (E1) that owns the configuration data and also acts as the pricing organization and catalog organization, E1 would create profiles for all TableGroups that it wants to synchronize to an offline environment. If E1 wants all TableGroups to synchronize to an offline environment, it would create profiles such as for the Catalog, Category, CatalogSetup, PriceList, PriceRule, User, Entitlement, Approval, Validation, and Configuration TableGroups. In addition, the DEFAULT organization would create profiles for the Hub, User, and Configuration TableGroups.
  • More complex scenario – If you have an enterprise (E1) that has P1 as its pricing organization and C1 as its catalog organization, and all three enterprises have users defined, profiles would be created such as follows:
    • E1 would create profiles for the Configuration, User, Approval, and Validation TableGroups.
    • C1 would create profiles for the Configuration, User, Catalog, Category, CatalogSetup, and Entitlement TableGroups.
    • P1 would create profiles for the Configuration, User, PriceList, and PricingRule TableGroups.
    • DEFAULT organization would create profiles for the Hub, User, and Configuration TableGroups.

Notes:

  • The Configuration TableGroup profile is required for all enterprises that "own" data because configuration data exists for each enterprise; pricing configuration exists for the pricing enterprise, and catalog configuration exists for the catalog enterprise.
  • The User TableGroup profile is required for all enterprises that have users defined. The definition of a User TableGroup profile for an enterprise (organization) will also export all users for all organizations (sellers, stores) that have that enterprise as the primary enterprise.
  • The Approval and Validation TableGroup profiles are required for enterprise organizations that define approval and validation rules. If a template organization has defined such an enterprise as its primary enterprise, the enterprise’s approval and validation data will also be exported for the template organization. Therefore, you only need to create a profile for a template organization if the template organization is defined as an enterprise.
  • If you upgrade to a new version of IBM® Sterling™ Order Management System Software and want to use Data Sync to export data that has queries stored in the YFS_QUERY table, a CatalogSetup profile needs to be created by the DEFAULT organization rather than the enterprise (organization) that owns the data. This is because, as part of the upgrade, the YFS_QUERY table contains an additional column, ORGANIZATION_CODE, which has a default value of DEFAULT.