SAP Cloud For Customer Extension Guide: Public Document Version: 2002 - 2020-05-02
SAP Cloud For Customer Extension Guide: Public Document Version: 2002 - 2020-05-02
SAP Cloud For Customer Extension Guide: Public Document Version: 2002 - 2020-05-02
2 Adaptation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Know your Navigation Shortcuts in Fiori UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Create and Organize Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Create New Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Organize Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Hide Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Create a Query with a Relative Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 Manage the Master Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.4 Manage Page Layouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5 Create Property Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.6 Use Property Rules for Smartphone Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.7 Change UI Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.8 Move Views and Sections Across Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
2.9 View Layout Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3 Extension Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1 Extension Field Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 Create Extension Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Add PSM Fields to Standard OData Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.3 Restrict Personalization for Extension Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.4 Work with Multivalue Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4 Mashups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
4.1 Work with Mashup Authoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Activate Preconfigured Mashups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Create URL Mashups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Create Data Mashups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Create HTML Mashups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Copy Existing Mashups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Delete or Deactivate Mashups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Track Flexibility Change Log for Mashup Authoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2 Create Mashup Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
4.3 Add Mashups on Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.4 Add Mashups as Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.5 Web Service Message Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Important tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
5 Homepage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.1 Scope and Configure the Homepage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.2 Work with Card Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.3 Personalize Your Homepage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
17 Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
17.1 Configure Workflow Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
17.2 Configure Workflow Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
17.3 Configure Messaging Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
17.4 Configure Field Updates using Workflow Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
17.5 Configure E-mail Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Configure Signature Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Set Account and Contact of Source Workflow Object in E-mail Notification. . . . . . . . . . . . . . . . . 121
Code List Descriptions in E-mail Notification Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Track and Manage Bounced E-mails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Configure Employee E-mail Address as Default Sender Address. . . . . . . . . . . . . . . . . . . . . . . . 123
Configure Workflows to Send E-mail Notifications to Active Delegates. . . . . . . . . . . . . . . . . . . . 124
Configure Tracking E-Mail Triggered from Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Configure to Send E-Mail and SMS to Main Recipient Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Attach Business Object Summary as PDF in an Outgoing E-mail. . . . . . . . . . . . . . . . . . . . . . . . 126
17.6 Configure Workflow Follow-Up Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
17.7 Configure Workflow Actions on Business Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
17.8 Design Your Workflows Using Workflow Analysis and System Recommendations. . . . . . . . . . . . . . .129
19 Personalization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
19.1 Personalize your SAP Fiori Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
Customize and extend your solution using personalization, adaptation, field extensions, and SAP Cloud
Applications Studio.
● Adaptation [page 6]
● Personalization [page 147]
● Extension Fields [page 20]
● SAP Cloud Applications Studio [https://help.sap.com/viewer/p/SAP_CLOUD_APPLICATIONS_STUDIO]
As an administrator, you can customize and extend your solution using various tools.
Note that you must first switch on adaptation settings in individual systems. To do this, click your user profile,
and select Settings Adaptation Settings and set the Enable Adaptation toggle button to Yes. Refresh the
browser and you will see a new option under user profile to Start Adaptation.
This document describes all functions that you can accesse as an administrator using the Start Adaptation
menu that you can find under the user profile dropdown list. You can change the look and feel of the SAP
solution for all users, or selected business roles by changing layout settings, adding mashups and fields, as well
as defining extension fields for further usage. You can also determine the client type to be used by all users. The
adaptation changes replace any personalization changes that users have done.
Note
If you don’t see the Start Adaptation option, it is likely that you have the PDI work center assigned to your
role. You must remove the PDI work center assignment to be able to use adaptation.
You can make changes to your system using the navigation shortcuts on the right hand side of your Fiori UI
screen.
Drill Down: Click the drill down icon to navigate further into
the other sections within the header.
Create
Table View
Refresh
Actions
Search
Sort
Advanced Search
Right Click a field Right click a field to directly access the field level configura
tion.
Learn the different ways you can work with queries on each screen.
1. Go to the screen where you want to create a new query. Select the filter icon. Enter the parameters for the
new query. Select Save Query.
2. In the pop-up box, you can give the query a name, and opt to make it your default query.
3. Select Save. A new query is created, and it appears in your default selection drop down list.
Learn how to organize the queries you have created for easy access.
1. Go to the screen where you want to organize your queries. Select the filter icon. Click Organize Queries.
2. In the dialogue box that pops up, you can see all the queries available for the screen. Perform the following
actions:
○ To select a query as your default query, click the radio button next to the name of the query.
○ To remove a query from the list, select the checkbox next to the name of the query.
Note
You can only remove the queries that you have created, and not the once which are pre configured
in the system.
○ To disable object list queries from loading automatically select the Disable checkbox against the query
you do not want to load. When you wish to reload the list, press Click here to execute the query.
3. Select Save. The selected appears as the default query in your default selection drop down list. While the
removed query no longer appears in the list.
1. Click your profile on the top right corner of your screen, and select Start Adaptation. The system opens in
the Adaptation Mode and the section where the changes can be made is highlighted with a red border.
2. In the side pane, click the reverse arrow icon to navigate to the UI Component.
3. Click the Drill down icon next to Implementation. The screen drills down to the child level
4. Click the Drill down icon again next to Queries. The screen moves to the list of queries available.
5. Open the query you want to hide.
6. Select the checkbox next to the Hide field. The query is no longer visible on the screen.
Note
This feature is available for both administrators (master layout only) and business users. Even if an
administrator has set the element to hide, users can override this setting using personalization.
7. To save your settings, click your profile and select End Adaptation.
When you define a query, you can choose a relative date, such as current quarter, and save it with a name of
your choice, such as My Opportunity - current quarter. You can then publish it for all the business
users.
Make the following layout changes and make them available for all users:
Fields Add, hide, change order, set as mandatory, set as read only,
make visible
1. Go to your user profile, and from the dropdown list select Start Adaptation.
2. Make your changes.
3. When your changes are complete, go to your user profile, and from the dropdown list select End
Adaptation.
Note
● Implicit changes in Adaptation mode, such as list and column sorting, take effect for all users.
● Your changes are saved automatically and take effect immediately.
On the Fiori Client UI, change the properties of a field to mandatory or read-only. Additionally, make a field
visible on a screen.
1. Navigate to the screen where you want to change the properties of fields.
2. Click your profile on the top right corner of your screen, and select Start Adaptation. The system opens in
the Adaptation Mode and the section where the changes can be made is highlighted with a red border.
3. Select the section where the field you want to change, exists. The system shows a list of all the available
fields in the side pane. Each field is accompanied by inline icons for the relevant properties available for the
field. You can change the field properties in one of the following ways:
○ Click the icons to set them to Mandatory, Read-Only, and Visible.
○ If you click any of these icons, it overrides any existing rules for that particular property.
○ You cannot configure rules from inline icons. You must drill down to the field level to set the
rules.
○ If a certain property is not applicable for a particular field, the corresponding property icon is
not shown.
○ If you log in as an administrator, you can no longer see the Hide icon for fields in adaptation
mode. You must drill down to the field level to check or uncheck the Hide settings. Business
users will, however, see the Hide (Eye) icon in personalization mode.
○ In the side pane, click the Drill down icon next to the field that you want to change. The screen drills
down to the child level and you can see the properties available for the field.
Select the checkbox next to the properties. The checkboxes always show the value that you, as an
administrator, have set.
You have the following results:
○ The fields that you have set as Mandatory now have the mandatory indicator (*)
○ The fields that you have set as Read-Only appear grayed out, and do not allow the user to change the
contents.
○ The fields you have set as Visible now appear on the screen.
Note
If a field is set by SAP or Cloud Applications Studio, you cannot override the setting. For example, if a
field on the UI shows the asterisk symbol next to it (*) even though you haven’t set the property, it
means that the field has already been marked as mandatory by SAP or Cloud Applications Studio.
4. To save your settings, click your profile and select End Adaptation.
Note
4. Select the checkbox next to the Hide field. The element (section or field) is hidden from view.
Note
This feature is available for both administrators (master layout only) and business users. Even if an
administrator has set the element to hide, users can override this setting using personalization.
5. To save your settings, click your profile and select End Adaptation.
As an administrator, you can modify the basic search fields in an object list.
The system shows you a standard list of fields that are enabled for basic search by default. You can deselect
fields to make them unavailable for basic search. You can also add new standard fields to be enabled for basic
search.
1. Navigate to the screen where you want to modify the basic search fields.
2. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
3. In the side pane, under Overview, click Add Basic Search Fields . This opens a list of all the fields that
include the standard basic search fields, the additional fields available for you to add to basic search, and
the extension fields already enabled for basic search. The fields that are greyed out are not visible in
advanced search. So you must first add them in advanced search and only then enable them for basic
search. The fields that are checked under the Visible header, are the fields available for you to add to basic
search.
Caution
Selecting more than eight fields for basic search can result in poor search performance and this would
vary across various screens.
4. Select the checkbox against the fields that you want to add, and click Apply. The selected settings are
applied to the field.
5. To save your settings, click your profile and select End Adaptation.
Note
● You can also add PSM fields in advanced search and then add the same in basic search as well.
● Extension fields are enabled for basic search by default if they are part of advanced search.
As an administrator, you can manage page layouts specific to certain users or instances.
1. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
2. In the side pane, click Layouts and then click New to open the New Layout quick create dialog box.
1. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
2. In the side pane, click Layouts and then select the relevant page layout that you wish to make changes to.
3. Click to open the Edit Name dialog box.
4. Rename your page layout and click Apply.
5. When your changes are complete, go to your user profile, and from the dropdown list select End
Adaptation.
Note
While editing a page layout, if you change the label of a field, the system applies the change to the master
layout. Only property changes to a field such as making it visible, mandatory, or read-only, while editing a
page layout is considered as a page layout adaptation.
As an administrator, you can assign page layouts to specific business users or instances. The changes that are
made in the page layouts only apply to the assigned roles or instances.
1. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
2. In the side pane, click Layouts and then select the relevant page layout that you wish to assign.
3. Click Assign Layouts to open a new dialog box.
4. Select the relevant Business Object from the dropdown.
Note
The system only displays the business objects related to fields whose property has been changed
within that particular page layout.
5. Based on the selected business object, select the relevant Instance Type.
The system generates certain business roles and instances against which you can assign the relevant page
layouts.
Note
It is not mandatory to select the Instance Type. The system generates data with just the Business
Object selection.
Note
We recommend that you use page layouts only to simplify the layout. If you want to enforce
restrictions, use the Access Restriction feature.
8. When your changes are complete, go to your user profile, and from the dropdown list select End
Adaptation.
Delete page layouts along with all the changes or adaptations made as part of the page layout.
1. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
2. In the side pane, click Layouts and then select the relevant page layout that you wish to delete.
You can rearrange sections and adjust their column and row spans.
You can adjust the master layout for an item details screen so that the sections within a tab are arranged in the
order you like. You can also manage the white space by adjusting the column and row span individual sections
use.
Example
For example, on the Overview tab of an account, you can select the Account Team section and drag it to the top
left. The other sections are pushed down or moved over. Now if you remove the section to the right of Account
Team, you'll be left with an empty space; so you can adjust the Account Team section to span two columns
rather than one.
1. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
2. In the side pane, click Layouts and from the dropdown menu, select the layout that you want to copy.
3. Click (Copy icon) to open the Copy Layout quick create dialog box. .
4. Enter a name in the New Layout box and click Save.
5. When your changes are complete, go to your user profile, and from the dropdown list select End
Adaptation.
Note
● All changes made by the administrator for a particular layout are copied to the new layout.
● Copied page layouts are not linked to the source and are independent.
● Assignments are not copied. You must configure the assignments manually.
3. In the side pane, click the reverse arrow icon to navigate to the UI Component.
4. Click the Drill Down icon next to Implementation, and under Rules and Validations, click Add Rule
to open a new window.
5. Enter a Rule Name and a Rule Description.
6. In the middle pane, write the code for a particular business case. For example, you can write a code where,
for opportunities with value greater than 20 million, the Executive Sponsor Name field is mandatory.
You have the following sections in the screen:
○ Field Names: Here, the system displays all the technical names for all the fields available on that
screen. If you select a field, you can see the actual value of the field in the gray box directly below. For
example, if it’s a code list, or a multivalue list, the system displays the current value in the UI that is
already open. Use this value to create your condition.
○ Code: In this section, you can create the conditions for your rule.
○ Operations/Functions: This section gives you a list of all the functions and operations that you need to
create your condition.
Functions
DAY Returns the day component of a date (if the date is Octo
ber 28, 2016, the system returns 28).
YEAR Returns the year component of a date (if the date is Octo
ber 28, 2016, the system returns 2016).
AND Output is a Boolean value; TRUE if all values are true, and
FALSE if one or more values are false
TRIM Removes the spaces and tabs from the beginning and end
of a text string.
7. Click Apply.
8. When your changes are complete, go to your user profile, and from the dropdown list select End
Adaptation.
Unassign Rules
If you want to unassign a rule for a particular field, select the rule, select an empty rule name and click Apply.
This ensures that the rule is unassigned to that particular field but is still valid for all the fields that it was
previously assigned to. You can continue to use it in the future.
Edit Rules
To edit a rule, navigate to the rule using Implementation Rules and Validations and click Edit. Make your
changes and click Apply. Note that the new rule is applied to all the fields to which the rule is applied.
If you want to delete a rule, go to any field in which the rule is assigned. Select the rule, and then select the
3. In the side pane, click the reverse arrow icon to navigate to the UI Component.
4. Click the Drill Down icon next to Implementation, and under Rules and Validations, click Add Rule
to open a new window.
5. Enter a Rule Name and a Rule Description.
6. Go to Functions Special Functions and click DEVICETYPE.
7. In the middle section of the screen, the system auto populates the special function that you have chosen.
Double click it to make it editable and write the code for a particular business case. For example, to make
screen elements visible on smartphones, you can enter the following description:
DEVICETYPE()==”PHONE”.
8. Click Apply.
9. Go to the section or field level and apply this rule.
10. When your changes are complete, go to your user profile, and from the dropdown list select End
Adaptation.
The section or field becomes visible only in case of mobile phones and is hidden for desktop/tablet.
Note
Move views and sections across tabs in an object details screen. Adaptations made on the views also move
across the tabs.
After the move, the view is no longer available on the source tab.
1. Navigate to the tab from where you want to move a view or section.
2. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
3. Select the view or section that you want to move. The system highlights it in a red border.
4. In the side pane, click the reverse arrow icon to navigate to the Pane and click Move.
5. In the pop-up window, select a new tab from the dropdown and click Apply.
The section now appears on the target tab and is no longer available in the source tab.
6. To save your changes, go to your user profile, and from the dropdown list select End Adaptation.
As an administrator, you can view layout changes that have been made in your system. The changes include
details, such as, the type of change, the user who created it, the date on which it was created.
Procedure
Additionally, you have the option of grouping your change history based on either UI Component or Layout
by selecting the Sort icon.
If you are unable to view certain changes made to your solution on your user interface, you can generate
the implementation of these changes manually. Select the line item with the relevant change details, and
click Generate Load.
Extension fields are additional fields that administrators can add to a cloud solution from SAP.
Administrators can create extension fields for a screen that has been enabled for extension fields. The field can
then be added to other screens, form templates, analytical data sources and reports, and so on.
Note
To create extension fields, you must be assigned to the Flexibility Change Log view in the Administrator work
center.
Business Context
When you first create an extension field, you navigate to a screen on which you want it to appear and add it to a
section of the screen. Each screen section is based on an underlying business context. The business context
typically corresponds to part of a business document or other object, for example, the header data of a sales
order. The business context is used to determine which other screens you can add the field to and, in addition,
the form templates, analytical data sources and reports, enterprise search categories, and extension scenarios
that the field can be added to.
The following table lists the different field types available and the settings you can make for each field type. For
example, you can define a default value that is automatically entered in the field but which can be overwritten
by the user. For some field types you can also define a calculation rule, for example, in order to combine data
from two different fields into one field.
Field Type Default Value Calculated Field Character Limit Other Settings
Text Yes Yes ● Short Text - You can choose the follow
40 ing text types based on your
● Medium requirement:
Text - 80
● Short Text
● Long Text -
● Medium Text
120
● Long Text
● Extended
● Extended Text
Text - 0
(String)
Amount Yes: Default value and de Yes 31 (28 and 3 for None
fault currency currency code)
Decimal Number Yes Yes 31 (including You can specify the field
decimal places) length and the number of
decimal places.
Quantity Yes: Default quantity and Yes 34 (31 and 3 for None
default unit of measure unit code)
Note
● You cannot use
these extension
fields offline.
● Only a limited
number of stand
ard object types
are supported.
● Edit field function
ality is not availa
ble for these fields.
So you cannot add
the fields to Enter
prise search,
OData Service,
Scenarios etc.
● You cannot use
these fields in
ABSL script
( via .ref file)
● You cannot set the
default values for
these fields.
● You cannot add
these fields to ob
ject work list UI
(List columns, ad
vanced search list
and basic search)
Note
○ If you select the field type as Text, the system populates the Sub Type field. Select the available
sub types based on whether you want a long, medium, short, or extended text.
○ If you select the field type as Decimel Number, the system populates the Decimel Places and
Length fields. You can specify the field length and a maximum of 31 characters including the
decimal places.
○ If you select the field type as List or Multivalued List, the system gives you an option to define a
list of values that can later be selected from the dropdown list by users.
6. Mark the data protection and privacy level of the field, if required. You can mark the field as one of the
following:
○ Personal Data: If you select this option, the following happens:
○ The content of the field is destroyed when the corresponding business object instance is
removed using the data removal process
Note
○ You can mark the data protection level of a field only for Business Partner extensions.
○ You can create a maximum of five sensitive personal data fields. You can define an additional
five fields per solution using the Cloud Applications Studio.
○ You cannot add sensitive personal data fields to object work lists, value selections, enterprise
search, or extension scenarios.
○ You cannot use sensitive personal data fields as placeholders in workflow rules.
○ If the field that you have marked as sensitive personal is part of a field group that is already
active, the system takes one day to start reading the access log for the same. To start read
access logging immediately, activate or deactivate the corresponding field group.
1. Click your profile on the top right corner of your screen, and select Start Adaptation.
2. Navigate to the screen where the PSM field exists and click to select the relevant section. The system
highlights the section with a red box.
3. In the side pane, click next to Header to see the list of available fields.
4. Navigate to the PSM field and click next to it. The system highlights the PSM field with a red box to
indicate that it is editable.
5. Click Edit. The system displays the table with the list of available OData extensions.
6. Click the Edit icon and the Action column appears in the table.
7. Under Action, click the Add Field icon next to the OData Service where you want to add the PSM field.
The system indicates that it has been added with a check sign in the Field Added column.
8. Click Save.
Note
1. These changes are not included in the adaptation changes transport. You must create the same fields
in the production/other systems.
2. You cannot remove a PSM field from an OData service if it is already shipped as part of standard OData
service by SAP.
3. This feature is not available for the Lead UIs, such as Lead, Lean Lead, and Deal Registration UIs.
As an administrator you can decide the fields, sections, panes, and tabs that the users can personalize.
When you add new fields, sections, panes, or tabs, select the Personalize checkbox to make them available for
business user personalization. If you deselect the checkbox, the items are no longer available for the user. You
can also add extension fields that are not yet added to the UI.
When the user is in personalize mode, they can see only those items marked by the administrator. All the
existing fields added by the users remain unaffected. If they want to use any additional content, they must
contact their administrator to enable the fields, sections, panes, and tabs for personalization.
As an administrator, you can create extension fields of type Multivalue List. This allows you to select multiple
values from the drop down option of that particular field. You can also search with multiple values in the
advanced filter option.
This document shows how to work with a multivalue list. To do that, follow the steps below:
1. Open an instance of a business object where you want to add an extension field. For example, an Employee,
Lead, Customer.
2. Select an area, for example, the overview area, header area, and so on, where you would like to add the
extension.
3. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
1. Go to the object, and click on the newly added extension field, in this example, Employee > Sports. The
system displays the values that you added earlier.
2. Select one or more values (for example, Football, Tennis) from the multivalued dropdown list and click
Save.
Note
To edit or maintain values, please add the extension field through the business object and Quick Create.
Add the extension field to the Advanced Filter section of the Object Work
List (OWL)
Note
To use it as a filter parameter, add it under the advanced query of the OWL. To view it as read-only, add it
under quick view or OWL.
1. Click on the Show Advanced Filter icon. The system displays the new field, Sports, in this example.
2. Click on the drop down to see the values. Select the values that you require, for example, Football, Tennis,
and click Go.
The system displays all the employee records that have listed Football or Tennis under Sports.
Mashups are used to integrate data from SAP's cloud solution with data provided by an online Web service or
application. Users can access the content provided by these Web services and applications, and use it in their
daily work. Mashups can include Web searches, company or industry business information, or online map
searches.
Prerequisites
● You have enabled Communities, Document Management and External Services in your system
configuration. To find this business option, go to the Business Configuration work center and choose the
Implementation Projects view. Select your implementation project and click Edit Project Scope. In the
Scoping step of the project, ensure that People Collaboration, Intranet and External Services is selected
within Communication and Information Exchange.
● In the Questions step, expand the Communication and Information Exchange scoping element and select
People Collaboration, Intranet and External Services. Select Communities, Document Management and
External Services and answer the question related to Mashups, Web Services, and External Search Providers
Integration.
● Before a mashup can be used, it must be activated by an administrator. This administrator must have
authorization for the Mashup Authoring and Mashup Web Services work center views.
Note
Some mashups may not be applicable to your country. Your administrator should ensure that the mashup
is valid for your country before activating it for company-wide usage.
The following preconfigured mashups for Web services are provided in SAP Cloud for Customer:
Preconfigured Mashups
Relevant For Mashup Name Mashup Type Mashup Category Port Binding
Sales & Social SAP (sap.com) URL Mashup News & Reference Search Provider
Sales & Social Embedded Map (bing.com) Custom Mashup Location & Travel Web Map
Sales & Social Embedded Route (bing.com) Custom Mashup Location & Travel Route Planner
Sales Sales Intelligence for Ac HTML Mashup Business & Finance InsideView Account In
counts (insideview.com) formation
Sales Sales Intelligence for Con HTML Mashup Business & Finance InsideView Contact In
tacts (insideview.com) formation
Social Tweets by Handle Data Mashup Business & Finance Additional Account In
formation
In addition, the following preconfigured mashup Web services are provided, which the administrator can use to
create mashups:
Relevant For Mashup Web Service Service ID Web Service Type Service Domain
Name
As an administrator, you can create new URL, HTML, or data mashups based on a mashup category provided
by SAP. Depending on your solution, preconfigured mashup Web services are provided, which you can use to
create data and HTML mashups. To display them, go to Administrator Mashup Web Services .
Once a mashup has been activated and made visible on screens, you can access it in the following ways:
● URL Mashups
A mashup that sends data from SAP's cloud solution to the URL of an online service provider. The service
provider uses the data, for example, to perform a search, and the results are displayed in a new browser
window.
● HTML Mashups
A mashup that embeds an HTML or JavaScript based Web page directly on a screen.
● Data Mashups
A mashup combines and displays data from both internal and external sources. To create a data mashup,
an integrated authoring tool is used to transform or merge external Web services with internal business
data using industry-standard Web service protocols.
● Custom Mashups
A mashup that has been created as an add-on solution by SAP.
Administrators can create new data, URL, and HTML mashups. Custom mashups can be created only by SAP.
● Mashup Categories
Mashups are grouped together into categories according to the type of service or information that they
provide.
● Port Binding
Certain fields on screens are predefined as screen out-ports and in-ports. These screen out-ports and in-
ports are grouped together as a port binding.
The port binding defines the type of information that can be used in the mashup and defines on which
screens you can use the mashup. The mashup category specifies which port bindings are available.
● API Keys
Some Web services require a unique API key to allow you to access their services. You can generate a
companyspecific API key on the service provider's Web site and then use this key to authenticate access
to the service from SAP's cloud solution.
You can identify which mashups require an API key by the icon displayed in the API Keys column. The Enter
API Keys dialog box displays the API keys that are required by the selected mashup.
● Basic Authentication
Basic authentication allows you to enter a user name and password for authenticating access to a Web
service. This user name and password is then used to automatically authenticate all other users accessing
the service.
● Secure Authentication
For Web services that support the OAuth authentication protocol, you can set up secure authentication.
The OAuth protocol enables secure, user-based access to Web services from SAP's cloud solution. Unlike
other authentication methods, OAuth gives the user full control of his or her own authentication details. To
use a mashup based on an OAuth authenticated Web service, users need to authenticate themselves on
the service provider's web site, where they are given a unique PIN code. This PIN code is then used to
authenticate access to the service from SAP's cloud solution.
● Centrally
Navigate to Administrator Mashup Authoring
● On a particular screen
Use the Adapt function on any screen enabled for mashups to access the adaptation sidecar.
Activate preconfigured mashups, and create new mashups either from scratch or by copying a preconfigured
mashup.
After a mashup has been activated, it can be made visible on the screens for which it is configured. The
administrator does this centrally for all users via adaptation. For more information, see Add Mashups on
Screens [page 47].
Note
If a mashup is not activated, the administrator can edit and activate it at a later date from the Mashup
Authoring view.
Depending on your cloud solution, preconfigured mashups are provided that give access to services and
content provided by third-party service providers. As an administrator, you can activate these preconfigured
mashups and make them visible on selected screens.
Note
Some Web services may pass your business data to a third-party organization, for example, account data is
passed to a search engine when performing a reverse lookup in an online address book. We recommend
that you check whether the mashup conforms to your company’s data privacy policies before activating the
mashup.
Note
Certain Web services require API keys. If a mashup uses such a Web service, ensure that this Web service
has been activated and that you have entered the required API keys for it. You can do this on the Mashup
Web Services view.
The SAP-Google Maps partnership allows SAP to offer Google Maps within our application using the API
key provided by SAP from Google. SAP has essentially pre-paid for Google Maps usage by our customers
during this partnership. This partnership will expire at the end of 2014, and if it is not renewed, the SAP-
provided API key will expire, and our customers will need to get an API key directly from Google.
Note
The solution renders all custom mashup in an iframe. Some custom mashups are not designed to be
rendered in an iframe, which is a limitation of the selected mashup.
As the solution cannot determine whether a custom mashup will be rendered in iframe or not, you will see
all the custom mashups in the list of available mashups.
To check if the mashup can be rendered correctly, use preview option in the mashup authoring tool. If there
is an error, the selected mashup will not work with the solution.
As an administrator, you can activate a mashup partner solution in your SAP cloud solution.
Prerequisites
You have procured a mashup partner solution from the SAP Store at https://store.sap.com.
Procedure
1. In the Mashup Web Services view, check that any Web services belonging to the mashup partner solution
are activated and that API keys have been maintained.
2. In the Mashup Authoring view, check that the mashups belonging to the mashup partner solution are
activated and that any necessary API keys have been maintained.
Note
Note that if the mashup partner solution contains multiple mashups and you only want one of these to
be available to business users, you can deactivate the unwanted mashups in the Mashup Authoring
view by selecting the mashup and clicking Deactivate.
Create URL mashups to send data from your cloud solution to a URL of a Web service provider. The results are
displayed on the Web service provider’s Web site, which is opened in a new browser window.
Note
Some Web services may pass your business data to a third-party organization, for example, account data is
passed to a search engine when performing a reverse lookup in an online address book. We recommend
that you check whether the mashup conforms to your company’s data privacy policies before activating the
mashup.
Prerequisites
You know the end-point URL of the Web site providing the service. This could be, for example, the search results
page of an online search provider.
Procedure
Go to Administrator Mashup Authoring . Click New URL Mashup , and follow these steps:
Note
By default, the status of mashup is Inactive. This means it will not be available for use when saved.
If you want users to access the mashup immediately, change the status to Active.
2. Under URL Information, enter the URL of the Web service and click Extract Parameters.
The URL can be taken directly, for example, from the search results Web page of an online search provider.
Copy and paste this URL directly into the field. The system then extracts all parameters from the URL and
displays them in the table.
Note
Note that for URLs that do not use queries you can manually add curly brackets around terms that
should act as placeholders. For example, in the URL https://mail.google.com/mail/#search/
SAP, you can replace the word SAP with a search term in curly brackets, for example, {term}.
Create data mashups for integrating data provided by third-party Web services with business data from your
SAP cloud solution.
Note
Some Web services may pass your business data to a third-party organization, for example, account data is
passed to a search engine when performing a reverse lookup in an online address book. We recommend
that you check whether the mashup conforms to your company’s data privacy policies before activating the
mashup.
Prerequisites
Web services that you have integrated for use in data mashups must use the XML service protocol. You have
either integrated a new Web service or have decided to base your mashup on one or more of the preconfigured
Web services provided by SAP or partners.
You can display a list of available Web services in Administrator Mashup Web Services .
Go to Administrator Mashup Authoring . Click New Data Mashup , and and follow these steps:
1. Under General Information, enter a name and a description for the mashup.
The mashup name is displayed to business users when using the mashup.
Note
By default, the status of mashup is Inactive. This means it will not be available for use when saved. If
you want users to access the mashup immediately, change the status to Active.
2. Under Binding, select the port binding type. The port binding defines which screen out-ports or in-ports
can be used in the mashup and on which screens the mashup can be used.
○ If you select With Port Binding, click the value help to choose a port binding from the available list.
○ If you select Without Port Binding, choose a mashup category from the dropdown. The mashup
category is used to group mashups by the type of information they provide. It is shown to business
users when they personalize mashups in the side pane.
3. Click Next.
4. On the Define Mashup Details step, create the mashup by adding building blocks and adjusting the
properties. First, define the source of input for the mashup. You have the following options:
User Inputs
User inputs allow you to define a field in which a user can enter or select a value. This value is then used as
input for the mashup. To add a user input to the mashup, click +User Input. Click the block title to edit its
properties in the pop-out window.
User Inputs
Text Input Allows users to enter a string of characters as input for the mashup.
Number Input Allows users to enter a number as input for the mashup.
Select Option Input Allows users to select an option from a dropdown list as input for the mashup.
In the Label field, enter the field label that should be shown to users for this input field. You can enter a
name in the Name field. This can then be mapped to an input parameter, for example, in a search service.
For text and number inputs you can also define a default Value, which can then be overwritten by other
users. If you have selected a Select Option Input building block, click the button next to List Options to
define the list of options that the user can choose from.
Services
Select the services you want to integrate into the mashup. Click +Service to choose the service source.
Click the block title to edit its properties in the pop-out window. You have the following options:
Data Sources
CSV Data Source Use a CSV file as input for the mashup. You can choose to either upload a file or reference an
online CSV file.
Click the block title to open a pop-out window and select your file.
XML Data Source Use an XML file as input for the mashup.
To preview the mashup results you may have to manually add a value to the input field of the mashup in-
port or user input. To do this click the block title and under properties, enter a value. In the runtime version,
these values will be replaced automatically by either the parameter taken from the screen out-port or by
the user entering their own value.
Note
If you are using a service that uses the authentication method OAuth, then you will need to log on to the
service and generate a PIN code in order to preview the service results. Afterwards when users are
accessing the mashup, they will be prompted to create their own PIN code.
Actions
Actions allow you to transform the content retrieved by the Web services. Click +Actions to choose one of
the following options:
Actions
Filter Data Filter the items returned by the service. You can create rules based on the parameters pro
vided by the service.
Sort Data Sort the display order of items in the results based on the parameters provided by the service.
Truncate Data Truncate the number of items displayed in a feed after a given number.
Merge Data Mashup WebMerge multiple feeds to display in a common results list. You can use this action
to combine data from two sources that have the same format into a single results list.
Join Data Join two data sources based on conditional rules to form a new data source. You can use this
action to combine data from two sources that do not have the same format.
Add Field Add one or more fields available in the parameters returned by the service to the results.
Extract Field Extract a specific piece of information from the results, for example to use as input for another
service within the same mashup.
Replace Text Replace a specific piece of text in the results with a different text.
Convert Text Convert text based on conditional rules. For example, by applying formatting to the text.
Concatenate Text Concatenate text in the results. For example, you can use this action to concatenate two pa
rameters in the search results to display in the same field.
Arithmetic Operation Perform an arithmetic operation with the results based on operation rules.
Output Parameters
For mashup categories that allow the results data returned by the service to be integrated back into the
screen, click +Output Parameters to add a Mashup Out-Port building block to the mashup.
Adjust the display settings of the mashup results.
By default, the results are displayed in a table format. Click Edit Display Settings and select one or more
formats in which the mashup will be made available to all users. You must specify a default display option.
For each display option you can also configure additional display properties, such as the maximum number
of items that should be displayed. Note that the XML view is provided for your information while creating
the mashup but will not be shown to other users.
If required, you can also change the default refresh settings that are used to determine when the Web
service used in the mashup is called. You have the following options:
○ Refresh on Mashup Loaded: Deselect this checkbox if you do not want the Web service to be called
when the mashup is loaded for the first time.
○ Refresh on In-Port Data Changed: Deselect this checkbox if you do not want the Web service to be
called when the user changes the in-port value.
These options can be used if, for example, your mashup involves complex services such as calculations or
uses a paid service such as an SMS sending service that should only be triggered manually.
5. On the Review step, you can view how the mashup will be displayed to users. Review your settings and click
Confirm to create the mashup.
Create HTML mashups to embed an HTML or JavaScript based Web page into a screen of your SAP cloud
solution.
Note
Some Web services may pass your business data to a third-party organization, for example, account data is
passed to a search engine when performing a reverse lookup in an online address book. We recommend
that you check whether the mashup conforms to your company’s data privacy policies before activating the
mashup.
Prerequisites
You know the URL of the Web site that you want to embed.
Go to Administrator Mashup Authoring . Click New HTML Mashup , and and follow these steps:
Note
By default, the status of mashup is Inactive. This means it will not be available for use when saved.
If you want users to access the mashup immediately, change the status to Active.
Note
For URLs that do not use queries you can manually add curly brackets around terms that
should act as placeholders. For example, in the URL https://mail.google.com/mail/
#search/SAP, you can replace the word SAP with a search term in curly brackets, for
example, {term}. If you then enter https://mail.google.com/mail/#search/
{term} in the URL field and click Extract Parameters, the word in brackets is extracted as
a parameter.
Note
To assist you in coding HTML Mashups, some example APIs are documented here:
Example APIs for HTML Mashups [page 40].
Note
If you change the code, you need to click Preview again to display the updated result of the
mashup.
○ Adjust the display height, as required. The default height is 200 pixels.
3. Save your changes.
This document provides some example APIs to help you to code HTML mashups.
Method
sap.byd.ui.mashup.callService(serviceOptions)
Usage
When you click Add REST Service in the toolbar of the editor, the code template of this API is inserted
automatically.
Parameters
Example
sap.byd.ui.mashup.callService({
serviceId: 'CW00001'
parameter: {'query': 'SAP',},
onComplete: 'serviceCallback_CW00001',
onError: 'exceptionHandler_CW00001'
});
Method
sap.byd.ui.mashup.onContextUpdate()
Usage
If a port binding is assigned in the mashup, all the context parameters from out-port of the application and the
predefined system parameters are displayed in the Input Parameters table. If you select an input parameter
and click Copy, the system automatically copies the parameter in the selected row as a code string to the first
line of the editor. You can then move this code string to the required location in the code.
After you have finished entering the code and clicked Preview to preview the results of the mashup, you can test
the onContextUpdate API. Enter sample values for the input parameters and then click Update Parameter
Values.
Parameters
The context can be accessed via sap.byd.ui.mashup.context, which is a JSON object with the following objects:
● In-port
if the mashup defines port binding, the values from the corresponding application out-port can be
accessed by using inport.ParameterName.
● System
Mashup system parameters
Parameter Description
Example
sap.byd.ui.mashup.onContextUpdate = function() {
Method
sap.byd.ui.mashup.fireResultUpdate(resultObject)
Usage
To consume this API, a writeback port binding (for example, Reverse Lookup) should be specified in the
mashup. The Output Parameters table contains the parameters used to write back data to the corresponding
application in-port. Click Copy to copy the corresponding parameter of the selected row to the editor. Using
this API method, the preview values are filled with the values from the HTML application.
Parameters
resultObject is a JSON object which reflects the corresponding in-port of the application UI.
Example
Create a copy of a mashup delivered by SAP or partners. This enables you to adapt preconfigured mashups or
to create your own mashup based on the configuration settings of an existing mashup.
1. In the Mashups Authoring view, select the mashup you want to copy by clicking on the mashup name.
2. On the mashup details screen, click Copy.
Delete or deactivate mashups that you and other users have created.
The Flexibility Change Log view contains all changes that have been made by administrators in adaptation
mode and in the Mashup Authoring view regardless of the version you are using. This includes changes to
screens, extension fields, and mashups. This view allows administrators and auditors to trace the way in which
data is being accessed by users. For example, by creating calculated extension fields and mashups,
administrators can grant users access to data that they were not originally authorized to access. You can
access this view from the Administrator work center.
You can use this view to track and manage changes to objects. By default, the list of changed objects displays
all objects that have been changed by you. You can view changes made by others by selecting an option from
the Show dropdown menu. In the Status of Changes column, you can see whether the object contains any
changes that have not been published. You can then decide whether to publish or discard all changes to the
object. For each changed object you can also view the change history which is a detailed log of each change
that has been made.
To help you keep track of why changes were made, you can add a tags to the individual changes in an object's
change history.
You can add tags to individual changes in the change history of an object. This helps you keep track of why you
made your changes, for example, if you made the change in the context of a scope change project.
1. In the Flexibility Change Log screen, select a changed object and click Change History.
The Change History screen opens displaying a list of all changes that have been made to the object.
2. On the Change History screen, select a row in the table and enter a text in the Tag column.
We recommend that you use one or more key words related to why you have made this change. If you enter
multiple tags for different changes, these are listed for the changed object on the Flexibility Change Log
screen.
You can publish changes that have been made to an object but which have not yet been published.
1. In the Flexibility Change Log screen, select a changed object that contains not published changes.
2. Click Publish.
The changes are made visible to other users.
You can discard a single change to an object if it has not been published.
1. In the Flexibility Change Log screen, select a changed object and click Change History.
2. On the Change History screen, select a row in the table and click Discard.
The administrator change is deleted from the object.
All administrator changes are deleted from the object and it is restored to its original state.
You can export a detailed list of all changed objects containing all changes that were made to each object. Note
that to use this function, you must install the add-In for Microsoft Excel® on your local computer.
Create mashup web services to integrate third-party services with your solution.
As an administrator, you can create mashup web services to integrate third-party web services with SAP Cloud
for Customer and use them in data or HTML mashups. You can integrate the following types of web services:
● RSS/Atom
● REST
● SOAP
Prerequisites
● For RSS or Atom feeds, you know the end-point URL of the Web service or the WSDL location.
● For REST Web services, you need to know the request URL as well as any relevant parameters.
● For SOAP Web services, you need to know the WSDL location (URL).
Typically, you can find this information on the Web site of the service provider.
Procedure
Navigate to Administrator Mashup Web Services . Click New, select the type of web service you want to
create, and follow these steps:
Note
You can only use the OAuth standard to authenticate users accessing the service if OAuth is
supported by the provider. You can find all of the information required on the Web site of the
provider.
2. Enter the URL of the RSS or Atom feed and click Extract Parameters.
Note
For URLs that do not use queries you can manually add curly brackets around terms that should act as
placeholders. For example, in the URL https://mail.google.com/mail/#search/SAP, you can
replace the word SAP with a search term in curly brackets, for example, {term}. If you then enter
https://mail.google.com/mail/#search/{term} in the URL field and click Extract Parameters,
the word in brackets is extracted as a parameter.
REST
1. On the REST Service screen, under Service Information, select an authorization method, if required.
Note
You can only use the OAuth standard to authenticate users accessing the service if OAuth is
supported by the provider. You can find all of the information required on the Web site of the
provider.
Note
For URLs that do not use queries you can manually add curly brackets around terms that
should act as placeholders. For more information, see the related note in the RSS or Atom
Feed section.
Note
You can also use curly brackets to define parameters in POST XML bodies. For example, you
can replace a value returned by the REST service with a placeholder, for example
{placeholder}, which can then be mapped to a screen out port in a mashup.
SOAP
1. On the SOAP Service screen, under Service Information, enter the WSDL URL and click Import.
The system extracts the WSDL content.
Note
The following restrictions apply when creating SOAP-based web services: the XSD extensions
union, list, and restriction are not supported; it is not possible to use header messages, imports in
WSDLs, and maximum or minimum occurrence indicators; the XSD complex type structure is
always handled as a sequence; for WSDLs containing more than one service, multiple ports with
the same name are not supported; and SOAP 2.0 is not supported.
As an administrator, you can add a mashup to a screen and make it visible to all users. Each mashup can be
added to a predefined set of screens based on the mashup category and port binding.
Tip
Alternatively, if you do not want to make a mashup visible to all users who have access to a screen, then
individual users can add the mashups by going to Personalize Start Personalization . This means that
only users who have personalized the screen will be able to use it.
Prerequisite
Procedure
1. Navigate to the screen on which you want to make the mashup available to all users.
2. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
3. Click the blue icon on a header, section, or tab and the system highlights the area with a red border
to indicate that changes can be made. In the side pane, click the reverse arrow icon to navigate to the
UI Component.
4. If you are adding a URL mashup, in the side pane, click the Drill down icon next to Section. The screen
drills down to the child level.
If you are adding a HTML or Data mashusp, in the side pane, use the back arrow and click the Drill down
icon next to Header. The screen drills down to the child level.
5. Click Add Mashup to open a new window.
6. Select the row that contains the required mashup to display the Properties header.
7. Select the checkbox against the same mashup to make the properties editable.
8. If required, you can adjust the appearance of the mashup by selecting one of the following options under
Properties.
Note
○ Appearance
○ New Screen Section: The mashup is embedded directly into the screen as a new section.
○ Link: The mashup is embedded into the screen as a link. This is available for URL mashups only.
○ Select the Full Width checkbox if you want the mashup to take up the full width of the screen.
○ Select the Show Pane Header checkbox if you want to see the mashup title on the screen.
○ Height(%)
You can define the height of HTML Mashups to be displayed in the available screen. For example, if you
set the value of Height(%) to 100, the newly added mashup will occupy the full height of the screen.
9. If the Input Binding or Output Binding section is displayed, select the extension fields that should be
mapped to the parameters.
10. Click Apply.
11. To save your settings, click your profile and select End Adaptation.
Note
We recommend that you do not add more than one mashup on a screen. This can cause delays and affect
performance.
It is a two step process where you first create a tab and then embed a mashup to the tab.
Using page layouts and visibility property you can control who is allowed to use the mashup.
The Web Service Message Monitoring view allows you to monitor and process asynchronous incoming and
outgoing messages. You can also view inbound groupware messages and messages based on A2X traces of
groupware calls.
When you scope the Web Service Message Monitor, a job is scheduled, which checks for incoming and
outgoing messages every 15 minutes. Completed messages are automatically deleted at specific intervals:
● Successful and canceled, asynchronous, inbound and outbound messages are deleted every 42 days.
● Successful and erroneous, synchronous, inbound and outbound messages are deleted every 30 days.
● Canceled, synchronous, inbound and outbound messages are deleted 48 hours after cancellation.
Caution
The Web Service Message Monitor is intended for technically skilled persons with in-depth knowledge of
SOA technology.
Caution
If you activate this function in Business Configuration, the person running the Web Service Message
Monitor can access messages that may contain confidential data. For example, payroll and business
partner data.
● Read Access Logging – for security purposes, you can view a record of each payload access instance
Restart Messages
You can restart messages that can't be processed due to temporary issues, for example, locked data, missing
master data, or configuration data. Select messages, or click the filter icon to filter the message list. To restart
message communication after you have corrected the error, click Restart, then choose either Selected, or
Based on filter criteria. If the error cannot be corrected, you can cancel the messages.
Note
Cancel Messages
To stop message processing, select messages manually, or click the filter icon to filter the message list. Click
Cancel, then choose either Selected, or Based on filter criteria.
You can only cancel messages with the status Application Error, System Error, or inbound messages with the
status Waiting. Application errors are due to invalid or missing data, whereas system errors are due to
configuration or integration issues.
You can’t resend a canceled message. A canceled message is permanently canceled. In such a case, a new
transmission must be initiated.
To check for new messages and update the status of existing messages in the results list, click Refresh. The
solution automatically updates message status in the list at 15 minute intervals.
To view detailed error information for a specific message, select an error message in the results list.
You can navigate to the related task in Business Task Management, if applicable.
The error counter displays the number of errors for which detailed information is available, whereas the retry
counter the number of messages that are automatically restarted.
Download the filtered list of messages in Microsoft Excel format using a template, or a CSV format file that also
includes the remote object ID. To download the message list, proceed as follows:
To view the information sent with the request, or response payload of A2X inbound and outbound services:
To view the child messages of a message that has been split, proceed as follows:
To receive a daily digest message with the statistics of messages for the day – successful, failed, total
messages, proceed as follows:
The solution sends a daily message to the employee e-mail specified for the logged-in user. To cancel the daily
e-mail, choose Unsubscribe.
Trace successful A2X inbound and outbound calls for the next 30 minutes:
● In the Web Service Message Monitoring view, choose Start A2X Trace.
Message Status
Messages processed in SAP Cloud for Customer , can have one of the following status.
Status Description
APPLICATION ERROR A business error has occurred when processing this mes
sage.
Learn how to activate or deactivate several external sources (URL mashups) that are shipped with the solution.
The enterprise search feature can be configured to include external sources. You can also add new external
sources by creating a new URL mashup of the News & Reference category.
Caution
The new URL mashup is now available for selection in the enterprise search drop down list.
Administrators can configure Google Maps or AutoNavi Maps for different accounts.
Note
● The use of the Google Maps Service is subject to Google Terms of Service, which are written in http://
www.google.com/intl/en/policies/terms/ . If you do not accept such Terms of Service, including but
not limited to all limitations and restrictions therein, you may not be able to use Google Maps Service in
SAP Cloud for Customer. The use of Google Maps Service in or through SAP Cloud for Customer
constitutes your acceptance of Google Terms of Service, and it can be terminated by SAP without
reason at any time and SAP is not required to provide an equivalent service via another provider.
As a prerequisite, please create a support ticket to obtain and use the SAP API key for Google Maps.
● The use of AutoNavi Maps Service is subject to AutoNavi Terms of Service, which are written in https://
lbs.amap.com/home/terms/ . If you do not accept such Terms of Service, including but not limited
Enable agents to search for solutions and attach articles to responses without having to leave the workspace by
integrating an external knowledge base.
Overview
By integrating an external knowledge base, you enable agents to search for solutions and attach articles to
responses without having to leave the workspace. The workspace will also include a list of recommended
articles based on an automatic search of the knowledge base using the product and other keywords identified
via text analysis as the search parameters.
Prerequisites
● You have an external knowledge base that supports the OpenSearch standard with an RSS or Atom based
search API.
● You know the URL for the API (from your knowledge base vendor).
● You know the search term input parameter for the API (from your knowledge base vendor).
Note
As part of your scoping activities for your SAP Cloud for Customer implementation project, you need to enable
the Knowledge Base Integration business option. This basically turns on the solution finder feature of the
workspace where your external knowledge base is integrated.
Note
3. Enter the URL of the RSS or Atom feed and click Extract Parameters.
The system extracts any parameters and displays them under Input Parameters.
You can also manually enter the input parameters if you know them.
4. Adjust the input parameter values as required, ensuring that the search term parameter is blank.
Example
For example, if the URL for the RSS or Atom feed for your knowledge base vendor is https://
KBvendor.com/search?q=test, then the system would extract the parameter, q, with the constant,
test. You would need to delete the constant value so it remains blank.
Once you've created the web service for your knowledge base, you need to create a data mashup to specify the
mapping between the search parameters used by the system and the web service input parameters.
Caution
1. The knowledge base web service you created needs to be added as a source for the data mashup.
Click on the Sources tab.
Tip
Depending on the size of your screen, you may have to scroll within the left pane to see the Sources tab.
By default, the Parameters tab is active.
2. Drag and drop the RSS/Atom Services building block onto the central authoring canvas.
3. In the dialog box, select the web service you created for your knowledge base.
4. Using the cursor, draw a connection between the bottom of Mashup In-Port and the top of Fetch Feed boxes
of the new service.
5. With Fetch Feed selected, in the properties pane on the right, select SearchExpression for the search term
parameter.
6. Now with Mashup In-Port selected, in the properties pane on the right, enter a search expression that
you're sure will return results.
7. Click Preview Result.
The results of your search expression are displayed in the result pane.
8. If the results are what you expected, click Next .
If all the information for the mashup is correct and OK, save it by clicking Finish.
Caution
Learn how to configure the URL shortner using an existing web service.
The URL Shortener is used when attaching knowledge base articles to message responses. It is configured
using an existing web service.
Example
Learn how to configure a chat URL generator using an existing mashup web service.
Overview
The chat URL generator enables an agent to send the customer an invitation and link to a chat session. It is
configured using an existing mashup web service.
Note
This mashup web service integrates with a third-party chat solution by SnapEngage. SAP is not responsible
for setup or support. Contact SnapEngage directly if you have questions or issues related to chat
integration.
Prerequisites
Results
Learn how to configure Klout web services for Twitter social media customer profiles and to retrieve the
customers' Klout scores and associated information.
Overview
The Klout web services are used for Twitter social media customer profiles to retrieve the customers' Klout
scores and associated information. There are two existing web services for which you need to maintain the API
keys.
See relevant information and activities, and plan your day with the homepage. And get a high-level visual
overview of your sales data.
Homepage displays preconfigured business cards based on your business role. You can click a card to see its
details. For example, you can click Today's Activities to see the details of your schedule and activities for today.
You can work with the different cards types, view report details, and also personalize the cards you want to see
on the Homepage.
The news section on the homepage helps you prepare for appointments and phone calls, by displaying stories
about the accounts related to your scheduled activities. The shelf card shows Flags and Favorite items. The
Feeds card shows the feed updates. Use the dashboard cards to drill down and view details and increase your
visibility into transactional data, KPIs, and reports. You can also do mark ups, add notes, and send e-mails right
from the homepage.
Homepage content is cached to improve the sign-in experience. Content caching loads the homepage cards
faster and retrieves the homepage content efficiently, keeping the user experience interactive. You can access
the homepage cards with no updates immediately and don't have to wait for the homepage to load completely
before using it. A visual transition shows the information being updated in the background. You can see the
cached information in gray. he cached data is shown immediately and any updates to the homepage cards
automatically occurs in the background. You can see the previous information while the system updates the
cards with latest information. This transition takes no more than 5 to 10 seconds.
Administrators can configure and adapt the homepage for each user and business role.
When you log on as the administrator and go to the home page to manage the make changes, you have two
options- Adapt and Personalize. With Adapt, you first choose the user role and then make changes for that user
role. Personalize allows you to make individual changes that you want for yourself and is also available for every
user to personalize their homepage.
Remember
The administrator can define the home page for each role.
Context
If the administrator does not define a home page for a role, the default home page layout is maintained. To
select a role and start defining the home page for all users with that role, do the following:
Procedure
The administrator can access homepage setting as a gear icon on the homepage.
As an administrator, under homepage settings you can enable the users or roles to group cards on their
homepage. To do so, check the checkbox Show cards in Groups under settings. You can also change the
homepage to show as the default start page when the user logs in. To do so, you can uncheck the checkbox Set
Homepage as the Start Page under settings.
The administrator can define the cards for each role under adapt mode.
Procedure
1. In adapt mode, select a role and the different card types (KPI, custom, report, filter, and tools card) for the
user role.
2. To add cards, click, or tap the+ icon, located at the end of each card. As the administrator you have two
options for adding different cards-
1. Add Existing card: Select the different cards you want for the user or business role from the catalog.
2. Create Custom card: You can create the following type of custom cards:
○ URL
○ Floorplan
○ Ticket Creation
○ URL Mashup
○ HTML Mashup
Note
URL Mashup and HTML Mashup custom cards are only available in Fiori client.
With floorplan card option, you can create a card that launches any screen for a work center or detail
view in the solution that the user wants. Custom card also includes custom screens the user may have
defined.
Do the following steps to create a custom card:
○ Choose the custom card you want to create.
○ Add the required fields and click Save. Custom card created is stored in the card Catalog.
3. If you want the changes, select Publish, and if you do not like the changes you made, select Revert.
4. To go back, select Leave Adaptation Mode .
When you are in adapt mode, you can change the appearance of a card by selecting it. You can set the following
attributes for a card:
● card Visualization
● Available
● Visible
● Specify a group for the card, if grouping is available for the role.
Context
The administrator can configure the news card by either selecting the news source or by selecting the url for
RSS feeds to show up on the user's news card.
The Google News API is deprecated and gives errors on the current news card. See the Related Links for more
information. Therefore, the administrator can set up Bing News for all users and roles as the news card. You can
buy Bing News APIs and enable it in the solution. See the Related Links for more information.
Note
Bing News has different markets based on country and language. Right now, in the solution the market is
preset only to US English for Bing news. This means that the business news is in English and from US.
Depending on what is the user’s current news source, there are two use cases to change the news card to Bing
News-
● If the user currently has Google news set up for the news card.
● If the user currently has URL for RSS Feeds selected for the news card.
Note
If you opted for Bing news or opted for RSS feed or already on RSS feed as new source, switching back to
Google news isn’t possible.
Procedure
1. On the home page, select the edit icon at the bottom-right corner.
2. From the pop-up select Adapt.
3. Select the user role.
4. Select the news card.
5. Select the link Switch to Bing New under Select News Source if Google news is set up as the news card.
Select API Key for Bing News if URL for RSS Feeds is set up as the news card.
6. Enter the API key and Save.
○ If the news source is Bing News, no news is shown on the news card in offline mode.
○ Bing news V7 is supported.
You have five different card types ( KPI, Report, Tools, Filter and Custom card) available in the solution.
Note
● Tools cards
cards like News and My Upcoming Activities are available online only and enhance your daily productivity.
My Tasks card displays the optimized view of your tasks and clicking on the card allows you to quickly
navigate to the Task work center. The number of overdue tasks, if present, are displayed in a red font.
Otherwise, tasks displayed are prioritized by Today, This Week, This Month, or as Open Tasks.
● Filter cards
Filter cards provide quick access to your saved queries. You can select the filter card to go to the saved
query. You see the custom queries as list items on the Filter card. When you select a query, you directly
navigate to the list. Thus, improving the usability and reducing the number of clicks. To see the filter card
on the homepage, ask your administrator to make the card visible for your role.
● Custom cards
Custom cards display an icon, and can be set to launch a floorplan, ticket creation or an external URL. With
floorplan card option, you can create a card that launches any screen for a workcenter or detail view in the
solution that the user wants. This also includes custom screens the user may have defined. Please contact
your administrator if you would like to create any specific custom cards.
Based on the KPIs defined by your administrator, you can launch an interactive dashboard or KPI overview. KPI
cards provide a snapshot of the key metrics. You can select the KPI card, to view additional details.
The system uses this pattern for KPI views with a threshold value defined. The following KPI cards are
supported:
● Gauge Pattern
The system uses this pattern for KPI views with a threshold value defined.
In Fiori Client, gauge helps extract complex information and gives a graphical view of how you’re doing
towards a goal. It shows KPI views with a threshold value defined and requires either target or threshold or
both to be maintained. It requires at least one of the two (Target or Threshold) to be maintained. Odometer
shouldn’t be used as a pattern for minimize.
There are three options here:
You can select the report card, for detailed analysis of the report. For optimal performance, we recommned not
to add more than 4 reports on the home page. Reports with table are not supported. The following Report
cards are supported:
Note
Note
Note
Note
You can personalize your homepage screen with your preferences. To personalize your homepage, you enter
the personalization mode by clicking the edit icon located inside the footer toolbar. Once you are in the
personalization mode, you can hover over the content area and see that editable areas are highlighted and
marked by a frame. You can select the icons which allows you to make the corresponding personalized
changes.
In the personalize mode, you can make various changes to the current screen such as rearranging the cards
and groups by dragging and dropping them, adding and deleting card and groups, renaming groups etc. You
can make hidden items visible again by turning on the visible switch. All hidden and available items will appear
in the list and you can add them again.
After completing the personalization of your homepage screen, you can exit the personalization mode by
saving the changes you made. Or if you want to remove the changes, press cancel.
If you are not actively using the homepage, you can disable it from being the default landing page.
Remember
Home Page Settings icon (gear icon) is located on the top right when you are in personalization mode.
With this setting, the first work center view defined for the user or role in becomes the default landing page for
the Fiori client.
In the personalization mode on homepage, you can uncheck the checkbox Set Homepage as the Start Page
under settings.
Learn how to add and edit cards on the homepage. You can rearranging these cards by dragging and dropping
them and also move them to different groups.
Note
For an optimal performance experience, you’ll get a warning message when you exceed the recommended
number of KPI and Report cards on the homepage. The recommended maximum number of KPI cards
supported is 10 and the maximum number of Report-based cards (Custom pattern cards like Bar Chart
cards) supported is 4. You still have the option to add additional cards, but it impacts the performance.
There’s no limit on recommended number of List cards, Tool cards, and Custom cards.
● Add card
There’s a + icon to add a new card at the end of each card. To add cards, click/tap the + icon. You can also
remove a card that you don't need by turning off the visible switch and making it invisible. If the card
preview shows a card as visible, then card is shown on the homepage.
● Edit Existing cards
Click/ Tap on a card to open the settings screen for the respective card. Turning off the Available switch
removes the card from the homepage, and automatically turns off the Visbile switch. You can change the
group of the card, for example, move the card to a different group and then save your changes. card
visualization can also be changed.
● Edit Custom card
Once a custom card is created, it’s placed on the user interface as available and visible. To edit custom
cards, click the card and open the edit dialog as you would usually edit other cards. The dialog includes
details such as Title, Path, and Description that are editable. However, the type of the card (URL vs.
Floorplan can’t be changed).
On the homepage, you can view the content of the mashup card. You can also click to launch the same mashup
shown in the card or you can launch a different mashup that shows more details of the HTML mashup card.
Note that mashups which do not have a port binding are also allowed in the home page card mashups
Based on your requirement and preference, you have the option to cluster the cards into a logical group.
● Add Group
You have the option to cluster cards by creating new groups. There is a + icon to add at the end of each
group. To add new groups, click/tap the + icon. You can also rename the supported groups.
● Delete Group
You can also delete groups created by you besides rearranging groups by dragging and dropping them. A
group created by you shows a Delete button. Delete will simply remove the group permanently so that it will
not be visible on the user interface any longer. You will get a warning message before removing the group.
The administrator can access homepage setting as a gear icon on the homepage.
As an administrator, under homepage settings you can enable the users or roles to group cards on their
homepage. To do so, check the checkbox Show cards in Groups under settings. You can also change the
homepage to show as the default start page when the user logs in. To do so, you can uncheck the checkbox Set
Homepage as the Start Page under settings.
As an administrator, you can adapt the look and feel of your SAP solution to suit your company’s need.
You can adapt the company logo and related settings in the title bar. You can also set a default background
image for your SAP solution. The changes will be visible to all users the next time they log on to the system.
Note
You cannot adapt the system watermark in the title bar, because the watermark indicates the nature of
your system.
Remember
You can define the company settings and all company level branding such as logo, theme builder, and
background image in Fiori client also with 1902 release. In Fiori client, you can access company settings
and branding from User Menu> Settings.
Navigate to Adapt Edit Master Layout Company Branding Images . The Shell Personalization dialog box
opens.
1. To upload a background image, in the Background tab, drag and drop an image file. The image file should
be in .png or .jpg format. We recommend that the size of the image is the size of your screen resolution.
The size of the image cannot exceed 1MB.
2. To save your changes, click OK . This background image is the default background image of your SAP
solution. The default background image is visible to all users who have not personalized their background
image settings.
1. To adapt the header bar, go to Header Bar tab. Drag and drop the required image file. The image file should
be in .png or .jpg format. We recommend that the size of the image is the size of your screen resolution.
The size of the image cannot exceed 1MB.
2. Click OK to save the settings.
Note
It is not possible to maintain multiple logos on the system. You will be able to maintain only one logo for all
the companies that are maintained on a system.
1. To upload a company logo, in the Logo tab, drag and drop an image file. The image file should be in .png
or .jpg format. We recommend that the height of the image is 20 pixels. The size of the image cannot
exceed 1MB.
2. To save your changes, click OK .
To remove your selected background, header, or logo image, in the Company Branding Images screen, click
Clear. To remove all the branding images and related settings, in the Company Branding Images screen,
click Reset All .
Click Adapt End Layout Changes once you have completed all your changes.
As an administrator, you can define your company settings that are applicable for all users, or a selected
business role.
To define the settings, log on as an administrator and navigate to the user menu, and click Settings
Company Settings . Under Define Settings for, choose Company, if you want to make the changes for all users.
Otherwise, choose Role, if you want to make the changes for a selected role.
General Settings
You can enable or disable a number of options for your users or a selected role via company settings. To
perform this setting, proceed as follows:
1. In the General tab, select any of the following checkboxes to enable or disable specified features:
○ Disable User Personalization Features: Prevents users from personalizing their screens. The option of
personalization doesn’t appear for all users the next time they log on to the system. Any
personalization settings maintained by the users prior to disabling of the option are retained. They
can’t make any further changes except personalizing the background image.
○ Disable Flags: Prevents users from marking objects as flags for quick access.
○ Disable Favorites: Prevents users from marking objects as favorites for quick access.
○ Disable Follow: Prevents users from following items for quick access.
○ Disable Download Button: Prevents users from using the download button.
○ Disable Quick View: Prevents users to see a preview for an object without navigating to its details.
○ Enable Chunk View as Default in Tablets: Provides the users an alternative visualization for the table
view in tablets.
○ Disable Report Incident: Prevents users from creating an incident. This allows administrators to
control the incidents that are reported to SAP.
○ Disable Annotation : Prevents the end user from annotating their screen to highlight a specific part of
the information using tools such as free-hand drawing, arrow, rectangle, and call-out texts in the Fiori
Client.
○ Enable Flat List Navigation Menu : If you work with a small set of work centers, you can see only those
work centers views rather than the complete set. This avoids additional clicks in opening the work
center and then clicking the view you’re looking for, thus, enhancing your user experience by reducing
the number of clicks needed to perform a task. Once turned on, this affects all business roles and
business users.
Note: Some work center views like Target Group are assigned to multiple work centers and might
appear more than once.
○ Enable Easy Create from Object Detail View: When you are in an object detail view, the easy create
feature lets you create a related object. This reduces the number of clicks as you don’t have to first
navigate to the respective tab to create a related object. Easy create is available within an object detail
page and can be accessed by the “+” sign.
Note
Currently, the drag and drop of accounts is available only in Google Maps.
○ Enable Side Pane: The side pane appears vertically on the right side of the screen. You can see the
header information and machine learning recommendations in the side pane for quick access.
○ Disable Vertical Split View of Master-Detail: Disable the master details split-screen view for products
and involved parties in sales orders.
○ Enable Semi-Collapsed Navigation Menu upon Sign-in: Under flat navigation, you can also enable
semicollapsed navigation upon sing-in. With semicollapsed navigation, the user can quickly launch
object lists without opening or closing the navigation menu. Ensure that hide navigation menu setting
isn’t selected and flat navigation is enabled.
Note
○ Disable Multi-Tabs for Desktop: Disabling the multitabs in desktop provides a simple navigation path.
With this company setting, the user clicks a business object in a list, and can directly navigate back to
the list using the back button.
○ Enable New UI for Smartphone Extended App: You can use the new redesigned smartphone
extended edition app with this setting. The navigation menu is redesigned like the consumer-based
app layout, with menu bar on the bottom of the screen, thus optimizing the user experience.
○ Enable Auto Adjustment of Table Column Width: You don’t have to expand or reduce the column
widths in a table to see the complete table. The columns automatically adjust to the table size and
shrink to minimize the white space. In case, the table is long, the columns shrink further by wrapping
the header text. Thus, maintaining all the values on one screen.
○ Show the Actions Menu on the Top Right: From the current location on the user interface, you have
the option to see all actions at the top right on the homepage, list view and detail view. You get a
consistent experience, and have quick access to the actions in one place. You don't have to search for
actions across the user interface. However, the completion actions such as Save and Cancel appear at
the bottom, in most cases.
The company setting Show the Actions Menu on the Top Right will be retired with May 2020 release
and be available as default.
○ Enable Editing in Dataset: In many objects, you can edit information directly in the worklist view,
without navigating to the detail view. Directly editing in the worklist view reduces the number of clicks,
and the time it takes to navigate to object detail view to make an edit.
Note
The company setting Enable Editing in Dataset will be retired with May 2020 release and be
available as default.
○ Enable Inline Editing in Browser: With inline editing, you can quickly edit a field without going into the
global edit mode. In inline edit mode, when you hover over a field, you see the related icon to edit the
field. For example, let's say you want to edit the phone number in inline edit mode. When you hover
over the phone number field, you see the pencil icon. Click the pencil icon to change the phone
number. After you have made the edit, Save and Cancel action are available. You can either save or
cancel your changes.
Restriction
The enabling and disabling the two settings (Enable Inline Editing in Browser and Enable Editing in
Dataset) gives you different combinations of how the user can interact with object detail view, new
quick view and datasets.
Disabled Enabled Only global edit is allowed. Only global edit is allowed.
Enabled Enabled Both global edit and inline Both global edit and inline
edit allowed. edit allowed.
Note
○ Inline edit capability for data sets is enabled only when both the company settings (Enable
Inline Editing in Browser and Enable Editing in Dataset) are switched on.
○ The new quick view is a beta feature in 1911. Customers can request access via incident
creation.
○ Mass edit capability on data set is a beta feature in 1911. Customers can request access via
incident creation. Mass-edit is a functionality in data set where you can edit multiple records of
○ Enable in-app help with SAP Enable Now: Allows you to access the in-app contextual help in the
solution. SAP Enable Now Web Assistant is a web-based help system to provide you context-sensitive
user assistance. It enables you to get started quickly and to find all relevant information easily without
needing to leave the respective application. Web Assistant provides additional information directly on
top of the current application screen.
○ Enable Geolocation Tracking: You can enable the region-based map setting to show regional
international boundaries for your country.
Remember
The display of international boundaries based on geo location tracking is currently supported only
in Google Map.
When you use the map feature within the app, your country’s boundaries aren’t default displayed
regionspecific in the map. For example, if you log in from within your country, you see a solid black line
between all areas of your country’s boundaries. However, if you log in from outside your country, you
see a dotted line for the region under a territorial dispute with another country.
You can enable how the map shows up based on the company setting Enable Geolocation Tracking.
When the company setting is enabled by the administrator, you see a localized version of the map as in
the web. With the setting enabled, you see a pop-up from the system asking to know your current
location. If you allow the system to track your location, you see a regionspecific display of the map. In
future, if you don’t want to allow the geolocation tracking, you can block the geolocation tracking from
under your browser settings. When you block the geolocation tracking, then Google map API of default
country, United States of America is displayed.
Remember
Geolocation tracking is only used to show regional international boundaries for your country.
○ Show Header Details on the Top: You can see the header fields at the top in the object detail view. The
header fields are always visible, even when you switch to a different tab. You can expand and collapse
the header fields to view the fields. When enabled, inline editing is also available for header fields. If the
header field is enabled, and the side pane is also turned on, then the header fields show at the top in
the details view.
Note
Note
Flag, favorites, and tags aren’t supported in the new quick view.
Note
○ Hide Notification: You can hide the notifications and the notifications icon with this setting. Seeing
notifications can be disruptive, and also takes space on the screen.
○ Enable Value Help Suggestion in Phone:You can enable value help suggestion in phone with this
setting. However, enabling value help suggestion may affect its performance in phone.
For security reasons, users are automatically logged off of the system if they’ve been inactive in the system for
a certain period of time. If you leave this option empty, inactive users will be logged off of the system after 1
hour. You can set the auto logoff time for all users in your company. To do so, proceed as follows:
1. In the Auto sign out tab, open the dropdown list against the Inactivity Duration field, and select the
preferred time duration when inactive users will be automatically logged off the system.
2. Click Save or Save and Close to save your changes.
Note
Client
In the Client tab, you can set your thumbnail cache validity.
Signature
You can define the URL for your preferred C/4HANA products here. When you open your extended edition UI,
you’ll have a shortcut to the saved URLs.
You can launch and navigate to different SAP C/4HANA applications in a new browser from within the solution.
To do so, proceed as follows:
When you open your extended edition UI, you have a shortcut to the saved URLs.
UI Controls
You can define font type and font size for rich text fields. To do so, proceed as follows:
1. In the UI Controls tab, select a font type for default font type and a font size for default font size
2. Click Save and Close.
Note
Business users can override this setting by explicitly changing the font type and font size for a specific rich
text field. The change is implicitly remembered for each device.
Global Settings
You can define system settings and preferences that apply to all users in the organization irrespective of the
business role assigned to them.
For example, if you want all the users to use the configured language for single sign-on, set Enable Configured
Language for Single Sign-On to Yes. The result is that irrespective of the business role that the users are
assigned to, the global settings that you configured will apply to them.
As an administrator, you can create custom work centers and custom work center views.
Navigate to Administrator General Settings Users and click Custom Work Center. The system shows
you a list of all the custom work center and work center views.
To create a new work center, click New. Select the type, enter a name and click Save.
To create a new work center view, click New. Select the type, enter a name, assign it to a standard or custom
work center, and click Save.
You can also assign mashups to a work center view. To do this, assign the work center and work center view to
the business role or business user first.
In your solution there are various predefined templates that you, as an administrator, can use when you export
data or create new data from Microsoft Excel.
Overview
As an administrator, you can change the existing templates according to your company's specific requirements
by adapting the properties of a template, such as the formatting or the sequence of columns. You can also
create new templates, for example, for different languages that you require. In addition, you can add charts,
diagrams, or formulas to the template.
Prerequisites
You have installed the latest Add-In for Microsoft Excel from the Download area.
Procedure
1. In the Microsoft Office Template Maintenance view, under Business Flexibility of the Administrator work
center, go to the template group that you require for your worklist or floorplan.
Note
If you want to change a pre-delivered template, export the template from the relevant application work
center by clicking Export and To Microsoft Excel.
Delete the data records that have been exported from the system before changing the template.
2. Choose the type of template depending on whether you want to export data or create new data from
Microsoft Excel and the language you require.
3. Download the template that you want to change to your local machine by selecting the template and
clicking Download.
4. Use the Microsoft Excel functions to adapt the template according to your needs by changing the column
sequence, the texts for the different fields, or the formatting.
○ If you want to change the general layout of the Microsoft Excel template, such as the fonts of individual
cells or the date format or other styles for cells, go to the Master Template Maintenance view.
○ When you download a Microsoft Excel template of the type Export, any extension fields for the
business context are automatically included in the template and you can map these fields as additional
columns. When you have added the new field, you can format the column heading and the column
Note
You can also change the name and description of a template in the worklist by selecting the template
and clicking Actions and Maintain General Information.
Likewise, you can change the master template setting for a template by selecting the template and
clicking Actions and Change Master Template Usage.
8. If you want to make the template that you created or changed available for all users, you have to publish it
by clicking Publish.
1. Once you have published a template in various versions, you can go back to an older version of the
template. Select the version that you want to use and click Versions and then Revert To.
2. Publish the valid version to make it available for use.
9. If you want to delete a template, select the template and click Delete.
Caution
If you delete a template with the status Not Published, you cannot restore this template.
The Help Center contains the solutionspecific Help documentation delivered by SAP. As an administrator, you
can also add companyspecific documentation in any workset, for example process descriptions or general
business rules. It is also possible to add a file to all screens within the system.
Prerequisites
You have written your help document in one of the following formats:
Steps
Tip
You can upload files up to 500 MB in size. However, for performance reasons we recommend not
uploading files larger than 20 MB.
Your companyspecific help document is added to the Help Center, and can be accessed by all users in your
company.
Administrators can restrict the values available from a dropdown list by creating and maintaining code list
restrictions for different business objects.
In this example, if you select the AND operator, then Y is the dropdown value when the control fields are
A and C.
If you select the OR operator, then Y and Z are the dropdown values when the control fields are B and C.
4. Click:
○ Save to save your code list restriction.
○ Save and New to save your current code list restriction and open a new quick create box to create a
new restriction.
○ Save and Open to save your current code list restriction and open it in maintenance mode.
Result: You have restricted certain code values from appearing in certain drop-downs. This restriction is based
on either a field or a business role, or a combination of both field and business role.
Example
The system displays all the available code list values for the code Cash Discount Term Code, for the
business object Sales Data. You have an option to restrict or allow the code values for the control field
values Direct Sales and Indirect Sales individually.
To sort or change display mode for code lists, follow these steps:
1. Right-click the field where you want to sort or change display mode for code lists. The system opens the
field configuration details on the right pane. Alternately, you can navigate to the details screen.
2. Click the Drill down icon next to Code List to go to the next level.
You can view the following new fields:
○ Sort: Allows you to sort code lists by ascending code, ascending description, or default order.
○ Display: Allows you to display code lists by values, codes, or both code and value.
3. Select the required option from the dropdown list.
4. To save your changes, go to your user profile, and from the dropdown list select End Adaptation.
As an administrator, you can transfer code list restrictions from one system to another using the Transport
Management System.
This provide you with an easy way of migrating code list restrictions from a test to a productive environment
thus helping you save implementation time.
To transport code list restrictions from one system to another, follow these steps:
Note
You can download the zip file on the Transport Content tab and verify its content.
7. Choose Action Release to export the code list restrictions to the target systems.
Note
You can check the assemble and release information on the Transport Logs tab.
8. Log on to the target system and go to Administrator Transport Management All Transport
Requests .
A survey object with the Imported status appears in the table.
9. Select the imported object and you can see the list of code list restrictions assembled in the source
system.
10. Choose Action Activate to transport all the code list restrictions to the target system.
As an administrator, you can create and edit custom orders for code lists.
1. Navigate to the screen where you want to create the custom order.
2. Go to your user profile, and from the dropdown list select Start Adaptation. The system opens in the
Adaptation Mode.
3. Right-click the field where you want to create the custom order to open the field configuration details on
the right pane. Alternately, you can navigate to the details screen.
4. Click the Drill down icon next to Code List to go to the next level.
5. In the Sort field, select Custom from the drop-down list. The Custom Order field becomes visible.
6. Click Edit.
7. In the new screen, enter a Name, rearrange the code list order using the available buttons, and click Save.
Note that you can enter only the following characters: A-Z, a-z, 0-9, and underscore (_).
Note
Select the Reusable checkbox if you want to reuse this custom order in other objects. Note that
selecting this checkbox resets the code list section. Therefore, we recommend that you select it before
creating the order.
8. Click Assign. The new custom order settings are applied to the field.
9. To save your changes, go to your user profile, and from the dropdown list select End Adaptation.
As an administrator you can organize work centers and work center views.
1. Navigate to Administrator General Settings Organize Work Center and Work Center Views and click
New.
2. Enter a name and select a navigation type.
3. Select a work center to see the corresponding work center views. By default the Visible (for Desktops and
Tablets) and Visible (for Smartphones) checkboxes are selected. To hide a work center or work center view,
deselect it.
4. Highlight a work center or work center view and click Up, Down, Top, or Bottom to rearrange the sequence.
5. Click Save and Close.
You can assign the organized work centers and work center views to the master layout or a specific business
role.
If you have assigned an organized work center and work center view to a role and another one to the master
layout, then the role specific one takes precedence.
Note
If a user has more than one business role assigned, then the first role alphabetically takes precedence.
If a user with multiple business roles has different organized work center view names assigned, then the
system uses the union operation to hide or show the work center and work center views.
As an administrator, you can track details of all the adaptation changes that have been exported or imported
from your system.
You will see a list of all the adaptation changes that have been imported or exported. The table displays the
following columns:
● Content: Displays whether the xml file has been imported or exported.
● Name: Displays the link to the details of the export or import. Clicking on this link will display the individual
migrated items that have been changed or updated in the system.
● Last Date: Displays the date it was imported or exported.
Note
If you are exporting the adaptations changes for the first time from your system, the base xml version
will be 1. After the first export, if you make further adaptation changes to the system and export the
changes a second time, the base xml version will be 2.
You can can import and export adaptation changes made to the following items as part of the content transfer:
● Extension fields
● Extension scenarios
● Reports
● Services
● Form types
● ODATA services
Use the language adaption tool to translate and adapt user interface (UI) fields with terms that better suit your
business. As an administrator, you can translate or adjust texts for most areas such as application work
centers, Feed, Live Activity, Enterprise Search categories, and most texts created in the SAP Cloud Applications
Studio.
By using Language Adaptation in the Administrator work center, administrators can translate and adapt fields
belonging to work centers and views into languages that are not currently supported by SAP. You can adapt
field label terminology to fit your business needs. For example, if you are working in the health care industry
and use the term 'patient' instead of ‘account’, you can exchange the user interface term account with patient.
In addition to static terms, you can also adapt most other user interface elements such as code-based value
help (selection help), reports, and application messages. After you have completed the adaptations, you are
able to export and import the text pools into other systems using Microsoft Excel.
Note
Due to technical reasons, there are a limited number of screen texts that cannot be adapted, such as, the
migration workbench, and some texts in the Analytics work center.
If your business would like to receive translation proposals from the SAP Translation Hub, please contact your
SAP representative (additional fees apply).
Use the available additional communication languages for creating customer languages, for languages that are
not available in business scoping.
1. Choose the work center Business Configuration Implementation Projects Open Activity List .
2. In the Show field select All Activities and in the Find field type language.
3. Select the Additional Communication Languages line item and click Add to Project.
4. Double-click line item Additional Communication Languages.
5. Look for the desired language in the Language Key field and ensure the corresponding Language is Allowed
field contains a check mark area for the desired languages.
Note
If the desired language is not in the list, you can select Customer Reserve from the Language Key list
or contact your SAP representative.
When you log on to the system, an additional language appears on the logon screen with an extension
<Language> (Customer Language).
The logon language extension only appears after you have created and filled a text pool for that language.
To remove a language from the logon screen without deleting the corresponding adapted texts, navigate to
Business Configuration Fine-Tune Additional Communication Languages and deselect Language is
Allowed for the desired language.
Create additional logon languages and adapt the desired field texts accordingly.
1. To create a new translation or adaptation, click Administrator Language Adaptations New and
enter the following text in the mandatory fields:
1. ID
2. Name
3. Select a language from the Source Language drop-down list.
4. Select a language from the Target Language drop-down list.
2. Click Save and Open to continue with the language adaptation process.
Tip
If you want to adapt a term to your business needs, for example, replace Accounts with Patients, use the
Filter Texts and Replace with fields located on the upper right-hand side of the screen. You can also create
language adaptations using the same source and target language.
To quickly find the desired work center, type the name in the Filter Work Center Name field and hit enter
on your keyboard.
The solution's text collector will begin to drill down through the selected work centers and compile the texts.
The solution will also fill the target text column with the existing overrides you or other administrators in your
solution may have made in other language adaptations.
Once the texts have been collected, you'll see the quantity of texts on the left-hand side of your language
adaptation screen and can begin maintaining them.
Note
When collecting texts, keep in mind a particular language does not necessarily have to reside in one text
pool. Since text pools contain a large quantity of texts, they may be difficult to manage. Therefore, we
recommend dividing a translation into multiple text pools, for example, one for each text type.
Tip
In order to avoid a system time out, we highly recommend that you only add one to three (1- 3) work
centers at a time to the text pool and execute Collect Texts before proceeding with the additional work
centers in batches of one to three.
Caution
When unselecting work centers of an existing language adaptation, recollecting the texts again will remove
the texts for these work centers including their adaptations from this language adaptation. Remember
clicking Save can cause adaptation loss.
In this step you will begin adapting and translating texts from text pools to meet your business needs.
1. Click the tab of the text type you collected in the previous step, such as the UI Texts tab.
2. You can use the Sort filter to conveniently find the field you wish to adapt.
Note
If the Target Text field is read-only and highlighted in green, either another administrator has created
language adaptations or you previously created a language adaptation that already contains those field
and the texts cannot be overwritten. When you hover over the text, a tool tip displays the name of the
original text pool. This only applies to the UI texts and messages since code and report texts do not
have locks.
If you want to move the write permission target text read-only fields from for example, Language
adaptation 1 to Language adaptation 2, you must make sure that the actual target texts have been
collected for the Language adaptation 2. Afterward, you can delete Language adaptation 1. Collecting
the texts for Language adaptation 2 again will remove the read-only mode.
3. Search for the text you wish to adapt by using the Filter Texts and enter the desired text in the Replace with
field. The Target Text column will be populated with the adapted text.
Remember
The Search function is not case-sensitive, but the Replace function is.
4. Click Save.
To better understand the language adaptation tool, let's take a look at some of the important fields.
Source Text The original source text delivered by SAP Hybris Cloud for Customer or the text your company has
previously created in the SAP Cloud Applications Studio.
Target Text The adapted text you entered to meet your language needs.
UI Type The name of the UI element type, such as, UIWC (work center), UIWV (work center view), UICT
(floor plan).
UI Short Name The UI short name as identified in the back end system of the solution.
Cleanup Used when you have finished populating the Target Text. This will remove rows with empty target
texts. In addition, it will remove the rows where target texts have been populated using the Collect
Target Texts action for target texts which have never been modified.
Note
Choosing Cleanup will not remove rows with collected target texts that were manually modi
fied after being collected. Subsequent Collect Text actions can be executed at any time and
will refill the text pool again.
Note
To reduce load time and a high data volume of unused or redundant text data, run the
Cleanup action once the target text modifications are finished. This is especially important if
Collect Target Text has been used.
Export Used if you want to export the text pool to Microsoft Excel®. See Exporting and Importing Text Us
ing Microsoft Excel®below for more information.
Remove Select a row or multiple rows and use to remove all selected rows from the table.
Clear Target Texts Used to clear all entries from the Target Text column.
Collect Target Texts By clicking Collect Target Texts, you will collect the SAP-delivered target texts according to the tar
get language settings in your language adaptation. When you choose Collect Target Texts, a new
complete Collect Text action is not performed, but it will take the given source texts and find their
target language counterparts.
Note
When choosing the Collect Target Texts field, the existing adaptations are never overwritten.
Collect Text actions can be executed at any time and will not clear any target texts.
Reuse Translations Once you populate a target text field and click Reuse Translations, the tool automatically populates
the previously translated text to empty target text fields with the same source text.
Tip
If you have created SAP Cloud Applications Studio custom messages and want to adapt or translate them,
the system can collect business object messages and business object extension messages.
Update Texts from Mi Choose this action if your company has a large number of texts to adapt, prefers to work offline,
crosoft Excel® will use an external agency to adapt the text, or wish to transport language adaptations across test
and/or productive systems. See Exporting and Importing Text Using Microsoft Excel below for
more information.
Fill-Up Target with Select this action to fill the target text field with the same text as the source text field.
Source
Note
Only use this function in translation scenarios where you do not want to have English as the
fallback language, but need the language adaptation's source language to fill the gaps for
missing translations.
Restriction
Fill-Up Target with Source can only be used when the source language is not equal to the target
language.
Simulate Translation Choosing this action will copy source texts to target text denoted by a <‘^’>.
Tip
This will help you to determine an estimation whether a translation using the language adap
tion tool will meet your demands. You can remove the <‘^’> character by deleting the lan
guage adaption.
Restriction
Simulate Translation can only be used when the source language is not equal to the target lan
guage.
There are a few system messages that cannot be adapted using the language adaptation tool, for example, a
mandatory field belonging to a form that has not been filled. You will receive a system error message stating
you must populate the field. Keep in mind, this message cannot be overwritten.
The language adaptation functionality can export and import text pools and is typically used in the following
scenarios:
There are limitations to importing and exporting text pools, so take note of them before you proceed.
Caution
It is not possible to create new text pools from the beginning by simply importing an Excel file exported
from another system. The current Excel import is only able to modify an existing text pool. This means the
text pool you want to import needs to be created manually in the target system before populating it with
content using the Excel import functionality.
The language adaptation tool uses the Standard Excel for downloading, but the Template Based Excel for
uploading files.
This means that in order to transport all texts from a source text pool to a target system, you must:
1. Export from the different text type tables (UI, codes. messages, reports) separately by choosing Export
To Microsoft Excel .
2. Download the Excel upload template from the text pool's root node of the solution.
3. Manually copy and paste the corresponding columns from the downloaded Excel files into the upload
template.
4. Import the populated upload template into the target system.
Example
An administrator wishes to adapt the text pool called 'Activity work center in Bulgarian' from their test system
into their productive system. The text pool has English as its source language and Bulgarian as its target
language. It only contains the Activities work center and will drill down to look for UI texts, code texts, and
report texts that need to be adapted. The text pool has been populated with Bulgarian target texts and
everything appears as expected when logging on to the test system using the Bulgarian (Customer
Language). Now, the administrator wants to use the same text pool in the productive system.
Note
Export the Excel files from each text table separately. In this example, the administrator will have to go to
each of the tabs (UI Texts, Code Texts, Report Texts) and download separate Excel files for each table.
1. Logon to the target system by navigating to Administrator General Settings Language Adaptations
and create the same text pool and a different text pool ID (just to avoid confusion).
2. Enter the source language (which can be different from original) and enter the same target language, work
center name, and text types to be collected (UI, Codes, Reports).
3. Click Collect Texts which is mandatory step, in order to populate the text pool with text elements.
Note
6. Tip
The upload and download files are not exactly the same, so ensure you are copying the correct text into
the desired fields.
7. Ensure the Text Pool ID field in the upload Excel contains the text pool ID in the target system.
8. From the Excel, navigate to SAP Add-in, logon to your system, and click Save Data to. You can then begin to
view your adapted texts in the system.
Remember
The most common misunderstanding that can occur is when you attempt to upload text elements that do
not yet exist in the target text pool. This is indicated by a warning displaying the text and the text ID.
According to the limitation mentioned above, it is not possible to create entire text pools or to create new
text rows for an existing text pool. The Excel upload is only capable of modifying the target texts of existing
text elements.
As an administrator, you can create and define custom business objects as per your requirements. This creates
a customerspecific solution called KeyUserSolution in the SAP Cloud Applications Studio.
Prerequisites
You are creating the custom business object in one of your test systems. You can then download and upload it
into your productive system and other test systems.
Procedure
1. Go to the Administrator work center, and select General Settings Custom Object Builder New .
2. Enter name, and select Save and Close to save the new custom business object. You can see the newly
created business object in the list appearing on your screen.
While entering a name for your custom business object, you must use only alphanumeric values; however,
you will not be allowed to start the name with a digit. You can also use capital letters; but the system does
not allow you to use spaces or other special characters.
After creating a custom business object, you tailor it to suit your specific requirements.
Procedure
Assign to Other Work Center: Allows you to assign your business object to other work centers. The system gives
you the option of selecting the work center to which you would like to assign your custom business object.
With Authorization: Allows you to assign access control for the data of your business object.
Example
By selecting 1010--employee, you can restrict access to records based on the employee assigned to that
record. Make sure you've done the following:
● Added an employee field at the root node or sub node of your object: Entity type Relation to Thing
Type with Thing Employee
● Flagged the field for Used for Authorization
This enables the restriction of access based on the employee added to this field.
You can also create a sub node for teams and add an employee field and flag that for authorization to grant
access to custom object records based on employees assigned to the team.
With Multiple Nodes: Allows you to add nodes (a collection of 1:N cardinality) to the root node of your business
object. This creates a tab under which you can create the sub nodes.
You can only create sub nodes for the root node, and not for other sub nodes.
With Actions: Allows you to create actions, which can be executed by the end user. This creates a tab under
which you can make specific changes/assignments.
You can only add actions here. For further scripting of these actions, log on to the SAP Cloud Applications
Studio.
With Approval Process: Allows you to define approval processes for the data instances of your custom business
object. You can then define and manage the approval processes, including multi step approvals, via the
Approval Processes view of the Administrator work center.
With Workflow Rules: Allows you to define notification rules for your business object using workflow rules.
With Data Source: Allows you to generate data sources for the custom business object to meet your reporting
needs.
With Web Service: Allows you to generate SOAP web services for the business object. By selecting this option,
all elements and operations of the business object will be a part of the web service.
You can also download the WSDL file directly from the Custom Object Builder screen for the relevant business
object.
For the custom business object to be visible as a tab, make sure you've done the following:
● Created an association between the custom business object and account: Entity type Relation to Thing
Type with Account as Thing.
● Saved and published your changes.
Add and define new fields for your custom business objects.
To add a new field, choose Add, and enter the relevant information:
● The name you enter (256 character limit) will display on the screen.
● Indicate whether the field is mandatory.
● Select the entity type. Available types include:
○ Identifier: If you add an identifier type field to your custom business object, the system automatically
generates a number when a new record is created.
○ Description
○ Amount
○ Quantity
○ Time
○ Web URL
○ Date
○ Decimal value
○ Indicator
○ List: Use this list to define your own code list.
○ Code: This option allows you to use any SAP delivered code list released in our public solution model.
○ Relation to thing type
● You can reference the custom business object to another custom business object, an account, an
employee, or another standard object by selecting the Relationship to Thing Type option.
If you selected the Multiple Nodes option, then you can select from the list of nodes to indicate where to add a
field. You can create new nodes under the nodes tab and add new fields to it in this section.
Note
You can build the hierarchy structure of your business object by adding one or many nodes under the root
node.
After creating a custom business object, model it to suit your requirements using actions.
Context
You can add actions for each of the nodes by choosing Add.
Note
You can only add actions here. For further scripting of these actions, log on to the SAP Cloud Applications
Studio.
Note
The system displays certain elements that have been created for your business object by default and you
cannot edit or delete these elements even in the edit mode.
Once you've finished defining your custom business object, you can:
Once you have published your custom business object, you can also use ODATA Explorer to generate a custom
ODATA service.
You must log on to the SAP Cloud Applications Studio in order to further implement the custom business
object. You will be able to add logic to the ABSL script files of your custom business object in SAP Cloud
Application Studio.
Once your custom business object has been successfully published and the implementation is complete, you
will need to transport it to a productive tenant. You can also transport your custom business object to another
test system by following the steps mentioned in this document.
Procedure
1. Select the custom business object with the status Published. You can see the status of your business
object in the Custom Object Builder tab.
2. Select the Mark for Transport icon under the actions column.
Only business objects with the status Published will have the option of being marked for transport. You can
mark more than one published custom business object for transport. This helps to download all relevant
business objects together.
3. The status of the business object changes to Marked for Transport.
4. After all the relevant business objects have been Marked for Transport, click Prepare Download. The system
saves the download in a zip folder.
5. Login to the relevant productive tenant.
6. Navigate to the Administrator work center, and select the Custom Object Builder tab.
7. To upload the custom business objects, click Upload via Control, and select the relevant zip file.
Results
● The system displays a Version Number, which shows you the different versions of the same custom
business object that have been uploaded with modification.
● The system does not include the assigned business roles in the transport. The business role must be
assigned again in the deployed system.
Note
After transport to a productive tenant, the system does not allow you to delete the custom business
objects.
You can use business-object-based navigation to navigate from any external object to any linked appointment,
task, e-mail, phone call, visit, or route.
To activate this navigation, your custom developer must know which import to use for navigation to make the
appropriate settings.
Learn how you can use workflows to support your business processes.
Automate your business processes using workflows. Configure to send notifications, trigger automatic e-mails
and define conditions to update fields or calculated values. Also trigger actions or schedule workflows based
on dates, time or other complex conditions. Workflows also allow you to create multi-step approvals.
Workflow configuration involves creating workflow rules that can trigger automatic e-mail messages,
notifications, field updates and actions for business objects. Administrators can create workflow rules
specifying actions/notifications/field updates for business objects, recipient groups, employees and so on.
Workflows enhance the flexibility and adaptability of your Cloud for Customer solution to your custom business
requirements.
To configure workflow rules, go to Administrator Workflow Rules New . Using workflows,you can
activate rules for updating fields, setup automatic notifications, trigger creating tasks, send e-mail notifications
to customers and so on. The various configuration possibilities for workflows are described here.
Workflow rules involve a five step process. These include Business Object, Timing, Conditions, Actions, Review
and Confirmation. These components determine how the workflows will be used in the various business
processes. The steps are described in detail further in this chapter.
The first step to creating a workflow rule is selecting the business object for which the rule applies.
Timing
The timing determines when the system should evaluate the rule. The three available options are On Create
Only (when the object is created), On Every Save (every time an object is saved) and Scheduled (scheduled
after an event occurs). You can specify, for example, if a workflow rule be triggered when an object like a sales
quote or ticket is created or when saved. There is also an option to schedule the rule for a specific time, for
example two days before the due date of an item.
Conditions
Conditions are the criteria which trigger workflow rules. These conditions may be standard fields, extension
fields, field value change and so on. For example, if you create a sales quote above a certain value (the
condition), the system triggers the associated action. You must maintain conditions in Groups. Maintain
multiple conditions within a group if you need more than one criteria to be met for the workflow rule. Use
separate groups to define OR conditions.
Actions
E-mail, Messaging and Actions define tasks that must be executed when a workflow rule is triggered. For
example, send an e-mail, generate a notification, send a text message or update a field of the object (both
standard and extension fields as well as trigger an action). You can define actions using one of the supported
rule-types namely the Notifications. To better understand how these actions are triggered, here are the basic
steps your administrator takes to set up workflow:
Administrators can configure when a workflow rule must be evaluated and triggered. Timing can be relative to
create or change of a business object or can be scheduled.
The three available options in configuring workflow timing are are On Create Only (when the object is created),
On Every Save (every time an object is saved) and Scheduled (scheduled after an event occurs).
● On Create Only - The rule is applied at every create of a business object instance; No other attributes are
considered for On Create Only selection.
Note
The events listed in the field help are specific to a business object you have selected. Further, the
business object selected can be enhanced with a custom field with data type as Date.
Recommendation
● Workflow rules that are set to with Timing - On Every Create or On Every Save are run synchronously
while the transaction object is being created or saved in user session. Too many rules affect system
performance. Therefore it is recommended that you consolidate these rules.
● Use the Scheduled option as the scheduled rules run asynchronously and the conditions and actual
workflow for scheduled rules are triggered outside the user session.
● Note that workflow time affects all users using the business object within a process and define rules
accordingly.
Administrators can configure conditions to specify criteria that must be fulfilled in order to trigger workflow
rules. Conditions can be based on standard fields, extension fields, field value change and so on.
Conditions are structured in groups and include criteria that must be fulfilled if a workflow action must be
triggered. More than one condition can be defined using logical operators AND/OR. The AND operator can be
defined using condition within the same group. To add more than one condition, use the OR operator. Add a
new group to define the OR operator amongst the workflow conditions such that if conditions in at least one
group are met, then the overall condition is considered fulfilled and the workflow rule has been triggered.
For example, the value - Before Object Change, can be used to define conditions based on the field value
changes. For a notification is sent when the field - Escalated is changed from Not Escalated to Escalated.
Note
You can also create conditions using custom (adapted) fields. Set up any custom fields first, before
you create your workflow rules.
Messaging rules can be configured to send a formatted text message to the mobile device number registered
in the master data of the recipients.
● Select the flag Create Messaging Activity to create a business activity for the SMS text messages.
● Specify the Sender of this message. This is the Mashup Web Service ID that is used to trigger the SMS text
message.
● In the Text field, enter the description that should be displayed for the user.
● Placeholders are the field values of the formatted text message. To add placeholders, perform these steps:
1. Click Add Row.
2. Enter the placeholder as it appears in your chosen template file.
Caution
All placeholders included in notification templates must be in all caps, contain no special
characters, and begin and end with a hash tag (#).
For example:
○ #ID#
3. Select from the available list of fields. The list is dependent on the business object you selected for the
workflow rule. Custom fields appear in the list, and can be used with template placeholders.
4. You may also use your defined placeholders in the subject line of the notification.
● To define employees of a particular responsibility category as the recipients, click Add Determination. Then
select from the available list and repeat this selection as necessary.
Note
All business partner roles are available for selection in the list. The complete selection list is
dynamically added using code list and hence the values in the selection list can be modified. You can
use the fields Top Level Account Owner and Top Level Account Team as filters to include only the parent
company in a notification.
● To define a particular employee as the recipient, click Add Employee. Repeat this selection to add all
recipients of the notification.
● Configure sender service: Activate the scoping question - Do you want to record messaging activity?
under Business Configuration Implementation Projects Your Project Edit Project Scope
Questions Sales Account and Activity Management Activity Management Activity Types .
● Under Administrator Business Flexibility Mashup Web Services , create a mash-up web service to
integrate to the SMS provider.
Any e-mail and messaging activity that you trigger using workflows can be tracked in the document flow for an
object. This is possible because e-mail and messaging activities created through workflows are now linked to
the source object.
When creating workflows for sales order, if you select the Create E-Mail Activity flag, the e-mail activity is linked
to the sales order and also available in the Document Flow and Activities tabs in the sales order.
Administrators can configure updates to fields that must be performed when workflow rules are triggered.
Field updates change value of the field. For example, when a lead is created with Qualification level as Hot,
priority of the lead is automatically changed to Immediate
1. In the Fields to Update table, click Add Row to choose a field to update if the rule conditions are met.
2. Selects the fields that are required for update OR or select the Actions that are required to be triggered. For
example, if you select the field Priority, then select an Update Type with value as Urgent.
Depending on the type of field you select, the Update Type displays various options such as Calculated,
Value, Formula and Copy from Field :
○ Value - This option allows you to enter text, numeric value, add/remove for multivalue fields, or even
calculate values. These options vary based on the update type that you have selected.
○ Formula - Enter the formula that is internally in the system to perform the calculations and accordingly
update the existing field value.
Note
When workflow rules impact fields from other business objects, then the authorization of the user
triggering the workflow is not considered. For example, an administrator configures the workflow to
update the account role from Prospect to Customer when the quote is converted to Won. The end
user only has a read authorization to customer records even though the user has a create/update
authorization of sales quote. When the user converts the quote to Won, the customer's role is
updated to Customer even though the user does has no authorization to update customer record.
You can replace the entire lists and add or remove specific values from value help lists using the Field Update
option for workflow rules. Note the following checkbox options:
● Replace all existing values - Select this checkbox to replace the existing codelist with new values. When you
select this flag, the Add checkbox is automatically enabled for all the new values you have added in the list.
● Add - Enables you to select individual values from the list.
● Remove - Enables you to remove select values from the list.
For example, when you define workflow rules for visits, you can send e-mail notifications to visit attendees or
visit contacts.You want to ensure that everyone involved in a visit always has the latest information. Define a
rule so that anytime a visit is updated (any save), an e-mail notification is sent to the visit contacts and visit
attendee.
In the Define Actions step, select the Rule Type - E-mail. The E-Mail rules result in an e-mail being sent to the list
of recipients and requires an HTML file for use as the e-mail template. Use the following options to configure an
e-mail workflow template:
Tip
If you want to use predefined HTML templates for e-mail notifications, add HTML files to the list of allowed
MIME types in the Allowed MIME Types for Document Upload finetuning activity.
● Some appointment attendees may be outside your company and have no access to notifications in the
solution. Use rule type E-Mail to notify attendees of changes to appointments. When you use rule type E-
Mail, the option Appointment Attendees appears in the Recipient Determination section.
● Select Always Send E-mail flag if you want to receive an e-mail each time the business object is changed.
By default (flag is unchecked), an e-mail is sent only once.
● If you trigger creation of an activity for the e-mails that are triggered based on the workflow rule, select the
flag Create E-mail Activity.
● Select the flag Add Attachment if you want to enable adding custom attachments to the e-mails sent using
this workflow rule. Maintain the required logic to collect documents and attach them to e-mail. You
Note
Only parties with employee role can be used in the sender determination. If there are multiple
employees assigned to a party role, the determination selects details of the first employee in the list.
● Subject Template File - Mandatory - In order to complete configuring the workflow rule for e-mails, browse
for and select a template file that will be used for the e-mail notification.
● Enter the subject displayed for the recipient of the notification. You can also enter the subject in other
available languages by clicking
● Add placeholders to include them in the subject line and the template file of your e-mail notification. Map
any placeholders used in the template to fields in your solution. To do this,
1. Click Add Row.
2. Enter the placeholder as it appears in your chosen template file.
Caution
All placeholders included in e-mail notification templates must be in all caps, contain no special
characters, and begin and end with a hash tag (#).
For example:
○ #ID#
○ #ACCOUNT#
○ #100#
3. Select from the available list of fields. The list is dependent upon the business object you selected for
the workflow rule. Custom fields appear in the list, and can be used with template placeholders.
4. You may also use your defined placeholders in the subject line of the e-mail notification.
● To define employees of a particular responsibility category as the recipients, click Add Determination. Then
select from the available list and repeat this selection as necessary.
Note
All business partner roles are available for selection in the list. The complete selection list is
dynamically added using code list and hence the values in the selection list can be modified. You can
use the fields Top Level Account Owner and Top Level Account Team as filters to include only the parent
company in a notification.
● To define a particular employee as the recipient, click Add Employee. Repeat this selection to add all
recipients of the notification.
Users can be assigned to whom these templates apply. These signature templates will overwrite any existing
assigned templates. This feature allows administrators to enforce a uniform template for all users in the
organization.
Configure this feature under Administrator General Settings Templates Default Signature Templates .
Example
A workflow rule is configured for a sales quote to send an e-mail notification to contact person. However, the
contact person has primary relationships with two accounts, Account1 and Account2. In this scenario, if the
sales quote is created for Account2, then the e-mail notification triggered for the sales quote has account
defaulted to Account2.
These descriptions are more relevant and meaningful and add context to the e-mail. However, if you use
formatted texts in template placeholders, the e-mail displays same format in which the field value is saved in
the source transaction (for example, sales quote, sales order, ticket and so on).
The graphic explains the difference between using code list descriptions and formatted texts. The placeholder
#SOURCE# displays code list description E-mail request while the #MANAGERNOTES# placeholder field is
replaced by a text Manager with bold and colored font.
Track bounced e-mails and correct any inconsistencies in e-mail addresses. The workflow log is also updated
with the bounced instances.
Sender name and e-mail address can be automatically determined for workflow generated e-mail notifications.
For example, you may want to use e-mail address of the sales representative to send a sales quote. The feature
uses party determination to select a sender address. With this feature, any e-mail replies to the workflow
generated e-mails are routed to the inbox of the sender and you no longer need to provide a hard-coded sender
name and address.
Only parties with employee role can be used in the sender determination. If there are multiple employees
assigned to a party role, the determination selects details of the first employee in the list.
To use this feature, select the checkbox for Select a Sender E-mail for rule type - Actions under Workflow
Rules Define Actions .
Administrators can configure workflows to allow active delegates in your system can receive e-mail
notifications.
Use this feature to ensure information channeled for employees is received by their delegates or substitutes in
the absence of the employees. You can configure this feature under Administrator Workflow Settings
Recipient Determination Determine the active delegates for an employee in the system, as a recipient in
workflow rules .
As an administrator, any e-mail and messaging activity that you trigger using workflows can be tracked in the
document flow for an object. This is possible because e-mail and messaging activities created through
workflows are now linked to the source object. To enable tracking e-mails, you must select the flag Create E-
mail Activity in the workflow rule.
Example
When creating workflows for sales order, if you select the Create E-Mail Activity flag, the e-mail activity is linked
to the sales order and also available in the Document Flow and Activities tabs in the sales order.
Administrators can configure workflows to send e-mail and SMS only to the main recipient maintained in the
address.
Under Workflow Settings Address Determination , select Use main address of the recipient to send out e-
mail and sms, to send e-mail only to the main address that is maintained in the business address for a contact.
System behavior when this setting is applied, is documented below:
You have the ability to attach the business object summary as PDF in an outgoing e-mail.
When you configure a workflow for triggering email notifications, then depending on the condition of the
business object (for example, a sales quote) for which you configure the workflow, a summary of the business
object gets attached to the outgoing email.
Note
This feature is possible only if a form template has been maintained for a business object and an e-mail
template has been configured in the workflow configuration.
The enhancements have been defined in the third step of workflow configuration - Define Actions. Select the
Create E-mail Activity checkbox to send the PDF summary as an attachment in e-mail. If you do not select this
checkbox, only an e-mail notification will be sent without the PDF attachment.
Note
Also note that when you select the Create E-mail Activity checkbox, the PDF attachment sent in the e-mail
also gets attached to the activity.
Also note the new selection options for the template for PDF summary. The PDF Template Language and the
PDF Template Country together determine the PDF Template Variant. You also will need to add the employees
who are recipients of this notification rule.
If defined conditions are fulfilled, this rule type Activity-Task triggers creation of a task for the selected business
object.
The creation of a task results in a new Save of the main object involved (e.g. Opportunity or Ticket), potentially
triggering the execution of other workflow rules. Always define the conditions of each rule to be as restrictive as
possible, to avoid the risk of creating loops.
Restriction
Workflow rules of type Activity Task cannot be created for activity objects (appointments, tasks, phone
calls, and visits).
● By default, creation of a task results in a save instance for the business object. To create a task on every
save of the object, select the flag - Always Create Activity Task.
● Enter the subject to displayed to the recipient of the notification. Enter the subject in other available
languages by clicking
Caution
All placeholders included in e-mail notification templates must be in all caps, contain no special
characters, and begin and end with a hash tag (#).
For example:
○ #ID#
○ #ACCOUNT#
○ #100#
3. Select from the available list of fields. The list is dependent upon the business object you selected for
the workflow rule. Custom fields appear in the list, and can be used with template placeholders.
4. You may also use your defined placeholders in the subject line of the e-mail notification.
● Maintain Recipient Determination; To define a particular employee as the recipient, click Add Employee.
Repeat this selection until all recipients of the notification are defined.
● Maintain Employee Determination; To define employees of a particular responsibility category as the
recipients, click Add Determination. Then select from the available list and repeat this selection as
necessary.
Note
All business partner roles are available for selection in the list. The complete selection list is
dynamically added using code list and hence the values in the selection list can be modified. You can
use the fields Top Level Account Owner and Top Level Account Team as filters to include only the parent
company in a notification.
Rule type - Actions allows you to set certain statuses for the business objects.
If the conditions you have defined are fulfilled, you can set following updates to the respective business objects:
● Activate - This action changes the account status from In Preparation to Active.
● Assign Me as Owner - This action adds the logged in employee as employee responsible to the account
team.
● Block - This action changes the account status from Active to Blocked.
● Derive Territories - This action derives the territory for an account.
● Flag as Obsolete - This action changes the account status from Active or Blocked to Obsolete.
● Revoke Obsolescence - This action changes the account status from Obsolete to Blocked.
● Unblock - This action changes the account status from Blocked to Active.
You can use the workflow engine to configure custom actions and define when to trigger these custom actions.
This allows you to leverage the scheduling capabilities of the workflow engine. It also allows administrators to
modify the standard logic without having to modify the SDK code.
Run workflow analysis to use system generated recommendations to configure workflows for optimum
performance.
Administrators can run the workflow analysis using Administrator Workflow Rules More Workflow
Analysis .
Apart from design time analysis of the workflow rules for best system performance, this feature also identifies
workflow rules that are maintained without conditions or actions. Recommendations are given to configure
workflow rules with specific conditions and actions, in order to maintain a defined scope.
Internal notifications are those sent only to users of the solution and include the workflow notifications found
on the toolbar as well as e-mails.
In the Define Actions step, select the rule type Notification. Notification rules create a new item in the
Notifications list available in the toolbar. Only internal recipients receive notifications.
● Send Notification determines when the notification must be sent to the recipient. You can specify for
example, if the notification be sent on change or create of business object. In the previous Conditions
tab,define time-based conditions based on a date or time field of the selected business object. The system
uses these conditions to determine when to send notification to the recipient. For example: Send a
notification 10 days before the due date of the completion of a business document.
● Specify the expiration period for the notification — for example 10 Day(s). Expires After defines when the
notification is removed from the Notification List of the recipientThe default validity is set to 30 days after
which the notification expires if you have not mentioned an expiration period.
● Under Cancellation of Task, select the criteria, which for cancellation of the notification.
● Enter the subject to be seen by the recipient of the notification. You can also enter language specific
subject in other available languages by clicking .
● Placeholders are field values of the object that are used in the subject of the formatted text for notification.
Add placeholders to include them in the subject line and the template file of your notification. Map any
placeholders used in the template to fields in your solution. Placeholder are the field values of the object
that are used in the Subject of the Notification. To do this,
1. Click Add Row.
2. Enter the placeholder as it appears in your chosen template file.
Caution
All placeholders included in notification templates must be in all caps, contain no special
characters, and begin and end with a hash tag (#).
For example:
○ #ID#
○ #ACCOUNT#
○ #100#
3. Select from the available list of fields. The list is dependent on the business object you selected for the
workflow rule. Custom fields appear in the list, and can be used with template placeholders.
4. You may also use your defined placeholders in the subject line of the notification.
● To define employees of a particular responsibility category as the recipients, click Add Determination. Then
select from the available list and repeat this selection as necessary.
All business partner roles are available for selection in the list. The complete selection list is
dynamically added using code list and hence the values in the selection list can be modified. You can
use the fields Top Level Account Owner and Top Level Account Team as filters to include only the parent
company in a notification.
● To define a particular employee as the recipient, click Add Employee. Repeat this selection to add all
recipients of the notification.
Administrators can choose to send notifications for failed workflow rules to specific administrators and users.
You can choose whom to send notifications for failed workflow rules. In the Workflow Rules workcenter view,
click on the gear icon for Actions and then choose Workflow Settings. In the Workflow Settings screen, click on
the hyperlink for Notifications on Failed Rules. You are navigated to Failed Notification Recipient dialog screen
where you can add specific administrators to whom you want to send the notifications for failed workflow rules.
Use Remove to delete administrators from this list.
Send push notifications to inbox and mobile devices. Tap on the notification to navigate to the object related to
the notification.
Administrators can configure this feature by selecting the Send Push Notification indicator in the workflow rules
of type Notification.
Use the push notifications sent to social media channels such as WeChat to communicate and also fillup
surveys.
To receive these notifications, the contacts or users must register on the official social media account, that
creates a social media user profile for the contact.
Notifications for failed workflow rules are generated using an hourly background scheduled run. Note that the
notifications are generated only if there are failed workflow rules in the scheduled run. For each of the
background job, you can see how many workflow rules have failed.
Follow these steps to view the failed workflow rules notification logs:
You can now clean up your notifications list using Dismiss. This dismisses the notification for your user but
continues to display in the list for other users to whom the notification has been sent. You can also dismiss
multiple notifications at a time using multi-select and Dismiss option.
In the Notifications screen, click on the icon for advanced search and create a new query filter or modify
existing ones. Save these query filters and use them to search for notifications.
In the Notifications screen, click on the icon for advanced search and create a new query filter or modify
existing ones. Save these query filters and use them to search for notifications.
This dismisses the notification for your user but continues to display in the list for other users to whom the
notification has been sent. You can also dismiss multiple notifications at a time using multi-select and Dismiss
option.
Administrators can define notifications for delegates, where the delegate receives notifications of tasks to be
completed, or general notifications for the employee who is absent. Follow the steps given below to create a
delegate notification:
Note
When you or the employee activates delegate, the system automatically provides copies of notifications to
the delegate without the administrator having to manually maintain this view.
Note
You will see a list of existing delegates, if any. You can activate them by selecting Activate.
Note
Administrators can access workflow logs in the actions listed under the Settings (gear) icon in the Workflow
Rules work center view.
● Workflow logs are listed for all Past Rules and Scheduled Rules. Choose additional filters to display logs.
● The logs display date and time stamp for the error.
● The logs contain error messages displayed in the business object instance where the error occurred. Click
the hyperlink for business object ID to navigate to the business object instance where the error has
occurred.
● Select a rule and click Retry action listed under the actions.
● Click Export Rules to download the logs in an excel file.
Rule log displays error log for a selected workflow rule. Access this menu option under the settings (gear) icon
in the Workflow Rules work center view. Same set of details as workflow logs are displayed for the selected
workflow rule.
Following actions provided under the gear icon in the Workflow Rules work center view:
● Deactivate
● Activate
● Rule Schedule
● Workflow Log (shows past rules and scheduled rules to be executed in the future)
● Rule Log
● Workflow Settings (notifications on failed rules)
Monitor the status of the workflow rules that have already been triggered.
Use the Rule Log action to view the status of executed rules and review the outcome of all rules executed in the
past, and confirm if any rules have failed. This feature is helpful to monitor rules scheduled on multiple
instances. Further, if the workflow rule fails to execute, you can navigate to the object or to the rule to
investigate further.
With the Retry feature, administrators can re-trigger a failed workflow rule. you can filter the logs results by
specifying a time frame. For example, select Today in the selection help to view the logs created on that
particular day. A new log is generated with the updated statuses for the rules that have been re-executed. To
view the logs, click on Refresh. You can also filter the logs based on Rule Description, Object Type and Status in
the advanced search.
View the execution status for a workflow rule in the Past Rules table under Workflow Changes.
As an administrator, you can manage all your transport requests in one place. Create transport requests and
move implementation content between different systems.
Note
This feature is available only for customer systems and not for partner systems.
● Adaptation Changes
● Add-On Solutions
● Business Roles
● Code List Custom Order
● Code List Restrictions
● Custom Work Center
● Key User Extension Fields
● Language Adaptations
● Local Form Templates
● Mashups
● Organized Work Centers
● Surveys
● Templates
● Workflow Rules
The first step to managing your transports is to define the transport routes from the source system to the
target system.
1. Navigate to Service Control Center Systems Active Systems , and in the Overview tab, click Create
Transport Route. The system opens a dialog box.
2. In the Create Transport Route dialog box, select the Target System from the available list of active systems
assigned to the customer. The source system is defaulted to the current logged on system and is read-only.
3. Click OK.
You can view the existing transport routes listed in the Service Control Center screen. Click the System ID link to
view the transport routes for the system. If you are logged on to the selected system, all the connected
systems are displayed. For any other system, only the transport route to the currently logged on system is
displayed.
Once you have defined the transport route, you can create a transport request.
In the Transport Request page under Administrator Transport Management , to open the page. The
following table explains the different field labels on the screen:
Labels Explanation
● New - Indicates a new transport request (target systems and transport objects
may have already been assigned, but the assembly has not yet started)
● Assembly Started - Indicates that the assembly process has started and is cur
rently running as a background job
● Assembled - Indicates that the content of the assigned transport objects is
collected and packaged in the transport object
● Assembly failed - Indicates that an error occurred during the assembly proc
ess. The transport log lists the details of the error.
● Released - No further changes can be made to this transport. Transport is re
leased to a target system. However, you can still add additional target systems
and the assembled content is sent to those systems as well.
● Assembled with Warnings - Indicates that only some of the assigned transport
objects were successfully assembled. The transport log lists the details
● Closed - Indicates the transport request is no longer available for use, either
for transports nor for copying or to add any target system). By setting a trans
port request as closed, you avoid using the request to move content to another
target system.
For transport requests that are not local, the status values are:
● Imported - Indicates that the transport request is received from the source
system and is created in the target system
● Activation Started - Indicates that the activation process has started and is
currently running as a background job
● Activation Failed - Indicates that an error occurred during the activation proc
ess. The transport log lists the details of the error.
● Partially Active - Indicates that only some of the assigned transport objects
were successfully activated. The transport log lists the details.
● Activated - Indicates that the activation is successful.
Source System URL In the target system, use this URL to navigate to the transport request in source
system. Similarly, in the source system, use Target System URL to navigate to the
transport request in the target system.
Local Indicates whether the transport request is imported or created in the current sys
tem.
Action Required in Target System Indicates if any action is required in the target system. When the transport object is
imported and ready for activation, the field is updated. The checkbox is selected if
the transport object is ready for activation in one or multiple target systems. The
field is reset after the actions are complete in all the target systems.
1. In the Transport Management launch page, click New to open the New Transport Request dialog box.
Note
You can also copy transport requests to a new transport request, irrespective of their statuses.
In the Transport Management launch page, select the transport request you want to copy, and under
the actions menu, click Copy. Alternatively, in the detailed view, click More Copy to copy the
transport request
The target systems are copied if the transport request being copied is a local transport request
(created in the same system). The target systems are not copied if the request has been imported to
the system. Further, if any of the target systems is not active, it will not be copied.
2. Enter a name and note and click Save and Open. The Transport Request window opens.
1. In the Transport Objects tab, click Select. The Select Transport Objects popup window opens.
2. In the new window, select one of the transport objects from the first column in the table listed here,
followed by the relevant step listed in the Further Steps column, and then click OK.
Adaptation Changes Enter the work center ID (use You can move the key user adaptations in master
wildcards to search for a work layout and page layouts using Transport
center) or use the value help. Management:
Note
Analytical content related to embedded ICPs
(Information Consumer Pattern) are
considered in these Adaptation Changes
transports only if all adaptation changes of the
system are added to the transport request.
Note
Administrators must have necessary
authorizations to the SAP Cloud
Application Studio Developer workcenter
in SAP Cloud Application Studio.
Restriction
○ You cannot transport deletion patches.
○ You cannot transport key user (KUT)
solutions since these solutions have own
lifecycle management.
○ Due to automation, there is no e-mail
communication after you have
assembled the add-on solution.
○ Only the latest patch version can be
selected for transport.
○ You cannot trigger partial assembly from
the transport request. The assembly from
the transport request will always be
complete solution assembly.
○ You cannot transport deployed solutions.
○ You cannot transport to partner
development systems.
○ If patch solution and original solution
both exist, then the solution goes in the
Business Roles Select a business role ID from Select a business role ID from the value help. You
the value help. can activate unchanged business roles in target
system.
Note
The following data is not transported in
business role:
○ Notes History
○ Responsible Identity
○ Restriction rule 99
The values are hard coded master data in
rule 99. We cannot be sure that these
master data, such as, Customer ID,
Territory, Sales Org and so on, will exist
with the same ID in the target systemt.
This might create a mismatch during
transports, and therefore the requests
might fail.
○ User Assignment
Code List Custom Order Code List Custom Order are automatically
included as mandatory dependencies in all
transports wherever applicable. They are also
Code List Restrictions Select business object, the You don’t need to transport the UI layout to
code to restrict, control field, transfer the code list restrictions as the code list
and the business role from the restrictions is a separate transport object.
value help.
Custom Work Center Select work center or work The new work center created in the target system
center view from the drop may have a different technical ID, however the
down. description is the same as in the source system.
Key User Extension Fields This feature is supported for the following
transport objects:
○ Add-On solutions
○ Business Roles
○ Language Adaptations
○ Form Templates
○ Code List Restrictions
○ Organize Work Centers
○ Custom Work Center
○ Survey
○ Workflow Rules
○ Code List Custom Order
○ Key User Extension Fileds
Restriction
Analytical objects and forms/reports are NOT
considered in these transports.
Local Form Templates Enter the path for the template The form templates must be in published status to
form in the Local Form be included in the transport request.
Template field. The template
path may look like this, for
example, /BYD_COD/
ServiceOnDemand/
Collaboration/
PT_ZCPES_CI_E.QA.uicompon
ent.
Mashups Select a mashup from the ○ You can transport mashups that are created
value help. by customers.
○ You can transport standard or pre-delivered
mashups for which layout changes exist for
changing URL or status of the mashup.
○ If there are mashups with the same ID in the
source and target systems, then the system
compares the content. If the content is same,
then the content is skipped during activation
in target system. If the content differs, the
mashup in the target system is deleted and
recreated with the content coming from the
source system with the same ID. If the
deletion fails, delete the usage and try again.
Restriction
○ Mashups must be in status active to be
included in a transport request.
○ You cannot transport mashups created
by partners. Use the SAP Cloud
Applications Studio deployment.
○ You cannot transport data mashups using
partner created web services.
Organized Work Centers Select a organized work center ○ If a configuration with the same name already
name from the value help. exists in the target system, it will be replaced
with the new transport.
○ Ensure that the dependent work centers and
work center views are scoped and available in
the target system.
Surveys Select a Survey ID from the ○ Surveys imported in the target system is in
value help. the In Preparation status.
○ If the dependent objects such as, products,
product lists, and classifications, are not
available in the target system, then warnings
are raised during assembly and activation.
Workflow Rules Select a description and then ○ The workflow rules are created in the inactive
select a Business Object from status in the target system, and you must
the value help. activate the workflow rules.
○ If email templates are part of the workflow
rules, they are also transported along with the
rules.
○ If PDFs are used in the rule, then you must
assign them to the rule in the target system
before activating it.
Note
Select a transport object and click Add Selected to include it in the transport request. To include all the
objects, click Add All.
3. When you select and add a transport object, mandatory dependencies associated with the transport
object are automatically updated for the object. These mandatory dependencies cannot be removed
unless you remove the transport object from the transport request.
The standard system has hardcoded dependencies that are added to transport objects when they are added to
transport requests. You can add additional dependencies too.
1. Mandatory Dependencies: The standard system proposes mandatory dependencies that include objects
that have a dependency with the selected transport object. You can add further additional mandatory
dependencies if your transport object has been modified in the meantime. Use the Update Mandatory
Dependencies action to manually add mandatory dependencies.
For objects that have been added through mandatory dependency, you can view the list of source objects
having dependency on the selected transport object using action - Explain Dependency. Such objects have
the selection method - Added by Dependency.
Click Action Update Mandatory Dependencies if you need to add new mandatory dependencies. You
can also use this action to add dependencies if objects have been changed since they were last added to
the transport request.
Also, look up the list in this document to understand the mandatory dependencies supported for each
transport object.
Code List Custom Order Key User Extension Fields Adaptation Changes; Add-On Solutions
Key User Extension Fields Key User Extension Fields ( self de Add-On Solutions
pendency for calculated fields from Key
user rules)
Local Form Templates Key User Extension Fields Add-On Solutions (Extension Fields)
Organized Work Centers No Dependencies Custom Work center and Views, Busi
ness Roles and Add-On Solutions
Workflow Rules Key User Extension Fields Add-On Solutions (Extension Fields)
1. In the Target Systems tab, click Add System to open the Select Target System dialog box.
Note
You can select the target systems only if you have already selected the transport objects.
You can see a list of all potential target systems. Under the Selectable head, if the checkbox is selected,
it means that the system can be selected as a target. To add this system, select the line. The OK button
gets enabled. If a target system is not selectable, the system grays out the OK button and displays at
least one message in the Details section explaining the reason. If a system is already added to a
transport request, it does not appear in the list.
1. Click Action Assemble . This triggers a background job to collect all the active objects and package it
in the transport request. The Transport Status changes from New to Assembled.
Tip
2. Click Action Release . This triggers the transfer of the transport request to the target system. The
Transport Status changes to Imported in the target system. In the source system, this information is
displayed in the Target System tab on system line and the transport status is displayed as Released.
To deploy your updates in target system, you must activate the transport request in the target system.
1. Log on to the target system as an administrator. Find and open the transport request that you previously
created under Transport requests Ready for Activation.
2. Click Action Activate . This triggers the deployment of the changes in the target system in a
background job. The Transport Status changes to Activated.
The Transport Logs tab displays the Log Item Severity and the Log Messages. You can toggle between a default
view of the most important log messages, and a more detailed list. The Transport Content tab displays the
zipped content of all transported changes.
When SAP Cloud for Customer is implemented by your administrator, they will define the way your system is
displayed. Since personalization is all about you, tweak the solution into your solution so that it best suits your
working style and uniqueness.
As an end user, you can for example, add your own background image, use drag and drop to easily move screen
sections to another location, set the regional time settings, select whether to display additional onscreen
explanatory text, and manage passwords and certificates.
Go a step further in your personalization experience by adding, changing or hiding labels and adding mashups.
You can also create new queries, change the default queries, and organize the queries in each screen to save
time. The personalization settings that you make on the screen take effect immediately. You can go ahead and
accomplish your daily activities without having to restart the system. If you ever decide to go back to the
original personalization settings, you can set it back to default.
Learn how you can personalize the solution with your preferences regarding system setting, navigation
settings, content, and layout settings with SAP Fiori client.
The following table gives a list of all the UI elements that you can personalize:
Action UI Elements
On the Fiori Client UI, click your profile on the top right corner of your screen, and select Start Personalization.
The system opens the Personalization Mode side pane.
● To select an area on the screen, right click (for Windows) and tap with two fingers (for Mac).
● To directly edit an area, use . The selected area is indicated by and a yellow border. The
corresponding rows,columns, or buttons appear on the right pane.
● To change the sequence of fields, drag and drop them on the right pane using .
For the changes to take effect, click your profile, and select End Personalization. To discard the changes, select
Discard Personalization Changes.
The system remembers your behavior as you navigate the data set view, change the column width and the
action choice you make and displays the selections made the next time you log in.
If last selected action is hidden in certain scenarios, then it does not show as the default selection. Instead the
default selection of quick create component is seen. For example, Save in account creation screen.
Note
The Theme Builder is a tool to create a theme to match the branding of your company. Theme builder gives you
advanced control over the look and feel of your app.
Context
You can customize the look and feel of your solution with your company branding using the Theme Builder.
There are three themes available to use Belize theme - Belize Theme (light) and Belize Deep Theme (dark) and
SAP Fiori 3. SAP Fiori 3 theme is the default theme available and provides consistent look-n-feel across all SAP
C/4HANA products.
Note
Only if you’re using Blue Crystal theme, you see the transition to SAP Fiori 3, as SAP Blue Crystal Theme is
retired and not available for selection. However, if you’re using the SAP Belize, SAP Belize Deep or a Custom
theme, then you aren’t affected by the change.
As an administrator, you can enable the themes under user menu > Settings Branding Theme Builder .
Note
● SAP Fiori 3 theme selection can only be done on desktop and laptop.
● It is recommended to use SAP Fiori 3 theme with the company setting - Enable New Navigation Menu
in Fiori Client
● With November (1911) release, SAP Fiori 3 theme is the default theme, and SAP Blue Crystal Theme is
retired.
● For the first time user, a theme is selected and published by default and applied for all the end users.
However, if you want to define your own custom theme, then click Custom Theme.
Under custome theme, you can make finer adjustments to the color in theme builder via the color picker.
Procedure
1. Access the Theme Builder from the user menu > Settings Branding .
2. Choose Custom Theme. You can see the list of UI elements that you can edit for the company brand.
Default values are set to the previously published theme.
3. Select the hex code or the color box. Selecting the color box shows the color picker overlay and you can
change any color there for the UI elements listed, to a desired state color. For example, you can choose
Global Background and change to the background color you want.
You can view the changes in real time as you change in the UI element.
4. Then, select Save to save the changes.
You have the Clear All button to remove all the custom theme selection in one go. You can also see the
original theme from which the new custom theme is created. For example, If the published theme is SAP
Fiori, and then you chose to select the custom theme, you can see that the custom theme is an extension
of the SAP Fiori theme.
Limitation: Before you select the custom theme from a published theme, you need to refresh the screen to
see the correct theme from which the new custom theme is created.
5. As an administrator you can then publish the theme for all the user by selecting Publish. When the selected
theme is published, the check mark appears for custom theme.
6. Or, if you do not like the changes you made, select Revert to revert to the previous published theme.
○ You can also export a custom theme from the test system and import it into the production system.
○ Custom theme is available only in the SAP Fiori client (responsive user interface), both in the browser
and the extended apps.
Using this tool, you can create a theme to match the branding of your company. The following solution areas
can be customized under custom theme:
● Global
● Navigation Pane
● Detail View
Note
All the custom changes made under the detail view section, are reflected in the new quick view and the
detail view on the user interface.
● Logon Page
Remember
Learn the different ways you can work with queries on each screen.
1. Go to the screen where you want to create a new query. Select the filter icon. Enter the parameters for the
new query. Select Save Query.
2. In the pop-up box, you can give the query a name, and opt to make it your default query.
3. Select Save. A new query is created, and it appears in your default selection drop down list.
Learn how to organize the queries you have created for easy access.
1. Go to the screen where you want to organize your queries. Select the filter icon. Click Organize Queries.
2. In the dialogue box that pops up, you can see all the queries available for the screen. Perform the following
actions:
○ To select a query as your default query, click the radio button next to the name of the query.
○ To remove a query from the list, select the checkbox next to the name of the query.
Note
You can only remove the queries that you have created, and not the once which are pre configured
in the system.
○ To disable object list queries from loading automatically select the Disable checkbox against the query
you do not want to load. When you wish to reload the list, press Click here to execute the query.
3. Select Save. The selected appears as the default query in your default selection drop down list. While the
removed query no longer appears in the list.
You can control the queries that take a long time to execute from automatically loading by using advanced
search and narrowing down the potential result set, before executing the query.
Open advanced search for data lists and select Organize Queries. In the dialog box that opens up, select the
queries for which you want to disable auto initial load.
For example, when searching for a serial Id in a ticket, opening the value help for Serial ID field sets the
customer's context from the ticket. However, service agent may want to search for a serial Id for US based
accounts beginning with 1. Agents can now create a custom query for this, thus overriding the contextual query
to a broader result set.
In value help, the auto execution for the All query is disabled by default.
Disabling the auto execution improves the user experience and performance. You don’t have to wait till the
query is executed, to interact with the UI. For example, if you want to search for a specific term, you can quickly
do so.
To turn on the auto execution for the All query, go to Organize Queries under advanced filter and uncheck the
Disable checkbox for query name All.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use genderspecific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.