SAP HRDSYS_VIEW_DOCU_EDIT_2 Function Module for









HRDSYS_VIEW_DOCU_EDIT_2 is a standard hrdsys view docu edit 2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 hrdsys view docu edit 2 FM, simply by entering the name HRDSYS_VIEW_DOCU_EDIT_2 into the relevant SAP transaction such as SE37 or SE38.

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



Function HRDSYS_VIEW_DOCU_EDIT_2 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 'HRDSYS_VIEW_DOCU_EDIT_2'"
EXPORTING
STATUS_ACTION = "
* MFIELD = "
OFIELD1 = "
* OFIELD2 = "
OTYPE = "
NEXTLINE = "
VIM_EXTRACT_STRUC = "
VIM_TOTAL_STRUC = "

CHANGING
FUNCTION = "
XACTION = "
ACTION = "

TABLES
EXTRACT = "
TOTAL = "

EXCEPTIONS
FIELDNAME_ERROR = 1 INDEX_ERROR = 2
.



IMPORTING Parameters details for HRDSYS_VIEW_DOCU_EDIT_2

STATUS_ACTION -

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

MFIELD -

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

OFIELD1 -

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

OFIELD2 -

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

OTYPE -

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

NEXTLINE -

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

VIM_EXTRACT_STRUC -

Data type:
Optional: No
Call by Reference: Yes

VIM_TOTAL_STRUC -

Data type:
Optional: No
Call by Reference: Yes

CHANGING Parameters details for HRDSYS_VIEW_DOCU_EDIT_2

FUNCTION -

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

XACTION -

Data type:
Optional: No
Call by Reference: Yes

ACTION -

Data type:
Optional: No
Call by Reference: Yes

TABLES Parameters details for HRDSYS_VIEW_DOCU_EDIT_2

EXTRACT -

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

TOTAL -

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

EXCEPTIONS details

FIELDNAME_ERROR -

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

INDEX_ERROR -

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

Copy and paste ABAP code example for HRDSYS_VIEW_DOCU_EDIT_2 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:
lt_extract  TYPE STANDARD TABLE OF STRING, "   
lv_function  TYPE STRING, "   
lv_status_action  TYPE C, "   
lv_fieldname_error  TYPE C, "   
lt_total  TYPE STANDARD TABLE OF C, "   
lv_mfield  TYPE VIMNAMTAB-VIEWFIELD, "   
lv_xaction  TYPE VIMNAMTAB, "   
lv_index_error  TYPE VIMNAMTAB, "   
lv_action  TYPE VIMNAMTAB, "   
lv_ofield1  TYPE VIMNAMTAB-VIEWFIELD, "   
lv_ofield2  TYPE VIMNAMTAB-VIEWFIELD, "   
lv_otype  TYPE SDOK_PRV_L, "   
lv_nextline  TYPE SY-TABIX, "   
lv_vim_extract_struc  TYPE SY, "   
lv_vim_total_struc  TYPE SY. "   

  CALL FUNCTION 'HRDSYS_VIEW_DOCU_EDIT_2'  "
    EXPORTING
         STATUS_ACTION = lv_status_action
         MFIELD = lv_mfield
         OFIELD1 = lv_ofield1
         OFIELD2 = lv_ofield2
         OTYPE = lv_otype
         NEXTLINE = lv_nextline
         VIM_EXTRACT_STRUC = lv_vim_extract_struc
         VIM_TOTAL_STRUC = lv_vim_total_struc
    CHANGING
         FUNCTION = lv_function
         XACTION = lv_xaction
         ACTION = lv_action
    TABLES
         EXTRACT = lt_extract
         TOTAL = lt_total
    EXCEPTIONS
        FIELDNAME_ERROR = 1
        INDEX_ERROR = 2
. " HRDSYS_VIEW_DOCU_EDIT_2




ABAP code using 7.40 inline data declarations to call FM HRDSYS_VIEW_DOCU_EDIT_2

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 VIEWFIELD FROM VIMNAMTAB INTO @DATA(ld_mfield).
 
 
 
 
"SELECT single VIEWFIELD FROM VIMNAMTAB INTO @DATA(ld_ofield1).
 
"SELECT single VIEWFIELD FROM VIMNAMTAB INTO @DATA(ld_ofield2).
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_nextline).
 
 
 


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!