AdminEdward M. Kwang - NETcellent System, Inc. (Admin, NETcellent Systems, Inc.)

My feedback

  1. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    As for the archiving issue, we are working on allowing alphabetic invoice number. It is still 6 digits like now. But because alphabetic characters are allowed, it will greatly enhanced the number of invoice number that can be stored in the 6 digits space so you will probably never have a need to archive after. We plan to release this feature in Elliott 8.3 before the end of the year.

    It has no impact to InvoiceInquiry web services as it draw the data from invoice history database.

    Currently, we noticed some of our customers get duplicate invoice number assigned as the invoice is printed. Elliott posting routine will catch this and prevent the duplicate invoice from posted, so it is still safe. But the invoice is already printed and maybe sent to customer already. This cause operation difficulty. So our focus is to prevent assigning duplicate invoice number in order header, in the mean time, provide an auditing database of invoice printing activities.

  2. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    It will be difficult to support adding "Productive" operation once the production is started. We can have calculation integrity issue. But adding a "Setup" type of operation is doable. So rework can be done through adding new "setup" operation in between two operations.

    We could always void the printed work order, and allocated it, then go back to change the work order. Once change the plus work order, re-print it.

  4. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

  5. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

  7. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    It is possible to use line item audit trail database to create some kind of revision history by date for order inquiry. We could provide a function key and when user choose, it will bring up a list of entry base on line item audit trail by date. We have to exclude the header record in CPLINAUD which is related to changing the shipping date on the order header. From there, user can drill down to the detail. Because the database of line item audit trail is different from PO revision history, so the presentation will be different. But we probably can make it somewhat similar and useful.

  8. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Print one invoice use the regular invoice printing routine and so it already support event. I think the issue is you can't tell whether the invoice was a duplicate invoice from print one invoice function.

    We have to be careful with several areas: (1) No new invoice number is assigned; (2) Customer file pick/invoice amount will not be updated; (3) credit checking....etc. should not take place; (4) no new invoice date should be assigned. As a matter of fact, no update should take place at all.

  9. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    We should implement this like PDF Post office but not using PDF at all. User can layout the email template by login as SUPERVISOR and make it enforce. The system manager need to be modified to support the variables so it will do a merge and present the final output per user's layout. This is a Jim's project.

  10. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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.

  11. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    We suspect this is not going to be an issue as we move toward the future. We had introduced phantom locking capability in customer and item file maintenance. So we will see how that reduce record locking and reevaluate this request.

  12. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    In Global Setup, ask user the folder name for each task of defer processing to store the non-email one. For example, user can specify CPINVPRT-No-Email as the folder name. Then during invoice printing, the PDF Post Office document that does not have the eContact will be sent to this folder (instead print a hard copy, which is not possible with defer processing.

    But we still need to change the CPINVPRT so it does not prompt for parameters in the printing screen.

    The main reason PDF PostOffice dos not allow to run in defer processing has to do with the requirement to check the select the printer tab. The printer tab is used when there's no eContact for a particular PDF PostOffice document, in that case, a hard copy is printed on the printer instead.

    Defer Processing, by design, does not allow printing to printer, and therefore is not compatible with the current PDF PostOffice design.

    An idea had been mentioned that we may print to the disk, instead of printer, when eContact is not found. We are evaluating if this is a viable method to move forward with future enhancement.

  13. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    We could add a global setup flag something like "Add number of days to pick ticket cut-off date". By default, the value = 0, so it is the system date. User can set it "1", so we will print all pick ticket that's schedule to ship today or tomorrow. Or you could set it to "999999", then we use the max date, which in this case is 12/31/30.

  14. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    To do this, we need to introduce a global setup flag to enable this feature (by default, not enable). This is necessary not to introduce un-expected changes to other users. If this flag is enabled, and the customer file "Transfer Days" = 0, then we can directly transfer the inventory to the target location without going through the transfer location. The posted invoice will be marked as "received". All ATP records will be adjusted accordingly.

  15. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    We will evaluate this for Elliott V9

  16. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    We will do this for Elliott V9

  17. 3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    We will add support for this in the SY12MONS table.

  18. 4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    When perform re-apply, system currently will assume to create a new record.
    If the new record key already exist, then we do not allow.
    We will evaluate to change so when the new record key already exist, we will perform a merge, instead of stopping it.

  19. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    We are evaluating to add the ability so we can add or change a ship-to in Sales Desk, or order entry, by using the special function. The system will launch add, or change ship-to task by pre-populate the customer number so users does not need to enter the customer again. But user still need to manually enter the ship-to number once back to the sales desk or order entry screen because these are two different process and we can't pass the ship-to number back easily.

  20. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    This should be doable with Elliott 8.3 which has the report writing capability

← Previous 1 3

Feedback and Knowledge Base