Presentación Viktor Karpyuk Mekolayovech | Hybris - eCommerce IT Camp
•Descargar como PPTX, PDF•
0 recomendaciones•271 vistas
Diapositivas presentadas por Viktor Karpyuk Mekolayovech, Hybris Team Leader en Inclusion Services, en el eCommerce IT Camp del eCommerce Day Buenos Aires 2017.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (19)
Similar a Presentación Viktor Karpyuk Mekolayovech | Hybris - eCommerce IT Camp
Similar a Presentación Viktor Karpyuk Mekolayovech | Hybris - eCommerce IT Camp (20)
Más de eCommerce Institute
Más de eCommerce Institute (20)
Presentación Viktor Karpyuk Mekolayovech | Hybris - eCommerce IT Camp
- 1. ECOSISTEMA E INTEGRACIONES PARA UN ECOMMERCE ESCALABLE
- 2. About me Viktor Karpyuk Mekolayovech Ingeniero en Sistemas de Información (UTN FRBA) Hybris Team Leader – SAP Hybris Certified Developer Inclusion
- 5. ¿Por qué es importante? Omnicanalidad
- 6. • Fortalece la lealtad • Aumenta el compromiso • Estimula el interés • Mejora la experiencia del usuario Omnicanalidad
- 7. Omnicanalidad •Centralización de la información •Reducción de las interfaces •Menor costo de desarrollo •Rapidez de implementación
- 8. SAP Hybris PCM Product Content Management
- 10. SAP Hybris PCM
- 11. SAP Hybris PCM • Información centralizada • Gestión del contenido de los productos • Manejo flexible de los atributos • Mejora la calidad de datos
- 12. SAP Hybris PCM • Clasificación y categorización de los productos • Flujos de trabajo flexibles • Administración de múltiples catálogos • Internacionalización
- 13. Integración
- 14. Integración
- 15. • Productos • Clientes • Órdenes • Envíos • Estados de las órdenes Integración
- 16. Integración
- 17. Integración Hybris – SAP ERP
- 18. Hybris Commerce –> SAP ERP
- 19. Hybris Commerce –> SAP ERP
- 20. SAP ERP –> Hybris Commerce
- 21. SAP ERP –> Hybris Commerce
- 22. Integración Hybris – C4C
- 23. Integración Hybris – C4C Direcciones Clientes
- 24. Integración Hybris – C4C
- 25. Integración Hybris – C4C
- 27. Preguntas
Notas del editor
- Una imagen vale mas que mil palabras! Integración, conexión de todos los canales existentes. Ejemplo: un cliente que hace una compra en la tienda física, aun sin tener una cuenta web. Cuando se registra en la pagina web del retailer, va a poder continuar: La edición de sus datos personales. Ver la/las ordenes(visualización de las facturas) Ver la información de valor del retailer, por ejemplo “los puntos acumulados” por sus compras para canjear por los productos Ver el historial de las compras Etc…
- Permite un acompañamiento en todas las etapas del proceso con el cliente. Mayor información y visibilidad al cliente
- Que es SAP? Sistemas, Aplicaciones, Procesos en ingles: "Systems, Applications, Products in Data Processing“ ERP: Enterprise Resource Planning, en español “Sistema de Planificación de Recursos Empresariales”
- Evolucion de PIM(product information management) a PCM Problemas: Información diferente que proviene de diferentes departamentos Areas comercial, marketing, logística etc…. Sistemas diferentes Como se maneja la info Centralización en la
- Vista única de la data cross platforms, sistemas y diferentes líneas de negocios Creación del contenido enriquecido y consistente para miles de productos Manipulación y administración de los atributos que clasifican a los productos, coladores de atributos. Many organizations today rely on a centralized Product Content Management (PCM) solution to manage, update, consolidate, and distribute product data as part of a successful eCommerce strategy
- Coordinación de las tareas colaborativas Agregación de todo el contenido proveniente de múltiples fuentes Estandarización y la validación del contenido Soporte para múltiples lenguajes
- Integración bidireccional Datahub Es una plataforma de integración y puesta en escena de datos. Técnicamente es una webapp que recibe data de diferentes fuentes, una de ellas puede ser el ERP de SAP. Facilita la carga de mucha cantidad de información desde una o muchas fuentes. La procesa y prepara para el delivery hacia n sistemas de destino. Usando las BAPIS de SAP para determinados casos, como reserva/consulta de stock
- Integración bidireccional Datahub Es una plataforma de integración y puesta en escena de datos. Técnicamente es una webapp que recibe data de diferentes fuentes, una de ellas puede ser el ERP de SAP. Facilita la carga de mucha cantidad de información desde una o muchas fuentes. La procesa y prepara para el delivery hacia n sistemas de destino. Usando las BAPIS de SAP para determinados casos, como reserva/consulta de stock
- 1. Source System Adapter - The source system adapter provides an integration between the source system and Data Hub. The source system adapter is an essential part of your data integration solution because it is required to import raw, unprocessed data from the source system to Data Hub. The REST endpoint used to import data corresponds to the Data Hub integration channel and data feed. A more complex adapter may include event responses and data preprocessing capabilities. If your source system is SAP Hybris Commerce or SAP ERP, then you can use one of the provided, out-of-the-box adapters for this purpose. For more information 2. Inbound Channel - Data Hub provides a single inbound channel that is a Spring Integration channel. Spring Integration is the preferred method for importing data into Data Hub. The CSV inbound adapter provides a convenient method for data already in CSV format. It sends the data along to the Spring Integration channel.. For more information, see:Load 3. Data Feeds and Pooling Strategy - Do you need more than one feed or pool for either concurrent processing or data segregation? Data Hub provides a single feed and a global pool by default. If you need more than one feed or pool, you can use either a named pool or new pool per input pooling strategy. Using a strategy other than the default feed and global pool is optional. For more information, see:Feeds and Pools 4. Data Model - The data model defines how raw, canonical, and target data items are structured, and includes metadata that assists with composition and publication. Typically, you create separate XML files for RawItem, CanonicalItem, and TargetItem definitions. The target item XML also includes target system definitions. The data model is an essential component of your Data Hub integration project. For more information, see:Advanced Metadata Structure 5. Data Handlers - Data handlers are classes that are used to execute data transformations, including grouping, especially during the composition phase of the Data Hub workflow. Data Hub is shipped with a set of default grouping and composition handlers. You may develop your own dedicated handlers in addition to the provided defaults. Handlers can run in any order and you can insert as many handlers as you need. Publication grouping handlers are optional, but provide powerful data transformation possibilities during the publication phase. For more information, 6. Target System Adapter - The target system adapter is a means to deliver data to target systems and gather results. The target system adapter is the normal endpoint for the Data Hub publication phase. It does the final packaging of target items for delivery, then forwards them to the target system. If your target system is SAP Hybris Commerce, or either SAP ERP or SAP C4C, then you can use one of the provided out-of-the-box adapters. For more information, see: 7. Configuration - Data Hub provides a number of configuration possibilities, including parameters related to performance, the database, security, and integration with external systems through the adapters. Although not all configuration options are mandatory, you need to provide some essential basic configuration for your integration scenario. Essential configuration includes credentials for connecting to the Data Hub database, and for use with basic authentication. In addition to providing basic configuration for your project in the local.properties file, you may choose to create a custom Spring Security profile. This profile is used for the protection of Data Hub REST endpoints using HTTP Basic Authentication. For more information, see:
- The SAP ERP system also serves as an authoritative master data source for pricing information. The pricing information includes campaigns and discounts, product information, and inventory, as well as anticipated future stock
- SAP Hybris Cloud for Customer (C4C) provides a complete solution for targeted customer support, sales, and marketing that goes well beyond traditional Customer Relationship Management (CRM). C4C allows sales and customer service teams to provide a relevant customer experience at every stage of the customer journey. However, in a commerce environment, it is the front-end web shop that is the first point of contact for customers. It is also the primary repository for customer data, which is vital to enabling this targeted customer experience. With Data Hub, customer data created in the Hybris Commerce solution can easily be transferred to SAP C4C for use during sales, marketing, and support activities.
- Customer Data Customer Data includes names, addresses, IDs, payment addresses, and shipping addresses. During the data transformation process, Data Hub adds new fields required by C4C that are not present in the Hybris platform. Fields might include items such as gender or form of address, which is not necessary for an online commerce platform but is useful in customer service. It additionally splits or joins fields, such as address or name fields, where a single field maps to multiple fields in the target system. It also works in the opposite way where there is only one field in the target system for data in multiple fields in the source. Address Data Address data includes customer contact details, and also such items as shipping and billing addresses. In Hybris Commerce, billing and shipping addresses are closely tied to the customer persona. In C4C, such details are distinct. The data mapping for C4C integration splits Hybris Commerce address data, transferring it from the CustomerItem to the AddressItem and splitting or combining fields as necessary.
- Mencionar la importancia de la omnicanalidad, donde mercado libre forma parte de un canal. En el momento de aprobación de un producto, se realiza la publicación/modificación de un producto a ML Para facilitar el trabajo de publicar manualmente los productos y hacer la administración de los mismos centralizada desde el mismo lugar