SAP FLQ_DEFAULT_ASSIGN_DK Function Module for
FLQ_DEFAULT_ASSIGN_DK is a standard flq default assign dk SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 flq default assign dk FM, simply by entering the name FLQ_DEFAULT_ASSIGN_DK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FLQCCR
Program Name: SAPLFLQCCR
Main Program: SAPLFLQCCR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FLQ_DEFAULT_ASSIGN_DK 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 'FLQ_DEFAULT_ASSIGN_DK'".
EXPORTING
P_BKPF = "
P_BSEG = "
P_KNA1 = "
P_LFA1 = "
P_ACTUAL_KEY = "
* P_D_SEQUENCE = "
* P_C_SEQUENCE = "
P_OLD_ASSIGNMENT = "
IMPORTING
E_NEW_ASSIGNMENT = "
E_QUERY = "
E_QUERYTYPE = "
IMPORTING Parameters details for FLQ_DEFAULT_ASSIGN_DK
P_BKPF -
Data type: BKPFOptional: No
Call by Reference: Yes
P_BSEG -
Data type: BSEGOptional: No
Call by Reference: Yes
P_KNA1 -
Data type: KNA1Optional: No
Call by Reference: Yes
P_LFA1 -
Data type: LFA1Optional: No
Call by Reference: Yes
P_ACTUAL_KEY -
Data type: BSEG_KEYOptional: No
Call by Reference: Yes
P_D_SEQUENCE -
Data type: FLQGRPIDOptional: Yes
Call by Reference: Yes
P_C_SEQUENCE -
Data type: FLQGRPIDOptional: Yes
Call by Reference: Yes
P_OLD_ASSIGNMENT -
Data type: FLQ_ASSIGNMENTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FLQ_DEFAULT_ASSIGN_DK
E_NEW_ASSIGNMENT -
Data type: FLQ_ASSIGNMENTOptional: No
Call by Reference: Yes
E_QUERY -
Data type: FLQQRIDOptional: No
Call by Reference: Yes
E_QUERYTYPE -
Data type: FLQORIGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FLQ_DEFAULT_ASSIGN_DK 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_p_bkpf | TYPE BKPF, " | |||
| lv_e_new_assignment | TYPE FLQ_ASSIGNMENT, " | |||
| lv_p_bseg | TYPE BSEG, " | |||
| lv_e_query | TYPE FLQQRID, " | |||
| lv_p_kna1 | TYPE KNA1, " | |||
| lv_e_querytype | TYPE FLQORIG, " | |||
| lv_p_lfa1 | TYPE LFA1, " | |||
| lv_p_actual_key | TYPE BSEG_KEY, " | |||
| lv_p_d_sequence | TYPE FLQGRPID, " | |||
| lv_p_c_sequence | TYPE FLQGRPID, " | |||
| lv_p_old_assignment | TYPE FLQ_ASSIGNMENT. " |
|   CALL FUNCTION 'FLQ_DEFAULT_ASSIGN_DK' " |
| EXPORTING | ||
| P_BKPF | = lv_p_bkpf | |
| P_BSEG | = lv_p_bseg | |
| P_KNA1 | = lv_p_kna1 | |
| P_LFA1 | = lv_p_lfa1 | |
| P_ACTUAL_KEY | = lv_p_actual_key | |
| P_D_SEQUENCE | = lv_p_d_sequence | |
| P_C_SEQUENCE | = lv_p_c_sequence | |
| P_OLD_ASSIGNMENT | = lv_p_old_assignment | |
| IMPORTING | ||
| E_NEW_ASSIGNMENT | = lv_e_new_assignment | |
| E_QUERY | = lv_e_query | |
| E_QUERYTYPE | = lv_e_querytype | |
| . " FLQ_DEFAULT_ASSIGN_DK | ||
ABAP code using 7.40 inline data declarations to call FM FLQ_DEFAULT_ASSIGN_DK
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