A config organization represents an organization in the
hierarchy at which a set of point-of-sale configurations, business
rules, and processes are defined for a store or a group of stores.
A config organization provides any of the following functions:
- Defines a set of business rules and configuration information
that is shared by a group of stores. Consider a group of stores where
the stores are located in the same region or share business needs.
The stores can designate a config organization that defines a common
set of business rules to be shared by the stores in the group.
- Can exist as a logical organization. A config organization can
be an enterprise, seller, or node. A config organization cannot be
a buyer or carrier.
- Can exist only for the purpose of managing business rules and
does not exist as a logical organization. In this case, the config
organization is designated to play the role of a template organization.
- Defines store rules and configuration information that can be
overridden or extended by child config organizations. The following
figure shows an example in which XYZ-WEST is a template organization
that acts as the config organization for XYZ-SAN JOSE, and XYZ-EAST
is a template organization that acts as the config organization for
XYZ-BOSTON and XYZ-NEW YORK. No config organization is defined for
XYZ-DALLAS. XYZ-CORP is the primary enterprise for XYZ-WEST, XYZ-EAST,
XYZ-SAN JOSE, XYZ-BOSTON, XYZ-NEW YORK, and XYZ-DALLAS. In the example,
the child config organizations share the business rules and configuration
information that is defined by their respective config organization.
Additionally, the child config organizations can override or extend
the rules and information that is defined by their config organization.
Because no config organization is defined for XYZ-DALLAS, store business
rules and configuration information for XYZ-DALLAS are defined by
the primary enterprise, XYZ-CORP.
Figure 1. Example:
config organization and primary enterprise
In the application framework, all configurations and business rules
are associated with BaseConfigGroups. Some rules are defined out-of-the-box
for the "Store" group level. BaseConfigGroups that are associated
with the "Store" group level follow the template organization hierarchy.
The following table shows an example where the template organization
hierarchy is used by organizations inheriting the OFFLINE_LIMIT_STORE
rule and rule values. In the example, the OFFLINE_LIMIT_STORE base
rule and values are defined by the primary enterprise, XYZ-CORP, and
config organizations, XYZ-WEST and XYZ-EAST.
Table 1. Rule value
for the OFFLINE_LIMIT_STORE base ruleRule ID |
Organization |
Rule_ID |
Rule Set Value |
Rule-1 |
XYZ-CORP |
OFFLINE_LIMIT_STORE |
$130 |
Rule-2 |
XYZ-WEST |
OFFLINE_LIMIT_STORE |
$120 |
Rule-3 |
XYZ-EAST |
OFFLINE_LIMIT_STORE |
$100 |
In the example, XYZ-BOSTON and XYZ-NEW YORK inherit the rule value
from XYZ-EAST config organization; XYZ-SAN JOSE inherits the rule
value from the XYZ-WEST config organization. XYZ-DALLAS inherits the
rule value from the primary enterprise, XYZ-CORP. The following table
shows the rule value that is returned to each calling organization.
Table 2. Rule value returned
to calling organizationCalling Organization |
Rule Value Returned |
XYZ-SAN JOSE |
$120 |
XYZ-BOSTON |
$100 |
XYZ-NEW YORK |
$100 |
XYZ-DALLAS |
$130 |