Product – Sub product Definition
The setup of products and sub products is done by adding entries to the OD_PRODUCT_MASTER_MB table. This need not have to be a table. Instead it can be a view that aggregates dynamic setup done in the underlying system.
The definition of this Object in the Canvas schema is provided in the following table:
Column Name | M / O | Type | Purpose |
---|---|---|---|
OD_HOST_ID | M | String | A unique ID with which this product can be categorized against a host. |
OD_HOST_PRODUCT_CODE | M | String | This is the product code under which the host system respects this product. |
OD_HOST_SUBPROD_CODE | M | String | This is the sub product code under which the host system identifies this sub product. |
OD_PRODUCT_TYPE | M | String | This is used for categorizing this product / sub product offering. |
OD_PRODUCT_CODE | M | String(10) | This is the product code that is recognized by Canvas and is used as part of its internal storage of profiles, etc. |
OD_PRODUCT_DESC | M | String | This is a column provided to the developer for storing any meaningful comment for quick identification of this product. |
OD_SUBPROD_CODE | M | String | This is the sub product under the provided product that is to be used. This is the code that is recognized by Canvas and is used as part of its internal storage of profiles, etc. |
OD_SUBPROD_DESC | M | String | This is a column provided to the developer for storing any meaningful comment for quick identification of this sub product. |
OD_PRODUCT_DEFN | O | String | One more categorization provided for the product. |
OD_PRODUCT_CATEGORY | O | String | Another categorization option provided for the product. The possible values used are as follows:
|
The data level entitlement is configured through the object OO_CRITERIA_TYPE_MASTER. Canvas expects that the data level entitlements are mapped to the Product – Sub Product combination and not directly to functions. This goes with the concept that all functions under a Product – Sub Product combination automatically derive the data level criteria applicable. There could be scenarios where a function may not work with any data level criteria. In such cases, the function could be marked as read-only to indicate that scenario.
The definition of this Object in the Canvas schema is provided in the following table:
Column Name | M / O | Type | Purpose |
---|---|---|---|
CRITERIA_TYPE | M | String | The criteria type (key) against which the data level entitlement is captured as part profiling. |
DESCRIPTION | M | String | This is a column provided to the developer for storing any meaningful comment for quick identification of the criteria. |
PRODUCT_CODE | M | String(10) | This is the product code that is recognized by Canvas and is used as part of its internal storage of profiles, etc. |
SUBPRODUCT_CODE | M | String | This is the sub product under the provided product that is to be used. This is the code that is recognized by Canvas and is used as part of its internal storage of profiles, etc. |
ENABLE_FLAG | M | String | Provide this as Y to indicate that this criterion is activated. |
SOURCE_TYPE | M | String | Indicates how the possible values for the criterion can be fetched. The default source type is V.
|
SOURCE_VALUE | M | String | Provides the actual value corresponding to the source type. |
LOOKUP_CLASS | M | String | For requests that are raised linked to transaction flow, this is the class that is invoked for evaluating limits against the criteria. |
LIMIT_REQUIRED | M | String | This is applicable only for requests that are raised linked to the transaction flow. Provide this as Y to indicate that limit validation should be activated for this criterion. |
For more information, refer the Data Level Entitlements Configuration section in this document.