BBP_CHANGE_DOC_GET_NEW SAP Function module

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

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

Pattern for FM BBP_CHANGE_DOC_GET_NEW - BBP CHANGE DOC GET NEW

CALL FUNCTION 'BBP_CHANGE_DOC_GET_NEW' "
* EXPORTING
*   iv_header_guid =            " crmt_object_guid
*   it_item =                   " bbpt_changedoc_object_id
*   iv_with_versions =          " char1
*   iv_objecttype =             " crmt_subobject_category_db
  IMPORTING
    et_change_documents =       " bbpt_changedoc_cdred
    et_count =                  " bbpt_changedoc_count
    ev_header_descript =        " crmt_process_description
    ev_versions_exist =         " char1
  EXCEPTIONS
    ERROR_1 = 1                 "
    .  "  BBP_CHANGE_DOC_GET_NEW

ABAP code example for Function Module BBP_CHANGE_DOC_GET_NEW

The ABAP code below is a full code listing to execute function module BBP_CHANGE_DOC_GET_NEW 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_et_change_documents  
 
 TYPE BBPT_CHANGEDOC_CDRED
,
ld_et_count  
 
 TYPE BBPT_CHANGEDOC_COUNT
,
ld_ev_header_descript  
 
 TYPE CRMT_PROCESS_DESCRIPTION
,
ld_ev_versions_exist  
 
 TYPE CHAR1
.


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

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

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

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

CALL FUNCTION 'BBP_CHANGE_DOC_GET_NEW'
* EXPORTING
*   iv_header_guid =             ld_iv_header_guid
*   it_item =                    ld_it_item
*   iv_with_versions =           ld_iv_with_versions
*   iv_objecttype =              ld_iv_objecttype
  IMPORTING
    et_change_documents =        ld_et_change_documents
    et_count =                   ld_et_count
    ev_header_descript =         ld_ev_header_descript
    ev_versions_exist =          ld_ev_versions_exist
  EXCEPTIONS
    ERROR_1 =                    1
    .  "  BBP_CHANGE_DOC_GET_NEW

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_et_change_documents
 
 TYPE BBPT_CHANGEDOC_CDRED ,
ld_iv_header_guid
 
 TYPE CRMT_OBJECT_GUID ,
ld_et_count
 
 TYPE BBPT_CHANGEDOC_COUNT ,
ld_it_item
 
 TYPE BBPT_CHANGEDOC_OBJECT_ID ,
ld_ev_header_descript
 
 TYPE CRMT_PROCESS_DESCRIPTION ,
ld_iv_with_versions
 
 TYPE CHAR1 ,
ld_ev_versions_exist
 
 TYPE CHAR1 ,
ld_iv_objecttype
 
 TYPE CRMT_SUBOBJECT_CATEGORY_DB .


ld_iv_header_guid = 'Check type of data required'.
ld_it_item = 'Check type of data required'.
ld_iv_with_versions = 'Check type of data required'.
ld_iv_objecttype = 'Check type of data required'.