lr_object = go_handler_factory->get_handler( iv_object_name = lv_name ).
TRY.      lr_post ?= lr_object.
CATCH:cx_sy_move_cast_error.     EXIT.
ENDTRY.
CHECK lr_post IS NOT INITIAL.
CALL METHOD lr_post->read_object    EXPORTING        it_request_objects = it_request_objects        iv_ref             = iv_root_list   CHANGING        ct_bapireturn      = lt_bapireturn. 

method GET_FE_DATA.    data: lv_guid         TYPE crmt_genil_object_guid,          lv_attr         TYPE ZCRM_EXT_SMC_DYNP_SV,          lv_convert_guid TYPE socialdata-socialdatauuid,          lv_post_id      TYPE socialdata-internal_id.    data(lv_children) = iv_container->GET_CHILDREN( IV_AS_COPY = ABAP_TRUE ).    data(lv_child) = LV_CHILDREN->GET_FIRST( ).    ASSERT lv_child IS BOUND.    iv_container->get_key( IMPORTING es_key = lv_guid ).    lv_convert_guid = lv_guid.    lv_attr = zcl_crm_soc_fe_buffer_access=>get( lv_convert_guid ).    lv_child->set_attributes( lv_attr ).    DATA(lv_attr_props) = lv_child->get_attr_props_obj( ).    lv_attr_props->set_all_properties( if_genil_obj_attr_properties=>changeable ).    SELECT SINGLE internal_id INTO lv_post_id FROM socialdata WHERE socialdatauuid = lv_convert_guid    ASSERT sy-subrc = 0.    data(ls_key) = VALUE ZCRM_EXT_SMC_KEY( client = sy-mandt post_id = lv_post_id ).    lv_child->set_key( ls_key ).  endmethod.

method GET.    DATA: ls_data TYPE ZCRM_SOC_FE,          ls_attr TYPE ZCRM_EXT_SMC_DYNP_SV.    READ TABLE st_buffer ASSIGNING FIELD-SYMBOL(<buffer>) WITH KEY uuid = iv_guid.    IF sy-subrc = 0.        rs_data = <buffer>-data.        RETURN.    ENDIF.    SELECT SINGLE * INTO CORRESPONDING FIELDS OF ls_data FROM ( ZCRM_SOC_FE AS A INNER JOIN  socialdata AS B        ON B~internal_id = A~post_id ) WHERE B~SOCIALDATAUUID = iv_guid.    CHECK ls_data IS NOT INITIAL.    MOVE-CORRESPONDING ls_data TO ls_attr.    DATA(ls_entry) = VALUE ty_buffer( uuid = iv_guid data = ls_attr ).    APPEND ls_entry TO st_buffer.    rs_data = ls_attr.  endmethod.

types:    BEGIN OF ty_buffer,           uuid TYPE socialdata-socialdatauuid,           data TYPE ZCRM_EXT_SMC_DYNP_SV,         END OF ty_buffer .  types:    tt_buffer TYPE STANDARD TABLE OF ty_buffer WITH KEY uuid .

Those features like F4 help and validation logic for respective data type are automaitcally handled by AET framework. You do not need to code by yourself

METHOD GET_P_INTERNAL_ID.  CASE iv_property.      WHEN if_bsp_wd_model_setter_getter=>fp_fieldtype.        rv_value = cl_bsp_dlc_view_descriptor=>field_type_event_link.      WHEN if_bsp_wd_model_setter_getter=>fp_onclick.        rv_value = 'ATTACHMENT'.   ENDCASE.
ENDMETHOD.

  DATA: lr_popup TYPE REF TO IF_BSP_WD_POPUP,          lv_post TYPE REF TO cl_crm_bol_entity,          lv_bol_col TYPE REF TO CL_CRM_BOL_BO_COL.    lv_post = zcl_jerry_tool=>get_selected_post_by_event( iv_col_wrapper = me->typed_context->searchresult->collection_wrapper        iv_event = htmlb_event_ex->event_id ).    CREATE OBJECT lv_bol_col.    lv_bol_col->IF_BOL_BO_COL~add( lv_post ).  lr_popup = comp_controller->window_manager->create_popup(     iv_interface_view_name = 'ZSMCATT/MainWindow'     iv_usage_name = 'ZSMCATT'     iv_title = 'Social Post Attachment Maintenance' ).  lr_popup->set_on_close_event( iv_view = me iv_event_name =
'CLEAR').  lr_popup->open( iv_inbound_plug = 'FROM_SEARCH' iv_collection = lv_bol_col ).

all the content in pop up window is encapsulated in interface view MainWindow of ZSMCATT. Our next step will focus on its implementation.
the method get_selected_post_by_event is a handy method which just returns the selected post BOL entity via event:
DATA:
    lv_index_str TYPE string,    lv_idx       TYPE string,    lv_index     TYPE i,    lv_result    TYPE REF TO cl_crm_bol_entity.    lv_index_str = iv_event.  SHIFT lv_index_str UP TO '[' LEFT CIRCULAR.  SHIFT lv_index_str BY 1 PLACES.  WHILE lv_index_str(1) <> ']'.    CONCATENATE lv_idx lv_index_str(1) INTO lv_idx.    SHIFT lv_index_str BY 1 PLACES.  ENDWHILE.  lv_index = lv_idx.  CHECK lv_index >= 0.  lv_result ?= iv_col_wrapper->find( iv_index = lv_index ).  CHECK lv_result IS NOT INITIAL.  rv_result = lv_result->get_related_entity( 'SocialPostRel' ). "#EC NOTEXT

step3:

component ZSMCATT just contains one overview page and one post header page.

The overview page has two assignment blocks: one( headerWindow ) for post header which indicates the current post being maintained, the other one( attachmentWindow ) just displays the UI of reuse component GS_CM.

step5

in component controller of ZSMCQR, do component context node binding for component usage ZSMCATTR:

method WD_USAGE_INITIALIZE.   DATA:          lv_usage  TYPE REF TO if_bsp_wd_component_usage,          lo_entity TYPE ref to cl_crm_bol_entity.    CHECK me->typed_context->socialpost->collection_wrapper IS NOT INITIAL.    lv_usage = me->comp_controller->get_component_usage( iv_usage->usage_name ).    IF lv_usage->usage_name = 'ZSMCATT'.      CALL METHOD lv_usage->bind_context_node         EXPORTING           iv_controller_type  = cl_bsp_wd_controller=>co_type_component           iv_target_node_name = 'SOCIALPOST'                   "#EC NOTEXT           iv_node_2_bind      = 'SOCIALPOST'.                  "#EC NOTEXT    ENDIF.  endmethod.

step6

in component ZSMCATTR, create a custom controller and create a context node CMBO. Implement its on_new_focus method:

METHOD on_new_focus.
 DATA: lr_qs              TYPE REF TO cl_crm_bol_query_service,       lr_data            TYPE REF TO data,       ls_cmbo_prop       TYPE crmt_cmic_rfolder_attr,       lr_entity_col      TYPE REF TO if_bol_entity_col.  FIELD-SYMBOLS: <fs_guid> TYPE crmt_genil_object_guid.  CHECK focus_bo IS BOUND.  TRY.      lr_qs = cl_crm_bol_query_service=>get_instance( cl_crm_cm_genil_comp=>gc_query_bo_link ).    CATCH cx_root.                                      "#EC NO_HANDLER      RETURN.  ENDTRY.  CHECK lr_qs IS BOUND.  lr_data = focus_bo->get_property( 'UUID' ).  ASSIGN lr_data->* TO <fs_guid>.  ls_cmbo_prop-instid = <fs_guid>.  ls_cmbo_prop-typeid = 'BUS1006'. ------------- use your own BOR type here!  ls_cmbo_prop-catid = 'BO'.  lr_qs->set_properties( ls_cmbo_prop ).  lr_entity_col = lr_qs->get_query_result( ).  me->collection_wrapper->clear_collection( ).  me->collection_wrapper->set_collection( lr_entity_col ).  ENDMETHOD.

in component controller of ZSMCATTR, do the context node binding logic:

METHOD wd_usage_initialize.
DATA: lr_cn       TYPE REF TO cl_bsp_wd_context_node,           lr_property         TYPE REF TO if_bol_bo_property_access,           lr_cn_attr  TYPE REF TO if_bol_bo_property_access,           lr_cuco_attachement TYPE REF TO CL_ZSMCATT_CMBO_IMPL,           ls_cm_attr  TYPE crmt_cm_comp_st.   IF NOT me->context IS BOUND.     me->wd_create_context( ).   ENDIF.   CASE iv_usage->usage_name.     WHEN 'AttachmentUploadDet' or 'AttachmentUpload' or 'AttachmentProperty'.      CALL METHOD iv_usage->bind_context_node        EXPORTING          iv_controller_type  = cl_bsp_wd_controller=>co_type_custom          iv_name             = 'ZSMCATT/CMBO'          iv_target_node_name = 'CMBO'                "#EC NOTEXT          iv_node_2_bind      = 'CMBUSOBJ'.                "#EC NOTEXT       CALL METHOD iv_usage->bind_context_node        EXPORTING          iv_controller_type  = cl_bsp_wd_controller=>co_type_component
*         node at the calling component          iv_target_node_name = 'SOCIALPOST'                       "#EC NOTEXT
*         name of the called component          iv_name             = iv_usage->usage_name
*         node at the called component          iv_node_2_bind      = 'PARENTNODE'.   ENDCASE.
 ENDMETHOD.

never forget to call on_new_focus of custom controller context node manually:

lr_cuco_attachement ?= get_custom_controller( 'ZSMCATT/CMBO' ).
 IF lr_cuco_attachement IS BOUND.        lr_property = me->typed_context->socialpost->collection_wrapper->get_current( ).        lr_cuco_attachement->typed_context->cmbo->on_new_focus( lr_property ).        lr_cuco_attachement->typed_context->attribute->on_new_focus( lr_property ).
 ENDIF.

step7:

implement the inbound of outbound plug of window attachmentWindow,

and DetailWindow:

for source code of these two class please refer to attached document.

that's all.

Summary: in this solution we use three component usage on GS_CM, one for attachment list page in attachment assignblock, the second for Attachment upload page and the third for attachment property page. If you would like to know how to control the enablement of attachment maintenance dynamically, please continue to read the next blog.

 method IF_BSP_MODEL~INIT.  super->if_bsp_model~init( id    = id                            owner = owner ).  mr_owner ?= owner.  DATA: lv_struct_ref TYPE REF TO crmt_cm_comp_st,        lv_value_node TYPE REF TO cl_bsp_wd_value_node,        lv_bo_coll    TYPE REF TO if_bol_bo_col.  CREATE DATA lv_struct_ref.  CREATE OBJECT lv_value_node    EXPORTING      iv_data_ref = lv_struct_ref.  CREATE OBJECT lv_bo_coll    TYPE      cl_crm_bol_bo_col.  lv_bo_coll->add( lv_value_node ).  set_collection( lv_bo_coll ).  CL_ZSMCATT_BSPWDCOMPONENT_IMPL=>GO_ATTR_WRAPPER = me->collection_wrapper.  endmethod.

 method ON_NEW_FOCUS.     DATA:     lr_entity          TYPE REF TO cl_crm_bol_entity,     lr_parent          TYPE REF TO cl_crm_bol_entity,     lv_entity_name     TYPE string,     ls_cm_attr         TYPE crmt_cm_comp_st,     lv_product_type    TYPE comt_product_type,     lr_bo_attr         TYPE REF TO if_bol_bo_property_access,     ls_prtyp_cust      TYPE coms_prtyp_cust,     lv_object_guid     TYPE ib_recno_16,     lv_current         TYPE flag,     ls_button          TYPE crmt_thtmlb_button.  CHECK focus_bo IS BOUND.  lr_entity ?= focus_bo.  lv_entity_name = lr_entity->get_name( ).  IF CL_ZSMCATT_BSPWDCOMPONENT_IMPL=>gv_can_edit = 'X'.    ls_cm_attr-display = ''.  ELSE.    ls_cm_attr-display = 'X'.  ENDIF.  CHECK CL_ZSMCATT_BSPWDCOMPONENT_IMPL=>GO_ATTR_WRAPPER IS NOT INITIAL.  lr_bo_attr = CL_ZSMCATT_BSPWDCOMPONENT_IMPL=>GO_ATTR_WRAPPER->get_current( ).  CHECK lr_bo_attr IS BOUND.  lr_bo_attr->set_properties( ls_cm_attr ).  endmethod.

CALL METHOD iv_usage->bind_context_node        EXPORTING          iv_controller_type  = cl_bsp_wd_controller=>co_type_custom          iv_name             = 'ZSMCATT/CMBO'          iv_target_node_name = 'ATTRIBUTE'                "#EC NOTEXT          iv_node_2_bind      = 'ATTRIBUTES'.                "#EC NOTEXT

lr_cuco_attachement ?= get_custom_controller( 'ZSMCATT/CMBO' ).
IF lr_cuco_attachement IS BOUND.
        lr_property = me>typed_context->socialpost->collection_wrapper->get_current( ).        lr_cuco_attachement->typed_context->cmbo->on_new_focus( lr_property ).        lr_cuco_attachement->typed_context->attribute->on_new_focus( lr_property ).

ENDIF. 

In every implementation of SAP CRM, We come across to the many challenges and one of these challenges is the prevention of hard coding in system enhancements.

For implementation point of view the hard coding of transaction types might cover current requirements, but maybe in the future a new transaction type will be created or removal of existing transaction type. In this case the transaction type was hard coded, a program change is required. So, Most of customer do not like such approach example the below code since it is not flexible.

This blog is to describe ways of preventing hard coding, 

• Use SAP Own way of parameter customizing option via the transaction STVARV: 

Go to Transaction STVARV and maintain the data. Create a parameter or select option data and fill in the values/constants that your program requires. 

Use a select query in the beginning of your program to fetch the parameters you have maintained in the table.  At any point, any functional or support person can edit the entries in the TVARVC table and your program will consider the updated values without the need of modifying the code.

• Object Oriented Approach By Creating a customizing table for these entries and Define an access class:-

Although, SAP provides it own parameter customizing option via the transaction STVARV. With this transaction it is possible to define your own parameter and set a value for this parameter. In my experience it is useful to have the option to deviate per sales organisation and even distribution channel or many more options based business. For Example, may be the French (FR) business has other requirements then the Dutch Business(NL). So in this example we have created our own table with the following key fields:

• Usage Type – Parameter value
• Sales Organisation – Sales Organisation
• Distribution Channel – Distribution Channel

Define Customizing table

Next to the Key fields we use the standard fields for a range table. This will make it easier to use the values in the calling code. For our example we now need to divine a parameter and create two entries in the table, one for each transaction type.

Define Access class

To enable an easy access for calling programs we have created an access class that will build a range table. The method in this class will have the key fields of the table as import parameters. The export parameter will be a range table. One of the challenges here is that the range table should be different depending on the field that is in the value part. In our example this field should be of the same type as the field process type. We manage this by using a STANDARD TABLE and field symbols as follows.

  DATA: lt_crm_customizing TYPE TABLE OF zcrm_customizing.

 

FIELD-SYMBOLS:

<lfs_crm_customizing> TYPE zcrm_customizing,

<lfs_custom_range>  TYPE any,

<lfs_sign> TYPE any,

<lfs_option> TYPE any,

<lfs_low> TYPE any,

<lfs_high> TYPE any.

 

CLEAR: et_custom_range.

SELECT * FROM zcrm_customizing INTO TABLE lt_crm_customizing

WHERE usage_type = iv_usage

AND sales_org = iv_sales_org

AND distr_channel = iv_distr_channel.

 

LOOP AT lt_crm_customizing ASSIGNING <lfs_crm_customizing>.

   APPEND INITIAL LINE TO et_custom_range ASSIGNING <lfs_custom_range>.

   ASSERT sy-subrc = 0.

   ASSIGN COMPONENT 'SIGN' OF STRUCTURE <lfs_custom_range> TO <lfs_sign>.

   ASSERT sy-subrc = 0.

   ASSIGN COMPONENT 'OPTION' OF STRUCTURE <lfs_custom_range> TO <lfs_option>.

   ASSERT sy-subrc = 0.

   ASSIGN COMPONENT 'LOW' OF STRUCTURE <lfs_custom_range> TO <lfs_low>.

   ASSERT sy-subrc = 0.

   ASSIGN COMPONENT 'HIGH' OF STRUCTURE <lfs_custom_range> TO <lfs_high>.

   ASSERT sy-subrc = 0.

   <lfs_sign> = <lfs_crm_customizing>-sign.

   <lfs_option>  = <lfs_crm_customizing>-opti.

   <lfs_low> = <lfs_crm_customizing>-low.

   <lfs_high> = <lfs_crm_customizing>-high.

ENDLOOP.

Calling Program

The calling program needs to define a range table of the type of the expected value. In our example we expect a process type in the value so we create the range table as follows.

DATA: lt_range_proces TYPE RANGE OF crmt_orderadm_h_wrk-process_type.

 

  "we will now call the access class with this table and will tell the class what field type it should use for the range table.

 

  zl_crm_customizing_access=>read_customizing( EXPORTING iv_usage  = 'CHECK_QUOTE_START_DATE'

                                                         iv_sales_org = lv_sales_org

                                                         iv_distr_channel  = lv_dis_channel

                                                 IMPORTING  et_custom_range = lt_range_proces ).

 

      The range table can now easily be used to check the transaction type.

CHECK ls_orderadm_h-process_type IN lt_range_proces.

     PS:  If the same check should be executed for more transaction types in the future, it is only a matter of creating a new entry in customizing table and the work is done.  

     Other scenario or examples where in the same table will/can be used are as follows-

• ORDER_SAVE BAdI implementation with restriction on transaction type or check before save
• Adding the description of an order/contract that is created via copy control.
• Setting shipping condition based on sale organisation via CRM_SHIPPING_BADI

Multi-level Categorization is a kind of hierarchical categories which can be used in the business transaction for classification purposes. For example, in the service order, we can categorize the defect, reason, solutions into many hierarchical categories. One or more than one can be selected easily from the hierarchical tree in the service order header or item.

Multilevel categorization is available in varying scopes for the following applications:

• Service orders
• Service order templates
• Confirmations
• Complaints
• In-house repair orders
• Case management
• Interaction record

In some cases if we need to know which level in the category is filled , then we need to calculate the node level which is filled and based on that we can determine whether the node level which we have to look for is filled or not. For e.g. in defect there are L1->L2->L3->L4->L5 , then if we need to find out if L5 is filled or not and if only level L3 is filled then the output that we would get is level 3 and we sure that L5 is not filled. In some business scenario we need to determine if a particular level is filled ( Level has to be filled mandatorily in the transaction). If the level is not filled we need to raise an error message. So the blog below would help to calcuate the level in a category. Using the APIs in the code below , you can twist and tweak as per your requirement.

data: lr_aspect   type ref to if_crm_erms_catego_aspect,      lr_category type ref to if_crm_erms_catego_category,      lv_ref_guid type guid_16 value '0050560600AD1ED2B8E18732B52E5D75',      lv_asp_guid type crm_erms_cat_guid,      lv_cat_guid type crm_erms_cat_guid,      lv_sel_level type int4,      ls_cat      type crmt_erms_cat_ca_buf.

call method cl_crm_ml_category_util=>get_categoryfirst  exporting    iv_ref_guid     = lv_ref_guid    iv_ref_kind     = 'A'
*   iv_catalog_type = 'C'"ORDER_READ->ET_SUBJECT->CAT_ID'  importing    er_aspect       = lr_aspect    er_category     = lr_category.

* get aspect guid
call method lr_aspect->get_asp_guid  receiving    rv_asp_guid = lv_asp_guid.
* get category guid
call method lr_category->get_details  importing    ev_cat = ls_cat.
lv_cat_guid = ls_cat-cat_guid.

cl_crm_ml_category_util=>get_selected_category_tree(  exporting    iv_selected_cat_guid = lv_cat_guid    " Selected Category GUID    iv_schema_guid       = lv_asp_guid    " Schema GUID  importing    ev_selected_level    = lv_sel_level    " Selected Category Level
*    ev_parent_cat_guid   =     " Parent Category GUID
*    ev_parent_cat_id     =     " Parent Category ID
*    ev_parent_level      =     " Parent Category level
).

The lv_sel_level would give you the level details. Based on business sceanrio , we can add validations .

The topic of the blog may seem queer but as I would illustrate later it is very relevant in the lives of technical consultants. I would illustrate with examples how these approaches would help you succeed or if fail then fail gracefully ( read exception and dumps ) . Lets look into each of one at a time.

CHECK

• For e.g. if you want to do something like this then this a recipe for sure shot disaster. If lv_entity is not bound then you would run into a dump/exception.You can use this in possibly many ways and you should use this as much as possible.

lv_bo ?= lv_entity.
lv_bo->set_property( iv_attr_name = ‘CITY’
iv_value = ‘Walldorf’ ).

the better way to the similar coding would be

lv_bo ?= lv_entity.
CHECK lv_bo is bound. 
lv_bo->set_property( iv_attr_name = ‘CITY’
iv_value = ‘Walldorf’ ).

or

lv_bo ?= lv_entity.
if lv_bo is bound.
lv_bo->set_property( iv_attr_name = ‘CITY’
iv_value = ‘Walldorf’ ).
endif. 

This is a very common failure scenario and is so common that we often tend to ignore this.

• The second variety is when you write a new method/form etc. , then check whether the importing parameters are proper. This would mean if you expect a reference variable to be passed then it should be bound or if you have a mandatory parameter passed then it should be having some value. Similarly pass export only those parameters which are requested. ( This is not a disastrous case but can save performance).For e.g. if you are sending a collection as an importing parameter to a method then you can write the following statement. This way you know that the col is bound and contains entities

          CHECK ir_col is bound and ir_col->size(  ) > 0. 

CLEAR

This one is my personal favorite. Often uncleared variable could cause embarrassing problems and of magnitude you cannot even imagine. For e.g. you are in a conditional statement where you fill some variables based on condition being true and condition was false and since the variable were not cleared you still get data in variables. Or for e.g. you failed to clear an entity reference variable it would cause you lots of issues. I am providing some examples

lv_bo ?= lv_person.
lv_*** = lv_bo->get_property( ‘***’ ). “Key code
if lv_person->get_parent( ) is not initial.
lv_bo ?= lv_person->get_parent( ).
lv_*** = lv_bo->get_property( ‘***’ ). “Key code
ENDWHILE.

Now if the if condition is not true , then lv_*** is line no 5 should be blank but it would be filled with value fetched in line no 2. In this case it may not seem disastrous but in some cases it is extremely catastrophic.

The better way to do this would be following. As a general rule for methods which have returning or exporting parameters , clear the variables which are collecting values.

lv_bo ?= lv_person.
clear lv_***.
lv_*** = lv_bo->get_property( ‘***’ ). “Key code
if lv_person->get_parent( ) is not initial.
lv_bo ?= lv_person->get_parent( ).
clear lv_***.
lv_*** = lv_bo->get_property( ‘***’ ). “Key code
ENDWHILE.

In my case , I was trying to create multiple DOCFLOW entities but I not have cleared the variable through which I was passing the data to docflow and I was passing the same docflow instance every time hence the data was getting overwritten in same entity. 

CATCH

Another of my personal favorite. Exceptions are pretty common while we execute a scenario in WebUI. But they are handled in the framework and hence even though exceptions are raised , gracefully WebUI screen opens. If I call a method and it runs into an exception , then it could result in a dump or exception. Both of them are not appreciated by the users hence it makes a lot of sense to fail gracefully and provide exception handling. As a general rule if you are coding in WebUI , don't raise exceptions and don't fail to catch exceptions. Both of them are absolutely necessary.

while lr_current_entity is not initial and lr_entity is not initial .
 *  Add the entitiy
 try.                Clear lr_entity.
CHECK lr_ent is bound.
 lr_ent ?= lr_entity.
 if lr_ent->alive( ) = abap_true.
 Clear lr_adminh , clear lv_object_type.
 lr_adminh ?= lr_ent->get_related_entity( 'BTOrderHeader' ).
 if  (Your_Condition).
 else.  lr_current_entity ?= lr_iterator->get_next( ).
 lr_entity ?= ir_valuehelp_collection->get_next( ).
 endif.
 endif.
 catch cx_root.
 lr_current_entity ?= lr_iterator->get_next( ).
 lr_entity ?= ir_valuehelp_collection->get_next( ).
 endtry.
 endwhile.

Now this code serves two purposes

a) It handles the exception hence there would not be any disruption in WebUI.

b) In case of exception occurs , there is a handling in that case.

Some of these guidelines may appear didactic but in reality they help in avoiding embarrassing code mishaps.

Hi friends,

I am CRM developer in SAP and our team has already integrated twitter ( also facebook ) into interaction center in CRM7.0 EHP3.

You can see an example below:

Create a tweet in twitter website:

Now I can see the tweet created just now in the web site.

And I can also see it in CRM IC agent inbox:

select the first row and I can directly reply it in CRM by clicking reply button:

just click the send button:

after click send button, I can see the reply also in twitter website:

if you would like to integrate other social channel than twitter and facebook, you just have to implement your own client class for the new social channel, and all left tasks are centrally done by us from framework side.

you can get more detail information from consulting note 1832462 about social integration achitecture. Implementation detail for facebook client class: note 1832481. And note 1832480 for twitter.

Welcome to post any questions you have here if you are interested with this topic.

Hi All,

This one takes us back to the basics of CRM, power of text determination procedure. We have been using notes in CRM transactions very
frequently to capture various texts entered by different Users during the process. Through this blog I am trying to showcase one of the old features
available in text determination procedures i.e. access sequence to source the content in the note type.

In my recent project, I got a requirement from customer where they wanted a default text to appear in the notes. As this note type was to be
used for printing CRM generated letter, it was acting as template for the letter and also it was supposed to be changeable by user during the process and
the changed version of the template should go for printing. As this criteria came into picture, we couldn’t just create a smartform with hardcoded text
instead found the standard way to find solution.

Access sequence in text determination procedure can be used in this case.

Following are the steps to make this work:

1. Create the text template using SAPscript Tcode SO10

  Maintain the default text here:

2.  Create you text determination procedure and create access sequence for the text type for which the default text has to be sourced:

3. The function has to be created by technical team which has a small code for calling the SAPscript created in step 1:

Function ZFM_UPLOAD_TEXT

CLEAR: es_reference.

  es_reference-tdobject = 'TEXT'.

  es_reference-tdid = 'ST'.

  es_reference-tdname = 'ZTEMPLATE'.

  es_reference-tdspras = 'E'.

Endfunction.

4. Once the access sequence is created, assign this access sequence to the text type:

Leave the changes column as empty as you want it to be editable and select value “A” in transfer column for this text type.

That’s it. When this procedure is assigned to a transaction and when user creates the transaction, the default text appears in the
respective note type (text type) which can be changed by user.

A small configuration changed helped us in meeting the requirement. Thought of sharing this as a lot of us sometimes miss these
excellent features available as part of std CRM.

Hope you enjoyed revisiting the basics. sometimes it really helps.

  method DO_CONFIG_DETERMINATION.  " IF search result view should be hidden     me->set_config_keys( iv_object_type          = 'CRM_SMC'                          iv_propagate_2_children = abap_false ).  " ENDIF  endmethod.

Hi Friends,

recently I am working on one project which will make use of CRM content management. We will extract data from external web site and store them into CRM  system.

I will put something which I think is worth sharing to a series of blogs here. I hope they can help.

1. how to put the attachment view in a pop up window

2. how to dynamically control the enablement of attachment maintenance

3. how to create attachment for your business object via code

4. how to delete attachment belonging to a business object via code

5. how is attachment physically stored in database table

6. how to make your custom developed business object type also support content management - see note 1710485.

7. technical detail for attachment attributes

8. display thumbnail in CRM UI with the help of attachment

9. internal mode for Attachment creation

10. change CREATED_BY property by code

11.  the more to be added soon..

If you want to know more technical detail, please find my blog list here.

History:

Content Management(CM) was introduced in basis release 6.10 and implemented in CRM 3.0. Before CM was used, CRM applications was using the Business Document Service (BDS) or Generic Object Services (GOS) to implement Document management requirement. BDS was used in most applications like Business partners, products, product catalogues, solution database, campaigns. GOS was only used in the One Order objects like activities and opportunities. All BDS applications changed to CM in 3.0, the One Order objects only in 3.1.

A document in CM consists of several objects. The most important two are so called “logical info object” (LOIO) and a “physical info object” (PHIO). A LOIO as a logical folder or bracket which holds PHIOs together, while a PHIO represents the content of a specific version of a document. Let's use the word edit in the real world as example. If one works on a Word document and changes the document over time, each saved version would be represented by a PHIO. The LOIO would be the word document itself. This is much like if one looks at SE38 in ABAP: The program name is the LOIO and each transported version of the code is the PHIO.

Let's see an example. I have a product ZCM_DEMO with guid 0090FA0D8DC21ED395FD7C687F99BFF7, BOR type = BUS1178.

I create one attachment for it:

Go to table SKWG_BREL, input product guid 0090FA0D8DC21ED395FD7C687F99BFF7, and we see two entries belonging to this product. The first entry indicates a folder instance which is actually a logical container to hold all attachments for the given product. 

The content of column INSTID_B has naming convention as <type: F(older) or L(ogical object)><Logical object type name><guid>.

The guid in the first row can be found in table CRM_FOLDER:

The guid 0090FA0D8DC21ED395FD830F8DD9DFFF in the second row can be found in table BDSLOIO22, together with the name of attachment.

You are asking how I get to know the name of table BDSLOIO22? If one application wants to use CM to store document, it should have its dedicated class for physical object and logical object, or use the default one CRM_L_DOC. The relationship between application and its class is maintained in tcode DMWB:

in table BDSPHIO22, by specifying logical information object ID, we can get all phyiscal object lists.

once you get phyical object id 0090FA0D8DC21ED395FD830F8DD9FFFF, you can find the respective entries in table BDSCONT22.

The real content of attachment is stored in a claster way, so you cannot see its detail in SE16.

How do I know the database table name BDSCONT22?

1. Get the storage category BDS_DB22 by physical class name.

2. execute function module SCMS_SDOKSTRE_LIST to get all lists of database table. Then you can find the table name BDSCONT22 for your storage category BDS_DB22.

For a complete list of my blogs regarding content management in CRM, please seehere.

In the beginning I consider it is very easy to delete attachments via code, just like below.

I have defined one method with following two importing parameters:

iv_bor_type type string - the BOR type of your business object

iv_uuid type raw16 - the guid of your business object instance

rv_successful type abap_bool - indicates whether the deletion is successful

          lt_loios    TYPE SKWF_IOS,          ls_loios    TYPE SKWF_IO,          ls_error    TYPE SKWF_ERROR,          lt_badios   TYPE SKWF_IOERRS,          lv_del_flag TYPE ABAP_BOOL.    ls_bo-instid = iv_uuid.    ls_bo-typeid = iv_bor_type.    ls_bo-catid  = 'BO'.    rv_successful = abap_false.    CALL METHOD cl_crm_documents=>get_info      EXPORTING        business_object = ls_bo      IMPORTING        loios           = lt_loios.    LOOP AT lt_loios INTO ls_loios.      CALL METHOD cl_crm_documents=>lock        EXPORTING          is_bo    = ls_bo          is_loio  = ls_loios        IMPORTING          es_error = ls_error.      IF ls_error IS NOT INITIAL.         RETURN.      ENDIF.    ENDLOOP.    CALL METHOD cl_crm_documents=>delete      EXPORTING         business_object = ls_bo         ios             = lt_loios      IMPORTING         bad_ios         = lt_badios         error           = ls_error.    IF ls_error IS INITIAL. " deletion failed       rv_successful = abap_true.    ENDIF.

Through testing I found it works perfectly well with most of BOR type like product, ibase, BP, and one order.

However, it does not work for my new BOR type CRMSOCPOST in CRM7.0 EHP3 - the relationship between my bo and the attachments is not really deleted until

an explicit call COMMIT WORK is written in the report. However, for any other standard CRM BOR type, the COMMIT WORK is not needed. Why?

After some debugging finally I find answer. Have you already observed the comments below? It is written quite clearly: if the business object exists in the database, the COMMIT WORK is not needed.

Back to my case, since CRMSOCPOST is a new BOR type created in CRM7.0 EHP3, the function module does not recoginize it, so the code reached line 225, and

then the bo instance is regarded as non-exist in DB. So an explicit COMMIT WORK is always necessary to make deletion work.

For a complete list of all my blogs regarding content management, please seehere.

When you create attachments for your business objects via cl_crm_documents=>create_with_table, you have to pass in an internal table for attachment property.
The namelist of attribute name could be got from attachment class via function module SDOK_PHIO_ATTRIBUTES_GET.

For example, attachment class CRM_P_DOC has 36 attributes.

The attributes could also be viewed in tcode DMWB

The actual attribute value could be got via function module CRM_KW_PROPERTIES_GET:

The importing parameters are guid of logical/physical object instances:

The attribute values are stored in PROPERTIES internal table.

Do you know why in the backend table, the property is stored in field PROP09?

actually it is because I hard code the content of relative url as the attachment file name.

    ls_prop-name = 'KW_RELATIVE_URL'.

    ls_prop-value = iv_file_name.

    APPEND ls_prop TO lt_prop.

The index of attribute could also be found in tcode DMWB.

  Yesterday when I am doing my development under interaction center environment, I suddenly find I cannot log on interaction center UI any more.

After I choose my business role ZSOCIAL, the UI hangs there with only information "Starting". Ten minutes later, I got a time out error in UI.

I did a quick check on my development objects and I can ensure this is not caused by my new development. I checked SM21 and SM50 and could not find any hints.

So again I have to debug to find the root cause. But where should I set breakpoint? Since in principle the component set for IC CRMIC_DEFAULT will always be loaded when IC UI is launched, it will be a good starting point to set breakpoint in method CL_CRM_BOL_CORE=>load_component_set. Soon I found the application will hang once that method is called, so I know I am not far from the truth.

In this customizing you can find all components belonging to component set CRMIC_DEFAULT.

The timeout must come from loading one of these components.

Finally I found the component ERP is the trouble maker. The system hangs after I click F6 in line 101.

The root cause is that RFC destination EBJCLNT001 does not work, so RFC call hangs until time out occurred.

This RFC destination is maintained in this customizing:

For a complete list of all my blogs regarding content management, please see here.

During my recent project I found a strange behavior in attachments.

Click the hyperlink of Properties

do not change anything, and click back

After back to product overview page, the overview page looks exactly the same before you click Property hyperlink.

However, if you use SM12 to check in backend, you will find the current product is locked, although it still looks as under display mode in UI!

The same behavior could be observed in one order application. I would assume this as a bug.

By debugging I found the parent node, Product instance, is explicitly locked by content management class.

However, in my application I do not need this behavior - in my application, the whole attachment assignment block has read only mode, so I don't want my BO to be locked after property hyperlink is clicked. The solution is very easy: do not bind my BO node to PARENTNODE of content management UI component GS_CM by commenting out the related code:

For a complete list of all my blogs regarding content management, please seehere.

In CRM Product UI, A thumbnail could be displayed in Product header and Thumbmail assignment block.

The Thumbnail assignment block is not available in SAP predefined UI configuration. Customer needs to manually make it visible via UI configuration change:

The thumbnail view implementation itself is very simple, just use the lib thtmlb image tag.

The thumbnail view implementation itself is very simple, just use the lib thtmlb image tag.

If a product has multiple attachments, how does the UI know which one should be displayed as thumbnail? The default attachment with type BDS_IMAGE will be choosen.

However, these two fields are not available in default standard configuration of GS_CM/EditProp

if your application need also allow users to specify these two fields, you can create a new configuration by copying from the one with object type = PRD_MATSRV.