SAP BBP_CTR_UI_DETAILS_GET Function Module for Lesen der Objekttabellen und Konvertierung in UI Format









BBP_CTR_UI_DETAILS_GET is a standard bbp ctr ui details get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lesen der Objekttabellen und Konvertierung in UI Format 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 details get FM, simply by entering the name BBP_CTR_UI_DETAILS_GET 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_UI_DETAILS_GET 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_DETAILS_GET'"Lesen der Objekttabellen und Konvertierung in UI Format
  EXPORTING
   IV_GUID =  "Globally Unique Identifier
*  IV_READ_ALL = 'X' "Feld zum Ankreuzen
*  IV_READ_HEADER = 'X' "Feld zum Ankreuzen
*  IV_READ_ITEM = 'X' "Feld zum Ankreuzen
*  IV_READ_TEXT = 'X' "Feld zum Ankreuzen

 IMPORTING
   ES_HEADER =  "Kopfstruktur Einkaufskontrakt
   ET_ITEMS =  "Tabellentyp Position Einkaufskontrakt
   ET_PARTNERS =  "Tabellentyp Partner Einkaufskontrakt
   ET_STATUS =  "Tabellentyp Status Einkaufskontrakt

EXCEPTIONS
   READ_PARAMETER_NOT_SELECTED = 1
.



IMPORTING Parameters details for BBP_CTR_UI_DETAILS_GET

IV_GUID - Globally Unique Identifier

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

IV_READ_ALL - Feld zum Ankreuzen

Data type: XFELD
Default: 'X'
Optional: No
Call by Reference: Yes

IV_READ_HEADER - Feld zum Ankreuzen

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_READ_ITEM - Feld zum Ankreuzen

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_READ_TEXT - Feld zum Ankreuzen

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BBP_CTR_UI_DETAILS_GET

ES_HEADER - Kopfstruktur Einkaufskontrakt

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

ET_ITEMS - Tabellentyp Position Einkaufskontrakt

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

ET_PARTNERS - Tabellentyp Partner Einkaufskontrakt

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

ET_STATUS - Tabellentyp Status Einkaufskontrakt

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

EXCEPTIONS details

READ_PARAMETER_NOT_SELECTED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_CTR_UI_DETAILS_GET 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_iv_guid  TYPE BBP_GUID, "   
lv_es_header  TYPE BBPS_CTR_UI_HEADER, "   
lv_read_parameter_not_selected  TYPE BBPS_CTR_UI_HEADER, "   
lv_et_items  TYPE BBPT_CTR_UI_ITEM, "   
lv_iv_read_all  TYPE XFELD, "   'X'
lv_et_partners  TYPE BBPT_CTR_UI_PARTNER, "   
lv_iv_read_header  TYPE XFELD, "   'X'
lv_et_status  TYPE BBPT_CTR_UI_STATUS, "   
lv_iv_read_item  TYPE XFELD, "   'X'
lv_iv_read_text  TYPE XFELD. "   'X'

  CALL FUNCTION 'BBP_CTR_UI_DETAILS_GET'  "Lesen der Objekttabellen und Konvertierung in UI Format
    EXPORTING
         IV_GUID = lv_iv_guid
         IV_READ_ALL = lv_iv_read_all
         IV_READ_HEADER = lv_iv_read_header
         IV_READ_ITEM = lv_iv_read_item
         IV_READ_TEXT = lv_iv_read_text
    IMPORTING
         ES_HEADER = lv_es_header
         ET_ITEMS = lv_et_items
         ET_PARTNERS = lv_et_partners
         ET_STATUS = lv_et_status
    EXCEPTIONS
        READ_PARAMETER_NOT_SELECTED = 1
. " BBP_CTR_UI_DETAILS_GET




ABAP code using 7.40 inline data declarations to call FM BBP_CTR_UI_DETAILS_GET

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_iv_read_all) = 'X'.
 
 
DATA(ld_iv_read_header) = 'X'.
 
 
DATA(ld_iv_read_item) = 'X'.
 
DATA(ld_iv_read_text) = 'X'.
 


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!