SAP SEO_BUFFER_CHECK_CHANGED Function Module for Abfrage, ob sich der Puffer geändert hat









SEO_BUFFER_CHECK_CHANGED is a standard seo buffer check changed SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Abfrage, ob sich der Puffer geändert hat 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 seo buffer check changed FM, simply by entering the name SEO_BUFFER_CHECK_CHANGED into the relevant SAP transaction such as SE37 or SE38.

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



Function SEO_BUFFER_CHECK_CHANGED 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 'SEO_BUFFER_CHECK_CHANGED'"Abfrage, ob sich der Puffer geändert hat
EXPORTING
* VERSION = SEOC_VERSION_INACTIVE "

IMPORTING
CHANGED = "
CIFKEYS = "
.



IMPORTING Parameters details for SEO_BUFFER_CHECK_CHANGED

VERSION -

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

EXPORTING Parameters details for SEO_BUFFER_CHECK_CHANGED

CHANGED -

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

CIFKEYS -

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

Copy and paste ABAP code example for SEO_BUFFER_CHECK_CHANGED 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_changed  TYPE SEOX_BOOLEAN, "   
lv_version  TYPE SEOVERSION, "   SEOC_VERSION_INACTIVE
lv_cifkeys  TYPE SEOC_CLIF_KEYS. "   

  CALL FUNCTION 'SEO_BUFFER_CHECK_CHANGED'  "Abfrage, ob sich der Puffer geändert hat
    EXPORTING
         VERSION = lv_version
    IMPORTING
         CHANGED = lv_changed
         CIFKEYS = lv_cifkeys
. " SEO_BUFFER_CHECK_CHANGED




ABAP code using 7.40 inline data declarations to call FM SEO_BUFFER_CHECK_CHANGED

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.

 
DATA(ld_version) = SEOC_VERSION_INACTIVE.
 
 


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!