SAP Function Modules

BBP_PD_SC_UPDATE SAP Function module







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

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


Pattern for FM BBP_PD_SC_UPDATE - BBP PD SC UPDATE





CALL FUNCTION 'BBP_PD_SC_UPDATE' "
  EXPORTING
*   iv_bapimode =               " xfeld
*   i_park =                    " xfeld
    i_header =                  " bbp_pds_sc_header_u
*   i_save =                    " xfeld
*   iv_reject =                 " xfeld
*   iv_testrun =                " xfeld
*   iv_msg_scenario =           " bbp_msg_scenario
*   it_attach =                 " bbpt_pds_att_t
*   iv_with_change_approval = 'X'  " xfeld
  IMPORTING
    e_changed =                 " xfeld
* TABLES
*   i_item =                    " bbp_pds_sc_item_icu
*   i_account =                 " bbp_pds_acc
*   i_partner =                 " bbp_pds_partner
*   i_confirm =                 " bbp_pds_con
*   i_longtext =                " bbp_pds_longtext
*   i_limit =                   " bbp_pds_limit
*   i_orgdata =                 " bbp_pds_org
*   i_tax =                     " bbp_pds_tax
*   i_pridoc =                  " bbp_pds_prc
*   i_hcf =                     " bbp_pds_hcf_sc
*   i_icf =                     " bbp_pds_icf_sc
*   e_messages =                " bbp_pds_messages
    .  "  BBP_PD_SC_UPDATE

ABAP code example for Function Module BBP_PD_SC_UPDATE





The ABAP code below is a full code listing to execute function module BBP_PD_SC_UPDATE 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_changed  TYPE XFELD ,
it_i_item  TYPE STANDARD TABLE OF BBP_PDS_SC_ITEM_ICU,"TABLES PARAM
wa_i_item  LIKE LINE OF it_i_item ,
it_i_account  TYPE STANDARD TABLE OF BBP_PDS_ACC,"TABLES PARAM
wa_i_account  LIKE LINE OF it_i_account ,
it_i_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER,"TABLES PARAM
wa_i_partner  LIKE LINE OF it_i_partner ,
it_i_confirm  TYPE STANDARD TABLE OF BBP_PDS_CON,"TABLES PARAM
wa_i_confirm  LIKE LINE OF it_i_confirm ,
it_i_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT,"TABLES PARAM
wa_i_longtext  LIKE LINE OF it_i_longtext ,
it_i_limit  TYPE STANDARD TABLE OF BBP_PDS_LIMIT,"TABLES PARAM
wa_i_limit  LIKE LINE OF it_i_limit ,
it_i_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG,"TABLES PARAM
wa_i_orgdata  LIKE LINE OF it_i_orgdata ,
it_i_tax  TYPE STANDARD TABLE OF BBP_PDS_TAX,"TABLES PARAM
wa_i_tax  LIKE LINE OF it_i_tax ,
it_i_pridoc  TYPE STANDARD TABLE OF BBP_PDS_PRC,"TABLES PARAM
wa_i_pridoc  LIKE LINE OF it_i_pridoc ,
it_i_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_SC,"TABLES PARAM
wa_i_hcf  LIKE LINE OF it_i_hcf ,
it_i_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_SC,"TABLES PARAM
wa_i_icf  LIKE LINE OF it_i_icf ,
it_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES,"TABLES PARAM
wa_e_messages  LIKE LINE OF it_e_messages .

DATA(ld_iv_bapimode) = 'Check type of data required'.
DATA(ld_i_park) = 'Check type of data required'.
DATA(ld_i_header) = 'Check type of data required'.
DATA(ld_i_save) = 'Check type of data required'.
DATA(ld_iv_reject) = 'Check type of data required'.
DATA(ld_iv_testrun) = 'Check type of data required'.
DATA(ld_iv_msg_scenario) = 'Check type of data required'.
DATA(ld_it_attach) = 'Check type of data required'.
DATA(ld_iv_with_change_approval) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_item to it_i_item.

"populate fields of struture and append to itab
append wa_i_account to it_i_account.

"populate fields of struture and append to itab
append wa_i_partner to it_i_partner.

"populate fields of struture and append to itab
append wa_i_confirm to it_i_confirm.

"populate fields of struture and append to itab
append wa_i_longtext to it_i_longtext.

"populate fields of struture and append to itab
append wa_i_limit to it_i_limit.

"populate fields of struture and append to itab
append wa_i_orgdata to it_i_orgdata.

"populate fields of struture and append to itab
append wa_i_tax to it_i_tax.

"populate fields of struture and append to itab
append wa_i_pridoc to it_i_pridoc.

"populate fields of struture and append to itab
append wa_i_hcf to it_i_hcf.

"populate fields of struture and append to itab
append wa_i_icf to it_i_icf.

"populate fields of struture and append to itab
append wa_e_messages to it_e_messages. . CALL FUNCTION 'BBP_PD_SC_UPDATE' EXPORTING * iv_bapimode = ld_iv_bapimode * i_park = ld_i_park i_header = ld_i_header * i_save = ld_i_save * iv_reject = ld_iv_reject * iv_testrun = ld_iv_testrun * iv_msg_scenario = ld_iv_msg_scenario * it_attach = ld_it_attach * iv_with_change_approval = ld_iv_with_change_approval IMPORTING e_changed = ld_e_changed * TABLES * i_item = it_i_item * i_account = it_i_account * i_partner = it_i_partner * i_confirm = it_i_confirm * i_longtext = it_i_longtext * i_limit = it_i_limit * i_orgdata = it_i_orgdata * i_tax = it_i_tax * i_pridoc = it_i_pridoc * i_hcf = it_i_hcf * i_icf = it_i_icf * e_messages = it_e_messages . " BBP_PD_SC_UPDATE
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:
it_i_item  TYPE STANDARD TABLE OF BBP_PDS_SC_ITEM_ICU ,
wa_i_item  LIKE LINE OF it_i_item,
ld_iv_bapimode  TYPE XFELD ,
ld_e_changed  TYPE XFELD ,
ld_i_park  TYPE XFELD ,
it_i_account  TYPE STANDARD TABLE OF BBP_PDS_ACC ,
wa_i_account  LIKE LINE OF it_i_account,
ld_i_header  TYPE BBP_PDS_SC_HEADER_U ,
it_i_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER ,
wa_i_partner  LIKE LINE OF it_i_partner,
ld_i_save  TYPE XFELD ,
it_i_confirm  TYPE STANDARD TABLE OF BBP_PDS_CON ,
wa_i_confirm  LIKE LINE OF it_i_confirm,
ld_iv_reject  TYPE XFELD ,
it_i_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT ,
wa_i_longtext  LIKE LINE OF it_i_longtext,
ld_iv_testrun  TYPE XFELD ,
it_i_limit  TYPE STANDARD TABLE OF BBP_PDS_LIMIT ,
wa_i_limit  LIKE LINE OF it_i_limit,
ld_iv_msg_scenario  TYPE BBP_MSG_SCENARIO ,
it_i_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG ,
wa_i_orgdata  LIKE LINE OF it_i_orgdata,
ld_it_attach  TYPE BBPT_PDS_ATT_T ,
it_i_tax  TYPE STANDARD TABLE OF BBP_PDS_TAX ,
wa_i_tax  LIKE LINE OF it_i_tax,
ld_iv_with_change_approval  TYPE XFELD ,
it_i_pridoc  TYPE STANDARD TABLE OF BBP_PDS_PRC ,
wa_i_pridoc  LIKE LINE OF it_i_pridoc,
it_i_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_SC ,
wa_i_hcf  LIKE LINE OF it_i_hcf,
it_i_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_SC ,
wa_i_icf  LIKE LINE OF it_i_icf,
it_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES ,
wa_e_messages  LIKE LINE OF it_e_messages.


"populate fields of struture and append to itab
append wa_i_item to it_i_item.
ld_iv_bapimode = 'Check type of data required'.
ld_i_park = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_account to it_i_account.
ld_i_header = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_partner to it_i_partner.
ld_i_save = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_confirm to it_i_confirm.
ld_iv_reject = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_longtext to it_i_longtext.
ld_iv_testrun = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_limit to it_i_limit.
ld_iv_msg_scenario = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_orgdata to it_i_orgdata.
ld_it_attach = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_tax to it_i_tax.
ld_iv_with_change_approval = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_pridoc to it_i_pridoc.

"populate fields of struture and append to itab
append wa_i_hcf to it_i_hcf.

"populate fields of struture and append to itab
append wa_i_icf to it_i_icf.

"populate fields of struture and append to itab
append wa_e_messages to it_e_messages.

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_SC_UPDATE or its description.