When you need to email the Pick Ticket to a remote warehouse (might be a 3rd party), it will be nice to use the Post Office.
1. Add the Pick Ticket as possible Post Office Document.
2. Allow to assign the Pick Ticket on the eContact of the location. Elliott allows to add an eContact to a location in the Location file maintenance.
3. In order entry add the eContact of the location to the order.
4. When printing Pick Ticket, allow Post Office (now only PDF is allowed).
Cybermac plans to create a modification that will do the above but it is always better to have these modifications done by Netcellent. Also I am aware that in version 9 we might be able to have multiple locations on one order that of course changes the above concept.

Resolve Cost Adjustment Issues Across Multiple Asset Accounts

Currently, if you post a Cost Adjustment to an item that has QOH in multiple locations, with a different assigned GL Asset Account per location (via material cost type/location account control), the system defaults to writing the _entire_ adjustment (qty summed across all locations) to the asset account indicated by the transaction location. If posted, this creates immediate discrepancy between effected GL Asset Account balances and the Stock Status by GL Report. Would like to see the system pre-fill distributions to accommodate this scenario, allowing user to choose final distribution account(s) to offset the re-valuation. Example screenshot attached.

Our business model is 90% direct ship orders. Right now there is no correlation between the Sales Order and the Purchase Order number which is causing us lots of issues due to the volume of orders we take. I've been told there is nothing on the table to assist with this. One idea given to me is to use the job # field for both the Sales/Purchase Order for a stop gap. That is great, but I have to run a report on the PO side in order to find the Job#. I'd like to be able to query the PO side by Job #.

If a customer has an EDI Partner profile setup, general speaking, they would (1) need a valid PO number; (2) need the PO number be less than 22 digits because that's standard EDI limit.

For (1), we should setup a flag in EDI trading partner profile to indicate whether PO number is required or not. For (2), it is safe to assume that if the EDI trading partner profile is setup for the customer, then the PO length should not exceed 22 digits. Currently, Elliott allow 25 digits PO number.

The implementation should apply to the following areas: (a) COP Order Entry; (b) COP Copy/Consolidate Order; (c) COP Sales Desk. We probably do not need to apply to Sales Order Import or web services because we can assume the original data should not have this issue.

We can look at the existing coding and implement changes by following CHECK-DUP-PO paragraph.

Currently when receiving a partial shipment against a purchase order we are able to record the receipt and the PO inquiry shows the original order and received quantity correctly. This creates a "back order" quantity due on the PO. Item quantities on order fields show the back orders still open as long as the PO is not closed during receiving.

Reprinting the PO shows the original item Quantity and extends the amounts based on the original quantity.

It would be helpful to have a utility to reprint partially received POs showing the back order quantity and the new item extensions. This would be a big aid in both the receiving as well as invoice reconciliation process.

Alternately, instead of a separate utility there could be an option when posting receipts to "Reprint Partially Received POs". Y/N

We had the following situation on a customer site:
1. User intended to add a "faked" email address. This adress is added to customers that do not want to receive an email for the invoice and do not need a printed invoice. (a hard copy of the invoice is delivered and when running duplicate invoice (after posting), it is not necessary to get a hard copy or an email). This is a valid process.
2. After adding the faked email econtct, user changed the email address to one of the real emails of this customers. This was a mistake.
3. As a result the email of step 2 above received all the emails that went to the faked email. There were many emails and the customer was able to see other customers' invoices which is always bad.

We changed the faked econtact details Name, Company, Address etc. to say DO NOT CHANGE THE E-MAIL !!! in order to prevent future mistake.

A warning " Are You sure you want to change the econtact email?, This can cause a problem " or similar message, could help as well.

There is no elegant way to print a duplicate invoice for an order that is not yet posted. Printers sometimes have issues or some other printing errors can occur while printing an invoice. Bad toner, bad printout, etc... If the invoice does not physically print there are only 2 options to get the invoice printed that I know of.

1. Print a duplicate invoice using Print Invoices. This can be done, but will also lock all users from printing invoices if the user does not complete the task quickly enough. This options is not good for users not skilled in Elliott enough to get it done quickly.

2. Void the invoice and reprint it using Print One Invoice. This works, but unnecessarily burns invoice numbers just to get an invoice to print.

If an order is not yet posted, allow the duplicate invoice to be printed in Print One Invoice if it meets all of the criteria to be printed.

Currently, when print packing list, the total weight is always printed at the the bottom of the packing list like:
TTL WEIGHT - 999,999.999
It has been suggested by some users that the total weight in Elliott is not necessary correct due to various reasons. Therefore, it would be desirable if the packing list does not print total weight. We could potentially introduce a global setup flag for this purpose. If we should make this change, this flag should apply to both regular packing list, as well as packing list by box.

Please let us know how do you feel about this change.