SAP SD_MESSAGE_SPLIT Function Module for NOTRANSL: Message holen und in zwei Teile teilen

Search SAP Function Modules

SD_MESSAGE_SPLIT is a standard sd message split SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Message holen und in zwei Teile teilen 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 sd message split FM, simply by entering the name SD_MESSAGE_SPLIT into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_MESSAGE_SPLIT 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 'SD_MESSAGE_SPLIT'"NOTRANSL: Message holen und in zwei Teile teilen
  EXPORTING
   MSGID =  "ABAP System Field: Message ID
   MSGNO =  "ABAP System Field: Message Number
*  MSGV1 = ' ' "
*  MSGV2 = ' ' "
*  MSGV3 = ' ' "
*  MSGV4 = ' ' "
*  LANGU = SY-LANGU "ABAP System Field: Language Key of Text Environment
*  CUTOFF = 42 "Predefined Type

 IMPORTING
   TEXT1 =  "Text Line
   TEXT2 =  "Text Line

EXCEPTIONS
   MESSAGE_NOT_FOUND = 1 

.

IMPORTING Parameters details for SD_MESSAGE_SPLIT

MSGID - ABAP System Field: Message ID

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

MSGNO - ABAP System Field: Message Number

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

MSGV1 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: Yes

MSGV2 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: Yes

MSGV3 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: Yes

MSGV4 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: Yes

LANGU - ABAP System Field: Language Key of Text Environment

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

CUTOFF - Predefined Type

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

EXPORTING Parameters details for SD_MESSAGE_SPLIT

TEXT1 - Text Line

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

TEXT2 - Text Line

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

EXCEPTIONS details

MESSAGE_NOT_FOUND -

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

Copy and paste ABAP code example for SD_MESSAGE_SPLIT 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 SD_MESSAGE_SPLIT

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