When doing Order Import, Netcellent introduced new flags, 26 and 27 that handles the move of a file with errors to a different folder, this is a good feature. For good files. Elliott deletes the import file. My understanding from a conversation with Mark is that this logic of NOT archiving the import file is because of the assumption that the file already created in an EDI system and exists there. But if the import is NOT from EDI (maybe the partner created it in the required format), forcing the user to save it in 2 places is an extra step. I suggest to add 2 flags, "Move good files to a folder?" and the folder location. If user answer N to the first question continue to delete the file, but user will be able to save the import file. There is a point of the file name (in case the same file name is used), so adding a date-time stamp to the file name will prevent overriding previous files. Thanks.

We would like to be able to create bills of materials with out using obsolete items. It would be nice to have a pop up window when you enter an obsolete item that tells you it is an obsolete item and wont allow you to use that item. We may have machinery out in the field that has the item that is now obsolete that we might still sell to them but we would like not to have the option to even use that item in a current build when creating the bill of material. I understand the "Transition an item to Obsolete" feature but it would be nice to have it go a step further and not allow BOM process to not allow the use of the obsolete item.

We will introduce a Order Invoice Cross Reference File to be introduced in Elliott 8.3. The file structure is as below:
Order# Primary key
Invoice# Primary Key, Alternate Key-1 (Allow Duplicate)
Status Primary Key, Alternate Key-1
Date Stamp Primary Key, Alternate Key-2 (Allow Duplicate)
Time Stamp Primary Key, Alternate Key-2
Sequence No Primary Key, Alternate Key-2
Date Pick
Date Selected
Invoice Date
Ship Via
Invoice Amount
Freight Amount
Misc. Charge Amount
Sales Tax Amount 1
Sales Tax Amount 2
Sales Tax Amount 3
Payment Amount
User ID
Filler

This file is to be updated at time of invoice printing as soon as the order record is rewrite. Keep in mind the first rewrite is to update the status from "S" to "N". Once user answer "Yes" to printed OK, there will be a second rewrite, which will change the status from "N" to "X". If user answer "No", then the second rewrite will change the status from "N" to "S". If user choose to void the invoice later on through the "Void Invoice" function, we will change the status from "X" to "S" as well. Once the invoice is posted, we need to update the status field to "Z". So the "Status" field could have value of "S", "N", "X" and "Z". We keep the record for "S" because an actual invoice hard copy was created. If user question why there's a hard copy invoice, but there's no record in Elliott, it could be because they answer "N", or it could be because they void the invoice. So having a table that show a record as soon as the invoice copy is printed will give us the ability to perform auditing better down the road.

The primary key will show all the invoices had ever printed for this order.

The Alternate Key-1 will show if this invoice had been printed. If yes, and the status is "N", "X" or "Z", then it will be problem. We should assign the next invoice number and check duplicate again. We will repeat this process until it is not duplicate and reflect ARCTLFIL for starting invoice number accordingly. The checking of duplicate invoice number should check CPINVHDR as well.

The Alternate Key-2 is designed to show each batch of invoice printing (Date Stamp + Time Stamp). The Sequence No is to establish the sequence of printing within the batch.

Because an order can be invoiced multiple times, so the following fields in the order should be saved with this file for better auditing:
Date Pick
Date Selected
Invoice Date
Ship Via
Invoice Amount
Freight Amount
Misc. Charge Amount
Sales Tax Amount 1
Sales Tax Amount 2
Sales Tax Amount 3
Payment Amount

At this moment, we only utilize this file to check duplicate invoice number during invoice printing. This feature does not apply to invoice history invoice printing, and pick up pending invoice printing.

We may choose to support other functions in the future including: (1) Show all invoices for the order (including the not posted or abandon invoices); (2) Use it as invoice log. The difference with the existing CSV invoice log is that this one does not require user to turn on. Also, this one is an index file so we can provide the log with Elliott user interface.

It is suggested that in item generic search, we have the option to show item quantity per global setup. It is suggested that, we need to allow user to press a flag that only show those item quantity is greater than zero so customer service rep can focus on those item that we have on-stock.

Currently, the bottom line of the item generic search can as following:
Up, Dn, PgDn, PgUp, F4=Detail
Up, Dn, PgDn, PgUp, RETURN To Select
Up, Dn, PgDn, PgUp, F4=Detail F5=Wish List
Up, Dn, PgDn, PgUp, F1/F2=Next/Prev Loc F3=Setup F4=Detail
Up Dn PgUp/Dn F1/F2=Next/Prev Loc F3=Setup F4-Detail F5=Wish

We can modify to allow F7 key which is a toggle key to display between showing Qty > 0 only, or show all items. See below:
Up, Dn, PgDn, PgUp, F4=Detail, F7=Qty>0
Up, Dn, PgDn, PgUp, F4=Detail, F7=QtyAll
Up, Dn, PgDn, PgUp, RETURN To Select,F7=Qty>0
Up, Dn, PgDn, PgUp, RETURN To Select,F7=QtyAll
Up, Dn, PgDn, PgUp, F4=Detail, F5=Wish List, F7=Qty>0
Up, Dn, PgDn, PgUp, F4=Detail, F5=Wish List, F7=QtyAll
Up,Dn,PD,PU,F1/F2=Next/Prev Loc,F3=Setup,F4=Detail,F7=Qty>0
Up,Dn,PD,PU,F1/F2=Next/Prev Loc,F3=Setup,F4=Detail,F7=QtyAll
F1/F2=Next/Prev Loc,F3=Setup,F4-Detail,F5=Wish,F7=Qty>0
F1/F2=Next/Prev Loc,F3=Setup,F4-Detail,F5=Wish,F7=QtyAll

The F7 key will only be available if the Global Setup -> Dist -> I/M Global Control, field "4. Item Generic Search With Avail/Excess Qty" = "Y".

The Qty to filter depend on whether we are displaying Item Qty Avail, Location Qty Avail, or Excess Qty (which is base on another Global Setup Flag).

Special logic need to considerate when user press F5, there may not be any item qualify to display in some situation, and the program still need to handle it gracefully (maybe reverse the toggle key back after showing no item to display, because it obviously make no sense to display no item in generic search screen). Also, the search show base on the current pointer of item, not a starting over search when F5 key is pressed.

For users who do temporary year end, from the time of temporary year end to the final year end, the General Ledger Balance Sheet will be out of balance.

This is because the Balance Sheet Net Income (BSNI) only calculate the number from this year once you do a temporary year end. In the mean time, the detail transaction for last year is still there because final year end is not done.

It has been suggested, that we can introduce another financial statement layout code:
LYNI = Last Year Net Income
This is similar to BSNI. But LYNI only reflect last year data. It will only have value after the temporary year end, before the final year end. If the value is zero, then do not print this line on the balance sheet at all. If you should include this code on your balance sheet (presume before BSNI) then your balance sheet will be in balance even after the temporary year end. Let us know if you think this is a good idea for you.