101 Enhancement Package 1 for SAP CRM 7.0

7/27/2019 101 Enhancement Package 1 for SAP CRM 7.0

http://slidepdf.com/reader/full/101-enhancement-package-1-for-sap-crm-70 1/38

]

Orange County Convention Center

Orlando, Florida | May 15-18, 2

CRM 7.0 EHP1 - Taking advantage of the major performance

features added to Sales and Service

Sei Drake



Real Experience. Real Advantage.

[

2

Learning Points

Understand the key Sales and Service performance features

released with CRM 7.0 EHP1 to improve usability of large one

order documents

Understand the improvement potential possible by adopting

the features and how they can be leveraged to improve the

usability of document maintenance

An awareness of customizations which may need to be adapted

to take advantage of some of the performance features of CRM

7.0 ehp1




[

ONE ORDER BACKGROUND

3




[ One Order Background – Document Data Model

4

One Order – Header Administration Data

Extensions – Product, Price, Schedule, etc…

Sets – Sales, Partner, Shipping, etc…

Item 1 Administration data

Item 2 administration data

Extensions – CUMULAT_H, Activity, etc…

Sets – OrgMan, Sales, Partner, Shipping, etc…

Item 3 administration data




[ One Order Background – Partner Set example

5

Set – Partner

One Order – Header Administration Data

Role Value

Sold-to ABC Corp

Ship-to ABC Denver

Employee Responsible Halladay

Payer ABC Main

Sets are generic containers which can store multiple kinds of datarepresenting a specific transaction business area:

Partner Set contains multiple roles (Sold-to, Ship-to, etc)




[

EHP1 NEW PRICINGINTERFACE

6


http://slidepdf.com/reader/full/101-enhancement-package-1-for-sap-crm-70 7/38Real Experience. Real Advantage.

[ What is the One Order Pricing Interface

The Pricing Interface is the bridge between the One Order

Transaction Data and the Pricing Engine (IPC)

It listens for changes made to One Order fields and triggers

pricing when necessary

There are 2 pricing interfaces in CRM 7.0 EHP1

The ”traditional” interface used in all previous releases

Will be supported in current and future releases

The “new” interface

Recommended for new implementations and large document

customers Not activated by default - Activation customizable based on

transaction type

Both can be used – Transaction Type customizing

dependent

7

PricingInterface



[ The “traditional” Pricing Interface

The “traditional” interface registers and listens for changes to

specific pricing relevant Sets (example: Partner Set)

Any change to the data in a registered Set triggers pricing

Pro: Pricing is always correct

Cons:

Cannot track pricing relevance below the Set changed level

Slower Response time when changing some non-pricing relevant

fields in *large documents

Dependent on hardware, document size, and pricing complexity

8

PricingInterface

* Large Document: 100+ line items



[ The old Pricing Interface (pre-ehp1) - Example

User changes Employee Responsible at Document header

Pricing Relevant fields Sold-to

Ship-to

Product

Quantity

9

Pricing

Interface

Partner Set chg = yes

IPC

Reprice

Document

Role Old Value New Value

Sold-to ABC Corp

Ship-to ABC Denver

Employee

Responsible Halladay Hamels

Payer ABC Main



[

© SAP

New Pricing Interface

The New Pricing Interface builds a buffer of pricing relevantfields based on a mapping table and the pricing procedure

Mapping tables:

CRMC_CND_FLD - SAP Standard Pricing relevant fields

CRMC_CND_FLD_CUS - Customer Pricing relevant fields

During document maintenance document field changes are

compared to the buffer for pricing relevance

Objects supporting the new pricing interface

Service Contract, Service Contract Quote

Sales Quote, Sales Order, Sales Contract

Service Order, Service Order Quote, Package Quote

Financing (FS) Contract/Quote, FS Multiple Asset Contract

PricingInterface



[ The New Pricing Interface - Example

User changes Employee Responsible at Document header

Pricing Relevant fields Sold-to

Ship-to

Product

Quantity

11

Role Old Value New Value

Sold-to ABC Corp

Ship-to ABC Denver

Employee

Responsible Halladay Hamels

Payer ABC Main

IPC

Sold-to chg = noShip-to chg = no

Product chg = no

Qty chg = no

PricingInterface



[

© SAP

New Pricing Interface - Disable Cross Item Pricing

Group Pricing is a special calculation which must considermultiple items of the document (cross-item) to determine a

value

example: freight cost requires the gross weight of all items

Cross-item (group) calculations are performance intensive

New Pricing Interface feature: Cross item pricing calculations

can be temporarily disabled in the UI for faster editing

Document Save will trigger the cross item calculation

If Cross-item pricing is re-enabled in the UI the cross item

calculation is triggered



[

© SAP


Pros: Significantly improves the response time while editing a large

document

Item pricing calculation still performed

Cons:

One long running step to finalize the (cross-item) calculations

No document totals available until cross-item calculation

triggered



[

© SAP


„Disable the cross item pricing' located under „More‟ button



[

© SAP

New Pricing Interface – Delayed item load mode

Background:

When switching to edit mode in a One Order document the complete

pricing is loaded to the IPC. This can be a performance intensive step

when handling a large document

Delayed item load mode

Prevents the need to load the item data to the IPC until a pricingrelevant change is made

On request loading - when an item is changed/created it is loaded to

the IPC and priced

Only active when cross-item calculations are disabled or unnecessary

Using Delayed item load mode Disable cross-item pricing in display mode prior to document edit

Active by default when no group or structured conditions

exist in the pricing procedure (cross-item customizing

flag set)



[

© SAP


1. User displays a large document

Database

IPC

Document

Pricing

without delayed item load (slide 1 of 2)



[

© SAP


without delayed item load (slide 2 of 2)

2. Clicks Edit

Database 3. Pricing loaded

IPC

Document

Pricing



[

© SAP


with delayed item load (slide 1 of 4)

Database

IPC

Document

Pricing

1. User displays a large document



[

© SAP


Database

IPC

Document

Pricing

3. Clicks Edit

2. Disable cross-item

Pricing




[

© SAP


Database

IPC

Document

Pricing

4. Changes an item

5. Pricing loaded (1 item)




[

© SAP


Database

IPC

Document

Pricing

8. Cross-item pricingperformed

6. Selects save


* Step 7 & 8 will also

occur if cross-item pricing

is re-enabled in the UI

7. Pricing loaded



[

© SAP

New Pricing Interface - Customizing

How to activate this functionality:

IMG> CRM> Basic Functions> Pricing> Pricing in Business Transactions>Performance-Optimized Condition Processing and Pricing



[

© SAP

New Pricing Interface:

Important Enhancement information

CRM_COND_COM_BADI – Not used by the new pricing

interface

New enhancement concept to map custom fields for pricing CRMC_CND_FLD_CUS – Extending the Standard Pricing

relevant fields

Mapping BADIs: IMG> CRM> Basic Functions> Pricing> Pricing

in Business Transactions> Performance-Optimized Condition

Processing and Pricing> Business Add-Ins



[

© SAP

Summary: Features of the New Pricing Interface

Only calls pricing when pricing relevant field values are changed

Temporarily disable cross-item pricing in the UI for faster

document editing

Improve document edit performance by delaying the load of

pricing to the pricing engine until necessary




[

ITEM SEARCH & LARGETRANSACTION MODE

25




[

© SAP

Item Search in Sales Order and Service Contract

Item Search in Sales Order and Service Contract

For large documents an inter-document item search is offered

Extensibility concept available to add new search fields

UI Search Criteria section can be closed




[

© SAP

Large Transaction Mode: Sales Order and Service Contract

Background

Default behavior is to load all items to the Backend UI layer during display

When handling large documents this can have an impact on response time

Large Transaction mode only loads the displayed items of the Service Contract

Activated automatically when a customized item threshold is exceeded

Item Search and Pager load more items to the UI layer




[

© SAP

Item Search & Large Transaction Mode customizing

IMG: CRM> Transactions> Basic Settings> Item List Mode and Item Search




[

BILLING REQUEST LINES

29




[ Service Contract - Billing Request Lines (option)

Billing Request Lines Extension (for Service Contracts)

Traditional Billing Request Items store billing periods as OneOrder items

More items = Slower contract maintenance performance

New Billing Request Lines for periodic billing plans

Uses an item extension to store billing plan periods

Less items = Faster contract maintenance performance

Available for Service Contract (Service Contract Quote)

30




[ Service Contract - Billing Request Lines

31




[

© SAP

Service Contract - Billing Request Lines

Supports CRM and ERP Billing

Periodic billing plans only, no milestone billing

Existing Service Contracts with Billing Request Items still can

be used

No Automatic migration of billing plan items to billing plan lines




[

OTHER PERFORMANCEHIGHLIGHTS

33

[




[ Other Improvements and Activities

34

DB Persistence of cumulated header values instead of calculating values on

display – Improves performance of Document Display

Transaction data is asynchronously Saved to the database using the update

task

Kernel BADIs created for most frequently called BADIs

No automatic migration of traditional BADI code

Wiki page created to collect all tips to improve Performance of CRM

applicationshttp://wiki.sdn.sap.com/wiki/display/CRM/Performance+Tips+and+Tricks

[

http://wiki.sdn.sap.com/wiki/display/CRM/Performance+Tips+and+Tricks

http://wiki.sdn.sap.com/wiki/display/CRM/Performance+Tips+and+Tricks




[

THE RESULTS

35

[




[ Internal test results

36

Testing Documents 100 – 4000 items

EHP1 new features = Response time improvements ranging

from 35% to 90% for all document maintenance steps when

compared to CRM 7.0

General One Order code improvements in EHP1 resulted in a

general improvement of 10-30% without use of the EHP1

features

[




[

37

Key Learnings

Understand the new pricing interface and it‟s features for

improving the usability of one order document maintenance

Understand the inter-document item search and how it assists

users to locate items in large documents

Understand the new billing request lines feature and how they

improve overall document maintenance performance

Understand how to activate the new features and be aware of

adjustments which may be necessary to use them

[



[

] Thank you for participating.

SESSION CODE:

INSERT SESSION CODE

Please remember to complete and return your

evaluation form following this session.

For ongoing education in this area of focus, visit www.asug.com.