SAP SIPT_BTE_00001020 Function Module for Signature PT: check and lock numberrange
SIPT_BTE_00001020 is a standard sipt bte 00001020 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Signature PT: check and lock numberrange 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 sipt bte 00001020 FM, simply by entering the name SIPT_BTE_00001020 into the relevant SAP transaction such as SE37 or SE38.
Function Group: SIPT_BTE
Program Name: SAPLSIPT_BTE
Main Program: SAPLSIPT_BTE
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SIPT_BTE_00001020 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 'SIPT_BTE_00001020'"Signature PT: check and lock numberrange.
TABLES
T_BSEG = "Belegzeilen
T_BKPF = "Belegkopf
TABLES Parameters details for SIPT_BTE_00001020
T_BSEG - Belegzeilen
Data type: BSEGOptional: No
Call by Reference: No ( called with pass by value option)
T_BKPF - Belegkopf
Data type: BKPFOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SIPT_BTE_00001020 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_t_bseg | TYPE STANDARD TABLE OF BSEG, " | |||
| lt_t_bkpf | TYPE STANDARD TABLE OF BKPF. " |
|   CALL FUNCTION 'SIPT_BTE_00001020' "Signature PT: check and lock numberrange |
| TABLES | ||
| T_BSEG | = lt_t_bseg | |
| T_BKPF | = lt_t_bkpf | |
| . " SIPT_BTE_00001020 | ||
ABAP code using 7.40 inline data declarations to call FM SIPT_BTE_00001020
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