Example: Deleting receipts

You can delete receipts by using the Data Load utility. This example uses a CSV file to demonstrate how to delete your receipt information.

This example uses a CSV file to demonstrate how to insert, replace, or delete your data. You can also create and use an XML formatted file to insert, replace, or delete your data. If you choose to create and use an XML formatted file, ensure that your XML elements use the same names as are used for CSV column names.

You can use the Data Load utility to delete receipts data from the database.

CSV file with sample receipt data

In this example, the data source is a CSV file named receipt_delete.csv. The file contains sample receipt data with minimum columns that are necessary for "delete" dataLoadMode. Each column is delimited by a comma.

CSV file with sample receipt data


	PartNumber	CreateTime	CatEntryStoreIdentifier
Example-PN-10002	2005-07-12 01:01:01.123456	10701
Example-PN-10003	2008-05-15 04:04:04.0

Note: When you are deleting a record from RECEIPT table, the corresponding data in the table RCPTAVAIL is also deleted because RCPTAVAIL has cascade constraint on the RECEIPT table.

CSV column and XML element definitions

PartNumber: (string) The part number of this item. It uniquely identifies an item for a particular owner. Together with the owner identifier, it is used to retrieve the primary key of ITEMSPC table, that is, ITEMSPC_ID. This field is mandatory and cannot be null if the CatalogEntryUniqueId field is not specified in CSV file.
CreateTime: (Mandatory, timestamp) The date and time this record is created. The format of the input is yyyy-mm-dd hh:mm:ss.SSSSSS. The length of the fractional seconds must be no more than 6. The format can be customized by setting timestampPattern property in wc-dataload.xml. This field is part of the unique index of RECEIPT table. It is mandatory and cannot be null.
CatEntryStoreIdentifier: (String) This field is used in an extended sites store. If the CatalogEntry is defined in a catalog entry asset store, this field stands for the identifier of the catalog entry asset store. This identifier is used to retrieve the store that owns the catalog entry.; This field is mandatory if you are using an extended sites store.

Other optional fields not included in the example:

CurrentStoreIdentifier: (String) The identifier of the store that this item belongs to. This column can be added into CSV if the item belongs to a store that is different from the store that is defined in BusinessContext elements of wc-dataload-env.xml. If this column is not provided in the CSV file, the StoreIdentifier in the business context is used.
FulfillmentCenterId: (Integer) The identifier of the fulfillment center that this item belongs to. This column can be added into CSV if the item belongs to a fulfillment center that is different from the one defined in BusinessContext property of wc-dataload-env.xml. If this column is not provided in the CSV file, the fulfillmentCenterIdentifier is retrieved by FulfillmentCenterName. If it is not found, the fulfillmentCenterIdentifier in the business context is used. If it is not specified in either CSV file or business context, the default fufillmentCenter of the specified store is used.
FulfillmentCenterName: (String) The name of the fulfillment center that this item belongs to. This column is used to retrieve fulfillmentCenterIdentifier.
OwnerId: (Long) The identifier of the owner of this item. If it is not specified in the CSV file, the owner of the catalog entry asset store is retrieved. If it is not found, the owner of current store is retrieved. If it is not found either, the ownerId specified in BusinessContext property of wc-dataload-env.xml is used.
CatalogEntryUniqueId: (Long) The identifier of the catalog entry. It is used to retrieve the primary key of ITEMSPC table, that is, ITEMSPC_ID. If this field is not specified in CSV file, ITEMSPC_ID is retrieved by part number and owner of the item.

Business context data

The following code snippet from the wc-dataload-env.XML configuration file provides the business context data necessary for loading the receipt data:

<_config:BusinessContext storeIdentifier="AuroraESite">
               <_config:property name="fulfillmentCenterName" value="Aurora Home"/>
               <_config:property name="ownerId" value="7000000000000000102"/>
</_config:BusinessContext>

storeIdentifier: (String) The identifier of the store this item belongs to. It is used if CSV file does not provide this information. The StoreIdentifier is used to retrieve the storeID and the ownerID.
fulfillmentCenterId: (String) The identifier of the fulfillment center this item belongs to. It is used if the identifier cannot be retrieved by FulfillmentCenterId or FulfillmentCenterName specified in CSV file.
fulfillmentCenterName: (String) The name of the fulfillment center this item belongs to. It is used to retrieve the fulfillmentCenterID, if fulfillmentCenterID is not retrieved from CSV file or defined in business context.
ownerId: (Long) The identifier of the catalog entryOwner of this item. It is used if the catalog entryOwner is not provided in CSV file and cannot be retrieved by specified store identifier.

Mapping data

The following snippet from the sample configuration file demonstrates how to map each column of data in the source CSV file to a value.

<_config:DataReader className="com.ibm.commerce.foundation.dataload.datareader.CSVReader" firstLineIsHeader="true">
               <_config:Data>
                               
                      <_config:column number="1" name="PartNumber" />
                      <_config:column number="2" name="CreationTime" />
										<_config:column number="3" name="CatEntryStoreIdentifier" />
               
               </_config:Data>
</_config:DataReader >

The following snippet from the sample configuration file demonstrates how to map each column of the data in the CSV file to a business object logical schema path. The attribute 'value' represents the name of a column of the CSV file that is defined in the configuration snippet. Each column in the CSV file must have a mapping to the logical schema path. If the optional fields previously specified are present in the CSV file, the mapping for them must be added.

<_config:DataMapping>
	<_config:mapping xpath="InventoryReceiptIdentifier/ExternalIdentifier/CatalogEntryIdentifier/ExternalIdentifier/PartNumber" value="PartNumber" valueFrom="InputData" />
	<_config:mapping xpath="InventoryReceiptIdentifier/ExternalIdentifier/CreationTime" value="CreationTime" valueFrom="InputData" />
	<_config:mapping xpath="InventoryReceiptIdentifier/ExternalIdentifier/CatalogEntryIdentifier/ExternalIdentifier/StoreIdentifier/ExternalIdentifier/NameIdentifier" value="CatEntryStoreIdentifier" />
</_config:DataMapping>

Business object mediator

The mediator class name is com.ibm.commerce.inventory.dataload.mediator.InventoryReceiptMediator.

Note: When you use a mediator that is provided with HCL Commerce with the Data Load utility, the utility assumes that you are loading data for all columns for a business object. If you want to update the data in only specific columns, configure a column exclusion list for the load process. A column exclusion list causes the Data Load utility to ignore specific columns during the load operation. If you do not use a column exclusion list, the utility updates all columns in the row of a database table row when the utility updates the row. If no value is set in the input file, the utility can replace the existing column value with a default value or set the value to be null. For more information, see Configuring a column exclusion list.