Sample: Loading merchandising associations
This sample demonstrates how to load merchandising associations for SKUs that have already been loaded to your 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.
- On a command line, go to the /opt/CommerceUtilities/samples/bin directory.
Open a command line in the .
Change the directory to
utilities_root/bin directory.
For information about entering and leaving containers, see
Running utilities from the Utility server Docker container.- Enter the following command:
./dataload.sh ../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')You can also verify the load by viewing the
new associations in the Commerce Lab.
Note: By default, you cannot verify the
merchandising associations for these SKU catalog entries in your storefront. If
you want to view merchandising associations for SKUs in your storefront, your
store JSP files can be customized to display this information. By default, your
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 you run the
CleanUp.sql file, you 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.