Price Guidance Override History

When price guidance is used, all price overrides are stored in the price override history. This document describes the process for price override history, how and when the override history is created and updated

Price override details are stored if alternative '2-Yes, and store details' in parameter 'Price Guidance' on the customer order type 'CO Type. Open' (OIS010/I) is selected.

Price override history table

The price override history is stored in table OIPROI. There is no program where this can be viewed. An information browser category can be created in 'Information Browser Category. Open' (CMS010). It can be used for Ad Hoc reporting, viewing in a list (including search and filtering capabilities), or for creating an API transaction in CMS100MI.

Price override details table

When alternative '2-Yes, and store details' in parameter 'Price Guidance' on the customer order type (OIS010/I) is selected, price override details are stored in table OIPROD. OIPROD stores all price levels of the used price guidance model available upon price override in (OIS337). For every record stored in OIPROI, a record in OIPROD is stored.

There is no program where this can be viewed. An information browser category can be created in 'Information Browser Category. Open' (CMS010). It can be used for Ad Hoc reporting, viewing in a list (including search and filtering capabilities), or for creating an API transaction in MCS100MI.

Update the price

F15='Update' in 'Price Guidance. Display' (OIS337) writes a record in OIPROI and updates these values:

  • 'Original net price' (ORNP)
  • 'Override price' (OVRP)
  • 'Override date' (ORDA)
  • 'Override user' (OVRU)

If the order line is blocked for authorization and an authorizer or authorizer user class can be found through the object control table for price authorization, then the 'Authorizer' (AUUI) and 'Auth user class' (AUUC) are updated.

If a record exists in OIPROI and OIPROD, and the same user uses F15 again, then the existing record is deleted and a new record is written. If another user updates the price with F15, then the existing record is flagged as cancelled (CCEL=1) and a new record is written.

Recalculation of the price (for example F14 in (OIS337) or (OIS101)) removes the record in OIPROI and OIPROD.

Approve the price

F16='Approve price' in (OIS337) updates these fields on the existing record in OIPROI:

  • 'Authorized price' (AUP2)
  • 'Authorizer' (AUUS)
  • 'Authorized date' (AUDA)

Special scenario – Immediate price approval:

The salesperson asks the manager to approve the price immediately, without first updating the CO line and stop it. The manager uses F19='Local authorization' to see the manager's price limits. The manager uses F15='Update' to set the price. The price is stored both as 'Override price' and 'Authorized price'. The actual user (the salesperson) is registered as the 'Override user' (OVRU) and the local authorization user (the manager) is registered as the 'Authorizer' (AUUS). The other 'Authorized' fields (AUP2, AUUS, and AUDA) are also updated.

However, if the local authorization user (the manager) is not allowed to set the price, the local authorization user is registered as the 'Override user' (OVRU) and the other fields (AUP2, AUUS, and AUDA) are left blank since the price is not Approved. The 'Authorizer' (AUUI) and 'Auth user class' (AUUC) are updated based on the set up for the local authorization user (the manager), to be able to send the application message to the correct person(s).

Special scenario – Not authorized to approve the price:

If the price is below what you are authorized to approve when F16='Approve price' is used, you get a message that you will need authorization to sell at this price. If the message is confirmed, the existing record is flagged as cancelled (CCEL=1) and a new record is written. You are registered as the 'Override user' (OVRU) and the 'Authorizer' (AUUI) and 'Auth user class' (AUUC) are updated as if you used F15='Update' to update the price.

When the price is approved, price guidance levels available from the used price guidance model during price override in (OIS337) are stored in OIPROD if alternative '2-Yes, and store details' in parameter 'Price Guidance' on the customer order type (OIS010/I) is selected.

Audit

If the Audit process is triggered, these fields are updated in OIPROI:

  • 'Audit triggered date' (Audit date - ATDT)
  • 'Audit reason 1' (ARS1 - Ref RSCO)
  • 'Audit reason 2' (ARS2 - Ref RSCO)

Copy customer order lines

When sales prices in a customer order are copied to a customer order with 'Price guidance' selected, existing OIPROI and OIPROD records are copied, but the following are set in OIPROI: 'Override user' is set to 'COPY ORDER' and the 'Auth user class' and 'Authorizer' are blanked out to prevent messages about authorization to be sent.

When the price is confirmed, existing transactions are flagged as cancelled and a new transaction is created.

Copy a quotation

When sales prices in a quotation are copied to a customer order with 'Price guidance' selected some conditions apply for the override history:

  • If the price on the quotation was changed through price guidance, the price override history (OIPROI) and the price override details (OIPROD) are copied to the new customer order (or new quotation if you are copying to another quotation).
  • If the quotation order line is blocked for price authorization, the new order line is also blocked. When an order line is blocked for price authorization, existing OIPROI and OIPROD records are copied, but the following are set in OIPROI: the 'Override user' is set to 'COPY QUOTE' and the 'Auth user class' and 'Authorizer' are blanked out to prevent messages about authorization to be sent.

When the price is confirmed, existing transactions are flagged as cancelled and a new transaction is created.

Related topics