Transferring catalog item data

The catalog item ingestion feature transfers item data from an external system into the catalog in Sterling Intelligent Promising. Any invalid input is uploaded back to you as a .csv file for errors to be addressed.

1. To create the .csv files, complete the following steps:
   1. For the file name, use the appropriate naming with .csv format. For example, <tenantId>_Items_20240531010101.csv.
   2. For the separator, use the comma (",").
   3. Upload multiple .csv files by compressing them into a tar.gz file.
2. You must follow the order of the fields shown in the data type table by matching the same order for the fields in the column in the CSV file. For example, if Item ID is the first field that is defined in the data type table, it must follow the same order in the column in the CSV file. Review the following fields and descriptions for the catalog item ingestion data:

3. Review the following sample .csv file:

   itemId,unitOfMeasure,itemGroupCode,globalItemId,allowGiftWrap,assumeInfiniteInventory,isAirShippingAllowed,isDeliveryAllowed,isForwardingAllowed,isFreezerRequired,isHazmat,isModelItem,isParcelShippingAllowed,isPickupAllowed,isProcurementAllowed,isReturnable,isShippingAllowed,substitutionAllowed,taxable,bundleFulfillmentMode,colorCode,costCurrency,countryOfOrigin,defaultProductClass,description,effectiveEndDate,effectiveStartDate,extendedDescription,extendedDisplayDescription,itemType,keywords,kitCode,manufacturerDescription,manufacturerItemId,manufacturerName,masterCatalogId,maxOrderQty,minOrderQty,minReturnWindow,returnWindow,shipmentConsolidationWindow,modelItemId,modelItemUnitOfMeasure,primaryEnterpriseCode,primarySupplier,productLine,shortDescription,sizeCode,status,unitCost,unitHeight,unitLength,unitWidth,unitWeight,unitHeightUOM,unitLengthUOM,unitWeightUOM,unitWidthUOM,imageUrl,advanceNotificationTime,timeSensitive,fifoTracked,itemBasedAllocationAllowed,useUnplannedInventory,tagControlled,leadTime,maxNotificationTime,minNotificationTime,onhandSafetyFactorQty,onhandSafetyFactorPercentage,futureSafetyFactorPercentage,defaultExpirationDays,processingTime,batchNo,lotAttribute1,lotAttribute2,lotAttribute3,lotKeyReference,lotNumber,manufactureDate,revisionNo,commodityCode,eccnNo,harmonizedCode,hazmatClass,naicsCode,nmfcClass,nmfcCode,pickingType,postingClassification,scheduleBcode,storageType,taxProductCode,unspsc,velocityCode
   
   pen,EACH,PROD,GTIN1,TRUE,FALSE,TRUE,TRUE,FALSE,FALSE,TRUE,FALSE,TRUE,TRUE,FALSE,FALSE,TRUE,FALSE,TRUE,,RED,USD,US,,ballpoint pen,2030-09-09T01:01:01.001Z,2024-05-09T01:01:01.001Z,red color ballpoint pen,,,,,,,,,20,2,1,1,2,,,,,,pen,,3000,10,1,4,1,1,inch,inch,gram,inch,http://image/item/1,,FALSE,FALSE,FALSE,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
   
   book,EACH,PROD,GTIN2,TRUE,FALSE,FALSE,FALSE,FALSE,FALSE,FALSE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,FALSE,,,USD,US,,notebook,2030-09-09T01:01:01.001Z,2024-05-09T01:01:01.001Z,notebook for students,,,,,,,,,5,3,1,1,2,,,,,,book,,3000,6,1,8,7,1,inch,inch,gram,inch,http://image/item/2,,FALSE,FALSE,FALSE,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

4. Complete one of the following steps:
   • Upload a single file to the <Input_Prefix>/UPLOAD/ITEM/ virtual folder on IBM Cloud Object Storage.
   • Upload all files from a local directory to the <Input_Prefix>/UPLOAD/ITEM/ virtual folder on IBM Cloud Object Storage.
5. Familiarize yourself with the file format, for example:
   • If the original file is called 2024-01-01-10-59-00.0000-3423-Availability.csv, for simplicity, you might call this file <myfilename>.csv.
   • If the data row fails to process, you receive the following error row.csv and the error summary.txt files:

     <myfilename>_file_failed_row.csv. for the error rows only (all successful are not present here)
     <myfilename>_file_failure_reason.txt are the summary file which provide the error codSterling Intelligent Promising automatically create prefix to store processed files based on their current state which includes:

     The error row.csv file is the original ingestion record that can't be processed. The error summary.txt file provides the reason for the processing failure.
6. Understand the prefix that is created automatically by Sterling Intelligent Promising to store processed files that are based on the following current states:

   /failed

   Any CSV row that fails to process is placed in a file for download and review. As part of the monitoring process, you should review any files that are placed in this prefix. Then, you must rectify the failure and resubmit the CSV rows for reprocessing in the input stream.

   /reprocessed

   Any files that are in a queue for reprocessing due to connectivity issues. No actions are required for this prefix. Any files that are stored in the reprocessing prefix temporarily are retired automatically in Sterling Intelligent Promising. More actions are not required to handle the data.

   /completed

   All files that completed processing. It is important to clean up the completed files routinely to minimize the storage requirements on IBM Cloud Object Storage.

   /summary

   A data ingestion summary file that describes the error that occurred during execution. This summary file can be used in conjunction with the files that failed to process to help to understand the error code and the reason for failure.