BBP_TOLERANCE_GROUP_DETERMINE SAP Function module - Toleranzgruppe aus Eingangsweg und Transaktion bestimmen

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

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

Pattern for FM BBP_TOLERANCE_GROUP_DETERMINE - BBP TOLERANCE GROUP DETERMINE

CALL FUNCTION 'BBP_TOLERANCE_GROUP_DETERMINE' "Toleranzgruppe aus Eingangsweg und Transaktion bestimmen
* EXPORTING
*   i_user_name =               " sy-uname      R/3-System, Anmeldename des Benutzers
*   i_vendor_guid =             " crmt_partner_no  Partnernummer
*   i_use_message_log =         " xfeld         Feld zum Ankreuzen
  IMPORTING
    e_tol_group =               " bbp_tol_group  Toleranz Gruppe
* TABLES
*   e_messages =                " bbp_pds_messages  Fehlermeldungen zu einer PD-Methode
  EXCEPTIONS
    ERROR_IN_ATTRIBUTE = 1      "
    VENDOR_NOT_FOUND = 2        "
    .  "  BBP_TOLERANCE_GROUP_DETERMINE

ABAP code example for Function Module BBP_TOLERANCE_GROUP_DETERMINE

The ABAP code below is a full code listing to execute function module BBP_TOLERANCE_GROUP_DETERMINE 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_e_tol_group  
 
 TYPE BBP_TOL_GROUP
,
it_e_messages  
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES,"TABLES PARAM
wa_e_messages
 
 LIKE LINE OF it_e_messages
.


DATA(ld_i_user_name) = 'some text here'.

DATA(ld_i_vendor_guid) = 'some text here'.

DATA(ld_i_use_message_log) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_e_messages to it_e_messages.
.

CALL FUNCTION 'BBP_TOLERANCE_GROUP_DETERMINE'
* EXPORTING
*   i_user_name =                ld_i_user_name
*   i_vendor_guid =              ld_i_vendor_guid
*   i_use_message_log =          ld_i_use_message_log
  IMPORTING
    e_tol_group =                ld_e_tol_group
* TABLES
*   e_messages =                 it_e_messages
  EXCEPTIONS
    ERROR_IN_ATTRIBUTE =         1
    VENDOR_NOT_FOUND =           2
    .  "  BBP_TOLERANCE_GROUP_DETERMINE

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_e_tol_group
 
 TYPE BBP_TOL_GROUP ,
ld_i_user_name
 
 TYPE SY-UNAME ,
it_e_messages
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES ,
wa_e_messages
 
 LIKE LINE OF it_e_messages,
ld_i_vendor_guid
 
 TYPE CRMT_PARTNER_NO ,
ld_i_use_message_log
 
 TYPE XFELD .


ld_i_user_name = 'some text here'. 

"populate fields of struture and append to itab
append wa_e_messages to it_e_messages.
ld_i_vendor_guid = 'some text here'.
ld_i_use_message_log = 'some text here'.