SAP KKA_ABGR_HOLE_KDU_ZIDS Function Module for
KKA_ABGR_HOLE_KDU_ZIDS is a standard kka abgr hole kdu zids 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 hole kdu zids FM, simply by entering the name KKA_ABGR_HOLE_KDU_ZIDS 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_HOLE_KDU_ZIDS 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_HOLE_KDU_ZIDS'".
EXPORTING
KATEGORIE = "
TABLES
TKKA3000 = "
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_HOLE_KDU_ZIDS
KATEGORIE -
Data type: KKALKKAG-KATEGORIEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for KKA_ABGR_HOLE_KDU_ZIDS
TKKA3000 -
Data type: KKA3000Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KKA_ABGR_HOLE_KDU_ZIDS 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: | ||||
| lt_tkka3000 | TYPE STANDARD TABLE OF KKA3000, " | |||
| lv_kategorie | TYPE KKALKKAG-KATEGORIE. " |
|   CALL FUNCTION 'KKA_ABGR_HOLE_KDU_ZIDS' " |
| EXPORTING | ||
| KATEGORIE | = lv_kategorie | |
| TABLES | ||
| TKKA3000 | = lt_tkka3000 | |
| . " KKA_ABGR_HOLE_KDU_ZIDS | ||
ABAP code using 7.40 inline data declarations to call FM KKA_ABGR_HOLE_KDU_ZIDS
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 KATEGORIE FROM KKALKKAG INTO @DATA(ld_kategorie). | ||||
Search for further information about these or an SAP related objects