SAP TERM_UPDATE Function Module for Save term module

Search SAP Function Modules

TERM_UPDATE is a standard term update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save term module 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 term update FM, simply by entering the name TERM_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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

Function TERM_UPDATE 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 'TERM_UPDATE'"Save term module
  EXPORTING
*  ANLEGDATUM = SY-DATUM "
*  START_RELEASE = ' ' "
*  CHANGED_RELEASE = ' ' "
*  ANLEGER = SY-UNAME "
   APPLIKKZ =  "
   BEGRIFF =  "
   GELENKNR =  "
*  GENUS = ' ' "
*  KATEGORIE = ' ' "
*  SPRACHE = ' ' "
*  STATUS = ' ' "

 IMPORTING
   RETCODE =  "

TABLES
   ITERMATTR =  "

.

IMPORTING Parameters details for TERM_UPDATE

ANLEGDATUM -

Data type: TERM6-ADATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

START_RELEASE -

Data type: TERM6-RELEASE_F
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGED_RELEASE -

Data type: TERM6-RELEASE_L
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ANLEGER -

Data type: TERM6-ANLEGER
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

APPLIKKZ -

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

BEGRIFF -

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

GELENKNR -

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

GENUS -

Data type: TERM6-GENIUS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KATEGORIE -

Data type: TERM6-KATEGORIE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SPRACHE -

Data type: TERM6-SPRAS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

STATUS -

Data type: TERM6-STATUS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TERM_UPDATE

RETCODE -

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

TABLES Parameters details for TERM_UPDATE

ITERMATTR -

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

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

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