The AP Rebuild is not resolving data issue. After the AP rebuild is run, a series of transactions with dMatchDocIDf = 41241.520981597 are exist in tblDLTrans with an outstanding balance but not in tblAPOpenDoc
Received error “ADO Error: -2147217900 Error Code:-2147217900 is not defined in this product at this time. Go to support.microsoft.com/kb/q168354/for a possible definition of your error.” when trying to create an ARM/ARC
When using the Distribution Code icon in a Transaction Entry that has a default Distribution Code, the transaction description does not update after changing the Distribution Code that was pre-populated
There is a posted and unposted JV session with the same session id. One document in the session is posted but the other is not. The Session still appears in Transactions>Enter Journal Vouchers as an unposted session, but no edits can be made. Since the session is available to post under Activities>Manage Sessions>Post Transactions the user can select to post again. However, there is no warning that there is an issue with this session and the system ‘behaves’ as if the posting was successful, but upon review, that information does not get posted and there is no warning.
When attempting to reduce the columns to fit onto one page, the report prints correctly when displayed to screen, but removes a column when sending the report to Print Preview.
Customer is unable to find an encumbrance to liquidate when doing an accounts payable invoice. The encumbrance has already been liquidated in an existing API session. Deleting the API session should free the encumbrance up but it does not. If you delete the API session and go back and create a new API invoice and choose encumbrances that encumbrance is not on the list.
When the fiscal year is set to something other than a calendar year, the first months of the new FY are not included in the Dashboard correctly. For example if the Fiscal year changes September 1, 2010 (so FY is September 1, 2010-August 31, 2011) – September, October, November, and December for FY 2011 will not display, even though there is activity for those months. The Activity will appear once the computer date changes to 1/1/2011.
Help states that the ‘Daily Reminder of Requisitions that require Approval’ is ‘only available if the SQL/Database Mail Requisition E-mail option is selected on Administration>Organization>Set Up Modules>Electronic Requisitions and a SQL or Database Mail configuration is set up on your machine.” When accessing Security>Set Up Requisitions Users>E-mail the ‘Daily Reminder of Requisitions that Require Approval’ is correctly grayed out. However, when accessing Admin>Options>User Preferences the options is available to be checked.