Elliott Forum

Post your ideas, questions, or feedback.

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Check If Valid PO Number Entered for EDI Trading Partner

    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…

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Admin →
  2. F4 - Showing Purchase order Revision level on ATP drill down

    In the ATP inquiry section when drilling down to a purchase order it would
    be nice to see the F4 revision level (like under purchase order inquiry).
    Going further it would be nice that it would automatically go the the specific part number based on the part number you are working with to
    save time.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Admin →
  3. Option to Supress Total Weight When Print Packing List

    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…

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Admin →
  4. Purge Utility for SYACTLOG (System Activity Log) Table

    SYACTLOG (System Activity Log) table contains the following kind of data:
    * Elliott Users Login
    * Web (Web Services) eContact Login
    * Email Activities
    * Credit Card Charges
    * Print Activities
    * Other activities
    This table tend to become very big and make it difficult to retrieve data. Currently, system does not have a purge utility for this table. It is suggested that we should provide a utility to allow users to purge this table for certain type of activities with cut-off date.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Admin →
  5. View Invoice from Invoice History Inquiry by Customer/Item

    When going into Invoice History Inquiry, if you look up invoices by item# you can select/highlight a specific invoice and see the details of.

    However, this option is not available when searching invoices by customer and then item#. You have to then go back or open another window to see the details of that specific invoice.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Admin →
  6. Prevent Two Conflict Defer Processings Running at The Same Time

    It is well known that if user run defer processing on two different workstations at the same time can cause problem. The following knowledgebase article show this may cause error 80: http://support.elliott.com/knowledgebase/articles/814293-btrieve-error-80-during-defer-processing. The type of error is not limit to Error 80. It can also be error 25. Another recent support incident shows that this cause quantity allocation double due to running reset quantity allocation at the same time on two different machine through defer. So running defer processing at the same time on different workstations is very problematic.

    Elliott does not prevent two Defer Processing tasks from running…

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Admin →
  • Don't see your idea?

Elliott Forum

Feedback and Knowledge Base