SAP CHANGEDOCU_CDPOS_READ Function Module for

Search SAP Function Modules

CHANGEDOCU_CDPOS_READ is a standard changedocu cdpos read 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 changedocu cdpos read FM, simply by entering the name CHANGEDOCU_CDPOS_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCD1
Program Name: SAPLSCD1
Main Program: SAPLSCD1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CHANGEDOCU_CDPOS_READ 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 'CHANGEDOCU_CDPOS_READ'"
  EXPORTING
*  IV_OBJECTCLAS = ' ' "Object Class
*  IV_OBJECTID = ' ' "Object Value
*  IV_CHANGENR = ' ' "Document change number
*  IV_TABNAME = ' ' "Table Name
*  IV_TABKEY = ' ' "Table Key for CDPOS in Character 254
*  IV_FNAME = ' ' "Field Name
*  IV_PCDPOS_FLAG = ' ' "Single-Character Flag
*  IV_CLIENT = ' ' "

 IMPORTING
   EV_COUNT =  "No. of Data Records Found
   ET_CDPOS =  "Internal Table for cdpos
   ET_PCDPOS =  "Table type of PCDPOS (positions of planned changes)

EXCEPTIONS
   NO_IMPORTPARAMETER = 1 

.

IMPORTING Parameters details for CHANGEDOCU_CDPOS_READ

IV_OBJECTCLAS - Object Class

Data type: CDHDR-OBJECTCLAS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_OBJECTID - Object Value

Data type: CDHDR-OBJECTID
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CHANGENR - Document change number

Data type: CDHDR-CHANGENR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TABNAME - Table Name

Data type: CDPOS-TABNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TABKEY - Table Key for CDPOS in Character 254

Data type: CDPOS-TABKEY
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_FNAME - Field Name

Data type: CDPOS-FNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PCDPOS_FLAG - Single-Character Flag

Data type: CHAR1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CLIENT -

Data type: MANDT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CHANGEDOCU_CDPOS_READ

EV_COUNT - No. of Data Records Found

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

ET_CDPOS - Internal Table for cdpos

Data type: CDPOS_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

ET_PCDPOS - Table type of PCDPOS (positions of planned changes)

Data type: PCDPOS_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_IMPORTPARAMETER -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CHANGEDOCU_CDPOS_READ 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.

ABAP code using 7.40 inline data declarations to call FM CHANGEDOCU_CDPOS_READ

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