BBP_CTR_NOV_OBJECT_GET SAP Function module - Novation Protocol Old Supplier -> New Supplier

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

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

Pattern for FM BBP_CTR_NOV_OBJECT_GET - BBP CTR NOV OBJECT GET

CALL FUNCTION 'BBP_CTR_NOV_OBJECT_GET' "Novation Protocol Old Supplier -> New Supplier
  EXPORTING
    iv_object_id =              " crmt_object_id_db  Transaction Number
*   iv_object_type = 'BUS2000113'  " crmt_subobject_category_db  Business Transaction Category
*   iv_subtype = '  '           " bbp_h_subtype  Specification of a Purchasing Doc.(e.g. Credit Memo/Invoice)
    iv_vendor_id_old =          " but000-partner  Business partner no.
    iv_vendor_id_new =          " but000-partner  Business partner no.
    iv_time_nov_utc =           " timestamp     UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
  IMPORTING
    ev_ctr_nov_obj_found =      " xfeld         Checkbox
* TABLES
*   et_ctr_nov_log =            " bbpd_ctr_nov_log  Novation Protocol
    .  "  BBP_CTR_NOV_OBJECT_GET

ABAP code example for Function Module BBP_CTR_NOV_OBJECT_GET

The ABAP code below is a full code listing to execute function module BBP_CTR_NOV_OBJECT_GET 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_ev_ctr_nov_obj_found  
 
 TYPE XFELD
,
it_et_ctr_nov_log  
 
 TYPE STANDARD TABLE OF BBPD_CTR_NOV_LOG,"TABLES PARAM
wa_et_ctr_nov_log
 
 LIKE LINE OF it_et_ctr_nov_log
.


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

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

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

SELECT single PARTNER 
  FROM BUT000 
  INTO @DATA(ld_iv_vendor_id_old).

 

SELECT single PARTNER 
  FROM BUT000 
  INTO @DATA(ld_iv_vendor_id_new).


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

"populate fields of struture and append to itab
append wa_et_ctr_nov_log to it_et_ctr_nov_log.
.

CALL FUNCTION 'BBP_CTR_NOV_OBJECT_GET'
  EXPORTING
    iv_object_id =               ld_iv_object_id
*   iv_object_type =             ld_iv_object_type
*   iv_subtype =                 ld_iv_subtype
    iv_vendor_id_old =           ld_iv_vendor_id_old
    iv_vendor_id_new =           ld_iv_vendor_id_new
    iv_time_nov_utc =            ld_iv_time_nov_utc
  IMPORTING
    ev_ctr_nov_obj_found =       ld_ev_ctr_nov_obj_found
* TABLES
*   et_ctr_nov_log =             it_et_ctr_nov_log
    .  "  BBP_CTR_NOV_OBJECT_GET

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_ev_ctr_nov_obj_found
 
 TYPE XFELD ,
ld_iv_object_id
 
 TYPE CRMT_OBJECT_ID_DB ,
it_et_ctr_nov_log
 
 TYPE STANDARD TABLE OF BBPD_CTR_NOV_LOG ,
wa_et_ctr_nov_log
 
 LIKE LINE OF it_et_ctr_nov_log,
ld_iv_object_type
 
 TYPE CRMT_SUBOBJECT_CATEGORY_DB ,
ld_iv_subtype
 
 TYPE BBP_H_SUBTYPE ,
ld_iv_vendor_id_old
 
 TYPE BUT000-PARTNER ,
ld_iv_vendor_id_new
 
 TYPE BUT000-PARTNER ,
ld_iv_time_nov_utc
 
 TYPE TIMESTAMP .


ld_iv_object_id = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_ctr_nov_log to it_et_ctr_nov_log.
ld_iv_object_type = 'Check type of data required'.
ld_iv_subtype = 'Check type of data required'.

SELECT single PARTNER 
  FROM BUT000 
  INTO ld_iv_vendor_id_old.


SELECT single PARTNER 
  FROM BUT000 
  INTO ld_iv_vendor_id_new.

ld_iv_time_nov_utc = 'Check type of data required'.