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


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Submitted
Created by Guest
Created on Oct 25, 2024

Mapping Leaf Level Node to a Higher Level Node

We have a use case wherein we intend to link a Leaf Level Node in Manta to a Higher Level Node considering the functionality of process flow among the applications from different technologies.

Manta may already have an understanding of IFPC hierarchy but here is the same for everyone who’s following this ticket for reference, to be on same page.

 IFPC (Technology) >> Repository >> Project Folders >> Workflows >> Sessions >> Mappings >> Transformations

 For Control-M, we’ve already added more detail to Job_Name to the underlying Oracle DB scanned attributes, so that it isn’t the leaf node anymore.

 For Teradata, a Macro_Name is the leaf node under a database (Schema), since the underlying Table/View is auto linked by Manta through the scan.

 Coming to the use case that we’re trying to accomplish based on the information received from respective teams for end-to-end lineage visibility leveraging, Open Manta Extensions, we intend to manually link IFPC Workflow to Control-M Job_Name (Upstream) and Teradata Macro_Name (Downstream), which is like intermediate linking between Control-M and IFPC, while it is intermediate to leaf between IFPC and Teradata.

 Kindly let us know if any further clarification is needed in this regard 

Needed By Week