Skip to Content
author's profile photo
Former Member

Custom Messages Long Text not appearing

Hi Everybody!

We are having a problem displaying the long text of custom messages.

After we click on the "More Information" link beside the message short text, we should get a pop-up message with the long text.

Instead, we get a pop-up message showing an internet explorer 400 error.

We are OK displaying long text of standard messages. Should we do something extra to display long text of custom messages?

Thanks

Gabriel

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • author's profile photo
    Former Member
    Posted on Aug 15, 2007 at 05:44 PM

    Hi

    Have you tried using BBP_DOC_CHECK_BADI to issue customer messages ?

    Regards

    - Atul

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Atul,

      Regarding the long-text option, yes, I have marked: The "Self-Explanatory" checkbox is not checked.

      Here is the source code!

      ** VARIABLES **
        DATA: t_partner          TYPE TABLE OF bbp_pds_partner,
              x_partner          TYPE bbp_pds_partner,
              u_vendor_set       TYPE TABLE OF bbp_vendor_getlist_s,
              x_vendor_set       TYPE bbp_vendor_getlist_s,
              w_xfeld            TYPE xfeld,
              e_message          TYPE bbp_smessages_badi,
              w_guid_crmt_object TYPE crmt_object_guid,
              w_guid_bbp_guid    TYPE bbp_guid,
              w_partner_no       TYPE  bu_partner_guid,
              w_nombre           TYPE bdl_logfun,
              w_process          TYPE bbp_proc_type,
              w_status           TYPE xfeld,
              w_header           TYPE bbp_pds_po_header_d.
      
          CALL FUNCTION 'BBP_PD_PO_GETDETAIL'
            EXPORTING
              i_guid          = iv_doc_guid
              i_with_itemdata = 'X'
            IMPORTING
              e_header        = w_header
            TABLES
              e_partner       = t_partner.
      
          IF iv_cv_updated_active_doc = space.
            w_guid_bbp_guid   = iv_doc_guid.
            w_guid_crmt_object = w_guid_bbp_guid .
      
            LOOP AT t_partner INTO x_partner WHERE partner_fct = '00000019'.
      
              w_partner_no = x_partner-partner_no.
      
      *     This function check if the partner is valid.
              CALL FUNCTION 'Z_BC_BLOQ_GET'
                EXPORTING
                  iv_bu_partner_guid = w_partner_no
                IMPORTING
                  ev_xfeld           = w_xfeld.
      
              IF w_xfeld IS NOT INITIAL.
      
      *  Get the name of the vendor.
                CALL FUNCTION 'BBP_VENDOR_GETINFO'
                  EXPORTING
                    partner_guid       = w_partner_no
                    x_with_name        = 'X'
                    x_show_inv_parties = 'X'
                    purch_pd_org_type  = 'O'
                  TABLES
                    vendor_set         = u_vendor_set.
      
                READ TABLE u_vendor_set INTO x_vendor_set INDEX 1.
      
                CLEAR e_message.
                e_message-msgty   = 'A'.
                e_message-msgid   = 'ZSRM_ERRORES'.
                e_message-msgno   = '005'.
                e_message-msgv1   =  x_vendor_set-partner.
                e_message-msgv2   =  x_vendor_set-vendor_name.
                e_message-msgv3   =  x_vendor_set-vendor_no.
                APPEND e_message TO et_messages.
              ENDIF.
              CLEAR x_partner.
      
            ENDLOOP.
      
        ENDIF.
      
      ENDMETHOD.