Agenda: Replicate the stock level data from SAP ERP to Hybris.

Tasks:

————————-End of the Page———————–

Agenda: Replicate product master from SAP ERP to Hybris.

Tasks:

.

————————-End of the Page———————–

Agenda: Replicating material characteristics, classes and class hierarchies from SAP ERP to hybris.

Tasks:

————————-End of the Page———————–

Agenda: Create ERP settings

Tasks:

————————-End of the Page———————–

Agenda: Configuration settings for the Product master data replication

Tasks:

————————-End of the Page———————–

Agenda:

1. Understand the product master data & stock level exchange
2. Prerequisites
3. Architecture and extensions

Procedure: hybris-SAP Solution Integration for Asynchronous Scenario.

Data Synchronization:

Product data replication allows you to send product data to hybris Commerce Suite from SAP ERP or SAP Retail. Product data includes master data, product classification data, material variants and stock level information. Replicated data goes first to hybris Data Hub where it is composed and published, and then is transferred to hyrbis Commerce Suite.

In SAP ERP, products are commonly referred to as materials, whereas is SAP Retail they are labelled as articles.  Furthermore, classes and characteristics in SAP ERP correspond to categories and features in hybris Commerce Suite. Additionally, material variants(standard products linked to configurable master product) can be send to hybris. The variants inherit the same classification data as the master product, typically an assignment to a class of type 300.

You replicate product master data, classification data and material variants from SAP ERP, You ensure that master data is replicated to the desired catalog by making mapping settings in hybris Management Console.

In the delivered implementation, stock level data represents the physical inventory for a product at a particular date and time. You can set up a background job in SAP ERP to periodically send stock level information to hybris.

Scenarios

Replicated Material Master Attributes

Basic Data:

• Material Number / Article Number
• Language-dependent short Descriptions
• Basic Unit of Measure
• EAN Codes
• Cross-Distribution Chain Block status and date(displayed only in hMC)
• Configurable Product Indicator(data model enhancement only)

Sales Area Dependent Data:

• Material price group(mapped to Price Class in hybris)
• Sales Unit of Measure
• Sales block status and date(displayed only in hMC, no OMS integration)
• (Some) Conversion Rules between Sales UoM and Base UoM(if applicable, supported by some hybris functionality only)
• For an IS-Retail enabled ERP the related article master information can be replicated via ARTMAS idoc message.

Data Flow

The hmc on hybris core is where all business configuration should be made. So the idea is to provide a simple configuration UI where the relationship between product sales area and catalogs is possible. Then, via a synchronization button(or event), the configuration data is replicated into the datahub DB.

Sales Area Specific Product Catalogs:

• Material attributes can be dispatched into sales area specific catalogs.
• Inserted into hybris catalog management & synchronization concept.
• Support SAP ERP common distribution channel to share product catalogs among web shops whenever possible by means of base store configuration(aligned with pricing dispatching)

Material Attributes Defined by ERP Classification:

• SAP ERP material classification is replicated into hybris classification systems
• SAP ERP classes are mapped to classification categories as part of classification catalogs(based on feature values mapped from SAP ERP characteristic values)
• Replication via Idoc-Messages CHRMAS, CLSMAS, CLFMAS.

Example:

Material Variants:

In SAP ERP, variants are standard products linked to a configurable master product. The variants inherit the same classification data as the master product, typically an assignment to a class of type 300.

However, unlike product classification data, which is transferred using the CLFMAS Idoc, classification attributes of variants are contained in the MATMAS Idoc.

Stock level replication – enabling base commerce

ERP stock levels can be replicated to hybris warehouse to enable usage of stock service API as part of hybris base commerce.

Stock level type: Unrestricted stock, consolidated on plant level across all relevant storage locations inside the plant. Stock levels expressed in the material base units.

Idoc used: LOISTD01

Prerequisite:

• The hybris warehouse identifier should match the ERP plant identifier. Optional: More flexible mapping configuration.
• hybris product data modell and accelerator content support one unit of measure to be used as the sales unit and stock keeping unit, which is assumed to be the same stock keeping unit used in ERP. More complex scenarios require project specific enhancements.
• No OMS integration

Field mapping Stock levels:

Prerequisite configuration in SAP ERP

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)

Data Synchronization

Solution Configuration in SAP ERP

• Creating a Model View
• Replicating Characteristics, classes and Class Hierarchies
• Replicating Characteristics
• Replicating Classes
• Replicating Class Hierarchies
• Replicating Product Master Data
• Replicating Stock Level Data
• Required Material Data for Order Management

Solution Configuration in hybris hMC

In SAP ERP and SAP Retail, products are assigned to sales areas, which, for the purpose of catalog mapping, each consists of a sales organization and a distribution channel. (The division is not relevant when mapping products to catalogs). Sales areas are equivalent to catalog versions in hybris.

You map sales areas to catalog versions to ensure that all products belonging to particular sales areas are automatically replicated to corresponding catalog versions in hybris. This makes it possible to have different product offerings and pricing structures for different regions. For example, a given product may be available only for a particular region, or may be available in mulitple sales areas but priced differently in each.

If a product is assigned to several sales areas, you need to assign the product to each corresponding catalog(catalog version) in hybris.

In the Common Settings tab in the SAP Base Store Configuration node, you also specify sales area information. However, this is relevant for order management and does not extend to product data replication.

————————-End of the Page———————–

Agenda: Enable a Customer Organization(B2B Unit) structure in Hybris.

Tasks:

Agenda: To replicate the Customer Master Data replication to Hybris from SAP ERP.

Tasks:

Agenda: To create your own Customer data in SAP ERP.

Tasks:

Agenda: To create the configuration for the replication of Customer and Contact persons.

Tasks:

Address semantics menu Option