Status

DONE 

Author

Feature No.

ODP-7819 - Getting issue details... STATUS

Test Case No.

ODP-7980 - Getting issue details... STATUS

Related Features

General Description of the Feature

Pages

Lead/Opportunity Lists

In the Lead and Opportunity Grid Lists the following were added:

  • New column “Needs Order Prices Update” 

  • New filter “Needs Order Prices Update”

Lead/Opportunity pages

A new sub-header has been implemented. This sub-header will only be visible if an active order within the lead requires a price update.

To activate this functionality, the lead's make must be added to a setup key. 

Workflow

Offer TRV (Transition Required View)

When a user attempts to create a new offer, the following processes will occur:

  • The system always will check:
    1. Whether the “CheckForOfferPricesValidity“ setup key is true.
    2. If the Vehicle of Interest (VOI) is of the interest type 'Vend Configurator' or 'Stock Locator'.
  • If the above conditions are met:
    1. The system will verify if the interest contains the latest price. If the vehicle's price is valid, the process will continue as before.
    2. If the vehicle has an outdated price, the following changes will occur:
  • The system will update the interest prices.
  • Will change the “U_IDMS_InqIntAmount“ on inquiry buffer
  • Will change the serialized interest with the new price
  • The sidebar will refresh to display the new prices.
  • The new offer will include the updated price of the vehicle.
  • A new column, “ Needs Offer Prices Update“ will be added to the selection of previous offers.

      

  • If a previous offer is selected and has outdated prices, it will be marked with a banner. The “Select“ and “ Print“ buttons will be removed, and a new button, “Copy Offer with Updated Prices“ will be added. Clicking this button will copy the offer structure and open the offer sheet with the updated prices.

 

       



Accept Offer (Order Creation) TRV

At offer accept TRV, the system will do the following process:

  1. The system always will check:
    1. Whether “CheckForOfferPricesValidity“ setup key is true.
    2. If the Vehicle of Interest (VOI) is of the interest type 'Vend Configurator' or 'Stock Locator'.
  2. If the above conditions are met:
    1. The system will check if the price of the vehicle associated with the offer has been updated since the offer's creation or last update. If no updated prices exist, the system flow is the same as before.                                                                                                                                                                       
    2. A new column, “ Needs Offer Prices Update“ will be added to the selection of previous offers                                                                                                                                                                                                                                                                    
    3. If the offer's vehicle has an outdated price, the “Select“ and “ Print“ buttons will be removed, preventing the user from creating an order.                                                                                                                                                                        

Update Order Prices TRV

A new TRV, named ”ODP_UpdateOrderPrices”, has been created to update order prices. In this TRV, the order will be displayed in a view similar to an offer. The user will have the capability to perform the following actions:

  • "Update Order Price: Initially, the order opens displaying outdated prices. When the user clicks the “Update Order Prices“ button, the system will:
    1. Copy the structure of the order with the new vehicle price.
    2. The system will update the interest prices.
      1. Will change the “U_IDMS_InqIntAmount“ on inquiry buffer
      2. Will change the serialized interest with the new price
    3. The sidebar will refresh to display the new prices.
  • The user cannot perform other actions before updating the order price.
  • Add Discount: The user can add a discount to the vehicle line from a button in the total discount amount row. 
                 
  • Simulate Price: this button is turned on/off with the setup key “EnableVehicleOfferPriceSimulation“ and functions identically to the “Simulate Price“ feature in the offer sheet.
  • Print document without standard options: When it is checked, the standard option will not be printed in the document




Business Benefit

The user is now able to :

  • import/maintain prices per effective date From/To
  • consider the order creation based on the effective date of the customer price list and not the offer selected.

Configuration 

Business Cases:

Business Case

Description

12340

Enables/Disables filters and columns functionality in the Leads/Opportunities pages

Administration and Process pages: N/A


Setup Keys:

Setup Key

Description

CheckForOfferPricesValidity

Enable/disable if the system will check for offer prices validity

CheckForOrderPricesValidityEligibleMakeCodes

List of Make codes that the system will check for order prices validity

AddressesToSendItemPriceUpdateSPFailureEmail

List of email addresses to which the system will send notifications regarding synchronization errors in ITM1 from the 'update order prices' job.

Option Fields: N/A


Workflow:

Validations

  • OrderNeedsPriceUpdate

  • OrderDoesNotNeedPriceUpdate

Transition Required Views

ODP_UpdateOrderPrices

External Functions

ODP_UpdateOrderPrices: 

A new external function (ODP_UpdateOrderPrices) is created to be set with the updated order prices TRV. This external function is responsible for the following tasks:

  • Recalculate all order prices according to the old order structure, the new vehicle prices, and the user input discount
  • Recalculating related entities to the order that are affected by changes in the vehicle price.
  • Invalidates old Signed Order Documents
  • Sending the updated order to the DMS
  • Prints new order document
  • Updates lead prices

Approvals

jobs (Two new jobs have been created and must schedule to run daily at midnight, or run after the change of the price by uploading a new model tree)

~/SalesOpportunity/MarkLeadsNeedingPriceUpdates

A new job is created to update @IDMS_LEAD.“U_IDMS_NeedsOrdrPrcUpd” with 1 if the following rules are valid:

  1. The lead's make code is on the “ CheckForOrderPricesValidityEligibleMakeCodes“ setup key.
  2. The Interest Type Function of the VOI should be “VendConfigurator“ or “StockLocator“.
  3. The Lead has an Active Document Code (indicating that it is past the order step) and does not have a Vehicle Delivery Date (implying that the lead is before the vehicle delivery step).
  4. The creation or update date of the order falls within a valid period
    1. Take the model code of the vehicle line of the order
    2. Check if has entry on table “@IDMS_ITEMPRICE_EFD“
    3. Compare the creation or update date of the order with the effective from date in the '@IDMS_ITEMPRICE_EFD' table."
~/ SalesOpportunity/UpdateItemPrices

A new job is created to call a store procedure that updates item prices is created. The job does the following:

  1. Calls IDMS_UPDATEITEMPRICES_EFD SP with inputting the date that the service user logs in.
  2. Checks if there are any logs with that effective date.
    1. If they are, each of them are logged in our mongologs and a check is made to setup key “AddressesToSendItemPriceUpdateSPFailureEmail“. If there are any addresses, an email is sent to each of them using the ad-hoc email template ( setup key EmailAdHocNotificationTempl) with Subject "Update Item Prices SP failed!" and content: "Errors occurred during the Item Price update of the Effective Date: {effectiveDate} for the environment: {SiteRootURL}".

Additional Information

Feature Availability

This feature is mainly developed for version 3.14.0 but it is also patched in:

  • 3.12.9

The following were added to QA_RetailSales_v.02 - DocuSign - Configurators flow for testing purposes:

1.Validation "OrderNeedsPriceUpdate" was added to:
   1.Sign Order
   2.Delivery Appointment
   3.Order

2.Validation OrderDoesNotNeedPriceUpdate was added to: 
   Update Order Prices

3.Update Order Prices step was added to 'Delivery appointment call' state


4.External function “Update Order Prices” (ODP_UpdateOrderPrices) was added to Delivery appointment


Write a comment…