Avi Weissbard - Cybermac software LLC
My feedback
-
1 voteAvi Weissbard - Cybermac software LLC
shared this idea
·
-
3 votesAvi Weissbard - Cybermac software LLC
supported this idea
·
An error occurred while saving the comment -
2 votesAvi Weissbard - Cybermac software LLC
supported this idea
·
-
2 votes
An error occurred while saving the comment Avi Weissbard - Cybermac software LLC
commented
Also as we know the report is driven by the date of the transaction and not the document date. If Netcellent is making a change maybe the Doc Date can be used as an alternate key to allow selection by document date. Currently users make a wider range and filter the output in order to get information by doc date.
Avi Weissbard - Cybermac software LLC
supported this idea
·
-
1 voteAvi Weissbard - Cybermac software LLC
shared this idea
·
-
2 votesAvi Weissbard - Cybermac software LLC
supported this idea
·
-
11 votesAvi Weissbard - Cybermac software LLC
supported this idea
·
-
3 votesAvi Weissbard - Cybermac software LLC
supported this idea
·
-
2 votesAvi Weissbard - Cybermac software LLC
shared this idea
·
-
2 votesAvi Weissbard - Cybermac software LLC
shared this idea
·
-
2 votesAvi Weissbard - Cybermac software LLC
shared this idea
·
-
2 votesAvi Weissbard - Cybermac software LLC
shared this idea
·
-
12 votes
An error occurred while saving the comment Avi Weissbard - Cybermac software LLC
commented
Allow Misc. Charges on COP to be 6 digits and 2 decimals (currently maximum of 99999.99).
An error occurred while saving the comment Avi Weissbard - Cybermac software LLC
commented
SYZIPCDS table primary key is a 5 digits zip code. The maximum size is 5 digits. Canadian postal code is in the format is of “XXX XXX”. At this moment, Elliott can’t populate Canadian postal code to SYZIPCDS table due to the database incompatibility. I suggest to change the table in version 9 so Canadian zip codes will be supported.
An error occurred while saving the comment Avi Weissbard - Cybermac software LLC
commented
Add a FIPS County Code. With the increasing demand to pay sales tax for nation wide transactions (as far as I know now apply to CA, IL, OH and AL) and the need to report total sales by jurisdiction, and the assumption that we will NOT have all the possible jurisdictions in Elliott, we need to capture the FIPS code. This is available now using the zip code database but there is no logic to attach it to the order. Edward, I am using the Job field to capture it for the Amazon orders' import, but it will be nice to add a unique field. When running the Sales tax liability report, we can subtotal by juristriction which is required by the sales tax portals.
An error occurred while saving the comment Avi Weissbard - Cybermac software LLC
commented
Increase COP Ship To to 6 characters. With more businesses selling nation wide through Amazon, Groupon etc. and with a need to trace these different ship to's we need a bigger field size. The current 4 characters field size allows 1,679,616 combinations if you use numbers and letters. Cybermac has the logic to create Ship to codes for these combinations. This looks as a big number but with a realistic 2000 orders per day it will not hold for very long time.
An error occurred while saving the comment Avi Weissbard - Cybermac software LLC
commented
I like the changes. Few comments that Dan and I thought of:
1. Search by name (Customer, Vendor, Item). I assume that the upper case search field will be eliminated but we will be able to continue to search by name and will be case sensitive.
2. Replacing the Note fields by Attribute - will we be able to search by these attributes? Currently many of my customers are using the Notes' fields as a search for their customer's number. In some cases there are 2 or 3 cross reference numbers for the same customer (currently kept in a Note field) and I am not sure how the search can be done after the change.
3. I see the Order Number, Invoice number etc are going to 9 digits. I didn't see the PO number and would like to see the PO number being 9 digits (or 9 + 2 with the release number) as well. This is extremely helpful for the Petroleum industry.
4. Price at 9,999,999.9999. There are situations where the unit price is more than $1,000,000. I suggest to allow a unit price accordingly.
5. Cost with 5 decimals. In some situations the "M" unit of measure is not allowed and it is necessary to present the cost with 5 decimals. There are Tax Jurisdictions where translating the tax to a number will cause 5 decimals. These are usually Petroleum Tax.
6. I assume Lot number will be changed to 18 characters as well.
7. I like to see Lot functionality on the same or close to the Serial processing level. I see the improvement of preventing splitting a COP line to multiple lines because of the different lots (nice !!!) but would like to see a better functionality in areas such as Inventory Transfer.
Thank YouAvi Weissbard - Cybermac software LLC
supported this idea
·
-
3 votesunder review ·
AdminEdward M. Kwang - NETcellent System, Inc.
(CEO / Founder, NETcellent Systems, Inc.)
responded
We will have our system developer evaluate this request
Avi Weissbard - Cybermac software LLC
shared this idea
·
-
3 votesAvi Weissbard - Cybermac software LLC
supported this idea
·
-
4 votesAvi Weissbard - Cybermac software LLC
shared this idea
·
-
4 votesAvi Weissbard - Cybermac software LLC
shared this idea
·
-
2 votesAvi Weissbard - Cybermac software LLC
shared this idea
·
-
1 voteAvi Weissbard - Cybermac software LLC
shared this idea
·
-
5 votesAvi Weissbard - Cybermac software LLC
supported this idea
·
Excellent idea. Also the U with previous periods functionality is excellent !!!