SAP FRE_MESSAGE_DB Function Module for Database Access to Table FRE_ORD_UI_MSG
FRE_MESSAGE_DB is a standard fre message db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Database Access to Table FRE_ORD_UI_MSG processing and below is the pattern details for this FM, 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 fre message db FM, simply by entering the name FRE_MESSAGE_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: FRE_ORDER_DB
Program Name: SAPLFRE_ORDER_DB
Main Program: SAPLFRE_ORDER_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FRE_MESSAGE_DB 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 'FRE_MESSAGE_DB'"Database Access to Table FRE_ORD_UI_MSG.
EXPORTING
MODE = "Insert 'I', Delete 'D', Update 'U'
* NO_COMMIT = "'X' = No DB Commit
TABLES
MESSAGES = "F&R CON R/3 - Messages for User Interface (Order In & Out)
EXCEPTIONS
DATABASE_ERROR = 1 WRONG_MODE = 2 FOREIGN_LOCK = 3
IMPORTING Parameters details for FRE_MESSAGE_DB
MODE - Insert 'I', Delete 'D', Update 'U'
Data type: CHAR1Optional: No
Call by Reference: Yes
NO_COMMIT - 'X' = No DB Commit
Data type: CHAR1Optional: Yes
Call by Reference: Yes
TABLES Parameters details for FRE_MESSAGE_DB
MESSAGES - F&R CON R/3 - Messages for User Interface (Order In & Out)
Data type: FRE_UI_MSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
DATABASE_ERROR - Database Access Error
Data type:Optional: No
Call by Reference: Yes
WRONG_MODE - Mode contains wrong value
Data type:Optional: No
Call by Reference: Yes
FOREIGN_LOCK - Table already locked
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FRE_MESSAGE_DB 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.DATA: | ||||
lv_mode | TYPE CHAR1, " | |||
lt_messages | TYPE STANDARD TABLE OF FRE_UI_MSG, " | |||
lv_database_error | TYPE FRE_UI_MSG, " | |||
lv_no_commit | TYPE CHAR1, " | |||
lv_wrong_mode | TYPE CHAR1, " | |||
lv_foreign_lock | TYPE CHAR1. " |
  CALL FUNCTION 'FRE_MESSAGE_DB' "Database Access to Table FRE_ORD_UI_MSG |
EXPORTING | ||
MODE | = lv_mode | |
NO_COMMIT | = lv_no_commit | |
TABLES | ||
MESSAGES | = lt_messages | |
EXCEPTIONS | ||
DATABASE_ERROR = 1 | ||
WRONG_MODE = 2 | ||
FOREIGN_LOCK = 3 | ||
. " FRE_MESSAGE_DB |
ABAP code using 7.40 inline data declarations to call FM FRE_MESSAGE_DB
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