SAP PLANNED_CHANGES_READ_POSITIONS Function Module for Change document: Read and edit scheduling items

Search SAP Function Modules

PLANNED_CHANGES_READ_POSITIONS is a standard planned changes read positions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change document: Read and edit scheduling items 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 planned changes read positions FM, simply by entering the name PLANNED_CHANGES_READ_POSITIONS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCD3
Program Name: SAPLSCD3
Main Program: SAPLSCD3
Appliation area: *
Release date: 19-Dec-1994
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PLANNED_CHANGES_READ_POSITIONS 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 'PLANNED_CHANGES_READ_POSITIONS'"Change document: Read and edit scheduling items
  EXPORTING
*  OBJECTCLAS = ' ' "Object Class
*  OBJECTID = ' ' "Object value
   CHANGENUMBER =  "Change document number
*  TABLEKEY = ' ' "Table key of object class table
*  TABLENAME = ' ' "Object class table name
*  TABLEKEY254 = ' ' "Table Key for CDPOS in Character 254

 IMPORTING
   HEADER =  "Change document header (structure CDHDR)
   ET_CDRED_STR =  "Table Type for Structure CDRED_STR

TABLES
   EDITPOS =  "Table with edited change document items

EXCEPTIONS
   NO_POSITION_FOUND = 1 

.

IMPORTING Parameters details for PLANNED_CHANGES_READ_POSITIONS

OBJECTCLAS - Object Class

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

OBJECTID - Object value

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

CHANGENUMBER - Change document number

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

TABLEKEY - Table key of object class table

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

TABLENAME - Object class table name

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

TABLEKEY254 - Table Key for CDPOS in Character 254

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

EXPORTING Parameters details for PLANNED_CHANGES_READ_POSITIONS

HEADER - Change document header (structure CDHDR)

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

ET_CDRED_STR - Table Type for Structure CDRED_STR

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

TABLES Parameters details for PLANNED_CHANGES_READ_POSITIONS

EDITPOS - Table with edited change document items

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

EXCEPTIONS details

NO_POSITION_FOUND - No item found

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

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

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