SAP EFG_ADOBEFORM_DELETE Function Module for
EFG_ADOBEFORM_DELETE is a standard efg adobeform delete 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 efg adobeform delete FM, simply by entering the name EFG_ADOBEFORM_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EFG_ADOBEFORMS
Program Name: SAPLEFG_ADOBEFORMS
Main Program: SAPLEFG_ADOBEFORMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EFG_ADOBEFORM_DELETE 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 'EFG_ADOBEFORM_DELETE'".
EXPORTING
I_ADFORM = "
* I_TRKORR = "
EXCEPTIONS
NOT_QUALIFIED = 1 NOT_FOUND = 2 FAILED = 3 CANCELLED = 4
IMPORTING Parameters details for EFG_ADOBEFORM_DELETE
I_ADFORM -
Data type: FPNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_TRKORR -
Data type: TRKORROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_QUALIFIED -
Data type:Optional: No
Call by Reference: Yes
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
FAILED -
Data type:Optional: No
Call by Reference: Yes
CANCELLED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EFG_ADOBEFORM_DELETE 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_adform | TYPE FPNAME, " | |||
| lv_not_qualified | TYPE FPNAME, " | |||
| lv_i_trkorr | TYPE TRKORR, " | |||
| lv_not_found | TYPE TRKORR, " | |||
| lv_failed | TYPE TRKORR, " | |||
| lv_cancelled | TYPE TRKORR. " |
|   CALL FUNCTION 'EFG_ADOBEFORM_DELETE' " |
| EXPORTING | ||
| I_ADFORM | = lv_i_adform | |
| I_TRKORR | = lv_i_trkorr | |
| EXCEPTIONS | ||
| NOT_QUALIFIED = 1 | ||
| NOT_FOUND = 2 | ||
| FAILED = 3 | ||
| CANCELLED = 4 | ||
| . " EFG_ADOBEFORM_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM EFG_ADOBEFORM_DELETE
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