What is the best practice for deleting or retiring records?


I have some records in the classifications hierarchy. These classifications are now associated to several BOs, like building equipment and tasks. I want to delete some of the values in the classification hierarchy because they are values we do not want users to use in the future. I understand that the best practice is the change the status of the record to “Retire” for audit purposes. But if we decided to just delete those records, what is the impact to any of the associated BOs? Would I have to create a workflow to remove the associations?

There are certain classification records that are used in forms, workflows, and/or queries. If you delete one of these records that are used in the application, you will in effect, lose some application functionality. Take, for example, “triClauseType” (Lease Clause), where several of these classification values are used on the Lease Clause form to determine which sections of the clause to unhide.

I suggest a best practice would be to look in the Data Modeler for the business object of the classification you want to delete records on. Select the triNameTX field and click ‘Where Used’. If nothing comes back you should be pretty safe to make changes to that classifications record list (add, delete, modify). If you see any workflows, queries, forms, etc., come back as using this field, you’ll need to analyze each to determine if your business needs them. However, I’d suggest pushing back against the business and advise that the application requires the values in question.

[Admin: To see other related posts, use the Classifications tag or Hierarchy tag.]

Continue reading

Webinar: ValuD best practices of implementing TRIRIGA for FASB


Webinar: Thursday, September 14, 2017, 12:00 PM – 1:00 PM Eastern Time

Join ValuD’s Lease Accounting expert team in their Sept 14th webcast for “Best Practices of Implementing TRIRIGA for FASB Compliance” and get prepared to meet your FASB compliance deadline. Register here.

[Admin: The same announcement is also posted in the LinkedIn group. To see other related posts, use the ValuD tag or FASB tag.]

Continue reading

What are some better practices for lease accounting payments?


I have come across numerous TRIRIGA clients who run their monthly lease accounting payment schedules as one single synchronous task in TRIRIGA. Often, this slows down the response times and overall environment performance considerably. Here are some simple steps to consider as recommended better/best practices for your lease accounting payment schedule run as follows:

  • 1. Break up processing payments into batches that fit well with your business organizations or perhaps geographical regions.
  • 2. Each of these batches can be filtered when selecting the leases to process payments for and/or before Get Payments.

Note: This will limit the number of records to process, and the load that is put on the system, and possibly, make it easier to validate payments…

[Admin: To see other related posts, use the Accounting tag or Payments tag.]

Continue reading

What are the new best practices for upgrading TRIRIGA apps?


Object Labels and Revisions

Starting in TRIRIGA 3.5.3, consider converting the TRIRIGA as-shipped objects that you renamed and modified back to the TRIRIGA objects from which they originated.

The purpose of the new conversion process is to enable the objects to use the new TRIRIGA object revisioning capabilities while preserving your object modifications. When you make future modifications to the objects, the modifications are saved in object revisions. Ultimately, the object revisioning and object labeling capabilities and tools aid in the future upgrade of your TRIRIGA applications.

Resources

[Admin: This post is related to the 09.24.15 post about the best practices for configuring and upgrading TRIRIGA applications. To see other related posts, use the Best Practices tag or Object Label tag.]

Continue reading

What is the IBM TRIRIGA Support best practice for SRs and PMRs?


IBM TRIRIGA Support works on addressing problems through a problem ticketing system where each issue is logged as an IBM Service Request (SR) or Problem Management Report (PMR).  We manage problems reported via this process.

IBM TRIRIGA Support provides a support landing page titled “IBM TRIRIGA Information and Support Resources” which has a lot of very helpful information. This page has a Support Resources Home section that provides numerous links to some great resources, including a link to our IBM Service Request system, where you can open a Service Request (SR). On the “IBM TRIRIGA Information and Support Resources” page, there are also IBM Support phone numbers.

Once an SR/PMR is opened, it can be tracked for updates via the SR tool.  You may also request an update at any time and this will notify the Support team to follow up with you as soon as possible.

For the most efficient IBM TRIRIGA support experience…

  • There should only be one problem per SR/PMR per customer environment. This helps to keep the focus on a particular issue…
  • SRs/PMRs also have the concept of “severity”. This is a ranking that is set by the customer to indicate the urgency and importance…
  • When opening your SR/PMR, try to be as complete as possible and provide as much of the critical information as possible…

[Admin: This post is related to the 07.14.15 post about collecting data to resolve PMRs, the 07.07.15 post about resolving PMRs as soon as possible, and the 04.26.17 about outlining the process for SRs, PMRs, and APARs.]

Continue reading