How long can a password be in IBM TRIRIGA?
There is no maximum password length imposed by the out-of-the-box TRIRIGA system. The encrypted password length is 500 characters. However, that encrypted length translates to about 125 characters.
[Admin: To see other related posts, use the Password tag.]
We have upgraded the TRIRIGA platform to 188.8.131.52 and started upgrading the application from 10.2 to 10.5.2 in incremental order (10.3, 10.3.1, until 10.5.2). To minimize the outage and complexity during production implementation, we have been suggested to take a final OM package after completing 10.5.2 deployment, and apply all the customizations which might have been impacted with the upgrade. This final OM package will contain all the changes from 10.2 to 10.5.2.
Our question is on the patch helpers: Can we run all the patch helpers (from 10.3 to 10.5.2 in order) after importing the final OM package?
Also, we are running the Varchar-to-Numeric script before importing the application upgrade packages. This script is taking a long time (almost a day in two test environments), but when we tried in another environment, it’s running for more than 2 days and still didn’t get executed. Is it normal for this script to run like that? Or will it be an issue? There are no differences between the environments.
I wouldn’t recommend doing the upgrade in one package. Usually, it ends up being quite large and it will cause issues. The IBM-recommended way is to perform each OM, then run the patch helpers. Once you have upgraded the OOB OM packages, you can have one OM which has your custom objects…
[Admin: This post is related to the 10.25.17 post and 04.28.17 post about running “SetVarcharColsToNumeric” scripts. To see other related posts, use the Scripts tag.]
In a standard OOB installation of TRIRIGA on Windows Server 2012 R2, it gives the user group the “Execute” and “Special” permissions to the TRIRIGA folder. We are concerned from a security perspective: Why are the “Execute” and “Special” permissions needed for a standard installation? What are the minimum permissions needed for TRIRIGA to function correctly?
You can remove the user group “Execute” permission on Windows. Only the service user needs permissions to read from the install directory, and/or execute WebSphere Liberty under the TRIRIGA install directory (if so installed).
[Admin: To see other related posts, use the Permission tag or Security tag.]
Let’s review the six major enhancements for advanced lease accounting…
- 1. Period end close capabilities. TRIRIGA 10.5.3 delivers “Advanced Lease Accounting Period Close” which ensures that no additional journal entries can be posted for that closed period…
- 2. Enhanced segregation of duties. With IBM TRIRIGA 10.5.3, the roles and responsibilities of Lease Accountant and Lease Administrator have been clearly delineated…
- 3. Streamlined modification processing. A revised process for recording lease modifications has been introduced in this version which supports FASB/IFRS compliance and creates a single process flow for all modifications…
- 4. Disclosure requirements templates (quantitative metrics). IBM TRIRIGA 10.5.3 comes pre-loaded with a variety of OOB report templates which support FASB/IASB lease accounting compliance…
- 5. Journal Entry Configuration Framework. With capabilities to generate Journal Entries for ASC 840 and ASC 842 under US-GAAP, as well as for IAS 17 and IFRS 16, IBM TRIRIGA 10.5.3 practically transforms the Real Estate Manager module into a sub-ledger system for Real Estate and Asset Lease Accounting…
- 6. Simplified ERP Integration (Data Transfer Object). IBM TRIRIGA 10.5.3 simplifies the process of transferring the lease accounting data into your ERP system by creating a Data Transfer Object (DTO) file that loads into the ERP General Ledger…
[Admin: To see other related posts, use the ValuD tag.]
Are you getting ready to address the implications of the new lease accounting changes with TRIRIGA? Although FASB’s ASC 842 and IASB’s IFRS 16 will take effect in 2019, many organizations are only now beginning to realize the amount of effort required to meet the new standards…
The biggest changes to businesses will be the new Right of Use (ROU) Assets and Lease Liabilities that will hit balance sheets, as well as the intensely manual approaches and effort that many see before them. How many organizations are leveraging Integrated Workplace Management Systems (IWMS) to manage their real-estate holdings and automate these manual efforts?…
In order to help organizations comply with the new standards, and understand the implications of these changes, TRIRIGA continues to deliver a single integrated workplace management system with new enhancements in the next release. TRIRIGA supports the lifecycle of facilities management and will automate compliance activities to address changes that affect multiple teams and roles.
Here’s how TRIRIGA can help:
- CFO and CAO: The release of IBM TRIRIGA 10.5.3 will provide a sub-ledger system for real estate and asset lease accounting that is able to generate journal entries out-of-the-box for ASC 840 and ASC 842 under US-GAAP as well as for IAS 17 and IFRS 16. It also covers period closings and report generation for the most common reports required under the new standards.
- Real Estate and Fixed Asset Managers: The release of IBM TRIRIGA 10.5.3 separates the duties of a lease administrator and a lease accountant, allowing the lease administrator to enter contractual information, and then enabling the lease accountant to run classification tests, reassess lease decisions, and report on the ROU Asset and Lease Liability.
- Facility Management, and Occupants: There are also new capabilities to improve day-to-day and occupancy experience. They can leverage a new Workplace Services offering that engages everyday employees through new mobile web apps that provide access to services managed by IBM TRIRIGA, anywhere, and on any device. This includes: a new Service Request app to submit work requests, a new Reservation app to quickly create reservations for individual workspaces or multi-attendee meeting rooms, and a new location-aware Workplace Services Portal to provide a single, unified access point for launching the apps and tracking status of requests…
[Admin: To see other related posts, use the FASB tag or IFRS tag.]
For TRIRIGA 10.5.2/3.5.2 OOB, there is an issue with the “Initial Liability Carryover” (ILC) field. In both operating leases and capital leases, when a value is entered in this field, the right of use (ROU) asset in the future accounting schedules is not reduced at Day 1 (against lease liability (LL) and initial direct costs (IDC)).
- What should happen: Day 1 ROU = Day 1 LL + IDC – Initial Liability Carryover.
- What is happening now: Day 1 ROU = Day 1 LL + IDC. (No ILC is applied.)
The balance in this ILC field should get pulled into the Day 1 ROU asset balance, and it currently does not. If this field is functioning per OOB, then we need to fix it. It is critical that the transition to the new accounting standards is calculated correctly.
The initial carryover balance (ICB) was not applied to new accounting schedules. Moving forward, if leases are created on or after the look-back period, the initial carryover balance will now be applied to operating leases and finance/capital leases.
[Admin: A similar article is also posted in the IBM TRIRIGA blog. This post is related to the 07.27.16 post by ValuD about handling GAAP and IFRS in TRIRIGA leases. To see other related posts, use the ROU tag.]
It looks like TRIRIGA 184.108.40.206 changed the way that reports are generated. After we enter a user filter and refresh, a very long URI is generated, which causes an error on the IBM HTTP Server: “Request-URI Too Large”. Previously, with an OOB query, the URL might look like: /html/en/default/reportTemplate/viewPageReport.jsp. But now, the URL is excessively long.
It looks like the filter details were sent in as headers to the server. But now, they are included in the URI. This is a major change for a fix pack and I believe that it shouldn’t have been included. This pretty much limits the number of columns and user filters that a report can have. Our environment is hosted by IBM and we don’t have access to the back-end server.
We will be addressing this issue in our next fix pack.
[Admin: This post is related to the 05.26.17 post about getting an error that the URL is too large for queries with filters. To see other related posts, use the Filter tag.]