You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-HR-19695-Earnings codes do not display on Earnings Tab in HR after the 16.1.1.0 update
↧
DF-FA-19731-Controls to Print Charts Are Not Active
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
↧
DF-EWS-19735-Adjusted Leave available to use before effective date
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-FA-19737-Customer Statements with Statement Balance and Invoice Balances Do Not Print
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-FA-19739-Aged Receivables Report shows wrong invoice information when invoice number is not included
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
↧
Database Schema Comparison v15200 to v16100
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
Resolving Common "Unable to Connect to SQL" type error messages
Answer:
These are a few of the causes and solutions for connectivity error messages. There may be other reasons as to why you are experiencing connectivity issues, some of which may fall outside the scope of support. Please review the material below before contacting Abila Customer Support.
Symptom 1:
Login Error Received: NpsSMOError – Login failed for user ‘NpsAdmin’ when launching MIP Fund Accounting workstation.
Resolution:
Uninstall the MIP workstation via MIP Share>Setup>Uninstall (located on your MIP server).
Then at the workstation, navigate to Add/Remove programs or Programs and Features. Locate and uninstall the Microsoft Management Objects and System CLR Types
These are files that were delivered during the previous workstation installation to facilitate SQL connectivity. *These may vary based on your version of SQL at the server*
Reinstall the workstation: Access Start>Run>type the following command substituting your MIP server name: \\servername\MIP Share\Setup
Double click on Setup.exe - proceed through the installation prompt
Once the workstation is re-installed, you should be able to log in without issue.
Symptom 2:
Login Error Received: NpsSMOError – Error:26 received when launching MIP Fund Accounting workstation.
Resolution:
This is due to the Windows Firewall settings. Please refer to KB #5156 on how to set up the Firewall Exceptions.
Once the firewall exceptions are configured, you should be able to log in without issue.
Symptom 3:
Login Error Received: NpsSMOError – Error: 28 when launching the MIP Fund Accounting workstation.
Resolution:
This is due to a faulty configuration of Named Pipes. Please refer to KB #901 on how to configure Named Pipes.
Once the Named Pipes are configured, you should be able to log in without issue.
Symptom 4:
Login Error Received: NpsSMOError – Error: 4 upon launch of MIP Fund Accounting workstation.
Resolutions:
This may be due to improper MIP Share permissions on the server. Please refer to KB #1746 for the recommended sharing permissions.
This can also ensue is if the workstation was installed from the Sub Installs folder on the server. Uninstall the MIP workstation via MIP Share>Setup>Uninstall on the server. Then reinstall via: \\yourservername\MIP Share\Setup
Double click on Setup.exe - proceed through the installation prompt
This error can also arise if the SQL service on the MIP server is stopped. At the MIP server, navigate to services.msc and verify that ‘SQLServer (instance name)’ is started and set to automatic.
If it is not started, start the service.
Once these resolutions are executed, you should be able to log in without issue.
↧
DF-EWS-19799- Certifications default incorrect dates and values
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-FA-19800-Error Logging in Using Windows Authentication
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
↧
DF-EWS-19801- “No Row Selected” error in Approve Timesheets
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-FA-19804-Unable to Edit Percent fields in Percent of Wages with Pay Cycle Cap Option for Local Tax Setup
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-HR-19805-Changing Year ID for a terminated employee generates error - SelectEmployee: Object reference not set to an instance of an object.
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
Importing User Defined Fields (UDFs) values
Answer:
User defined fields are custom fields created by the user that may apply to segment codes, vendors, customers, purchase orders, transaction documents or transaction lines.
These user-defined fields (UDFs), created through Organization > Set Up User Defined Fields, can be included as part of the import process when necessary.
When importing UDF data, the field attributes defined by the user during the creation of the UDF, will determine the editing of the definition file used in the import process. These attributes also have a bearing on the data file requirements. This is consistent with other types of data imports.
It is important to review the UDF setup information carefully before attempting the import of records containing UDF data.
The following are some FAQ’s and other points to keep in mind when preparing to import data which includes UDF values:
Question
Is importing UDF information any different than other system fields related to the same record?
Answer
No, however, the customer’s ability to add, delete, or modify UDF’s at any time may complicate new or existing import processes.
Question
How do I identify the FieldID for a newly created UDF?
Answer
To determine the FieldID, print a User Defined Field List report Reports > Lists > User Defined Fields, select the report called <User Defined Fields>. Include “Field ID/Context ID” in the report body.
Print the report to screen.
The format should appear in the Definition file exactly as it shows in the report including punctuation. For example: The context ID for the import of the “Location” for transactions to be imported reads “Transaction Lines:Transaction Lines:Location”.
Question
How do I indicate a UDF in my DEF file?
Answer
To import UDF data, the UDF must be added to the customer’s definition file.
Add the FieldID to the appropriate section of your DEF file and indicate the location of the data in the text file like you would any other field you were importing. Note: The context section of the definition file contains the [Context Type]_[Field Name] (referred to as the FieldID) of each field that will be imported into the application.
The context section of the definition file contains the [Context Type]_[Field Name] (referred to as the Field ID) of each field to be imported into the system. The Master Definition files, installed with the system, contain the Field IDs for all system defined fields. UDF Field IDs are not included in the Master Definition files. To import UDF data, the UDF Field ID must be added to your definition file. Here is a sample DEF file with the UDF in the transaction line information. The label Transaction Line comes from the UDF setup. The UDF is a Transaction Line type. The Location is the name given to the UDF. By running the UDF List Report, the Context ID column, will tell you exactly what the name should be in your DEF file.
Additional Information:
A UDF with a field type of number can have up to, but not more than 5 decimal places. The setup parameters of the field will determine the number of decimals.
Decimal indicators only work with UDFs of the field type “Currency” and not with field type “Number”.
UDFs with a number or currency field type will always default to 0.00 value if no value exists in the data file. No blanks are allowed for these field types.
UDFs cannot be independently imported.
UDFs follow the same rules as other fields you might import that have the same data type. For instance, a Date UDF will have the same DEF file rules as an Effective Date field that would be imported with a transaction. The DEF file entry would be, ‘Transaction Lines:Transaction Lines:EntryDate, columnnumber,,MM/DD/YYYY’ and your data file would need to reference a date.
If USEDISTCODE is used on the DEF file, UDFs will not import.
Header records and detail records have identifiers. For example, when you import vendors there is the header identifier (HVEND) and the detail identifier (DVEND). When you import new Vendor ID header records (with or without detail records), any Vendor ID beginning with “D” will not import because the import process thinks it is a detail record, such as (Default Vendor, A, Default Vendor). In this case, since there is no matching header, the record is not imported. In order to tell the import process there is no detail record, the first field in the record must be the applicable header identifier (HVEND, Default Vendor, A, Default Vendor).
↧
↧
DF-FA-19807-Statement of Revenue and Expenditure Not Following Statement Format when Printing
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-HR-19808-Error Inputting Bank Information with Dashes
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-FA-19690-Summary Organization Audit returns out of memory error
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
Information entered in Details Form 1095-C not flowing to the Aatrix grid
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
↧
DF-FA-19853-Error Collecting Employee Data Information in Aatrix
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-FA-19857-CDS will not allow a Zero Dollar Check
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧
DF-EWS-19858-Staff Schedules Report Displays No Data without Selecting Staff
You must be logged in and have a current support plan to view the full content of this page.
Click to login »↧