BBP_BP_GROUPING_DETERMINE SAP Function module

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

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

Pattern for FM BBP_BP_GROUPING_DETERMINE - BBP BP GROUPING DETERMINE

CALL FUNCTION 'BBP_BP_GROUPING_DETERMINE' "
  EXPORTING
    iv_partner =                " bu_partner
*   iv_standard_only =          " xfeld
  IMPORTING
    ev_group =                  " bu_group
    ev_is_standard =            " xfeld
  EXCEPTIONS
    GROUPING_NOT_CUSTOMIZED = 1  "
    PARTNER_OUT_OF_RANGE = 2    "
    MISSING_INPUT = 3           "
    MISSING_NUMBER_RANGE_OBJECT = 4  "
    PARTNER_OUT_OF_STANDARD = 5  "
    .  "  BBP_BP_GROUPING_DETERMINE

ABAP code example for Function Module BBP_BP_GROUPING_DETERMINE

The ABAP code below is a full code listing to execute function module BBP_BP_GROUPING_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_ev_group  
 
 TYPE BU_GROUP
,
ld_ev_is_standard  
 
 TYPE XFELD
.


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

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

CALL FUNCTION 'BBP_BP_GROUPING_DETERMINE'
  EXPORTING
    iv_partner =                 ld_iv_partner
*   iv_standard_only =           ld_iv_standard_only
  IMPORTING
    ev_group =                   ld_ev_group
    ev_is_standard =             ld_ev_is_standard
  EXCEPTIONS
    GROUPING_NOT_CUSTOMIZED =    1
    PARTNER_OUT_OF_RANGE =       2
    MISSING_INPUT =              3
    MISSING_NUMBER_RANGE_OBJECT =    4
    PARTNER_OUT_OF_STANDARD =    5
    .  "  BBP_BP_GROUPING_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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "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_ev_group
 
 TYPE BU_GROUP ,
ld_iv_partner
 
 TYPE BU_PARTNER ,
ld_ev_is_standard
 
 TYPE XFELD ,
ld_iv_standard_only
 
 TYPE XFELD .


ld_iv_partner = 'Check type of data required'.
ld_iv_standard_only = 'Check type of data required'.