Here you can search through the pages of this Namespace, their attachments and the files uploaded to the system.
Note: the results will only display the items you have permissions to read.
List of Common Errors and Their Solutions
1-Error Instantiating Object when sending email dbxsmtp.dll is not registered on the local machine.
Register the missing DLL using the Register OCX/DLL option on the Transaction >> System Menu or run setup.exe in the workstation install folder.
Class Definition AOSMTP.MAIL is not found. dbxsmtp.dll is not registered on the local machine.
Register the missing DLL using the Register OCX/DLL option on the System/Maintain Menu.
Another option is to enable the NEWEMAILOCX option, and verify the EmailActiveX.msi [...]
[...] that they be mapped before clicking OK. Validate to TXT file: Selecting this box will create a TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered. AR Invoice Import Header File Definitions
*f1 - InvNo - AR Invoice number *f2 - CustNo - Sold [...]
[...] that they be mapped before clicking OK. Validate to XLS File: Selecting this box will create an XLS errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered. User Record Import File Definitions
Required fields are indicated with * *f1 - Contid - Contact [...]
[...] Data: This checkbox is no longer used Validate to TXT file: Selecting this box will create an TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered.
AP Check Import Header File Definitions
f1 - Invno - AP invoice number f2 - Vendno - Vendor [...]
[...] Data: This checkbox is no longer used Validate to TXT file: Selecting this box will create an TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered.
AP Invoice Import Header File Definitions
f1 - Invno - AP invoice number f2 - Vendno - Vendor [...]
[...] credit balances. The fifth range of account numbers are equity accounts. Equity accounts can include common stock at parr, paid-in additional to par, owner’s equity, retained earnings, and treasury stock. These accounts have normal credit balances. The sixth range of account numbers are operating revenues accounts. These accounts have normal credit balances. These accounts have normal credit balances. The seventh range of account numbers are cost of goods sold accounts or the direct cost of sales accounts. These accounts can include purchase of raw material, warehouse [...]
[...] that they be mapped before clicking OK. Validate to TXT file: Selecting this box will create a TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered. Sales Order Import Header File Definitions
Required fields are indicated with an * f1 - TaxTable [...]
[...] that they be mapped before clicking OK. Validate to TXT file: Selecting this box will create a TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered. Sample Import Files
Header Import File Details Import File Purchase Order Import Header File [...]
[...] transaction date for the QTYIMP transaction. Validate to TXT File: Selecting this box will create a TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and [...]
[...] that they be mapped before clicking OK. Validate to TXT file: Selecting this box will create a TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and [...]
[...] updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors. Templates generally (but not in all cases) contain 3 rows of header information. The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed. The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the field mapping process difficult. The third [...]
[...] import can create either customer pricing or vendor pricing controls. Vendor pricing groups are not as common. The Price Group Import can update either the Customer Pricing or the Vendor Pricing(Costing) screen. Adjustments to the pricing setup can easily be made by re-importing the same file after making changes. The import works to update existing records, as well as deleting unwanted records if the 'DeleteOnly' column is checked and there is an exact match. There are four types of pricing models that can be defined. The pricing model code is required for the first column [...]
[...] updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors. Templates generally (but not in all cases) contain 3 rows of header information. The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed. The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the field mapping process difficult. The third [...]
[...] updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors. Templates generally (but not in all cases) contain 3 rows of header information. The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed. The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the field mapping process difficult. The third [...]
[...] updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors. Templates generally (but not in all cases) contain 3 rows of header information. The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed. The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the field mapping process difficult. The third [...]
[...] It is possible to change machines on a work order, but the options will only be a list of machines common to all the items on the work order. Set Up The first step to setting up the Multiple Machine Production functionality is to enable the MULTIMACHINE setup option. This will enable several of the necessary fields and logic needed. Next, each potential machine will need to be added to the machine rule. Capacities can be stored for each individual machine on the rule. Then, each item will need to be set up with the potential machines that the item can be made [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] should be complete when the time entries are imported. 4. Click the Import button. If there are no errors on the file, the import will process and will display a message that says "Import Complete" when it is done. If there are problems with the file, you will receive validation errors [...]
[...] will require that they be mapped before clicking OK. Validate to XLS File: Generates an XLS file of errors that will prevent the import from completing. The file will only be created if there are errors. [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] month's backlog should reconcile to the previous month's backlog - shipments + new orders. There are some common actions listed below that will 'break' that reconciliation. This is not meant to be a complete list, just an idea of some common [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors [...]
[...] on Board. FOB determines where the person that pays for the freight changes. Origin or Factory are common ones, which means the buyer pays for the freight. Q: What is "CustPO#" used for?
A: This is a user defined text field that allows you to enter a customer's PO#. Many times a customer will tell you that you cannot place an order for them unless they give you a PO number, the PO number goes here. Q: What does "Confirm to" mean?
A: Confirm to can be an internal or external contact which allows you to list a user defined name or text. There is a setup option [...]