Source data categorization

Master data is divided into categories, which helps when exporting data. Categories ensure that only necessary data is exported.

Master data is divided into the following categories, which list TableGroups with their respective driver tables in parentheses:

  • Catalog Related
    • Catalog (YFS_ITEM)
    • Category (YFS_CATEGORY)
    • CatalogSetup (no driver table - filter is not supported)
    • Entitlements (YFS_ENTITLEMENT_RULE_HDR)
  • Pricing Related
    • Price Lists (YPM_PRICELIST_HDR)
    • Pricing Rule (YPM_PRICING_RULE)
  • Other
    • Approval (YFS_ORDER_APPROVAL_RULE)
    • Users (YFS_USER) - When exporting, the following users are exported for the enterprise that has defined this profile. Users of that enterprise and users of any organization have defined that the enterprise that owns the profile is the organization’s primary enterprise.
    • Validation Rule (YFS_VALIDATION_RULE)
  • Configuration Data is divided into the following Table Groups:
    • Configuration
    • Hub

Notes:

  • Master data export can also be customized based on user preference. You can extend master data export templates in a similar way to extending API templates. For additional information about extending these templates, search for the topic "About Extending API Templates".
  • If your table modifications impact any APIs, you must extend the templates of those APIs. Place the extended API templates in the INSTALL_DIR/extensions/global/template/resource directory.

The Master data is further categorized based on certain filters on the master database entities. These filters allow the enterprise to categorize its data so that organizations synchronize only the data they need. For example, price lists can be exported only to the stores assigned to them, and a store imports catalog information only for the items it sells.

  • Profiles are used to define what should be exported. They are defined by the enterprise that owns the data.

    A profile contains a set of data. It acts on a single table group that maps to a single driver table. The data can be filtered at the driver table level using queries. The query and the entity are both stored in the filter.

    For example, you can profile some of the items as “SOLD IN STORES ”or “DO NOT SELL”.

    The entities in the database are related according to how they are used in the system. A table group contains a set of these related entities that are to be included in a profile.

    For example, the catalog table group contains items, item categories, item units of measure, and other data. A store that is interested in catalog information is interested in all of these entities but might not be interested in the Users data. The table groups specify the tables to be included in a profile.

    For more information about configuring profiles, seeConfiguring profile.

  • Subscriptions are used to group profiles.

    When a store is interested in a subset of Master data, you can create subscriptions to a set of profiles to export data to the store.

    For example, a subscription can be created to include catalog and pricing data profiles, and a store can subscribe to this subscription.

    For more information about configuring subscription, seeConfiguring subscription.

  • Target: A target is used to define who the subscription is for.