SAP Function Modules

comments icon Comments

BBP_PD_BID_DOC_FLOW SAP Function module - Document Flow of RFx Document







BBP_PD_BID_DOC_FLOW 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_PD_BID_DOC_FLOW into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BBP_PDH_HISTORY
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM BBP_PD_BID_DOC_FLOW - BBP PD BID DOC FLOW 





CALL FUNCTION 'BBP_PD_BID_DOC_FLOW' "Document Flow of RFx Document
  EXPORTING
    is_object_key =             " bbps_object_key  Schlüsselfelder für Lean- oder Backend-Dokument
  IMPORTING
    e_be_log_system =           " bbp_logsys    Business Document Service: ID des logischen Systems
  TABLES
    et_bid_history =            " bbp_pds_history  Bestellentwicklung
  EXCEPTIONS
    BID_NOT_FOUND = 1           "               Ausschreibung nicht gefunden
    .  "  BBP_PD_BID_DOC_FLOW

ABAP code example for Function Module BBP_PD_BID_DOC_FLOW





The ABAP code below is a full code listing to execute function module BBP_PD_BID_DOC_FLOW 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_e_be_log_system    TYPE BBP_LOGSYS
,
it_et_bid_history    TYPE STANDARD TABLE OF BBP_PDS_HISTORY,"TABLES PARAM
wa_et_bid_history  LIKE LINE OF it_et_bid_history
.




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

"populate fields of struture and append to itab
append wa_et_bid_history to it_et_bid_history.
.

CALL FUNCTION 'BBP_PD_BID_DOC_FLOW'
  EXPORTING
    is_object_key =              ld_is_object_key
  IMPORTING
    e_be_log_system =            ld_e_be_log_system
  TABLES
    et_bid_history =             it_et_bid_history
  EXCEPTIONS
    BID_NOT_FOUND =              1
    .  "  BBP_PD_BID_DOC_FLOW

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_e_be_log_system  TYPE BBP_LOGSYS ,
ld_is_object_key  TYPE BBPS_OBJECT_KEY ,
it_et_bid_history  TYPE STANDARD TABLE OF BBP_PDS_HISTORY ,
wa_et_bid_history  LIKE LINE OF it_et_bid_history.




ld_is_object_key = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_bid_history to it_et_bid_history.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BBP_PD_BID_DOC_FLOW or its description.


   
 

BBP_PD_BID_DOC_FLOW - Document Flow of RFx Document
BBP_PD_BID_DB_DELETE_MULTI - 
BBP_PD_BID_DB_DELETE - 
BBP_PD_BID_CREATE - 
BBP_PD_BID_CHECK_SOCO - 
BBP_PD_BID_CHECK -