SAP CY_BT_KBED_IDV_TAB_GET Function Module for NOTRANSL: Einzelkapazitätsbedarfe eines Kapazitätsbedarfs aus der Belegtab









CY_BT_KBED_IDV_TAB_GET is a standard cy bt kbed idv tab get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Einzelkapazitätsbedarfe eines Kapazitätsbedarfs aus der Belegtab 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 cy bt kbed idv tab get FM, simply by entering the name CY_BT_KBED_IDV_TAB_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: CYBT
Program Name: SAPLCYBT
Main Program: SAPLCYBT
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CY_BT_KBED_IDV_TAB_GET 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 'CY_BT_KBED_IDV_TAB_GET'"NOTRANSL: Einzelkapazitätsbedarfe eines Kapazitätsbedarfs aus der Belegtab
  EXPORTING
*  I_AUFNR = ' ' "Order Number
*  I_BEDID = '000000000000' "ID of the Capacity Requirements Record
   I_BEDZL =  "Internal counter
   I_CANUM =  "Counters for cap. rqmts. records (various caps. + indiv.caps
*  I_KBED_TYPKZ = ' ' "Scheduling Level
*  I_FLG_CONV = ' ' "Generic Type
*  I_FLG_WORK = ' ' "Read Work Center

 IMPORTING
   E_ENTRIES =  "ABAP System Field: Row Index of Internal Tables

TABLES
   T_KBEDD =  "Capacity requirements: dialog table for KBED

EXCEPTIONS
   NO_ENTRY = 1
.



IMPORTING Parameters details for CY_BT_KBED_IDV_TAB_GET

I_AUFNR - Order Number

Data type: CAUFVD-AUFNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BEDID - ID of the Capacity Requirements Record

Data type: KBED-BEDID
Default: '000000000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BEDZL - Internal counter

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

I_CANUM - Counters for cap. rqmts. records (various caps. + indiv.caps

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

I_KBED_TYPKZ - Scheduling Level

Data type: KBED-TYPKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_CONV - Generic Type

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_WORK - Read Work Center

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CY_BT_KBED_IDV_TAB_GET

E_ENTRIES - ABAP System Field: Row Index of Internal Tables

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

TABLES Parameters details for CY_BT_KBED_IDV_TAB_GET

T_KBEDD - Capacity requirements: dialog table for KBED

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

EXCEPTIONS details

NO_ENTRY - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for CY_BT_KBED_IDV_TAB_GET 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_aufnr  TYPE CAUFVD-AUFNR, "   SPACE
lt_t_kbedd  TYPE STANDARD TABLE OF KBEDD, "   
lv_no_entry  TYPE KBEDD, "   
lv_e_entries  TYPE SY-TABIX, "   
lv_i_bedid  TYPE KBED-BEDID, "   '000000000000'
lv_i_bedzl  TYPE KBED-BEDZL, "   
lv_i_canum  TYPE KBED-CANUM, "   
lv_i_kbed_typkz  TYPE KBED-TYPKZ, "   SPACE
lv_i_flg_conv  TYPE C, "   SPACE
lv_i_flg_work  TYPE C. "   SPACE

  CALL FUNCTION 'CY_BT_KBED_IDV_TAB_GET'  "NOTRANSL: Einzelkapazitätsbedarfe eines Kapazitätsbedarfs aus der Belegtab
    EXPORTING
         I_AUFNR = lv_i_aufnr
         I_BEDID = lv_i_bedid
         I_BEDZL = lv_i_bedzl
         I_CANUM = lv_i_canum
         I_KBED_TYPKZ = lv_i_kbed_typkz
         I_FLG_CONV = lv_i_flg_conv
         I_FLG_WORK = lv_i_flg_work
    IMPORTING
         E_ENTRIES = lv_e_entries
    TABLES
         T_KBEDD = lt_t_kbedd
    EXCEPTIONS
        NO_ENTRY = 1
. " CY_BT_KBED_IDV_TAB_GET




ABAP code using 7.40 inline data declarations to call FM CY_BT_KBED_IDV_TAB_GET

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 AUFNR FROM CAUFVD INTO @DATA(ld_i_aufnr).
DATA(ld_i_aufnr) = ' '.
 
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_e_entries).
 
"SELECT single BEDID FROM KBED INTO @DATA(ld_i_bedid).
DATA(ld_i_bedid) = '000000000000'.
 
"SELECT single BEDZL FROM KBED INTO @DATA(ld_i_bedzl).
 
"SELECT single CANUM FROM KBED INTO @DATA(ld_i_canum).
 
"SELECT single TYPKZ FROM KBED INTO @DATA(ld_i_kbed_typkz).
DATA(ld_i_kbed_typkz) = ' '.
 
DATA(ld_i_flg_conv) = ' '.
 
DATA(ld_i_flg_work) = ' '.
 


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!