Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Functionality already exists
Workspace Planning Analytics
Created by Guest
Created on Oct 24, 2017

Financial Reporting Sign Formatting

Financial data which is sourced from a General Ledger typically requires the reversal of the accounting sign for the majority of management and statutory reporting. For example, Income accounts are held as negative values in the Ledger however they are reported as positive.
Changing the accounting sign for management reporting is usually achieved by using an “accounting sign” element attribute (e.g. 1 or -1) for the “General Ledger Account” element. Then a “Reporting” element is added to the “Version” dimension and a rule calculates the “Reporting” version with the management reporting sign rather than the “accounting” sign.
E.g. [Reporting Version] = [General Ledger] * ATTRN(‘Account', !Account , ‘Account Sign');
While this works it would be nice feature if TM1 had a standard “Sign Format” and PAW had the functionality to apply the accounting sign or not.
The alternative is to use the Format element to achieve the same outcome. However, this approach removes the flexibility of being able to see the data with either accounting or natural sign.