Where financial data already exists in a database, the reporting requirements of a business may change and this requires changes being made to the table GL_Config - UPDATED for 7.00.157 and 7.00.175
Step-by-step guide
| Warning | ||
|---|---|---|
| ||
Advanced SQL programming skills are required to complete this task. Make sure this is tested out thoroughly on a copy of the database first. |
...
- update the fields in this record by changing the relevant PeriodStart dates e.g. PeriodStart7 = 04/12/2016, PeriodStart8 = 9/12/2016, PeriodStart9 = 13/12/2016, PeriodStart10 = 17/12/2016, PeriodStart11= 23/12/2016, PeriodStart12 = 27/12/2016 (these dates are just suggestions - discuss what works for the client)
- edit table GL_Config editing the record where YearStartingDate = 2017-07-01
- change the fields in this record by changing the relevant PeriodStart dates e.g. PeriodStart1 = 01/01/2017, PeriodStart2 = 01/02/2017
- then run usp_Jiwa_GL_Repost and usp_Jiwa_GL_UpdateParents to update the movement table with the new reporting periods
UPDATE: 7.00.157 databases need to be upgraded to 7.00.175 SR 4 with the attached patch applied. Service Release 5 for 7.00.175 will include this fix.
Please log a Service Request or call the office on 02-9409 0700 if you have any further questions
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...