C4C PDF

SAP Hybris
Cloud for Customer

Release Conversation
Release Version – August 2016 (16.08)
June 23, 2016
Legal Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of
SAP. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP
has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or
release any functionality mentioned therein. This document, or any related presentation and SAP's strategy and possible
future developments, products and/or platforms directions and functionality are all subject to change and may be changed by
SAP at any time for any reason without notice. The information on this document is not a commitment, promise or legal
obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or
non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no
responsibility for errors or omissions in this document, and shall have no liability for damages of any kind including without
limitation direct, special, indirect, or consequential damages that may result from the use of this document. This limitation shall
not apply in cases of intent or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially
from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only
as of their dates, and they should not be relied upon in making purchasing decisions.
Brand Unification
SAP Cloud for Customer

will now be known as
SAP Hybris Cloud for Customer
Conversation Outline
Purpose
 This conversation is to brief the audience about the August 2016 release of SAP Hybris
Cloud for Customer, public cloud SaaS offering from SAP
Audience
 Solution Key User, Solution Administrator, Line of Business Operations User and related
enterprise functions
Content
 Solution overview
 Upgrade timeline
 Line of Business and Industry solution enhancements
 Configuration options
 Further Training, Engagement, Contact and Information
Omni-Channel Customer Engagement
Anywhere, Anytime
WEB MOBILE IN STORE/ CONTACT DIGITAL MARKET- IOT SOCIAL SMS/ SEARCH DIGITAL EMAIL PRINT AGENT
BRANCH CENTER GOODS PLACE NOTIFICATION KW/ADS ADS TOOLS
EXPERIENCE MANAGEMENT
COMMERCE BILLING MARKETING SERVICE SALES
DATA & PROCESS MANAGEMENT
PLATFORM, INFRASTRUCTURE, INTEGRATION

Enhanced and Updated on a Quarterly Schedule
SAP Hybris Cloud for Customer Innovation Cycle
February May August November
Line of Business Solution
Industry Cloud Solution
User Experience
Packaged Integration
Key User Enhancements

SAP Hybris Cloud for Customer – August 2016 Release Subject to
Planned Timeline Change!
23rd June 2016 – Planned August 2016 Release Conversation with Customers and Partners ~6 weeks to upgrade
22nd July 2016 – Planned Solution Release to Market
23rd July 2016 – Planned Upgrade of Test Tenants ~2 weeks to upgrade
6th August 2016 – Planned Upgrade of Production Tenants Upgrade Day 0

Key Topics for Today’s Session
 Sales
 Mobility & Responsive UI
 Platform & Misc.
 Service
 Integration
 Industry
SAP Hybris
Cloud for Sales
What‘s new in 16.08?
1605 Highlights in Sales – Areas of Investment
 Account/Customer/Contact/Partner
 Lead Management
 Opportunity Management
 Sales Quotes
 Marketing & Marketing Attributes
 Analytics
 Outlook Integration
 Sales Orders
 Product Lists and Products
 Activities
 Visits & Routes
 Surveys
 Promotions
Account, Contact, Individual
Customer, Partner
Automatically Assign the logged in user as the Owner for an
Account/Individual Customer through Workflow
 When creating a new account or
customer, the logged in user can
be defaulted as the “owner”.
 You can enable this feature by
defining a workflow rule that
conducts the assignment.
 Set-up: With new workflow action

‘Assign Me as Owner’ ,an
administrator can now create a
workflow rule which will assign
the logged in user as the owner of
the account /individual customer
as a default during new record
creation.
Account Role in Enterprise Search and Result
 You can now use Enterprise

Search to filter accounts based
on the Role assignment to the
account.
 The Enterprise Search result has
also been enhanced to show the
Role assigned to the account
Contact Merge Enhancement - Delete Relationship for Obsolete
Contact after Merge
 During the merge process, we now
delete all relationship records for the
duplicate contact.
 This ensures that the duplicate
record does not have any
relationship, primarily with the
accounts it was assigned to prior to
the merge.
 Only the ‘Is Replaced by’ relationship
is automatically added for the
duplicate contact.
Access Restriction based on Sales Data – Compatibility Switch
 New Scoping Question that enables

customers to deactivate the Access
Context 1015 compatibility mode, that
we delivered with release 1508.
 This compatibility mode was needed to

make the additional restriction possible
by sales data compatible for end users
 Scoping question : Built-in Services and

Support > System Management > User
Note: and Access Management
 If this Option is scoped, the  If the Option is un-scoped, than the

compatibility mode is active, which sales area restriction of the Access
means that sales area restriction of the Context 1015 (Employee, Territory,
Access Context 1015 (Employee, Sales Data) will always be taken into
Territory, Sales Data) will only be account (independent from any
effective for objects, that have an employees or territories that might be
employee or a territory assigned. assigned to the objects).
Update Identity restrictions based on ‘Works for' relationship
changes
 We now update the identity restrictions

for access restriction rule ‘6-My
workforce’ based on the changes made
to the ‘Works for’ relationship for
employees
• Note : This is a asynchronous update

and is effective with a 1 day delay.
Employee Edit/Create Enabled in an Integrated Scenario
 Prior to 1608 release , it was not

possible to edit & create employees if
Cloud for Customer was integrated with
an external system
 With 1608 release we now allow

employee creation and & editing in
Cloud for Customer in an integrated
scenario.
 Please note that employees created in

Cloud for Customer will not be
replicated to the external application.
 For all the employees created locally in

your cloud solution, the complete
lifecycle will have to be managed within
the cloud solution in order to keep the
master data consistent and in sync with
your external system
Field Extensions are Now Supported for the Partner
Application, the Partner, and the Partner Contact
 You can now add extension
fields to Partner Application in
the Partner Channel scenario
 In addition, you can have these
field extensions flow from the
Partner Application to the
Partner and Partner Contact
following approval of the partner
application.
 To configure this extension

scenario: ‘Channel Partner
Registration Request > General
Information to Business Partner
> General Information’
Other Enhancements
 We have now introduced

business address selection on
contact quick create
 We have also introduced notes
in account and contact quick
create view
 Notes: These attributes will be
personalized hidden.
Lead Management
Lead Notification E-Mail Recipient enhancements
 Contact E-Mail and Individual

customer E-Mail are now available
in order to send out E-mail
notifications from workflow rules.
 These could be used to achieve a
Lead receipt confirmation/follow-up
use case.
Contacts Not Mandatory for Lead Creation
 It is now possible to create

Leads without a Contact
name.
 In order to enable this

feature answer the scoping
question “Do you want to
make contact for leads an
optional field?” in the
affirmative.
Opportunity Management
Activity Timeline: Addition of Visits
 Visits can now be
visualized in the Activities
Timelines of an
Opportunity.
 In addition, a new filter is
now available to view only
the desired activities.
 Status filter is also
available to only show
Activities that are in a
specific status.
Activity Timeline: Designate Internal vs External Activities
 You can differentiate between
Internal and External Activities
in the Activity Timeline of the
Opportunity.
 Key users can now define
whether an activity type is
internal or not.
 If internal, the activity would
show below the date line in
the Activity Timeline,
otherwise it would show
above the date line.
 Visits is turned off by default.

In order to show Visits in the
Activity Timeline, turn it on in
this fine tuning activity.
Buying Center: Contacts Outside of the Account
 Contacts that do not belong to
the Account in question, will be
shown in a diamond shape as
opposed to being shown as a
circle.
 This is applicable to the Buying
Center views within Account,
Contact and Opportunity.
Buying Center – Import Action Enhanced
 “Import from Contact

Relationships” now import
Contact-Employee
relationships in addition to
Contact-Contact
relationships.
Relationships” is now also
available on the graphical
view of the Buying Center,
in addition to the list view.
Buying Center
Relationships” is now being
renamed to “Import from
Contact Relationships”.
Opportunity Migration: Item Notes in Migration template
 Product Notes (Item

notes) can now be
migrated into SAP Hybris
C4C using the migration
templates
Document Flow Refinement for Replicated Documents
 Documents that replicated

to integrated systems
(such as SAP CRM or
SAP ERP, are now
depicted with a downward
arrow under the C4C
document block.
 Upon clicking on the
arrow, the replicated
document with its ID in
the integrated system, is
shown.
Sales Quotes
Sales Quotes
 Authorization Level for External Pricing
 Involved Parties Extensibility
 Ship-To on Item Level
 Enhanced Code List Restrictions: Party Roles, Payment Terms, Reason for Rejection
 Offline Quoting: Set to Lost, Display of Involved Parties Addresses
 Miscellaneous
 Product GTIN part of output sales quote form message
 Display Determination Method for Involved Parties
 Display of Tax Amount (Total and Item)
 Display of Product Category in Product table
Authorization Levels for External Pricing Elements
 You can additionally

restrict read and write
access to price elements
for external pricing, that
allows you to hide certain
conditions, such as profit
margin and cost to certain
users.
 Fine-tuning Activity or
access via view General
Settings in work center
Administration:
Authorization Levels for
External Pricing.
Note: Not applicable to offline

pricing.
Authorization Level for External Pricing
 Fine-tuning Activity ->

External Pricing: External
Pricing Authorization
Levels
Take care that an initial
business role is assigned to the  Fine-tuning Activity ->
max. authorization level once
you like to restrict one business External Pricing: External
role. Pricing Procedures
 Check and compare
customizing in SAP
ERP/CRM concerning
step/level definition.
Take care to set authorization

levels based on step definitions
in SAP ERP/CRM customizing.
Involved Parties Extensibility
 A key user can now

define extension fields for
involved parties tab.
Ship-To on Item Level
 You can now change the delivery

address on item level by
selecting a different Ship-to party
or Ship-to Address or even item
document address.
 Add field via Adaptation or

Personalization.
Enhanced Code List Restrictions
 You can now additionally

restrict the selection of codes
lists in Sales Documents (valid
for Sales Quotes and Sales
Orders) for:
 Party Roles
 Payment Terms
 Reason for Rejection
 Work center Administrator ->

View General Settings: Code
List Restrictions
Display Determination Method for Involved Parties
 A key user can now analyze the

party determination or re-
determination for a sales quote.
 Makes party and redetermination
more transparent for the key
user.
 Add field Determination Method

to Involved Parties table from
hidden field list via Adaptation
mode.
* Note: Party role Account is treated
as manual entry even if the
transaction is copied or created as
follow-up to control party
redetermination once account is
changed.
Display of Tax Amount (Total and Item)
Display of Product Category in Product table
 Add read-only fields Tax Amount (only available for documents that use external Pricing) or Product Category via
Adaptation or Personalization.
Marketing Attributes
Marketing Attributes – ‘Add’ Button Can be Hidden
 You can control who is

allowed to add or edit
marketing attributes.
 Using Business role

configuration ‘Add’ button can
be hidden.
Marketing Attributes – Selection Enhancement
Types of MA Free Text Interval Value Set/Code

 Selection for Marketing
Anything e.g. 111 100 - 200 e.g. Customer, Prospect etc. 100, 200 etc. Attribute has been
Char EQ, NEQ, Contains EQ, NEQ enhanced to allow
Date and Time EQ, NEQ, GT, LT, Bet, GTEQ etc. EQ, NEQ EQ, NEQ, GT, LT, Bet, GTEQ etc.
additional Search
Date EQ, NEQ, GT, LT, Bet, GTEQ etc. EQ, NEQ EQ, NEQ, GT, LT, Bet, GTEQ etc.
Integer EQ, NEQ, GT, LT, Bet, GTEQ etc. EQ, NEQ EQ, NEQ, GT, LT, Bet, GTEQ etc. Operators.
Currency EQ, NEQ, GT, LT, Bet, GTEQ etc. EQ, NEQ EQ, NEQ, GT, LT, Bet, GTEQ etc.
 The table shows the full set
now supported.
Reporting on Marketing Attributes
 Additional fields for Numeric/Quantity/Time/Date/Currency are added for formatted reporting.

These fields can also be used for sorting etc.
Marketing
Campaigns & Lead Scores view on Responsive UI
 We have now enabled

campaigns & lead scores on
Responsive UI.
 *Note: These WoC views are

enabled only for desktop UI.
Dynamic place holder for Account Owner in E-Mail templates
 New dynamic place holder for

assigning account owner in E-
Mail templates.
Workflow for Campaigns
 You can create workflow rules

for campaigns
‘Related-to Account’ default set for Campaign Overview Search
 We now offer a new query ‘Campaigns

Related to Account’ for campaign OVS,
which will select all active campaigns for
the accounts in transactions (for e.g..
leads, opportunity , task , phone call
activity etc.).
Analytics
Navigation from Reports in Responsive UI
Navigation to
Object detail view
Report to Report
Navigation
Manage View and Selection in Responsive UI
You can rename, delete or mark selections and view as default in manage
selections.
Mobile: Download report data as a CSV file in Extended App
 Additional actions are now

available in RUI.
 Export to CSV option is now
available in reports
Enhanced KPI Gauge Pattern in HTML5
 The odometer has been changed to

show variation in three colors.
 The dial is divided based on threshold

values.
 If the current value >= target then the

dial will appear in green.
 When no threshold is maintained the

dial will be divided in Orange and
Green.
Hierarchy view support in Dashboard and Homepage
 You can now configure

Hierarchical charts and tables
on the Home page and in
Dashboards
 One can click on hierarchical
table on Homepage to
expand or collapse hierarchy
for further analysis
 Note: Navigations and
Interactivity is not supported
for Hierarchical reports in
Dashboard
Business Analytics in HTML5 Beta Version
Business Analytics work center is now available in HTML5. Common Tasks is available as separate work center
view.
Hierarchical Selection support for Report-to-Report Navigation
Now you can pass Hierarchical selection

for report to report navigation.
e.g. if you are looking at data at quarterly

Account Hierarchy level and now want to drill down to
Details
territory then you can navigate to another
report where Territory can be passed as
filter and this new report will show you
data for all underlying child territories.
Upload/Download of Dashboard and KPI
You can upload and download KPI & Dashboards to move content from
Development to Test to Production tenants.
SAP Lumira Integration
Data Connector for visualizing SAP Cloud for Customer

data with SAP Lumira  Lumira Integration Add-in is available
for download at the link below:
 https://analytics-
extensions.enter.sap/
 It will also be available for download

from the Download Center
Send Email from Logged-in user
 You can define if you would

like to use default sender ID
or ID of logged-in user for
emailing reports.
Save Filters in variants in HTML5
Now filters get saved along with select parameters in variant/selection.

Analytics: Other Enhancements
 MS Excel Add-in is now supported for Office 2016
 Performance enhancement during dashboard creation preview
 Restrictions on Join DataSource

o Join on Text type fields is no longer allowed
o Joined DS cannot be exposed for ODP extraction
Groupware – MS Outlook
Integration
Topic Highlights
 MS Outlook Integration
 Server Profiles
 Improved handling for obsolete contacts
 Sorting for side-bar entries
 Supportability Matrix
MS Outlook plugin: Server Profiles – Setting Defaults
 Key user can define settings

centrally, which will be
automatically applied to the
add-in, thereby reducing work
for end user.
 The settings are just a
defaulting mechanism. End
user can overwrite them.
 The settings are automatically
downloaded in the upgrade
scenario (1605 -> 1608)
MS Outlook: Improved handling for Obsolete Contacts
 Obsolete contacts are no

longer available in MS
Outlook.
 Contacts which changed
status to obsolete (from
active) will be removed during
the next synchronization
 If it’s changed back to active,
'Synchronize Contacts
Automatically' need to be
checked to re-download it
again.
Sorting for side-bar entries
 You can now manually sort the

entries in the side-bar by
clicking the column headers
MS Outlook: Version Supportability Matrix
 The details for the MS

Outlook versions and Office
license types are mentioned.
This is valid from 16.05.
 Due to many possible
combinations, SAP does
official testing for each add-in
version only on particular
combinations (listed in green).
Enhanced Restriction Rules
 You can now grant data

access based on the
employee and employees
assigned to user’s org. unit
including all sub org units.
 Restriction rule 10 for
Access Context 1015
(Account, Sales
Transactions) Employees
(for Non-Managers).
 Restriction rule 8 for Access
Context 1016 (Activities)
Employees (for Non-
Managers).
 Restriction rule 03 for
Access Context 2008
(Employee + Business
Users) Employees (for
Non-Managers).
Enhanced Party Determination Configuration
 New configuration setting

allows you to disable party
determination for
transactions transferred
from SAP ERP or CRM
 Fine-tuning activity. E.g.

Sales Quotes: Involved
Parties, set Exclude for
relevant party role in column
Inbound Integration.
Sales Orders
Sales Orders
 Copy action on Products facet in Order Details
 Order Items - Support for Custom Line increments – Online and Offline
 Order Items – Renumbering – Online and Offline
 Sales Order Facet available Offline in Account and Individual Customer TI
 External Pricing Document enhancements in Offline Orders
 Custom Involved Parties for Order Items in Offline
 Edit of Ship-to Involved Party for Order Items
 E-Mail Action Available on Completed Orders
 Native Feed Event enabled for Sales Orders

Sales Orders
 Adding products from Promotions Enabled in Order TI – Offline
 Scoping Option to Enable/Disable Offline Pricing
 Account Summary Form – Sales Order Header enhanced with additional fields
 Code List Restrictions - Possibility to restrict by Party Role for Sales Documents
 Sales Order OData Services - Enhancements
 Performance Enhancements
Copy action on Products facet in Order Details
 Ability to copy Order items inline
within the Order Details
 Copy of line item adds a new
row with the next line item
number
 New line item copies over the
following:
 Product ID
 Product Category
 Item Type
 Item Qty
 Manual Conditions
 Extension field values
 Item Parties
 Item Parties – Document Address
 Internal & External Notes
 Pricing does not get copied if Order
has been simulated
 Delivery Status, Billing status and
ATP quantities also, does not get
copied for transferred orders
 Free Goods and Cancelled
products do not have the ‘copy’
function.
Support for Custom Line increments
 Ability to maintain custom line
increments per document type for
Sales Order Items and Sub-Items.
 Maintain custom line increments in

Fine Tuning, per Sales document
type.
 Augmentation of Order items and
Sub-Items in the Order shall appear
inline with the custom increment
that is maintained.
 On Simulation or Transfer of orders
to ERP, line item numbers
maintained in ERP shall take
precedence.
 Feature is available both Online and
Offline.
Order Items - Renumbering
 Ability to renumber order items in

the Products facet of the Order
TI - Online and Offline.
 Users can renumber order items
in the table and tap on
‘Renumber’ in the Actions Menu
to re-organize the order items.
 The newly organized items shall
take into consideration any
custom line increments so
configured, in the new sequence.
 The feature is available to users
in both online and offline modes.
Sales Order Facet available Offline in Account and Individual
Customer Overview
 Sales Order Facets are
now available in both
Accounts and Individual
Customer Overviews in
Offline mode.
 Prerequisite - Enable
‘Sales Orders’ in Offline
setup.
External Price Document enhancements in Offline Orders
 Manually added discounts (of both

types) in offline are now considered
at the time of simulation of Orders
in ECC.
 External Price Documents will be
created for Sales Documents (if
external pricing relevant) at time of
creation of Orders/Quotes/Order
Items in Offline mode.
 Operational Price Elements will be
created for Order Items in Offline
for both %discounts and Absolute
value discounts.
 The pricing will be
created/updated/deleted based on
user update of the order in offline.
Custom Involved Parties for Order Items in Offline
 Ability to add/update or
delete custom involved
parties for Order Items in
Offline mode
 Based on fine-tuning
options, that are setup
for the custom involved
parties, users shall be
able to add, or edit
custom involved parties
for an order item in
offline mode
Edit of Ship-to Involved Party for Order Items
 Ability to edit Ship-To

parties for an Order Item
 Users shall be able to
view and edit the ship-to
party for each order item.
 At the time of creation of
the order item, the ship-to
involved party shall be
inherited from the order
header.
 Users shall also be able to
maintain the document
address for the ship-to
involved party at each
order item.
E-Mail Action Available on Completed Orders
 Users can now send out

E-Mails on completion of
orders
 This is available as an
action, in the actions
menu on completed
orders
 The email is then sent to
the recipient/s with a
summary of the order
attached
Native Feed Event enabled for Sales Orders
 Distinct native feed event

has been enabled for Sales
Orders
 The following events on a
Sales Order can be enabled
to trigger feed notifications:
 Change in Owner
 Change in Lifecycle Status
 Change in Total Value
 Change in Approval Status
 Change in Signatures
 *The feed events were combined for

Sales Orders and Quotes and are now
distinct for each.
Adding products from Promotions Enabled in Order TI - Offline
 Users shall now be able to add

products from promotions while
in offline mode.
Scoping Option to Enable/Disable Offline Pricing
 The existing Sales Price

Specification Scoping
question has been leveraged
to switch on or off the offline
pricing.
 The scoping option now can

be used to enable/disable
offline pricing. The following
pricing fields relevant for
Offline only are disabled if
Offline pricing is switched off
 Discount % (FoE)
 Discount (FoE)
 Discount % (TI)
 Discount (TI)
 The ‘Prices’ WCV under
‘Products’ will also be
disabled when Offline pricing
is switched off using this
option.
Sales Order: Additional Enhancements
 Account Summary Form – Sales Order Header enhanced with additional fields:
 Ship-To Party Internal ID
 Ship-to Party Name
 Code List Restrictions - Possibility to restrict by Party Role for Sales Documents
Products & Product Lists
Product Features
 Support Product Attachments in Offline

 Product OVS Enhancements for Offline
Support Product Attachments in Offline
 User should be able to see attachments in

Offline RUI.
Product OVS Enhancements for Offline
 Product OVS Query “Related to Document”

is made available for offline as well.
Activities
Activities
 Workflow Enhancements
 Contacts/Attendees – Details Enhancement
 E-mails Quick Create – Opportunities/Leads/Sales Quotes
 General Round-offs
Workflow Enhancements
 Ability to assign parties

maintained as custom roles
as workflow e-mail recipient
 Created By/Changed By
(Name) fields in Activity/Visit
workflows
 Create Workflow rules or
utilize these fields as
placeholders
Contacts/Attendees – Detail Enhancement
 Previous behavior – Parties

added to Visit/Activities for
Account for which party has
no business relationship –
Details (e.g. Address/Phone
Number, etc.) are not
displayed
 New behavior – Party
details are displayed even in
scenario where business
relationship with Account
being visited doesn’t exist
E-mail – Quick Create in Leads/Opportunities/Sales Quotes
 Ability to create e-mails from

the Activities facet in Leads,
Opportunities and Sales
Quotes
General Round-offs
 Campaign/Response Option – Advanced Search fields
 Task – Advanced Search Enhancement – Category field
 Tasks Data Source Enhancement – Activity Plan fields (Name/ID)

Visits
Visits
 Performance Optimizations
 One-Time Task Enhancements
 Related Items Table
 Prevention of deletion of Visits
 General Roundoffs
Performance Optimizations
 Optimized performance for background jobs

 Worklist determination for Visits
 Nightly refresh of Visit worklist items/Survey products
Prevention of deletion of Visits
 Ability to restrict deletion

of Visits by Business Role
 Ability to restrict deletion
of Visits in ‘Completed’
status
 ‘Completed’ status delete

restriction requires BC
scoping
Related Items table
 Ability to maintain
reference to predecessor
object/campaign
automatically from follow-
up creation of Visit or
manual addition of
relation
General Roundoffs
 Check-In Enhancement – Set Visit status to ‘In Process’ upon Check In
 Primary Contact field – added to OWL + Advanced Search
 One-off Task Enhancement

 Update Org Unit upon transfer of Task to another Visit
Routes
Routes
 Performance Optimizations
 Add Accounts – Sales Area-specific fields
 Add Accounts – “My Territory Team’s Accounts” query

Performance Optimizations
 Optimized background job for Visit generation from Route

Add Accounts – Sales-area specific fields
 Ability to search for

Accounts to add using
fields maintained at
Account Sales Area level
 Delivered hidden – needs

to be personalized
Add Accounts – “My Territory Team’s Account” Query
 Ability to search for

Accounts to add to a
Route utilizing
Accounts belonging to
a Territory team
Surveys & Promotions
Survey and Promotions
 Odata services for reading C4C survey data
 A2A services for writing data into C4C survey
 Attachment search for surveys and Visit
 Enabling more than 4 answer options for radio button and checkbox type answers
 Enhance - Save as draft functionality
 Performance improvements for Survey
 Creation of Promotion within C4C in an Integration Scenario

oData and A2A services for Survey
Odata Services
 The Odata services would enable the reading of survey results from an external system, thus
providing the flexibility in the usage of C4C survey. These services would efficiently handle high
volume data.
 Both checklist and product type surveys are supported.
A2A Services
 It is possible to write back data into C4C surveys using A2A services.
 The services have been enabled for checklist type surveys only
Attachment search for surveys and Visits
 A single window to search for

the attachments related to
surveys and visits.
 This would help the user in
quickly finding the required
attachments across all
surveys/visit.
 Searching of attachments
based on various parameters
like survey/visit name, account
name, document name etc.
 Predefined search queries e.g
last 7 days, last month.
Enabling more than 4 answer options for radio button and
checkbox type answers
 More than 4 answer options can
be provided for checkbox type and
radio button type answers.
 This would only be valid for non

Matrix surveys.
 For Matrix surveys we would still

have restriction of 4 answer
options for checkbox and radio
button type answers.
Enhanced save as draft functionality
 Save as draft option would

enable the user to save the
partially filled surveys as
drafts.
 The user can later
complete the surveys and
set the status to completed.
 The user need not answer
all the mandatory questions
to save a survey as a draft.
 This option would be
available for all open
surveys
Performance improvements
Performance improvements
 Lazy loading of for surveys having more than 200 products.
 Dynamic product list determination optimization
 JSON optimization
Promotions
Topic Highlights
 Creation of Promotion within C4C in an Integration Scenario

Creation of Promotion in C4C in an Integration Scenario
 A user should be able to create a

promotion in the C4C system in an
integrated scenario, where the
creation of promotion is also
allowed in the back end CRM
system.
 A scoping/configuration would
enable this feature in C4C. Without
switching on this setting the user
would not be allowed to create a
Promotion in C4C for an
integration scenario.
 This would be supported in the
online scenario only
Responsive UI (RUI),
Mobile & Extensibility
1608 Responsive UI (RUI) – Features Overview
 Homepage Enhancements
• Homepage Personalization and Adaptation with groups
• Remove scorecard facet
• When adding tiles, ability to see the tiles that are already visible
• Warning message for number of KPI and Report tiles on the homepage for optimal performance
experience
 Quick create on home screen
 Advance Search – operator support like EQ, GT, LT, etc
 Usability improvement for combo box
 Alternative Visualization for Table view: Chunk View
 Client side persistency for alternative visualization
 Horizontal Scrollbar is displayed for tables with no data
 Swipe Gestures in Smartphones –in Object Detail View
 Vertical scroll - Better utilization of screen space on smpartphone
 Visual Design Enhancements in Calendar
 Supported for Formatted text type extension fields in Edit.
 Notes History enhancements
 Visual Design Enhancements in Calendar
 Disable Quick View based on Company Settings
 Link to launch HTML5 UI
Homepage Personalization & Adaptation
 In Responsive UI Home page
 Key Users can define Tiles that are Available and Visible
by default, for a specific business roles
 End user can remove or add tiles based on what is
allowed for their business role.
Group Tiles for better usability
 Tiles can be collected in a group for easy organization
 Key User and End Users can create, edit and delete groups.
 End users can only delete groups they have created.
Remove scorecard in RUI Homepage
 Scorecard grouping has been removed to simplify
searching for homepage tiles
Ability to see if a tile is already visible on Homepage
 When adding new tiles, administrator can see if the tile is
already available for the role, and is visible by default.
Warning message for number of KPI and Report tiles on the homepage for
optimal performance experience
 Users will now get a warning message when they exceed
recommended number of KPI and Report tiles on the
homepage for optimal performance experience.
 The warning limits are only on
o KPI Tiles = 10 maximum
o Report Tiles = 4 maximum
 Once these limits are reached the user will receive these
warning messages when they try to add more of these
types of tiles.
 Users can still add additional tiles for these tile types, but
doing so will impact performance of the Homepage, and
hence we wanted to warn the key users about it, so that
they can make the best trade-off while designing the home
page for a specific business role.
 There is no limit on List tiles, Tool Tiles and Custom Tiles.
Quick Create on Homepage
 You can create records using the + icon from
home page
 This feature is supported on all form factors –
Desktop, Tablet, Smartphone
 This is launched via the “+” at the bottom left of the
screen
Advance Search – operator support like EQ, GT, LT, etc
 Advance Search has been enhanced to
support operator like
o Equal To
o Greater than
o Greater than or equal to
o Less than
o Less than or equal to
o Between
o Contains pattern
o Is initial
 When defining Query you can “Include” and
“Exclude” multiple searches options
 For multivalued list fields AND/OR condition
are also supported like we did in HTML5
Usability improvement for combo box
 On touch device (Tablet & Smartphone)

o Tap on any area of combo box, to load values.
o Type-in is disabled on touch devices, to avoid keyboard
to take up the space.
Alternative Visualization for Table view: Chunk View
L M S
Table View Chunk View Chunk View - Condensed
Label + Value Value Only
Chunk View
Chunk View (Continued)
Chunk View will be available in Desktop, Tablet & Smartphone. The first 5-7 number of column fields shall be shown on chunk view.
The default view for smartphone and Tablet shall be Chunk view for better touch experience.
List control will be shown as list by default in desktop.
If end user changes the table visualization (Example from chunk view to map view), app will remember this for next time login on same device
for that specific table. Such a personalization is User specific, table specific and device specific.
For chunk view , since we don’t have a concept of leading object in 1608, we will display the first column of table as Title and Navigation shall be
based on what is configured as First Column. If we configure for e.g. Date or Status field as first column, then no navigation will be triggered.
Note: In all result set please ensure that the first column is the main field that supports navigation. For example in Account result set, have
Account Name as first field, so that we supports navigation to Account Detail view from result set.
Chunk view in cozy mode will not show any links. For e.g., if you are account owl, you will not see a link for navigation to owner. Cozy mode will
enable only one navigation which will work based on point 5. Compact mode will show all links in addition to one click navigation based on
leading object described on point 5.
Chunk views configured by applications will no longer be visible on RUI, as they will be replaced by a consistent feature.
Client side persistency for alternative visualization
Based on the last visualization that the

end user selected, the client will
remember it next time.
For example: If for Account, you selected

Map visualization, then next time you click
on Accounts, it will default to Map view,
instead of table view.
Horizontal Scrollbar is displayed for tables with no data
 Horizontal Scrollbar is displayed for

tables with no data, so that user can see
all available columns
Swipe Gestures in Smartphones –in Object Detail View
 Swipe gesture is now supported on Smartphones to

move to next facet
 Swiping in both direction is supported i.e. right-to-left
or left-to-right
Vertical scroll - Better utilization of screen space on smpart phone
Shell Bar Collapsing Tool bar, Shell bar

and Title bar area, as the
user scroll up.
Title Bar On scroll down, the Tool bar
shows up and then
eventually the shell bar and
title bar also show-up.
Tool Bar
Visual Design Enhancements in Calendar
 On smartphone user can see 7-hour work day without having to

scroll. The toolbar collapses to increase space to view calendar
events
 Create events even when offline from the Calendar screen
Extension fields of type formatted text
 User can now Edit and maintain Rich Text in Responsive UI

Notes History Improvements
 Notes are expanded completely by default to improve readability.

o On browser, inline editing is supported
o On touch devices a separate popup is shown to edit notes
 “Collapse All” will collapse all notes to show maximum of 3 lines for
each note.
 Note “Edit” and “Delete” texts have been replaced with icons.
Company setting Remove Quick View in RUI
Reduce one click when you disable Quick View using Company setting.
Link to launch HTML5 UI
 Launch HTML5 link in browser will launch the current screen in a new tab in HTML5.
 This can be used by end user to personalize the screen in HTML5,
 Personalization made in HTML5 will be reflected in Responsive UI.
Extended Edition Mobile Apps
Topic Highlights
 Extended Edition Mobile Apps  Mobile Offline

 Ability to remove Passcode as a  Key-user sync error resolution
company setting  Sync improvements
 Upload files from iCloud
 Check network latency
 Download report data as a CSV file
Ability to remove Passcode using Security Policy
As a security policy you can disable the need to

enter passcode, saving end user a few seconds
each time they open app.
Please note: As per SAP Security Policy, We need

to ship secure, and if customer is ok with disabling
the Passcode as the employee device is secured
with a MDM solution then they will now have an
option to do so.
 Create a new Security Policy (Common Tasks > Edit Security

Policy) or change an existing Policy and Uncheck ‘App Password
Enabled’ under Mobile App Logon Password
iOS: Upload files from iCloud
 You can now upload files from

iCloud as attachments in the
extended application on iOS
Mobile: Check network latency
 You can now check the

network latency within the
Settings screen
 This is helpful to understand
performance issues if you face
any
Switching Off certain features in Offline Mode
 For the Extended Edition Apps the

Online following features are disabled in
the Offline mode:
o Enterprise Search
o Notification
o Report Incident
Offline
o Checking for Updates
o Switching off Tile navigation where
applicable
o Access to Help link
Mobile Offline: Key-user sync error resolution
 A key-user can now see all sync

upload information centrally
 See all uploads made by all users
 Filter for errors
 Option to resolve or discard the
changes which are part of a
particular error
 Monitor overall ‘synchronization

status’
Sync reminders
 Users are now reminded on

switching modes from Offline to
Online that pending changes need
to be synchronized
 Users are also given an option to
synchronize when switching from
Online to Offline mode – this way
they can ensure that they always
have the latest data available
locally.
Offline improvements
 Improved (lower) memory consumption during synchronization across platforms

 Synchronization process is now more tolerant to intermittent network conditions and can recovers gracefully when possible
 Caching mechanism on the server to ensure improved download times for synchronization
 Improved database access routines for faster offline performance
 Data scoping optimizations for faster offline performance
Key User Tools
KUT features
 Model Rule Property(Mandatory, Visible, Read only)

 Defaulting and Filtering values using Code List Restriction
 Include PSM fields in Object Header using KUT
 Mandatory Fields cannot be Hidden
 Support of Rich Text in Formatted Fields
Advance search enhancement
 The code restrictions works also in advance search when selecting values in dependent fields
Code List Restriction – Default Value Beta Version
 Using code list restrictions administrator

user can now default code list value based
on control field.
Model Rule Property Beta Version
 Key User shall be able to define rules to

change property of fields, sections, facets.
 Rule conditions shall be defined based on
the available fields in the UI model.
 Rules are executed only on client and not
on server.
 Since it is a client side logic so user has to
write the logic on each screen.
 Rules run online and offline as well.
 Rules are applied on Master Layout.
Include PSM fields in Object Header Beta Version
 Key User will be able to add PSM enabled fields in the Object Header.
 Currently fields will be Read-only.
Mandatory Fields cannot be Hidden
 Key User cannot hide mandatory fields.

SAP Cloud Applications Studio
1608 Delta Highlights
1605 1608 Type Area Description Details
X  New ABSL OnSave validation – Mandatory error message
X  New ABSL Warning message for Query usage
  New Studio Solution properties – Enhancement
X  New ABSL OnDelete Event
  New LM Production bug fix for pre-production tenants
X  New ABSL DateTime Enhancement
Legend:  available X not available

PDI - OnSave validation - Mandatory error message
Feature: With OnSave validation returning false, the Save is not executed and the user does not get relevant error messages. With 1608, there
is an enhancement in the OnSave validation framework to check if there are error messages returning from the underlying layer. If not, a technical
error message is added to explain which solution is responsible for the rejection.
Business Value: This feature shall provide the relevant error messages to the developer when a Save is rejected. The information shall
provide the solution details that is responsible for the save rejection.
Examples of the Error message

Warning message for query usage
Background: The default QueryByElements execution if used without any
Selection parameter shall lead to a full table scan and may take a longer
runtime execution. In 1608, the following enhancements are done for query usage.
Design Time:
 If no selection parameters are provided for the query execution, the ABSL
compiler shall raise a warning message to caution the developer on a longer
runtime.
 This shall apply for queries on Custom BOs and SAP BOs
Run Time:
A warning message is displayed in UI if the hits
of a QueryByElements exceeds specific value.
Solution property Enhancement
 In 1605 Studio release, two new fields (Detailed Description & Keywords) were
introduced in the solution properties.
 The Detailed Description field that allows developers to add more information/description
about the add-on solution.
 The Keywords field that allows the developers to maintain relevant keywords for the add-
on solution.
 In 1605, these properties were available only for new solutions that were created.
 With 1611 release, these properties shall be maintained for existing solutions.
For existing solutions which were created prior to 1605, these fields shall be defaulted with
the value of the ‘Description’ field in the following cases.
1. When user opens the solution properties, by right clicking on solution name
(original/patch)
2. When patch is created, it will default the fields in both original and patch solution.
3. When the patch solution is uploaded to production tenant, Original solution will be
defaulted with long text and keyword of patch solution.
The user shall be allowed to edit the values of the properties anytime through the lifecycle of
the solution and in all types of tenants (DEV,TEST,PROD).
SAP Hybris Cloud for Service
What’s new in 16.08
SAP Cloud for Service
INTERNET OF CALL
WEB MOBILE SOCIAL EMAIL&SMS CHAT
THINGS CENTER
OMNICHANNEL SERVICE ORDER RESOURCE

SELF-SERVICE SOCIAL SERVICE MOBILE
SUPPORT MANAGEMENT SCHEDULING
CUSTOMER SERVICE FIELD SERVICE
KNOWLEDGE SOCIAL COLLABORATION SALES
ANALYTICS
SAP HANA CLOUD PLATFORM
UNIFY THE CUSTOMER VIEW CLOSED LOOP ENTERPRISE OPEN FRAMEWORK

PROCESSES
Develop a holistic customer view and End-to-end integrated process Leverage existing solutions,
enable complete context automation partners, or build your own
TICKET ENHANCEMENTS
• Involved parties in Ticket

Quick Create
• Ticket Closed status can be
visible on UI
• Ticket Routing by SMS
Channel
• Error-safe email threading
Ticket Management Subject to
Expose involved parties in Ticket Quick Create Change
• See the involved parties

added to a ticket while
creating it
• Remove or add parties as
necessary
• Particularly useful when
Preliminary UI creating tickets as follow
up to existing documents
Ticket Closed status can be visible on UI Change
• Allow Closed status to be

visible on the UI
• Closed tickets are read-
only and cannot be
reopened
• To be used only when the
Preliminary UI specific scenario requires
it, for example for ECC
integration
Ticket Routing by SMS Channel Change
• Ability to route SMS

tickets based on which
SMS Channel received
the SMS
• SMS sent to different
numbers can be routed to
different teams
• SMS Channels will appear
among all other channels
in the Channel column
Preliminary UI
Error-safe email threading Change
• Minimized the number of

possible errors that would
stop an email to become a
new ticket or get added to
an existing one (e.g. SDK
issues on Ticket creation)
• Dangerous attachment will
be removed without
stopping the whole email-
to-ticket process
• Any issue in the email
process generates a
Preliminary UI
notification to the
administrator
CALL CENTER
INTEGRATION
• HTML5: Link phone call to an

existing ticket
• Via IVR
• Manual Select
Call Center Integration Subject to
HTML5: Link phone call to an existing ticket Change
• If a customer is calling
about an existing ticket,
simply select the ticket
from the list at the bottom
of Live Activity
Preliminary UI
• The Phone Call will be
appended to the existing
Preliminary UI
ticket, tracking the multiple
interactions
Support multiple callers as Phone Activity participants Change
• When Live Activity

identifies multiple callers
with the same phone
Preliminary UI number, the agent can
select the correct one
from the Customer Search
• The selected customer is
correctly added as a
participant to the Phone
Call activity, even though
he was not identified
automatically
RUI: Normalized phone number search Change
• Preview of call center

integration in RUI, to be
Preliminary UI
released in 1611/1702
• Support for normalized
phone number search
across customers
Preliminary UI
• Planned enhancements
around supporting full
screen caller identification
and phone call
management
WORKFLOW
ENHANCEMENTS
• Send SMS notifications to

custom parties
• Workflow monitoring:
overall, by rule, by object
Workflow Subject to
Send SMS to custom parties Change
• When defining SMS

notifications, it is now
possible to select custom
parties as SMS recipients
Preliminary UI
Workflow Subject to
Workflow Monitoring Change
• Monitor all rules executed

by the system in the past
or scheduled to be
executed in the future
• For each rule, monitor
which specific objects
have been impacted or
Preliminary UI
will be impacted
• For each object instance,
monitor which rules
impacted it in the past or
will impact it in the future
SOCIAL MEDIA
ENHANCEMENTS
• Include photo in reply

• Instagram integration via
Sprinklr*
*Separate License required for Sprinklr

Subject to
Social Media Enhancements: Include Photo in Reply Change
• On Facebook you can

include a photo when:
• Reply on a post
• Reply on a comment
• Direct message reply
Preliminary UI
• On Twitter you can

include a photo when:
• Twitter post reply
• Single photo attachment

supported
• Twitter direct message

reply not supported
(Twitter restriction)
Subject to
Social Media Enhancements: Instagram Integration Change
• Intagram integration via

Sprinklr
• Configuring Instagram
Preliminary UI Channel through Sprinklr in
C4C
• Single, unified Service
Queue (included with
existing Twitter, Facebook
and Youtube messages)
• Read/Respond to Instagram
response from C4C. Similar
to Twitter, Facebook and
Youtube
REGISTERED PRODUCTS
& INSTALLED BASE
• Offline enhancements
• Registered product –
enhancements in RUI
• Registered Product Location
determination – ship to default
option
• Hierarchical list in Registered
Product items
• Registered Product – New Ticket
from OWL
• Enhanced Web Services
• Installation Point and Installed
Base enhancements
Registered Products and Installed Base Subject to
Offline Enhancements Change
• Installed Base facet now

on Account TI in Offline
mode
• Registered Products
facet now enabled on
Account TI in Offline mode
• The Tickets facet on

Registered Product is
enabled in Offline
Preliminary UI
• The Contracts facet on
enabled in Offline.
 Installed Base now

supports the following My
queries in offline
 My Installed Bases –
Employee Responsible  Creation and recording of Measurements logs and readings depends
 My Installed Bases – on the registered product status (same as it is in online).
Service Technician
Registered Products and Installed Base Subject to
Installation Point Change
 New Facet CHANGES – allows

Changes/Change History to be
tracked
Preliminary UI
 Attachments are now supported
for Installation Points
• It is now possible to reinstate an

Obsolete item by changing the
status from Obsolete to Blocked
(Changing the status from
Blocked to Active was already
possible)
• for Installed Base, Registered

product NOTES supports
Multilanguage based on user
login language
• Installed Base and Installation

Point now support Page Layout
Installation Point Subject to
Add Existing Functional Location Change
 You can now assign an

existing functional
location as a child item
under another functional
location.
 In edit mode, assign the

parent functional
Preliminary UI
location in the Belongs
to Installation Point ID
field.
 Only Active/In
Preparation status are
eligible for this (both for
parent and child
functional locations)
NOTE: Once assigned, the

field cannot be changed.
Offline Subject to
Installed Base on Account Change
• Installed Base facet now

enabled on Account TI in
Offline mode.
Note: In offline mode, this

facet only shows the list of
Installed bases where this
customer is assigned at the
header level.
Preliminary UI
Offline Subject to
Registered Product on Account Change
• Registered Products facet

now enabled on Account TI in
Offline mode
Preliminary UI
Offline Subject to
Tickets on Registered Product Change
 The Tickets facet on

enabled in Offline.
Note: Creation of New ticket

from this facet is not enabled
in offline mode.
Preliminary UI
Offline Subject to
Contracts facet on Registered Product Change
 The Contracts facet on

Registered Product is enabled
in Offline.
Preliminary UI
Offline Subject to
My queries in Installed Base Change
 Installed Base now supports the

following My queries in offline.
 My Installed Bases – Employee Responsible
 My Installed Bases – Service Technician
Preliminary UI
Offline Subject to
Measurements Enhancement Change
 Now in offline mode also, the creation and

recording of Measurements logs and
readings depends on the registered product
status (same as it is in online).
For example for obsolete status, new logs
and readings cannot be created.
Preliminary UI
Registered Product Subject to
Overview in Responsive UI Change
 In Responsive UI, the

following sections are now
supported on the Registered
Product Overview facet
 Sales and Distribution
 Warranty
Preliminary UI
Location determination Change
 Registered Product location

is taken from the customer
address by default.
It is now possible to default
the location from the ship-to-
party address.
 To enable this, scope in the

following question:
Registered Product and Installed

Base -> Group: Additional options Preliminary UI
-> Registered Product uses
customer address as the default
location. Do you want to the use
the ship-to-party address instead?
Location determination Change
 After scoping in the

relevant option, when a
registered product is
created, the location of the
registered product is
determined from the Ship-
to Party’s address (if
maintained)
Preliminary UI
Location Update Change
 It is possible to update the

location of a registered
product if the customer or
ship-to party is updated**.
 Go to Action -> Update

Product Location
**For update, the location is

automatically taken from either the
Customer or the Ship-to Party
depending on the BC scoping Preliminary UI
option for Location Determination
that you select (Refer previous 2
slides).
For example: If the location

determination is based on
customer, ‘Update Product
Location’ will take the location
from the customer.
Items – Hierarchical List Change
 Registered Products Items

are now visible in a
Hierarchical List (H-List)
 You can add new or

existing registered
products at different levels
in the H-List.
 Most Actions in Installed

Base Items H-list are
available in Registered Preliminary UI
Product Items H-List as
well.
New Ticket from OWL Change
 A new ticket can be

created directly from the
Registered Product list.
 If a registered product is
selected from the list,
certain fields, such as,
customer, serial ID,
product etc. are
automatically determined
in the ticket.
Preliminary UI
Query A2X Change
 A new version of the Query

A2X is available for Registered
Product. This has many more
selection parameters to query
registered products which are
not available in the old
version.
 For example you can query

by:
Installation Point ID
Serial ID
Involved Parties Preliminary UI
External ID
Registered Product Category
Change History Change
 It is now possible to track

changes made to an
installation point on the
new facet CHANGES
(Except for Notes and

Attachments – changes to
these are not displayed)
Preliminary UI
Attachments Change
 Attachments are now

supported for
Installation Points
Preliminary UI
Add Existing Functional Location Change
 You can now assign an

existing functional
location as a child item
under another functional
location.
 In edit mode, assign the

parent functional
Preliminary UI
location in the Belongs
to Installation Point ID
field.
 Only Active/In
Preparation status are
eligible for this (both for
parent and child
functional locations)
NOTE: Once assigned, the

field cannot be changed.
Installed Base/Registered Product/ Installation Point Subject to
Status Change
 It is now possible to reinstate an

Obsolete item by changing the
status from Obsolete to
Blocked (Changing the status
from Blocked to Active was
already possible)
 This status change (from

Obsolete to Blocked) is enabled
for all - Installed Base Item,
Registered Product and
Installation Point.
(It was already supported for Preliminary UI
Installed Base header)
 This feature is also enabled in

offline mode for Installed Base
item and Registered Product.
Notes – Multi Language support Change
 Multilanguage support is
enabled for Installed Base
notes.
 Example: Notes maintained in

one language will be visible
whenever the user is logged in
in that language.
If you login in German and
maintain a note (Screenshot
1) this will not be visible when
you login in any other
language (Screenshot 2) Preliminary UI
 Multilanguage support is also

enabled for Registered
Products and Installation Point
UIs
Page Layout Enablement Change
 Installed Base and

Installation Point now
support Page Layout.
 Create a Page Layout

to customize the
screen and assign it to
the required role for
the relevant business
object.
NOTE: Choose Installation Preliminary UI

Point for Registered
Product UI as well.
Installed Base Subject to
Add existing Registered Product Change
OLD – TILL 1605

 Minor change in the way Add
Existing Registered Product
Popup is shown:
The extra “Search” field is removed.

User can directly enter a value in the
ID field or search using the OVS.
NEW – 1608 ONWARDS
Preliminary UI
SERVICE CONTRACTS
• Quantity contracts
• Header document types and page
layouts
• Item Type determination
enhancements
• Exclude Services and Parts
• Item hierarchy
• Offline enhancements
• Contracts in Individual Account
• Authorization levels for External
Pricing
• ECC integration enhancements
Contracts Subject to
Quantity Contracts Change
• Enabled via Business

Configuration/scoping
setting
• A target quantity can be
defined per item in a
Quantity Contract
• When a ticket is created
with reference to a Quantity
Contract, the Release
Quantity and Remaining
Preliminary UI Quantity are updated
• Release History” shows the
list of Tickets that have been
created with reference to a
contract item and release
quantity per ticket.
• Release History information
is available on Contract
Preliminary UI
Header and Item
Document Types Change
• Contract types can be defined in

Business Configuration
Preliminary UI • Define Line Interval steps

during contract creation
with [Sub]Increment
(default=10)
• Code List Mapping for contracts
that need to be replicated to ECC
• It is possible to set an individual
contracts design based on
its type [=purpose] such as
´Service Contract´, ´Maintenance
Contract´, Support/Repair
contract…
and set contracts fields on read
only/ or not visible for users.
Quantity Contracts – BC Setting Change
Preliminary UI
Quantity Contracts –Target Definition Change
• A target quantity can be

defined per item in a
Quantity Contract
Preliminary UI
Quantity Contracts Ticket  Contract Release Change
• When a ticket is created with

Ticket
reference to a Quantity Contract,

the Release Quantity and
Remaining Quantity are updated
Contract
Preliminary UI
Quantity Contracts – Release History [Item] Change
• “Release History”
shows the list of
Tickets that have
been created with
reference to a
contract item
• It also shows the
release quantity per
ticket
3992493
Preliminary UI
Quantity Contracts – Release History [Header] Change
• Release History
information is
available on Contract
Preliminary UI Header and Item
3992493
Header [Document] Types – BC Path Change
• Contract types can be defined in

Preliminary UI
Header [Document] Types – BC & UX Relation Change
 Define Line Interval steps

during contract creation
with [Sub]Increment  To be set for data exchange with external
(default=10) Preliminary UI applications like ECC
Header [Document] Types – BC Creation Change
Preliminary UI
 delivered Value by SAP Standard
 Values created by users

Header [Document] Types – BC Mapping Change
• Code List Mapping for

contracts that need to
be replicated to ECC
Preliminary UI
Header [Document] Types – ECC Mapping Change
C4S:
Preliminary UI
ECC:
Header [Document] Types – Page Layout Change
 It is possible to set an individual

contracts design based on
its type [=purpose] such as
´Service Contract´, ´Maintenance
Contract´, Support/Repair Preliminary UI
contract…
and set contracts fields on read
only/ or not visible for users.
 Page layouts can be assigned by
Business Role of user
…
Item Types Enhancements – BC Path Change
• Contract Item Types can be

defined in Business Configuration
Preliminary UI
Contracts
Item Types Enhancements - Determination Relevance Rules
 Contract Item Types can be defined in
Preliminary UI  Determination relevance rules: Limited to

Entitled Services and Parts = this contract
item will be determined if at least one of the
listed entitled Services & Parts is used in the
ticket item [Example: Entitled Services &
Parts ´Filter X´, ´Repair Service Y´ assigned
to Entitlement Product ´5 Years Support´]
 Items and Entitled Services and Parts = this
contract item will be determined if this item
[product] or one of its assigned Entitled
Services & Parts are used in the ticket item
[Example: Filter X or identical Filter X*]
 Limited to item = this contract item will be
determined only if if this item [product] is
used in the ticket item.
[Example: ´Filter Z´ with 50 each quantity
limit]
 None = this contract item will not be
Subject to determined in the ticket item [Example: Texts
Change like ´following items are result of contract
consilidation done May 15th 2016 …]
Contracts
Item Types Enhancements – Products Assignment (1)
 Use Excel Down &

Upload function to
assign n products
to types/ determination Preliminary UI
relevance rules
3 1
Subject to
4
Change
Contracts
Item Types Enhancements – Products Assignment (2)
Subject to
 [Contains Pattern] Set Categories Change
and.. using (*)Categories
incl. Subcategories to assign n
products to types/ determination Preliminary UI
relevance rules
 [Contains Pattern] Set Products
and using (*) to assign n products
to types/ determination
relevance rules 3
1
2
4
Contracts
Item Types Enhancements –Det. Relev. & dynamic Facets (1)
Preliminary UI
 Items and Entitled Services and Parts = this contract item will be determined if this item [product] or one of
its assigned Entitled Services & Parts are used in the ticket item [Example: Education - Installation…
(here limited to 50 hours] MCD-0443 or Boiler-Calibration-Training MCD-0502
 Type & Determination Relevance Combination: all facets are enabled
Subject to
Change
Contracts
Preliminary UI
 Limited to Entitled Services and Parts = this contract item will be determined if at least one of the listed
entitled Services & Parts is used in the ticket item [Example: any Service from category Ćommercial
heating Services´ assigned to Entitlement Product ´1-Year-Extended Warranty´] Subject to
 Type & Determination Relevance Combination: No Target Definition and Release History Facets Change
Contracts
Preliminary UI
 None = this contract item will not be determined in the ticket item [Example: Texts for grouping purposes like
´Break Fix Box´…]
 Type & Determination Relevance Combination: only General Data and Billing Plan Facets Subject to
Change
Contracts
Preliminary UI
 Limited to item = this contract item will be determined only if this item [product] is used in the ticket item.
[Example: Remote Calibration with 100 hours quantity limit]
 Type & Determination Relevance Combination: No Entitled Services & Parts and Excluded Services & Parts
Facets
Subject to
Change
Item Type Enhancements Change
 Contract Item Types can be defined in

Preliminary UI Business Configuration
 Determination relevance rules
 Product Assignment (via excel) to
relevance rules
 Dynamic UI/Facets based on determination
– All Facets visible when based on product
and relevancy
Preliminary UI
Item Products Enhancements Change
• Text/description can be
added per product/line
item
• It’s now possible to
EXCLUDE Services &
Parts per contract item
• It’s possible to search for
contract based on
ENTITLED or
Preliminary UI
EXCLUDED Services and
Parts
• Contract templates not
only consider Hierarchy
but also, determination
reference and manual
entered pricing
conditions
• ECC Costing assignment
Item Products – Text Items Change
Preliminary UI
Item Products – Excluded Services & Parts (1) Change
Preliminary UI
• It’s now possible to

EXCLUDE Services &
Parts per contract item
Search…
Item Products – Excluded Services & Parts (2) Change
• It’s possible to
search for contract
based on ENTITLED
Preliminary UI or EXCLUDED
Services and Parts
Item Products – Template Enhancement Change
Preliminary UI
 Usage of contract templates considers by 1608 in addition the Hierarchy

[Parent/Child] structure, type, determination reference and manual entered pricing
conditions
Item Products – ECC Costing Assignment Change
Preliminary UI
 If we have [e.g. limited] products on sub item level in contracts these products can also
be determined [-> see Determination Relevance] in the C4S on work ticket item level
and be set there as contract reference (Example: Contract Subitem 3917/101 for Filter
X in ticket line 4711/10). Same applies for the contract reference in the following
ECC invoicing process (Example: use ECC contract 40001548/101 for Filter X)
 In Accounting the costs of such products are often handled differently: Product Costs
should in ECC [needs customizing] be assigned/ related to the main item
(Example: Filter Costs should be posted to 40001548/100 - 1 YEAR GOLD SUPPORT)
Item Hierarchy – Inheritance Header->Item Change
• Status and Contract Validity dates

are inherited from header to
items
Preliminary UI
Item Hierarchy – Inheritance Item ->Sub Item Change
Preliminary UI
• Status and Validity
dates are inherited
from Contract Item
to Sub-item
Item Hierarchy – Inheritance Item Checks (1) Change
Status:  Not possible to activate sub item

if parent item is still ín
preparation´
Preliminary UI
Item Hierarchy – Inheritance Item Checks (2) Change
Item Start/End Date:  Not possible to set a ´Begins on´

date for sub item prior to ´Begins
on´ of relating parent item date
Preliminary UI
Item Hierarchy – manual editable Item IDs Change
 Default Increment by BC
Preliminary UI
Item Hierarchy – Inheritance Header->Item Change
• Status and Contract Validity dates

are inherited from header to
items
Preliminary UI
• Status and Validity dates are
inherited from Contract Item to
Sub-item
• Not possible to activate sub item
if parent item is still ín
preparation´
• Not possible to set a ´Begins on´
date for sub item prior to ´Begins
on´ of relating parent item date
• Editable item ID‘s
• Renumbering based on default
increment set in BC
Item Hierarchy – Renumbering Change
 Renumbering based on default

increment set in BC
Preliminary UI
Contracts
Offline Function Enablements – new Fields
Preliminary UI
Contracts
Preliminary UI
Contracts
Preliminary UI
Contracts
Preliminary UI
Contracts
Preliminary UI
Offline Function Enablements - Attachments Change
Preliminary UI
Offline
Contracts
Offline Function Enhancements – Dynamic Accounts
Navigate from contracts - offline –

to relating Floorplans of..
 Individual Accounts or
Preliminary UI
• Corporate Accounts
Subject to
Change
Contract Facet – Individual Accounts Change
Preliminary UI
Contracts
Determination - Reference Objects on Work Ticket Item –
 Example: Customer
has two Contracts for different
Covered Objects/ Products
Preliminary UI
Subject to
Change
N different Reference Objects on Work Ticket Item Change
 Example: Create Ticket

and assign these Products
as Objects
Preliminary UI
Assign Reference Object on item Change
Preliminary UI
Determination Contract on item Change
Preliminary UI
ECC Contract Integration – Revoke Transfer Status Change
 Via ´Revoke Transfer

Status´ from current
ínterrupted´ to the initial
…ńot started´ or
Preliminary UI
…´finished´ status
ECC Contract Integration – Revoke Transfer Status Change
 Via ´Revoke Transfer

Status´ from current
ín Process´ to the initial
….ńot started´ or
….´finished´ status Preliminary UI
Authorization Control – Contract pricing BC Change
Preliminary UI
Preliminary UI
Preliminary UI
 Set Minimum Authorization Level

to see/ edit Price Components
in Contracts
Preliminary UI
Preliminary UI
 Define for Business Roles Authorization

 Example: Only users with Business Role ´Social Agent´ have the
Minimum authorization [Read/ Write Access] level for ´Profit Margin´ in Contracts
Contracts
Form Message Type Enhancements
Root:
- ProcessingTypeCode + Name
- IncludeBusinessPartnerHierarchyIndicator
Covered Objects:
- Product Category ID + Description
Item:
- ProcessingTypeCode + Name
- ReleaseControlCode + Name
- TargetQuantity
- HierarchyRelationship/ParentItemID
- ItemEntitledProduct/ExcludeIndicator
Parties:
- Product Recipient Party (= Ship To)
- Bill-to Party
- Payer
- Employee Responsible
MAINTENANCE PLANS
• Set Ticket Timeline

Maintenance Plan Subject to
Set Ticket Timeline Change
 For Tickets created from

Maintenance Plans,
user can decide the
ticket timeline –
Requested Start Date
and Requested End
Date determination -
relative to the other Preliminary UI
dates
Ticket Timeline Details

 Provide the values in
Set Requested Start Date From Ticket Creation Date
Ticket Template ->
Ticket Timeline Details Set Requested End Date From Requested Start Date
section ->
Set Requested Start
Date and Set
Requested End Date
 Enabled easy day entry

vs. complete date entry
– while dates are
generated based on day
entry
 For Tickets created from

Maintenance Plans,
user can decide the
ticket timeline –
Requested Start Date
and Requested End
Date - relative to the
other dates
 Provide the values in Ticket Timeline Details

Ticket Template ->
Set Requested Start Date From Ticket Creation Date
Ticket Timeline Details
section -> Set Requested End Date From Requested Start Date
Set Requested Start

Date and Set
Requested End Date
Example: User enters 2 Preliminary UI

days and 4 days in these
fields.
See next slide.

Example continued:
If a ticket is created on 9th June –
The Requested Start Date in the

Ticket will be 2 days from the ticket
creation date, i.e. 11th June.
And Requested End Date in the

Ticket will be 4 days from the
Requested Start date, i.e. 15th June Set Requested End Date From Requested Start Date
Preliminary UI
FURTHER TICKET
ENHANCEMENTS
• Multiple Registered Products

• Item processing code
enhancements
• Add from Product List
• Add Summary with Signature
MULTIPLE REGISTERED
PRODUCTS in TICKET
Preliminary UI
• Ability to add multiple objects on

ticket header
• Link one object to ticket item
• Integration with ECC
Multiple Registered Products in Ticket Subject to
Objects in Ticket Overview and Objects tab Change
• “Main” object in Ticket Overview

• Contract and Warranty
determination based on main
object
• “Main” object also shown in
Objects tab
• One object can be marked as
main object
Preliminary UI
• Contract and warranty
redetermination when main
object is changed
• Possible to add more objects into
the Objects table: Registered
Product, Product, Installation
Points, Installed Base
Add objects Change
Preliminary UI
• Main object can be changed  new contract and warranty determination on ticket header
• Ticket included in the Ticket History of each of the added objects
Objects tab in RUI Change
Preliminary UI
Link ticket items to Serial ID or Installation Point Change
• Ability to link a ticket item to a

Registered Product or Installation
Point in “Add Item” or in Item
details
• “Main” Registered Product is
defaulted
Preliminary UI
Link ticket items to Serial ID or Installation Point Change
• Ability to link a ticket item to a

Registered Product or
Installation Point in “Add Item”
or in Item details
• “Main” Registered Product is
defaulted
Preliminary UI
Integration with ECC Change
• Registered Product on Ticket header: included in Internal Order as

characteristic
• Registered Product on Ticket item: included in Billing Request
item
• IDOC DATA
• Equipment number on Header: included in Internal Order
• Equipment number on Item: included in Billing Request
Preliminary UI
Preliminary UI
Integration with ECC – data in IDOC Change
• Equipment number on Header: included in Internal Order

• Equipment number on Item: included in Billing Request
Preliminary UI
Preliminary UI
Restrictions Change
• Following ticket capabilities are based on the main object on ticket header level, and are not dependent on the
additional registered products in the Objects tab:
• Service Categorization of the ticket
• Routing Rules for the ticket
• Work flow Rules for the ticket
• Tasks for the ticket
• Surveys for the ticket
• Service Location of the ticket
• Reports based on ticket data source
• Warranty determination
• SLA determination
• The registered product shown in Ticket Lists (OWL, Queue, Ticket in Account, …) is the main object. Additional
registered products will not be visible in such lists
ENHANCEMENTS in ITEM
PROCESSING CODE
CONFIGURATION
• Pricing Relevant flag

• ERP Relevant flag
• Scheduling Method
Item Processing Code Subject to
Pricing relevant flag Change
• If an item processing code is flagged

as “Pricing Relevant”, then a ticket
item will be set by default as relevant
for pricing
• This only applies if the ticket type is
also set as “Pricing Relevant”
• The default pricing flag on ticket item
level can be changed by the end-user
• The pricing flag is re-determined if the
Preliminary UI
item processing code is changed by
the end-user
ERP Relevant flag Change
• If an item processing code

is flagged as “ERP
Relevant”, then the ERP
Release status of a ticket
item is set to “Not
Released”
• If an item processing code
is not flagged as “ERP
Relevant”, then the ERP
Preliminary UI
Release status of a ticket
item is set to “Not
Relevant”
• The ERP Release Status
can be changed between
“Not Relevant” and “Not
Released” using item
Ticket Items:
actions
Scheduling Method Change
• The Scheduling Method of an item can be set to:

Blank, Manual or Auto-Dispatch
• Blank = Item is not relevant for scheduling
screenshot
• Manual = Item is relevant for scheduling, and can be
released for scheduling. This will create a demand,
that can be scheduled in the Resource Scheduler
Preliminary UI
• Auto Dispatch = Item is relevant for scheduling, and
upon release for scheduling, a demand and
assignment will be created automatically. The
assignment will be created for the technician with
the least amount of assignments within the
requested start and end date of the ticket item
Ticket Enhancements Subject to
Add from Product List in Ticket AWS Change
Preliminary UI
Add Summary with Signature Change
Customers now have option to add summary with signature i.e. signature can only be captured while generating the Summary
Preliminary UI
Additional fields for the Ticket Summary Template Change
Preliminary UI
Main Ticket Reference in Ticket Migration template Change
• Users can now migrate sub-tickets with main ticket reference.
Preliminary UI
Web Service to provide email interactions for Ticket(s) Change
Preliminary UI
RESOURCE SCHEDULER
• Enhancements in Demand
creation
• Redesign of Resource
Scheduler UI
• Configuration enhancements
Resource Scheduler Subject to
Ticket requires on-site work Change
While creating a ticket the scheduling method

is determined based on the settings at the
processing type code (see configuration
settings below). Here you have the possibility
to overrule the predetermined method as long
as the item is not released for scheduling.
Currently the following is supported:
• No scheduling
• Manual
• Auto Dispatch
This will replace the resource relevance flag in
the future. So far this flag is considered if no Preliminary UI
method is entered.
Manual: Indicates items, which needs a

resource planner to assign a feasible field
engineer to this. Requested start and end
defines the time constraints for the planning
phase and is inherited form the header. The
expected duration for this job is calculated from
the planned quantity of the item. A service
team defines the team which perform this
service. These are essential data, therefore a
check has been introduced if these are not
available.
Auto Dispatch Change
Auto Dispatch: Indicates items which are

planned automatically in the background
looking for a free resource.
The way the resource is determined can be
influenced via PDI.
Once the ticket is ready for planning the work

progress run the action “Release for
Scheduling”. This sends the demand to the
resource scheduler Work Center and sets the
item to “in Scheduling”. Once the demand is
planned the status switches to “ready”.
The ticket status is cumulated on the header. Preliminary UI
The Assignments can be found in the

document flow at the ticket.
Work Center Change
Evolving the Resource Scheduler led to

a complete new layout. The demands
are shown at the left side and provide,
depended on the screen resolution up to
15 demands at once.
The Gantt Chart is shown right beside
the demands list and can show up to 13
resources at once.
Below the planning board a detail
section was introduced showing details
of demands and assignments.
Preliminary UI
Search queries can be used to find
demands and resources. For each
timeframe chosen in the Gantt the
plannable demands are shown.
Different Time Frame Views Change
Different views were optimized to

show as much as possible of
relevant data.
The default startup view can be

defined in user specific settings.
Preliminary UI
Clicking on a day in the Gantt always

jumps to the day view of this day.
The month view is an overview only.

Subject to
Resource Scheduler Change
Every ticket item relevant for dispatching, represents a

demand. Choosing a team starts the search for
unscheduled demands. Queries can be defined to
structure the resources and find the correct data.
Via drag ’n’ drop the demand can is assigned to a

resources for a specific timeframe. After the
assignment is done the demand disappears from the
above list.
When a team is chosen the employees assigned to

this team, which have working times assigned, are
shown in the Gantt area. All resource times are shown Preliminary UI
as local time. 8am in the Gantt is always 8 local
employee time.
The Gantt chart shows assigned demands

(assignments) color codes via status and time to
provide an overview. Every system status can be
assigned to multiple free definable user status, which
can be shown in an own color.
After save the assignments are visible in the

employees calendar. He can directly jump to the
ticket.
Dispatchers helper Change
Longer demands, which does not completely fit into

the day to be dropped will end at 5pm. The remaining
time is shown in the demand section. 20 hours
Remaining time of the demand cab dispatched again

to the same or a different resource. Only 5 hours
15 hours left in the day
Modifying
Preliminary UI
assignments show
new time on the fly
Shifting assignments show

new planning time while
moving
Assignment Details Change
Clicking on a demand in the demand list immediately

shows the details of the demand in the details area
below the Gantt Chart.
If assignments are existing these are shown as well.
Hint: You can define searches to show already

planned demands or demands in a different time
period. Usually only unplanned demands valid for the
used time frame of the Gantt area are shown.
Preliminary UI Assignments now hold two new status. The release

status indicates assignments which should not be
moved anymore, because it is already communicated
to the customer.
The Fix Status limits shifting of the assignment either

in time (it can be moved to a different technician) or
prevents a technician shift as well.
Hint: The assignment is now also available in the

workflow. This means emails can be triggered by e.g.
the release status.
Resource Relevance Change
Defining the resource scheduling

relevance was changed. Now you can
directly assign the default scheduling
method directly at the processing type
code.
The Resource Relevance Flag will be

discontinued.
Preliminary UI
Demand Processing Change
Defining general settings for the resource

scheduler can be done in the fine tuning
section
Preliminary UI
Maintain Colors Change
Defining colors to be used for assignments

in the Resource Scheduler as time-
dependent status and ticket type color
(margin around the assignment)
Preliminary UI
External Status and Time Entries Change
Preliminary UI
Assign the defined color to the respective

status and time.
Additionally you can define if and what

time entry should be created when setting
this status.
Color of Ticket Type Change
You can highlight specific ticket types in Preliminary UI

the Resource Scheduler by assigning one
of the defined colors to a ticket type.
Multiple ticket types can have the same
color to group similar jobs.
VAN STOCK
• Offline stock visibility

• Offline stock search
Van Stock
Offline – Stock
 Stock Work Center is supported in
offline mode.
 Query “My Stock Location” is

supported in offline
Van Stock
Stock – Search
• Search is enabled on the

list of Products in the Stock
TI
• This feature is also

available in offline mode
TIME ENTRY & TIME
REPORTS
• New default query “My Open

Work Tickets”
• Total Duration for a Time Report
• Enable “New” on the Time
Entries facet for Ticket in Offline
• Merge Time Entries
Time Recording Subject to
New default query “My Open Work Tickets” Change
• My Open Work Tickets is

now the new default query
in Ticket value help for
Time Entries.
Preliminary UI
Total Duration for a Time Report Change
• Total Duration for a time

report i.e. the summation
of the duration of all the
time entries for the time
report is now calculated.
Preliminary UI
Enable “New” on the Time Entries facet for Ticket in Offline Change
• User can create new time

entries in offline in Time
Entries facet for Ticket.
Preliminary UI
Merge Time Entries Change
• User can merge time

entries to create a single
Time Item.
Preliminary UI
OFFLINE ENHANCEMENTS
• Involved Party – Add, Delete

• Enable queries “My Work Tickets” &
“Work Tickets with my Involvement”
• Expose involved parties in Ticket
QC
• Contract for Ticket
• Van Stock for Ticket
• Surveys in Ticket
• Serial ID, Installed Base &
Installation Point in Ticket QC
Offline Ticket Subject to
Offline Involved Party – Add Change
• User can now add involved parties which are maintained in the Business Configuration of the Ticket
Preliminary UI
Offline Involved Party – Delete Change
• User can delete involved parties which are maintained in the Ticket
Preliminary UI
Offline Ticket
Enable queries “My Work Tickets” & “Work Tickets with my Subject to
Change
Involvement”
Preliminary UI
Offline : Expose involved parties in Ticket QC Change
• User can add the involved party details in Ticket Quick Create in offline
Preliminary UI
Offline : Contract for Ticket Change
• User can now navigate to Contract from Ticket Overview in offline
Preliminary UI
Offline : Van Stock for Ticket Change
• User can now add product from van stock as Ticket Item in offline
Preliminary UI
SAP Hybris
Cloud for Customer
What’s new in Integration in 16.08
SAP Hybris Cloud for Customer - On-Premise Integration
Release Highlights 1608
C4C Integration with SAP S/4 HANA

• S/4HANA  C4C: Employees, Sales Org Hierarchy, Functional Location, Equipment
• S/4HANA  C4C: Accounts, Contacts, Service Contracts
Integration with SAP ERP
• Work ticket integration passes over registered products and adds them to the ECC billing request (item level registered products) and ECC
internal order (header level registered products)
• Enhanced service contract integration: Transfer additional parties. Transfer contract types and contract item types.
• Bi-directional integration of channel partners between ERP and C4C (without sales arrangement data)
Integration with SAP Hybris Marketing
• Initial load of opportunities C4C  hybris Marketing
Integration with SAP CRM
• Actvity integration now supports attachments
This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP
at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied,
© Subject to change including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement
SAP Hybris
Cloud for Customer
What’s new for Industries in 16.08
SAP Hybris Cloud for Customer - Utilities
Highlights of Release 1608 for Utilities Call Center
The focus of SAP Cloud for Customer for Utilities is on providing a customer call center solution that enables
Utilities companies to engage with and service their B2B and residential customers.
Key capabilities:
 Call Center solution for customers enabling multi-channel service such as social, email, and chat
 360 view of the customer though integration with SAP IS Utilities backend capabilities
Hana Cloud Integration (HCI) for Utilities Customer Overview & Hierarchy
 Update installation/pod level description
Performance Enhancements - Improve ERP response message
 Provide extensibility on highlights/alerts
handling
Mailing Address Handling for Move In / Transfer/ Move Out
Internal/External IDs - Personalization to hide/unhide IDs & hyperlinks
 Add new mailing address during the process
BP Replication - Replicate from C4C to IS-U in contract partner role
Premise Overview & Hierarchy
Extensibility  Enable search for premise by Point of Delivery
 Hide/unhide actions in facets  Ability to add meter reading
 Ability to add new facets  Update installation/pod level
 PSM enablement for replicated objects description
IS-U Finder Bill Correction
 Extensibility for custom search fields  Ability to rebill from the bill correction
 Enhance IS-U finder search fields to include contract ID screen for adjustment reversals
Guided Sales Process Installment Plan Create
 Launch guided sales process in edit mode  Ability to select multiple open items
 Enable search for premise by Point of Delivery  Payment plan type to default fields
 Prospect and status handling
Service Order
 Switch doc status and action to update in quote TI
 Add time stamp to service order
 Extensibility for switch doc
Resources
Resources, Contact, Training and Engagement
SAP Service Marketplace SAP Community Network YouTube Channel
SAP Help Portal SAP Hybris Wiki HANA Marketplace
SAP Training and Certification Incident Management
Subject to Change
Thank You!
SAP Hybris Cloud
for Customer
Release Version – August 2016 (16.08)

C4C PDF

Uploaded by

Copyright:

Available Formats

C4C PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C4C PDF

Uploaded by

Copyright:

Available Formats

SAP Hybris

Cloud for Customer

SAP Cloud for Customer

COMMERCE BILLING MARKETING SERVICE SALES

DATA & PROCESS MANAGEMENT

PLATFORM, INFRASTRUCTURE, INTEGRATION

February May August November

Line of Business Solution

Industry Cloud Solution

Key User Enhancements

22nd July 2016 – Planned Solution Release to Market

23rd July 2016 – Planned Upgrade of Test Tenants ~2 weeks to upgrade

6th August 2016 – Planned Upgrade of Production Tenants Upgrade Day 0

 Set-up: With new workflow action

 You can now use Enterprise

 New Scoping Question that enables

 This compatibility mode was needed to

 Scoping question : Built-in Services and

 If this Option is scoped, the  If the Option is un-scoped, than the

 We now update the identity restrictions

• Note : This is a asynchronous update

 Prior to 1608 release , it was not

 With 1608 release we now allow

 Please note that employees created in

 For all the employees created locally in

 To configure this extension

 We have now introduced

 Contact E-Mail and Individual

 It is now possible to create

 In order to enable this

 Visits is turned off by default.

 “Import from Contact

 Product Notes (Item

 Documents that replicated

 Involved Parties Extensibility

 Ship-To on Item Level

 Offline Quoting: Set to Lost, Display of Involved Parties Addresses

 You can additionally

Note: Not applicable to offline

 Fine-tuning Activity ->

Take care to set authorization

 A key user can now

 You can now change the delivery

 Add field via Adaptation or

 You can now additionally

 Work center Administrator ->

 A key user can now analyze the

 Add field Determination Method

 You can control who is

 Using Business role

Types of MA Free Text Interval Value Set/Code

 Additional fields for Numeric/Quantity/Time/Date/Currency are added for formatted reporting.

 We have now enabled

 *Note: These WoC views are

 New dynamic place holder for

 You can create workflow rules

 We now offer a new query ‘Campaigns

 Additional actions are now

 The odometer has been changed to