SAP G_SET_BUF_CHANGE_RELATION Function Module for









G_SET_BUF_CHANGE_RELATION is a standard g set buf change relation 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 g set buf change relation FM, simply by entering the name G_SET_BUF_CHANGE_RELATION into the relevant SAP transaction such as SE37 or SE38.

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



Function G_SET_BUF_CHANGE_RELATION 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 'G_SET_BUF_CHANGE_RELATION'"
EXPORTING
* FCODE = 'INSE' "
EXT_HRI1001 = "

EXCEPTIONS
NO_AUTHORITY = 1 ENQUEUE_FAILED = 2 CHANGE_NOT_POSSIBLE = 3
.



IMPORTING Parameters details for G_SET_BUF_CHANGE_RELATION

FCODE -

Data type: T77FC-FCODE
Default: 'INSE'
Optional: Yes
Call by Reference: Yes

EXT_HRI1001 -

Data type: HRI1001
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

ENQUEUE_FAILED -

Data type:
Optional: No
Call by Reference: Yes

CHANGE_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for G_SET_BUF_CHANGE_RELATION 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_fcode  TYPE T77FC-FCODE, "   'INSE'
lv_no_authority  TYPE T77FC, "   
lv_ext_hri1001  TYPE HRI1001, "   
lv_enqueue_failed  TYPE HRI1001, "   
lv_change_not_possible  TYPE HRI1001. "   

  CALL FUNCTION 'G_SET_BUF_CHANGE_RELATION'  "
    EXPORTING
         FCODE = lv_fcode
         EXT_HRI1001 = lv_ext_hri1001
    EXCEPTIONS
        NO_AUTHORITY = 1
        ENQUEUE_FAILED = 2
        CHANGE_NOT_POSSIBLE = 3
. " G_SET_BUF_CHANGE_RELATION




ABAP code using 7.40 inline data declarations to call FM G_SET_BUF_CHANGE_RELATION

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 FCODE FROM T77FC INTO @DATA(ld_fcode).
DATA(ld_fcode) = 'INSE'.
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!