SAP BPAR_C_CENTRAL_GROUP_ID Function Module for NOTRANSL: Alle Prüfungen Partner-Gruppierung
BPAR_C_CENTRAL_GROUP_ID is a standard bpar c central group id SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Alle Prüfungen Partner-Gruppierung processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for bpar c central group id FM, simply by entering the name BPAR_C_CENTRAL_GROUP_ID into the relevant SAP transaction such as SE37 or SE38.
Function Group: BPC4
Program Name: SAPLBPC4
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BPAR_C_CENTRAL_GROUP_ID pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'BPAR_C_CENTRAL_GROUP_ID'"NOTRANSL: Alle Prüfungen Partner-Gruppierung.
EXPORTING
I_GROUP_ID = "Business Partner Grouping
I_TYPE = "Partner category
I_BP_GROUP = "BP: Collective Business Partner Indicator
I_PARTNR = "Partner Number
I_CUSTOMER = "Customer Number
* FLG_CHECK_ALL = ' ' "Business partner: Interface flag
* ACTIVITY = ' ' "ABAP System Field: Current Transaction Code
TABLES
* T_MESG = "Message collector
* T_RLTYP = "BP: Business Partner - Role
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for BPAR_C_CENTRAL_GROUP_ID
I_GROUP_ID - Business Partner Grouping
Data type: BP000-GROUP_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_TYPE - Partner category
Data type: BP000-TYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_BP_GROUP - BP: Collective Business Partner Indicator
Data type: BP000-BP_GROUPOptional: No
Call by Reference: No ( called with pass by value option)
I_PARTNR - Partner Number
Data type: BP000-PARTNROptional: No
Call by Reference: No ( called with pass by value option)
I_CUSTOMER - Customer Number
Data type: BP000-CUSTOMEROptional: No
Call by Reference: No ( called with pass by value option)
FLG_CHECK_ALL - Business partner: Interface flag
Data type: BPIB0-BP_FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACTIVITY - ABAP System Field: Current Transaction Code
Data type: SY-TCODEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BPAR_C_CENTRAL_GROUP_ID
T_MESG - Message collector
Data type: MESGOptional: Yes
Call by Reference: No ( called with pass by value option)
T_RLTYP - BP: Business Partner - Role
Data type: BP1000Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BPAR_C_CENTRAL_GROUP_ID Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_error | TYPE STRING, " | |||
| lt_t_mesg | TYPE STANDARD TABLE OF MESG, " | |||
| lv_i_group_id | TYPE BP000-GROUP_ID, " | |||
| lv_i_type | TYPE BP000-TYPE, " | |||
| lt_t_rltyp | TYPE STANDARD TABLE OF BP1000, " | |||
| lv_i_bp_group | TYPE BP000-BP_GROUP, " | |||
| lv_i_partnr | TYPE BP000-PARTNR, " | |||
| lv_i_customer | TYPE BP000-CUSTOMER, " | |||
| lv_flg_check_all | TYPE BPIB0-BP_FLAG, " SPACE | |||
| lv_activity | TYPE SY-TCODE. " SPACE |
|   CALL FUNCTION 'BPAR_C_CENTRAL_GROUP_ID' "NOTRANSL: Alle Prüfungen Partner-Gruppierung |
| EXPORTING | ||
| I_GROUP_ID | = lv_i_group_id | |
| I_TYPE | = lv_i_type | |
| I_BP_GROUP | = lv_i_bp_group | |
| I_PARTNR | = lv_i_partnr | |
| I_CUSTOMER | = lv_i_customer | |
| FLG_CHECK_ALL | = lv_flg_check_all | |
| ACTIVITY | = lv_activity | |
| TABLES | ||
| T_MESG | = lt_t_mesg | |
| T_RLTYP | = lt_t_rltyp | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " BPAR_C_CENTRAL_GROUP_ID | ||
ABAP code using 7.40 inline data declarations to call FM BPAR_C_CENTRAL_GROUP_ID
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single GROUP_ID FROM BP000 INTO @DATA(ld_i_group_id). | ||||
| "SELECT single TYPE FROM BP000 INTO @DATA(ld_i_type). | ||||
| "SELECT single BP_GROUP FROM BP000 INTO @DATA(ld_i_bp_group). | ||||
| "SELECT single PARTNR FROM BP000 INTO @DATA(ld_i_partnr). | ||||
| "SELECT single CUSTOMER FROM BP000 INTO @DATA(ld_i_customer). | ||||
| "SELECT single BP_FLAG FROM BPIB0 INTO @DATA(ld_flg_check_all). | ||||
| DATA(ld_flg_check_all) | = ' '. | |||
| "SELECT single TCODE FROM SY INTO @DATA(ld_activity). | ||||
| DATA(ld_activity) | = ' '. | |||
Search for further information about these or an SAP related objects