SAP ISP_NETCHANGE_BY_ORDER_SAVE Function Module for Update Netchange Files from Order Processing (Publishing)









ISP_NETCHANGE_BY_ORDER_SAVE is a standard isp netchange by order save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Netchange Files from Order Processing (Publishing) 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 netchange by order save FM, simply by entering the name ISP_NETCHANGE_BY_ORDER_SAVE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_NETCHANGE_BY_ORDER_SAVE 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_NETCHANGE_BY_ORDER_SAVE'"Update Netchange Files from Order Processing (Publishing)
  EXPORTING
   XJKAK =  "
   YJKAK =  "

TABLES
   XJKAP =  "
   YJKPAZ =  "
*  POS_RW_DONE =  "
   XJKEP =  "
   XJKKD =  "
   XJKPA =  "
   XJKPAZ =  "
   YJKAP =  "
   YJKEP =  "
   YJKKD =  "
   YJKPA =  "
.



IMPORTING Parameters details for ISP_NETCHANGE_BY_ORDER_SAVE

XJKAK -

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

YJKAK -

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

TABLES Parameters details for ISP_NETCHANGE_BY_ORDER_SAVE

XJKAP -

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

YJKPAZ -

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

POS_RW_DONE -

Data type: JKAP
Optional: Yes
Call by Reference: Yes

XJKEP -

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

XJKKD -

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

XJKPA -

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

XJKPAZ -

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

YJKAP -

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

YJKEP -

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

YJKKD -

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

YJKPA -

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

Copy and paste ABAP code example for ISP_NETCHANGE_BY_ORDER_SAVE 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_xjkak  TYPE JKAKVB, "   
lt_xjkap  TYPE STANDARD TABLE OF JKAPVB, "   
lt_yjkpaz  TYPE STANDARD TABLE OF JKPAZ, "   
lt_pos_rw_done  TYPE STANDARD TABLE OF JKAP, "   
lt_xjkep  TYPE STANDARD TABLE OF JKEPVB, "   
lv_yjkak  TYPE JKAK, "   
lt_xjkkd  TYPE STANDARD TABLE OF JKKDVB, "   
lt_xjkpa  TYPE STANDARD TABLE OF JKPAVB, "   
lt_xjkpaz  TYPE STANDARD TABLE OF JKPAZVB, "   
lt_yjkap  TYPE STANDARD TABLE OF JKAP, "   
lt_yjkep  TYPE STANDARD TABLE OF JKEP, "   
lt_yjkkd  TYPE STANDARD TABLE OF JKKD, "   
lt_yjkpa  TYPE STANDARD TABLE OF JKPA. "   

  CALL FUNCTION 'ISP_NETCHANGE_BY_ORDER_SAVE'  "Update Netchange Files from Order Processing (Publishing)
    EXPORTING
         XJKAK = lv_xjkak
         YJKAK = lv_yjkak
    TABLES
         XJKAP = lt_xjkap
         YJKPAZ = lt_yjkpaz
         POS_RW_DONE = lt_pos_rw_done
         XJKEP = lt_xjkep
         XJKKD = lt_xjkkd
         XJKPA = lt_xjkpa
         XJKPAZ = lt_xjkpaz
         YJKAP = lt_yjkap
         YJKEP = lt_yjkep
         YJKKD = lt_yjkkd
         YJKPA = lt_yjkpa
. " ISP_NETCHANGE_BY_ORDER_SAVE




ABAP code using 7.40 inline data declarations to call FM ISP_NETCHANGE_BY_ORDER_SAVE

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.

 
 
 
 
 
 
 
 
 
 
 
 
 


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!