pricing in sap eco

Table of Contents1 Pricing in SAP E-Commerce for SAP ERP................................................................. 11.1 Deployment Scenarios..............................................................................................................11.1.1 Business-to-Business (B2B) Application......................................................................................1

1.1.1.1 List Prices in Web Catalog and Shopping Basket....................................................... 11.1.1.2 IPC Prices in the Web Catalog/Shopping Basket Prices are Taken from the Web

Catalog .................................................................................................................... 21.1.1.3 IPC Pricing in the Shopping Basket ........................................................................... 3

1.1.2 Business-to-Consumer (B2C) Application....................................................................................41.1.2.1 List Prices in the Web Catalog and in the Shopping Basket........................................ 41.1.2.2 IPC Prices in the Web Catalog/Shopping Basket Prices are Taken from the Web


1.1.3 Business-to-Business (B2B) for Occasional Users.......................................................................61.1.4 Business-to Business (B2B) for Internal Users.............................................................................6

1.1.4.1 List Prices in the Web Catalog and Shopping Basket ................................................. 61.1.4.2 IPC Prices in the Web Catalog/Shopping Basket Prices are Taken from the Web


1.1.5 Business-On-Behalf (BOB) Application/Reseller Scenario ...........................................................71.1.5.1 List Prices in the Web Catalog and in the Shopping Basket........................................ 71.1.5.2 IPC Prices in The Web Catalog/Shopping Basket Prices are Taken from the Web


1.2 Summary: Settings That Influence Pricing in SAP E-Commerce for SAP ERP......................81.3 How to Extend Pricing ..............................................................................................................81.3.1 On J2EE Side .............................................................................................................................81.3.2 On ABAP Side ............................................................................................................................91.3.3 SAP Notes ................................................................................................................................101.4 Upgrading from SAP E-Commerce for SAP ERP 4.0 to 5.0...................................................101.4.1 System Setup............................................................................................................................101.4.2 Pricing-Relevant Header Attributes............................................................................................101.4.3 Pricing-Relevant Item Attributes ................................................................................................10

1 Pricing in SAP E-Commerce for SAP ERPThis document describes pricing in SAP E-Commerce for SAP ERP pricing features. It lists the main ideasfor each deployment scenario and also the available attributes that can be used for pricing.

This document does not cover the handling of business transactions like orders, quotations, and inquiries,as we only display the results of SAP ERP pricing here. The same is true for the order checkout (ordersimulation).This document does not consider features like free goods or bill of materials, as they are notsupported in the E-Commerce ERP shopping basket. This document covers the upgrade from SAP E-Commerce for SAP ERP 4.0 to 5.0 and the options for extending pricing.

1.1 Deployment Scenarios

1.1.1 Business-to-Business (B2B) Application

1.1.1.1 List Prices in Web Catalog and Shopping Basket

You enable the use of list prices in the Web catalog via the attribute ‘Controlling Price Determination in theCatalog’.

In this deployment scenario, Internet Pricing and Configurator (IPC) is not involved in pricing. The Webcatalog and shopping basket prices are determined via ERP pricing. The prices are saved in the Webcatalog index, or read from the Web catalog at runtime, and are not re-determined in every user session.

© SAPDietmar-Hopp-Allee 16

Page2 of 11

The pricing procedure used is calculated in a similar way to that in the ERP sales order: sales area,customer procedure (from the reference customer of the Web catalog), and business transaction schema(which is directly entered for the Web catalog) control the determination of the pricing procedure. For moreinformation, see transaction WWM3 in the SAP GUI.

For configurable items, IPC pricing is always performed because in principal the characteristic valueassignment can influence prices. If this is not desired, for example, for performance reasons, set flag‘preventIPCpricing’ to ‘true’ in the Web catalog component of the Extended Configuration Managementapplication (XCM). Check the following section on the determination of the pricing procedure and the list ofavailable fields.

1.1.1.2 IPC Prices in the Web Catalog/Shopping Basket Prices are Taken from the Web Catalog

You enable the use of IPC prices in the Web catalog via the attribute ‘Controlling Price Determination inthe Catalog’.

In this case, the prices for the Web catalog items are calculated dynamically. This allows more flexibility,for example, customer-specific discounts can be taken into account. Note that no group conditions areprocessed in this case, as there is no dependency between different Web catalog items in the same area.

When a product is transferred from the Web catalog to the shopping basket, its price is copied.

For the calculation of the pricing procedure, you need the sales area, the customer pricing procedure, andthe business transaction schema.

Sales area (sales organization, distribution channel,division)

From E-Commerce Web shop.

Customer pricing procedure From sold-to party. Takes sales area into account.

Business transaction schema From the first order type that is specified in the E-Commerce Web shop as valid for E-Commerce.

Function module ISA_FIND_PRICING_PROCEDURE performs the determination of the pricing procedure.If there are problems, it makes sense to examine it. The function module also takes care of the sales areabundling.

A precondition for the use of a specific pricing procedure for IPC catalog pricing is that all field attributes ofall used condition types are available. In the following table, you can find the available attributes.

Source = SAP ERP: data is read from the current sold-to party in SAP ERP.

Field Level Source Description

ALAND Header Shop Departure country

AWAHR Header ERP Order probability

HEADER_SPART Header Shop Division

INCO1 Header ERP Incoterms 1

KDGRP Header ERP Customer group

KONDA Header ERP Price group (customer)


Page3 of 11

KUNNR Header ERP Customer

KURST Header ERP Exchange rate type

LAND1 Header ERP Country

PLTYP Header ERP Price list type

STCEG Header ERP VAT registration number

TAXK1-TAXK9 Header ERP Tax classification

VKORG Header Shop Sales org

VTWEG Header Shop Distribution channel

ZTERM Header ERP Terms of payment key

WAERK Header ERP Document currency

BONUS Item ERP Volume rebate group

KONDM Item ERP Material pricing group

MVGR1-MVGR5 Item ERP Material group

PMATN Item ERP Price material

PRODH Item ERP Product hierarchy

PROVG Item ERP Commission group

SKTOF Item ERP Cash discount indicator

TAXM1-TAXM9 Item ERP Tax classification material

Function module ISA_PRICING_HDRDATA_GET reads the attributes at header level and takes care ofsales area bundling, which means that the reference distribution channel and division are taken intoaccount for reading the customers’ sales data. These attributes are read in each user session.

For the item attributes, the system behaves differently, depending on the Web catalog scenario.

If TREX is used, the pricing-relevant attributes are saved with the Web catalog data. In this case it is notnecessary to find these attributes in every user session. At replication time, the attributes are read inmethod IF_ISA_REPLICATION_CATALOG~IPC_ATTRIBUTE_VALUES_GET of classCL_ISA_REPLICATION_CATALOG.

If TREX is not deployed (in the case of small catalogs), the IPC-relevant item attributes are read withISA_PRICING_ITMDATA_GET. This happens in every session.

Both ways of reading the item attributes take sales area bundling into account, which means that if acommon distribution channel exists, the material sales attributes are read for this distribution channel.

1.1.1.3 IPC Pricing in the Shopping Basket

This scenario is similar to that described in the previous section. The determination of the pricingprocedure, and the list of available fields are the same.

In this scenario, the Java shopping basket performs separate pricing for its items instead of asking theWeb catalog for the price information. To trigger this function, set XCM scenario ‘forceIPCpricing’ to ‘true’in the Java shopping basket component.

Reasons for choosing this variant:

- Group condition processing is necessary


Page4 of 11

- Customer-specific pricing is necessary, but for performance reasons for the Web catalog, listprices should be displayed

1.1.2 Business-to-Consumer (B2C) ApplicationIn all cases, pricing in the order checkout, confirmation, display, and change screens originates in SAPERP.

1.1.2.1 List Prices in the Web Catalog and in the Shopping Basket

You enable the use of list prices in the Web catalog via the attribute ‘Controlling Price Determination in theCatalog’.

In this deployment scenario, IPC is not involved in pricing. The Web catalog and shopping basket pricesare determined via ERP pricing. The prices are saved in the Web catalog index and are not re-determinedin every user session.

The pricing procedure used is calculated in a similar way to that in the ERP order: sales area, customerprocedure (from the reference customer of the catalog), and business transaction schema (which is directlyentered for the Web catalog) control the determination of the pricing procedure. For more information, seetransaction WWM3 in the SAP GUI.

For configurable items IPC pricing is always performed, because in principal the characteristic valueassignment can influence prices. If this is not desired, for example, for performance reasons, set flag‘preventIPCpricing’ to ‘true’ in the Web catalog component of the Extended Configuration Management(XCM) application. Check the following section on the determination of the pricing procedure and the list ofavailable fields.


You enable the use of IPC prices in the Web catalog via the attribute ‘Controlling Price Determination inthe Catalog’.

In this case, the prices for the Web catalog items are calculated dynamically. Note that no group conditionsare processed in this case, as there is no dependency between different catalog items in the same area.

When a product is transferred from the Web catalog to the shopping basket, its price is copied.

For the calculation of the pricing procedure, you need the sales area, the customer pricing procedure, andthe business transaction schema.

Sales area (sales organization, distribution channel,division)

From E-Commerce shop

Customer pricing procedure From reference customer (Web shop setting). Takesales area into account.

Business transaction schema From the first order type that is specified in the E-Commerce Web shop as valid for E-Commerce.

Function module ISA_FIND_PRICING_PROCEDURE performs the determination of the pricing procedure.If there are problems, it makes sense to examine it. The function module also takes care of the sales areabundling.


Page5 of 11

A precondition for the use of a specific pricing procedure for IPC catalog pricing is that all field attributes ofall used condition types are available. In the following table, you can find the available attributes.

Source = SAP ERP: data is read from the current reference customer in ERP.



AWAHR Header ERP Order probability

HEADER_SPART Header Shop Division

INCO1 Header ERP Incoterms 1

KDGRP Header ERP Customer group

KONDA Header ERP Price group (customer)

KUNNR Header ERP Customer



PLTYP Header ERP Price list type



VKORG Header Shop Sales org

VTWEG Header Shop Distribution channel

ZTERM Header ERP Terms of payment key










Function module ISA_PRICING_HDRDATA_GET reads the attributes at header level and takes care ofsales area bundling, which means that the reference distribution channel and division are taken intoaccount for reading the customers’ sales data. These attributes are read in every user session.

For the item attributes, the system behaves differently, depending on the Web catalog scenario.

If TREX is used, the pricing-relevant attributes are saved in the Web catalog data. In this case, it is notnecessary to find these attributes in every user session. At replication time, the attributes are read inmethod IF_ISA_REPLICATION_CATALOG~IPC_ATTRIBUTE_VALUES_GET of classCL_ISA_REPLICATION_CATALOG.


Page6 of 11

If TREX is not deployed (in case of small catalogs), the IPC-relevant item attributes are read withISA_PRICING_ITMDATA_GET. This happens in every session.

Both ways of reading the item attributes take sales area bundling into account, which means that if acommon distribution channel exists, the material sales attributes are read for this distribution channel.

The attributes that refer to a sold-to party are always taken from the reference customer from the Webshop. This is valid for pricing procedure determination and for pricing. Even if an end user logs on, IPC isnot re-initialized. Customer-specific discounts are therefore not possible in the B2C Web catalog.


This scenario is similar to that described in the previous section. The determination of the pricingprocedure, and the list of available fields are the same.

In this scenario, the Java shopping basket performs separate pricing for its items instead of asking theWeb catalog for the price information. To trigger this function, set XCM scenario ‘forceIPCpricing’ to ‘true’in the Java shopping basket component.

Reason for choosing this variant:


Even in this scenario, customer-specific prices are not available in the shopping basket. If you run the B2Capplication, prices should always be set up independently of the actual customer. The technical attributesthat are needed for pricing and that are based on a sold-to party, are derived from the reference customerin the Web shop.

1.1.3 Business-to-Business (B2B) for Occasional UsersThis scenario is based on the Business-to-Consumer (B2C) templates. There are two differences betweenthis and the Business-to-Consumer (B2C) scenario:

- The end user cannot register him- or herself

- The logon is performed with a user ID, not with an e-mail address

With regards to pricing, there are no differences compared to the Business-to-Consumer (B2C) application.For more information, see 1.1.2.1 List Prices in the Web Catalog and in the Shopping Basket and 1.1.1.2IPC Prices in the Web Catalog/Shopping Basket Prices are Taken from the Web Catalog

Therefore, customer-specific prices are not available in the scenario ‘B2B for Occasional Users’.

1.1.4 Business-to Business (B2B) for Internal UsersThe user logs on with his or her SU01 account. No sold-to party needs to be linked; the user can createorders for any sold-to party, in the SAP GUI transaction VA01.

1.1.4.1 List Prices in the Web Catalog and Shopping Basket

Pricing is the same as in the standard B2B scenario. See 1.1.1.1 List Prices in Web Catalog and ShoppingBasket.


Pricing is the same as in the standard B2C scenario, because no specific customer can be determined.See 1.1.2.2 IPC Prices in the Web Catalog/Shopping Basket Prices are Taken from the Web Catalog.


Page7 of 11


To trigger this function, set XCM scenario ‘forceIPCpricing’ to ‘true’ in the shopping basket component.



For the available attributes and the way in which the pricing procedure is found, see the tables in 1.1.2.2IPC Prices in the Web Catalog/Shopping Basket Prices are Taken from the Web Catalog.

In this case, prices that are specific for the actual sold-to party (which has been selected in the shoppingbasket) are not available. If customer-specific prices are part of the pricing procedure used, these pricesare evaluated for the reference customer.

1.1.5 Business-On-Behalf (BOB) Application/Reseller ScenarioThe user logs in with an SU01 or SU05 account that is linked to a reseller. The user can create orders forsold-to parties that are linked to the reseller via a specific partner function.

1.1.5.1 List Prices in the Web Catalog and in the Shopping Basket

Pricing is the same as in the standard B2B scenario. See 1.1.1.1 List Prices in Web Catalog and ShoppingBasket.

1.1.5.2 IPC Prices in The Web Catalog/Shopping Basket Prices are Taken from the Web Catalog

Pricing is the same as in the standard B2B scenario (see 1.1.1.2 IPC Prices in the Web Catalog/ShoppingBasket Prices are Taken from the Web Catalog). There is one exception: the actual sold-to party that mayhave been specified in the shopping basket is not taken into account. Instead, the KUNNR attribute and allother attributes that are based on a customer are derived from the reseller.

Customer-specific prices are possible, but these prices would refer to the reseller.


To trigger this function, set XCM scenario ‘forceIPCpricing’ to ‘true’ in the shopping basket component.



- Reseller-specific pricing is necessary, but for performance reasons for the Web catalog, list pricesshould be displayed

For the available attributes and the way the pricing procedure is found, see the tables in 1.1.1.2 IPC Pricesin the Web Catalog/Shopping Basket Prices are Taken from the Web Catalog.

In this case, prices that are specific for the actual sold-to party (which has been selected in the shoppingbasket) are not available. If customer-specific prices are part of the pricing procedure used, these pricesare evaluated for the reseller.


Page8 of 11

1.2 Summary: Settings That Influence Pricing in SAP E-Commerce for SAP ERP

This section does not cover the standard sales document pricing in ERP for the checkout, confirmation,display, and change screens. Here the pricing is purely controlled by ERP and is the as in the transactionsva01, va02, va03.

Parameter Source Remarks

Business transactionschema

ERP catalog Only if list pricing is used in the Web catalog:controls the determination of the pricingprocedure for Web catalog pricing.

Reference customer ERP catalog Only if list pricing is used in the Web catalog:controls the determination of the pricingprocedure and the pricing itself in all scenarios.

Controlling pricedetermination in thecatalog

Shop List pricing and IPC pricing are possible. Thissetting controls whether IPC pricing is used at all.

Country Shop Only if IPC pricing is used: might influence pricing(header attribute ALAND).

First order type Shop Only if IPC pricing is used: controls thedetermination of the pricing procedure.

Reference customer Shop Only if IPC pricing is used: controls thedetermination of the pricing procedure and thepricing itself in B2C and the scenario “B2B forInternal Users”.

Sales area (salesorganization, distributionchannel, division)

Shop Only if IPC pricing is used: controls thedetermination of the pricing procedure and thepricing itself.

forceIPCpricing XCM/Java shoppingbasket

Controls whether IPC pricing is used in theshopping basket.

preventIPCpricing XCM/Java shoppingbasket

“preventIPCpricing” is only of interest if“forceIPCpricing” is set to true. In this case,“preventIPCpricing” on true copies the prices forconfigurable products from the Web catalog(mainly used in an AFS scenario for performancepurposes).

preventIPCpricing XCM/Catalog Important if configurable products are used in theWeb catalog and therefore IPC is needed, but IPCpricing is not required.

1.3 How to Extend Pricing

1.3.1 On J2EE SideFor more information, see the SAP E-Commerce 5.0 – Development and Extension Guide on the SAPService Marketplace at http://service.sap.com/instguides. Choose SAP Business Suite ApplicationsSAP ERP SAP ERP 6.0 Installation. Search for ‘Call IPC for Pricing or Configuration (ISA ERP)’,where the available user exits are listed. These user exits allow for adding new price-relevant attributes tothe header or item.

http://service.sap.com/instguides.


Page9 of 11

In this guide you can also find the techniques for accessing the SAP ERP backend system from Java orhow to implement new Java classes that implement the user exits.

In the following section, you can find an example for the implementation of such a user exit. For example,you have derived ServiceR3IPC with a subclass Z_ ServiceR3IPC and registered this class in thebackendobject-config.xml.

You want to add a certain customer field to the item attributes. This attribute could, for example, be derivedfrom the product catalog item. The implementation could look like this:

import java.util.Map;import com.sap.spc.remote.client.object.IPCDocument;import com.sap.spc.remote.client.object.IPCItemProperties;

public class Z_ServiceR3IPC extends ServiceR3IPC {

protected void customerExitBeforeItemCreation(IPCDocument document, IPCItemProperties[] properties){

//loop over item propertiesfor ( int i = 0; i<properties.length;i++ ){

IPCItemProperties ipcProperties = properties[i];String productId = ipcProperties.getProductId();

// now find the relevant catalog attribute via the ID// ...// assume the value should be passed to pricing// as Z_ATTR, its value is stored in attributeValue

String attributeValue = null;Map itemAttributes = ipcProperties.getItemAttributes();itemAttributes.put("Z_ATTR", attributeValue);

//set new propertiesipcProperties.setItemAttributes(itemAttributes);

}

}

}

1.3.2 On ABAP SideIf it is only necessary to add new attributes to pricing, it is also possible to enhance the application purelyon the ABAP side.

Header Attributes

If additional header attributes are required: wrap function module ISA_PRICING_HDRDATA_GET, forexample, through a new function module ZISA_PRICING_HDRDATA_GET. This function module canadditionally access tables in ERP and pass additional attribute values to Java through generic tableHDRDATA_OUT.

The function module can then be registered in the modification-config.xml. For more information, see theSAP E-Commerce 5.0 - Development and Extension Guide.

Item Attributes


Page10 of 11

If additional item attributes are required, and TREX is not deployed as Web catalog engine: proceed asdescribed above, but with ISA_PRICING_ITMDATA_GET instead of ISA_PRICING_HDRDATA_GET.

Item Attributes / TREX

If additional item attributes are required, and TREX is used: create a new implementation ofBADI_ISA_REPL_CAT.

Implement method IF_EX_BADI_ISA_REPL_CAT~INSTANCE_GET to return your new subclass ofCL_ISA_REPLICATION_CATALOG. Check the standard class CL_IM_ISA_REPL_CAT_IMP_DEF as anexample.

This subclass implements IF_ISA_REPLICATION_CATALOG~IPC_ATTRIBUTE_VALUES_GET in adifferent way, and extends changing table IPC_ATTR_VALUES.

1.3.3 SAP NotesFor more details about the extension concepts in the pricing area, see SAP notes 999051 and 1004335.

For more details about the pricing analysis tool, see SAP Note 1005377.

1.4 Upgrading from SAP E-Commerce for SAP ERP 4.0 to 5.0

1.4.1 System SetupIn release 5.0, IPC is available on VMC (‘Virtual Machine Container’) on the SAP NetWeaver ApplicationServer. It is integrated with SAP E-Commerce via the RFC protocol.

The tools that must be used to download data from SAP ERP to IPC have changed: The ‘Data Loader’ isno longer used. Pricing data does not have to be replicated anymore.

For the system setup, see the SAP E-Commerce 5.0 for mySAP ERP - IPC Configuration Guide on theSAP Service Marketplace at http://service.sap.com/instguides. Choose SAP Business Suite Applications

SAP ERP SAP ERP 6.0 Installation.

1.4.2 Pricing-Relevant Header AttributesIn release 5.0, a new function module for reading the header-relevant attributes has been introduced:ISA_PRICING_HDRDATA_GET. The following attributes are now provided that were not available inrelease 4.0:








1.4.3 Pricing-Relevant Item AttributesIn release 4.0, no specific item attributes were passed to IPC, because IPC accessed the product masterinternally. Now, only the following attributes are available in the standard system:

http://service.sap.com/instguides.


Page11 of 11










If you need additional item attributes, you have to pass them to IPC explicitly. For more information, see1.3 How to Extend Pricing.

pricing in sap eco

Documents