Recommended better practices when using Lease Accounting Payments in TRIRIGA
EdgarMe 2700002WQQ Visits (6919)
My name is Edgar Mengelberg and I have been working with the Maximo and TPAE product suite in various Support roles for over 15 years and recently started to further work with the full TRIRIGA product suite.
I have come across numerous TRIRIGA clients that run their monthly Lease Accounting Payment Schedules as 1 single synchronous taks in their TRIRIGA.
Often this results in slowing down the response times and overall environment performance considerably.
There are some simple steps you can consider that are seen as recommended best practices where it concerns 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
It is well known that this is a heavy area of processing in TRIRIGA since Lease Payment Schedules are typically well into the future and processing a payment will generate data according to the Payment Instructions, etc.
In addition, another reason why it is also encouraged to break the Lease Payments into batches is that Processing Payments typically are for Rent Roles & Monthly Expenses that are recurring payments (non-invoices).
Lastly, you can also change a long running workflow process from a synchronous to asynchronous process if you feel it is still running too long, partly because you have not followed the above recommended Leasing recommended practices, also for the Lease module and business object in IBM TRIRIGA.
For example , you then could make the triProcessPayments - Synchronous - Get Payments workflow as well as the triProcessPayments - Synchronous - Get Payments - Associate triPaymentLineItem workflow both an Asynchronous process.
If you find this short blog useful , please click the "Like" button to show your appreciation and follow me here --> Fo