Modeling of the Required Characteristics in Fulfillment Catalog

As per the requirement of the amendment use case, some or all of the following characteristics are required to be available in the product model published to TIBCO Fulfillment Order Management. The modeling of these characteristics and relating them with the required products, needs to be done in TIBCO Fulfillment Catalog at the design time. Refer the generic steps given below for modeling.

Note:

This section covers just the high level modeling steps specific to the characteristics required for amendments. Refer TIBCO Fulfillment Catalog documentation for details.

  1. Create the following records in CHARACTERISTIC repository:
    • EPMR_ACTION_PROVIDE
    • EPMR_ACTION_CEASE
    • EPMR_ACTION_UPDATE
    • EPMR_ACTION_WITHDRAW
    • COMPENSATE_PROVIDE
    • COMPENSATE_CEASE
    • COMPENSATE_UPDATE
  2. For more granular EPMR actions based on the plan item statuses, the user can add additional characteristics mentioned below in generic format. Note that these characteristics are used only in case of the new and improved UDF modification functionality. Refer the New Characteristics sub-section in OrderLine UDF change.
    • EPMR_ACTION_<<action>>_UDF_CHANGE_<<Plan Item Status>>. For example, EPMR_ACTION_PROVIDE_UDF_CHANGE_SUSPENDED.
  3. Create the Characteristic relationship between the records in PRODUCT repository and one or more EPMR_ACTION_* records in the CHARACTERISTIC repository mentioned in point 1 and 2 above. The logically valid value for the RelationshipValue attributes in all these Characteristic relationships can be one of the four EPMR actions - COMPENSATE, RESTART, COMPENSATE_RESTART, or IGNORE. Refer the Execution Plan Modification Rules (EPMR) topic for the significance of these four actions. For example, the technical product Router can have a Characteristic relationship with EPMR_ACTION_PROVIDE characteristic, with the value of RelationshipValue attribute as COMPENSATE_RESTART.
  4. Create the Characteristic relationship between the records in PRODUCT repository and one or more COMPENSATE_* records in the CHARACTERISTIC repository mentioned in point 1 above. The logically valid value for the RelationshipValue attributes in all these Characteristic relationships should be the ID of the plan fragment record that is required to be executed as the compensation task for corresponding action. For example, the technical product Router can have a Characteristic relationship with COMPENSATE_PROVIDE characteristic, with the value of RelationshipValue attribute as the planFragmentID Router_Cancel.