Agreement Header
- Ondřej Tesař
You can set up the agreement using the following inputs and settings:
Inputs
Start Date: The date when the agreement starts. It defines the validity period of the agreement. According to this period, agreements for recalculation are selected (by feeder logic in Calculations).
End Date: The date when the agreement ends.
User Group (View Details): The user group that can view the agreement details
User Group (Edit): The user group that can edit the agreement.
Input Parameters
Customer(s): Select the customer(s) involved in the agreement. You can select a single customer or multiple customers based on higher hierarchies, like customer groups.
Calculation Currency: The currency used for price calculations.
Calculation UOM: The unit of measure used for calculations.
Forecast Engine: Select the forecast engine to be used for the forward-looking projection. Options include out of the box pre-configured engines or custom engines. This is optional, do not select an engine if you do not use forecasts. Refer to the Formula Forecasts article for more details, or How to Configure a new Forecast Engine for technical details on configuring a new forecast.
Lower Bound: Define the lower bound for bounding rules.
Upper Bound: Define the upper bound for bounding rules.
Bounding Rules are mechanisms used to maintain price stability by setting thresholds that prevent frequent minor price changes from being communicated to customers. For instance, if the calculated price fluctuates minimally from one period to another (e.g., from $22.00 to $22.02), bounding rules can be applied to keep the price constant (at $22.00) within a defined threshold. This helps in avoiding unnecessary notifications or changes for small price variations, ensuring a smoother pricing experience for both the company and its customers.
Additional Calculation Output Types
Here you can define additional output types for price calculations in various currencies and units of measure.
Currency: Specify additional currencies that will be used to calculate an additional price.
UOM: Select additional units of measure for price output.
Lower Bound: Define lower bounds for the additional currency (to ignore changes in the exchange rate within these bounds).
Upper Bound: Define upper bounds for the additional currency (to ignore changes in the exchange rate within these bounds).
Calculations & Details
Calculation Outputs Result Matrix
In the Calculations tab, you can view calculation results under Calculation Outputs Result Matrix by clicking the Show link. This opens a table with view of all line item results in the active scenario. The results, grouped by currency and UoM, show the calculated prices for each product, currency, and unit of measure. You can also see the formula detail and success or error messages.
The Calculation Outputs Result Matrix on Header, Line Item and Scenario differ visually and in content:
Header: Displays only Line Items from the Active Scenario and includes Scenario Label and Line Item Label columns.
Line Item: Displays the selected line item’s data.
Scenario: Displays only Line Items present in the selected Scenario and includes the Line Item Label column.
Warning Matrix
In the Calculations tab, you can view warnings and errors that occurred during the Agreement calculation under Warning Matrix by clicking the Show link. This opens the Warning Matrix table, where various warning messages, their severity, sources, and potential solutions are captured.
See also: Warning and Error Messages
There are the following columns in the table:
Order: The sequential number assigned to each warning entry.
Severity: Indicates the seriousness of the issue.
Example:
Medium: Issues that may not be critical but should be addressed.
Fatal: Critical issues that require immediate attention.
Source: Specifies the source that generated the warning.
Example: "Scenario A - Formula Based Pricing Type."
Element Type: Identifies the type where the issue occurred.
Example: "Line Item."
Message: Provides a detailed description of the issue encountered.
Example: "No historical data found for SKUs."
Solution: Suggested actions or solutions to resolve the warning or error.
Example: "Contact support."
Technical Element Name: Indicates the specific technical element associated with the warning.
Example: "HistoricalData."
Technical Message Additional technical details or error messages related to the warning.
Example: "Error in HistoricalData.groovy at line: 65."