SAP B46B_CTR_CHECK Function Module for

Search SAP Function Modules

B46B_CTR_CHECK is a standard b46b ctr check 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 b46b ctr check FM, simply by entering the name B46B_CTR_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function B46B_CTR_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 'B46B_CTR_CHECK'"
  EXPORTING
   IV_BE_CONTRACT_NUMBER =  "Vorgangsnummer
*  IV_LANGUAGE =  "R/3-System, aktuelle Sprache
   IV_LOGICAL_SYSTEM =  "
*  IV_PORG_PARTNER_ID =  "Geschäftspartnernummer
*  IV_LOCATION_PARTNER_ID =  "Geschäftspartnernummer
*  IV_BE_LOGSYS =  "Logisches System
*  IV_BE_OBJTYPE =  "Objekttyp im Zielsystem

 IMPORTING
   EV_CTR_CREATION =  "Einstelliges Kennzeichen
   EV_CND_CREATION =  "Einstelliges Kennzeichen
   ET_CTR_DISTR_MESSAGES =  "Messages from the backend system

TABLES
   ET_CTR_MM_ITEM_MAP =  "Mapping Informationen Kontraktposition
*  ET_MESSAGES =  "Returnparameter
   ET_CONTROL_RECORD =  "

.

IMPORTING Parameters details for B46B_CTR_CHECK

IV_BE_CONTRACT_NUMBER - Vorgangsnummer

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

IV_LANGUAGE - R/3-System, aktuelle Sprache

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

IV_LOGICAL_SYSTEM -

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

IV_PORG_PARTNER_ID - Geschäftspartnernummer

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

IV_LOCATION_PARTNER_ID - Geschäftspartnernummer

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

IV_BE_LOGSYS - Logisches System

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

IV_BE_OBJTYPE - Objekttyp im Zielsystem

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

EXPORTING Parameters details for B46B_CTR_CHECK

EV_CTR_CREATION - Einstelliges Kennzeichen

Data type: BAPIFLAG-BAPIFLAG
Optional: No
Call by Reference: Yes

EV_CND_CREATION - Einstelliges Kennzeichen

Data type: BAPIFLAG-BAPIFLAG
Optional: No
Call by Reference: Yes

ET_CTR_DISTR_MESSAGES - Messages from the backend system

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

TABLES Parameters details for B46B_CTR_CHECK

ET_CTR_MM_ITEM_MAP - Mapping Informationen Kontraktposition

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

ET_MESSAGES - Returnparameter

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

ET_CONTROL_RECORD -

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

Copy and paste ABAP code example for B46B_CTR_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.

ABAP code using 7.40 inline data declarations to call FM B46B_CTR_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.

Search for further information about these or an SAP related objects