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

Function RE06 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 'RE06'"Invoice receipt, vendor.
EXPORTING
I_BSEG = "
I_DM08R = "
TABLES
T_T169C = "
EXCEPTIONS
NOT_FOUND_T169A = 1
IMPORTING Parameters details for RE06
I_BSEG -
Data type: BSEGOptional: No
Call by Reference: No ( called with pass by value option)
I_DM08R -
Data type: DM08ROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RE06
T_T169C -
Data type: T169COptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND_T169A -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RE06 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_i_bseg | TYPE BSEG, " | |||
| lt_t_t169c | TYPE STANDARD TABLE OF T169C, " | |||
| lv_not_found_t169a | TYPE T169C, " | |||
| lv_i_dm08r | TYPE DM08R. " |
|   CALL FUNCTION 'RE06' "Invoice receipt, vendor |
| EXPORTING | ||
| I_BSEG | = lv_i_bseg | |
| I_DM08R | = lv_i_dm08r | |
| TABLES | ||
| T_T169C | = lt_t_t169c | |
| EXCEPTIONS | ||
| NOT_FOUND_T169A = 1 | ||
| . " RE06 | ||
ABAP code using 7.40 inline data declarations to call FM RE06
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