SAP APPT_CREATE Function Module for
APPT_CREATE is a standard appt create 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 appt create FM, simply by entering the name APPT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SSCE
Program Name: SAPLSSCE
Main Program: SAPLSSCE
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function APPT_CREATE 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 'APPT_CREATE'".
EXPORTING
DATE_FROM = "
* APPOINTMENT_IS_PLANNED = ' ' "
* ACTIVATE_SUBSTITUTE = ' ' "
* SUPPRESS_MAIL = "
* TYPE_SPECIFIC_DATA = "Additional Information
* CUSTOMER_NUMBER = ' ' "
* APPOINTMENT_RULE = ' ' "Periodic appointments: Rule
* RULE_ID = ' ' "Internal Identification of Rules of Periodic Appointments
DATE_TO = "
TIME_FROM = "
TIME_TO = "
* TYPE = "Appointment type
* DESCRIPTION = "
* ROOM = "Room
* VISIBILITY = '1' "
* BODY_ACCESS_ID = ' ' "
IMPORTING
ERROR_MESSAGE = "
TABLES
* PARTICIPANT_LIST = "Participant list
* APPOINTMENT = "
* APPOINTMENT_PATTERN = "
* APPOINTMENT_BODY = "Description
* APPOINTMENT_DATES = "
* APPOINTMENT_CONFLICT_DATES = "
IMPORTING Parameters details for APPT_CREATE
DATE_FROM -
Data type: SCAPPT-DATE_FROMOptional: No
Call by Reference: No ( called with pass by value option)
APPOINTMENT_IS_PLANNED -
Data type: SCSDATAFLD-SC_FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACTIVATE_SUBSTITUTE -
Data type: SCSDATAFLD-SC_FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUPPRESS_MAIL -
Data type: SCSDATAFLD-SC_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
TYPE_SPECIFIC_DATA - Additional Information
Data type: SCAPPT-EXIT_INFOOptional: Yes
Call by Reference: No ( called with pass by value option)
CUSTOMER_NUMBER -
Data type: SCAPPT-CUST_NODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
APPOINTMENT_RULE - Periodic appointments: Rule
Data type: RULESDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
RULE_ID - Internal Identification of Rules of Periodic Appointments
Data type: SCSRULES-RULE_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DATE_TO -
Data type: SCAPPT-DATE_TOOptional: No
Call by Reference: No ( called with pass by value option)
TIME_FROM -
Data type: SCAPPT-TIME_FROMOptional: No
Call by Reference: No ( called with pass by value option)
TIME_TO -
Data type: SCAPPT-TIME_TOOptional: No
Call by Reference: No ( called with pass by value option)
TYPE - Appointment type
Data type: SCAPPT-APPT_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
DESCRIPTION -
Data type: SCAPPT-TXT_SHORTOptional: Yes
Call by Reference: No ( called with pass by value option)
ROOM - Room
Data type: SCAPPT-ROOMOptional: Yes
Call by Reference: No ( called with pass by value option)
VISIBILITY -
Data type: SCAPPT-CLASS_IDDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
BODY_ACCESS_ID -
Data type: SCAPPT-BD_ACCS_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for APPT_CREATE
ERROR_MESSAGE -
Data type: SCSERROROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for APPT_CREATE
PARTICIPANT_LIST - Participant list
Data type: SCSPARINCOptional: Yes
Call by Reference: No ( called with pass by value option)
APPOINTMENT -
Data type: SCSAPPTOptional: Yes
Call by Reference: No ( called with pass by value option)
APPOINTMENT_PATTERN -
Data type: SCSGENAPPTOptional: Yes
Call by Reference: No ( called with pass by value option)
APPOINTMENT_BODY - Description
Data type: SOLIOptional: Yes
Call by Reference: No ( called with pass by value option)
APPOINTMENT_DATES -
Data type: SCSDATESOptional: Yes
Call by Reference: No ( called with pass by value option)
APPOINTMENT_CONFLICT_DATES -
Data type: SCSDATESOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for APPT_CREATE 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_date_from | TYPE SCAPPT-DATE_FROM, " | |||
| lv_error_message | TYPE SCSERROR, " | |||
| lt_participant_list | TYPE STANDARD TABLE OF SCSPARINC, " | |||
| lv_appointment_is_planned | TYPE SCSDATAFLD-SC_FLAG, " ' ' | |||
| lv_activate_substitute | TYPE SCSDATAFLD-SC_FLAG, " ' ' | |||
| lv_suppress_mail | TYPE SCSDATAFLD-SC_FLAG, " | |||
| lv_type_specific_data | TYPE SCAPPT-EXIT_INFO, " | |||
| lv_customer_number | TYPE SCAPPT-CUST_NO, " SPACE | |||
| lv_appointment_rule | TYPE RULES, " SPACE | |||
| lv_rule_id | TYPE SCSRULES-RULE_ID, " SPACE | |||
| lv_date_to | TYPE SCAPPT-DATE_TO, " | |||
| lt_appointment | TYPE STANDARD TABLE OF SCSAPPT, " | |||
| lv_time_from | TYPE SCAPPT-TIME_FROM, " | |||
| lt_appointment_pattern | TYPE STANDARD TABLE OF SCSGENAPPT, " | |||
| lv_time_to | TYPE SCAPPT-TIME_TO, " | |||
| lt_appointment_body | TYPE STANDARD TABLE OF SOLI, " | |||
| lv_type | TYPE SCAPPT-APPT_TYPE, " | |||
| lt_appointment_dates | TYPE STANDARD TABLE OF SCSDATES, " | |||
| lv_description | TYPE SCAPPT-TXT_SHORT, " | |||
| lt_appointment_conflict_dates | TYPE STANDARD TABLE OF SCSDATES, " | |||
| lv_room | TYPE SCAPPT-ROOM, " | |||
| lv_visibility | TYPE SCAPPT-CLASS_ID, " '1' | |||
| lv_body_access_id | TYPE SCAPPT-BD_ACCS_ID. " SPACE |
|   CALL FUNCTION 'APPT_CREATE' " |
| EXPORTING | ||
| DATE_FROM | = lv_date_from | |
| APPOINTMENT_IS_PLANNED | = lv_appointment_is_planned | |
| ACTIVATE_SUBSTITUTE | = lv_activate_substitute | |
| SUPPRESS_MAIL | = lv_suppress_mail | |
| TYPE_SPECIFIC_DATA | = lv_type_specific_data | |
| CUSTOMER_NUMBER | = lv_customer_number | |
| APPOINTMENT_RULE | = lv_appointment_rule | |
| RULE_ID | = lv_rule_id | |
| DATE_TO | = lv_date_to | |
| TIME_FROM | = lv_time_from | |
| TIME_TO | = lv_time_to | |
| TYPE | = lv_type | |
| DESCRIPTION | = lv_description | |
| ROOM | = lv_room | |
| VISIBILITY | = lv_visibility | |
| BODY_ACCESS_ID | = lv_body_access_id | |
| IMPORTING | ||
| ERROR_MESSAGE | = lv_error_message | |
| TABLES | ||
| PARTICIPANT_LIST | = lt_participant_list | |
| APPOINTMENT | = lt_appointment | |
| APPOINTMENT_PATTERN | = lt_appointment_pattern | |
| APPOINTMENT_BODY | = lt_appointment_body | |
| APPOINTMENT_DATES | = lt_appointment_dates | |
| APPOINTMENT_CONFLICT_DATES | = lt_appointment_conflict_dates | |
| . " APPT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM APPT_CREATE
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 DATE_FROM FROM SCAPPT INTO @DATA(ld_date_from). | ||||
| "SELECT single SC_FLAG FROM SCSDATAFLD INTO @DATA(ld_appointment_is_planned). | ||||
| DATA(ld_appointment_is_planned) | = ' '. | |||
| "SELECT single SC_FLAG FROM SCSDATAFLD INTO @DATA(ld_activate_substitute). | ||||
| DATA(ld_activate_substitute) | = ' '. | |||
| "SELECT single SC_FLAG FROM SCSDATAFLD INTO @DATA(ld_suppress_mail). | ||||
| "SELECT single EXIT_INFO FROM SCAPPT INTO @DATA(ld_type_specific_data). | ||||
| "SELECT single CUST_NO FROM SCAPPT INTO @DATA(ld_customer_number). | ||||
| DATA(ld_customer_number) | = ' '. | |||
| DATA(ld_appointment_rule) | = ' '. | |||
| "SELECT single RULE_ID FROM SCSRULES INTO @DATA(ld_rule_id). | ||||
| DATA(ld_rule_id) | = ' '. | |||
| "SELECT single DATE_TO FROM SCAPPT INTO @DATA(ld_date_to). | ||||
| "SELECT single TIME_FROM FROM SCAPPT INTO @DATA(ld_time_from). | ||||
| "SELECT single TIME_TO FROM SCAPPT INTO @DATA(ld_time_to). | ||||
| "SELECT single APPT_TYPE FROM SCAPPT INTO @DATA(ld_type). | ||||
| "SELECT single TXT_SHORT FROM SCAPPT INTO @DATA(ld_description). | ||||
| "SELECT single ROOM FROM SCAPPT INTO @DATA(ld_room). | ||||
| "SELECT single CLASS_ID FROM SCAPPT INTO @DATA(ld_visibility). | ||||
| DATA(ld_visibility) | = '1'. | |||
| "SELECT single BD_ACCS_ID FROM SCAPPT INTO @DATA(ld_body_access_id). | ||||
| DATA(ld_body_access_id) | = ' '. | |||
Search for further information about these or an SAP related objects