SAP TB_POSTING_MESSAGE_STORE Function Module for Flag Error Message in the Posting Interface









TB_POSTING_MESSAGE_STORE is a standard tb posting message store SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Flag Error Message in the Posting Interface 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 tb posting message store FM, simply by entering the name TB_POSTING_MESSAGE_STORE into the relevant SAP transaction such as SE37 or SE38.

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



Function TB_POSTING_MESSAGE_STORE 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 'TB_POSTING_MESSAGE_STORE'"Flag Error Message in the Posting Interface
  EXPORTING
   DEAL =  "Transaction
*  MSGV4 = ' ' "Message variable 4
   FLG_DEAL =  "Meldung zum Geschäft(X); zur Bewegung(sonst)
*  FLOW =  "Flow
   MSGID =  "Message ID
   MSGNO =  "Message Number
   MSGTY =  "Message Type
*  MSGV1 = ' ' "Message variable 1
*  MSGV2 = ' ' "Message variable 2
*  MSGV3 = ' ' "Message variable 3

TABLES
   MSGPOST =  "Tabelle der Messages
.



IMPORTING Parameters details for TB_POSTING_MESSAGE_STORE

DEAL - Transaction

Data type: VTBFHA
Optional: No
Call by Reference: No ( called with pass by value option)

MSGV4 - Message variable 4

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FLG_DEAL - Meldung zum Geschäft(X); zur Bewegung(sonst)

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

FLOW - Flow

Data type: VTBFHAPO
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGID - Message ID

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MSGNO - Message Number

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MSGTY - Message Type

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MSGV1 - Message variable 1

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGV2 - Message variable 2

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGV3 - Message variable 3

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TB_POSTING_MESSAGE_STORE

MSGPOST - Tabelle der Messages

Data type: VTBMSGPOST
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for TB_POSTING_MESSAGE_STORE 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_deal  TYPE VTBFHA, "   
lt_msgpost  TYPE STANDARD TABLE OF VTBMSGPOST, "   
lv_msgv4  TYPE VTBMSGPOST, "   SPACE
lv_flg_deal  TYPE VTBMSGPOST, "   
lv_flow  TYPE VTBFHAPO, "   
lv_msgid  TYPE VTBFHAPO, "   
lv_msgno  TYPE VTBFHAPO, "   
lv_msgty  TYPE VTBFHAPO, "   
lv_msgv1  TYPE VTBFHAPO, "   SPACE
lv_msgv2  TYPE VTBFHAPO, "   SPACE
lv_msgv3  TYPE VTBFHAPO. "   SPACE

  CALL FUNCTION 'TB_POSTING_MESSAGE_STORE'  "Flag Error Message in the Posting Interface
    EXPORTING
         DEAL = lv_deal
         MSGV4 = lv_msgv4
         FLG_DEAL = lv_flg_deal
         FLOW = lv_flow
         MSGID = lv_msgid
         MSGNO = lv_msgno
         MSGTY = lv_msgty
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
    TABLES
         MSGPOST = lt_msgpost
. " TB_POSTING_MESSAGE_STORE




ABAP code using 7.40 inline data declarations to call FM TB_POSTING_MESSAGE_STORE

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.

 
 
DATA(ld_msgv4) = ' '.
 
 
 
 
 
 
DATA(ld_msgv1) = ' '.
 
DATA(ld_msgv2) = ' '.
 
DATA(ld_msgv3) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!