Type copyright symbol text message code#

Once you would have this, ZFLC_ERROR_POPUP should display correctly the message with 7 parameters. 'This is message with parameters A, B, C, D, E, F and G' 'This is message with parameters A, B, C, D, &, & and &'Īfter that call, the LR_MSG-MESSAGE will contain: ZFLC_ERROR_SET lr_msg 'E' 'ZABC' 20 'A' 'B' 'C' 'D'.Īfter this call, LR_MSG-MESSAGE field will contain the following text: ZABC 020 'This is message with parameters &, &, &, &, &, & and &' Let us assume that we have the message with 7 parameter holders: You could develop ZFLC_ERROR_UPDATE ABAP macro that could populate parameters 5, 6. The same popup window will appear if we would change Function Module/ABAP Form Name parameter from ZAWB_SOHDR_GET1 ABAP Form name to* ZAWB_SOHDR_GET2* Function Module name.Īs described in this paper, the message was formatted by ZFLC error macros and ZFLC_ERROR_SET function module from messages, with special formatting strings, defined in SE91 message class: Now let us execute the ZAWB_TEST_MESSAGE test program as shown on the following screen:Ĭlick on the Execute button. If not &1-type is initial and &2 cs &1-type.Ĭoncatenate ‘Message:’ sy-title into sy-title The error message is displayed by ZFLC_ERROR_POPUP macro defined in ZFLC_ERROR_M include and shown in the following table:

Type copyright symbol text message code#

The function module source code is shown in the following table: The ZFLC_ERROR_SET macro calls ZFLC_ERROR_SET function module that formats message processing message extension strings #. If sales order is not found, the ZAWB_SOHDER_GET1 ABAP Form sets the error message in xr_msg BAPIRET2 structure using ZFLC_ERROR_SET macro defined in ZFLC_ERROR_M include and shown in the following table: The ZAWB_SOHDER_GET1 ABAP Form is shown in the following table: &1 ” BAPIRET2^ message object e.g., lr_msg The ZFLC_ON_ERROR_SY_SET macro source code defined in ZFLC_ERROR_M include is shown in the following table:

CALL FUNCTION ‘ZAWB_SOHDR_GET2’ EXPORTING uc_vbeln = p_vbeln IMPORTING xr_vbak = gr_vbak EXCEPTIONS invalid_so_num = 1 OTHERS = 2. The calling program converts SY structure error parameters to gr_msg BAPIRET2 structure calling ZFLC_ON_ERROR_SY_SET macro as shown in the following table: If sales order is not found, the ZAWB_SOHDER_GET2 Function Module raises exception. MESSAGE ID ‘ZAWB’ TYPE ‘E’ NUMBER 18 WITH uc_vbeln The above program tries to retrieve the sales order header record using ZAWB_SOHDER_GET1 ABAP Form or ZAWB_SOHDR_GET2 Function Module shown in the following table: Zflc_error_set xr_msg ‘E’ ‘ZAWB’ 18 uc_vbeln ” ” ”. SELECT SINGLE * INTO xr_vbak FROM vbak WHERE vbeln = uc_vbeln. Xr_vbak TYPE vbak ” sale order header record Zawb_sohdr_get1 ” get sales order header record PERFORM zawb_sohdr_get1 USING p_vbeln gr_vbak gr_msg. REPORT zawb_test_message.INCLUDE zflc_error_m.PARAMETERS: p_func TYPE char20 DEFAULT ‘zabc_sohdr_get1’ LOWER CASE, p_vbeln TYPE vbeln DEFAULT ‘4981’.DATA: gr_vbak TYPE vbak, gr_msg TYPE bapiret2.START-OF-SELECTION. Let us write the ZAWB_TEST_MESSAGE test program as shown in the following table: The ‘#021’ string at the end of the message 019 indicates that the message 021 should be appended at the end of the message 019.Īdditionally, the ‘|’ character is used as the line break. The ‘#019’ string at the end of the message 018 indicates that the message 019 should be appended at the end of the message 018. The messages 018 and 019 end up with the continuation string, in # format, that points to the next message to be appended. There are 3 messages 018, 019 and 021 defined above. Let us define the following messages in SE91: You could display up to 200 characters long message using SE91 message class short text.