SAP APPTSEG_MODIFY Function Module for

Search SAP Function Modules

APPTSEG_MODIFY is a standard apptseg modify 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 apptseg modify FM, simply by entering the name APPTSEG_MODIFY into the relevant SAP transaction such as SE37 or SE38.

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

Function APPTSEG_MODIFY 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 'APPTSEG_MODIFY'"
  EXPORTING
   APPT_GUID =  "GUID of appointment
*  TXT_PUB_ID = ' ' "
*  DATE_FROM =  "From Date
*  TIME_FROM =  "From time
*  ZONE_FROM =  "Appointment calendar: Time zone of start of appointment
*  DATE_TO =  "To Date
*  TIME_TO =  "To time
*  ZONE_TO =  "Appointment calendar: Time zone of end of appointment
*  APPT_TYPE =  "Technical appointment type name
*  APPL_GUID =  "GUID (Hex) specified by the application

 IMPORTING
   APPTSEG_NEW =  "Interface: Individual Appointments
   ERROR_MESSAGE =  "Appointments diary: Error structure

.

IMPORTING Parameters details for APPTSEG_MODIFY

APPT_GUID - GUID of appointment

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

TXT_PUB_ID -

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

DATE_FROM - From Date

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

TIME_FROM - From time

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

ZONE_FROM - Appointment calendar: Time zone of start of appointment

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

DATE_TO - To Date

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

TIME_TO - To time

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

ZONE_TO - Appointment calendar: Time zone of end of appointment

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

APPT_TYPE - Technical appointment type name

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

APPL_GUID - GUID (Hex) specified by the application

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

EXPORTING Parameters details for APPTSEG_MODIFY

APPTSEG_NEW - Interface: Individual Appointments

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

ERROR_MESSAGE - Appointments diary: Error structure

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

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

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