SAP SO_DYNP_SHORT_MESSAGE Function Module for SAPoffice: Send short message









SO_DYNP_SHORT_MESSAGE is a standard so dynp short message SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAPoffice: Send short message 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 so dynp short message FM, simply by entering the name SO_DYNP_SHORT_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SO00
Program Name: SAPLSO00
Main Program: SAPLSO00
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SO_DYNP_SHORT_MESSAGE 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 'SO_DYNP_SHORT_MESSAGE'"SAPoffice: Send short message
EXPORTING
* KEEP_MODE = ' ' "
* RECEIVER = ' ' "
.



IMPORTING Parameters details for SO_DYNP_SHORT_MESSAGE

KEEP_MODE -

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

RECEIVER -

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

Copy and paste ABAP code example for SO_DYNP_SHORT_MESSAGE 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_keep_mode  TYPE SONV-FLAG, "   SPACE
lv_receiver  TYPE SOOS1-RECNAM. "   SPACE

  CALL FUNCTION 'SO_DYNP_SHORT_MESSAGE'  "SAPoffice: Send short message
    EXPORTING
         KEEP_MODE = lv_keep_mode
         RECEIVER = lv_receiver
. " SO_DYNP_SHORT_MESSAGE




ABAP code using 7.40 inline data declarations to call FM SO_DYNP_SHORT_MESSAGE

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 FLAG FROM SONV INTO @DATA(ld_keep_mode).
DATA(ld_keep_mode) = ' '.
 
"SELECT single RECNAM FROM SOOS1 INTO @DATA(ld_receiver).
DATA(ld_receiver) = ' '.
 


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!