Hybris: Synchronize Pricing Master Data Exchange between SAP ERP and hybris

Agenda: Pricing Integration scenarios between SAP ERP and hybris and prerequisites and configurations needed for hMC.

Learning Path:

hybris Pricing and ERP pricing scenarios

There are two options for pricing integration:

1. Hybris pricing(Asynchronous pricing): Pricing conditions are replicated from SAP ERP to hybris and pricing is done in hybris. The advantage is that pricing in hybris is done independent of the availability of SAP ERP, however the disadvantage is that the pricing logic needs to be setup in hybris.
2. ERP pricing(Synchronous pricing): SAP ERP is called directly from hybris for pricing. The advantage is that the pricing logic remains in SAP ERP and does not need to be replicated. The disadvantage is that pricing functionality is dependent on the availability of SAP ERP.

Pricing:

• Only product prices and discounts transferred from SAP ERP tohybris.
• Payment costs, delivery costs and taxes are not transferred and require double maintenance.
• Once the transfer is done, all calculations are done by hybris, by which it can run independently of SAP ERP.
• IDoc type ‘COND_A04’ is used
• Pricing data is send to Data Hub using Spring Integration
• hybris Data Hub handles receiving, processing and saving the IDoc to hybris platform.
• Insert and update operations are supported.

Mapping of SAP Condition to hybris PriceRow and DiscountRow

Example price in hybris Management Console(hMC)

Asynchronous Process Flow

1. Pricing data(idoc COND_A04) sent from ERP (eg. VK13)
2. sapidocintegration – HTTP servlet that receives the idoc xml and forward it to appropriate handler.
3. sappricing – handles COND_A04 payload.
   • Has mappings from Raw to Canonical to Target
   • Has grouping handler that reads Condition Type customizing to determine if Price or Discount
   • Has transformations to format data and read other customizing.
4. Data Hub saves PriceRow and DiscountRow into hybris via the Data Hub Adapter

Overview ERP Pricing

• Pricing data is read directly from SAP ERP backend for
  • catalog
  • Product details
  • Cart / Checkout
  • Product list will always reads from cache(SOLR, get updated via ERP list price incl. general discounts, not the personlized price). On a project basis SOLR can be bypassed and read directly from ERP.
  • Generic articles, configurable products, Sales BOM are excluded.
• Backend calculation are done using FM PIQ_CALCULATE
• Indication when to use ERP pricing
  • Complex pricing 24X7 availability of backend.
  • Sizing: sizing guide provided
• Prices, Discounts, Payment costs, Delivery costs and Taxes are provided by the API(contract and quote prices would require additional enchancement)
• Synchronous scenarios for Catalog and Cart / Checkout.

Synchronous scenarios for Catalog and Cart / Checkout

Extensions and services for ERP pricing

        

• sappricingbol takes care of all calls to the backend.
• sappricing overrides hybris services, so that we can provide our logic
  • SAPPriceService overrides PriceService and calls ERPPricingBackend
  • SAPCalculationService overrides CalculationService and Calls ERPPricingBackend
  • SAPPartnerService is used to determine the partner for pricing. If this is a b2bsappricing extension will be active and will override the logic so that the b2bunit is taken into account.

Prerequisites

• hybris Commerce Suite 5.3+ incl. hybris Data Hub
• hybris pricing SAP ERP 6.0 Ehp5 SP09 or higher
• ERP pricing: SAP ERP 6.0 Ehp7 SP04 or higher SP

Configuration checklist on ERP side

• RFC destination to the hybris server is created(tcode: SM59)
• Distribution model has been created(tcode: BD64)
• IDoc Processing Port of type XML HTTP has been created(tcode: WE21)
• Partner Profile of type LS (logical system) has been created(tcode: WE20)

Configuration in hybris hMC

• Product, User group, Product group and Discount must exist prior to Pricing data transfer(from ERP)
  • Report DOWNLOAD_CUSTOMIZING_AS_IMPEX(note 1983231) to export general customizing from SAP ERP.
  • Manual import into hybris via ImpEx.
• Maintain SAP Runtime Configuration – Pricing tab(disable sync flags)(ERP Pricing for catalog and Orders)
• Assign configuration to BaseStore.

Configuration of hybris Data Hub

• Condition Types and Condition Class(from SAP ERP)
  • Used to determine if a condition is a price or discount
  • Transfer method to be finalized
• Catalog determination
  • Mapping will use Product Sales Organziation and Distribution Channel to Catalog.
  • Each pair can map to one or more hybris catalogs
  • Final logic to be finalized

Customizing / Configuration

hybris hMC

• RFC Destination to ERP backend
• SAP Runtime Configuration
  • Setup Common Settings – Sales org, Distribution Channel, Reference Customer, etc..
  • Setup Pricing – Enable Synchronous flags
  • Setup Pricing – Front-end field mappings
  • Setup Pricing – Delivery and Payment methods
• Assign Configuration of BaseStore.

Pricing Settings in SAP Base Store Configuration in hMC

• ERP Pricing for Catalog – Activate ERP pricing in catalog
• ERP Pricing for Orders  – Activate ERP pricing in basket and checkout
• Cache ERP Catalog Prices – see below
• Subtotals for price elements
  • Product Price
  • Discounts
  • Taxes
  • Shipping Costs
  • Transaction Costs
• Payment : You can map different payment options(eg Mastercard or invoice) in hybris to Payment Modes in SAP ERP(e.g. to CCINS: PTMC ‘Master-/Euro Card’, or 0001 ‘Pay immediately w/o deduction’). This can determine payment costs in the order and set the Payment card type or Payment terms respectively in the order

sapPricingCache in hyrbis management console

With caching you can improve the performance or your shop. Caching can be switched on in the hMC with ‘Cache ERP Catalog Prices’. The pricing cache can be managed in the hybris management console.

Example mapping of hybris to SAP ERP payment mode

You can map different payment options (eg. Master card) in hybris to Payment Modes in SAP ERP (e.g to CCINS: PTMC ‘Master-/Euro Card’ ). This can determine payment costs in the order(additional charges for mastercard)

Example pricing setup for asynchronous order

The Pricing Condition Types maintained in the hMC under SAP Integration/ Pricing need to be mapped to the Condition types in the pricing procedure in SAP ERP(tcode: v/08)

Hybris:  WCMS – Web Content Management Systems

Agenda: To know about the WCMS architecture of Hybris Commerce Suite. All the brief reading and the practical exercises also if any of the things needed to do further from the trailer that can be helpful in getting certified.

Topics:

• CMS items hierarchy,
•  configure the data model of base store, 
•   website, 
•   warehouse, 
•   Point of Sale and their relations; 
•   create new and configure existing CMS restrictions, 
•   explain their evaluation – CMS restrictions,
•   new CMS component types.

Points:

• multi-channel publishing system – transactional / non-transactional parts of sites
• multi-channel capabilities – various communication channels.
• model supports regular websites, rich internet applications(RIA), mobile devices
• intuitive graphical user interface for data presentation and management.
• business needs & knowledge of the product
• completely independent from old CMS Module.(CMS stack = WCMS, CMS Core, CMS CIS), if you have old CMS module and one based on the WCMS module – both can run on the same SAP Hybris Commerce.
• Might required an additional license to implement all the features

Content publishing for Commerce Sites

• prepare and publish content across multiple channels
• more dynamic content, structured content – product data; unstructured content – editorial info, product buying guides in a single page
• Content manager(cmsManager) expects to easily coordinate all publishing, regardless of channel and without use of developers

WCMS for publishing your Product-Related Content

• Multi-channel publishing
• Different content types
• Ease of use
• Marketing integration
• Technology independence

1. Multi-channel publishing

• minimal time-to-market
• expose content in regular websites, RIA websites & mobile devices.
• use diff communication channels from one tool

2. Different Content Types

• End users can manage various output channels from one tool: WCMS Cockpit, and can publish various sources across diff output channels
• Static Content: Content that is always the same when retrieved by diff users at diff times
• Dynamic Content: retrieved from DB and place in webpage only when req, specific user group.
• Unstructured Content – Edited or free text content
• Structured Content – Attribute-based data retrieved from a database, e.g. product data

3. Ease of Use

• control the stages and online content catalog versions
• Live Edit mode to make changes to content.
• Rendering information
• Navigation nodes provide business users with a tool that enables them to easily and efficient manage the navigation paths.
• With in enhancement, users can build the navigation paths and structures, assign the pages or medias to the nodes within the structure. WCMS Navigation Nodes you can decide availability and visibility of resources in a highly flexible website compositions

4. Marketing integration

• supports other integration like Endeca Page Builder
• WCMS Module supports multi-site and microsite concepts. Built-in SEO make it easier to let content be indexed by search engines. This improves the visibility of website in organic, unpaid listings of search engines.
• Landing pages are reached from content element links or from search engine results.
• create promotion landing pages, display content relating to promotions 
• WCMS module integrates Hybris marketing modules such as Promotion module.

5. Technology Independent

• A full page or only a single content component can be accessed through web services, thus the WCMS Module can co-exist or be tightly integrated with other CMS systems, Microsoft SharePoint

Key Features

• Collections sharing possibility
• Multi-channel support:
• Re-use of content in diff channels
• Run marketing campaigns across channels
• Channel-specific content also supported
• Component concept for updating and extending website and store site
• Page template concept:
• Easy building of site and pages from templates
• Create and edit product landing pages
• SEO supports the creation of SEO content
• Content workflow enables control and approval of content changes
• Live Edit mode enables to edit content whilst browsing the site
• preview content for a certain user or a certain time.
• Multi-site support provides multiple sites fro one store, these are micro sites
• Front-end independence facilities maintenance  of content for RIA, mobile native clients or other non-java technologies
• Possibility of creating new websites and microsite
• Endeca Page Builder
• Navigation Nodes enable building the navigation paths and structures and assigning the resources to the nodes
• The WCMS Cockpit

• WCMS Cockpit provides a simple way for cockpit users to manage their website pages. It provides an intuitive, graphical user interface for data presentation and management.
• The WCMS Cockpit also supports workflow and synchronization tasks.

WCMS Module Extensions

• The WCMS Cockpit is provided by CMSCockpit extension. The WCMS Cockpit, you can manage the pages of a website constructed using the CMS2 extension. You can also use the extended components included in the CMS2Lib extension to manage the website pages.

Known Issues in WCMS – as per the documentation

• Ant updatesystem Fails on the liveeditadon AddOn
• The liveeditaddon AddOn provides the Responsive Live Edit functionality to the WCMS Cockpit and the B2C storefront. When you add and install the liveeditaddon AddOn to your SAP Hybris Commerce, you cannot use ant update system to update your system data. You must use ant initialise to update your system data. Note that using ant initialize will overwrite your existing system data with the default SAP Hybris Commerce data
• Unwanted Behavious in Responsive Live Edit when yacceleratorcockpits Extension installed
• ECP installer recipes that contain the yacceleratorcockpits extension from the b2caccelerator module and the liveeditaddon extension from the responsiveliveedit module will display unwanted and unexpected behavior. 
• SAP Hybris recommends that you do not use the yacceleratorcockpits extension and liveeditaddon extension at the same time. (remove the yacceleratorcockpits extension from local extension.xml)

Working with WCMS Cockpit

• Create and update website pages and content components
• Verify and change website page status
• Synchronize content catalog versions of your website
• Create collections of selected pages
• Search for website pages according to advanced criteria

Overview of WCMS Cockpit

• Advanced mgmt of website pages
• Liveedit perspective for simplified mgmt of website pages 
• grid view modes 
• creating and editing existing content components
• Preview mode for previewing changes
• Mass data editing using list view
• customize views at runtime
• Switch user roles at runtime and change view config accordingly
• Keep user-based lists of favorite items
• Workflow actions with attached website pages- tracking, commenting, changing status
• Synchronise single content components as well as whole website pages

Prerequisites

• which user group your user account belongs. – WCMS cockpit admin
• basic knowledge of the WCMS cockpit perspectives

User Groups – WCMS Cockpit supports the following user groups

• CMS Designer
• CMS Content Manager
• CMS Publisher

Logging into the WCMS Cockpit

http://localhost:9001/cmscockpit/login.zul(user: cmsmanager pwd:1234)

WCMS Cockpit Menu 

• once logged in default perspective for your selected cockpit is displayed – Data Language, User Group, User Settings, Logout

The WCMS Cockpit Interface

• 4 perspectives for you to create, edit and manage your websites

1. WCMS Page View – Allows create, manage, remove pages and content components for Advanced WCMS Cockpit users. The options depend on the authorization rights assigned to your user group
2. Live Edit – dynamic preview of your website and intuitive data mgmt. It is indeed less-experienced WCMS cockpit users.
3. Navigation – Allows you to create, modify and remove navigation nodes, as well as specify the navigation rules of your website.
4. Customer Segments – allows you to define the marketing rules and output actions that they trigger- Add, modify and remove customer segments, customer segment rules and output actions. 

Accessing a WCMS Cockpit Perspective

Logging Out of the WCMS Cockpit

• Menu->Logout
• Home icon -> SAP Hybris Commerce login page/ Hybris Multichannel Cockpit.