SAP G_DELETE_AND_CORRECT_DOCS Function Module for









G_DELETE_AND_CORRECT_DOCS is a standard g delete and correct docs 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 g delete and correct docs FM, simply by entering the name G_DELETE_AND_CORRECT_DOCS into the relevant SAP transaction such as SE37 or SE38.

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



Function G_DELETE_AND_CORRECT_DOCS 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 'G_DELETE_AND_CORRECT_DOCS'"
EXPORTING
E01_RLDNR = "
E01_BUKRS = "
E01_RCOMP = "
E01_RYEAR = "
E01_DOCCT = "

TABLES
E01_SEL_DOC = "
.



IMPORTING Parameters details for G_DELETE_AND_CORRECT_DOCS

E01_RLDNR -

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

E01_BUKRS -

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

E01_RCOMP -

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

E01_RYEAR -

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

E01_DOCCT -

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

TABLES Parameters details for G_DELETE_AND_CORRECT_DOCS

E01_SEL_DOC -

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

Copy and paste ABAP code example for G_DELETE_AND_CORRECT_DOCS 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_e01_rldnr  TYPE GLU1-RLDNR, "   
lt_e01_sel_doc  TYPE STANDARD TABLE OF GDELT_SEL_DOC_T, "   
lv_e01_bukrs  TYPE GLU1-BUKRS, "   
lv_e01_rcomp  TYPE GLU1-RCOMP, "   
lv_e01_ryear  TYPE GLU1-RYEAR, "   
lv_e01_docct  TYPE GLU1-DOCCT. "   

  CALL FUNCTION 'G_DELETE_AND_CORRECT_DOCS'  "
    EXPORTING
         E01_RLDNR = lv_e01_rldnr
         E01_BUKRS = lv_e01_bukrs
         E01_RCOMP = lv_e01_rcomp
         E01_RYEAR = lv_e01_ryear
         E01_DOCCT = lv_e01_docct
    TABLES
         E01_SEL_DOC = lt_e01_sel_doc
. " G_DELETE_AND_CORRECT_DOCS




ABAP code using 7.40 inline data declarations to call FM G_DELETE_AND_CORRECT_DOCS

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 RLDNR FROM GLU1 INTO @DATA(ld_e01_rldnr).
 
 
"SELECT single BUKRS FROM GLU1 INTO @DATA(ld_e01_bukrs).
 
"SELECT single RCOMP FROM GLU1 INTO @DATA(ld_e01_rcomp).
 
"SELECT single RYEAR FROM GLU1 INTO @DATA(ld_e01_ryear).
 
"SELECT single DOCCT FROM GLU1 INTO @DATA(ld_e01_docct).
 


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!