SAP CRM / CS Supports

Symptom

For security reasons, you can only send certain types of files to SAP. We will reject any other attachments that are sent to us.

Other terms

Solution Manager, attachment, support message, CRM 5.0

Reason and Prerequisites

Implementation and security checks
Solution

Information messages cannot be transferred to the CRM application log in standard CRM 5.0 systems and subsequent releases.
A solution can only be implemented as part of a customer-specific project.
The following steps are necessary for the correction. See Note 83020 because they constitute a modification.
After you have implemented the following program changes manually and configured Customizing, information messages are written in the CRM application log.
Proceed as follows:
1. In transaction SE80, package CRM_DNO make the following program changes:
—————————————————————–
Generate a new BAdI implementation in the customer namespace by copying the BAdI implementation ‘CRM_DNO_SEND_TO_SAP’.
Make the following program changed in the “Execute” method of your new BAdI implementation:
Define the variables.
DATA: ls_message_return TYPE bapireturn1.
DATA: lt_message_return TYPE TABLE OF bapireturn1 INITIAL SIZE 0.
DATA: l_application_log TYPE BALLOGHNDL.
Define the INCLUDE.
INCLUDE crm_object_names_con.
For the generation of entries in the application log,
Replace
———————————————-
IF NOT lv_rcode IS INITIAL.
CALL FUNCTION ‘DNO_SAP_EVALUATE_RCODE’
EXPORTING
i_rcode = lv_rcode
IMPORTING
e_message1 = lv_message1
e_message2 = lv_message2
e_message3 = lv_message3.
MOVE ‘DNO’ TO ls_s_msg-msgid.
MOVE ‘I’ TO ls_s_msg-msgty.
MOVE ‘159′ TO ls_s_msg-msgno.
MOVE lv_message1 TO ls_s_msg-msgv1.
MOVE lv_message2 TO ls_s_msg-msgv2.
MOVE lv_message3 TO ls_s_msg-msgv3.
CALL FUNCTION ‘BAL_LOG_MSG_ADD’
EXPORTING
i_log_handle = ip_application_log
i_s_msg = ls_s_msg.
ENDIF.
———————————————-
with:
———————————————-
IF NOT lv_rcode IS INITIAL.
CALL FUNCTION ‘DNO_SAP_EVALUATE_RCODE’
EXPORTING
i_rcode = lv_rcode
IMPORTING
e_message1 = lv_message1
e_message2 = lv_message2
e_message3 = lv_message3
TABLES
message_return = lt_message_return.
MOVE ‘DNO’ TO ls_s_msg-msgid.
MOVE ‘I’ TO ls_s_msg-msgty.
MOVE ‘159′ TO ls_s_msg-msgno.
MOVE lv_message1 TO ls_s_msg-msgv1.
MOVE lv_message2 TO ls_s_msg-msgv2.
MOVE lv_message3 TO ls_s_msg-msgv3.
CALL FUNCTION ‘BAL_LOG_MSG_ADD’
EXPORTING
i_log_handle = ip_application_log
i_s_msg = ls_s_msg.
IF NOT lt_message_return[] IS INITIAL.
LOOP AT lt_message_return INTO ls_message_return.
CLEAR: ls_s_msg-msgv1,
ls_s_msg-msgv2.
MOVE ls_message_return-id TO ls_s_msg-msgid.
MOVE ls_message_return-type TO ls_s_msg-msgty.
MOVE ls_message_return-number TO ls_s_msg-msgno.
MOVE ls_message_return-message_v1 TO ls_s_msg-msgv1.
MOVE ls_message_return-message_v2 TO ls_s_msg-msgv2.
CALL FUNCTION ‘BAL_LOG_MSG_ADD’
EXPORTING
i_log_handle = l_application_log
i_s_msg = ls_s_msg.
IF ls_s_msg-msgno = ‘123′ AND ls_s_msg-msgid = ‘DNO’.
CALL FUNCTION ‘CRM_MESSAGE_COLLECT’
EXPORTING
iv_caller_name = gc_object_name-orderadm_h
iv_ref_object = lv_header_guid
iv_msgno = ‘123′
iv_msgid = ‘CRM_DNO’
iv_msgty = ‘I’
iv_msgv1 = ls_s_msg-msgv1
iv_msgv2 = ls_s_msg-msgv2
EXCEPTIONS
not_found = 1
appl_log_error = 2
OTHERS = 3.
ENDIF.
ENDLOOP.
ENDIF.
ENDIF.
———————————————-
2. Create a new message:
————————–
- Call transaction SE91 and open message number 123 for message class CRM_DNO in change mode.
- Enter the text “Attachment with file type &1 cannot be sent” and ensure that the “Self-Explanatory” indicator is not set.
- Choose “Long Text” and enter the following long text: “For security reasons, you can only send certain types of file to SAP; all other attachments that are sent to SAP will be rejected.”
- Save your changes.
3. Change the save attributes of the information message in the table CRMC_MESSAGES_S:
——————————————————————
- Call transaction SM30 for the view CRMV_MESSAGES_S:
- Choose “Create/Change” to change the following message:
ARBGB: CRM_DNO
MSGNR: 123
MSGSAVE: X
4. Create the new action ‘SEND_TO_SAP’ in the customer namespace:
———————————————————-
- Call transaction SPPFCADM.
- Choose “Define Action Profiles and Actions” for the application CRM_ORDER.
- In the action profile “SLFN0001_STANDARD” (or in your custom profile), copy the standard action definition to create your custom action definition for “SEND_TO_SAP”. The action conditions are not copied when you copy the standard action definition. You must create these in the same way as for the standard action definition.
- Assign your new BAdI implementation “CRM_DNO_SEND_TO_SAP” to the new action definition.
- You must now activate your new action definition and deactivate the standard action definition.