SAP J_1I7_USEREXIT_NUMKI Function Module for User exit for number key in certificate numbering
J_1I7_USEREXIT_NUMKI is a standard j 1i7 userexit numki SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User exit for number key in certificate numbering 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 j 1i7 userexit numki FM, simply by entering the name J_1I7_USEREXIT_NUMKI into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1I7
Program Name: SAPLJ1I7
Main Program: SAPLJ1I7
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1I7_USEREXIT_NUMKI 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 'J_1I7_USEREXIT_NUMKI'"User exit for number key in certificate numbering.
CHANGING
* TEMP_NUMKI = ' ' "Number range number
TABLES
TEMP_BUKRS = "
TEMP_SECT = "
TEMP_GSBER = "
CHANGING Parameters details for J_1I7_USEREXIT_NUMKI
TEMP_NUMKI - Number range number
Data type: INRI-NRRANGENRDefault: SPACE
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for J_1I7_USEREXIT_NUMKI
TEMP_BUKRS -
Data type:Optional: No
Call by Reference: Yes
TEMP_SECT -
Data type:Optional: No
Call by Reference: Yes
TEMP_GSBER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1I7_USEREXIT_NUMKI 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_temp_bukrs | TYPE STANDARD TABLE OF STRING, " | |||
| lv_temp_numki | TYPE INRI-NRRANGENR, " SPACE | |||
| lt_temp_sect | TYPE STANDARD TABLE OF INRI, " | |||
| lt_temp_gsber | TYPE STANDARD TABLE OF INRI. " |
|   CALL FUNCTION 'J_1I7_USEREXIT_NUMKI' "User exit for number key in certificate numbering |
| CHANGING | ||
| TEMP_NUMKI | = lv_temp_numki | |
| TABLES | ||
| TEMP_BUKRS | = lt_temp_bukrs | |
| TEMP_SECT | = lt_temp_sect | |
| TEMP_GSBER | = lt_temp_gsber | |
| . " J_1I7_USEREXIT_NUMKI | ||
ABAP code using 7.40 inline data declarations to call FM J_1I7_USEREXIT_NUMKI
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 NRRANGENR FROM INRI INTO @DATA(ld_temp_numki). | ||||
| DATA(ld_temp_numki) | = ' '. | |||
Search for further information about these or an SAP related objects