SAP SUGY_HANDLE_NAVERS2 Function Module for init and copy for NAVERS2
SUGY_HANDLE_NAVERS2 is a standard sugy handle navers2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for init and copy for NAVERS2 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 sugy handle navers2 FM, simply by entering the name SUGY_HANDLE_NAVERS2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: SUGY
Program Name: SAPLSUGY
Main Program: SAPLSUGY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SUGY_HANDLE_NAVERS2 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 'SUGY_HANDLE_NAVERS2'"init and copy for NAVERS2.
EXPORTING
* IV_RELSTAMP = 'CURRENT' "ID data type for a (future) system status
* IV_WORKMODE = 'R' "Single-Character Flag
* IV_TAR_RELSTAMP = 'CURRENT' "target relstamp for Copy mode
IMPORTING
EV_RC = "Natural number
EV_MESSAGE = "Char 80
TABLES
ET_FAILED = "failed NAVERS2 activities
ET_SUCCESS = "successful NAVERS2 activities
IMPORTING Parameters details for SUGY_HANDLE_NAVERS2
IV_RELSTAMP - ID data type for a (future) system status
Data type: NCVERS-RELSTAMPDefault: 'CURRENT'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_WORKMODE - Single-Character Flag
Data type: GSUGI_PA-W_ISTATUSDefault: 'R'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_TAR_RELSTAMP - target relstamp for Copy mode
Data type: NCVERS-RELSTAMPDefault: 'CURRENT'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUGY_HANDLE_NAVERS2
EV_RC - Natural number
Data type: GSUGI_PA-NR_CONVOptional: No
Call by Reference: No ( called with pass by value option)
EV_MESSAGE - Char 80
Data type: GSUGI_PA-RCMESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SUGY_HANDLE_NAVERS2
ET_FAILED - failed NAVERS2 activities
Data type: NAVERS2Optional: No
Call by Reference: Yes
ET_SUCCESS - successful NAVERS2 activities
Data type: NAVERS2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SUGY_HANDLE_NAVERS2 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_ev_rc | TYPE GSUGI_PA-NR_CONV, " | |||
| lt_et_failed | TYPE STANDARD TABLE OF NAVERS2, " | |||
| lv_iv_relstamp | TYPE NCVERS-RELSTAMP, " 'CURRENT' | |||
| lt_et_success | TYPE STANDARD TABLE OF NAVERS2, " | |||
| lv_ev_message | TYPE GSUGI_PA-RCMESSAGE, " | |||
| lv_iv_workmode | TYPE GSUGI_PA-W_ISTATUS, " 'R' | |||
| lv_iv_tar_relstamp | TYPE NCVERS-RELSTAMP. " 'CURRENT' |
|   CALL FUNCTION 'SUGY_HANDLE_NAVERS2' "init and copy for NAVERS2 |
| EXPORTING | ||
| IV_RELSTAMP | = lv_iv_relstamp | |
| IV_WORKMODE | = lv_iv_workmode | |
| IV_TAR_RELSTAMP | = lv_iv_tar_relstamp | |
| IMPORTING | ||
| EV_RC | = lv_ev_rc | |
| EV_MESSAGE | = lv_ev_message | |
| TABLES | ||
| ET_FAILED | = lt_et_failed | |
| ET_SUCCESS | = lt_et_success | |
| . " SUGY_HANDLE_NAVERS2 | ||
ABAP code using 7.40 inline data declarations to call FM SUGY_HANDLE_NAVERS2
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 NR_CONV FROM GSUGI_PA INTO @DATA(ld_ev_rc). | ||||
| "SELECT single RELSTAMP FROM NCVERS INTO @DATA(ld_iv_relstamp). | ||||
| DATA(ld_iv_relstamp) | = 'CURRENT'. | |||
| "SELECT single RCMESSAGE FROM GSUGI_PA INTO @DATA(ld_ev_message). | ||||
| "SELECT single W_ISTATUS FROM GSUGI_PA INTO @DATA(ld_iv_workmode). | ||||
| DATA(ld_iv_workmode) | = 'R'. | |||
| "SELECT single RELSTAMP FROM NCVERS INTO @DATA(ld_iv_tar_relstamp). | ||||
| DATA(ld_iv_tar_relstamp) | = 'CURRENT'. | |||
Search for further information about these or an SAP related objects