SAP QFGEN_DEFECT_SAVE Function Module for Save changes to active DB
QFGEN_DEFECT_SAVE is a standard qfgen defect save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save changes to active DB 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 qfgen defect save FM, simply by entering the name QFGEN_DEFECT_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: QFGEN
Program Name: SAPLQFGEN
Main Program: SAPLQFGEN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QFGEN_DEFECT_SAVE 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 'QFGEN_DEFECT_SAVE'"Save changes to active DB.
EXPORTING
* IV_UPDATE_TASK = ABAP_TRUE "Execute in Update-Task
IMPORTING
ET_MESSAGE = "Table with BAPI Return Information
ET_DEFECT = "
EO_MESSAGE = "Interface of Message Object
EV_REJECTED = "Save was rejected
IMPORTING Parameters details for QFGEN_DEFECT_SAVE
IV_UPDATE_TASK - Execute in Update-Task
Data type: ABAP_BOOLDefault: ABAP_TRUE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for QFGEN_DEFECT_SAVE
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
ET_DEFECT -
Data type: ITDEFECT_TPOptional: No
Call by Reference: Yes
EO_MESSAGE - Interface of Message Object
Data type: /BOBF/IF_FRW_MESSAGEOptional: No
Call by Reference: Yes
EV_REJECTED - Save was rejected
Data type: ABAP_BOOLOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for QFGEN_DEFECT_SAVE 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_message | TYPE BAPIRETTAB, " | |||
| lv_iv_update_task | TYPE ABAP_BOOL, " ABAP_TRUE | |||
| lv_et_defect | TYPE ITDEFECT_TP, " | |||
| lv_eo_message | TYPE /BOBF/IF_FRW_MESSAGE, " | |||
| lv_ev_rejected | TYPE ABAP_BOOL. " |
|   CALL FUNCTION 'QFGEN_DEFECT_SAVE' "Save changes to active DB |
| EXPORTING | ||
| IV_UPDATE_TASK | = lv_iv_update_task | |
| IMPORTING | ||
| ET_MESSAGE | = lv_et_message | |
| ET_DEFECT | = lv_et_defect | |
| EO_MESSAGE | = lv_eo_message | |
| EV_REJECTED | = lv_ev_rejected | |
| . " QFGEN_DEFECT_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM QFGEN_DEFECT_SAVE
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.| DATA(ld_iv_update_task) | = ABAP_TRUE. | |||
Search for further information about these or an SAP related objects