SAP CN_DB_PLAB_READ Function Module for Read relationships in database









CN_DB_PLAB_READ is a standard cn db plab 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 Read relationships in database 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 cn db plab read FM, simply by entering the name CN_DB_PLAB_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function CN_DB_PLAB_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 'CN_DB_PLAB_READ'"Read relationships in database
EXPORTING
DATUB = "Date upper limit for DB selection
DATUV = "Date lower limit for DB selection
* FLG_ORDER = ' ' "
* PLNAL = ' ' "selected alternative (operation specification)
PLNNR = "selected task list number
PLNTY = "selected task list type
* FLG_CHK_LOEKZ = ' ' "

IMPORTING
ZAEHL_MAX = "max. counter of changes

TABLES
PLANAOB = "Table corresponds to the document table of the AOBs

EXCEPTIONS
NO_RECORDS = 1
.



IMPORTING Parameters details for CN_DB_PLAB_READ

DATUB - Date upper limit for DB selection

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

DATUV - Date lower limit for DB selection

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

FLG_ORDER -

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

PLNAL - selected alternative (operation specification)

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

PLNNR - selected task list number

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

PLNTY - selected task list type

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

FLG_CHK_LOEKZ -

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

EXPORTING Parameters details for CN_DB_PLAB_READ

ZAEHL_MAX - max. counter of changes

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

TABLES Parameters details for CN_DB_PLAB_READ

PLANAOB - Table corresponds to the document table of the AOBs

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

EXCEPTIONS details

NO_RECORDS - No records exist for the selected task list no.

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

Copy and paste ABAP code example for CN_DB_PLAB_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, "   
lt_planaob  TYPE STANDARD TABLE OF PLABB, "   
lv_zaehl_max  TYPE PLMZ-ZAEHL, "   
lv_no_records  TYPE PLMZ, "   
lv_datuv  TYPE PLKO-DATUV, "   
lv_flg_order  TYPE RC27X-FLG_SEL, "   SPACE
lv_plnal  TYPE PLKO-PLNAL, "   ' '
lv_plnnr  TYPE PLAB-PLNNR, "   
lv_plnty  TYPE PLKO-PLNTY, "   
lv_flg_chk_loekz  TYPE PLKO-LOEKZ. "   SPACE

  CALL FUNCTION 'CN_DB_PLAB_READ'  "Read relationships in database
    EXPORTING
         DATUB = lv_datub
         DATUV = lv_datuv
         FLG_ORDER = lv_flg_order
         PLNAL = lv_plnal
         PLNNR = lv_plnnr
         PLNTY = lv_plnty
         FLG_CHK_LOEKZ = lv_flg_chk_loekz
    IMPORTING
         ZAEHL_MAX = lv_zaehl_max
    TABLES
         PLANAOB = lt_planaob
    EXCEPTIONS
        NO_RECORDS = 1
. " CN_DB_PLAB_READ




ABAP code using 7.40 inline data declarations to call FM CN_DB_PLAB_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 PLMZ INTO @DATA(ld_zaehl_max).
 
 
"SELECT single DATUV FROM PLKO INTO @DATA(ld_datuv).
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_flg_order).
DATA(ld_flg_order) = ' '.
 
"SELECT single PLNAL FROM PLKO INTO @DATA(ld_plnal).
DATA(ld_plnal) = ' '.
 
"SELECT single PLNNR FROM PLAB INTO @DATA(ld_plnnr).
 
"SELECT single PLNTY FROM PLKO INTO @DATA(ld_plnty).
 
"SELECT single LOEKZ FROM PLKO INTO @DATA(ld_flg_chk_loekz).
DATA(ld_flg_chk_loekz) = ' '.
 


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!