SAP Function Modules

BBP_SUSIV_PARTNER_DEFAULT SAP Function module - Partner einer Rechnung ergaenzen







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

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


Pattern for FM BBP_SUSIV_PARTNER_DEFAULT - BBP SUSIV PARTNER DEFAULT





CALL FUNCTION 'BBP_SUSIV_PARTNER_DEFAULT' "Partner einer Rechnung ergaenzen
* EXPORTING
*   is_user_info =              " bbps_sel_user_info  Benutzerinformationen
*   iv_buyer_guid =             " crmt_partner_no  Partnernummer des Lieferanten
*   iv_requestor_guid =         " crmt_partner_no  Partnernummer des Anforders
*   iv_with_header_partners = SPACE  " xfeld    auch Kopfpartner defaulten
*   iv_header_guid =            " bbp_guid      Guid des Rechnungskopfes
*   iv_xml_inbound = SPACE      " xfeld         XML-Rechnung
  TABLES
    it_item =                   " bbp_pds_susinv_item_d  Positionen
    ct_partner =                " bbp_pds_partner  Geschäftspartner
    .  "  BBP_SUSIV_PARTNER_DEFAULT

ABAP code example for Function Module BBP_SUSIV_PARTNER_DEFAULT





The ABAP code below is a full code listing to execute function module BBP_SUSIV_PARTNER_DEFAULT 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:
it_it_item  TYPE STANDARD TABLE OF BBP_PDS_SUSINV_ITEM_D,"TABLES PARAM
wa_it_item  LIKE LINE OF it_it_item ,
it_ct_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER,"TABLES PARAM
wa_ct_partner  LIKE LINE OF it_ct_partner .

DATA(ld_is_user_info) = 'Check type of data required'.
DATA(ld_iv_buyer_guid) = 'Check type of data required'.
DATA(ld_iv_requestor_guid) = 'Check type of data required'.
DATA(ld_iv_with_header_partners) = 'Check type of data required'.
DATA(ld_iv_header_guid) = 'Check type of data required'.
DATA(ld_iv_xml_inbound) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_it_item to it_it_item.

"populate fields of struture and append to itab
append wa_ct_partner to it_ct_partner. . CALL FUNCTION 'BBP_SUSIV_PARTNER_DEFAULT' * EXPORTING * is_user_info = ld_is_user_info * iv_buyer_guid = ld_iv_buyer_guid * iv_requestor_guid = ld_iv_requestor_guid * iv_with_header_partners = ld_iv_with_header_partners * iv_header_guid = ld_iv_header_guid * iv_xml_inbound = ld_iv_xml_inbound TABLES it_item = it_it_item ct_partner = it_ct_partner . " BBP_SUSIV_PARTNER_DEFAULT
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_is_user_info  TYPE BBPS_SEL_USER_INFO ,
it_it_item  TYPE STANDARD TABLE OF BBP_PDS_SUSINV_ITEM_D ,
wa_it_item  LIKE LINE OF it_it_item,
ld_iv_buyer_guid  TYPE CRMT_PARTNER_NO ,
it_ct_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER ,
wa_ct_partner  LIKE LINE OF it_ct_partner,
ld_iv_requestor_guid  TYPE CRMT_PARTNER_NO ,
ld_iv_with_header_partners  TYPE XFELD ,
ld_iv_header_guid  TYPE BBP_GUID ,
ld_iv_xml_inbound  TYPE XFELD .

ld_is_user_info = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_it_item to it_it_item.
ld_iv_buyer_guid = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_ct_partner to it_ct_partner.
ld_iv_requestor_guid = 'Check type of data required'.
ld_iv_with_header_partners = 'Check type of data required'.
ld_iv_header_guid = 'Check type of data required'.
ld_iv_xml_inbound = 'Check type of data required'.

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