CHANGEDOCUMENT_OPEN SAP Function module - Change document: Open change document creation

CHANGEDOCUMENT_OPEN is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CHANGEDOCUMENT_OPEN into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SCD0
Released Date: 29.01.1995
Processing type: Normal fucntion module

Pattern for FM CHANGEDOCUMENT_OPEN - CHANGEDOCUMENT OPEN

CALL FUNCTION 'CHANGEDOCUMENT_OPEN' "Change document: Open change document creation
  EXPORTING
    objectclass =               " cdhdr-objectclas  Object class name
    objectid =                  " cdhdr-objectid  Object value ID
*   planned_change_number = SPACE  " cdhdr-planchngnr  Task list number
*   planned_or_real_changes = SPACE  " cdhdr-change_ind  Flag whether changes are actual or planned
  EXCEPTIONS
    SEQUENCE_INVALID = 1        "               No CLOSE was called for last object
    .  "  CHANGEDOCUMENT_OPEN

ABAP code example for Function Module CHANGEDOCUMENT_OPEN

The ABAP code below is a full code listing to execute function module CHANGEDOCUMENT_OPEN including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

 

SELECT single OBJECTCLAS 
  FROM CDHDR 
  INTO @DATA(ld_objectclass).

 

SELECT single OBJECTID 
  FROM CDHDR 
  INTO @DATA(ld_objectid).

 

SELECT single PLANCHNGNR 
  FROM CDHDR 
  INTO @DATA(ld_planned_change_number).

 

SELECT single CHANGE_IND 
  FROM CDHDR 
  INTO @DATA(ld_planned_or_real_changes).

.

CALL FUNCTION 'CHANGEDOCUMENT_OPEN'
  EXPORTING
    objectclass =                ld_objectclass
    objectid =                   ld_objectid
*   planned_change_number =      ld_planned_change_number
*   planned_or_real_changes =    ld_planned_or_real_changes
  EXCEPTIONS
    SEQUENCE_INVALID =           1
    .  "  CHANGEDOCUMENT_OPEN

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_objectclass
 
 TYPE CDHDR-OBJECTCLAS ,
ld_objectid
 
 TYPE CDHDR-OBJECTID ,
ld_planned_change_number
 
 TYPE CDHDR-PLANCHNGNR ,
ld_planned_or_real_changes
 
 TYPE CDHDR-CHANGE_IND .



SELECT single OBJECTCLAS 
  FROM CDHDR 
  INTO ld_objectclass.


SELECT single OBJECTID 
  FROM CDHDR 
  INTO ld_objectid.


SELECT single PLANCHNGNR 
  FROM CDHDR 
  INTO ld_planned_change_number.


SELECT single CHANGE_IND 
  FROM CDHDR 
  INTO ld_planned_or_real_changes.

SAP Documentation for FM CHANGEDOCUMENT_OPEN