Update Release Cycle | 5/14/07 |
|
Issue ID | Title | Files to be Released | Solution |
16378 | Korean Tax fields in Sales Summaries are labeled incorrectly | Reports.exe | The labels for these fields have been updated to Korean Ext VAT$, Korean Ext SET$ & Korean Ext ET$. |
16377 | Korean Tax values in Journal Details should not be extended values | Reports.exe | The fields were modified to calculate and display unit values rather than extended. |
16375 | EFT Receipt is incrementing the receipt number | Rpro8.exe vclie.bpl vclie50.bpl RPRO_API.bpl ms_ie_d5.bpl | Rpro now copies the Receipt# from the deposit record rather than using the next # in sequence. |
16366 | CC numbers not masked in RBS log files. | RP3Manager.exe RP3Server.exe | Changes have been made to the server logging to correct this issue. |
16363 | EFT > PC Charge > Receipt/Ticket Number already used by system | Rpro8.exe RPRO_API.bpl ms_ie_d5.bpl vclie.bpl vclie50.bpl | After the receipt has been unheld, the fields are re-read from memory and displayed. |
16336 | Scanner allows RPRO to continue when there is a quantity discrepancy | Rpro8.exe RPRO_API.bpl ms_ie_d5.bpl vclie.bpl vclie50.bpl | The form that pops up if there's not enough onhand or available to sell now doesn't accept the enter key. Instead it accepts the F2 key. The caption in the dialog box was also changed. |
16334 | Reports are not reporting the correct Ext P$ when using the option to calculate Korean Tax Values | Reports.exe | A new field has been added to Reports and is available in Sales Journals and Summaries: Korean Ext P$. This field accounts for all 3 Korean taxes. Due to the nature of the Korean Tax Tool, the user should be aware that the Korean Ext P$ field will not match the Ext P$ value on Receipts. The issue has been re-opened to add a Korean P$ field to Sales Summaries and to Item Details in Sales Journals. |
16319 | Access violation in module CLoyalty | cloyalty.bpl | A memory corruption issue has been identified and resolved. |
16290 | Customer Loyalty - points are accumulated on items that are not marked as accumulable | cloyalty.bpl | There was a discrepancy between how two different parts of the code read the select items for redemption setting. This has been resolved. |
16254 | Shift Report produces incorrect results | Reports.exe | The breakdown of hours now totals correctly. |
16200 | Scheduler not executing tasks when run for extended periods of time | Schedule.exe | Scheduler application has been modified to resolve this issue. |
16092 | User Conference Issue -- QTY references in POQTY.dat are removed from file when a PO is Archived and Purged in DVS | Rpro8.exe RPRO_API.bpl ms_ie_d5.bpl vclie.bpl vclie50.bpl RDA2.dll Auto.exe DVS.exe Reconst.exe RproDB.exe | When restoring an Archived PO that was deleted by DVS>Purge, one of the keys in POQty.ix was not properly updated. This in turn caused Mprocout.exe to see these PO's as Archived rather than Active, so they were not polled. Code was modified to update the index correctly. |
15932 | Mprocin Fails when processing with Error 216 at 001B:424F | CPROCIN.EXE CPROCOUT.EXE MPROCIN.EXE MPROCOUT.EXE RPROCIN.EXE RPROCOUT.EXE | The Proc's have been modified to resolve a memory corruption issue which was causing the RTE 216 error. |
15615 | Customer Loyalty inconsistency - reversing a return receipt will add loyalty point back to customer but reversing a sale receipt will not subtract points | cloyalty.bpl | Reversing a Sale Receipt now subtracts loyalty points earned for that sale from the customer's balance. |