This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Thank you for submitting your request. Although this is something that I can see value in doing, this is not a priority for our roadmap for the next several releases.
In response to the comment below, in most cases for us, the requestor is Maximo via auto-reorder, so we use an alternate process to address part availability/obsolescence issues. This RFE is a request to provide an option to turn off the default Maximo behavior at the organization level when the default behavior is not compatible with functional procedures.
The problem I can see here is:. In the sample scenario, the requestor requested two items. One was deleted from the PO due to lack of availability, so the requestor will not be getting that second item. The requestor needs to be the one to resolve that issue since presumably he/she still needs that item. I would solve this by using an escalation to notify the person in the PR.Requestedby field that the PR has changed status back to APPR. It is then up to the requestor to un-approve the PR and delete the line, and then add a substitute part to order. The revised PR, once re-approved, can then go to the buyer to add the new line to the PO.
The problem I can see here is:. In the sample scenario, the requestor requested two items. One was deleted from the PO due to lack of availability, so the requestor will not be getting that second item. The requestor needs to be the one to resolve that issue since presumably he/she still needs that item. I would solve this by using an escalation to notify the person in the PR.Requestedby field that the PR has changed status back to APPR. It is then up to the requestor to un-approve the PR and delete the line, and then add a substitute part to order. The revised PR, once re-approved, can then go to the buyer to add the new line to the PO.