Information Systems:Periodic-Fiscal Year
Fiscal Year
Correct Last Day of February
In ASW Fiscal Periods
ASW does not handle leap year when setting period end dates - it simply adds one to the year. This means that February 29th is not in any fiscal period, and the system will not know how to deal with it.
At the beginning of a leap year, we must manually change February 28 to 29. Then, the year following, we must change it back.
The G/L Control File can only be changed by a user profile connected to the group profile ASW4ADM. An ASW administrator can change tables that affect the way ASW functions. They can also update an out of balance journal that would put the G/L out of balance - so use it with care!.
Sign on as user FINADMIN with our favorite password.
Key ASW and press enter.
Key GO GLSET and press enter.
Select option 2 Work with G/L control file, and correct the last day in February.
*VA/480B* G/L control file maintenance 10/15/15 09:16:16 GDMD0911
-------------------------------------------------------------------------------
Period name End date
Actual year/period.. 1609 FEBRUARY 022815
MARCH 033115
Last closed period.. 1607 APRIL 043015
First stored period. 0812 MAY 053115
JUNE 063015
JULY 073115
AUGUST 083115
SEPTEMBER 093015
OCTOBER 103115
NOVEMBER 113015
No of normal periods 12 DECEMBER 123115
Total no of periods. 13 JANUARY 013116
YEAR END 043016
In Statement Period End Dates
Go to Unity / Start uniPharm Extensions / VA Company (Production) / UWD Extensions / STM - Statements / View Statement Control Periods.
Page down to February, and make sure end date is correct; based on whether or not it is a leap year.
Make Sure Opening Balances for Analyser have been Built Correctly
Go into G/L transaction inquiry, and look at a balance sheet account, for example 130000. Look at the balance for the last period of the previous year, and the first period of current year. If they don't look right, check file ANOBOB with query.
Specify File Selections
Type choices, press Enter. Press F9 to specify an additional
file selection.
File . . . . . . . . . ANOSTK Name, F4 for list
Library . . . . . . UP1480BFVA Name, *LIBL, F4 for list
Member . . . . . . . . *FIRST Name, *FIRST, F4 for list
Format . . . . . . . . ANSTK Name, *FIRST, F4 for list
File ID . . . . . . . T01 A-Z99, *ID
File . . . . . . . . . ANOBOB Name, F4 for list
Library . . . . . . UP1480BFVA Name, *LIBL, F4 for list
Member . . . . . . . . *FIRST Name, *FIRST, F4 for list
Format . . . . . . . . ANBOB Name, *FIRST, F4 for list
File ID . . . . . . . T02 A-Z99, *ID
Specify Type of Join
Type choice, press Enter.
Type of join . . . . . . . . 1 1=Matched records
2=Matched records with primary file
3=Unmatched records with primary file
Specify How to Join Files
Type comparisons to show how file selections are related, press Enter.
Tests: EQ, NE, LE, GE, LT, GT
Field Test Field
KESUTA EQ BOSUTA
KEREFK EQ BOREFK
Select and Sequence Fields
Type sequence number (0-9999) for the names of up to 500 fields to
appear in the report, press Enter.
Seq Field Text Len Dec
10 T01.KESUTA Base or summary level code 3
20 T01.KEMK01 Mapped statistics key 01 35
30 T02.BOSUTA Base or summary level code 3
40 T02.BOYEAR Year 4 0
50 T02.BOBATP Balance type 3
60 T02.BOREFK Reference key between STK > BAL/BKX/BOB/BU 13 0
70 T02.BODAOB Debit opening balance value 21 4
80 T02.BOCAOB Credit opening balance value 21 4
Select Records
Type comparisons, press Enter. Specify OR to start each new group.
Tests: EQ, NE, LE, GE, LT, GT, RANGE, LIST, LIKE, IS, ISNOT...
AND/OR Field Test Value (Field, Number, 'Characters', or ...)
KEMK01 EQ '130000'
AND BOYEAR EQ 2015
Press F5 to run this query.
Lvl Key Lvl Year Bal Ref Debit opening Credit opening
cod 01 cod tpe key balance value balance value
008 130000 008 2015 301 150 1,230,233,934.2600 1,219,240,254.9400-
013 130000 013 2015 301 264 1,230,233,934.2600 1,219,240,254.9400-
004 130000 004 2015 301 152 1,230,233,934.2600 1,219,240,254.9400-
003 130000 003 2015 301 219 1,230,233,934.2600 1,219,240,254.9400-
005 130000 005 2015 301 128 1,230,233,934.2600 1,219,240,254.9400-
007 130000 007 2015 301 170 1,230,233,934.2600 1,219,240,254.9400-
014 130000 014 2015 301 264 1,230,233,934.2600 1,219,240,254.9400-
009 130000 009 2015 301 264 1,230,233,934.2600 1,219,240,254.9400-
002 130000 002 2015 301 264 1,230,233,934.2600 1,219,240,254.9400-
A11 130000 A11 2015 301 415 1,230,233,934.2600 1,219,240,254.9400-
A12 130000 A12 2015 303 18 1,230,233,934.2600 1,219,240,254.9400-
006 130000 006 2015 301 192 1,230,233,934.2600 1,219,240,254.9400-
001 130000 001 2015 301 264 1,230,233,934.2600 1,219,240,254.9400-
The different summary levels should all agree. (the base levels A11 and A12 will probably be correct). If they don't, sign on as FINADMIN and go to menu STCSLM. Do menu option 3 for each level that does not have the correct opening balances. You have to redo the most complex levels first; as the program will try to use a different summary level as the base. The most complex summary level will have to use the base levels to recalculate. For example, in this sequence. 1, 2, 3, 4, 5, 9, 6, 7, 8, 13, 14. See the section on ASW Analyser for an explanation of what these are.
- Note that you cannot rebuild these summaries while there is activity on the system. Current transactions will update Analyser dynamically, then be included a second time in the rebuild. It is also possible to use the same reference key number twice. I have been doing this on Saturdays.