Note the differences between Calculation and Recalculation (covered in this article):
Calculation on the agreement level does not create any Condition Records, it is only a preview of what the results could be, based on the setup. Condition Records are generated only when Recalculate is run for the agreement.
The Recalculation (the periodic one) which is done by Calculation object generates Condition Records based on the criteria set in the approved agreement. What gets recalculated is controlled by the feeder logic and the schedule controls how often the feeder is run.
See also the Condition Records in Rampur feature description.
All (re)calculations are done using the calculation currency and calculation UOM (those are defined at the header of an agreement). That implies that you will get the results only if your PX table has the cost defined for the calculation currency/UOM.
Go to Agreements & Promotions > Calculations and open the “Agreement Recalculation” Calculation object.
Open the calculation and go through all its tabs:
Schedule – Allows you to set up how often the recalculation should run.
Agreements & Promotions – Allows you to specify a list of agreements to recalculate by using the filter. The agreement must be approved in order to be recalculated – only approved agreements are displayed in this tab..
Note: Selection by the feeder logic (see below) has priority over whatever is selected here.
ℹ️ Line Items from inactive scenarios are not recalculated.Calculation – Allows you to select the logic and the feeder logic. The feeder logic provides a list of agreements to recalculate. These agreements must fulfill these conditions:
Have “Formula based pricing” as Header Type.
Be approved.
Be valid (fit in the range of from–to dates).
If there is no existing Condition Record, a new Condition Record for the current month or quarter will be generated. If a Condition Record already exists for the current month or quarter, no new one is generated.
If the agreement has a Condition Record with an error, it is recalculated.
Once everything is set up, click the Save button.
Let the calculation run according to the schedule.
Or, if you want to trigger the calculation manually, click Run Calculation.
The recalculation will now remove Forecast outputs from the source-approved agreements. To retain any Forecast information, it needs to be saved in Condition Records.
After the (re)calculation job is finished (you can view the
CONDITION_RECORDjob status in Administration > Logs > Jobs & Tasks), the Condition Records are generated. (This is a change compared to the previous version – Condition Records used to be generated immediately after an agreement was approved.)
Review Condition Records
See also the Condition Records Reference Knowledge Base article.
Go to Master Data > Condition Records.
There can be multiple records for a single product – depending on how many parameters combinations you have defined.
What fields are especially useful to check:
Formula Definition Name – Identifies which formula definition was used.
Formula Type – Identifies which formula type was used.
Base Adder Type – Identifies which adder type was defined in the formula definition.
Valid From / Valid To – Represent the defined calculation period (month or quarter).
Output Currency/UOM – They (together with other fields) distinguish variants of the product price.
Calculated Result – Result of the calculation with just adders. Bounds are not reflected here.
Engine Result – Result of the calculation with adders and bounds.
Converted Result – Reflects the currency conversion (from base currency to output currency). It is calculated as Engine Result times whatever value is in Exchange Rate or Conversion Rate columns.
Note: The conversion is looked up on the day of recalculation, that is why the results may vary between the agreement and Condition Records (if those are generated later on and if the conversion rates changed).Formula Detail – Shows you details of the calculation.
For example: 50 + 5 (PRODUCT_EXCEPTION) with 3 MONTH Rolling Period with 1 MONTH Lag Period
That is: initial cost + defined adder of 5 (either as percentage or absolute value – as defined) where the price is looked up one month back from the current date (Lag) and averaged using values found in previous 3 months (Rolling Period; this period is moved back by Lag)Calculation Status – Either OK or Error.
Message – If it says “No cost found”, check whether your Product Extension table has cost defined for the given combination of currency and UoM or whether the validity fits the defined range.