SAP ISP_PACKAGING_START_DATE_GET Function Module for IS-M/SD: Determine Whether Delivery Can Be Packaged (Order Deadline)









ISP_PACKAGING_START_DATE_GET is a standard isp packaging start date get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Determine Whether Delivery Can Be Packaged (Order Deadline) 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 isp packaging start date get FM, simply by entering the name ISP_PACKAGING_START_DATE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: JVY0
Program Name: SAPLJVY0
Main Program: SAPLJVY0
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISP_PACKAGING_START_DATE_GET 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 'ISP_PACKAGING_START_DATE_GET'"IS-M/SD: Determine Whether Delivery Can Be Packaged (Order Deadline)
EXPORTING
DRERZ = "Publication
* DRUERZART = CON_TITEL "
IN_VERSANDDATUM = "
LOGLFART = "Logistical delivery type
PVA = "Prod.Vers.
WERK = "
* NETCHANGE_COMPLETED = ' ' "

IMPORTING
PACKAGING_START = "

EXCEPTIONS
MISSING_LOGLFART = 1 NO_DATE_FOUND = 2
.



IMPORTING Parameters details for ISP_PACKAGING_START_DATE_GET

DRERZ - Publication

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

DRUERZART -

Data type: RJV1001-DRUERZART
Default: CON_TITEL
Optional: Yes
Call by Reference: No ( called with pass by value option)

IN_VERSANDDATUM -

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

LOGLFART - Logistical delivery type

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

PVA - Prod.Vers.

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

WERK -

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

NETCHANGE_COMPLETED -

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

EXPORTING Parameters details for ISP_PACKAGING_START_DATE_GET

PACKAGING_START -

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

EXCEPTIONS details

MISSING_LOGLFART -

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

NO_DATE_FOUND -

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

Copy and paste ABAP code example for ISP_PACKAGING_START_DATE_GET 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_drerz  TYPE RJV1001-DRERZ, "   
lv_packaging_start  TYPE JPSD_XFELD, "   
lv_missing_loglfart  TYPE JPSD_XFELD, "   
lv_druerzart  TYPE RJV1001-DRUERZART, "   CON_TITEL
lv_no_date_found  TYPE RJV1001, "   
lv_in_versanddatum  TYPE JVTLFNG-VERSANDDAT, "   
lv_loglfart  TYPE JVTLFNG-LFARTLOG, "   
lv_pva  TYPE RJV1001-PVA, "   
lv_werk  TYPE RJV1001-DRUCKEREI, "   
lv_netchange_completed  TYPE JPSD_XFELD. "   SPACE

  CALL FUNCTION 'ISP_PACKAGING_START_DATE_GET'  "IS-M/SD: Determine Whether Delivery Can Be Packaged (Order Deadline)
    EXPORTING
         DRERZ = lv_drerz
         DRUERZART = lv_druerzart
         IN_VERSANDDATUM = lv_in_versanddatum
         LOGLFART = lv_loglfart
         PVA = lv_pva
         WERK = lv_werk
         NETCHANGE_COMPLETED = lv_netchange_completed
    IMPORTING
         PACKAGING_START = lv_packaging_start
    EXCEPTIONS
        MISSING_LOGLFART = 1
        NO_DATE_FOUND = 2
. " ISP_PACKAGING_START_DATE_GET




ABAP code using 7.40 inline data declarations to call FM ISP_PACKAGING_START_DATE_GET

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 DRERZ FROM RJV1001 INTO @DATA(ld_drerz).
 
 
 
"SELECT single DRUERZART FROM RJV1001 INTO @DATA(ld_druerzart).
DATA(ld_druerzart) = CON_TITEL.
 
 
"SELECT single VERSANDDAT FROM JVTLFNG INTO @DATA(ld_in_versanddatum).
 
"SELECT single LFARTLOG FROM JVTLFNG INTO @DATA(ld_loglfart).
 
"SELECT single PVA FROM RJV1001 INTO @DATA(ld_pva).
 
"SELECT single DRUCKEREI FROM RJV1001 INTO @DATA(ld_werk).
 
DATA(ld_netchange_completed) = ' '.
 


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!