SAP BBP_CTR_UI_ITS_SCREEN_FLOW Function Module for Screen flow









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

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



Function BBP_CTR_UI_ITS_SCREEN_FLOW 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_UI_ITS_SCREEN_FLOW'"Screen flow
EXPORTING
* IV_SIMULATION = "Bildschirmbilder, Funktionscode, der PAI ausgelöst hat
IS_EXTERNAL_CALL = "Externer Aufruf des Kontraktes aus PO, WF, etc.
* IS_HEADER = "Kopfstruktur Einkaufskontrakt
* IS_ITEM = "Position Einkaufskontrakt

CHANGING
CV_FCODE = "Bildschirmbilder, Funktionscode, der PAI ausgelöst hat
CS_GLOBAL = "Globaldaten Einkaufskontrakt
CS_SUBSCREEN = "Subscreendaten Einkaufskontrakt
.



IMPORTING Parameters details for BBP_CTR_UI_ITS_SCREEN_FLOW

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

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

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

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

IS_HEADER - Kopfstruktur Einkaufskontrakt

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

IS_ITEM - Position Einkaufskontrakt

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

CHANGING Parameters details for BBP_CTR_UI_ITS_SCREEN_FLOW

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

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

CS_GLOBAL - Globaldaten Einkaufskontrakt

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

CS_SUBSCREEN - Subscreendaten Einkaufskontrakt

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

Copy and paste ABAP code example for BBP_CTR_UI_ITS_SCREEN_FLOW 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_cv_fcode  TYPE SYUCOMM, "   
lv_iv_simulation  TYPE XFELD, "   
lv_cs_global  TYPE BBPS_CTR_UI_GLOBAL, "   
lv_is_external_call  TYPE BBPS_CTR_EXTERNAL_CALL, "   
lv_is_header  TYPE BBPS_CTR_UI_HEADER, "   
lv_cs_subscreen  TYPE BBPS_CTR_UI_SUBSCREEN, "   
lv_is_item  TYPE BBPS_CTR_UI_ITEM. "   

  CALL FUNCTION 'BBP_CTR_UI_ITS_SCREEN_FLOW'  "Screen flow
    EXPORTING
         IV_SIMULATION = lv_iv_simulation
         IS_EXTERNAL_CALL = lv_is_external_call
         IS_HEADER = lv_is_header
         IS_ITEM = lv_is_item
    CHANGING
         CV_FCODE = lv_cv_fcode
         CS_GLOBAL = lv_cs_global
         CS_SUBSCREEN = lv_cs_subscreen
. " BBP_CTR_UI_ITS_SCREEN_FLOW




ABAP code using 7.40 inline data declarations to call FM BBP_CTR_UI_ITS_SCREEN_FLOW

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!