SAP ISU_O_ROUTEOBJ_ACTION_SAVE_SV Function Module for Internal: Save Service Frequency from Service Contract

Search SAP Function Modules

ISU_O_ROUTEOBJ_ACTION_SAVE_SV is a standard isu o routeobj action save sv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Internal: Save Service Frequency from Service Contract 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 isu o routeobj action save sv FM, simply by entering the name ISU_O_ROUTEOBJ_ACTION_SAVE_SV into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_O_ROUTEOBJ_ACTION_SAVE_SV 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 'ISU_O_ROUTEOBJ_ACTION_SAVE_SV'"Internal: Save Service Frequency from Service Contract
  EXPORTING
   X_SDAUFNR =  "
   X_FVBAK =  "Sales Document: Header Data
*  X_UPD_ONLINE = 'X' "
*  X_FVBAK_OLD =  "
*  XT_VBAP =  "
*  XT_VBAP_OLD =  "

 IMPORTING
   Y_DB_CHANGED =  "

TABLES
   T_XVBAP =  "

EXCEPTIONS
   CANCEL_UPDATE = 1 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEEWA_MD_ROUTE_001 Checks for Comparison: Service Frequency for Route/Container
EXIT_SAPLEEWA_MD_ROUTE_002 Prepares Customer Subscreen Call of Route
EXIT_SAPLEEWA_MD_ROUTE_003 Prepares Customer Subscreen (PAI) of Route
EXIT_SAPLEEWA_MD_ROUTE_004 Closes Route Customer Subscreen (PAI)
EXIT_SAPLEEWA_MD_RO_001 Check Default Route for Service Frequency
EXIT_SAPLEEWA_MD_RO_002 Check on Admissibility of Service Interval Grouping
EXIT_SAPLEEWA_MD_RO_004 Prepares the Customer Subscreen Call for Header Data
EXIT_SAPLEEWA_MD_RO_005 Prepares the CALL SUBSCREEN PAI for Header Data
EXIT_SAPLEEWA_MD_RO_006 Closes the CALL SUBSCREEN PAI of the Header Data
EXIT_SAPLEEWA_MD_RO_007 Prepares the Customer Subscreen Call for Item Data
EXIT_SAPLEEWA_MD_RO_008 Prepares the CALL SUBSCREEN PAI for Item Data
EXIT_SAPLEEWA_MD_RO_009 Closes the CALL SUBSCREEN PAI of the Item Data

IMPORTING Parameters details for ISU_O_ROUTEOBJ_ACTION_SAVE_SV

X_SDAUFNR -

Data type: SER02-SDAUFNR
Optional: No
Call by Reference: Yes

X_FVBAK - Sales Document: Header Data

Data type: VBAK
Optional: No
Call by Reference: Yes

X_UPD_ONLINE -

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: Yes

X_FVBAK_OLD -

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

XT_VBAP -

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

XT_VBAP_OLD -

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

EXPORTING Parameters details for ISU_O_ROUTEOBJ_ACTION_SAVE_SV

Y_DB_CHANGED -

Data type: REGEN-CHANGED
Optional: No
Call by Reference: Yes

TABLES Parameters details for ISU_O_ROUTEOBJ_ACTION_SAVE_SV

T_XVBAP -

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

EXCEPTIONS details

CANCEL_UPDATE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_O_ROUTEOBJ_ACTION_SAVE_SV 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.

ABAP code using 7.40 inline data declarations to call FM ISU_O_ROUTEOBJ_ACTION_SAVE_SV

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