SAP CP_DB_PLFL_READ Function Module for NOTRANSL: Füllen der Folgen-Belegtabelle von der Datenbank









CP_DB_PLFL_READ is a standard cp db plfl read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Füllen der Folgen-Belegtabelle von der Datenbank 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 cp db plfl read FM, simply by entering the name CP_DB_PLFL_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function CP_DB_PLFL_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 'CP_DB_PLFL_READ'"NOTRANSL: Füllen der Folgen-Belegtabelle von der Datenbank
EXPORTING
* DATUB = 0 "Date upper limit for DB selection
* DATUV = 0 "Date lower limit for DB selection
* PLNAL = ' ' "selected alternative (optional ent
PLNNR = "selected routing number
PLNTY = "selected routing type

IMPORTING
ZAEHL_MAX = "max. change counter

TABLES
PLANFL = "Planning sequences document table

EXCEPTIONS
NO_RECORDS = 1
.



IMPORTING Parameters details for CP_DB_PLFL_READ

DATUB - Date upper limit for DB selection

Data type: PLKO-DATUV
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATUV - Date lower limit for DB selection

Data type: PLKO-DATUV
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLNAL - selected alternative (optional ent

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

PLNNR - selected routing number

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

PLNTY - selected routing type

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

EXPORTING Parameters details for CP_DB_PLFL_READ

ZAEHL_MAX - max. change counter

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

TABLES Parameters details for CP_DB_PLFL_READ

PLANFL - Planning sequences document table

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

EXCEPTIONS details

NO_RECORDS - No data records exist for the sele

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

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

DATA:
lv_datub  TYPE PLKO-DATUV, "   0
lt_planfl  TYPE STANDARD TABLE OF PLFLB, "   
lv_zaehl_max  TYPE PLFL-ZAEHL, "   
lv_no_records  TYPE PLFL, "   
lv_datuv  TYPE PLKO-DATUV, "   0
lv_plnal  TYPE PLKO-PLNAL, "   SPACE
lv_plnnr  TYPE PLKO-PLNNR, "   
lv_plnty  TYPE PLKO-PLNTY. "   

  CALL FUNCTION 'CP_DB_PLFL_READ'  "NOTRANSL: Füllen der Folgen-Belegtabelle von der Datenbank
    EXPORTING
         DATUB = lv_datub
         DATUV = lv_datuv
         PLNAL = lv_plnal
         PLNNR = lv_plnnr
         PLNTY = lv_plnty
    IMPORTING
         ZAEHL_MAX = lv_zaehl_max
    TABLES
         PLANFL = lt_planfl
    EXCEPTIONS
        NO_RECORDS = 1
. " CP_DB_PLFL_READ




ABAP code using 7.40 inline data declarations to call FM CP_DB_PLFL_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.

"SELECT single DATUV FROM PLKO INTO @DATA(ld_datub).
 
 
"SELECT single ZAEHL FROM PLFL INTO @DATA(ld_zaehl_max).
 
 
"SELECT single DATUV FROM PLKO INTO @DATA(ld_datuv).
 
"SELECT single PLNAL FROM PLKO INTO @DATA(ld_plnal).
DATA(ld_plnal) = ' '.
 
"SELECT single PLNNR FROM PLKO INTO @DATA(ld_plnnr).
 
"SELECT single PLNTY FROM PLKO INTO @DATA(ld_plnty).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!