Sample: Loading non-ATP inventory

This scenario loads inventory records for a non-ATP store. We can either load the data into a B2C store, or an extended sites store.


About this sample

Each record stands for an inventory for a particular CatalogEntry be shipped from a FulfillmentCenter on behalf of a Store. The CatalogEntry can be identified by the PartNumber In non_ATP_inventory.csv and storeIdentifier in wc-dataload-env.xml For non-ATP store, we only load inventory for item data, it doesn't make sense to load inventory for product data.


Procedure

  1. (Developer) On a command line, go to the WCDE_installdir\bin directory.

  2. (Linux) Open a command line in the Utility server Docker container. Change the directory to utilities_root/bin directory.
    For information about entering and leaving containers, see Running utilities from the Utility server Docker container.

  3. Enter the appropriate command:

    1. B2C or B2B store

      • (Linux) ./dataload.sh ../samples/DataLoad/Inventory/Non-ATP/wc-dataload.xml

      • (Developer) dataload ../samples/DataLoad/Inventory/Non-ATP/wc-dataload.xml

    2. Extended sites store

      • (Linux) ./dataload.sh ../samples/DataLoad/Inventory/Non-ATP/wc-dataload-for-esite.xml

      • (Developer) dataload ../samples/DataLoad/Inventory/Non-ATP/wc-dataload-for-esite.xml


Loading data for inventory flags

We cannot use the Data Load utility to update the value of INVENTORYFLAGS. The default value of INVENTORYFLAGS is 0. Update it directly using the following SQL statement after the data has been loaded:


Verifying the results

Verify that the data has been loaded by running the following SQL statement:

To update after initial load, we can update in the CSV file and run the load again.


Cleaning up the data

To clean up the data loaded in the database, run the following SQL statement

: