Finishing the Base Store Configuration

By this point, in a project to integrate SAP Commerce Cloud, for example, with SAP S/4HANA Cloud for a B2B order fulfillment scenario, the B2B customer should be able to log on to the B2B storefront. However, the customer will still not yet be able to do any checkout. For checkout to work on the storefront, you need to update the checkout and order process configurations of the SAP Commerce Cloud base store.

1. Access the SAP Commerce Cloud Backoffice and log on as an administrator.
2. Navigate to Base Commerce→Base Store.
3. Choose the powertools base store entry from the list of the search result.
4. On the Properties tab, choose True for the Net field.
5. Still on the Properties tab, scroll down to find the Submit order process code section, modify this value to that for the SAP order process, which is sap-oms-order-process.
6. Choose Save to update the base store.
7. Choose the Administration tab, and scroll down to find the Checkout Flow Group field under the UNBOUND section, and modify the value to b2bCheckoutGroup, which is the value for the sales order checkout.
8. Choose Save to update the base store.

In an integration of SAP Commerce Cloud, for example, with SAP S/4HANA Cloud for a B2B order fulfillment scenario, order numbers are set according to the external number range of the SAP S/4HANA Cloud sales order type.

To check the existing Number Range intervals in SAP S/4HANA Cloud, navigate to the Manage Your Solution app in SAP S/4HANA Cloud, and choose Configure Solution.

1. On the Configure Your Solution screen, set the following search filters: Application Area; Sales.
2. From the search result list, search for the Sales Documents item belonging to the Sales application area.
3. You can read the external number range in the Define Number Ranges for the Sales Documents field.
4. Choose Configure next to the Configure Sales Document Types row.
5. You can choose a number range that you want by selecting check. You can also change the number range by configuring it.
   Caution

   Make sure that you've configured an external number range that is reserved for SAP Commerce Cloud.

SAP Commerce Cloud uses a key generator for the sales order ID/number. The key generator needs a start or initial value, which is specified in the manifest.json file or in a properties file in your SAP Commerce Cloud project repository. This value should be the same as defined in the SAP S/4HANA Cloud external number range as just discussed.

1. Access the manifest.json file under the core-customize folder of the Git-based code repository of your SAP Commerce Cloud project.
2. Open the file in any text editor, and create a new entry for:
   Code Snippet

   Copy codeSwitch to dark mode

   1
   keygen.order.code.start=<value from SAP S/4HANA Cloud>

   
   Note

   The number range for keygen.order.code.start can be read from the OR transaction type configuration in SAP S/4HANA Cloud via the SAP Fiori launchpad.

   Alternatively, you can put the key/value pair in a properties file, for example, local.properties, or saporder.properties and reference the properties file from the manifest.json file.

   After modifying the manifest.json file, or a properties file, you will commit and push the changes to the remote project repository. After this, you can create a new SAP Commerce Cloud build, and wait for the build to succeed. Once the new build has succeeded, you can deploy it to your target SAP Commerce Cloud environment.