SAP KL_DR_BCA_DERIVE Function Module for Derivation for BCA
KL_DR_BCA_DERIVE is a standard kl dr bca derive SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Derivation for BCA 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 kl dr bca derive FM, simply by entering the name KL_DR_BCA_DERIVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: KLDR
Program Name: SAPLKLDR
Main Program: SAPLKLDR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function KL_DR_BCA_DERIVE 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 'KL_DR_BCA_DERIVE'"Derivation for BCA.
EXPORTING
I_DINP = "Single-Character Flag
CHANGING
C_JBKLJOBJ1 = "FO Limit Part: Data and Status Information
EXCEPTIONS
DERIVATION_FAILED = 1
IMPORTING Parameters details for KL_DR_BCA_DERIVE
I_DINP - Single-Character Flag
Data type: BUS000FLDS-CHAR1Optional: No
Call by Reference: Yes
CHANGING Parameters details for KL_DR_BCA_DERIVE
C_JBKLJOBJ1 - FO Limit Part: Data and Status Information
Data type: JBKLOBJ1_EXTOptional: No
Call by Reference: Yes
EXCEPTIONS details
DERIVATION_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KL_DR_BCA_DERIVE 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_i_dinp | TYPE BUS000FLDS-CHAR1, " | |||
| lv_c_jbkljobj1 | TYPE JBKLOBJ1_EXT, " | |||
| lv_derivation_failed | TYPE JBKLOBJ1_EXT. " |
|   CALL FUNCTION 'KL_DR_BCA_DERIVE' "Derivation for BCA |
| EXPORTING | ||
| I_DINP | = lv_i_dinp | |
| CHANGING | ||
| C_JBKLJOBJ1 | = lv_c_jbkljobj1 | |
| EXCEPTIONS | ||
| DERIVATION_FAILED = 1 | ||
| . " KL_DR_BCA_DERIVE | ||
ABAP code using 7.40 inline data declarations to call FM KL_DR_BCA_DERIVE
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 CHAR1 FROM BUS000FLDS INTO @DATA(ld_i_dinp). | ||||
Search for further information about these or an SAP related objects