Вы находитесь на странице: 1из 13

I S - U /C R M I n t eg r a t i o n :

Replicati on of Prices fr om SAP CRM


in Conju nction wit h the
SAP IS-U Master Data Generator

S AP C R M R e l e a s e 7 . 0
Enhancement Package 3
Support Package 5
Copyright
2014 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and
notices. Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors. National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without
representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP AG or its affiliated companies have 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 AGs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be
changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this
document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. 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.
Introduction
This document describes the replication of prices from the CRM document to the ERP system. For
information about defining prices in the CRM system, see the document "Quotation Calculation - Sales
Process for Commercial and Industrial Customers on SAP Service Marketplace at
http://service.sap.com/utilities -> SAP for Utilities Product Information -> SAP CRM for
Utilities -> Cookbooks&Guidelines.

The master data generator is used to replicate prices from the CRM system to the ERP system. To
ensure this is possible, you must define the price nodes at two levels in the master data generator.
You can choose between three different procedures here:

You combine a node with the QPRICE category with a node with the INST_FACTS_QPRICE
category to replicate a quantity-based price.
QPRICE generates the quantity-based price, INST_FACTS_QPRICE generates an installation
fact with the operand to which the key for the quantity-based price is assigned.
As of SAP ERP 6.0 enhancement package 5, you are using the node with the QPRICE_NEW
category together with a node with the INST_FACTS_QPRICE category.
The node with the QPRICE_NEW category is easier to use and more flexible in its handling
than QPRICE. As of Release SAP ERP 6.0 enhancement package 5, we recommend using
QPRICE_NEW instead of QPRICE.
As of Release SAP ERP 6.0 enhancement package 7 SP 06, you are using a node with the
QPRICE_FIX category to generate quantity-based fixed prices. To create installation facts
with quantity-based fixed prices, you must activate nodes with the INST_FACTS_QPR_FIX
category.

In the following, we will only describe replication of quantity-based prices. Time-based prices that
have nodes with the TPRICE, TPRICE_NEW or TPRICE_FIX category can be replicated in the same
way. We use nodes with the LPRICE, LPRICE_NEW or LPRICE_FIX. category for flat-rates.

Price Replication with QPRICE


Design
First, you have to activate the QPRICE (Quantity-Based Price) node in a template with the category
CRMNEWCONTRACT (Create New Data in Conjunction with SAP CRM).

You can use nodes with this category to create or change quantity-based prices. Prices are selected in
the field Price Origin using the value "CRM". You cannot change these prices in the IS-U system using
the transaction EA90 (Change Price).

You can also use these nodes to create or change historical prices. This means that several
historically separate price amounts can exist for a price header.
The attribute PRICE represents the price key. Use "Parameter" to fill this attribute. You define the
other attributes in the characteristics for the price header.

When you activate the subnode QPRICE_HIST (Price History for Quantity-Based Price), the system
displays a dialog box where you have to enter the number of nodes or time slices to be generated,
and the pricing condition.
Based on this information, the master data generator generates n nodes with the category
QPRICE_HIST (Price History for Quantity-Based Price), and the parameter names, which are
compiled as follows:

PR_
<Pricing Condition>_
<Sequence Number>_
<Name of Attribute>

These parameter names correspond to the values that are written to the container for the master data
generator during contract replication from SAP CRM. The algorithm used to determine the parameter
names is identical in SAP CRM.
You also have to activate the nodes with the category INST_FACTS_QPRICE (Installation Facts:
Operand Category QPRICE) and allocate the same parameters to the attribute PRICE that you used
for the same attribute in the QPRICE (Quantity-Based Price) node. This multiple use of
parameter names ensures that the price and its history are saved in the correct installation facts.

Use an operand as a value for the attribute OPERAND for which the field Product-Related Operand is
selected.

The same applies to the nodes TPRICE (Time-Based Price) and LPRICE (Flat-Rates).

Runtime
At runtime, when you create a new contract, the system generates a new price key for each node with
the category TPRICE (Time-Based Price), QPRICE (Quantity-Based Price) und LPRICE (Flat-Rates),
and transfers historical values from SAP CRM to the price keys. Following this, when the installation is
processed, only the price key is written to the relevant installation facts (nodes with the category
INST_FACTS_*). This ensures that a price or price key is only used in one installation or contract.

This means that if you then change a contract and the price key at the same time, the changes affect
one contract only.

You can prevent a price that is replicated from the CRM system to SAP ERP being allocated to a
different installation manually. To do so, in the node INST_FACTS_QPRICE, activate the subnodes
with the category QPRICE_INST_ASSIGN Allocate Quantity-Based Price to Installation. If you activate
these nodes, the key for the utilities installation is entered in the price header. This means that the
price becomes an installation-specific price and can only be used in this installation.
Price Replication with QPRICE_NEW
Design
The disadvantage of replicating prices that have nodes with the category QPRICE is that you have to
define a fixed number of subnodes with the category QPRICE_HIST. Complete replication of price
data from CRM to ERP is only possible if the number of nodes with the category QPRICE_HIST is at
least as large as the amount of price data. You can use the generation assistant to activate a large
number of nodes with the QPRICE_HIST category. However, this means that the master data
template can become confusing.

You can avoid these disadvantages by activating nodes with the QPRICE_NEW category instead of
QPRICE. These nodes are available as of SAP ERP Enhancement Package 5. In the case of
QPRICE_NEW, there are no explicit subnodes with the category QPRICE_HIST. The master data
generator expects the container to contain price data with the same naming conventions as those
used to process it in QPRICE_HIST. You define the pricing condition, which is part of the naming
convention, using the attribute PRICECONDITION.

Runtime
At runtime, the node QPRICE_NEW responds in the same way as the nodes QPRICE and
QPRICE_HIST. The amount of price data is determined dynamically and a price is generated with the
corresponding number of historical price amounts.

Price Replication with QPRICE_FIX


What Are Fixed Prices?
As of Release SAP ERP 6.0 enhancement package 7 SP 06, the following nodes for fixed prices are
available to you in the master data template category CRMNEWCONTRACT:

QPRICE_FIX Quantity-Based Fixed Prices


TPRICE_FIX Time-Based Fixed Prices
LPRICE_FIX Flat-Rate Prices

A fixed price has the following characteristics:

Fixed prices are created using the master data generator. They are selected in the price
header using the value CFX (CRM fixed price).
A fixed price cannot be changed. This affects both the data in the price header and the price
history. A fixed price cannot be deleted.
A fixed price only has one price amount. This price amount is historically valid without
restriction.
A fixed price only has one currency.
Fixed prices cannot be defined as average prices or using a price adjustment clause.
Fixed prices in the IS-U system cannot be changed using the transaction EA89(Create Price)
and EA90 (Change Price). They can however be displayed using the transaction EA91
(Display Price).

The main advantage of fixed prices is that they can be reused without restriction. They can be used in
installation facts for various installations, since it is not possible to make unauthorized changes to
them. Price changes to an installation are modeled by changing the fixed price key in the installation
facts. This does not affect the installation facts for other installations.

If you are using standard prices, you must create a new price for every installation. This is the only
means of ensuring that price changes only affect the installation required. However, this may lead to
the creation of a large number of redundant prices with identical characteristics.

Example of using standard prices:

You create a quotation in SAP CRM for 100 installations. The same price is to apply to all
installations.
You are using a node with the category QPRICE_NEW in the master data template.
During contract replication, the system generates 100 identical prices and allocates them to
the facts for an installation in each case.

Example of using fixed prices:

You create a quotation in SAP CRM for 100 installations. The same price is to apply to all
installations.
You are using a node with the category QPRICE_FIX in the master data template.
During contract replication, the system creates a new fixed price. Its price key is used in the
facts for all 100 installations.

When the master data template is executed, the system checks whether a fixed price with the required
characteristics already exists. If this is the case, this price is used. If this type of fixed price does not
exist, the system creates a new fixed price.

Fixed prices are ideally suited to products with a price guarantee.

Example:

You define a product with a 12 month price guarantee in SAP CRM. This means that the price
is not changed for 12 months for every contract that is signed with this product. However, the
price changes according to the contract start. This means that an IS-U rate that defines the
price using the rate facts is not suitable.
You are using a master data template with fixed prices for the product. During the CRM
quotation process, you determine the required price according to the contract start.
During contract replication, the requested fixed price is created once and then reused for all
contracts until the guaranteed price changes in the CRM system.

It does not always make greater economic sense to use fixed prices in relation to the data volumes
generated in the IS-U system instead of standard prices. If during the quotation process for
commercial and industrial customers, you always calculate the price down to a large number of
decimal places, the "number of hits" and therefore the frequency of reuse is fairly low. Historical price
changes must also be represented by separating the installation facts. In the case of a product with 12
monthly prices, replication produces up to 12 new fixed prices and 12 separated installation facts.

You should therefore use fixed prices where possible in the following situations:

For products with a price guarantee


For quotations for a large number of installations
For prices with a small number of decimal places in the price amount
More Information

You should always fill the PRICE (price key) attribute using the Parameter supply type. It does
not make sense to specify a value for these parameters in the container, since no change
mode is available for fixed prices. The node can also generate or identify several fixed prices
in a general example. The parameter name is only required as a connection to the node for
installation facts.
To allocate a quantity-based fixed price to an operand for the installation facts, you must use a
node with the INST_FACTS_QPR_FIX category. The connection of QPRICE_FIX to
INST_FACTS_QPRICE is not allowed.
It does not usually make sense to define nodes with the category QPRICE_FIX as dynamic. If
no historical price data is found in the container, the node is terminated without an error
message and without a generated fixed price.
In the case of IS-U contracts, the move-in or move-out date can be changed subsequently
under certain circumstances. In the case of contracts with fixed prices, you can only make
these changes using the CRM system. Adjust the validity periods for the prices accordingly.
You cannot change the move-in or move-out date using the IS-U transactions EC51E (Change
Move-In) or EC56E (Change Move-Out).

Prerequisites
Note

The integrated search for a fixed price in the master data generator requires you to activate an
additional index for the database table EPREIH.
Activate the SAP-defined "index for fixed prices" using the index fields PREISBTR and
ABDATUM, if you are using the nodes QPRICE_FIX, TPRICE_FIX or LPRICE_FIX in a
master data template or create a comparable index.

Design
If you want to replicate prices from SAP CRM as fixed prices, you must activate a node with the
category QPRICE_FIX in the master data template with the CRMNEWCONTRACT category.
Specify a pricing condition for the attribute PRICECONDITION. The pricing condition defines the
parameter names used to find price data in the container using the same rules as those for nodes with
the category QPRICE and QPRICE_NEW. In the case of QPRICE_FIX, there are no explicit nodes for
the price history, as is also the case for QPRICE_NEW.

You also have to activate the node with the category INST_FACTS_QPR_FIX (Installation Facts:
Operand Category QPRICE Fixed Price) and allocate the same parameters to the attribute PRICE that
you used for the same attribute in the QPRICE_FIX (Quantity-Based Fixed Price) node. This
multiple use of parameter names ensures that the price and its history are saved in the correct
installation facts.
Use an operand as a value for the attribute OPERAND for which the field Product-Related Operand is
selected.

The same applies to the following combinations of nodes:

TPRICE_FIX Time-Based Fixed Prices and INST_FACTS_TPR_FIX Installation Facts:


Operand Category TPRICE Fixed Price
LPRICE_FIX Flat Rate Fixed Prices and INST_FACTS_LPR_FIX Installation Facts: Operand
Category LPRICE Fixed Price

Runtime
If new contract is created in SAP CRM during runtime, the system transfers and replicates the
historical price data to the container. Parameter names are represented using the pricing condition.
When nodes with the category QPRICE_FIX are processed, the system analyzes the historical price
data. The master data generator checks whether a corresponding fixed price is already available for
every price. If this is the case, the price key for the fixed price is noted internally by the system. If this
type of fixed price does not exist, the system creates a new fixed price. The system ignores price
periods in this step, since fixed prices are always valid without restriction.

Example:

You generate a contract with a 12 month validity period in SAP CRM. You negotiate a new
price amount for each month. During replication, the node with the category QPRICE_FIX
analyzes the historical price data. It finds suitable fixed prices for 10 price amounts and
makes an internal note of the price key. It creates new fixed prices for 2 additional price
amounts and also saves their key.

The node with the category INST_FACTS_QPR_FIX is then processed. This node transfers
the price key that was previously determined or generated using the node with the
QPRICE_FIX category. Time slices for the facts are transferred from the historical price data.
The node with the INST_FACTS_QPR_FIX category transfers the 12 price keys and their
associated time slices from the node QPRICE_FIX. It generates an installation fact for a price
operand with 12 separate values.