SAP ISP_DISTRIBUTION_VPLAN_EDIT Function Module for IS-M/SD: Access Analysis Type for Shipping Schedule









ISP_DISTRIBUTION_VPLAN_EDIT is a standard isp distribution vplan edit 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: Access Analysis Type for Shipping Schedule 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 distribution vplan edit FM, simply by entering the name ISP_DISTRIBUTION_VPLAN_EDIT into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_DISTRIBUTION_VPLAN_EDIT 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_DISTRIBUTION_VPLAN_EDIT'"IS-M/SD: Access Analysis Type for Shipping Schedule
  EXPORTING
   EINSTIEG =  "
   IN_SEL_VARIANTE =  "
   TRTYP =  "

TABLES
   RJV2402_TAB =  "
   RJV2403_TAB =  "
   RJV2404_TAB =  "
   RJV2405_TAB =  "
   RJV2701_TAB =  "
   RJV2702_TAB =  "
   RJV2703_TAB =  "
   RJV2704_TAB =  "
.



IMPORTING Parameters details for ISP_DISTRIBUTION_VPLAN_EDIT

EINSTIEG -

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

IN_SEL_VARIANTE -

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

TRTYP -

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

TABLES Parameters details for ISP_DISTRIBUTION_VPLAN_EDIT

RJV2402_TAB -

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

RJV2403_TAB -

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

RJV2404_TAB -

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

RJV2405_TAB -

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

RJV2701_TAB -

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

RJV2702_TAB -

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

RJV2703_TAB -

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

RJV2704_TAB -

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

Copy and paste ABAP code example for ISP_DISTRIBUTION_VPLAN_EDIT 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_einstieg  TYPE RJV2401-EINSTIEG, "   
lt_rjv2402_tab  TYPE STANDARD TABLE OF RJV2402, "   
lt_rjv2403_tab  TYPE STANDARD TABLE OF RJV2403, "   
lv_in_sel_variante  TYPE JVTVERVARI-VRSNDVARI, "   
lv_trtyp  TYPE TJ180-TRTYP, "   
lt_rjv2404_tab  TYPE STANDARD TABLE OF RJV2404, "   
lt_rjv2405_tab  TYPE STANDARD TABLE OF RJV2405, "   
lt_rjv2701_tab  TYPE STANDARD TABLE OF RJV2701, "   
lt_rjv2702_tab  TYPE STANDARD TABLE OF RJV2702, "   
lt_rjv2703_tab  TYPE STANDARD TABLE OF RJV2703, "   
lt_rjv2704_tab  TYPE STANDARD TABLE OF RJV2704. "   

  CALL FUNCTION 'ISP_DISTRIBUTION_VPLAN_EDIT'  "IS-M/SD: Access Analysis Type for Shipping Schedule
    EXPORTING
         EINSTIEG = lv_einstieg
         IN_SEL_VARIANTE = lv_in_sel_variante
         TRTYP = lv_trtyp
    TABLES
         RJV2402_TAB = lt_rjv2402_tab
         RJV2403_TAB = lt_rjv2403_tab
         RJV2404_TAB = lt_rjv2404_tab
         RJV2405_TAB = lt_rjv2405_tab
         RJV2701_TAB = lt_rjv2701_tab
         RJV2702_TAB = lt_rjv2702_tab
         RJV2703_TAB = lt_rjv2703_tab
         RJV2704_TAB = lt_rjv2704_tab
. " ISP_DISTRIBUTION_VPLAN_EDIT




ABAP code using 7.40 inline data declarations to call FM ISP_DISTRIBUTION_VPLAN_EDIT

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 EINSTIEG FROM RJV2401 INTO @DATA(ld_einstieg).
 
 
 
"SELECT single VRSNDVARI FROM JVTVERVARI INTO @DATA(ld_in_sel_variante).
 
"SELECT single TRTYP FROM TJ180 INTO @DATA(ld_trtyp).
 
 
 
 
 
 
 


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!