SAP CQ_DB_PLMK_READ Function Module for Update characteristic document table from the database









CQ_DB_PLMK_READ is a standard cq db plmk 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 Update characteristic document table from the 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 cq db plmk read FM, simply by entering the name CQ_DB_PLMK_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function CQ_DB_PLMK_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 'CQ_DB_PLMK_READ'"Update characteristic document table from the database
EXPORTING
* DATUB = 0 "Date upper limit
* DATUV = 0 "Date lower limit
* PLNAL = ' ' "selected alternative (optional entry)
PLNNR = "selected routing number
PLNTY = "selected routing type
* SERNB = 0 "
* SERNRKZ = ' ' "
* SERNV = 0 "

IMPORTING
FLG_NOT_FOUND = "No data for selection criteria
ZAEHL_MAX_PLMK = "

TABLES
PLANMK = "Characteristic document table

EXCEPTIONS
NO_RECORDS = 1
.



IMPORTING Parameters details for CQ_DB_PLMK_READ

DATUB - Date upper limit

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

DATUV - Date lower limit

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

PLNAL - selected alternative (optional entry)

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)

SERNB -

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

SERNRKZ -

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

SERNV -

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

EXPORTING Parameters details for CQ_DB_PLMK_READ

FLG_NOT_FOUND - No data for selection criteria

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

ZAEHL_MAX_PLMK -

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

TABLES Parameters details for CQ_DB_PLMK_READ

PLANMK - Characteristic document table

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

EXCEPTIONS details

NO_RECORDS - No records exist for the selected plan no.

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

Copy and paste ABAP code example for CQ_DB_PLMK_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_planmk  TYPE STANDARD TABLE OF PLMKB, "   
lv_no_records  TYPE PLMKB, "   
lv_flg_not_found  TYPE PLMKB, "   
lv_datuv  TYPE PLKO-DATUV, "   0
lv_zaehl_max_plmk  TYPE PLMK-ZAEHL, "   
lv_plnal  TYPE PLKO-PLNAL, "   SPACE
lv_plnnr  TYPE PLKO-PLNNR, "   
lv_plnty  TYPE PLKO-PLNTY, "   
lv_sernb  TYPE RQPAS-SERNV, "   0
lv_sernrkz  TYPE RQPAS-SERNRKZ, "   SPACE
lv_sernv  TYPE RQPAS-SERNV. "   0

  CALL FUNCTION 'CQ_DB_PLMK_READ'  "Update characteristic document table from the database
    EXPORTING
         DATUB = lv_datub
         DATUV = lv_datuv
         PLNAL = lv_plnal
         PLNNR = lv_plnnr
         PLNTY = lv_plnty
         SERNB = lv_sernb
         SERNRKZ = lv_sernrkz
         SERNV = lv_sernv
    IMPORTING
         FLG_NOT_FOUND = lv_flg_not_found
         ZAEHL_MAX_PLMK = lv_zaehl_max_plmk
    TABLES
         PLANMK = lt_planmk
    EXCEPTIONS
        NO_RECORDS = 1
. " CQ_DB_PLMK_READ




ABAP code using 7.40 inline data declarations to call FM CQ_DB_PLMK_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 DATUV FROM PLKO INTO @DATA(ld_datuv).
 
"SELECT single ZAEHL FROM PLMK INTO @DATA(ld_zaehl_max_plmk).
 
"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).
 
"SELECT single SERNV FROM RQPAS INTO @DATA(ld_sernb).
 
"SELECT single SERNRKZ FROM RQPAS INTO @DATA(ld_sernrkz).
DATA(ld_sernrkz) = ' '.
 
"SELECT single SERNV FROM RQPAS INTO @DATA(ld_sernv).
 


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!