2025 Q3: Foundation & Pricing Backlog

25Q3-01 Sales Area Contact Details in Printout

High Done!

As a sales manager

I want to maintain address, phone, and email by Sales Area

So that these contact details can be included in the PDF printout.

Acceptance Criteria

Sales Area master data includes address, phone, and email fields.
These details are available for use in the quote printout.
PDF printout displays Sales Area contact details in a dedicated section.

Technical Notes

Extend Sales Area entity.
Update printout template to include new fields.

---

25Q3-02 Quote Owner (Sales Rep) Assignment

High Done!

As a sales manager

I want each quote to have an assigned owner (Sales Rep)

So that accountability and contact information are clear.

Acceptance Criteria

Each quote record has a mandatory Sales Rep field.
Sales Rep can be selected from a list of users.
Sales Rep is shown in the quote details and printout.

Technical Notes

Add Sales Rep field to quote entity.
Integrate with user management.

---

25Q3-03 User (Sales Rep) Contact Details in Printout

High Done!

As a sales rep

I want my address, phone, and email to be included in the quote printout

So that customers can easily contact me.

Acceptance Criteria

User profile includes address, phone, and email.
Printout displays quote owner's contact details.

Technical Notes

Extend user entity/profile.
Update printout template.

---

25Q3-04 Pre-Products General Text Section in Printout

Medium Done !

As a sales manager

I want to define general text per Sales Area to appear before the products section in the printout

So that we can provide context or instructions to customers.

Acceptance Criteria

Sales Area has a field for predefined, translatable general text.
Printout displays this text before the products section.

Technical Notes

Support i18n for text.
Update printout template.

---

25Q3-05 Post-Products Extra Information Section in Printout

Medium Done !

As a sales manager

I want to define extra information text per Sales Area to appear after the products section in the printout

So that we can provide additional details to customers.

Acceptance Criteria

Sales Area has a field for predefined, translatable extra information text.
Printout displays this text after the products section.

Technical Notes

Support i18n for text.
Update printout template.

---

25Q3-06 Pricing Adjustments Section in Printout

High Done !

As a sales rep

I want pricing adjustments (e.g., product options, color, size) to be shown in the printout after the products section

So that customers see all price variations clearly.

Acceptance Criteria

Pricing adjustments are listed in the printout after the products section.
Each adjustment shows description and price impact.

Technical Notes

Use existing PricingAdjustments data from quote.
Update printout template.

---

25Q3-07 Post-Pricing Adjustments Extra Information Section in Printout

Low Done !

As a sales manager

I want to define extra information text per Sales Area to appear after the pricing adjustments section in the printout

So that we can provide further details to customers.

Acceptance Criteria

Sales Area has a field for predefined, translatable extra information text (post-pricing adjustments).
Printout displays this text after the pricing adjustments section.

Technical Notes

Support i18n for text.
Update printout template.

---

25Q3-09 Add plant at Header of the Quote

Medium Done!

As a sales manager

I want to display the plant information in the header of the quote printout

So that customers can see the relevant plant details at a glance.

Acceptance Criteria

Plant information is included in the header section of the quote printout.
Plant details are fetched from the Plant entity, and the SalesOrgDistributionChannelPlant association.

Technical Notes

Update printout template to include plant information in the header.
Ensure plant data is available in the QuoteItem context.

---

25Q3-10 Add plant at item of the Quote

Medium Done!

As a sales manager

I want to display the plant information in the item section of the quote printout

So that customers can see the relevant plant details at a glance.

Acceptance Criteria

Plant information is included in the item section of the quote printout.
Plant details are fetched from the Plant entity, and the SalesOrgDistributionChannelPlant association.

Technical Notes

Update printout template to include plant information in the item section.
Ensure plant data is available in the QuoteItem context.

---

25Q3-11 Add geocoordinates and address and contact details to plant master data

Medium Done!

As a sales manager

I want to have accurate plant data in the SEP tool

So that Important things like maps and automatic determination of plants are possible

Acceptance Criteria

Geocoordinates (latitude, longitude) are included in the plant master data.
Address details (street, city, zip code) are included in the plant master data.
Contact details (phone number, email) are included in the plant master data.

---

25Q3-12 Setup the Mockup servers for integration with S/4

Critical Done!

As a sales rep

I want to ensure my data is accurate in the relevant systems

So that subsequent teams can rest assured they have the most recent negotiation Sales data

Acceptance Criteria

We can simulate integration with a real SAP S/4 HANA system for development
Prepare the app for integration with a real SAP S/4 HANA environment

---

25Q3-13 Add Synchronize with Backend Button

High Done!

As a sales rep

I want a button in the Quote Tool to synchronize with the backend

So that I can ensure all relevant data is up-to-date and accurate.

Acceptance Criteria

A "Synchronize with Backend" button is added to the Quote Tool UI.
Clicking the button triggers the synchronization process with the backend.

Technical Notes

Implement the backend verification and creation logic as described in the user story.
Ensure proper error handling and user feedback during the synchronization process.
What that button will do is:
Verify the sold-to (customer) / ship-to (location) exist in the backend.
If not, create them and establish the relationship.
Create the Contract in SAP to get the prices of the items according to SAP S/4.
Set those prices from the response of the contract API in the quote tool.
Create condition records in S/4 based on the content of the items in the Discounts and Adjustments section.
Reprice via API to get the new net value.

---

25Q3-14 Make the test data persist in the sqlite using the csv only if the sql doesn exits

High Rejected - too much time, small value.

As a developer

I want to store the data properly

So that I see a more realistic system behavior when testing

Acceptance Criteria

Test data is persisted in the SQLite database using the CSV files only if the corresponding SQL tables do not exist.
Proper error handling is implemented to manage any issues during the data import process.

---

25Q3-15 Add AI Pricing Synchronization with 'AI Pricing' Button

High Done

As a sales rep

I want a button in the Quote Tool to synchronize with the AI Pricing backend

So that I can ensure all relevant data is up-to-date and accurate.

Acceptance Criteria

A "Synchronize with AI Pricing" button is added to the Quote Tool UI.
Clicking the button triggers the synchronization process with the AI Pricing backend.

Technical Notes

Implement the backend verification and creation logic as described in the user story.
Ensure proper error handling and user feedback during the synchronization process.
What that button will do is:
Prepare the payload for AI pricing inference
Call the AI Pricing backend API with the prepared payload
Update the quote tool Lower and Upper Price Values with the response from the AI Pricing API

25Q3-15 Add Pricing Synchronization with 'Sync with Backend' Button

High Done!

As a sales rep

I want a button in the Quote Tool to synchronize with the backend

So that I can ensure all relevant data is up-to-date and accurate.

Acceptance Criteria

A "Synchronize with Backend" button is added to the Quote Tool UI.
Clicking the button triggers the synchronization process with the backend.

Technical Notes

Implement the backend verification and creation logic as described in the user story.
Ensure proper error handling and user feedback during the synchronization process.
What that button will do is:
Verify the sold-to (customer) / ship-to (location) exist in the backend.
If not, create them and establish the relationship.
Create the Contract in SAP to get the prices of the items according to SAP S/4.
Set those prices from the response of the contract API in the quote tool.
Create condition records in S/4 based on the content of the items in the Discounts and Adjustments section.
Reprice via API to get the new net value.

---

25Q3-16 Multilanguage Support for Quote Tool

Medium Done!

As a sales rep

I want the quote tool to work in my own language

So that I can easily understand and use the tool without having to know english

Acceptance Criteria

The quote tool UI is available in multiple languages, including Polish and Portuguese.
Language is set automatically based on the language preferences of the user.
All text in the quote tool is translated according to the selected language.

Technical Notes

Implement i18n support in the quote tool.

---

25Q3-17 Add Address data and geocoordinates management for Plants

Medium Done!

As a Sales Pricing Administrator

I want to manage address data and geocoordinates for plants

So that I can accurately represent their locations.

Acceptance Criteria

Geocoordinates (latitude and longitude) fields are added to the plant data model.
Users can input and edit geocoordinates for each plant.
Address fields (street, city, country, state, zip code) are added to the plant data model.
Users can input and edit address information for each plant.
Geocoordinates and address data are stored in the database and can be retrieved for reporting and mapping purposes.
The feature is documented in readme.md or similar file documentation.

Technical Notes

Update the database schema to include geocoordinates and address fields for plants.
Implement frontend UI components (Plant Fiori app) for geocoordinates and address input.
Ensure proper validation and error handling for geocoordinates and address data.

Implementation (Aug 2025):

Added fields Street, City, State, PostalCode, Country, Latitude, Longitude to `Plant` entity in `db/schema.cds` (Latitude/Longitude as Decimal(9,6)).
Extended `plants/annotations.cds` with new LineItem columns (City, Country) and Address facet grouping address & geo fields.
Added i18n keys Latitude, Longitude, Street.
Persisted automatically via existing draft-enabled `SalesAdminService.Plants` projection.
Next (optional): add value helps & coordinate validation (range enforcement) via custom handler.

---

25Q3-18 Add maps for customers and plants supporting geocoding and reverse geocoding

Medium Done!

As a Sales Representative

I want to visualize customer and plant locations on a map

So that I can better understand their geographical distribution, as well as get accurate prefilled addresses.

Acceptance Criteria

A map interface is integrated into the quote tool for displaying customer and plant locations.
Users can view geocoded locations on the map.
Reverse geocoding is supported to display addresses for selected map points.

Technical Notes

Utilize a mapping library (e.g., Leaflet, Google Maps) for the map interface.
Implement geocoding and reverse geocoding APIs to convert between addresses and coordinates.
Ensure proper handling of map interactions (e.g., zooming, panning, selecting locations).
The mapping library should be easy to switch out per Sales Area and Use, for example, for Sales Area 1000_00_01, use view location, use OpenStreetMap, for edit use Google Maps, for reverse geocoding use Bing Maps, etc.. We need a configuration table mapping Sales Area and Use to the corresponding mapping library and API.
The mapping configuration should be easy to maintain, potentially via a user friendly Fiori app.

Implementation (Aug 2025):

Added `MappingConfiguration` entity to schema for configurable mapping providers per Sales Area and use case.
Created Mapping Configurations Fiori app for managing map provider settings.
Built reusable map component library with provider factory pattern (`app/common/maps/`).
Implemented OpenStreetMap provider with Leaflet and Nominatim geocoding (default).
Created placeholder providers for Google Maps, Bing Maps, Mapbox, and ESRI ArcGIS (ready for implementation).
Integrated map view into Plants app with location editing and geocoding capabilities.
Added seed data for default OpenStreetMap configuration.
Future: Complete Google/Bing/Mapbox/ESRI providers, add Customers app integration, create multi-location overview maps.

Post-Implementation Enhancements (Aug 2025 incremental):

Draft-aware edit gating using `IsActiveEntity` (map & geocode UI only in draft/edit mode; read-only otherwise).
Address confirmation dialog redesigned (multi-line formatting, coordinates line, structured components) for better readability.
Coordinate rounding & validation: all lat/long updates normalized to 6 decimals client-side to satisfy Decimal(9,6)/(10,6) constraints and reduce validation noise.
Reverse geocode debounce (400ms) to limit network chatter during drag.
OData V4 safe property updates: internal control now uses `context.setProperty` when available (fallback to model.setProperty for V2/JSON) preventing runtime errors.
Programmatic visibility replaced fragile binding expressions to remove `Invalid resource path` console warnings.
Added internal provider configuration fallback when Sales Area not supplied.
Dialog now supports House Number + Street concatenation and optional postal/city/state/country segmentation from Nominatim components.

---

25Q3-21 Automatic Quote header plant determination based on distance between Ship-to and Plants

Medium Done

As a Sales representative

I want the main supply plant to be determined automatically in the Quote tool based on distance to the ship-to location

So that I can save time and avoid errors when selecting the plant

Acceptance Criteria

The system automatically calculates the distance between the ship-to location and available plants
The main supply plant is selected based on configurable parameters, such as the shortest distance or the travel time, to the ship-to location
We need to use our UseCase mapping configuration too, to ensure the best mapping solution can be chosen for edit, while a cost-effective can be used for View. Also, as different mapping solutions have better accuracy in different countries, this configurations of mapping solutions should be per Sales Area to allow flexibility.
Probably is a good idea to implement a script to trigger via cronjob to run determination of radial and driving distances, as well as driving time, storing those in a dedicated database table for easy access and reporting. Also we would need a configuration at the Sales Area level to manage the settings of frequency of update of distances and travel times. This will help to avoid calling the APIs frequently, and will help to speed up the solution.
We should document the solution in our Readme.MD files
We should implement automated regression testing following the framework we already have.

---

25Q3-22 We need regression testing

Medium Done!

As a QA Engineer

I want to have regression tests for the whole workspace. All services and handlers

So that I can ensure that existing functionality is not broken by the new changes

Acceptance Criteria

Automated tests are created for the product functionalities
Tests cover all relevant scenarios, including edge cases
Tests are ready to be integrated into the CI/CD pipeline

---

25Q3-24 Digital Assistant

Medium Done

As a sales representative

I want to have interactive digital assistance which can answer by performing required action on information based on my query

So that I can get quick and accurate responses to my inquiries without having to navigate through multiple systems.

Scalability Issues: As the business grows, the demand for solution products has increased, making it difficult to manage quotations efficiently at scale.

Time-Consuming Quote Tracking: Tracking and managing all customer quotations is manual and time-intensive, leading to delays and operational inefficiencies.

Fragmented User Interfaces: Users must navigate multiple systems and interfaces, causing delays in decision-making and reduced responsiveness to customer needs.

Important to have strong error handling and validation to ensure data integrity and provide meaningful feedback to users.
We can have a configuration table to guide the system in different actions it can perform in each one of the error scenarios.
also strong search strategies to quickly find relevant quotes and customer information based on different content, like quotes that have X product, or search of quotes which are valid from X dates, or form certain Sold-to, from certain Owner, etc... That will need fuzzy search, which allows for more flexible matching and can improve the user experience by providing relevant results even when the search terms are not exact. Something like Solr, but nodejs based?
Confirmation to the user of the action the LLM understood before executing, like confirm that Sales Area is X Document Type is Y, Customer is Z, before executing...

---

Acceptance Criteria

25Q3-28 Bug in results of Customer search via digital Assistant

Medium Done

As a sales representative

I want to ensure the Digital Assistant returns accurate results for customer searches

So that I can rely on it for quick and effective customer interactions.

Acceptance Criteria

The Digital Assistant must return the correct customer information based on the search query.
The search results should include all relevant customer details, such as name, contact information, and quote history.
The system should handle ambiguous queries gracefully, prompting the user for clarification if needed.

Error

The Digital Assistant returned incorrect results for a customer search query.

[assistant:intent:llm] LLM result: {

intent: 'search',

entity: 'customer',

query: 'Uva',

confidence: 0.95

}

[assistant:search:customer] Query: "Uva", Session: ffc0bab3-9dba-4837-b538-f32e693ec6ee

[assistant:search:customer] Found 3 customers

[assistant:stream:completion] Full response: "I found 3 customers matching Uva:

uva_01 Uva Solutions Sp z o.o: Located in Zakrzewo
uva_02 Uva Solutions SAS: Located in Heidelberg
uva_03 Uva Solutions GmbH: Located in Heidelberg

All three customers share the same ID: b3c1f4ed-811c-439b-a51c-94ca47694425. Do you want to view details for a specific customer?"

---

25Q3-29 Make version of Virtual Assistant that can popup anywhere in the apps, starting with the quote app

Medium Done

Acceptance Criteria

The Digital Assistant must return the correct customer information based on the search query and the context in which the user is, in this case, a quote list report or a specific quote.
The system should handle ambiguous queries gracefully, prompting the user for clarification if needed.
Leverage the existing Digital Assistant capabilities to provide context-aware responses.
Use the current Digital AAssistant setup to ensure a seamless user experience.

---

25Q3-30 Improve the Assitant UI/UX

Medium Done

As a sales representative

I want to have an improved UI/UX for the Digital Assistant

So that I can interact with it more efficiently and effectively.

Acceptance Criteria

The UI should be intuitive and easy to navigate.
Responses from the assistant should be displayed in a clear and organized manner.
The assistant should be accessible from various points within the application.
User feedback should be incorporated into the design process.

---

25Q3-31 Make the AI LLM assistant choice configurable per Sales Area and Use Case

Medium Done

As a sales representative

I want to have very accurate and cost effective LLM AI assistant

So that I can have the best possible experience with the assistant, while keeping costs under control

Acceptance Criteria

The LLM AI assistant choice should be configurable per Sales Area and Use Case (e.g., Edit, View, etc.)
The configuration should allow for different LLM providers to be used based on the Sales Area and Use Case.
The system should automatically select the appropriate LLM provider based on the configuration when the assistant is invoked.

Technical Notes

Implement a configuration table to map Sales Areas and Use Cases to specific LLM providers.
Update the assistant invocation logic to reference the configuration table and select the appropriate LLM provider.
Additionally to ollama (offline option), we can have OpenAI, Azure OpenAI, Anthropic, Cohere, with API keys stored in the destination environment variables.
Each of those vendors also have different models, with different capabilities and costs. We should have a configuration table to map Sales Area and Use Case to the specific model to use too.

---

25Q3-33 Fix the error handling on extending customer and location in the quote tool

High Done!

As a sales representative

I want to have proper error handling when extending customer and location in the quote tool

So that I can tell the system to extend MD automatically when I create a quote, instead of having to do it manually

Acceptance Criteria

The system should automatically extend customer and location master data when creating a quote if they do not exist in the backend after I confirm to do so.
Proper error handling should be implemented to manage any issues that arise during the extension process.

---

25Q3-35 make the form to add products in the quote tool manually

High Done!

As a sales representative

I want to have a form to add products manually in the quote tool

So that I can quickly add products to the quote

Acceptance Criteria

A form should be available in the quote tool to add products manually.

---

25Q3-36 In the quote tool, make the Quote Owner be picked automatically based on the configurable parameters

Medium Done!

As a sales representative

I want the Quote Owner to be picked automatically based on configurable parameters

So that I can save time and avoid errors when selecting the Quote Owner

Acceptance Criteria

We will need a table to configure for which Sales Areas is each user allowed to access the data and to be selected as Quote Owner. A user can be assigned to multiple Sales Areas.
The Quote Owner should be automatically selected based on configurable parameters:
Global Default: Sales Area only
Customer-Specific: Sales Area + Customer
Document Type Specific: Sales Area + Document Type
Plant Specific: Sales Area + Plant
Customer + Document Type: Sales Area + Customer + Document Type
Customer + Plant: Sales Area + Customer + Plant
Document Type + Plant: Sales Area + Document Type + Plant
Fully Specific: Sales Area + Customer + Document Type + Plant Therefore, we will need a configuration table to map those parameters to the users allowed in the Sales Areas.
and also a Default field to indicate which one should be picked automatically when the Quote Owner is not specified.

---

25Q3-37 In the quote tool, the price, And Cost data of a newly added product should come from the sync with backend button

High Done!

As a sales representative

I want the price data of a newly added product to come from the sync with backend button

So that I can ensure that the price data is accurate and up-to-date and in sync with SAP S/4 HANA

Acceptance Criteria

The price data of a newly added product should be fetched from the backend when the sync with backend button is clicked.
The cost data of a newly added product should be fetched from the backend when the sync with backend button is clicked.
The price and cost data should be updated in the quote tool after the sync with backend button is clicked.
The flow of data should be as follows:
User adds a new products to the quote
User also adds some Discount and Adjustments to the quote. These represent Condition Records in SAP S/4 HANA
User clicks the sync with backend button
the system creates the new Condition Records in SAP S/4 HANA using the Conditions API (mockup service) based on the Discounts and Adjustments added in the quote tool
The system creates the Contract in SAP S/4 HANA, including the newly added products
When syncing a quote that already exists in SAP S/4 HANA, the system updates the Contract via Contract API adding any new Products and quantities, and triggering repricing to ensure the new condition records are loaded in the prices of the products of the contract
The system fetches the price and cost data for the newly added products from the backend API response
The price and cost data is updated in the quote tool

---

25Q3-38 In the quote tool, make the Contract Type be picked automatically based on the configurable parameters

Medium Done!

As a sales representative

I want the Contract Type to be picked automatically based on configurable parameters

So that I can save time and avoid errors when selecting the Contract Type

Acceptance Criteria

The Contract Type should be automatically selected based on Sales Area Allowed configuration with a new Default field

---

2025 Q3: Foundation & Pricing

Core Deliverables

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria

Technical Notes

Acceptance Criteria

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Technical Notes

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria

Technical Notes

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria

Acceptance Criteria