SAP SD_MESSAGES_FOR_SHIPMENTS Function Module for









SD_MESSAGES_FOR_SHIPMENTS is a standard sd messages for shipments 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 sd messages for shipments FM, simply by entering the name SD_MESSAGES_FOR_SHIPMENTS into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_MESSAGES_FOR_SHIPMENTS 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_MESSAGES_FOR_SHIPMENTS'"
  EXPORTING
*  PM_DPABF = ' ' "
*  NO_COMMIT_WORK = ' ' "
*  NO_SHIPMENT_LOCK = ' ' "
*  CREATE_LOGFILE = ' ' "
*  PM_TPLST = ' ' "Transportation planning point
*  PM_PARVW = ' ' "Partner Role
*  PM_PARNR = ' ' "Partner Number
*  PM_TRAN = ' ' "Indicator for shipment output
*  PM_VERV7 = ' ' "
*  PM_DPROF = ' ' "Print profile
*  PM_RFPRT = ' ' "Output Device
*  NODIALOG = ' ' "No dialog processing

TABLES
   RG_TKNUM =  "
*  RG_KSCV7 =  "Transportation Output
*  RG_NACV7 =  "

EXCEPTIONS
   NO_MESSAGES_EXIST = 1    INVALID_SHIPMENT_RANGES = 2    PARTNERROLE_MISSING = 3
.



IMPORTING Parameters details for SD_MESSAGES_FOR_SHIPMENTS

PM_DPABF -

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

NO_COMMIT_WORK -

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

NO_SHIPMENT_LOCK -

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

CREATE_LOGFILE -

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

PM_TPLST - Transportation planning point

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

PM_PARVW - Partner Role

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

PM_PARNR - Partner Number

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

PM_TRAN - Indicator for shipment output

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

PM_VERV7 -

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

PM_DPROF - Print profile

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

PM_RFPRT - Output Device

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

NODIALOG - No dialog processing

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

TABLES Parameters details for SD_MESSAGES_FOR_SHIPMENTS

RG_TKNUM -

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

RG_KSCV7 - Transportation Output

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

RG_NACV7 -

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

EXCEPTIONS details

NO_MESSAGES_EXIST - No message selected

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

INVALID_SHIPMENT_RANGES -

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

PARTNERROLE_MISSING -

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

Copy and paste ABAP code example for SD_MESSAGES_FOR_SHIPMENTS 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_pm_dpabf  TYPE VTTK-DPABF, "   SPACE
lt_rg_tknum  TYPE STANDARD TABLE OF RANGE_C10, "   
lv_no_messages_exist  TYPE RANGE_C10, "   
lv_no_commit_work  TYPE RV56A-SELKZ, "   SPACE
lv_no_shipment_lock  TYPE RV56A-SELKZ, "   SPACE
lv_create_logfile  TYPE RV56A-SELKZ, "   SPACE
lv_pm_tplst  TYPE VTTK-TPLST, "   SPACE
lt_rg_kscv7  TYPE STANDARD TABLE OF MSG2, "   
lv_invalid_shipment_ranges  TYPE MSG2, "   
lv_pm_parvw  TYPE DNAST-PARVW, "   SPACE
lt_rg_nacv7  TYPE STANDARD TABLE OF MSG3, "   
lv_partnerrole_missing  TYPE MSG3, "   
lv_pm_parnr  TYPE NAST-PARNR, "   SPACE
lv_pm_tran  TYPE RV56A-KZ_NACHTR, "   SPACE
lv_pm_verv7  TYPE NASE-VERMO, "   SPACE
lv_pm_dprof  TYPE LEDRUCKPROFIL-PROFILNAME, "   SPACE
lv_pm_rfprt  TYPE LEDRUCKPROFIL-PADEST_NEW, "   SPACE
lv_nodialog  TYPE RV56A-SELKZ. "   SPACE

  CALL FUNCTION 'SD_MESSAGES_FOR_SHIPMENTS'  "
    EXPORTING
         PM_DPABF = lv_pm_dpabf
         NO_COMMIT_WORK = lv_no_commit_work
         NO_SHIPMENT_LOCK = lv_no_shipment_lock
         CREATE_LOGFILE = lv_create_logfile
         PM_TPLST = lv_pm_tplst
         PM_PARVW = lv_pm_parvw
         PM_PARNR = lv_pm_parnr
         PM_TRAN = lv_pm_tran
         PM_VERV7 = lv_pm_verv7
         PM_DPROF = lv_pm_dprof
         PM_RFPRT = lv_pm_rfprt
         NODIALOG = lv_nodialog
    TABLES
         RG_TKNUM = lt_rg_tknum
         RG_KSCV7 = lt_rg_kscv7
         RG_NACV7 = lt_rg_nacv7
    EXCEPTIONS
        NO_MESSAGES_EXIST = 1
        INVALID_SHIPMENT_RANGES = 2
        PARTNERROLE_MISSING = 3
. " SD_MESSAGES_FOR_SHIPMENTS




ABAP code using 7.40 inline data declarations to call FM SD_MESSAGES_FOR_SHIPMENTS

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 DPABF FROM VTTK INTO @DATA(ld_pm_dpabf).
DATA(ld_pm_dpabf) = ' '.
 
 
 
"SELECT single SELKZ FROM RV56A INTO @DATA(ld_no_commit_work).
DATA(ld_no_commit_work) = ' '.
 
"SELECT single SELKZ FROM RV56A INTO @DATA(ld_no_shipment_lock).
DATA(ld_no_shipment_lock) = ' '.
 
"SELECT single SELKZ FROM RV56A INTO @DATA(ld_create_logfile).
DATA(ld_create_logfile) = ' '.
 
"SELECT single TPLST FROM VTTK INTO @DATA(ld_pm_tplst).
DATA(ld_pm_tplst) = ' '.
 
 
 
"SELECT single PARVW FROM DNAST INTO @DATA(ld_pm_parvw).
DATA(ld_pm_parvw) = ' '.
 
 
 
"SELECT single PARNR FROM NAST INTO @DATA(ld_pm_parnr).
DATA(ld_pm_parnr) = ' '.
 
"SELECT single KZ_NACHTR FROM RV56A INTO @DATA(ld_pm_tran).
DATA(ld_pm_tran) = ' '.
 
"SELECT single VERMO FROM NASE INTO @DATA(ld_pm_verv7).
DATA(ld_pm_verv7) = ' '.
 
"SELECT single PROFILNAME FROM LEDRUCKPROFIL INTO @DATA(ld_pm_dprof).
DATA(ld_pm_dprof) = ' '.
 
"SELECT single PADEST_NEW FROM LEDRUCKPROFIL INTO @DATA(ld_pm_rfprt).
DATA(ld_pm_rfprt) = ' '.
 
"SELECT single SELKZ FROM RV56A INTO @DATA(ld_nodialog).
DATA(ld_nodialog) = ' '.
 


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!