SAP DPWTY_TABLE_CONTENT_RFC Function Module for Read Table Content from RFC destination (F4 help)
DPWTY_TABLE_CONTENT_RFC is a standard dpwty table content rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Table Content from RFC destination (F4 help) 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 dpwty table content rfc FM, simply by entering the name DPWTY_TABLE_CONTENT_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: DPWTY_C_TABLES
Program Name: SAPLDPWTY_C_TABLES
Main Program: SAPLDPWTY_C_TABLES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DPWTY_TABLE_CONTENT_RFC 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 'DPWTY_TABLE_CONTENT_RFC'"Read Table Content from RFC destination (F4 help).
EXPORTING
IV_TABLE_NAME = "Table Name
* IV_TABLE_KEY = "Table Key
IMPORTING
ET_TABLE = "Table type for BAPIPAREX
ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for DPWTY_TABLE_CONTENT_RFC
IV_TABLE_NAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_TABLE_KEY - Table Key
Data type: TABKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DPWTY_TABLE_CONTENT_RFC
ET_TABLE - Table type for BAPIPAREX
Data type: BAPIPAREXTABOptional: No
Call by Reference: No ( called with pass by value option)
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DPWTY_TABLE_CONTENT_RFC 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_et_table | TYPE BAPIPAREXTAB, " | |||
| lv_iv_table_name | TYPE TABNAME, " | |||
| lv_et_return | TYPE BAPIRETTAB, " | |||
| lv_iv_table_key | TYPE TABKEY. " |
|   CALL FUNCTION 'DPWTY_TABLE_CONTENT_RFC' "Read Table Content from RFC destination (F4 help) |
| EXPORTING | ||
| IV_TABLE_NAME | = lv_iv_table_name | |
| IV_TABLE_KEY | = lv_iv_table_key | |
| IMPORTING | ||
| ET_TABLE | = lv_et_table | |
| ET_RETURN | = lv_et_return | |
| . " DPWTY_TABLE_CONTENT_RFC | ||
ABAP code using 7.40 inline data declarations to call FM DPWTY_TABLE_CONTENT_RFC
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