SAP FM16_RELEASE_GROUP_CUSTOMIZING Function Module for

Search SAP Function Modules

FM16_RELEASE_GROUP_CUSTOMIZING is a standard fm16 release group customizing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fm16 release group customizing FM, simply by entering the name FM16_RELEASE_GROUP_CUSTOMIZING into the relevant SAP transaction such as SE37 or SE38.

Function Group: FM16
Program Name: SAPLFM16
Main Program: SAPLFM16
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM16_RELEASE_GROUP_CUSTOMIZING 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 'FM16_RELEASE_GROUP_CUSTOMIZING'"
  EXPORTING
   I_FIKRS =  "
   I_GJAHR =  "
*  I_ORDER =  "
*  I_ACTIVITY =  "
*  I_SUBVO =  "
*  I_RELGRP =  "

 IMPORTING
   E_NO_RELEASE_GROUPS =  "
   E_NOT_ASSIGNED =  "
   E_COVER_INCONSIST =  "
   E_COVER_INCONSIST_TEXT =  "
   E_INVALID_RELE_ORDER =  "

TABLES
*  T_RELGRP =  "
*  T_ASSIGNED =  "

.

IMPORTING Parameters details for FM16_RELEASE_GROUP_CUSTOMIZING

I_FIKRS -

Data type: BPIN-FIKRS
Optional: No
Call by Reference: No ( called with pass by value option)

I_GJAHR -

Data type: BPIN-GJAHR
Optional: No
Call by Reference: No ( called with pass by value option)

I_ORDER -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ACTIVITY -

Data type: BPIN-VORGA
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SUBVO -

Data type: BPIN-SUBVO
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_RELGRP -

Data type: BPIN-VORGA
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FM16_RELEASE_GROUP_CUSTOMIZING

E_NO_RELEASE_GROUPS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

E_NOT_ASSIGNED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

E_COVER_INCONSIST -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

E_COVER_INCONSIST_TEXT -

Data type: FMBUDFRGRP-FRGT5
Optional: No
Call by Reference: No ( called with pass by value option)

E_INVALID_RELE_ORDER -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FM16_RELEASE_GROUP_CUSTOMIZING

T_RELGRP -

Data type: FMBUDFRGRP
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_ASSIGNED -

Data type: FMBUDFRGVO
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FM16_RELEASE_GROUP_CUSTOMIZING 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.

ABAP code using 7.40 inline data declarations to call FM FM16_RELEASE_GROUP_CUSTOMIZING

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.

Search for further information about these or an SAP related objects