Product Banner Finance
Module Fixed Assets
Part I – Functional Assessment
Assessment Capability Name
Importance to Customer Low 1 2 3 4 High 5 Unique Capabilities
Ability to create or adjust otags/ptags using journal vouchers
Best Capabilities
Being able to use commodity codes, account codes and/or dollar amounts to identify fixed assets.
System Control Maintenance Form (FOASYSC) determines minimum asset capitalization amount, fixed asset feed from and dtag feed from.
Integration of Fixed Assets with the Procurement and Payables process.
Ability to append additional records to a permanent tag in order to identify a subordinate asset as an attachment or component.
Ability to automatically capitalize a ptag/otag when the amount of the transaction is over the Minimum Asset Capitalization Amount on FOASYSC.
Inadequate
(poor) P-Card
A1 There isn’t a way to get fixed asset information from the P-card module
A2 There needs to be a method to add text in the P-Card module that flows to the o-tag in the Fixed Asset Module
B1 It is time intensive to reconcile fixed assets because
transaction detail is limited – the addition of a transaction date would help
B2 There needs to be a suggested method for recording work-in-process (fabricated equipment, buildings)
B3 Accounting methods are usually wrong and/or inconsistent – need more flexibility on how accounting is done. Alice Samuel USNH will provide examples.
B4 There needs to be a Banner reconciliation process between Fixed Assets module, General Ledger and Operating Ledger
Purchase Orders/Invoices
C1 There needs to be a way to allow more than one invoice to be allocated to one otag/ptag
C2 Need ability to allocate a credit memo to more than one otag/ptag
C3 Add quantity to direct invoices so that multiple otags can be created
C4 Add options available with JV/dtag processing to PO/Invoice processing
C5 Currency exchange rates on invoices cause problems in Fixed Assets
C6 Extract issue with document accounting when there are mixed non-fixed assets and fixed assets on an invoice – if the second item on the invoice is the fixed asset the source of funds on FFAMAST will display a sequence of 2 instead of a sequence of 1 even though there is only one sequence
C7 Defect 1-3XC0C0 - Abort occurs in ffpoext.log when an invoice is cancelled and is associated with a fixed asset where a dtag transaction was performed to add freight to the fixed asset funding source.
C8 Intermittently, the FFPOEXT process results in rounding errors when splitting the invoice amounts between tags. The total dollar amount on the invoice does not agree with the total dollar amounts in Fixed Assets. Each source C-FOAPAL amount should match each invoice accounting lines C-FOAPAL. RPE 1-5H3YIM
C9 Purchase Orders and Invoices will not allow 0 dollar amounts C10 Intermittently, the amount for an asset in Fixed Assets is
C11 Credits for invoice cancels and reissues should generate new Otags instead of posting to existing tags. The extract
shouldn’t allow credits to post to a cancelled Otag.
FFAMAST/FFATRAN
D1 Need ability to duplicate information in FFAMAST and FFATRAN for multiple tags
D2 Need ability to update information in the procurement block for a manually created otag
D3 Need ability to update the source document in the funding block for a manually created otag
D4 Allow update of user status on FFAMAST without using FFATRAN
D5 When creating a manual tag and assigning the ptag number, the system allows more than one otag to be assigned to the same ptag. (Intermittent problem due to system lockup) D6 Rounding errors occur on the ffrmasa where the total does not
equal 100.00 % and only able to adjust with SQL correction.
Example will be provided by University of Illinois
D7 When a Ptag is changed on FFATRAN, there is no record of the change. Once the new Ptag record is created, the old number is no longer recognized. Need a way to track the sequence of changes.
D8 Need a way to update the last inventory date when a grant code, index code or C-FOAPAL segment is closed without reactivating the closed segment.
FFAADJF
E1 Not able to dispose of $0 capital asset on FFAADJF. E2 On FFAADJF, a $0 capped asset cannot be uncapped
E3 On FFAADJF for the sale of an asset, a % must be entered for every funding line which requires manual percentage
calculations. The % should be calculated automatically, with option to spread it if necessary.
E4 On FFAADJF, when reverse cap an otag due to a coding error on the invoice, the transaction adjusts the General Ledger but does not move the transaction to the correct non-fixed asset operating expenditure.
E5 On FFAADJF, intermittently, the JV completes but on
FFAMAST, the asset is left flagged in use. SQL is required to correct.
E6 When deleting a line after entering a multiple line entry on FFAADJF, frequently, the document ends up out of balance which requires that the entire FFAADJF entry must be deleted and reentered.
E7 Update the FFRADJA_MASA_SEQ_NUM in FFRADJA for all adjustments to fixed assets.
E8 Need a way to write-off an asset when the grant, index code or C-FOAPAL segment is closed without reactivating the closed segment.
Journal Vouchers/Dtags
F1 Need to be able to create dtags from a JV expensing a balance sheet asset account. This can be used to correct transactions where otag were created from a balance sheet asset
F2 Cannot convert a negative d-tag to a negative o-tag through the d-tag create function.
F3 When there are d-tag trigger errors during the update process, the transaction created is out of balance. The d-tag entry still shows as pending and there is an entry posted to the
FFAMAST funding source. Requires removal of the record from the source. Usually from credit entries and/or percent calculation errors.
F4 When post a d-tag to a component o-tag, the posting is
duplicated in the parent o-tag. Usually the parent o-tag is from a previous year. This causes an out-of-balance.
F5 Need ability to uncap and recap debit and credit d-tags. F6 Need ability to cap a d-tag and update a capped o-tag in the
same process.
F7 When exploding d-tag records, records cannot be removed. Unused records must be adjusted to -0-.
F8 Intermittently, when offsetting a d-tag against another d-tag, one side of the entry does not complete. The d-tag is left pending and the status is left open.
F9 When exploding d-tags, the entry should not be able to be out-of-balance. The transaction is only balanced when action is taken on the d-tag and the d-tag is closed.
G1 Due to the volume of entries created during the depreciation calculation process, consolidate the entries by FOAPAL before posting.
G2 Update the FFRADJA_MASA_SEQ_NUM in the FFRADJA for the depreciation calculation. This will tie depreciation back to the original FFRMASF and FFRMASA tables for each tag.
G3 Need better documentation on depreciation process.
G4 When period 12 is closed and run depreciation during period 14, depreciation is still posted in period 12.
G5 Need year-to-date depreciation and accumulated depreciation on FFADEPR.
G6 Need 2 methods of depreciation calculation – financial statement method and tax method.
Reports
H1 Need FFRPROP report with dates of permanent tag assignment.
H2 Need annual depreciation report with variables by fund and organization.
H3 Need General Ledger and Operating Ledger reconciliation report by chart, fund and asset type.
H4 Need monthly report of disposals by chart and organization.
H5 Need ability to convert all baseline reports to an Excel spreadsheet
Physical Inventory
I1 Need ability to upload physical inventory from hand-held scanners
I2 Need ability to download physical inventory to hand-held scanners
Attachments/Components
J1 When dispose of non-capital assets on FFAMAST, the
attachments/components have to be detached. Want to be able to automatically dispose of assets with
attachments/components.
J2 Want ability to change the ownership of an asset by changing to a different C-FOAPAL without having to detach
Part 2 – Recommendations Problems to solve
Problems Urgent Pervasive
Willing
to Pay Unique
Recommendations Solution (high level – not “how)
Part 3 – User Personas for the Recommended Solutions
TITLE EDUCATION
COMPUTING SKILLS NOVICE AVERAGE ADVANCED
POWER USER OTHER APPLICATIONS USED? BACKGROUND SITUATION
A TYPICAL DAY IN THE LIFE OF YOUR PERSONA:
A TYPICAL INTERACTION WITH THE PRODUCT:
A PERFECT DAY:
Part 4 – Participants