SAP KQD_GET_LIMITS Function Module for Provides the limits for quality score calculation
KQD_GET_LIMITS is a standard kqd get limits SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Provides the limits for quality score calculation 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 kqd get limits FM, simply by entering the name KQD_GET_LIMITS into the relevant SAP transaction such as SE37 or SE38.
Function Group: QAQD
Program Name: SAPLQAQD
Main Program:
Appliation area: Q
Release date: 05-Oct-1993
Mode(Normal, Remote etc): Normal Function Module
Update:

Function KQD_GET_LIMITS 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 'KQD_GET_LIMITS'"Provides the limits for quality score calculation.
IMPORTING
E_KQD_MAX = "Maximum allowed quality score
E_KQD_MIN = "
EXPORTING Parameters details for KQD_GET_LIMITS
E_KQD_MAX - Maximum allowed quality score
Data type: QAVE-QKENNZAHLOptional: No
Call by Reference: No ( called with pass by value option)
E_KQD_MIN -
Data type: QAVE-QKENNZAHLOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KQD_GET_LIMITS 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_e_kqd_max | TYPE QAVE-QKENNZAHL, " | |||
| lv_e_kqd_min | TYPE QAVE-QKENNZAHL. " |
|   CALL FUNCTION 'KQD_GET_LIMITS' "Provides the limits for quality score calculation |
| IMPORTING | ||
| E_KQD_MAX | = lv_e_kqd_max | |
| E_KQD_MIN | = lv_e_kqd_min | |
| . " KQD_GET_LIMITS | ||
ABAP code using 7.40 inline data declarations to call FM KQD_GET_LIMITS
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 QKENNZAHL FROM QAVE INTO @DATA(ld_e_kqd_max). | ||||
| "SELECT single QKENNZAHL FROM QAVE INTO @DATA(ld_e_kqd_min). | ||||
Search for further information about these or an SAP related objects