Skip to Main Content
IBM Sterling


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).


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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Status Not under consideration
Created by Guest
Created on Oct 29, 2018

Return Order Invoice should not automatically reduce the LineCharge(DISCOUNT). If it is more than LineTotalWithoutTax but equals to LineTotalWithTax

Scenario: A Sales order is Created-Scheduled-Releases-Shipped-Invoiced(Either Order or Shipment Invoicing), Item theft reported, Customer care gave entire line total as a discount. Later item was identified at a Carrier location, and processed as a return for the same item.  

#1: Say Order has 2 lines,
* HeaderCharge&Tax for Shipping is USD5 and USD0.5 respectively.
* Line #1 1QTY, UnitPrice is USD100, and Tax(Price) is USD10.
* Line #2 1QTY, UnitPrice is USD50, and Tax(Price) is USD5.
* The invoiced total is USD170.50.
#2: Customer calls Customer Care, and complains that the Line #2 item was never received in the package:
At this stage, CSR doesn't know the state of the Item where it is.
So he will appease customer by giving LineCharge(DISCOUNT of USD55: ChargeCategory_ADJUSTMENT, ChargeName THEFT) for the entire line Total(LineTotalWithTax of USD55). This results in an adjustment invoice to refund Line#2 total USD55.

#3: CSR asks for a probe at Warehouse then at Carrier.
#4) Say an item is identified at Carrier location, Later when received at the warehouse this item will be processed as a Return against the actual Sales Order's Line#2.
* Return Order was created with the following values:
Line#2 1QTY, UnitPrice is USD50, Tax(Price) is USD5, and LineCharge(THEFT DISCOUNT) is USD55.
a) Return Order and Line total is ZERO dollars.
b) Return is Received and Invoiced.
On Return Order Invoicing,
Expected: It should generate an invoice with order/line total as ZERO dollars by including all the prices/Taxes/Charges.
Actual: Instead OOTB it is reducing the existing LineCharge(THEFT DISCOUNT) from USD55 to USD50(which is equal to LineTotalWithoutTax). As a result, the invoice is being generated to refund the LineTax of USD5.
This is what we understand from L3, "OOTB there is a validation internally to avoid Negative invoice totals, the product is picking up the LineCharge(Discount) which is GREATER than LineTotalWithoutTax and reducing the discount to make it equal to <LineTotalWithoutTax>. As a result, the invoice total is being USD5 in the above scenario, and we end up giving an excess refund."

Required Enhancement: We need to bypass the negative invoice total validation and consider Tax as well for Discounting. This is needed in 9.5 and future releases.

Note:- We understand OOTB by default there is no validation at the time of API<changeOrder> call while applying LineCharge(Discount), on how much MAX we can give a discount on a given line (or) order.
In that case, clients are forced to validate the max-limit of how much to refund for that line or order as part of their Customer Care/Store UI implementations.
On Order Invoicing Instead of automatically pick LineCharge(Discount which is more than the LinePriceWithoutTax) and reduce it to the Orderline's LineTotalWithoutTax. We should never update automatically to just go ahead with invoice creation, and to avoid Negative invoice totals.

What is your industry? Non-Industry Specific
How will this idea be used?

This will allow orders placed from various countries flow in with or without splitting tax from the unit price. A lot of countries in Europe tax will be part of the unit price. And in the USA we have the unit price and tax separated.

In either of the scenarios, when the customer calls and says (one or more) items he never received in the shipment. Customer care associate would need to give a full refund on that(those) line(s) as appeasement(this includes UnitPrice+Tax). And CCare agent would rise a THEFT inquiry. Later when the item is found somewhere at the warehouse or with the carrier, then the item can be processed as a return for the corresponding sales order line(We will copy all the prices, taxes and positive/negative charges), and the invoice(total will become ZERO) including the provided line prices (also tax in case of USA, etc. orders) and also the THEFT Discount (Line Charge).

  • Guest
    Sep 16, 2019

    FYR, Product case: TS001595797 in which we got a pre-release to bypass this behavior. 

    Please let us know a date for the fix. 

  • Guest
    Sep 16, 2019

    Do we have any update on this?

    We are waiting for a permanent fix in the product. 

    It is already completing 1 year of waiting on this since we got a fix.

  • Guest
    Apr 19, 2019

    We have got a pre-release for this as part of the PMRs. And we are waiting for a permanent fix in the product.