Feature - Fields Added to User-Defined CSV to Support EDI 846

Release date: 9/10/2019

Version 8.5 & up

The primary purpose of this enhancement is to support EDI 846 (Inventory Advise). If you do business with e-retailers like Amazon, Target, Wayfair, Home Depot, Lowes, etc., they often request that you provide updated inventory information a few times a day so that when their prospective customers are searching on their website, they can have your up-to-date inventory quantity.  

Define the User-Defined CSV Layout to Support EDI 846
To make this happen, you will go to I/M -> Reports -> Reorder Advice/User Def CSV -> Maintenance -> User Defined CSV Layout. Define a CSV export of the following columns:
A: [I] Item Number
B: [D1] Item Description 1
C: [D2] Item Description 2
D: [N1] UPC Code
E: [QH] Qty on Hand
F: [QA] Qty Allocated
G: [1Q] Qty on Order
H: [1D] Date Qty Available
I: [AY] Activity Code
J: [PC] Product Category
K: [IC] Inventory Class
L: [UC] Item User Defined Code
M: [UM] Item Stocking Unit of Measure
N: [SU] Item Selling Unit of Measure
O: [SR] Selling to Stocking Ratio    
P: [CI] Customer Item Number   (optional - if required by trading partner)  
Q: [L] Location (optional - if you have multiple physical locations to report inventory)
See sample screen below:


You can then use Elliott's deferred processing function to export this layout to CSV files several times a day. The exported CSV file can then be picked up by Elliott SPS Service, interfaced to SPS commerce and transmitted to your trading partner as an EDI 846 (Inventory Advise) document.

There were several fields required on this CSV that we did not support in the past. This feature supports the new columns needed for EDI 846. In addition, two existing fields have been improved to add more options on the ATP records included for calculation.

Customer Item Number
The last column "CI" (Customer Item Number) is optional. Your trading partner may or may not require you to provide their item number (Buyer's Item Number.) If they do require it, then you will need to set up their customer item number in Elliott COP -> Maintenance -> Customer Item. When you add the "CI" column to the CSV layout, you will need to specify which customer.  In the above example, we use customer# "OSH951."  That means this layout can only produce an Inventory Advise CSV for customer# OSH951. if you are not required to specify the customer number, then you don't need to add the "CI" column, and thus the CSV is generic and can be used for various trading partners.

1st Pending Receiving Qty & Date
As for columns 1Q (1st Pending Receiving Qty) and 1D (1st Pending Receiving Date), they are already supported. The purpose in providing these two columns in EDI 846 is in situations where you do not have quantity on hand. Your trading partner may be interested in knowing when you are going to receive them and how many. 

If you are an importer, it is a common practice for you to enter the scheduled receiving transactions into Elliott warehouse receiving or a regular receiving module as soon as the items are on the vessel headed for you.  These receiving transactions will normally be organized by a vessel ID (batch) with a scheduled receiving date.  You wouldn't post the items on the vessel until the container actually arrives your warehouse. These scheduled receiving transactions are reflected in the ATP and their dates are highly reliable because they are already at sea. In our previous implementation, 1Q and 1D columns always look for the first RW (Scheduled Warehouse Receiving) or RR (Schedule Regular Receiving) ATP record to determine the First Pending Receiving Quantity and Date. 

Since we need to assume that it is possible that you don't use the scheduled receiving function in Elliott, we may need to get the 1Q and 1D information from P* (Purchase) ATP records.  Also, if you are a manufacturer, you may want to look at the scheduled production, which are the B* (BOMP) ATP records.

For the above reasons, we now introduce a new flag in Global Setup -> Dist -> IM Global Control -> Screen 4.  
    9. ATP Type for IM User Def CSV 1st Pending Recv?
The default value of this field is "R," which indicates that the value of the results will remain the same with only RR and RW ATP records included.  If you don't use Elliott's scheduled receiving feature, then you should enter "P" and all P* (Purchase) and R* (Scheduled Receiving) records are included.  If you are a manufacturer and wish to include your BOMP work order's scheduled production, you should enter "A," and all B* (BOMP), P*, and R* records are included. See sample screen below:


Also, we added support for two new fields in user-defined CSV layout:

Selling UOM and Ratio
Type SU - Selling Unit of Measure
Type SR - Selling to Stocking Ratio

If your selling UOM is different from your stocking UOM, chances are your trading partners are more interested in the selling UOM and quantity instead of the stocking.


Keep in mind that the maximum number of items can be in an EDI 846 (Inventory Advise) document is 10,000.  You should make sure that you don't create user defined CSV file with more than 10,000 records with your selection criteria. 

Exported File Naming Convention
Keep in mind Elliott SPS Services (ESS) will only pickup file with extension EXP.  So even though the file exported by this process has CSV format. But the name must end with EXP in order to be picked up by SPS.  The typical file name and path would be like:
    ....\TestOut\IB{NAME}     during the testing period
or
    ...\Export\IB{NAME}      after go live
Where .... is the FTP folder that ESS can access. IB is the hard coded two digits for ESS/SPS to recognize that this is EDI 846.  {NAME} is the partner ID (decided at the time of implementation) like AMAZON, HOMEDEPOT, LOWES...etc.


Modified programs: IMCCLTYP.WS, IMCCLSTP, IMCCLMNT, IMSLSHCP

DLM

Elliott Version 8.5

  1. V8.5 Alpha Document Number Support
  2. Crystal Report Conversion for V8.5
  3. The Run Local or Hybrid Feature in Elliott 8.5
  4. How to Use EL850DB.EXE Utility to Create PSQL Databases
  5. Showing Document Date in Links After Elliott 8.5
  6. The Lessons We Learned from Upgrading Web Service 8.2 to 8.5 in eStore
  7. Feature - ASCII File Filter Condition in Mass Email and Export Processor
  8. Feature - List Users Acively Logged into Elliott and Optionally Send Email
  9. Feature - Allow Print One Invoice to Print Duplicate Invoices for Order Not Posted
  10. Feature - Print Range of Duplicate Unposted Orders
  11. Feature - Prevent Duplicate Invoice Numbers with Invoice Cross Reference File
  12. Feature - Last Year Net Income Layout Support
  13. Receive Message "Not Found" When Trying to Set Up Run Local
  14. Receive 'Invalid Column Name' Message After Starting to Use Alphabetic Document Numbers
  15. Feature - Invoice Log Report
  16. Feature - Add Sales or Usage to Where-Used inquiry
  17. Feature - Case Size Support for Quantity Per Box
  18. Feature - Exclude Obsolete Customers from Customer Generic Search
  19. Feature - Refresh VICS Bill of Lading
  20. Feature - Support Item Case Size in New Item CSV Import and Change Existing Item Import
  21. Feature - Copy Notes, Attributes, and Links When Copying Item Through the New Item CSV Import
  22. Feature - Enhanced Cash Receipts Processing Apply-To Range
  23. Feature - Add Links Import to System Files Setup
  24. Feature - Shipment Email Acknowledgement for Bill-To Customers
  25. Feature - Restrict Sending Tracking Number to Bill-To Customer in Shipment Email Acknowledgement
  26. Feature - Allow Source Range on Credit Card Log Report
  27. Feature - Indented Bill of Material CSV
  28. Feature - Stock Status Reports Add Include with Alloc or On Order Quantity Option
  29. Feature - Release Manually Held Orders
  30. Feature - Create Shipment Records When Complete Bill Of Lading
  31. Feature - Print Warning Msg for Cancelled PO Line Item
  32. Feature - Export 25-Character PO Number in Expanded Aging Report CSV File
  33. Feature - Show Pending Cash Receipts in Payment History Inquiry
  34. Feature - Show Customer Note Fields in Payment History Inquiry
  35. Receive "Error Getting List of Override Reports" When Printing Report
  36. Feature - Fields Added to User-Defined CSV to Support EDI 846
  37. Feature - Credit Memo Warning When Fully Paid
  38. Feature - Create Shipment Verification Box Records Through Billing CSV Interface
  39. Feature - Show Box ID on Order Inquiry Shipment Data Screen
  40. Feature - Print Error Message If Inventory Transaction Distributions Are Missing
  41. Feature - Customer CSV Import
  42. Feature - Alleviate Error 25 When Two Users Import Sales Orders Simultaneously
  43. Feature - Use Note Type for Special Instructions on VICS BOL
  44. Feature - VICS BOL to Enforce Shipment Verification Before Printing of BOL
  45. Feature - Order/Invoice Inquiry Box Serial Number Drill Down
  46. Feature - Delete Order Tracking Note When Void Completed VICS BOL
  47. Feature - Picking Ticket For Customer 2 Event
  48. Feature - Set All Options to Allow or Disable in User Global Security
  49. Feature - Stock Analysis Creation by Customer Range
  50. Feature - Print Work Order Planned Hours on Plus Work Order Traveler
  51. How to Ensure Local Elliott Folder Is Up to Date
  52. Feature - Global Setup Flag to Update Tracking Note from Box Data Window
  53. Feature - Packing List by Box One Box Per Page
  54. Feature - Move EDI Profile Maintenance Maximum # of Item Per Label
  55. How to Update Elliott 8.5 License Key Code
  56. Installing Elliott 8.5 and Received "PSQL v11, v12 or V13 Is Required" Message
  57. Feature - Warehouse Receiving Missing Item Attribute Event
  58. Feature - Added a Drill Down to Order by Item Inquiry in Newly Received Items Inquiry
  59. Feature - Customer Type Display in Pick Order Processing
  60. Elliott V8.5 Configuration Utility (EL850CF.EXE)
  61. Feature - Add Customer Type to Pick Ticket Selection
  62. Feature - Void Checks after Posting Warning for Multiple Checks
  63. Error 1315 Unable to Write to the Specified Folder When Installing Elliott 8.5

Feedback and Knowledge Base