IBM Sterling Ideas
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.
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).
Do not place IBM confidential, company confidential, or personal information into any field.