BBP_PCO_UI_ITS_PUT_PBO SAP Function module - Display Data from Purchase Order Response for Order Item

BBP_PCO_UI_ITS_PUT_PBO is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BBP_PCO_UI_ITS_PUT_PBO into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BBP_PCO_UI_ITS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BBP_PCO_UI_ITS_PUT_PBO - BBP PCO UI ITS PUT PBO

CALL FUNCTION 'BBP_PCO_UI_ITS_PUT_PBO' "Display Data from Purchase Order Response for Order Item
  EXPORTING
*   iv_header_guid =            " bbp_guid      Globally Unique Identifier
    iv_item_guid =              " bbp_guid      Globally Unique Identifier
    iv_object_type =            " crmt_subobject_category_db  Business Transaction Category
*   is_po_item =                " bbp_pds_po_item_d  Item Data Purchase Order GetDetail-Case Interface
*   is_po_header =              " bbp_pds_po_header_d  Header Data Purchase Order GetDetail-Case Interface
  IMPORTING
    ev_progname =               " sy-repid
    ev_screen =                 " sy-dynnr      ABAP Program: Number of Current Screen
    .  "  BBP_PCO_UI_ITS_PUT_PBO

ABAP code example for Function Module BBP_PCO_UI_ITS_PUT_PBO

The ABAP code below is a full code listing to execute function module BBP_PCO_UI_ITS_PUT_PBO including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_progname  
 
 TYPE SY-REPID
,
ld_ev_screen  
 
 TYPE SY-DYNNR
.


DATA(ld_iv_header_guid) = 'Check type of data required'.

DATA(ld_iv_item_guid) = 'Check type of data required'.

DATA(ld_iv_object_type) = 'Check type of data required'.

DATA(ld_is_po_item) = 'Check type of data required'.

DATA(ld_is_po_header) = 'Check type of data required'.
.

CALL FUNCTION 'BBP_PCO_UI_ITS_PUT_PBO'
  EXPORTING
*   iv_header_guid =             ld_iv_header_guid
    iv_item_guid =               ld_iv_item_guid
    iv_object_type =             ld_iv_object_type
*   is_po_item =                 ld_is_po_item
*   is_po_header =               ld_is_po_header
  IMPORTING
    ev_progname =                ld_ev_progname
    ev_screen =                  ld_ev_screen
    .  "  BBP_PCO_UI_ITS_PUT_PBO

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ev_progname
 
 TYPE SY-REPID ,
ld_iv_header_guid
 
 TYPE BBP_GUID ,
ld_ev_screen
 
 TYPE SY-DYNNR ,
ld_iv_item_guid
 
 TYPE BBP_GUID ,
ld_iv_object_type
 
 TYPE CRMT_SUBOBJECT_CATEGORY_DB ,
ld_is_po_item
 
 TYPE BBP_PDS_PO_ITEM_D ,
ld_is_po_header
 
 TYPE BBP_PDS_PO_HEADER_D .


ld_iv_header_guid = 'Check type of data required'.
ld_iv_item_guid = 'Check type of data required'.
ld_iv_object_type = 'Check type of data required'.
ld_is_po_item = 'Check type of data required'.
ld_is_po_header = 'Check type of data required'.