SAP AFX_MSG_OPEN Function Module for

Search SAP Function Modules

AFX_MSG_OPEN is a standard afx msg open SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for afx msg open FM, simply by entering the name AFX_MSG_OPEN into the relevant SAP transaction such as SE37 or SE38.

Function Group: AFX_MESSAGE_GLOBAL
Program Name: SAPLAFX_MESSAGE_GLOBAL
Main Program: SAPLAFX_MESSAGE_GLOBAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AFX_MSG_OPEN pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'AFX_MSG_OPEN'"
  EXPORTING
   I_PROG =  "Application log: Program name
   I_LOG_OBJECT_STD =  "Application log: Object name (Application code)
   I_LOG_OBJECT_EXC =  "Application log: Object name (Application code)
   I_LOGNUMBER =  "Application Log: External ID
   I_LOG_PERIOD =  "
   I_LOG_PERIOD_UNIT =  "

 IMPORTING
   E_MSG_HANDLE_STD =  "Message object identification
   E_MSG_HANDLE_EXC =  "Message object identification

EXCEPTIONS
   LOG_INIT_FAILED_STD = 1    LOG_INIT_FAILED_EXC = 2 

.

IMPORTING Parameters details for AFX_MSG_OPEN

I_PROG - Application log: Program name

Data type: BALPROG
Optional: No
Call by Reference: Yes

I_LOG_OBJECT_STD - Application log: Object name (Application code)

Data type: BALOBJ_D
Optional: No
Call by Reference: Yes

I_LOG_OBJECT_EXC - Application log: Object name (Application code)

Data type: BALOBJ_D
Optional: No
Call by Reference: Yes

I_LOGNUMBER - Application Log: External ID

Data type: BALNREXT
Optional: No
Call by Reference: Yes

I_LOG_PERIOD -

Data type: AFX_DTE_APPLLOG_PERIOD
Optional: No
Call by Reference: Yes

I_LOG_PERIOD_UNIT -

Data type: AFX_DTE_APPLLOG_PERIOD_UNIT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for AFX_MSG_OPEN

E_MSG_HANDLE_STD - Message object identification

Data type: EMSG_HANDL
Optional: No
Call by Reference: Yes

E_MSG_HANDLE_EXC - Message object identification

Data type: EMSG_HANDL
Optional: No
Call by Reference: Yes

EXCEPTIONS details

LOG_INIT_FAILED_STD -

Data type:
Optional: No
Call by Reference: Yes

LOG_INIT_FAILED_EXC -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for AFX_MSG_OPEN Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM AFX_MSG_OPEN

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects