The price on the sc_request is currently summing all the prices of the sc_req_item and not the correct total price of the whole request (see example below). The price on the sc_req_item is the unit price of the item. It is not taking into account the quantity of the item (this concept is consistent in Eureka). If you are using the price of the sc_request in reporting, the incorrect values affect report accuracy.


Item A costs $100 each.

On the sc_req_item record in Fuji:
- quantity: 5
- price: $100 (this value is consistent with Eureka - the value represents Unit Price)

On the sc_request record:
- price: $100 (this value is wrong - it should record as $500 because of the quantity specified)

Steps to Reproduce

  1. Navigate to Service Catalog > Catalog Definitions > Maintain Items.
  2. Select Access.
  3. Select Try It.
    Each item is about $133.99 currently.
  4. Add 5 quantity of the Access item into the cart.
    The Subtotal should be $699.95.
  5. Click Order Now.
    The Total for the request should be $699.95.
  6. Note the Request Number.
  7. In the Application Navigator filter, type sc_request.list.
  8. Personalize the list to show Price.
  9. Search for the Request Number record and look at the Price column. It is showing 133.99.
    Expected behavior: The price on the sc_request record should show $699.95 (this is the behavior on Eureka).
    Actual behavior: The price on the sc_request record is showing 133.99.


The business rule named Update Request Price is missing the quantity value of the individual item when it is summing up the value.

On line 10 of the script, change:

total += parseFloat(gr.price);


total += parseFloat(gr.price * gr.quantity);

Related Problem: PRB626481

Seen In

Fuji Patch 1
Fuji Patch 3

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2015-10-22 20:35:16