SAP CHANGEDOCUMENT_INSERT_NUMBER Function Module for
CHANGEDOCUMENT_INSERT_NUMBER is a standard changedocument insert number 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 changedocument insert number FM, simply by entering the name CHANGEDOCUMENT_INSERT_NUMBER into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCD0
Program Name: SAPLSCD0
Main Program: SAPLSCD0
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function CHANGEDOCUMENT_INSERT_NUMBER 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 'CHANGEDOCUMENT_INSERT_NUMBER'".
EXPORTING
OBJECTCLASS = "Object Class
OBJECTID = "Object ID
TABLES
PLANNED_CHANGES_NUMBERS = "
IMPORTING Parameters details for CHANGEDOCUMENT_INSERT_NUMBER
OBJECTCLASS - Object Class
Data type: CDHDR-OBJECTCLASOptional: No
Call by Reference: No ( called with pass by value option)
OBJECTID - Object ID
Data type: CDHDR-OBJECTIDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CHANGEDOCUMENT_INSERT_NUMBER
PLANNED_CHANGES_NUMBERS -
Data type: CDNUMBERSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CHANGEDOCUMENT_INSERT_NUMBER 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_objectclass | TYPE CDHDR-OBJECTCLAS, " | |||
| lt_planned_changes_numbers | TYPE STANDARD TABLE OF CDNUMBERS, " | |||
| lv_objectid | TYPE CDHDR-OBJECTID. " |
|   CALL FUNCTION 'CHANGEDOCUMENT_INSERT_NUMBER' " |
| EXPORTING | ||
| OBJECTCLASS | = lv_objectclass | |
| OBJECTID | = lv_objectid | |
| TABLES | ||
| PLANNED_CHANGES_NUMBERS | = lt_planned_changes_numbers | |
| . " CHANGEDOCUMENT_INSERT_NUMBER | ||
ABAP code using 7.40 inline data declarations to call FM CHANGEDOCUMENT_INSERT_NUMBER
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 OBJECTCLAS FROM CDHDR INTO @DATA(ld_objectclass). | ||||
| "SELECT single OBJECTID FROM CDHDR INTO @DATA(ld_objectid). | ||||
Search for further information about these or an SAP related objects