AM01.1 - Current Calendar
**Form purpose
Use Current Calendar (AM01.1) to define an asset processing calendar for a
book. Calendars are processing schedules and posting dates that asset books
use to calculate depreciation, replacement costs, insurance values, and
reporting date ranges. You must define a calendar for each book and for each
company that will use that book.
**Prerequisites
Before you define a calendar, you must have a General Ledger company and a
book defined.
**Process at a Glance for Asset Management required setup tasks
1. Define at least one depreciation book.
2. (This step) Define a depreciation calendar for the current year (AM01.1).
3. Define an asset type (AM06.1)
4. Define an account group (AM05.1)
5. Define an accounting unit group (AM09.1)
For complete instructions, see the Asset management User Guide.
**Required fields
The Book, Company, Required Book, Posting Book, End Date, and Total Periods
fields are required, and you must define at least one processing and posting
period.
**Decision/Impact
- If you specify more than one period per processing period, be aware that
the number you enter in the Total Periods field must be equal to the total
number of periods entered in the Per field for the entire calendar. For
example, in a 52 (4-4-5) week calendar, the total number of periods is 52,
even though the total number of processing periods is 12. For more information
on this type of calendar, see the Asset Management User Guide.
- If you are converting from non-Lawson to LAWSON INSIGHT II Asset Management
in mid-year, type the number of periods already closed in the Period Closed
field. This is important to ensure the accuracy of depreciation calculations
for the rest of the year.
**Application integration
If your company uses system control, the period end dates must be within the
GL company period end dates defined on Company (GL10.1) so you can close your
Asset Management periods before you close the General Ledger periods.
**More help
- The Historical and Future buttons let you define historical and future
calendars. An asterisk displays next to the appropriate button when historical
or future calendars exist.
- To generate a listing of your current, historical, or future calendars,
run System Setup Listings (AM200).
Updated Files
AMCALENDAR - Used to store calendar records that asset books use for
calculating depreciation, replacement cost, and insurance
values, and for reporting date ranges.
Referenced Files
AMASSET - Edits for a change or delete in Posting Book. Not allowed if
assets exist.
AMASTBOOK -
AMBOOK - Retrieves the book description.
AMCONTROL -
GLADDRESS - Accessed by common routine; not used by this program.
GLCHART - Accessed by common routine; not used by this program.
GLSYSTEM - Accessed by common routine; not used by this program.
AM01.2 - Historical Calendar
**Form purpose
Use Historical Calendar (AM01.2) to define a previous year processing
calendar for a book. Define a historical calendar if the previous year's
calendar structure is different from the current year's calendar structure. If
you do not set up a historical calendar, Asset Management uses the same
structure as the current calendar to calculate previous year depreciation.
**Prerequisites
Before you define a calendar, you must have a General Ledger company and a
book defined. You should also have a current calendar defined for the company
and book.
**Process at a Glance for Asset Management setup
1. Define at least one depreciation book.
2. Define a depreciation calendar for the current year (AM01.1).
2a. (Optional - this step) Define an historical calendar (AM01.2)
2b. (Optional) Define a future calendar (AM01.3)
3. Define an asset type (AM06.1)
4. Define an account group (AM05.1)
5. Define an accounting unit group (AM09.1)
For complete instructions, see the Asset management User Guide.
**Required fields
The Book, Company, Required Book, Posting Book, End Date, and Total Periods
fields are required, and you must define at least one processing and posting
period. If you are defining a calendar for a short year, the Short Year and
Original Year End Date fields are also required.
**Decision/Impact
If you specify more than one period per processing period, be aware that the
number you enter in the Total Periods field must be equal to the total number
of periods entered in the Per field for the entire calendar. For example, in a
52 (4-4-5) week calendar, the total number of periods is 52, even though the
total number of processing periods is 12. For more information on this type of
calendar, see the Asset Management User Guide.
**Application integration
If your company uses system control, the period end dates must be within the
GL company period end dates defined on Company (GL10.1) so you can close your
Asset Management periods before you close the General Ledger periods.
**More help
To generate a listing of your current, historical, or future calendars, run
System Setup Listings (AM200).
Updated Files
AMCALENDAR - Used to store calendar records that asset books use for
calculating depreciation, replacement cost, and insurance
values, and for reporting date ranges.
Referenced Files
AMASSET - Edits for a change or delete in Posting Book. Not allowed if
assets exist.
AMASTBOOK -
AMBOOK - Retrieves the book description.
AMCONTROL -
GLADDRESS - Accessed by common routine; not used by this program.
GLCHART - Accessed by common routine; not used by this program.
GLSYSTEM - Accessed by common routine; not used by this program.
AM01.3 - Future Calendar
**Form purpose
Use Future Calendar (AM01.3) to define a future asset processing calendar for
a book. Define a future calendar if you expect next year's calendar structure
to be different from the current year's calendar structure. If you do not set
up a future calendar, Asset Management uses the same structure as the current
calendar to calculate depreciation projections for real or simulated assets.
**Prerequisites
Before you define a calendar, you must have a General Ledger company and a
book defined. You should also have a current calendar defined for the company
and book.
**Process at a glance for Asset Management setup
1. Define at least one depreciation book.
2. Define a depreciation calendar for the current year (AM01.1).
2a. (Optional) Define an historical calendar (AM01.2)
2b. (Optional - this step) Define a future calendar (AM01.3)
3. Define an asset type (AM06.1)
4. Define an account group (AM05.1)
5. Define an accounting unit group (AM09.1)
For complete instructions, see the Asset management User Guide.
**Required fields
The Book, Company, Required Book, Posting Book, End Date, and Total Periods
fields are required, and you must define at least one processing and posting
period. If you are defining a calendar for a short year, the Short Year and
Original Year End Date fields are also required.
**Decision/Impact
If you specify more than one period per processing period, be aware that the
number you enter in the Total Periods field must be equal to the total number
of periods entered in the Per field for the entire calendar. For example, in a
52 (4-4-5) week calendar, the total number of periods is 52, even though the
total number of processing periods is 12. For more information on this type of
calendar, see the Asset Management User Guide.
**Application integration
If your company uses system control, the period end dates must be within the
GL company period end dates defined on Company (GL10.1) so you can close your
Asset Management periods before you close the General Ledger periods.
**More help
To generate a listing of your current, historical, or future calendars, run
System Setup Listings (AM200).
Updated Files
AMCALENDAR - Used to store calendar records that asset books use for
calculating depreciation, replacement cost, and insurance
values, and for reporting date ranges.
Referenced Files
AMASSET - Edits for a change or delete in Posting Book. Not allowed if
assets exist.
AMASTBOOK -
AMBOOK - Retrieves the book description.
AMCONTROL -
GLADDRESS - Accessed by common routine; not used by this program.
GLCHART - Accessed by common routine; not used by this program.
GLSYSTEM - Accessed by common routine; not used by this program.
INVOKED Programs
IFSG
|
