SAP SALU_EDIT_TID_CUST_MSGCONT Function Module for









SALU_EDIT_TID_CUST_MSGCONT is a standard salu edit tid cust msgcont 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 salu edit tid cust msgcont FM, simply by entering the name SALU_EDIT_TID_CUST_MSGCONT into the relevant SAP transaction such as SE37 or SE38.

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



Function SALU_EDIT_TID_CUST_MSGCONT 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 'SALU_EDIT_TID_CUST_MSGCONT'"
EXPORTING
SHORT_TID = "
* CUST_SETNAME = "
* USE_ACTIVE_CUSTSET = ' ' "

EXCEPTIONS
CUST_SETNAME_MISSING = 1 TID_NOT_FOUND = 2
.



IMPORTING Parameters details for SALU_EDIT_TID_CUST_MSGCONT

SHORT_TID -

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

CUST_SETNAME -

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

USE_ACTIVE_CUSTSET -

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

EXCEPTIONS details

CUST_SETNAME_MISSING -

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

TID_NOT_FOUND -

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

Copy and paste ABAP code example for SALU_EDIT_TID_CUST_MSGCONT 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_short_tid  TYPE ALTIDKEY, "   
lv_cust_setname_missing  TYPE ALTIDKEY, "   
lv_cust_setname  TYPE ALMTCUSMSC-SETNAME, "   
lv_tid_not_found  TYPE ALMTCUSMSC, "   
lv_use_active_custset  TYPE C. "   SPACE

  CALL FUNCTION 'SALU_EDIT_TID_CUST_MSGCONT'  "
    EXPORTING
         SHORT_TID = lv_short_tid
         CUST_SETNAME = lv_cust_setname
         USE_ACTIVE_CUSTSET = lv_use_active_custset
    EXCEPTIONS
        CUST_SETNAME_MISSING = 1
        TID_NOT_FOUND = 2
. " SALU_EDIT_TID_CUST_MSGCONT




ABAP code using 7.40 inline data declarations to call FM SALU_EDIT_TID_CUST_MSGCONT

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.

 
 
"SELECT single SETNAME FROM ALMTCUSMSC INTO @DATA(ld_cust_setname).
 
 
DATA(ld_use_active_custset) = ' '.
 


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!