Varad
1: Opening CRM Request in another window (SAP ABAP CRM Tips)
At the point when there is a prerequisite to open a CRM Request (Client Request. Administration Request. and so forth) from a program, the typical interaction is to populate the Business Item Boundary (CRM_OBJECT_ID) with the Exchange Number (OBJECT_ID) and afterward doing a CALL Exchange to CRMD_ORDER. Be that as it may, this technique doesn’t appear to work.
Befuddled? How to Debug any Work Item in SAP Workflow?
SET Boundary ID ‘CRM_OBJECT_ID’ FIELD .
CALL Exchange ‘CRMD_ORDER’ AND Skirt FIRST SCREEN.
It won’t get into the exchange (CRM Request) , however stop at the inquiry screen.
The strategy for getting around could be utilizing the BAPI BAPI_BUSPROCESSND_DISPLAY to show the CRM Request. You can utilize it to show the CRM Request screen straightforwardly. Simply pass your Request Header GUID ID to the business cycle and the CRMD_ORDER screen will be shown.
CALL FUNCTION 'BAPI_BUSPROCESSND_DISPLAY' EXPORTING business_process = <order_header_guid>
2: Embedding or Erasing Standard/Custom messages in CRM GUI.(SAP ABAP CRM Tips)
If conceivable, you can follow the accompanying advances.
a) First delete message, for example
* Deleting the messages from stack
CALL FUNCTION 'CRM_MESSAGES_DELETE' EXPORTING iv_caller_name = gc_object_name-order iv_ref_object = iv_item it_r_msgidno = lt_idno EXCEPTIONS OTHERS = 1.
b) Check for corresponding message text already exists or not, for example
CALLFUNCTION'CRM_TEXT_READ_API' EXPORTING it_guid = lt_object_guids iv_object_kind = gc_object_kind-orderadm_i IMPORTING et_text = lt_text.
OR
Search the corresponding messages, for example:
ls_idno-sign = 'I'. ls_idno-option = 'EQ'. ls_idno-low-msgid = 'Z_ZZZ_CA_MESSAGES'. ls_idno-low-msgno = '126'. APPEND ls_idno TO lt_idno. CALL FUNCTION 'CRM_MESSAGES_SEARCH' EXPORTING it_r_msgidno = lt_idno iv_ref_object = iv_header_guid iv_ref_kind = gc_object_kind-orderadm_h iv_only_errors_on_object = true IMPORTING et_msg_info = lt_msg_info EXCEPTIONS appl_log_error = 1 error_occurred = 2 OTHERS = 3.
c) If the message does not exist. Then raise message. For example
CALLFUNCTION'CRM_MESSAGE_COLLECT'
EXPORTING
iv_caller_name = gc_object_name-order
iv_ref_object = iv_item
iv_ref_kind = gc_object_kind-orderadm_i
iv_logical_key = 'MAINTAIN'
iv_msgno = lv_msgno
iv_msgid = 'CRM_ORDERADM_I'
iv_msgty = lv_msgty
EXCEPTIONS
not_found = 1
appl_log_error = 2
OTHERS = 3.
YOU MAY LIKE THIS
Conquering the Full Stack Developer Interview: Essential Questions and Expert Tips
Cracking the Code: Your Earning Potential as a SAP ABAP Developer with 5 Years of Experience
