This note provides recommendations for Microsoft Project Import to and Export from SAP Portfolio and Project Management 5.0.
1 Import Project from Microsoft Project
1.1 Information specific to MS Project Import to Portfolio Management
A Microsoft Project can be imported to Portfolio Management to transfer the project data to operational data in Portfolio Management. When an import takes place, a link is established between the Microsoft Project File and the Item to which it is imported to.
1.1.1 Pre-requisites
To enable the Integration, following conditions must be fulfilled.
- There exists an Item in Portfolio Management which is not linked to any project in Base Project System (Microsoft Project, Microsoft Project Server and SAP PS)
- There exists a Project in Project Management (referred as "Operational Project") attached to the Item
- Basic configuration steps have been carried in SAP Portfolio and Project Management IMG
- It is recommended to export a Project in Project Management to Microsoft Project, make changes and then import it again.
1.1.2 Configuration
Base Project import creates/modifies Project data in Project Management including Project Definition, Phase, Task, Checklists, Checklist Items, Project Roles and Resources. It is necessary that all the required configurations to create these objects have been carried upon before the integration takes place. To do the mentioned configuration, please go to Project Management IMG. Once you complete the configuration, please go to Global Settings (Portfolio Management -> Global Customizing -> Global Settings -> Override Default Global Settings) in Portfolio Management IMG and define default values for the Area '009'.
0001 - Default Status Profile for Portfolio Item Project Plan
0002 - Default cProjects Project Type
0003 - Default cProjects Task Type
0004 - Default cProjects Role Type
0005 - Default cProjects Phase Type
0006 - Default cProjects Role Type for Integration
While creating Status Profile in Project Management, please make sure that the status profile has settings that allow deletion. You can also copy the SAP delivered Status Profile '00000RPM' from Client 0
Default values are considered if this information can't be retrieved from Microsoft Project.
1.2 Information specific to MS Project Import to Project Management
A Microsoft Project can be imported to Project Management to transfer the project data to an operational project or a simulation in Project Management.
1.2.1 Pre-requisites
A MS Project file (.mpp file) can only be imported to Project Management if it has a 'Title' which is not empty (initial) and has a maximal length of 24 characters. The title of MS Project file can be maintained through the menu path File -> Properties -> Title in MS project.
1.2.2 Configuration
The following mappings should be necessarily maintained:
SAP Customizing Implementation Guide -> SAP Portfolio and Project Management -> Common Functions -> Import and Export of Project Data -> Microsoft Project Integration -> Assign Fields for Import to Project Management.
Main Group Group
PDMP PDMP
Sub Object Field Name - TITLE
Project Management Object - PDCP
Project Management Object field Name - PROJECT_ID
Above mapping will make the MS Project Title show up as the 'Number:' field for the imported project in Project Management.
The mapping process has been explained in detail in the next section.
In the PDF file attached to this note you can find more detail information for the Project Management customizing.
1.3 Common details of MS Project Import to Portfolio and Project Management
1.3.1 Mapping Table
To access the Mapping Table:
SAP Customizing Implementation Guide -> SAP Portfolio and Project Management -> Common Functions -> Import and Export of Project Data -> Microsoft Project Integration -> Assign Fields for Import to Project Management.
Choose an entry with appropriate Main Grouping and Sub Grouping and double click on "Field Mapping". Here "Sub Object Field Name" represents the fields that are available from Microsoft Project and "Project Management Object Field Name" represents the fields that are available from Project Management Project.
For example, to review the Project Header Mapping of MS Project and
Project Management Project, Select Main Grouping as "PDMP" and Sub Grouping as "PDMP" and review the field mapping. For Microsoft Project, Main Grouping is always "PDMP" and sub grouping can be any of the following:
PDMP - MS Project Client Project Definition
MT - MS Project Tasks
MR - MS Project Resources
MP - MS Project Phases
MC - MS Project Checklists
MCI - MS Project Checklist Items
MAR - MS Project Resource Assignments
MAT - MS Project Task Assignments
Please remember that mapping information of fields determines that what
field of Microsoft Project is transferred to what field of Project in Project Management. Incase you decide to alter the standard mapping delivered by SAP or you wish to add new mapping of fields, please note that conversion would be required from one field to another.
For example, Milestone (flag) of Microsoft Project Tasks is mapped to
Milestone (flag) of tasks in Project Management. In MS Project, flag is stored as either '1' or '0' whereas in Project Management, the same information is stored as 'X' or ' '. Hence when there is a mapping for any two fields, it is explicitly required that data is converted from one form to another unless and otherwise the formats of both fields are same.
Custom fields of tasks and resources in Microsoft Project can be
imported to Project Management. The data types of the mapped entries should correspond to each other for the values to be transferred directly. For SAP delivered mapping, conversions are provided by SAP and for any other addition, you must have custom implementation for BADI definition DPR_MSP_CUST_FIELDS for the method CUST_CONVERT_MSPINT2DPR. Populate CS_DPRDATA from IS_MSP_PROJECT_INT and convert all the data that is additionally added. Please refer BADI interface method documentation for more details.
1.3.2 Target Object
In Import Project UI, select the application 'Microsoft Project'. Choose the '.mpp' file. Click on 'Import Selected Data' button. The details (Target Object and Data for Import) will be shown. These details are based on the 'Category' in MS Project file (File->Properties).
The 'Target Object' section is invisible in case of new project creation.
In Portfolio and Project Management 5.0, you can choose if you want to create a new operational project or Overwrite an existing project or create a Simulation version. Depending on the 'Proj Type' value set in Project Management IMG, 'Target Object' is set in Import UI. To see the 'Proj Type' value, go to SAP Customizing Implementation Guide -> SAP Portfolio Management and Project Management -> Project Management -> Structure -> Define Project Types. Project Types are listed here. Note that 'Project Type' in Project Management corresponds to 'Category' in MS Project. Select the 'Project Type' (which is entered in Category field in MS Project). Click on 'Details'. Under the 'Project Integration' section, you can set the value for 'Proj Type'.
Always Overwrite Existing Project - If 'Proj Type' is set as 'Always Overwrite Existing Project', then 'Overwrite Current Project' radio button is selected in Import Project UI.
Always Create Simulation - If 'Proj Type' is set as 'Always Create Simulation', then 'Create Simulation Version' radio button is selected in Import Project UI.
End User Choice - If 'Proj Type' is set as 'End User Choice', then no option is selected in Import Project UI.
1.3.3 Project Header
Project Information stored in Microsoft Project File can be imported
as Project Header in Project Management. If you wish to create Project in Project Management with specific Project Type, please maintain "CATEGORY" field (File->Properties->Category) in MS Project with correct Project Type. To get the list of Project Types available in Project Management, please refer Project Management IMG structure.
It is possible to import values of standard and custom fields for the project summary task of MS Project. Mapping needs to be defined in
IMG Configuration.
In XML interface of MS Project if Title is empty (This may happen when new MS Project is created rather than using MS Project file saved from Project Export) Project Management will generate the Title and this Title is notified to the user in the Message area of Import Project UI. This can also be seen in the Import log once the project is imported successfully.
1.3.4 Phases
To create a phase in Project in Project Management from Microsoft Project, it is necessary to mark a task in Microsoft Project as Phase. To do so, please choose any enterprise text field (preferably TEXT20) for task in MS Project and maintain it with specific Phase Type. Use the Mapping table to map the Enterprise Field to Phase Type of Project in Project Management. To get the list of Phase Types available in Project Management, please refer Project Management IMG structure.
A task can be marked as phase only if it is a root level (level 1) task.
1.3.5 Tasks
When an import takes place, the tasks are created in Project in Project Management under a specific phase if the root level task is marked as Phase in Microsoft Project.
To meet this scenario, if a root level task has sub tasks and the root level task is not marked as phase, then the root level task and all its sub tasks are imported in Project Management under a phase called 'TASK HIERARCHY'. This behavior is due to the fact that a task under a project can't have sub tasks in Project Management.
If a root level task doesn't have sub tasks, then this task will be imported directly under the project.
1.3.6 Checklists
To create a checklist in Project in Project Management from Microsoft Project, it is necessary to mark a task in Microsoft Project as Checklist. To do so, please chose any enterprise text field (preferably TEXT21) for task in MS Project and maintain it with specific Checklist Type. Use the Mapping table to map the Enterprise Field to Checklist Type of Project in Project Management. To get the list of Checklist Types available in Project Management, please refer Project Management IMG structure.
A task can be marked as checklist only if it is a root level task or it is a first level sub task of a task which is marked as phase. Dates, Duration, Work, Predecessor Links or any task related information is not imported as a Checklist in Project Management doesn't have these attributes.
1.3.7 Checklist Items
All first level sub tasks of Checklist tasks (Tasks which are marked as
checklists) are automatically created as Checklist Items in Project Management. It is not possible to explicitly specify any task as a checklist item. All tasks under a checklist item are automatically created as sub tasks under the checklist item.
Checklist Item has only Finish Date in Project Management. All other task information is not imported as a Checklist item in Project Management as it does not have these attributes.
1.3.8 Calendar
Calendar plays a significant role in importing the project data into
Project Management. It is absolutely essential that Calendars maintained in MS Project matches with the Calendars maintained in Project Management.
By default, a calendar in MS Project has following attributes
- Monday to Friday is marked as working day
- Saturday and Sunday are non working days
- Working time is 8.00 AM to 12 PM and 1 PM to 5 PM
- A working day has 8 hours
You can either create a custom calendar in MS Project or in Project Management.
1.3.8.1 Creating custom calendar in MS Project
You can export the calendar from Project in Project Management. To do so, please follow the following steps.
- Create or Select a Project in Project Management which has the required calendar
- Export the Project as MS Project and store it in your local
machine
- Open the exported MS Project, Go to Tools -> Organizer ->
Calendars
- You will see Global Calendars in the Right hand side box and
the Custom calendars exported in the left hand side box
- Select the custom calendar from the Project
- Copy the Custom Calendar from the Project to 'Global.MPT'
SAP Calendar is now successfully integrated with MS Project and you can use this calendar for all the MS Projects you create. If you wish to export more calendars, follow the steps above mentioned. To maintain the Calendar for the MS project, go to Project -> Project
Information and select the calendar you have exported.
1.3.8.2 Creating custom calendar in SAP System
If the MS Project projects uses the default MS Project Calendar or the
Calendars that do not comply with the SAP Calendars in Project Management system, a custom calendar must be created in SAP system where the Portfolio and Project Management 5.0 is installed. To create a factory calendar, please follow following steps:
- Go to SAP Customizing Implementation Guide -> SAP NetWeaver
-> General Settings -> Maintain Calendar
- Select Factory Calendar and Click on Change
- Click on Create
- Specify the Calendar ID and description. Specify the validity
period of the all the projects. Please remember that all your
MS Project and Project Management must lie within the validity
- Do not specify any Holiday calendar.
- Check Monday to Friday and uncheck all other fields
- Save
1.3.8.3 Default Calendar Settings
Once you have created a custom calendar in either in MS Project or a
Factory Calendar with only holiday as Saturday and Sunday in Project Management, you must default the calendars that would be used for ALL import scenarios.
- Please go to SAP Customizing Implementation Guide -> SAP Portfolio and Project Management -> Project Management -> Resource Management -> Basic Settings for Roles -> Make General Settings for Distribution
- Select 'Customer Setting' in 'Type of Setting' drop down and click on 'Details'.
- Specify Distribution Unit as any unit which is configured for 8
hours
- Specify Hours Per Day as 8
- Specify Calendar which you have created just now
- Specify the Unit for Hour
1.3.9 Dates
It is necessary that Calendar maintained in MS Project match with the
Calendar in Project in Project Management without which it is not possible to import the dates correctly. Please refer the Calendar section for more details.
Dates are converted into Project Management format from the MS Project format. The Dates are filled with Fixed Start Constraint and Fixed Finish Constraint. Other constraint types are not mapped. While transferring Date to Project Management, the Time information attached to the date is ignored.
If a task is marked as Checklist, dates are not imported as Checklist in Project Management doesn't have dates.
If a task is marked as Checklist Item, Only finish date is imported.
1.3.10 Work Effort
Work effort attached to a task is transferred as Work effort in Project Management and stored with the default unit maintained in Project Type. If there is no unit maintained in Project Type, the unit is retrieved from Resource Management Default Settings.
For example, if 40 hours are maintained for a task, and default unit
maintained in Project Type is FTE (Assuming FTE is configured for 8 hours), the task will have work effort of 5 FTE.
1.3.11 Duration
Duration is calculated automatically from the Start Date and the Finish
Date. As long as Calendar is maintained correctly, the Duration is expected to be the same of Microsoft Project File. The unit for the Duration is the Unit which is configured for 24 hours.
1.3.12 Relationships
Predecessor links maintained in tasks in MS Project are transferred as Task Relationships in Project Management. The relationships are established with relationship types exactly with the same link types of Predecessor links in MS Project. The lag between the two tasks is also transferred as lag into Project in Project Management and stored in "Days" as Project Management schedules tasks in days. Percentage Lags in MS Project is imported as absolute lags in Project Management. While creating relationships, following business rules apply. Relationships can only exist between two tasks if no task of them is superior task or subtask of the other task. Note that it is only possible to link two tasks by a relationship.
1.3.13 Project Roles
Resources attached to the Microsoft Project are transferred as Project
Roles in Project Management. To create a Project Role in Project in Project Management from Microsoft Project, it is necessary to mark a resource in Microsoft Project as Project Role with the Role Type. To do so, please choose any enterprise text field (preferably TEXT3) for resource in MS Project and maintain it with specific non distributed Role Type staffed by either 'project lead' or 'resource manager via authorization'. Use the Mapping table to map the Enterprise Field to Role Type of Project Management. To get the list of Role Types
available in Project Management, please refer Project Management IMG structure.
Please note that only the resources with the type "Work" in MS Project are considered while importing them as Project Roles.
1.3.14 Resource Assignments to Project Roles
You must maintain "Code" field for resource with Employee ID in Resource Sheet of MS Project in order to import them as Resources in Project Management Project.
The Employee ID should have a corresponding Business Partner in Portfolio Management or Project Management. The "Employee" attached to the resource is transferred as a "Resource" attached to the Project Role in Project Management. Please note that every role will contain at most one resource attached to it at the end of Project Import.
1.3.15 Role Assignments to Tasks
Resource assignments to tasks in Microsoft Project are transferred as Role assignments attached to tasks in Project in Project Management. Please note that 'Resource' in MS Project represents 'Project Role' in Project Management whereas 'Employee' attached to resource in MS Project represents 'Resource' in Project Management.
Please note that it is possible in MS Project to specify the number of
hours a resource work in a day ( also known as Percentage of work ). This information will not be imported to Project in Project Management. It is always assumed that The Project Roles are equally assigned to the tasks.
1.3.16 Outline Codes
The custom outline codes in Microsoft Project for tasks and resources can be mapped to standard/custom fields in Project Management.
2 Exporting Projects to Microsoft Project
When a Project in Project Management is exported, a new Microsoft Project file is created with the necessary data. The export of data occurs mostly in the same way as the import functions.
2.1 Information specific to Project Management Export to MS Project
Please maintain the following mapping:
SAP Customizing Implementation Guide -> SAP Portfolio and Project Management -> Common Functions -> Import and Export of Project Data -> Microsoft Project Integration -> Assign Fields for Export from Project Management
Main Group Group
PDMP PDMP
Sub Object Field Name - TITLE
Project management Object - PDCP
Project management Object field Name - NUMBER
Sub Object Field Name - NAME
Project management Object - PDCP
Project management Object field Name - NUMBER
This mapping will make the Project's 'Number' in Project Management as the Title of MS Project file created out of the export.
2.2 General Details
- The Project data is exported as Project Definition in MS
Project
- It is possible to export the values of project definition fields to Project summary task in MS Project. Export of both the standard and custom fields is supported for the project definition.
After Project export, values will be added in the value list with the actual value of field defaulted in. For example, if a user maps "Created by" or "Description" fields of Project Management Project to enterprise fields (for example, Text17 or Text18) then these enterprise fields (Text17 or Text18) will appear as value lists with the value added in the value list. If the "Description" field of Project Management Project has the value "Project description" then in MSP after export this field will appear as value list (drop down) with the value "Project Description" defaulted.
- The Phases are exported as Tasks and are marked as Phases
- Tasks under the phase are exported as subtasks under the task
which is marked as phase
- If the calculation mode is automatic in MS Project and the start date and the finish date are the same in Project Management Project, the MSP duration will automatically be changed to 0, regardless if a value is populated in Project Management Project. Additionally, if the duration is 0, MS Project will automatically set the milestone flag of tasks regardless of milestone value coming from Project Management.
- If the work is filled and even the start date and finish date of task are not same, task is exported as Milestone. To avoid this, if a task has the work maintained then the project type should have the 'Time Recording for' field set. This can be set in the following location in IMG:
SAP Customizing Implementation Guide -> SAP Portfolio and Project Management -> Project Management -> Structure -> Define Project Types.
- Checklists are exported as Tasks and are marked as Checklists
- Checklist items and sub tasks of Checklist Item are exported
as sub tasks of the task which is marked as checklist
- Project Roles are exported as Resources and the Employee ID
of the resource assigned to the Project Role is copied to the
CODE field of the Resource in MS Project
- Relationships between the tasks are exported as Predecessor
Links in MS Project. If the Predecessor task finish earlier
than the start of the current task, the lag between the tasks
is automatically created
- Customer can export any number of times from the Item or
Project in Project Management.
2.3 Calendar
Custom Calendar is created in MS Project from the SAP Calendar attached to the Project in Project Management. The calendar is created with same start, end date and with same public holidays as of the SAP Calendar. By default, a Calendar in MS Project is created with
- A working day has 8 hours
- Working time is 8.00 AM to 12 PM and 1 PM to 5 PM
Customer would be able to modify this information using custom
implementation for BADI definition DPR_MSP_CUST_FIELDS for the method
CUST_CONVERT_MSPINT2ABAP. Please refer the BADI interface method
documentation for more details.
2.4 Dates
Tasks are populated with Start and Finish dates for the leaf tasks.
Microsoft Project controls how this date is carried to any parent tasks and hence the dates of the tasks in Microsoft Project and Project Management Project may not be exactly the same.
A checklist does not have any date information attached to it. And hence when they are exported as tasks, they get the dates of the respective phase or the project they belong to.
A checklist item does not have any start date information attached to it. And hence when they are exported as tasks, they get the start date of the respective phase or the project they belong to. The finish date of the checklist item is exported as finish date.
A task with 0 duration does not have any start date information attached to it. And hence when they are exported as tasks, they get the finish date maintained in Project Management as their respective start date. The finish date of the 0 duration task is exported as finish date.
2.5 Duration
In MS Project, Tasks are exported in such a way that duration is calculated automatically from the Start and Finish Date. Duration is expected to contain duration maintained in Project Management as long as Calendar is the same.
Please note that this may not be the case all the times as the Duration in MS Project is also affected by the dates, work effort, resource assignments and the way task is set up.
2.6 Work Effort
Work effort is exported from Project Management and is expected to contain the work effort of the corresponding object. Please note that this may not be the case all the times as work effort of the resource assignments to tasks have direct impact on work and duration. The unit is configured globally in MS Project and is automatically converted and displayed.
Automatic calculation of remaining work based on POC does not happen
in MS Project. For example, in Project Management if a task has total work and POC assigned and exported to MS Project then MS Project will not automatically calculate the remaining work. MS Project has the same effort as in Project Management.
2.7 Percent Complete
The percent complete value of a task is exported to MS Project
as the Percent Complete attribute of a task.
If actual work is maintained in Project Management with the corresponding mapping with MS Project and exported then MSP will calculate the POC automatically and the value can be seen in '% Complete' column in MS Project. For example, in Project Management if total work is maintained as 10 Hours and confirmed work as 2 Hours and exported to MS Project then MS Project will calculate the POC as 20% for task. This value can be seen in '% Complete' column.
2.9 Mapping Table
All the necessary mappings have been provided to achieve smooth export
and please note that any modifications or additions in Mapping Table might lead to inconsistencies and hence the customer is strongly recommended not to modify the mapping information related to project export.
All Business rules apply as mentioned in the section 1.3.1. Custom Fields of Project Management can be exported to Microsoft Project. The data types of the mapped entries should correspond to each other for the values to be transferred directly. For SAP delivered mapping, conversions are provided by SAP and for any other addition, you must have custom implementation for BADI definition DPR_MSP_CUST_FIELDS for the method CUST_CONVERT_DPR2MSPINT. Please refer BADI interface method documentation for more details.
2.10 Role to Task Assignments
All the Project Roles assigned to Tasks in Project Management Project are exported as Resource assignments to Tasks in MS Project. The work effort of the task must match with the combined work effort of the role assignments in Project in Project Management.
Please note that the Work Effort has the higher precedence in MS Project if a task has resource assignment and hence work effort and the duration must match. If they don't match, the amount of hours a resource work in a day is adjusted in such a way that work effort and duration are the same. In this process, the amount of work is equally distributed among the resources.
2.11 Value List
Value list descriptions are populated in MS Project during export of a Project. Value list descriptions are populated for
- Phase Type
- Checklist Type
- Process
- Priority
- Duration
- Severity
- Currency
- Responsible Role
- Responsible Resource
Value list will not be populated for fields on the project definition.
2.12 Sort Order
The project elements order will be retained during both import and export. That is the sequence of project elements will remain the same during both import and export. This applies for project elements where sort number is present.
3. Additional Information
3.1 Difference between Base Projects and Portfolio Project
- Portfolio Project is a Project in Project Management attached to an item in Portfolio Management which is stored in the same system as of Portfolio Management. A portfolio project is integral part of item and is called so only if the project in Project Management is either created from an item or later assigned to an item.
- A Base Project is a project in a different project system (MS
Project, MS Project Server, SAP PS).
3.2 Known Behavior
- If a task is exported with resource assignments and has a
predecessor links (or Relationships) with any other tasks,
there may be a warning in MS Project specifying that task is
automatically adjusted in order to accommodate the predecessor
links and resource assignments.
3.3 Whitelist and OfficeControl
- As of SAP Portfolio and Project Management 5.0, the import and export UI in both Project Management and Portfolio Management uses the Web Dynpro ABAP OfficeControl UI element for Microsoft Project Integration. Since rendered pages are normally displayed in a Web browser connected to the Internet in Web Dynpro, security aspects must be considered for UI elements like OfficeControl.
- The following security measures therefore exist for OfficeControl:
- OfficeControl only communicates with authorized servers.
- Data can only be stored in authorized directories.
- Data can only be read from authorized directories.
- The authorized servers and directories are listed in a whitelist (an administrator stores this information locally using transactions WDR_ACF_WLIST and ACF_WHITELIST_SETUP).
1. The administrator creates the whitelist in transactions WDR_ACF_WLIST.
2. To work with a local whitelist in an SAP system, user needs a certificate for the system in question. The administrator has to download this certificate using transaction ACF_WHITELIST_SETUP. The certificate will then be stored in a local directory.
- If requests for access to directories or communication with servers are sent using HTTP or HTTPS, the control first checks whether this is allowed. It then compares the directories or servers in question with the data in the local whitelist file. It only executes the relevant methods if the authorization is set in the whitelist.
- The whitelist certificate needs to be installed locally on each end-user PC to perform the project import and export. The whitelist certificate can be generated using transaction WDR_ACF_GEN_CERT. To install the whitelist certificate, go to transaction ACF_WHITELIST_SETUP and choose Install Certificate.
- An administrator can specify that the whitelist that is required for security reasons is installed automatically. It is then no longer necessary for each user to install the whitelist locally. The whitelist is transferred signed and decrypted. The administrator only has to store the decryption key in the system. The key can be distributed in the system environment using the SAP GUI installation.
- For more information, see Customizing for SAP NetWeaver under Application Server -> Web Dynpro ABAP -> Set Up Whitelist for Active Controls and Activate Whitelist for Active Controls.
- Import and export from or to MS Project is only supported when either Internet Explorer or NWBC for Desktop (with Browser rendering from Internet Explorer) are used. It is not supported for Firefox, for example. For supported browsers, see SAP Note 1402912.
- The Web Dynpro ABAP OfficeControl uses an ActiveX that does not access any resources on the front end, other than via the MS Project application. The ActiveX is digitally signed with the official SAP signature. With the intact official signature, SAP guarantees that the ActiveX, as provided, has not been changed or modified in any way.
- The ActiveX must be installed once only, the first time you use the integration of Microsoft Project. This occurs automatically in the Internet Explorer. Subsequent calls to the integration then reuse the installed ActiveX. However, you can activate or deactivate the download and execution of ActiveX components in the standard Internet Explorer browser settings (local front-end settings). If you cannot use ActiveX, for example, due to company policy, you cannot use the Microsoft Project integration.
- For more information about OfficeControl, see SAP Help Portal at http://help.sap.com -> SAP NetWeaver -> <release.> -> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> ABAP Technology -> UI Technology -> Web UI Technology -> Web Dynpro ABAP -> Reference User -> Interface Elements.