Are There User-Defined Fields in Elliott Sales Order for Analysis Purposes?

Are There User-Defined Fields in Elliott Sales Order for Analysis Purposes?

Release Date: 08/14/2025
Version: 8.x & Up

Q - Does Elliott has a Customer Order Field that could be used for "End Use Type?" This is the type of application the product is being sold to -- like datacenter, factory, residential, municipal, etc.

The field has to be associated with the order, and it would be entered during order entry process. We specifically want this field to have predefined options only. Can this be done with Elliott?

A - We have two different user-defined fields in the Elliott sales order:
  1. At Order Header Level - Job Number can become a user-definable field.
  2. At Order Line Item Level - Reason Code is also called User-Defined Code.
If both fields are already used for other purposes, you can use order header or line item attribute.  For more information on attributes, please look for associated documents.  Also, look at Elliott Export Processor, which provides great support for attributes.  Our focus of this article is to discuss Order Header Job Number and Order Line Item User Defined Code. We will not discuss attributes in this article.

Order Header Job Number

If you are not using Job Number in the order header, then you can redefine it for your own purpose. Below is an example where one of our customers used Order Job Number “4473#:”

You can go to Global Setup -> Cop-Func -> Order Header Screen -> Screen 2 and look for the following two flags:
28. Required Job No During Order Entry
29. COP Job No User Defined Literal
See sample screen below:


Also, in A/R -> Utility -> A/R Setup -> “18. Use Job Numbers?” flag determines whether the Job Number will be validated.  If you set this flag to “Y,” then you must define all valid Job Numbers in A/P -> Maintenance -> Job Code File.

Order Line Item Reason Code (User Defined Code)

Go to Global Setup -> Cop-Ctl -> User Defined Code, and change "1. user Defined Code Literal?" to the desirable literal.


Then, when you go to the Order Entry Line Item Screen, you will see the proper literal display at field 9. See sample screen below:


You can define the values for User Defined Code in COP -> Maintenance -> User Defined Cd File.


EMK

    • Related Articles

    • Elliott V7.3 Release Notes: What's New Since Elliott V7.2

      What’s New Since Elliott V7.2 Customer Relationship Management (CRM) CRM and beyond The center of Elliott’s Customer Relationship Management is eContact. eContact is an extension to the Customer database, as well as Vendor, Employee, Salesman, Sales ...

    • Feature - Display Line Item Reason Code in Order Inquiry

      Release Date: 1/12/24 Version: 8.5 and Above A new option has been added to Global Setup-> COP-Ctl-> User Defined Code-> field 8. Display User Defined Code In Order Inq. 8. Display User Defined Code In Order Inq - The default is N. A value of Y will ...

    • CPR01MNT Customer Order Processing User-Defined Code Maintenance

      User-Defined Code Maintenance Application Overview This feature gives you the ability to assign a “User-Defined Code” in the COP line item screen for special tracking purposes. In the Order Line Item Entry Screen, the system will prompt you to enter ...

    • Feature - Stock Analysis Processing

      Release Date: 10/28/16 This new feature is available under COP -> Processing -> Pick/Pack Tickets/Ship Labels-> Stock Analysis. This new feature is only available when the QTYAVAILBYCOMP, QTYAVAILBYCOM2 and QTYAVAILBYCOM3 attributes are in use. These ...

    • Feature - Sales Order Import Line Item Event

      Release Date - 6/29/16 A new event has been added when importing orders throught Customer Order Processing-> Util-Setup-> Sales Order Import-> Interface. The name of the event is Import Order Line Item Event under program CPORDIMP and type IMORDITM. ...