I Am Running Out of Invoice Numbers -- I Need Direction to Archive Invoices

Q: Within the next 6 months we will run out of invoice numbers.  I don't want to purge my invoice history because it contains valuable data that I would like to go back to in the future.  So I would prefer a method to archive my invoice history instead of purging it.  Can you provide the steps needed to perform an archive of invoice history? Also, can we archive invoices without archiving orders?

A: You can archive invoice history independent of orders.  In this document, I will show you the steps needed to archive invoice history. The strategy is to use Elliott's Multi-Company feature and create an archive company for historical inquiry purposes.  In Elliott, typically there will be a mapped network drive and a root Elliott folder to store data and programs. Just as a way to explain by example, the Elliott root folder may be:
        M:\Elliott7

Throughout this document, we will refer to the M:\Elliott7 folder even though that is not necessary your actual Elliott root folder. With regard to any instructions in this document that refer to M:\Elliott7, you can just change it to your actual Elliott root folder.  Your data will be stored in DATA or DATA_?? folders under the Elliott root folder.  For example, your company 1 data will be stored in the M:\Elliott7\DATA folder and your company 2 data will be stored in M:\Elliott7\DATA_02 folder. Using this principle, you can see how Elliott supports up to 99 companies.

Let's say your current company is company 1, so your current data resides in the M:\Elliott7\DATA folder.  Let's say that you wish to create an archive company 50 for archiving purposes.  Its corresponding data folder will be M:\Elliott7\DATA_50.  Throughout this document, we will refer M:\Elliott7\DATA as the current company data folder and M:\Elliott7\DATA_50 as the company created for archiving purposes.

So our strategy is to copy M:\Elliott7\DATA to M:\Elliott7\DATA_50. By doing so, we will create two Elliott companies that contain identical data initially.  Since modern servers often come with disk space much larger than the Elliott database, we will not have disk space issues using this strategy.  After the copying, we will delete invoice history data from the DATA folder so we can reset the invoice counter without worrying that the invoice number already exists in the invoice history database. Then company 50 can be used for archiving and history inquiries related to the invoice history that has been removed from the DATA folder.

To understand the background of this documentation, you should be aware of the database tables associated with invoice history.  In Elliott, the following database tables make up the invoice history:

  • CPINVHDR - Invoice Header
  • CPINVLIN - Invoice Line Item
  • CPINVOPT - Invoice Option (Kit/Feature or BOMP Material WO components)
  • CPINVRTG - Invoice Routing (BOMP Plus Work Order Related)
  • CPINVMTL - Invoice Material (BOMP Plus Work Order Related)
These tables reside in your current company M:\Elliott7\DATA folder. For example, you may bring up a command prompt, go to the M:\Elliott7\DATA folder, and use the following on the command line:
          DIR CPINV*.BTR
Then, you will see these corresponding tables show up.

M:\ELLIOTT7\DATA>DIR CPINV*.BTR
 Volume in drive M is Programs
 Volume Serial Number is 2EFF-394C
 Directory of M:\ELLIOTT7\DATA
07/10/2014  12:37 AM     1,065,222,144 CPINVHDR.BTR
07/10/2014  12:37 AM     1,214,373,888 CPINVLIN.BTR
07/10/2014  12:37 AM            61,440 CPINVMTL.BTR
07/10/2014  12:37 AM            65,536 CPINVOPT.BTR
07/10/2014  12:37 AM            57,344 CPINVRTG.BTR
               5 File(s)  2,279,780,352 bytes
               0 Dir(s)  372,678,299,648 bytes free

You may not see all of them depending on which Elliott features you are using.  All these tables have the BTR extension.  Throughout this document, we will use the command prompt to explain the actions that need to be taken.  You can use Windows Explorer to achieve the same result.

You must make sure that when you perform this archive procedure, there are no Elliott users in the system. Therefore, it is recommended that you do this either in the evening or on a weekend.  Furthermore, you can consider stopping the PSQL engine service on the database server while you perform the copying and delete steps to ensure there's no database activities can take place while you perform the archiving.

In addition, it is recommended that you do this at month end, or even better, year end.  Therefore, it is easy for everyone in your organization to remember that the invoice history before a certain cut-off date will be in the archive company.

Archive Procedures

In a straightforward scenario, you will take the following steps:
(1) Create a DATA_50 folder and copy all *.DAT and *.BTR files from e DATA to the DATA_50 folder.
(2) Follow the special procedure for tables exceeding 2 GB.
(3) Delete CPINV*.BTR files from the DATA folder.
(4) Initialize CPINV*.BTR files in the DATA folder.
(5) Delete other related tables.
(6) Apply NTFS Security to the New Archive DATA_50 Folder
(7) Change A/R Setup to use a new starting invoice number.
(8) Change Global Setup to point invoice history to the archive folder.
(9) Delete Invalid 5 Amigos Records.
(10) Delete COP Order Payment Records for Invoice History 
(11) Generate P/O Reference Files
(12) Change the new company with data in the DATA_50 company name so it is recognized as an archive company.

(1) Create And Copy DATA_50 Archive Folder

Go to the command prompt and make sure your current path is M:\Elliott7.  Then issue the following command:
        MD DATA_50
This will create the M:\Elliott7\DATA_50 folder. Now we need to copy Elliott data files. There are two types of Elliott data files, one type with the DAT extension, and another type with the BTR extension.  So from M:\Elliott7 directory, you will issue the following commands:
        COPY DATA\*.DAT DATA_50
        COPY DATA\*.BTR DATA_50
Also, it is possible that you may want to place your laser form company logo images in the DATA folder. So you may want to use the following command:
        COPY DATA\*.BMP DATA_50
You may also choose to copy the entire DATA folder to replace the above three commands:
        COPY DATA\*.* DATA_50
However, this may copy additional files, such as spooled report files and log files, which are not necessary for archiving purposes.

(2) Special Procedure for Tables Exceeding 2GB

In PSQL, by default each data file has a maximum size of 2GB.  For example, if the IMLSHST.BTR file exceeds 2GB, then it starts to create IMLSHST.^01, which is an integrated extension to IMLSHST.BTR.  If IMLSHST.^01 exceeds 2GB, then it creates IMLSHST.^02, and so on.  In that case, if you copy IMLSHST.BTR without copying IMLSHST.^01, or if you delete IMLSHST.BTR without deleting IMLSHST.^01, then you will receive a Btrieve file access error 002 when accessing that table.

If you use serial number tracking, then the IMLSHST.BTR file will tend to be huge.  NOTE.BTR is common too if you use note processing.  IMINVTRX.BTR (I/M Inventroy Transaction Audit Trail), which are typically huge as well.  The CPINVLIN.BTR file may also be large depending on the typical number of lines per invoice.  Verify if you have any tables exceeding 2GB.  I typically use the following command:
        DIR DATA\*.BTR /O-S/P
The parameter /O-S/P means order by reverse sequence of file size (the large ones show up first) and pause one page at a time.  This will cause the largest BTR files in the DATA folder to show up first.  If you see that your largest BTR file is 2,147,475,456, then bingo -- you have a data file that exceeds two 2GB.  If you do have data files exceeding 2GB, then you need to modify the above procedure to accommodate them accordingly. 

Be aware that the *.^01 file has special properties so if you try to copy that file directly, you will not be able to copy.  For example, if you use a command like
        DIR DATA\IMLSHST.^01
then you will not see that file.  But if you use 
        DIR DATA\IMLSHST.* 
then you will see it.  Also, if you use the "COPY DATA\IMLSHST.^01 DATA_50" command, it will not copy.  However, if you use "COPY DATA\IMLSHST.* DATA_50," then it will copy.  The following shows an example of an IMLSHST table that exceeds 2GB:
M:\ELLIOTT7\DATA>DIR IMLSHST.*
 Volume in drive M is Programs
 Volume Serial Number is 2EFF-394C
 Directory of M:\ELLIOTT7\DATA
08/14/2014  04:36 PM     2,147,475,456 IMLSHST.BTR
08/14/2014  04:36 PM       334,995,456 IMLSHST.^01
               2 File(s)  2,482,470,912 bytes
               0 Dir(s)  372,537,167,872 bytes free

(3) Delete CPINV*.BTR Files

Go to the command prompt and make sure your current path is M:\Elliott7. Then issue the following command:
        DEL DATA\CPINV*.BTR
This will delete all invoice history files from the current company data folder.

(4) Initialize CPINV*.BTR Files

We need to create the empty CPINV*.BTR files we just deleted.  Bring up Elliott and go to the current company (M:\Elliott7\DATA).  From the main menu, choose Util-Setup, then File Utilities.  From File Utilities, choose "Initialize," then choose "Customer Order Processing Files."  From "Initialize COP Data Files," find all CPINV* files and initialize them individually.

(5) Delete Other Related Tables

There are other related tables that should be deleted from the current company as well.  This includes:
        IMLSHST - I/M Lot Serial History (if you use the serial number tracking feature)
        CPBOXHST - COP Box History (if you use Shipping Verification)
        CPBOXFHS - COP Shipping Box History (if you use Shipping Verification)
        CPBOXHSR - COP Box Serial History (if you use Shipping Verification)
Follow the same principle as in steps (3)-(4) to delete the corresponding files and initialize them in the current company.

(6) Apply NTFS Security to the New Archive DATA_50 Folder

Depend on how you setup the NTFS security to your Elliott folder, you may have additional steps to apply NTFS security to the new DATA_50 folder.  Please see the following knowledge base article for more details:
    http://support.elliott.com/knowledgebase/articles/654601-elliott-8-0-directory-structure-and-ntfs-rights

(7) Change A/R Setup for New Starting Invoice Number

In the current Elliott company, go to Accounts Receivable and choose "Util-Setup," then "A/R Setup." Choose "Change" and change the first field:
        1. Starting Invoice No
Set the starting invoice number to, say "1000," and save the change.  You may choose whatever number you prefer, but you shouldn't choose a number that's too high or you'll reach the maximum of 999999 too quickly.

(8) Change Global Setup to Point Invoice History to Archive Folder

In the current Elliott company, go to Main Menu -> Util-Setup -> Global Setup -> Cop-Ctl -> Order/Invoice Inquiry. You will see the following two setups:
        4. Archive History is in Use ?
        5. Archive History Data Path (CPINV*.* & IMLSHST.*)
Set the flag "4" to "Y." Then set "5" to "M:\ELLIOTT7\DATA_50."

The purpose of this step is so that if your users go to COP -> Inquiry -> Invoice History Inquiry, the system is actually smart enough to look for the invoice history database from both companies.  It will look at the current company first for invoice history data.  If it can't find it, then it will go the archive folder as specified in field 5 to look for it.

(9) Delete Invalid 5 Amigos Records

5 Amigos refers to the following five systemwide features in Elliott
        Notes
        Attributes
        eContact
        Links
        Events
Out of these 5 systemwide features, Notes, Attributes, eContacts and Links may be related to Invoice History.  When the Invoice History database is deleted from the current company, there may be 5 Amigos records left behind, which become orphan records.  In the short term, there may not be any immediate impact.  But in the long run, this can lead to problems. For example, say that a NOTE record was created for invoice number 123456 and this NOTE record is not removed from the current company. After you reset the counter and when invoice number increases to 123456, you will find the new invoice 123456 will have this note attached to it, even though this note should belong to the invoice 123456 in the archive company.  This can create serious confusion.

To resolve these problems, there are existing utilities that address them:

(a) For eContacts: Bring up Elliott and go to the current company. Go to Main Menu -> Util-Setup -> Global Setup -> Utilities -> eContact Integrity Check.  This utility will remove all invalid eContacts relationships.  If you normally attach eContacts to COP Sales Orders for order or shipping acknowledgment e-mail purposes, or if you e-mail PDF invoices to customers, then it is likely you will have eContacts attached to the invoice history database.  You will probably see invalid eContact relationships deleted on this report when you run it.

(b) For NotesBring up Elliott and go to the current company. Go to Main Menu -> Util-Setup -> Global Setup -> Utilities -> Print or Purge Orphan Amigos. This utility can be used for Notes, Attributes, Events and Links. As for Notes, it is possible to attach Notes to Invoice Headers and Invoice Line Items.  Therefore, you should first choose the "type of Amigo to Purge" as "N" (Notes).  Then choose the Master File as "CPINVHDR" (COP Invoice Header).  For the "Purge" option answer "Y."  If you are not sure, you can answer "N" to the "Purge" question so the system can print a list of Notes records that would be deleted first. The following is an example screen:
 Type of Amigo to Purge  N
 Master File             CPINVHDR
 Purge?                  Y
Repeat the above steps for the "CPINVLIN" Master File.                                  

(c) For Attributes: Repeat the step (b) above for Attributes.

(d) For Links: It is unlikely that you will create a link for invoice history.  But if you do, repeat the step (b) above for Links.

(10) Delete COP Order Payment Records for Invoice History 

If you attached payment records to your COP Orders, then you are using the CPORDPMT table.  As the order becomes an invoice and posts to invoice history, the corresponding payment records for invoice history are created.  Unfortunately, we do not have a utility to purge records in the CPORDPMT table at the moment.  So if you use this feature, you will have to go to PSQL Control Center and issue the following SQL statement to delete all the CPORDPMT records associate with the CPINVHDR table:
        Delete from CPORDPMT where CPORDPMT_FILE_NAME = 'CPINVHDR'

(11) Generate P/O Reference Files

If you set up your Elliott system so that the COP Purchase Order Number is searchable, or duplicate the Purchase Order number in COP so it can be detected, then you are using this CPPOREF table in Elliott.  This table contains both Order and Invoice History data.  Since the invoice history is now located in the archive company, you should get rid of the corresponding records in the CPPOREF table. To do so, you may go to COP -> Util-Setup -> Generate PO Reference

(12) Change New Company to Reflect the Archive Name

Now go to the archive company 50 you just created.  Go to Main Menu -> Util-Setup -> Company Setup.  Change both Company Report Name and Display Name to reflect the fact that this is the archive data.  I typically put down the date of archive at the end of the company name so people can see clearly when the archive folder was created.

Additional Issues

COP Pickup Pending (CPPUDELV)

Few Elliott users use the Pickup Pending feature.  But if you do, then you have a headache here.  The primary key of this table is Invoice Number so if you don't purge it, it will create a future conflict. Most importantly, the pickup feature currently will not reference archive folder due to there's only few users using this feature.  So after the invoice history database move to the archive folder, you will not be able to use the records in pickup pending database. You will have two choices here:
(1) Use archive folder for pickup pending until all pickup pending records in the archive folder are gone.
(2) Do not use archive folder, instead issue credit memos for those pickup pending records, and re-issue the invoice in the current database.

In either case, you will need to delete and initialize the pickup pending table which is CPPUDELV from your M:\Elliott7\DATA folder.

Transfer Orders

If you use transfer orders and there are orders still in transit when this archive take place, then you should be aware of the following:
(1) Transfer orders receiving is based on invoice history. Therefore, you need to perform the receiving in your archive company when it finally arrived on the other end.
(2) The transit inventory is not going to moved to the final location in live company when you perform receiving of transferred orders at archive company, therefore, you will need to perform a manual transfer through I/M Inventory transaction processing to move the inventory over.

Serial Number Correction Tool

The Serial Number Correction Tool can't fixed the history records in archive company.  Therefore, you need to use this tool on both the archive and live company. if that should happen.

Database Rebuild

The above procedure may result in certain tables records deleted.  In PSQL database, when the data is deleted, it does not automatically return the disk space back.  To reclaim the disk space and for better database performance, you could consider the following data files in the DATA folder:
  • NOTE.BTR - Notes table. This is especially true if you have shipping tracking number stores in the note table.  As the invoice history is moved to the archive folder, the 5 Amigo Deleting steps can delete many note records attached to the invoice history.
  • SYCONREL.BTR - Contact Relationship table. This is especially true if you have eContacts attached to the order and invoice history.
  • CPPO*.BTR - PO Reference and related tables.
  • CPORDPMT.BTR - Order Payment table.

Database rebuild require Elliott users or web services that may access above tables to stop. If you are using PSQL 12 and above, there's a "Defragmenter" utility that you can use to reclaim the database disk space back real time while your users is in the system.

Known Issues with Archiving

The purpose of creating an archive company is so you can look up any past invoice history records by going to this archive company. You can either go to COP Invoice History Inquiry, or COP Invoice History Reports. The purpose of step (5) above to set up the archive folder in Global Setup is so you can go to COP Invoice History in the current company and still be able to reference the archive company invoice history records.

On the other hand, the Invoice History database is integrated in many areas throughout the Elliott system. Because the historical invoice history database is now moved to a new company, much of this integration will not work anymore. The following are known areas of this limitation:
  • The GUI Invoice History (from A/R, Customer, Special Function, Invoice History Inquiry, or COP, Processing, Sales Desk, Invoice History Inquiry) does not support accessing archived invoice history.
  • A/R Cash Receipt
  • Look up customer number by invoice number
  • Detail Interface from CSV file - when customer number is not provided 
  • COP Order Inquiry Drill Down to Invoice History
  • Even though the traditional invoice history (COP -> Inquiry -> Invoice History -> Invoice Inquiry by Invoice) supports archived invoice history, but it does not support the associated archived notes (tracking number), attributes, eContacts and links.

Other Considerations

There is no need to archive COP Sales History Transactions (CPHSTTRX) since the primary key of that table involves the invoice date.  In addition, the CPHSTTRX table is very compact so it uses a lot less disk space than the invoice history database. As a matter of fact, CPHSTTRX will serve as an invaluable data source for COP History to bridge the gap due to the invoice history archiving.


Systems Manager

  1. Mapped Drives Disappear After Logoff or Reboot
  2. Using Raw Data Pass Through for Dot Matrix Printer on Windows 10 Does Not Work
  3. How Do I Find The Workstation That's Infected with The Crypto Ransom Ware?
  4. How to Reset the Counter in *.DAT Files After Recovery from Crypto Ransom Ware Attack
  5. Aging Shows Differently After Database Rebuild
  6. What Do I Do When My Anti-virus Software Reports Elliott EXE File as a Virus?
  7. High CPU Usage and Performance Issues After Implementing NTFS Security
  8. "We can't verify who created this file. Are you sure you want to run this file?"
  9. Problem with Printer Configuration If Running Elliott from Multiple Workstations
  10. Inconsistent Elliott Error on Terminal Server
  11. How to Restore Elliott from CryptoWall Ransomware Attack
  12. Clarify Laser Forms Line Item Level Barcode Printing
  13. Is Dot Matrix Printer Still Supported in Elliott with Windows 10?
  14. Should I Install the 32-bit or 64-bit Outlook/Office?
  15. I Receive Error 114 When I Start Up Elliott on the Server
  16. Manage Data Execution Prevention (DEP) Through Registry Editing
  17. Windows Defender May Cause Elliott Start-Up Difficulties
  18. Why Do I Exceed Elliott User License Count When There are No or Very Few Users in Elliott?
  19. What Causes Load Error 198?
  20. How the Windows Scheme You Choose May Affect the Elliott Screen Display
  21. Still Get Error 114 After Adding All Elliott EXE Files to the DEP List
  22. How to Copy Laser Form Templates from Company to Company
  23. Weird Character Displayed for Backslash (\) Character
  24. Does Elliott Support Desktop Virtualization?
  25. Access Is Denied When Launching Elliott V8 Report Viewer
  26. User Cannot See Some Spooled Reports in Elliott V8
  27. Why Does the User List Function Take Forever to Bring Up?
  28. I Am Running Out of Invoice Numbers -- I Need Direction to Archive Invoices
  29. Algorithm to Speed Up eContacts List in Elliott V8
  30. Elliott Requires Volume Supporting 8dot3name
  31. Elliott Running Extremely Slow on Windows 8 with Trend Micro Anti Virus Software Installed
  32. What Causes "File Table Exceed Limit" Error?
  33. Mass Email Time Out
  34. Report Incomplete After 4 Hours: Event Stops Working After Upgrade to Elliott V8
  35. File Created in C:\ Root Directory Disappears
  36. Is There a Way to Create and Distribute Elliott Printer Configurations?
  37. What Are "COBOL Only" or "User Defined" Event Actions? Can We Use Them in Any Way?
  38. How to Purge WSORDHDR.BTR and WSORDLIN.BTR files?
  39. CPORDLS (Order Serial/Lot File) Btrieve Page Size
  40. Create PO Receiving Event to Trap Negative Qty on Hand Problem
  41. Reducing File Sizes for INITLFILE.LOG & SYACTLOG.BTR
  42. Windows 10 and Trend Micro Anti-Virus Software
  43. The Remote Certificate Is Invalid According to the Validation Procedure
  44. Customer Has Multiple Primary Contacts or No Primary Contact
  45. Btrieve Error 46 on S/M Activity Log File
  46. Multi-Currency Workarounds in Elliott
  47. Using the Export Processor to Export Data
  48. Instructions for Importing Laser Form Template
  49. I Am Unable to Post or Enter a Date for the New Year
  50. Does Elliott Work Under Virtualized Desktops Infrastructure (VDI)
  51. Btrieve Error 80 During Defer Processing
  52. Lauch CSV File -- There Was a Problem Sending the Command to the Program
  53. Feature - System Users File Integrity Check
  54. Receive Error in NWSMSCRN for Function Pf-Map-Coordinate-Space
  55. Not Able to Receive Event Emails from Certain Users
  56. Feature - Events for Add Note and Delete Note
  57. When and How to Use DDF2BTR.EXE Utility
  58. Elliott Last Printing Job Overrides Windows Default Printer on Windows 10
  59. Not Able to Change Attributes Added by Other Users
  60. Feature - New Context Menus in v8.0 Spooled Reports Manager
  61. Feature - Automatic Archiving of Spooled Reports in Elliott v8.0
  62. Feature - Enhanced Security for Attributes
  63. Feature - Deferred Processing Multiple Times Per Day
  64. Feature - Ability to Specify User ID in User Search
  65. Feature - Utility to Re-Calculate Item First Received and Last Received Date
  66. NSCTLMN1 Global Setup Time Clock Global Setup
  67. How to Set Up One-to-One Restriction of Customer and Item
  68. Recursion Error When Drill Down to Item File Inquiry
  69. Error Invoking Macro - Cannot Install Hook
  70. Feature - Record Navigation in Attribute Window
  71. Error Connecting VPN from Windows 10 to Windows 2008 Server
  72. How to Stop Users from Sending Elliott Reports through Email
  73. Does Elliott Support Windows 10?
  74. It Is Extremely Slow to Run Elliott over VPN Connection
  75. SYTIMCLK Systems Manager General Time Clock
  76. Feature - Recalculate AP Vendor YTD and Last Year Amount
  77. XCO0100 Systems Manager Design Your Own Order
  78. Feature - Restrict Recurring Event for Number of Times for a Specific Reference
  79. How Do I Limit the Companies for Users?
  80. Feature - Enforced Report Destinations
  81. I Am Unable to Create a New User in Elliott
  82. Feature - PDF Printing in Elliott V8.2
  83. Feature: PDF PostOffice in Elliott V8.2, Introduction
  84. Feature: PDF PostOffice in Elliott V8.2, Part 1
  85. Feature: PDF PostOffice in Elliott V8.2, Part 2
  86. Feature: PDF PostOffice in Elliott V8.2, Part 3
  87. Feature - Added Checkbox and Description to Attribute List and the SPS Commerce Create Attribute Register
  88. Feature - Performance Options for eContact Activity Tab
  89. Feature - Mass Change Salesman Utility
  90. Elliott Installer File-In-Use Warning During Installation
  91. Unable to Run Elliott from UNC Path
  92. V8 Program Desktop Startup Shortcuts - Internal Macro
  93. Event When Order Put On Hold at Invoice Printing
  94. Feature - Time Clock Logoff Type
  95. Feature - Added Distribution to G/L History Files
  96. Feature - Utility to Update eContact PDF PostOffice Flags
  97. Can I Use Elliott for Sales, Telemarketing and CRM Purposes?
  98. Emailing PDF with SSPI Failed After Online Charging Using Credit Card
  99. Can You Explain How Elliott Stores Serial Numbers in Its Database?
  100. Converting Elliott Internal Date to Conventional Date Format in Excel
  101. All of a Sudden, My Terminal Server's Elliott Default Changed to Someone Else's Settings
  102. WannaCry Ransomware Security Recommendation
  103. Symantec Endpoint Protection Versions 12 and 14 Cause Elliott Startup Error
  104. Notes Security - From Global Setup, Note Type to Supervisory Relationship
  105. Remote Desktop Workstation Name
  106. Which Anti-Virus Software Do You Recommend to Installing on the Elliott ERP Server?
  107. Menu Access Error - You Do Not Have Access to CP,INQ, Menu Item 01
  108. Ping Test to Isolate Inconsistent Load Error 198
  109. The Definitions of Extra Flags in System Period Control Setup
  110. How to Use Procdump.exe to Create a Memory Dump for PSQL Engine
  111. Feature - Group Location Security
  112. NSCTLMN4 Global Setup Bill of Lading 1
  113. NSCTLMN4 Global Setup Bill of Lading 2
  114. NSCTLMN4 Global Setup Bill of Lading 3
  115. NSCTLMN4 Global Setup Bill of Lading 4
  116. NSCTLMN4 Global Setup Bill of Lading 5
  117. NSCTLMN4 Global Setup Bill of Lading 6
  118. NSCTLMN4 Global Setup Bill of Lading 7
  119. NSCTLMN4 Global Setup Bill of Lading 8
  120. NSCTLMN4 Global Setup Bill of Lading 9
  121. NSCTLMN4 Global Setup Bill of Lading 10
  122. NSCTLMN4 Global Setup Bill of Lading: Index
  123. Feature - Support 12 Months History in Export Processor
  124. NSCTLMN3 Inventory Management Global Control Setup 1
  125. NSCTLMN3 Inventory Management Global Control Setup 2
  126. NSCTLMN3 Purchase Order Global Control Setup 1
  127. NSCTLMN3 Purchase Order Global Control Setup 2
  128. NSCTLMN3 Bill of Material and Production Order Global Control Setup
  129. NSCTLMN3 Distribution Modules Global Setup: Index
  130. NSCTLMN5 Global Setup Change Quote to Order 1
  131. NSCTLMN5 Global Setup Change Quote to Order 2
  132. NSCTLMN5 Global Setup Change Quote to Order 3
  133. NSCTLMN5 Global Setup Change Quote to Order 4
  134. NSCTLMN5 Global Setup Change Quote to Order 5
  135. NSCTLMN5 Global Setup Change Quote to Order 6
  136. NSCTLMN5 Global Setup Change Quote to Order: Index
  137. I Cannot See the Spooled Reports Even though I Am an Administrator Equivalent User
  138. Multi-Currency Exchange Handling in Elliott
  139. How to be a Good Elliott Citizen
  140. Salesman Security
  141. SYMENU System Manager Introduction 1
  142. SYMENU System Manager Introduction 2
  143. SYMENU System Manager Introduction 3
  144. SYMENU System Manager Introduction 4
  145. SYMENU System Manager Introduction 5
  146. SYMENU System Manager Introduction 6
  147. SYMENU System Manager Introduction 7
  148. SYMENU System Manager Introduction 8
  149. SYMENU System Manager Introduction 9
  150. SYMENU System Manager Introduction 10
  151. Feature - Audit Trail of Accumulator Clearing
  152. SYMENU System Manager Introduction 11
  153. SYMENU System Manager Introduction 12
  154. SYMENU System Manager Introduction 13
  155. SYMENU System Manager Introduction 14
  156. SYMENU System Manager Introduction 15
  157. SYMENU System Manager Introduction 16
  158. SYMENU System Manager Introduction 17
  159. SYMENU System Manager Introduction 18
  160. SYMENU System Manager Introduction 19
  161. SYMENU System Manager Introduction 20
  162. SYMENU System Manager Introduction 21
  163. SYMENU System Manager Introduction 22
  164. SYMENU System Manager Introduction 23
  165. SYMENU System Manager Introduction 24
  166. SYMENU System Manager Introduction 25
  167. SYMENU System Manager Introduction 26
  168. SYMENU System Manager Introduction 27
  169. SYMENU System Manager Introduction 28
  170. SYMENU System Manager Introduction 29
  171. SYMENU System Manager Introduction 30
  172. SYMENU System Manager Introduction 31
  173. SYMENU System Manager Introduction 32
  174. SYMENU System Manager Introduction 33
  175. SYMENU System Manager Introduction 34
  176. SYMENU System Manager Introduction 35
  177. SYMENU System Manager Introduction 36
  178. SYMENU System Manager Introduction 37
  179. SYMENU System Manager Introduction 38
  180. SYMENU System Manager Introduction 39
  181. SYMENU System Manager Introduction 40
  182. SYMENU System Manager Introduction 41
  183. SYMENU System Manager Introduction 42
  184. SYMENU System Manager Introduction 43
  185. SYMENU System Manager Introduction 44
  186. SYMENU System Manager Introduction 45
  187. SYMENU System Manager Introduction 46
  188. SYMENU System Manager Introduction 47
  189. SYMENU System Manager Introduction 48
  190. SYMENU System Manager Introduction 49
  191. SYMENU System Manager Introduction 50
  192. SYMENU System Manager Introduction 51
  193. SYMENU System Manager Introduction 52
  194. SYMENU System Manager Introduction: Index
  195. Elliott V7.0 Release Notes: What's New Since Elliott V6.7
  196. Elliott V7.1 Release Notes: What's New Since Elliott V7.0
  197. Elliott V7.2 Release Notes: What's New Since Elliott V7.1
  198. Elliott V7.3 Release Notes: What's New Since Elliott V7.2
  199. Elliott V8.1 Release Notes: What's New Since Elliott V8.0
  200. Elliott V7.4 Release Notes: What's New Since Elliott V7.3
  201. Elliott V7.5 Release Notes: What's New Since Elliott V7.4
  202. Elliott V8.0 Release Notes: What's New Since Elliott V7.5
  203. Elliott V8.2 Release Notes: What's New Since Elliott V8.1
  204. Drill Down and Receive Message You Do Not Have Access
  205. Problem Running Elliott After Upgrading Windows 10 to Fall Creator Edition
  206. MAPISendMail failed! Not supported [26]
  207. What Information Is Stored in System 12 Months Table (SY12MONS)?
  208. Elliott Telephony Integration - How to Call through My Telephone Set from eContact?
  209. Error Adding Printer Configuration After Latest Windows 10 Update
  210. Anti-Virus Causes PostOffice Emailing Problem
  211. Feature - Equal Sign Support in Export Processor
  212. Running Elliott 8.2 and Up on Windows 2003 Server
  213. How Can I Find Out About New Elliott Events Added or Changed Lately?
  214. Feature - Export Enhanced Attribute Predefined Code Value and Description
  215. Error 114 with GUIUTL32.LBR\GUIUTIL.int in Defer Processing
  216. EL800.EXE - Bad Image - MSVCRT20.dll Is Either Not Designed to Run on Windows or It Contains an Error
  217. Anti-Virus Caused Failure on Crystal Reports ODBC Access
  218. AVIRA Anti Virus Software Kills Elliott EL800 Executable

Feedback and Knowledge Base