SAP J_1B_CIAP_CREATE_CHANGE_DOC Function Module for Create Change Document
J_1B_CIAP_CREATE_CHANGE_DOC is a standard j 1b ciap create change doc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Change Document 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 1b ciap create change doc FM, simply by entering the name J_1B_CIAP_CREATE_CHANGE_DOC into the relevant SAP transaction such as SE37 or SE38.
Function Group: J_1B_CIAP_DIALOG
Program Name: SAPLJ_1B_CIAP_DIALOG
Main Program: SAPLJ_1B_CIAP_DIALOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function J_1B_CIAP_CREATE_CHANGE_DOC 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_1B_CIAP_CREATE_CHANGE_DOC'"Create Change Document.
EXPORTING
IV_OBJECTID = "Object value
IV_OBJECTCLASS = "Object class
IV_CHANGE_IND = "Change type (U, I, E, D)
IV_TCODE = "Transaction in which a change was made
IV_UDATE = "Creation date of the change document
IV_UTIME = "Time changed
IV_USERNAME = "User name of the person responsible in change document
IS_CIAP_OBJ_OLD = "CIAP Object Structure
IS_CIAP_OBJ_NEW = "CIAP Object Structure
IMPORTING Parameters details for J_1B_CIAP_CREATE_CHANGE_DOC
IV_OBJECTID - Object value
Data type: CDHDR-OBJECTIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_OBJECTCLASS - Object class
Data type: CDHDR-OBJECTCLASOptional: No
Call by Reference: No ( called with pass by value option)
IV_CHANGE_IND - Change type (U, I, E, D)
Data type: CDPOS-CHNGINDOptional: No
Call by Reference: No ( called with pass by value option)
IV_TCODE - Transaction in which a change was made
Data type: CDHDR-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
IV_UDATE - Creation date of the change document
Data type: CDHDR-UDATEOptional: No
Call by Reference: No ( called with pass by value option)
IV_UTIME - Time changed
Data type: CDHDR-UTIMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_USERNAME - User name of the person responsible in change document
Data type: CDHDR-USERNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IS_CIAP_OBJ_OLD - CIAP Object Structure
Data type: STR_CIAP_OBJOptional: No
Call by Reference: No ( called with pass by value option)
IS_CIAP_OBJ_NEW - CIAP Object Structure
Data type: STR_CIAP_OBJOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_1B_CIAP_CREATE_CHANGE_DOC 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_iv_objectid | TYPE CDHDR-OBJECTID, " | |||
| lv_iv_objectclass | TYPE CDHDR-OBJECTCLAS, " | |||
| lv_iv_change_ind | TYPE CDPOS-CHNGIND, " | |||
| lv_iv_tcode | TYPE CDHDR-TCODE, " | |||
| lv_iv_udate | TYPE CDHDR-UDATE, " | |||
| lv_iv_utime | TYPE CDHDR-UTIME, " | |||
| lv_iv_username | TYPE CDHDR-USERNAME, " | |||
| lv_is_ciap_obj_old | TYPE STR_CIAP_OBJ, " | |||
| lv_is_ciap_obj_new | TYPE STR_CIAP_OBJ. " |
|   CALL FUNCTION 'J_1B_CIAP_CREATE_CHANGE_DOC' "Create Change Document |
| EXPORTING | ||
| IV_OBJECTID | = lv_iv_objectid | |
| IV_OBJECTCLASS | = lv_iv_objectclass | |
| IV_CHANGE_IND | = lv_iv_change_ind | |
| IV_TCODE | = lv_iv_tcode | |
| IV_UDATE | = lv_iv_udate | |
| IV_UTIME | = lv_iv_utime | |
| IV_USERNAME | = lv_iv_username | |
| IS_CIAP_OBJ_OLD | = lv_is_ciap_obj_old | |
| IS_CIAP_OBJ_NEW | = lv_is_ciap_obj_new | |
| . " J_1B_CIAP_CREATE_CHANGE_DOC | ||
ABAP code using 7.40 inline data declarations to call FM J_1B_CIAP_CREATE_CHANGE_DOC
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 OBJECTID FROM CDHDR INTO @DATA(ld_iv_objectid). | ||||
| "SELECT single OBJECTCLAS FROM CDHDR INTO @DATA(ld_iv_objectclass). | ||||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_iv_change_ind). | ||||
| "SELECT single TCODE FROM CDHDR INTO @DATA(ld_iv_tcode). | ||||
| "SELECT single UDATE FROM CDHDR INTO @DATA(ld_iv_udate). | ||||
| "SELECT single UTIME FROM CDHDR INTO @DATA(ld_iv_utime). | ||||
| "SELECT single USERNAME FROM CDHDR INTO @DATA(ld_iv_username). | ||||
Search for further information about these or an SAP related objects