Project:
| View Revisions: Issue #41071 | [ Back to Issue ] | ||
| Summary | 0041071: In some circumstances some cash ups are not exported to SAP | ||
| Revision | 2019-06-13 13:21 by aferraz | ||
| Steps To Reproduce | When processing a cashup (and any DAL object), the updated column is not updated when the object is committed, but when the object is flushed. It could happen that the cashup export process is run between the moment a cashup is flushed and the moment it is committed. In that case, this cashup won't be exported during this process because although it meets the updated condition, it hasn't been committed to the database yet. It will neither be exported during next export processes because it won't meet the updated condition anymore. |
||
| Revision | 2019-06-13 09:41 by aferraz | ||
| Steps To Reproduce | If since the flush from Cash up is done until commit is finished the execution of cash up to SAP starts, then this cash up won't be exported to SAP. The flush can take a lot of time to finish and then when the commit is done the update field is filled with the flush date and not when the commit date. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |