SAP VBXD_GET_CUOBJ_CH_BY_CONDITION Function Module for NOTRANSL: Ermitteln der CUOBJ_CH für Chargenselektion aus dem Konditionssa









VBXD_GET_CUOBJ_CH_BY_CONDITION is a standard vbxd get cuobj ch by condition 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: Ermitteln der CUOBJ_CH für Chargenselektion aus dem Konditionssa 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 vbxd get cuobj ch by condition FM, simply by entering the name VBXD_GET_CUOBJ_CH_BY_CONDITION into the relevant SAP transaction such as SE37 or SE38.

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



Function VBXD_GET_CUOBJ_CH_BY_CONDITION 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 'VBXD_GET_CUOBJ_CH_BY_CONDITION'"NOTRANSL: Ermitteln der CUOBJ_CH für Chargenselektion aus dem Konditionssa
  EXPORTING
*  I_KOMKH =  "Batch Determination Communication Block Header
*  I_KOMPH =  "Batch Determination: Communication Record for Item

CHANGING
   C_BXCOM =  "Communication Structure ATP Check by Characters

EXCEPTIONS
   NO_APPLICATION = 1    NO_SEARCH_PROCEDURE = 2    NO_RECORD_FOUND = 3    CONDITION_NOT_FOUND = 4
.




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_SAPLVBXD_001 Control for Communication
EXIT_SAPLVBXD_002 Control for Selection Criteria
EXIT_SAPLVBXD_003 Control for the APO Call
EXIT_SAPLVBXD_004 Control for the Results

IMPORTING Parameters details for VBXD_GET_CUOBJ_CH_BY_CONDITION

I_KOMKH - Batch Determination Communication Block Header

Data type: KOMKH
Optional: Yes
Call by Reference: Yes

I_KOMPH - Batch Determination: Communication Record for Item

Data type: KOMPH
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for VBXD_GET_CUOBJ_CH_BY_CONDITION

C_BXCOM - Communication Structure ATP Check by Characters

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

EXCEPTIONS details

NO_APPLICATION -

Data type:
Optional: No
Call by Reference: Yes

NO_SEARCH_PROCEDURE -

Data type:
Optional: No
Call by Reference: Yes

NO_RECORD_FOUND -

Data type:
Optional: No
Call by Reference: Yes

CONDITION_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VBXD_GET_CUOBJ_CH_BY_CONDITION 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_c_bxcom  TYPE BXCOM, "   
lv_i_komkh  TYPE KOMKH, "   
lv_no_application  TYPE KOMKH, "   
lv_i_komph  TYPE KOMPH, "   
lv_no_search_procedure  TYPE KOMPH, "   
lv_no_record_found  TYPE KOMPH, "   
lv_condition_not_found  TYPE KOMPH. "   

  CALL FUNCTION 'VBXD_GET_CUOBJ_CH_BY_CONDITION'  "NOTRANSL: Ermitteln der CUOBJ_CH für Chargenselektion aus dem Konditionssa
    EXPORTING
         I_KOMKH = lv_i_komkh
         I_KOMPH = lv_i_komph
    CHANGING
         C_BXCOM = lv_c_bxcom
    EXCEPTIONS
        NO_APPLICATION = 1
        NO_SEARCH_PROCEDURE = 2
        NO_RECORD_FOUND = 3
        CONDITION_NOT_FOUND = 4
. " VBXD_GET_CUOBJ_CH_BY_CONDITION




ABAP code using 7.40 inline data declarations to call FM VBXD_GET_CUOBJ_CH_BY_CONDITION

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.

 
 
 
 
 
 
 


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!