Scribd Logo
Upload

Welcome to Scribd!

  • 910 views

    Hybris SAP

    Uploaded by

    GPFan
    The document discusses integrating SAP product configuration with Hybris e-commerce. Master data is sent from SAP to Hybris and the product configuration runtime is deployed to the Hybris server. The product configuration add-on enables customers to configure products and add them to their cart on the Hybris site.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Hybris SAP

    Uploaded by

    GPFan
    910 views32 pages
    The document discusses integrating SAP product configuration with Hybris e-commerce. Master data is sent from SAP to Hybris and the product configuration runtime is deployed to the Hybris server. The product configuration add-on enables customers to configure products and add them to their cart on the Hybris site.

    Original Description:

    Hybris SAP

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses integrating SAP product configuration with Hybris e-commerce. Master data is sent from SAP to Hybris and the product configuration runtime is deployed to the Hybris server. The product configuration add-on enables customers to configure products and add them to their cart on the Hybris site.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    910 views32 pages

    Hybris SAP

    Uploaded by

    GPFan
    The document discusses integrating SAP product configuration with Hybris e-commerce. Master data is sent from SAP to Hybris and the product configuration runtime is deployed to the Hybris server. The product configuration add-on enables customers to configure products and add them to their cart on the Hybris site.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 32
    At a glance
    Powered by AI
    The key takeaways are that the text mentions product configuration in hybris and SAP Commerce Cloud, enhancement of product details and configure pages, and sending of master data from SAP to hybris.

    The main components of the Core+ architecture are the REST WebApp, Facade, Service layer divided into the Data layer and Services layer, and Persistence layer with support for MongoDB.

    In hybris, the product details page is enhanced to show a 'Configure' button for configurable products. Additionally, a configure page is introduced to allow customers to configure a product and add it to their cart.

    1

    View portfolio slides for details

    10

    11

    12

    13

    14

    15

    16

    17

    18

    19

    20

    21

    22

    Master data, i.e. products, prices and modeling data is sent from SAP system to
    hybris.
    Product Configuration Runtime is deployed to hybris server.
    The general process from catalog browsing until checkout with creation of the order
    is done according to the scenarios defined for Order Management.

    23

    Master data, i.e. products, prices and modeling data is sent from SAP system to
    hybris. Product Configuration Runtime is deployed to hybris server.
    The general process from catalog browsing until checkout with creation of the order
    is done according to the scenarios defined for Order Management.

    24

    Product Details Page is enhanced to show a Configure button for all products
    which are marked as configurable in hybris PCM.

    25

    Configure Page is newly introduced with the ysapproductconfigb2baddon. The


    page enables customers to configure a product and add the configured
    product to the cart. Detailed explanation of the CMS Component will follow on
    next slide.

    26

    27

    28

    29

    30

    Core+ platform
    most important features of Core+ architecture:
    Similar to Core platform, it has type system (item xml), Persistency layer.
    1. Module independence (each module owns its data and other modules cannot
    break it by modifying its data or services)
    2. New persistence layer with a NoSQL engine for MongoDB
    3. Extensibility and customization options
    Architecture Overview:
    REST WebApp: Exposes the public API as a REST interface
    Facade - Provides a well-defined use case relating the API to the presentation
    layer, decoupled from the Service layer. It will be structured through use cases.
    Usually, the facade is composed of a set of Service layer calls, translating input
    arguments from DTO's to ManagedObjects and the results from
    ManagedObjects to DTOs.
    Service layer: Contains service logic needed to realize business use cases.
    This is the biggest layer and usually is divided into the:
    Data layer: Defines the domain model as ManagedObjects and data access
    components (Queries, DAOs)
    Services layer: Operates on ManagedObjects

    Persistence: If the service application requires persistence capabilities, it


    should use Kernel components and its PersistenceManager (supports several
    persistency engines MongoDB, NoSQL DBs like Cassandra)
    31

    32

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy