SAP BBP_CTR_APP_EVENT_HANDLER Function Module for FCODE Bearbeitung









BBP_CTR_APP_EVENT_HANDLER is a standard bbp ctr app event handler SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FCODE Bearbeitung 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 bbp ctr app event handler FM, simply by entering the name BBP_CTR_APP_EVENT_HANDLER into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_CTR_APP_EVENT_HANDLER 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 'BBP_CTR_APP_EVENT_HANDLER'"FCODE Bearbeitung
  EXPORTING
   IV_FCODE =  "Bildschirmbilder, Funktionscode, der PAI ausgelöst hat
*  IT_DIST_UPDATE =  "Kontrakt Verteilungsdaten
*  IS_DEFAULT =  "Vorschlagswerte für Einkaufskontrakt
*  IS_EXTERNAL_CALL =  "Externer Aufruf des Kontraktes aus PO, WF, etc.
   IS_HEADER =  "Kopfstruktur Einkaufskontrakt
*  IS_STATUS =  "Status Einkaufskontrakt
   IS_ITEM =  "Tabellentyp Position Einkaufskontrakt
   IT_ITEMS =  "Tabellentyp Position Einkaufskontrakt
   IT_ITEMS_UPDATE =  "Tabellentyp Position Einkaufskontrakt
*  IT_SEARCH_FIELD_LIST =  "Übergabe der Feldliste an den Search-Screen

 IMPORTING
   EV_FCODE =  "Bildschirmbilder, Funktionscode, der PAI ausgelöst hat
   ET_CALL_OFF_LIST =  "Liste von Abrufbestellungen
   ET_CUFTABLE_H =  "Tabellenartige Kunden- und Solutionfelder am Kontraktkopf
   ET_CUFTABLE_I =  "Tab. Kunden- und Solutionfelder an der Kontraktposition
   ET_DIST =  "Kontrakt Verteilungsdaten
   ES_HEADER =  "Kopfstruktur Einkaufskontrakt
   ES_ITEM =  "Tabellentyp Position Einkaufskontrakt
   ET_ITEMS =  "Tabellentyp Position Einkaufskontrakt
   ET_STATUS =  "Tabellentyp Status Einkaufskontrakt
   ET_PARTNERS =  "Tabellentyp Partner Einkaufskontrakt
   ET_SEARCH_FIELD_LIST =  "Übergabe der Feldliste an den Search-Screen
   ET_TEXT =  "Langtexte
   ET_ATTACH =  "KW-Anlagen inkl. Dokument

CHANGING
*  CS_GLOBAL =  "Globaldaten Einkaufskontrakt
*  CS_INFRAME_CATALOG =  "Struktur zur Anzeige von Inframe-Katalogen
*  CT_MESSAGES =  "Error Message for Procurement Document Methods

EXCEPTIONS
   ERROR_OCCURRED = 1    AUTHORIZATION_ERROR = 2
.



IMPORTING Parameters details for BBP_CTR_APP_EVENT_HANDLER

IV_FCODE - Bildschirmbilder, Funktionscode, der PAI ausgelöst hat

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

IT_DIST_UPDATE - Kontrakt Verteilungsdaten

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

IS_DEFAULT - Vorschlagswerte für Einkaufskontrakt

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

IS_EXTERNAL_CALL - Externer Aufruf des Kontraktes aus PO, WF, etc.

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

IS_HEADER - Kopfstruktur Einkaufskontrakt

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

IS_STATUS - Status Einkaufskontrakt

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

IS_ITEM - Tabellentyp Position Einkaufskontrakt

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

IT_ITEMS - Tabellentyp Position Einkaufskontrakt

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

IT_ITEMS_UPDATE - Tabellentyp Position Einkaufskontrakt

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

IT_SEARCH_FIELD_LIST - Übergabe der Feldliste an den Search-Screen

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

EXPORTING Parameters details for BBP_CTR_APP_EVENT_HANDLER

EV_FCODE - Bildschirmbilder, Funktionscode, der PAI ausgelöst hat

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

ET_CALL_OFF_LIST - Liste von Abrufbestellungen

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

ET_CUFTABLE_H - Tabellenartige Kunden- und Solutionfelder am Kontraktkopf

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

ET_CUFTABLE_I - Tab. Kunden- und Solutionfelder an der Kontraktposition

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

ET_DIST - Kontrakt Verteilungsdaten

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

ES_HEADER - Kopfstruktur Einkaufskontrakt

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

ES_ITEM - Tabellentyp Position Einkaufskontrakt

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

ET_ITEMS - Tabellentyp Position Einkaufskontrakt

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

ET_STATUS - Tabellentyp Status Einkaufskontrakt

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

ET_PARTNERS - Tabellentyp Partner Einkaufskontrakt

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

ET_SEARCH_FIELD_LIST - Übergabe der Feldliste an den Search-Screen

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

ET_TEXT - Langtexte

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

ET_ATTACH - KW-Anlagen inkl. Dokument

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

CHANGING Parameters details for BBP_CTR_APP_EVENT_HANDLER

CS_GLOBAL - Globaldaten Einkaufskontrakt

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

CS_INFRAME_CATALOG - Struktur zur Anzeige von Inframe-Katalogen

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

CT_MESSAGES - Error Message for Procurement Document Methods

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

EXCEPTIONS details

ERROR_OCCURRED - Fehler aufgetreten

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

AUTHORIZATION_ERROR - Fehler in der Berechtigungsprüfung aufgetaucht

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

Copy and paste ABAP code example for BBP_CTR_APP_EVENT_HANDLER 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_ev_fcode  TYPE SYUCOMM, "   
lv_iv_fcode  TYPE SYUCOMM, "   
lv_cs_global  TYPE BBPS_CTR_UI_GLOBAL, "   
lv_error_occurred  TYPE BBPS_CTR_UI_GLOBAL, "   
lv_it_dist_update  TYPE BBPT_PD_DIS, "   
lv_et_call_off_list  TYPE BBPT_CTR_UI_CALL_OFF, "   
lv_et_cuftable_h  TYPE BBPT_PDS_HCF_CTR, "   
lv_et_cuftable_i  TYPE BBPT_PDS_ICF_CTR, "   
lv_et_dist  TYPE BBPT_CTR_UI_DIS, "   
lv_es_header  TYPE BBPS_CTR_UI_HEADER, "   
lv_is_default  TYPE BBPS_CTR_UI_DEFAULT, "   
lv_cs_inframe_catalog  TYPE BBPS_INFRAME_CATALOG, "   
lv_authorization_error  TYPE BBPS_INFRAME_CATALOG, "   
lv_es_item  TYPE BBPS_CTR_UI_ITEM, "   
lv_ct_messages  TYPE BBPT_PDS_MESSAGES, "   
lv_is_external_call  TYPE BBPS_CTR_EXTERNAL_CALL, "   
lv_et_items  TYPE BBPT_CTR_UI_ITEM, "   
lv_is_header  TYPE BBPS_CTR_UI_HEADER, "   
lv_et_status  TYPE BBPT_CTR_UI_STATUS, "   
lv_is_status  TYPE BBPS_CTR_UI_STATUS, "   
lv_is_item  TYPE BBPS_CTR_UI_ITEM, "   
lv_et_partners  TYPE BBPT_PD_PARTNER, "   
lv_it_items  TYPE BBPT_CTR_UI_ITEM, "   
lv_et_search_field_list  TYPE BBPT_SEL_SEARCH_FIELD_CONTROL, "   
lv_et_text  TYPE BBPT_PD_LONGTEXT, "   
lv_it_items_update  TYPE BBPT_CTR_UI_ITEM, "   
lv_et_attach  TYPE BBPT_PDS_ATT_T, "   
lv_it_search_field_list  TYPE BBPT_SEL_SEARCH_FIELD_CONTROL. "   

  CALL FUNCTION 'BBP_CTR_APP_EVENT_HANDLER'  "FCODE Bearbeitung
    EXPORTING
         IV_FCODE = lv_iv_fcode
         IT_DIST_UPDATE = lv_it_dist_update
         IS_DEFAULT = lv_is_default
         IS_EXTERNAL_CALL = lv_is_external_call
         IS_HEADER = lv_is_header
         IS_STATUS = lv_is_status
         IS_ITEM = lv_is_item
         IT_ITEMS = lv_it_items
         IT_ITEMS_UPDATE = lv_it_items_update
         IT_SEARCH_FIELD_LIST = lv_it_search_field_list
    IMPORTING
         EV_FCODE = lv_ev_fcode
         ET_CALL_OFF_LIST = lv_et_call_off_list
         ET_CUFTABLE_H = lv_et_cuftable_h
         ET_CUFTABLE_I = lv_et_cuftable_i
         ET_DIST = lv_et_dist
         ES_HEADER = lv_es_header
         ES_ITEM = lv_es_item
         ET_ITEMS = lv_et_items
         ET_STATUS = lv_et_status
         ET_PARTNERS = lv_et_partners
         ET_SEARCH_FIELD_LIST = lv_et_search_field_list
         ET_TEXT = lv_et_text
         ET_ATTACH = lv_et_attach
    CHANGING
         CS_GLOBAL = lv_cs_global
         CS_INFRAME_CATALOG = lv_cs_inframe_catalog
         CT_MESSAGES = lv_ct_messages
    EXCEPTIONS
        ERROR_OCCURRED = 1
        AUTHORIZATION_ERROR = 2
. " BBP_CTR_APP_EVENT_HANDLER




ABAP code using 7.40 inline data declarations to call FM BBP_CTR_APP_EVENT_HANDLER

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!