Integrating hybris Commerce Accelerator with the OnPremise OMS fail to show Delivery Option at checkout process

[Former Member]

I am trying to follow the instruction in here

however, I got stuck somewhere, I can't include below extensions

  <extension name="omsorders" />
  <extension name="omssampledata" />

if I do so, my checkout process-Delivery Option will not show any address (by default, it should offer two options).

there is no error be thrown in console, we are using integrated cybersource payment integration. but it haven't reached so far, basically stop at step 2, delivery option.

does any one know the reason behind it ?

[Former Member]

thanks, Charles it is working now between our custom front store and OMS. Since we are using old CyberSource integration, I have temporarily disabled all CIS Payment, CIStax, CISavs extension, then the older come into OMS

[former_member357259]

Thats great. You can switch to CIS later on when you migrate from the old payment integration method.

[former_member357259]

Joe, you are right. The CIS payment service is meant to replace the cybersource functionality. In future CIS should become the standard gatweway for payment integrations.

[Former Member]

find some thing interesting : SOP Cybersource

There is additional interaction with a third party service when using CIS for payments: a form post is used to transfer credit card data directly to the payment provider. The hybris Commerce Accelerator for B2C already has a mock for the Cybersource Silent Order Post (SOP). This mock, however, does not work when cispayment AddOn is activated.

[Former Member]

few updates here, now I can get delivery method after changing above files. however, I encounter another issue, we have already integrated with Cybersource Silent Order Post method, now it seems that I am integrating with cisCybersource as default " Payment Provider" and when I am at Payment detail page and click Continue, it lead me to ---http://electronics.local:9001/acceleratorservices/sop-mock/process

how do I disable the default payment CIS to CyberSource and use our already configured CyberSource SOP method ?

I have made like below :

• cis.client.mock=true

• cis.client.payment.mock=false

• cis.client.tax.mock=true

• cis.client.shipping.mock=true

• cis.client.geo.mock=true

• cis.client.fraud.mock=true

but if I change cis.client.payment.mock=true, then it throw error at Payment Detail Tab.

by the way, we don't have following properties in local.properties since we integrate with cybersource SOP

Provide URLs for HOP

cis.rest.mock.payment.pspUrlLocation=https://electronics.local:9002/acceleratorservices/sop-mock/process cis.rest.mock.payment.pspUrl=https://electronics.local:9002/acceleratorservices/sop-mock/process website.electronics.http=http://electronics.local:9001/yacceleratorstorefront website.electronics.https=https://electronics.local:9002/yacceleratorstorefront media.electronics.http=http://electronics.local:9001 media.electronics.https=https://electronics.local:9002

any help will be appreciated, so close to reach " place an order" and then I will check if I could successfully send order to OMS.

[Former Member]

try to summarize the steps I followed : 1. Installing and extending OMS OnPremise 2. install OMS with DoB 3. Integrating hybris Commerce Accelerator with the OnPremise OMS

here is my local-extension.xml

       <!-- Extensions that contain information about the source server where OMS and DoB are deployed -->
       <extension name="omsclient" />
       <extension name="dataonboardingclient" />
       <extension name="corepluscommons" />
                
       <!--Extensions that provide all components that are necessary to access the OMS Cockpit from the web application provided by the backoffice extension -->
        <extension name="omsbackoffice" />
      <extension name="dataonboardingbackoffice" />
        
   
           <extension name="omsats" />           
       <extension name="omsorders" />
   
       <extension name="omssampledata" />
      
       <extension name="ondemandcommon" />
       <extension name="ondemandsampledata" />  

        <extension name="cisavs" />
       <extension name="cispayment" />
       <extension name="cistax" />
      <extension name="cissampledata" /> 

file to change : (to add your own store information )

• omssampledata\resources\omssampledata\import\common\common-integration-data.impex

• omssampledata\resources\omssampledata\import\common\stores\yourstoreid\integration-data.impex

• ondemandsampledata\resources\ondemandsampledata\import\common\common-integration-data.impex

• ondemandsampledata\resources\ondemandsampledata\import\stores\yourstoreid\integration-data.impex

I have deleted all sample stores and do system initializing now, will update status later.

[Former Member]

Hi Joe, Thanks to your comments I got idea on new things and understood problem better.As I am new to Hybris, could you please elaborate how did you add custom base store to OMS. Like where do we find integration.impex for our custom store, and if possible please paste a sample of your integration impex.

[Former Member]

some more questions, what is difference between OMS ondemand and OMS onpremises. in all documents, I don't see extension " ondemandcommon" is included , but I see the explanation of hybris ondemandcommon AddOn is to provides common functionality and libraries for supporting communication between the hybris Commerce Suite and the OMS and CIS services. do I need this extension be added

[Former Member]

Hi Joe, Just add your basestore, locations and stock to OMS through dataonboarding hot folders, create an omsZoneDeliveryModeValue that adjust to your own zone and basestore currency.

Locations ids on OMS must match with the ones you have in hybris side.

Basestore in hybris must have your country added in "deliveryCountries" (hmc -> basestores -> properties tab).

Your country must have an associated region. For example, if you want for your apparel store to deliver in UK you must go to country "GB" and create a new region "GB".

Hope these steps help you to make your OMS to works.

[Former Member]

Hi, Christian

you probably very right for this issue, I am still trying to figure out where is the problem in "common-integration-data.impex " however, in general, we are not following standard stores like apparel-de, apparel-uk,apparel-us,electronics. we have our own custom store page, hence when come to OMS setting, we don't want to import any sample file in oms such as "ondemandsampledata" and "omssampledata" , since they contains a lot of irrelevant content of us and we even don't have those stores name in our database.

I like to have some clear instruction about how to import all necessary OMS configuration impex file and modify accordingly to custom store name. for example, we have defined our own zone, neither usa, ca, japan, nor china, so again, come to OMS import , it is very mess and I don't know which file we need to import or modify. common-integration-data.impex absolutely will be one file we need to change. but to change what , please advise.

[Former Member]

Hi Joe,

I have gone through this issue, you have to take a look at hmc for the type "OmsZoneDeliveryModeValue" and make sure you have values for:

Your "fromZone" (warehouse/store location)

Your "deliveryZone" (customer address location)

Currency (baseStore currency)

DeliveryMode

Once you have set up these values you will see your delivery modes on the checkout process.

You can take a look to this file to figure out what am I talking about: \omssampledata\resources\omssampledata\import\common\common-integration-data.impex

[Former Member]

When adding new extensions you need to initialize the commerce suite. The exportToOMSretrycount error is simply because the DB is not in sync with the data model.

The OMS sample data only includes US stock locations so you need to enter a US delivery address to get US delivery options. Essentially when you add in the OMS the delivery mode rules become more sophisticated and subsequently more restrictive.

[Former Member]

do you mean, each time when I add new extension , I will need to initialize my system.

even so , I did system initialization after I add all required extensions , but It still missing delivery Option unless I comment two extensions below,

       <extension name="omsclient" />
       <extension name="dataonboardingclient" />
       <extension name="corepluscommons" />
        <extension name="omsbackoffice" />
               <extension name="dataonboardingbackoffice" />
   
        <extension name="cisavs" />
       <extension name="cispayment" />
       <extension name="cistax" />
       <extension name="omsats" />           
        <!--
       <extension name="omsorders" />
       <extension name="omssampledata" />
        -->
       <extension name="cissampledata" />
       <extension name="ondemandsampledata" />

[Former Member]

omsorders adds data model changes to Order, Consignment, Delivery Modes etc. (See items items.xml file) As a minimum your going to need to do an update running system. Then you'll need to run the sample data through. Or avoid confusion and just re-init to make sure everything's status quo since you just working in developer mode.

BTW this active post is also pretty much about the same topic : https://answers.sap.com/questions/12748441/enable-oms-for-demo-purposes-is-throwing-an-error.html

Christians answer I think is just about on the money.

[Former Member]

Hi Richard, don't know why, but some of the times i have initialized hybris with oms all went fine, but in most of the cases the required OmsZoneDeliveryModeValue to make an order for someone in New York were not there. I had to create the required instances of this type to see my delivery modes on the checkout process. Otherwise i cannot see any delivery mode on it.

[Former Member]

after I comment those two extension, yes I can continue in order process and finally place an order, but this order only exist in hmc, it never come into OMS. in console, I also can see some error to complain that missing of "omsOrder" extension.

INFO | jvm 1 | main | 2014/06/26 15:03:29.385 | WARN [hybrisHTTP35] [ReflectionAttributeAccess] extension omsorders not installed, cannot call attribute accessor for Order.exportedToOmsRetryCount:java.lang.Integer[rwoSRp]