This portal is to open public enhancement requests for IBM Sterling products and services. 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.
email@example.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi Aaron, we looked into your comments. We would like to have a call with you to let you know the requirements in full and get your inputs. Please suggest.
Hi Vimal, can you use a custom table or a hang-off table to store the necessary fields and use a unique index on that table? In the case of a custom table for example - before creating the customer order, attempt to add an entry to the custom table with the ship to customer and customer PO number.
We tried putting unique DB index on the two fields in yfs_order_header but index creation failed. We found this documentation which says unique index creation is not allowed on standard tables. Please suggest options.
Thank you for submitting your idea. For the requirement of checking for duplicate orders, we would suggest using a unique DB index - in your case you could add one on ship to customer and customer PO number, which would prevent duplicates from being created.
If you need to be able to override this, you could include another field in the index that the user can modify on the order to to allow it to pass the unique constraint.
I hope this suggestion helps you find a workable solution to meet your requirement.