Bulk Imports

Data feeds can be setup for bulk upload of vendor pricing, purchase order manifests, and shipment notification.

Shipment Notification Import

This uses the standard CORESense file format (.CSV) and is labeled Shipment Notification Import. The import process retrieves the file from the FTP location, reads each shipment record in the file, and updates the corresponding shipment record in CORESense with the following data:

Shipment ID
Tracking Number
Ship Date
Shipment Cost

The shipment's status is updated to Shipped, which then sends the corresponding shipment confirmation emails. The order status is updated to reflect either Fully or Partially Shipped as is appropriate.

Vendor Pricing Import

File data is used to update vendor pricing on SKUs. The import also generates an exception report related to the uploaded data either .CSV or tab delimited. The exception reports will be FTP’d to the location specified on the data feed properties. The import CSV file contains the following data field format:

Vendor SKU
Unit Cost
Discounted Unit Cost [from Purchasing Levels] (optional field)
Minimum Quantity [from Purchasing Levels] (optional field)
Vendor ID (optional field)

Receive Product from CSV Purchase Order Manifest

This functionality can import a CSV PO manifest. This data feed provides an efficient means of importing a manifest to create receivers on the corresponding POs, and update POs that are fully received. The new data feed, Receiver Import, was added and includes the following data columns

Quantity
Vendor SKU
PO Number
Unit Cost (Optional)
Ship Date (Optional)
Tracking Num (Optional)

Step	Action
1	Select the Receiver Import option.
2	When the data feed is triggered, use the Browse button to select the file from a local drive. When the Submit button is clicked, the feed loads the CSV data.
3	The feed looks up the PO: If no match is found, an error is sent to the log file as, <TimeStamp> Row X skipped: Purchase Order <PO Num> not found. If a matching PO is found, it verifies that the current Vendor SKU exists on the PO.
4	It verifies Vendor SKU: If the Vendor SKU does not exist on the PO, an error is sent to the log file as, <TimeStamp> Row X skipped: SKU <Vendor SKU> does not exist on PO <PO Num> If the Vendor SKU exists on the PO, it checks for Open Receivers.
5	It checks for Open Receivers: If no open receivers are found on the PO, it creates a new receiver output message to the log file <TimeStamp> Creating Receiver <receiver num> on Purchase Order <PO Num>. If open receiver(s) exist(s), the receiver with the latest creation date is used.
6	Quantity is updated: Update the Quantity on the SKU by adding to it the Quantity from the CSV file Record a message to the log file as <TimeStamp> Updating SKU <Vendor SKU> on PO <PO Num>, Receiver <Receiver Num> to Qty <Updated Qty>. If the Updated Quantity > Ordered Quantity on the SKU, a message is sent to the log file as <TimeStamp> Overage: SKU <Vendor SKU> Qty (##) exceeds Order Qty (##) on PO <PO Num>.
7	It checks for Unit Cost: If Unit Cost is provided, the SKU record is updated on the receiver with the new Unit Cost value. A message is sent to the log file as <TimeStamp> Updating SKU <Vendor SKU> on PO <PO Num>, Receiver <Receiver Num> to new unit cost <Updated Unit Cost>.
8	It updates received status: · If the current CSV record is the last record for this PO, the receiver is set to Received. · A message is sent to the log file as, <TimeStamp> Setting Receiver <receiver num> on PO <PO Num> to 'Received'. · If the current CSV record is NOT the last record for this PO, the receiver is saved for later. · If all SKUs on the PO are fully received (Received Qty >= Order Qty), the PO is closed. · A message is sent to the log file as, <TimeStamp> Closing PO <PO Num>. Fully Received.
9	For Drop-ship POs: The Ship Date (if provided) to the related shipment is updated. If Ship Date is NOT provided, the Ship Date field on related shipment is updated to the current date, and a message is sent to the log file as, <TimeStamp> Ship Date not provided for PO <PO Num>, using the current date. The Tracking Number (if provided) to the related shipment is updated. If Tracking Number is NOT provided, the field is left as null on related shipment, and a message is sent to the log file as, <TimeStamp> Tracking Number not provided for PO <PO Num>. The related shipment is updated to Shipped status

Auto Receive for Drop-Ship ASN

For drop-ship ASN POs, there is an ASN script to receive and close a PO if the ASN is associated to a drop-ship PO. When ASNs are created from inbound EDI-856, a check verifies if ASN is related to a drop-ship PO, and if Yes and items match PO quantity, the following actions are automated:

Create Receiver
Receive all items
Save the Receiver
Close the PO
Apply Tracking to related customer shipment
Set Ship Date to related customer shipment

Update shipment status to Shipped
Update order status to Shipped or Partially Shipped, as appropriate
Send Full Ship or Partial Ship Notification email, as appropriate

Use the System Setting for "EDI Error Email Address" in Order Lifecycle Management > Production to identify an email address for error notification emails. If ASN doesn't match quantities, an error email is sent to the designated address.