Skip to Content

Here I have used the complaints component but you can do it with any order object.

Creation of component usages

So in the component BT120H_CPL I have created 2 new usages (you can use more) in the runtime repositery :

/wp-content/uploads/2014/05/usages_459291.png

You need to name your usage starting with “CUBTCategories_” and then a letter corresponding to the catalog category you want to use, or you will have to change the code I used in the method WD_USAGE_INITIALIZE (see below).

Then I put these usages in the viewset :

/wp-content/uploads/2014/05/runtime_rep_459357.png

You can then add the new viewareas in the configuration (but they won’t work until coding and customizing is done).

Usage initialize in the component controller

I redefined the WD_USAGE_INITIALIZE method in the component controller :

You can see I used mr_cnode_binding_mgr which is the same than the one in the incident component controller :

/wp-content/uploads/2014/05/usage_mgr_459324.png

Several methods are redefine in order to create and manage this binding manager :

/wp-content/uploads/2014/05/methods_459333.png

You can find the added code for these methods in component controller of component SRQM_INCIDENT_H, I just copied them.

For instance :

/wp-content/uploads/2014/05/do_init_459334.png

Customizing of schemas

/wp-content/uploads/2014/05/app_areas_459341.png

In order to link our shemas with the application we will use a combination of transaction type and catalog category, this entry has to be added :

/wp-content/uploads/2014/05/complaint_area_459342.png

Then you just assign transaction type and catalog categories :

/wp-content/uploads/2014/05/assign_trans_459343.png

/wp-content/uploads/2014/05/zass_459351.png

Here you see why I put C and D in the usage names.

Then in your schema you need to use application areas corresponding to the catalog category :

/wp-content/uploads/2014/05/schema_areas_459352.png

Here I didn’t put a description in the customizing for the parameter.

/wp-content/uploads/2014/05/app_value_459356.png

And then do the same for others schemas, using different category of catalog.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Nelson Raj

    Hi Benoit,

    Thanks a lot for this great resource.

    I have a few clarifications for you.

    You mentioned that this can be applied to any 1-order object. I am trying to do this for the BUS2000126 (Activity) but it does not allow me.

    The missing piece in the puzzle is the Subject Profile Category = F, linked to Catalog Category = F, which is for Activities. However, for the Customizing “Assignment of Transaction Type to Catalog Categories”, the only options available are “C,D,E,T”.

    Do you have any suggestions how to tweak your solution for implementation within the Business Activity Object?

    Regards,

    Nelson

    (0) 
    1. Benoît Sabys Post author

      Hello,

      In fact you don’t need to use the subject profile.

      In “Define Application Areas for categorization”, you have to add the parameter TXN_TYPE_AND_CATALOGTYPE for the application area “BUS_ACTIVITY”.

      My screenshot is maybe misleading but you don’t need to use subject profile, you reallly need to use the transaction type.

      Regards,

      Benoît

      (0) 
      1. Nelson Raj

        Hi Benoit,

        Thanks very much for your reply.

        I did add the customizing for the BUS_ACTIVITY, as you mentioned, but it did not add it to the Application Area, within the Categorization Schema in the WebUI.

        However, it did appear when I added it for the COMPLAINT, when I added the TXN_TYPE_AND_CATALOGTYPE.

        It seems that the Categorization UI is only looking for the Service Transactions.

        Regards,

        Nelson

        (0) 

Leave a Reply