Sample: Loading merchandising associations

This sample demonstrates how to load merchandising associations for SKUs that have already been loaded to the database.

About this sample

This sample loads the following associations:

• A cross-sell from the SKU 'Cords-Black-29W x 28L' to the SKU 'Casual shirt-White-Small'.

• An up-sell from the SKU 'Cords-Black-29W x 28L' to the SKU 'Classic pleated dress pants-Black-29W x 32L'.

Procedure

Before running this sample, ensure that you have loaded the initial data.

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 following command:

   • (Linux) ./dataload.sh ../samples/DataLoad/Catalog/IntegrateScenario/wc-dataload-merchandising-association.xml

   • (Developer) dataload ..\samples\DataLoad\Catalog\IntegrateScenario\wc-dataload-merchandising-association.xml

Verifying results

Verify that the merchandising associations are loaded by running the following SQL statement:

select * from MASSOCCECE where catentry_id_from = (select catentry_id from catentry where partnumber 
='Cords-Black-29W x 28L')

We can also verify the load by viewing the new associations in the Management Center.

Note: By default, we cannot verify the merchandising associations for these SKU catalog entries in your storefront. To view merchandising associations for SKUs in the storefront, the store JSP files can be customized to display this information. By default, the storefront displays the merchandising associations for only catalog entries that are products.

Cleaning up the data

To remove the data that you loaded in this sample from the database, run the CleanUp.sql file in the /samples/DataLoad/Catalog/IntegrateScenario directory.

Note: After running the CleanUp.sql file, we might see that 0 rows are deleted for certain SQL statements. This result is expected, as not all rows are populated with data in this sample.