You can extend My Appointments
according to your business needs for different aspects, and correspondingly adjust the functions and layout of the app. For this purpose, the following extensibility options are available:
You can change which information should be displayed for the individual appointments on the overview page, and in which form.
You can add or change pushbuttons on the overview page.
You can adjust entire areas to your requirements for displaying the detail page, and add your own fields to the bottom of the page. In addition, you can add your own pushbuttons on the bottom right.
You can add your own fields in four places, for creating or changing the detail page. You cannot insert any new pushbuttons on the change page.
You can change the standard values (defaults) for fields.
To change which information should be displayed for the individual appointments on the overview page, and in which form, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:
UI | Back End/ABAP | |||
---|---|---|---|---|
View | Extension Point | Design Time: Entity Type | Design Time: Extension Include (in DDIC Structure) | Runtime: Data Structure to Be Redefined |
|
|
|
|
|
Parallel to this, you have to extend the OData service, in entity set AppointmentSet
.
The following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:
UI | Back End/ABAP | |||
---|---|---|---|---|
View | Extension Point | Entity Type | Extension Include (in DDIC Structure) | Data Structure to Be Redefined |
|
|
|
|
|
You can adjust entire areas to your requirements for displaying the detail page, and add your own fields to the bottom of the page. In addition, you can add your own pushbuttons on the bottom right.
The following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:
UI | Back End/ABAP | |||
---|---|---|---|---|
View | Extension Point | Entity Type | Extension Include (in DDIC Structure) | Data Structure to Be Redefined |
|
(replace or adjust header area of page) |
|
|
|
(replace or adjust area |
|
|
| |
(show additional fields at the bottom of the page) Note that you need to have previously defined the additional fields in the OData service. | ||||
(add additional pushbuttons) |
On the detail page, you can add your own fields in four places. You cannot insert any new pushbuttons on the change page.
The following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:
UI | Back End/ABAP | |||
---|---|---|---|---|
View | Extension Point | Entity Type | Extension Include (in DDIC Structure) | Data Structure to Be Redefined |
|
(add additional attributes in the header area of the edit view) |
|
|
|
(add additional attributes in the section of the edit view) | ||||
(add additional attributes in the section of the edit view) | ||||
(add additional attributes in the section of the edit view) |
To change the standard values (defaults) for fields, overwrite the function createAppointment
in controller NewAppointment
.
The following BAdI is available for extensibility purposes: CRM_APPT_ODATA_BD
in enhancement spot CRM_APPT_ODATA_ENH
.
You can use this BAdI to define your own logic for reading, creating, or changing appointments. This is necessary if, for example, you want to add your own fields, or use different processing logic for existing fields.
You call the BAdI by using transaction SE18
.
Note
For create and update scenarios, use the new BAdI method UPDATE_APPOINTMENT_DETAILS
instead of the old BAdI method UPDATE_APPOINTMENT
.
To plug in and execute custom code, the following hooks are available in the controller code:
Controller | Hook | Use |
---|---|---|
|
| Allows you to implement additional logic when the new appointments page is loaded. |
|
| Allows you to implement additional logic in the |
|
| Allows you to implement additional logic in the |
|
| You can decide if the save pushbutton has to be enabled for the fields added by you to the new appointments page. |
|
| Allows you to handle client side validations of the fields added by you to the new appointments page. |
|
| Allows you to provide additional properties that can be added to or removed from the Appointment entity JSON. |
|
| Allows you add additional update requests to the custom fields added as a part of the |
|
| Allows you to add additional update requests to the custom fields added as a part of the |
|
| Allows you to extend the |
For more information about UI controller hooks, see UI Controller Hooks.
The following UI controls can be hidden from the app UI.
View | Control ID | Use |
---|---|---|
|
| Allows you to add the object header in the detail view of an appointment. |
|
| Allows you to add the process type description in the detail view of an appointment. |
|
| Allows you to maintain the status of an appointment. |
|
| Allows you to maintain the text for priority status. |
|
| Allows you to maintain the status of the private flag. |
|
| Allows you to maintain the account field. |
|
| Allows you to maintain the location field. |
|
| Allows you to maintain the responsible field. |
|
| Allows you to maintain the end date in the appointment header. |
|
| Allows you to maintain an external attendee. |
|
| Allows you to maintain an internal attendee. |
|
| Allows you to display the notes tab in the appointment details screen. |
|
| Allows you to display the transaction history panel. |
|
| Allows you to maintain the document history tab. |
|
| Allows you to maintain the text for transaction description. |
|
| Allows you to display the date on which the document is created in the transaction history table. |
|
| Allows you to display the header information of an appointment. |
|
| Allows you to display the status of an appointment. |
|
| Allows you to display an icon, if an attachment is available. |
|
| Allows you to create a new appointment. |
For more information about hiding UI controls, see Concealable UI Controls.
For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.