SAP EXIT_SAPLJV22_002 Function Module for IS-M/SD: Carrier-Specific Change Notification









EXIT_SAPLJV22_002 is a standard exit sapljv22 002 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: Carrier-Specific Change Notification 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 exit sapljv22 002 FM, simply by entering the name EXIT_SAPLJV22_002 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPLJV22_002 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 'EXIT_SAPLJV22_002'"IS-M/SD: Carrier-Specific Change Notification
  EXPORTING
   BEZIRK =  "
   XVOLLABO =  "
   BEZPER =  "
*  VBELN =  "IS-M/SD: Publishing Sales Order
*  POSNR =  "Sales Order Item
*  POSNR_UR =  "Original Item in Publishing Sales Order
*  POSNR_VG =  "Preceding Item in Publishing Sales Order
*  POART =  "Internal Item Type for Sales Order
*  POSNR_GUELTIGVON =  "Valid-from Date of Sales Order Item
*  POSNR_GUELTIGBIS =  "Date to which Sales Order Item is Valid
   BEZRUNDE =  "
   VERSAND_DATUM =  "
   ERSCH_DATUM =  "
   VOR_VERSAND_DATUM =  "
   VOR_ERSCH_DATUM =  "
   BEZUGSTYP =  "
   DRERZ =  "
   PVA =  "

CHANGING
   XVERSENDET =  "
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISM_NOTICE_CREATE IS-M/SD Generate Carrier Change Notifications
ISM_NOTICE_PRINT IS-M/SD: Carrier Change Nnotification SDoc Type Cat. '1' - Truck Route-Or.
ISM_POTNOTICE_CREATE IS-M/SD Determine Potential Carrier Change Notifications
ISP_VSP_ZUST_AENDER_GET IS-M/SD: Carrier Change Notification SDoc. Type Cat. 1 - Truck Route-Rel.
ISP_VSP_ZUST_AENDER_MITTEIL2 IS-M/SD: Carrier Change Notification SDoc. Type Cat. 1 - Truck Route-Rel.
ISP_VSP_ZUST_AENDER_MIT_DELETE IS-M/SD: Save Prefetch of Affected Order Changes to DB
ISP_VSP_ZUST_AENDER_MIT_PRFTCH IS-M/SD: Prefetch of Affected Order Changes
ISP_VSP_ZUST_AENDER_MIT_READ IS-M/SD: Read Prefetch of Affected Order Changes from DB
ISP_VSP_ZUST_AENDER_MIT_SAVE IS-M/SD: Save Prefetch of Affected Order Changes to DB
ISP_VSP_ZUST_AENDER_MIT_SPOOL Display Change Notifications in Spool

IMPORTING Parameters details for EXIT_SAPLJV22_002

BEZIRK -

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

XVOLLABO -

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

BEZPER -

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

VBELN - IS-M/SD: Publishing Sales Order

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

POSNR - Sales Order Item

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

POSNR_UR - Original Item in Publishing Sales Order

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

POSNR_VG - Preceding Item in Publishing Sales Order

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

POART - Internal Item Type for Sales Order

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

POSNR_GUELTIGVON - Valid-from Date of Sales Order Item

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

POSNR_GUELTIGBIS - Date to which Sales Order Item is Valid

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

BEZRUNDE -

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

VERSAND_DATUM -

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

ERSCH_DATUM -

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

VOR_VERSAND_DATUM -

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

VOR_ERSCH_DATUM -

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

BEZUGSTYP -

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

DRERZ -

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

PVA -

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

CHANGING Parameters details for EXIT_SAPLJV22_002

XVERSENDET -

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

Copy and paste ABAP code example for EXIT_SAPLJV22_002 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_bezirk  TYPE JVTLFNG-BEZIRKTAT, "   
lv_xversendet  TYPE JVTLFNG, "   
lv_xvollabo  TYPE JVTLFNG, "   
lv_bezper  TYPE JKEP-BEZPER, "   
lv_vbeln  TYPE JKAP-VBELN, "   
lv_posnr  TYPE JKAP-POSNR, "   
lv_posnr_ur  TYPE JKAP-POSNR_UR, "   
lv_posnr_vg  TYPE JKAP-POSNR_VG, "   
lv_poart  TYPE JKAP-POART, "   
lv_posnr_gueltigvon  TYPE JKAP-GUELTIGVON, "   
lv_posnr_gueltigbis  TYPE JKAP-GUELTIGBIS, "   
lv_bezrunde  TYPE JVTLFNG-BEZRUNDTAT, "   
lv_versand_datum  TYPE JVTLFNG-VERSANDDAT, "   
lv_ersch_datum  TYPE JVTLFNG-ERSCHDAT, "   
lv_vor_versand_datum  TYPE JVTLFNG-VERSANDDAT, "   
lv_vor_ersch_datum  TYPE JVTLFNG-ERSCHDAT, "   
lv_bezugstyp  TYPE JVTLFNG-BEZUGSTYP, "   
lv_drerz  TYPE JVTLFNG-DRERZTAT, "   
lv_pva  TYPE JVTLFNG-PVATAT. "   

  CALL FUNCTION 'EXIT_SAPLJV22_002'  "IS-M/SD: Carrier-Specific Change Notification
    EXPORTING
         BEZIRK = lv_bezirk
         XVOLLABO = lv_xvollabo
         BEZPER = lv_bezper
         VBELN = lv_vbeln
         POSNR = lv_posnr
         POSNR_UR = lv_posnr_ur
         POSNR_VG = lv_posnr_vg
         POART = lv_poart
         POSNR_GUELTIGVON = lv_posnr_gueltigvon
         POSNR_GUELTIGBIS = lv_posnr_gueltigbis
         BEZRUNDE = lv_bezrunde
         VERSAND_DATUM = lv_versand_datum
         ERSCH_DATUM = lv_ersch_datum
         VOR_VERSAND_DATUM = lv_vor_versand_datum
         VOR_ERSCH_DATUM = lv_vor_ersch_datum
         BEZUGSTYP = lv_bezugstyp
         DRERZ = lv_drerz
         PVA = lv_pva
    CHANGING
         XVERSENDET = lv_xversendet
. " EXIT_SAPLJV22_002




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJV22_002

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 BEZIRKTAT FROM JVTLFNG INTO @DATA(ld_bezirk).
 
 
 
"SELECT single BEZPER FROM JKEP INTO @DATA(ld_bezper).
 
"SELECT single VBELN FROM JKAP INTO @DATA(ld_vbeln).
 
"SELECT single POSNR FROM JKAP INTO @DATA(ld_posnr).
 
"SELECT single POSNR_UR FROM JKAP INTO @DATA(ld_posnr_ur).
 
"SELECT single POSNR_VG FROM JKAP INTO @DATA(ld_posnr_vg).
 
"SELECT single POART FROM JKAP INTO @DATA(ld_poart).
 
"SELECT single GUELTIGVON FROM JKAP INTO @DATA(ld_posnr_gueltigvon).
 
"SELECT single GUELTIGBIS FROM JKAP INTO @DATA(ld_posnr_gueltigbis).
 
"SELECT single BEZRUNDTAT FROM JVTLFNG INTO @DATA(ld_bezrunde).
 
"SELECT single VERSANDDAT FROM JVTLFNG INTO @DATA(ld_versand_datum).
 
"SELECT single ERSCHDAT FROM JVTLFNG INTO @DATA(ld_ersch_datum).
 
"SELECT single VERSANDDAT FROM JVTLFNG INTO @DATA(ld_vor_versand_datum).
 
"SELECT single ERSCHDAT FROM JVTLFNG INTO @DATA(ld_vor_ersch_datum).
 
"SELECT single BEZUGSTYP FROM JVTLFNG INTO @DATA(ld_bezugstyp).
 
"SELECT single DRERZTAT FROM JVTLFNG INTO @DATA(ld_drerz).
 
"SELECT single PVATAT FROM JVTLFNG INTO @DATA(ld_pva).
 


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!