AdminEdward M. Kwang - NETcellent System, Inc.
(CEO / Founder, NETcellent Systems, Inc.)
My feedback
61 results found
-
2 votes
An error occurred while saving the comment -
3 votes
An error occurred while saving the comment We will evaluate this for Elliott V9
-
2 votes
An error occurred while saving the comment We will do this for Elliott V9
-
1 vote
-
1 vote
An error occurred while saving the comment We have no plan to support item cost at the warehouse level. We suggest you to use a different item.
-
3 votes
-
3 votesAdminEdward M. Kwang - NETcellent System, Inc.
(CEO / Founder, NETcellent Systems, Inc.)
supported this idea
·
-
3 votesunder review ·AdminEdward M. Kwang - NETcellent System, Inc.
(CEO / Founder, NETcellent Systems, Inc.)
responded
In addition to the potential complicated programming effort, I think the main issue is security. It is obvious that we don’t want all people who enter a credit memo also perform credit card refund. This may be something we can evaluate again in Elliott V9.
AdminEdward M. Kwang - NETcellent System, Inc.
(CEO / Founder, NETcellent Systems, Inc.)
supported this idea
·
-
3 votes
An error occurred while saving the comment We are aware of this might happen. But we are not sure how frequent this issue happen or under exact what condition this will happen. At this moment, we are not aware of a better solution than the current method to delete the orphan user session from PSQL engine.
-
1 vote
-
1 vote
An error occurred while saving the comment We had reviewed this issue in depth and we can't address this issue in any reasonable manner. Any changes will cause bigger problem in other area. At this moment, we are not going to address this issue. Instead, we are asking you to consider a few things in your procedure: (1) We suggest you not to perform GL interfacing while the posting is taking place. A lot of our users use defer processing at night to perform posting. That would certainly address this issue; (2) When interfacing with G/L , please interface distribution in the past, not the current date; (3) The chances of the out of balance increase because the distribution file is not purged and cause the interface take forever to complete which increase the chances of conflict. Therefore, we recommend you to purge your old distribution records to speed up your interface.
-
2 votes
An error occurred while saving the comment Expanding of the AP invoice number came up many times before. In our next major version, we plan to expand the AP invoice number from 8 digits to 12 digits. We do understand that there are certain vendors (especially, trucking companies) will send you invoices over 12 digits. On the other hand, if we expand the maximum invoice number field to something like 25 digits, then it will cause difficult with displaying it on the screen because there are only so much real estate space. The common strategy to deal with this type of long invoice number problem is to use AP Voucher Reference. Enter the long invoice number on AP Voucher Reference. Then you should also go to Global Setup -> Acct -> AP Global Control. Turn on the following flag: "1. Print Voucher Reference On A/P Check?"
-
1 vote
An error occurred while saving the comment Dan, in the original modules design, IM (Inventory Management) is a lower layer module than PO (Purchase Order). That is, you could have IM module, without PO module. But not vice versa.
Even though most of the user perform Landed Cost calculation through PO module, but user could perform do that base on the receiving transaction in IM Inventory Transaction Processing as well. Therefore, placing the report under the IM module making more sense than PO module. Just FYI
-
3 votes
An error occurred while saving the comment Dan, I like your idea. This is probably something we should look at in Elliott V9.
AdminEdward M. Kwang - NETcellent System, Inc.
(CEO / Founder, NETcellent Systems, Inc.)
supported this idea
·
-
1 vote
An error occurred while saving the comment There are two concerns with implementing this feature: (1) This particular feature is complicated. Especially the logic to ensure good performance now we are printing against the invoice history database; (2) The coding with DYO is difficult to maintain.
We are considering moving away from DYO. We can't be sure if we are going to create something new to replace DYO in Elliott V9 or continue to support it. If you can implement your invoice form with standard Elliott form, we would encourage you to do so.
-
3 votes
-
1 vote
-
1 vote
-
2 votes
An error occurred while saving the comment Did you try the function at PO -> Processing -> Purge Closed Purchase Order?
-
3 votes
We could add a global setup flag to treat non-stock item like a stock item in shipping verification, and by default this flag is not enabled so it does not affect other users.