Skip to Content

Why does the navigation after clicking email hyperlink not happen in Account search result

Issue description

In Account search result view, by clicking the email hyperlink,

/wp-content/uploads/2015/12/clipboard1_850265.png

 

we expected that there is a navigation to email creation view:

/wp-content/uploads/2015/12/clipboard2_850266.png

However in some system, after clicking email hyperlink, nothing happens.

Issue Analysis

1. Select one row in search result, click F2 to review technical information, and get the UI component name BP_HEAD_SEARCH.

2. Open the component via tcode BSP_WD_CMPWB, check the email hyperlink implementation by double clicking GET_P_EMAIL

/wp-content/uploads/2015/12/clipboard3_850267.png

3. From the p getter implementation, we get to know the logic that once it is clicked, the event handler and the outbound plug TOEMAIL will be triggered.

/wp-content/uploads/2015/12/clipboard4_850268.png

4. Then we can double click on OP_TOEMAIL and set breakpoint there to start debug.

/wp-content/uploads/2015/12/clipboard5_850269.png

I launch two debuggers separately in system AG3 ( where navigation works ) and K9E ( where navigation fails ) to compare the execution logic.

4.1 The navigation execution in K9E terminates due to the failure of check in line 37. So I have to check why lt_proc is empty after line 34.

/wp-content/uploads/2015/12/clipboard6_850270.png

 

4.2 When I debug into the method in 4.1, it is because is_navigation_supported returns false for process type 0005.

/wp-content/uploads/2015/12/clipboard7_850271.png

4.3 Within method IS_NAVIGATION_SUPPORTED, first the UI object type is determined in method 38.

/wp-content/uploads/2015/12/clipboard8_850272.png

In system AG3, the result is BT126_MAIL, and for K9E it is CRM_ICM_EMAIL. This difference is caused by the different business switch status as displayed in line 183 and 184 below.

/wp-content/uploads/2015/12/clipboard9_850273.png

The reason why the navigation works in AG3: it successfully finds a navigation target from internal table gt_map_infos for UI object type BT126_MAIL.

/wp-content/uploads/2015/12/clipboard10_850274.png

The found navigation target:

/wp-content/uploads/2015/12/clipboard11_850275.png

This target is maintained in customizing below:

/wp-content/uploads/2015/12/clipboard12_850276.png

/wp-content/uploads/2015/12/clipboard13_850277.png

But in system K9E, the different UI object type CRM_ICM_EMAIL is used, and the corresponding customizing for its navigation target is missing, so the navigation does not work.

/wp-content/uploads/2015/12/clipboard14_850278.png

After the necessary navigation customizing is added, the navigation in K9E also works.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.