BAPI_SALESSUPDOCUMENT_ADD_ASGN SAP Function module - Abstract BAPI Sales Support Document Add to Assigned

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

Associated Function Group: VBKA
Released Date: . .
Processing type: Remote-Enabled

Pattern for FM BAPI_SALESSUPDOCUMENT_ADD_ASGN - BAPI SALESSUPDOCUMENT ADD ASGN

CALL FUNCTION 'BAPI_SALESSUPDOCUMENT_ADD_ASGN' "Abstract BAPI Sales Support Document Add to Assigned
  EXPORTING
    salesactivity =             " vbka-vbeln    SD Document No. of a Sales Activity in Sales Support
    sender =                    " bapi_sender   Logical System of Sender
    roletype_ab =               " bapi_vbka_objref_cr-roletype_ab  Semantics Role Type of Instantiated Object
  TABLES
    object_list =               " bapiobjid     Objects to be Linked
*   return =                    " bapiret2      Return Parameter
    .  "  BAPI_SALESSUPDOCUMENT_ADD_ASGN

ABAP code example for Function Module BAPI_SALESSUPDOCUMENT_ADD_ASGN

The ABAP code below is a full code listing to execute function module BAPI_SALESSUPDOCUMENT_ADD_ASGN 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_object_list  
 
 TYPE STANDARD TABLE OF BAPIOBJID,"TABLES PARAM
wa_object_list
 
 LIKE LINE OF it_object_list
,
it_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_return
 
 LIKE LINE OF it_return
.

 

SELECT single VBELN 
  FROM VBKA 
  INTO @DATA(ld_salesactivity).


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


DATA(ld_roletype_ab) = some text here
 

"populate fields of struture and append to itab
append wa_object_list to it_object_list.
 

"populate fields of struture and append to itab
append wa_return to it_return.
.

CALL FUNCTION 'BAPI_SALESSUPDOCUMENT_ADD_ASGN'
  EXPORTING
    salesactivity =              ld_salesactivity
    sender =                     ld_sender
    roletype_ab =                ld_roletype_ab
  TABLES
    object_list =                it_object_list
*   return =                     it_return
    .  "  BAPI_SALESSUPDOCUMENT_ADD_ASGN

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_salesactivity
 
 TYPE VBKA-VBELN ,
it_object_list
 
 TYPE STANDARD TABLE OF BAPIOBJID ,
wa_object_list
 
 LIKE LINE OF it_object_list,
ld_sender
 
 TYPE BAPI_SENDER ,
it_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_return
 
 LIKE LINE OF it_return,
ld_roletype_ab
 
 TYPE BAPI_VBKA_OBJREF_CR-ROLETYPE_AB .



SELECT single VBELN 
  FROM VBKA 
  INTO ld_salesactivity.
 

"populate fields of struture and append to itab
append wa_object_list to it_object_list.
ld_sender = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_return to it_return.

ld_roletype_ab = some text here