SAP CO_MK_IBAPI_BDTER_CHECK Function Module for NOTRANSL: Bedarfstermin setzen und prüfen









CO_MK_IBAPI_BDTER_CHECK is a standard co mk ibapi bdter check 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: Bedarfstermin setzen und prüfen 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 co mk ibapi bdter check FM, simply by entering the name CO_MK_IBAPI_BDTER_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function CO_MK_IBAPI_BDTER_CHECK 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 'CO_MK_IBAPI_BDTER_CHECK'"NOTRANSL: Bedarfstermin setzen und prüfen
EXPORTING
I_CAUFVD = "Dialog Structure for Order Headers and Items
I_AFVGD = "Order: Dialog Table for Table AFVG (Order Operation)
I_RESBD = "Reservation/Dependent Requirements
I_RESBD_SAV = "Reservation/Dependent Requirements
* I_NO_DIALOGUE = YX "Single-Character Indicator

IMPORTING
E_RESBD = "Reservation/Dependent Requirements

EXCEPTIONS
UNSPECIFIED_ERROR = 1 SPECIFIED_ERROR = 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_SAPLCOMK_001 User Exit for Material Components
EXIT_SAPLCOMK_002 User Exit: BOM Explosion on Component Overview
EXIT_SAPLCOMK_003 Maintenance Order: Customer Enhancement for Component Selection
EXIT_SAPLCOMK_004 PM Order: Customer Enhancement - Default for Item Cat. in Comp. Assignmt
EXIT_SAPLCOMK_005 User Exit for Checking Changes to Components in Order
EXIT_SAPLCOMK_006 Enhancement in the adding and changing of components
EXIT_SAPLCOMK_007 Customer Enhancement: Plant and Storage Location Determination f. Compon.
EXIT_SAPLCOMK_008 Change Priorities for Selection Criteria for Batch Determination
EXIT_SAPLCOMK_009 Update Result of BOM Assignment
EXIT_SAPLCOMK_010 User Exit for Checking Component Changes in the Production Order
EXIT_SAPLCOMK_011 Check a Newly Assigned Component
EXIT_SAPLCOMK_012 Check a changed component
EXIT_SAPLCOMK_013 Check Whether Component can be Deleted
EXIT_SAPLCOMK_014 Checks Changes to Order Components
EXIT_SAPLCOMK_029 Inclusion of Bill of Material in PM/SM Order

IMPORTING Parameters details for CO_MK_IBAPI_BDTER_CHECK

I_CAUFVD - Dialog Structure for Order Headers and Items

Data type: CAUFVD
Optional: No
Call by Reference: Yes

I_AFVGD - Order: Dialog Table for Table AFVG (Order Operation)

Data type: AFVGD
Optional: No
Call by Reference: Yes

I_RESBD - Reservation/Dependent Requirements

Data type: RESBD
Optional: No
Call by Reference: Yes

I_RESBD_SAV - Reservation/Dependent Requirements

Data type: RESBD
Optional: No
Call by Reference: Yes

I_NO_DIALOGUE - Single-Character Indicator

Data type: CHAR1
Default: YX
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CO_MK_IBAPI_BDTER_CHECK

E_RESBD - Reservation/Dependent Requirements

Data type: RESBD
Optional: No
Call by Reference: Yes

EXCEPTIONS details

UNSPECIFIED_ERROR - Unspecified error

Data type:
Optional: No
Call by Reference: Yes

SPECIFIED_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CO_MK_IBAPI_BDTER_CHECK 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_e_resbd  TYPE RESBD, "   
lv_i_caufvd  TYPE CAUFVD, "   
lv_unspecified_error  TYPE CAUFVD, "   
lv_i_afvgd  TYPE AFVGD, "   
lv_specified_error  TYPE AFVGD, "   
lv_i_resbd  TYPE RESBD, "   
lv_i_resbd_sav  TYPE RESBD, "   
lv_i_no_dialogue  TYPE CHAR1. "   YX

  CALL FUNCTION 'CO_MK_IBAPI_BDTER_CHECK'  "NOTRANSL: Bedarfstermin setzen und prüfen
    EXPORTING
         I_CAUFVD = lv_i_caufvd
         I_AFVGD = lv_i_afvgd
         I_RESBD = lv_i_resbd
         I_RESBD_SAV = lv_i_resbd_sav
         I_NO_DIALOGUE = lv_i_no_dialogue
    IMPORTING
         E_RESBD = lv_e_resbd
    EXCEPTIONS
        UNSPECIFIED_ERROR = 1
        SPECIFIED_ERROR = 2
. " CO_MK_IBAPI_BDTER_CHECK




ABAP code using 7.40 inline data declarations to call FM CO_MK_IBAPI_BDTER_CHECK

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.

 
 
 
 
 
 
 
DATA(ld_i_no_dialogue) = YX.
 


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!