BBP_CF_LINK_UPDATE SAP Function module

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

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

Pattern for FM BBP_CF_LINK_UPDATE - BBP CF LINK UPDATE

CALL FUNCTION 'BBP_CF_LINK_UPDATE' "
  EXPORTING
    po_number =                 " bbps_bapiekkoc-po_number
    po_item =                   " bbps_bapiekpo-po_item
*   logsys =                    " bbp_backend_dest-log_sys  Logical system
    is_document_tab =           " bbp_document_tab
  IMPORTING
    o_in_process =              " char1         document is in process of being posted
* TABLES
*   related_objects =           " bbp_polinks
  EXCEPTIONS
    INTERNAL_ERROR = 1          "
    NO_OBJECT_FOUND = 2         "
    .  "  BBP_CF_LINK_UPDATE

ABAP code example for Function Module BBP_CF_LINK_UPDATE

The ABAP code below is a full code listing to execute function module BBP_CF_LINK_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_o_in_process  
 
 TYPE CHAR1
,
it_related_objects  
 
 TYPE STANDARD TABLE OF BBP_POLINKS,"TABLES PARAM
wa_related_objects
 
 LIKE LINE OF it_related_objects
.



DATA(ld_po_number) = some text here


DATA(ld_po_item) = Check type of data required
 

SELECT single LOG_SYS 
  FROM BBP_BACKEND_DEST 
  INTO @DATA(ld_logsys).


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

"populate fields of struture and append to itab
append wa_related_objects to it_related_objects.
.

CALL FUNCTION 'BBP_CF_LINK_UPDATE'
  EXPORTING
    po_number =                  ld_po_number
    po_item =                    ld_po_item
*   logsys =                     ld_logsys
    is_document_tab =            ld_is_document_tab
  IMPORTING
    o_in_process =               ld_o_in_process
* TABLES
*   related_objects =            it_related_objects
  EXCEPTIONS
    INTERNAL_ERROR =             1
    NO_OBJECT_FOUND =            2
    .  "  BBP_CF_LINK_UPDATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_o_in_process
 
 TYPE CHAR1 ,
ld_po_number
 
 TYPE BBPS_BAPIEKKOC-PO_NUMBER ,
it_related_objects
 
 TYPE STANDARD TABLE OF BBP_POLINKS ,
wa_related_objects
 
 LIKE LINE OF it_related_objects,
ld_po_item
 
 TYPE BBPS_BAPIEKPO-PO_ITEM ,
ld_logsys
 
 TYPE BBP_BACKEND_DEST-LOG_SYS ,
ld_is_document_tab
 
 TYPE BBP_DOCUMENT_TAB .



ld_po_number = some text here 

"populate fields of struture and append to itab
append wa_related_objects to it_related_objects.

ld_po_item = Check type of data required

SELECT single LOG_SYS 
  FROM BBP_BACKEND_DEST 
  INTO ld_logsys.

ld_is_document_tab = 'Check type of data required'.