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
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting 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 offering manager 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 notifications 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.
Account for store time zone in RTAM node level availability calculation
RTAM would honor the property yfs.useNodeLocaleTimeForCapacityCheck, which is currently required in CoC implementations to have inventory APIs correctly calculate availability in the store's local time.
Better integration between manageOrganizationHierarchy and Calendars
The API for managing organizations allows the caller to specify the receiving, shipping and business calendars, but only by specifying the calendar key. The key is typically a system generated value which is unique to the environment and therefore...
ATP calculations due to back order demands resulting in undersell issue
When there are orders in back order status (say ship to home orders that result in back order either a shortage reported from a fulfillment center or back order during the sourcing attempt), the system considers these backorders in both shipping a...
Ability to override the Node Transfer Schedule Data and use the external Transit days by enhancing the GetDeliveryLeadtimeUE
In ScheduleOrder API/Transaction we use GetDeliveryLeadtimeUE to pass the transit days. This Transit days are taken into availability date calculation only when Node Transfer schedule is not setup in the system. If the Node Transfer Schedule data ...
Order Status changes to be audited
when order line status is changed by schedule order/release order or any other API's, status change is not getting audited in the order audit tables. Request to get this feature added
CSR must be able to process refunds against the shipped quantity
When CSR does a refund for an overage product (Meat/Deli), IBM matches Refund quantity with ORDERED qty, NOT with SHIPPED quantity. This causes discrepancy during settlement, and needs to be manually adjusted
This is a test of adding support of Total_Volume allowing more than 14 characters.
This will benefit the customer.
Provide expected collection details via invoice APIs and OMS data prior to collection going through.
When an invoice fails to be collected due to payment method no longer being valid, invoice is in status 00, and there are multiple payment methods on the order there isn't any way to tell what amount is expected to be collected per payment method ...
Support(or Equivalent) API for deprecated - getInventoryAlertsList
We have a requirement to look for the ONHAND inventory of a specific ShipNode. Since this data is already available in the yfs_inventory_alert_detail table, getInventoryAlertsList suffice our requirement (Note: getInventoryAlertsList API has ShipN...
Increase OOTB YFS_REPROCESS_ERROR.ERRORMESSAGE columns size to 5M
The current YFS_REPROCESS_ERROR.ERRORMESSAGE columns size is only 1M and is bit small to handle a big message when dealing with dataload related tasks. Under error condition, customer is seeing large number of exceptions in the log indicated -302 ...
Do not place IBM confidential, company confidential, or personal information into any field.