SAP KKA_ABGR_VORBEREITEN Function Module for









KKA_ABGR_VORBEREITEN is a standard kka abgr vorbereiten 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 kka abgr vorbereiten FM, simply by entering the name KKA_ABGR_VORBEREITEN into the relevant SAP transaction such as SE37 or SE38.

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



Function KKA_ABGR_VORBEREITEN 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 'KKA_ABGR_VORBEREITEN'"
EXPORTING
ABGR_PERIODE = "
ABGR_VERSION = "
LEDGER = "
NUR_MANUELL = "
* NUR_MASCHINELL = ' ' "

IMPORTING
KOPFGRUPPE = "

EXCEPTIONS
NACHRICHT_TYP_A = 1 NACHRICHT_TYP_E = 2
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLKKAG_001 Customer-Specific Postprocessing of Auto. Calculated Results Analysis Data
EXIT_SAPLKKAG_002 Customer-Specific Determination of Planned Values/Valuation Basis
EXIT_SAPLKKAG_003 Customer-Specific Postprocessing of Values from Table COSP
EXIT_SAPLKKAG_004 Customer Change to Results Analysis Cost Elements
EXIT_SAPLKKAG_005 Customer-Specific Postprocessing of Plan Assignment of Dependent Objects
EXIT_SAPLKKAG_006 Customer-Specific Postprocessing of Data from Table COSS
EXIT_SAPLKKAG_007 Customer-Specific Determination of Time Frame and Results Analysis Key
EXIT_SAPLKKAG_008 Customer-Specific Enhancement of Results Analysis

IMPORTING Parameters details for KKA_ABGR_VORBEREITEN

ABGR_PERIODE -

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

ABGR_VERSION -

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

LEDGER -

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

NUR_MANUELL -

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

NUR_MASCHINELL -

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

EXPORTING Parameters details for KKA_ABGR_VORBEREITEN

KOPFGRUPPE -

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

EXCEPTIONS details

NACHRICHT_TYP_A -

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

NACHRICHT_TYP_E -

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

Copy and paste ABAP code example for KKA_ABGR_VORBEREITEN 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_kopfgruppe  TYPE KKALKKAG-KOPFGRUPPE, "   
lv_abgr_periode  TYPE KKALKKAG-ABGRPERIOD, "   
lv_nachricht_typ_a  TYPE KKALKKAG, "   
lv_abgr_version  TYPE KKALKKAG-VERSION, "   
lv_nachricht_typ_e  TYPE KKALKKAG, "   
lv_ledger  TYPE KKALKKAG-LEDGER, "   
lv_nur_manuell  TYPE KKALKKAG-NUR_MANUEL, "   
lv_nur_maschinell  TYPE KKALKKAG-NUR_MASCHI. "   ' '

  CALL FUNCTION 'KKA_ABGR_VORBEREITEN'  "
    EXPORTING
         ABGR_PERIODE = lv_abgr_periode
         ABGR_VERSION = lv_abgr_version
         LEDGER = lv_ledger
         NUR_MANUELL = lv_nur_manuell
         NUR_MASCHINELL = lv_nur_maschinell
    IMPORTING
         KOPFGRUPPE = lv_kopfgruppe
    EXCEPTIONS
        NACHRICHT_TYP_A = 1
        NACHRICHT_TYP_E = 2
. " KKA_ABGR_VORBEREITEN




ABAP code using 7.40 inline data declarations to call FM KKA_ABGR_VORBEREITEN

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 KOPFGRUPPE FROM KKALKKAG INTO @DATA(ld_kopfgruppe).
 
"SELECT single ABGRPERIOD FROM KKALKKAG INTO @DATA(ld_abgr_periode).
 
 
"SELECT single VERSION FROM KKALKKAG INTO @DATA(ld_abgr_version).
 
 
"SELECT single LEDGER FROM KKALKKAG INTO @DATA(ld_ledger).
 
"SELECT single NUR_MANUEL FROM KKALKKAG INTO @DATA(ld_nur_manuell).
 
"SELECT single NUR_MASCHI FROM KKALKKAG INTO @DATA(ld_nur_maschinell).
DATA(ld_nur_maschinell) = ' '.
 


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!