SAP Commerce/SAP Hybris Product Master Data Load(Inbound Integration Call)

 As part of SAP Commerce/SAP Hybris customer requirement solutioning, product master data load is one crucial topic,  

How the product master data will come? 

What are the field product master data will have? 

How data field will be mapped to SAP Commerce/SAP Hybris inbound integration object?

Let's talk on this point:- How well we can do it effectively.

SAP Commerce/SAP Hybris OOTB has most of the inbound integration objects and extensions which support them.

The extension list is as:-

         <extension name='inboundservices'/>

        <extension name='outboundservices'/>

        <extension name='integrationservices'/>

        <extension name='odata2services'/>

        <extension name='integrationmonitoringbackoffice'/>

        <extension name='integrationbackoffice'/>

        <extension name='outboundsyncbackoffice'/>

        <extension name='outboundsync'/>

So when you configure this list of extensions, after doing an update or initialize, in back office you will see the Integration UI Tool option.

In the Integration UI Tool, all the integration objects for inbound/outbound will be available.

In SAP Hybris/SAP Commerce product data load integration object name is InboundProduct.

InboundProduct implicitly takes the product model into consideration.

Now we have three items types, which play a significant role:-

1. IntegrationObject -> hear integration name is defined.

2. IntegrationObjectItem - hear integration data model name is defined and attribute mapping context is defined like  ALL_SUB_AND_SUPER_TYPES

3. IntegrationObjectItemAttribute -  hear Integration object name is mapped to Item type defined in Integration object items, and list of attributes.

Ex: -

INSERT_UPDATE IntegrationObject; code[unique = true]; integrationType(code) 

; InboundProduct; INBOUND 

INSERT_UPDATE IntegrationObjectItem; integrationObject(code)[unique = true]; code[unique = true]; type(code); root[default = false]; itemTypeMatch(code) 

; InboundProduct ; Catalog              ; Catalog              ; ; ALL_SUB_AND_SUPER_TYPES ;  

; InboundProduct ; Category              ; Category              ; ; ALL_SUB_AND_SUPER_TYPES ;  

; InboundProduct ; Unit                  ; Unit                  ; ; ALL_SUB_AND_SUPER_TYPES ;  

; InboundProduct ; Warehouse            ; Warehouse            ; ; ALL_SUB_AND_SUPER_TYPES ;  

INSERT_UPDATE IntegrationObjectItemAttribute; integrationObjectItem(integrationObject(code), code)[unique = true]; attributeName[unique = true]; attributeDescriptor(enclosingType(code), qualifier); returnIntegrationObjectItem(integrationObject(code), code); unique[default = false]; autoCreate[default = false] 

; InboundProduct:Catalog              ; id                      ; Catalog:id                      ;                                      ; ;  

; InboundProduct:Category              ; code                    ; Category:code                  ;                                      ; ;  

; InboundProduct:Category              ; catalogVersion          ; Category:catalogVersion        ; InboundProduct:CatalogVersion        ; ;  

; InboundProduct:Unit                  ; unitType                ; Unit:unitType                  ;                                      ; ;  

; InboundProduct:Unit                  ; name                    ; Unit:name                      ;                                      ; ;  

; InboundProduct:Unit                  ; code                    ; Unit:code                      ;                                      ; ;  

; InboundProduct:Warehouse            ; code                    ; Warehouse:code                  ;                                      ; true ;  

; InboundProduct:Warehouse            ; name                    ; Warehouse:name                  ;                                      ; ;  

; InboundProduct:Warehouse            ; vendor                  ; Warehouse:vendor                ; InboundProduct:Vendor                ; ;  

NOTE:- SAP Commerce/SAP Hybris OOTB provide all the attribute present in the OOTB data model, but if there is any customer-specific attribute created, then you need to update the impex, create a custom impex, copy the impex from the OOTB, paste it, in custom initial data extension in your relevant package, there define the custom attribute in IntegrationObjectItem and IntegrationObjectItemAttribute type, like present.

Also, you can modify the attribute from the integration UI tool of SAP Commerce/SAP Hybris from backoffice, like Unique to true, auto create, generate, and rename it adhocly from the back-office.

Once this activity is completed, then you can copy the rest OData endpoint, which the middleware has to hit, keep note all the mapping of incoming data from a legacy application like S4 Hana, SAP ECC, Oracle apps, to be done in Middleware like SAP CPI, Mule Soft, when the product data will get transition to SAP Commerce acceptable format.

Mandatory Attributes sent from S4 OTC Team/SAP ECC Team : 

• Product Code(Unique)

• Catalog Version

• Qualifier

This are mandatory attribute, without which the product creation will fail, as they are unique equals true.

WorkFlow:

• S4 OTC will send the material master to CPI(Middleware)

• CPI is going to send the Product Data to B2B environments using oAuth Authentication.

• Ideally, the received product will be in Staged Version.

• Catalog version will be <catalogName>ProductCatalog.

• Once, B2B receives the product data following operation are performed after we persist : 

• Update all the classification classes to the product, so that the product manager can easily update the values from backoffice.

• Default List Price will be created.

• Note : All the UOM details for each product will be coming from OTC.

• After catalog sync, the product will be displayed on the sit