zoukankan      html  css  js  c++  java
  • SAP CRM Advanced search和Simple search里Max hit表现行为的差异

    We could observe the different behavior of search max hits in product advanced search and simple search.
    For Advanced search: if we maintain an invalid max hit number:

    the default 100 could automatically be restored:

    However this is not possible in simple search view. After an invalid max hit is typed, the error message is displayed, but the invalid content is still there.

    The reason is the max hit field in Simple search is implemented via a pure input field, and conversion exception occurs here:

    The exception information is written into the error message internal table:

    And the rendering logic for inputField is, if there is an invalid content typed by end user (line 66), the invalid content will be kept in UI ( line 79)

    And the logic in method is_attribute_valid in line 66 is just check whether the error message table in errors variable ( type cl_bsp_messages) is empty or not.

    The solution for the max hit in simple search:

    Since the design to use inputField as max hit could not be changed, however we could still change the implementation in method CL_PRDIOQR_ESSEARCH_CN00~SET_MAX_HITS: if method if_bsp_model_util~convert_from_string is NOT used, the framework handling for inputField will NOT set the invalid flag any more.

    要获取更多Jerry的原创文章,请关注公众号"汪子熙":

  • 相关阅读:
    More than 100 ABAP Interview Faq's
    SAP所有模块用户出口(User Exits)
    机器巡检基本知识
    SAP常用词汇
    ERP系统模块完全解析──工作中心
    abap基础
    topas命令详解
    企业如何处理制度、ISO质量体系与ERP系统的冲突
    在ALV表格中双击某一行记录后,显示明细记录
    Linux 命令修改图片尺寸!
  • 原文地址:https://www.cnblogs.com/sap-jerry/p/13619234.html
Copyright © 2011-2022 走看看