SAP G_GENERATE_RULE_AFTER_IMPORT Function Module for
G_GENERATE_RULE_AFTER_IMPORT is a standard g generate rule after import 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 generate rule after import FM, simply by entering the name G_GENERATE_RULE_AFTER_IMPORT into the relevant SAP transaction such as SE37 or SE38.
Function Group: GBL1
Program Name: SAPLGBL1
Main Program: SAPLGBL1
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_GENERATE_RULE_AFTER_IMPORT 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_GENERATE_RULE_AFTER_IMPORT'".
EXPORTING
IV_TARCLIENT = "Desired client
IV_IS_UPGRADE = "
TABLES
TT_E071 = "
TT_E071K = "Table with the key entries
IMPORTING Parameters details for G_GENERATE_RULE_AFTER_IMPORT
IV_TARCLIENT - Desired client
Data type: E070C-TARCLIENTOptional: No
Call by Reference: No ( called with pass by value option)
IV_IS_UPGRADE -
Data type: TRPARI-W_UPGRADEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for G_GENERATE_RULE_AFTER_IMPORT
TT_E071 -
Data type: E071Optional: No
Call by Reference: No ( called with pass by value option)
TT_E071K - Table with the key entries
Data type: E071KOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_GENERATE_RULE_AFTER_IMPORT 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: | ||||
| lt_tt_e071 | TYPE STANDARD TABLE OF E071, " | |||
| lv_iv_tarclient | TYPE E070C-TARCLIENT, " | |||
| lt_tt_e071k | TYPE STANDARD TABLE OF E071K, " | |||
| lv_iv_is_upgrade | TYPE TRPARI-W_UPGRADE. " |
|   CALL FUNCTION 'G_GENERATE_RULE_AFTER_IMPORT' " |
| EXPORTING | ||
| IV_TARCLIENT | = lv_iv_tarclient | |
| IV_IS_UPGRADE | = lv_iv_is_upgrade | |
| TABLES | ||
| TT_E071 | = lt_tt_e071 | |
| TT_E071K | = lt_tt_e071k | |
| . " G_GENERATE_RULE_AFTER_IMPORT | ||
ABAP code using 7.40 inline data declarations to call FM G_GENERATE_RULE_AFTER_IMPORT
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 TARCLIENT FROM E070C INTO @DATA(ld_iv_tarclient). | ||||
| "SELECT single W_UPGRADE FROM TRPARI INTO @DATA(ld_iv_is_upgrade). | ||||
Search for further information about these or an SAP related objects