New Feature | Feature Description |
Cleanup Script Details Added to Getting Support | In error situations it might be necessary to execute SDI Agent cleanup scripts on the source database. The necessary details have been added to the Getting support UI. |
Display of Replicated Pricing Records | The replicated pricing records can be queried and displayed within the UI Replication → Pricing. In order to see the price data from table KONP the additional role PricingDataAccess is required. |
Improvements of Extension Traces | The trace content can now be viewed in a popup window, this option is found in the Extension Trace UI. A refresh and auto-refresh options are available as well. |
Performance Improvement for Loading Variant Tables | Several unnecessary steps have been removed from the load of variant tables to improve performance. |
Redesign for Trace UIs | The UIs for engine trace and extension trace have been combined into a new Trace UI. |
Support for Pricing Sub-procedures | Pricing Sub-Procedures are now supported in the UI Pricing-Replication. The replication is enhanced to load data related to pricing sub-procedures. |
New Feature | Feature Description |
External Configurations API – Create External Configuration by Date | When creating a new configuration from an external configuration via endpoint POST /api/v2/externalConfigurations, the knowledge-base id had to be provided. Now, the configuration date can alternatively be provided, that lets the service determine the valid knowledge-base version at the given date before creating the configuration. The configuration date is also stored with the configuration results and returned as part of the external configuration. |
Knowledgebases API – Return Variant Table Details | Variant table content can be displayed and used outside of the configuration engine thanks to:
See API Definition. |
New Feature | Feature Description |
Display of Replicated Pricing Records | The replicated pricing records can now be queried and displayed via the administration UI’s menu Replication → Pricing. To see the price data from table KONP, the additional PricingDataAccess role is required. See Administration Guide for SAP Variant Configuration and Pricing. |
S/4HANA Cloud – New Customer Hierarchy | Price conditions can be defined for various nodes of a customer hierarchy. Since S/4HANA Public Cloud 2208, Universal Hierarchy Framework is used as the foundation of a new customer hierarchy. Pricing service allows to provide the customer hierarchy as new item input structure customerHierarchy and supports condition finding based on the provided customer hierarchy. See API Definition, Development Guide for SAP Variant Configuration and Pricing, Customer Hierarchies in Sales, and Type: Customer Hierarchy - Sales. |
S/4HANA Cloud – New Product Hierarchy | Price conditions can be defined for various nodes of a product hierarchy. Since S/4HANA Public Cloud 1911, Universal Hierarchy Framework is used as the foundation of a new product hierarchy. Pricing service allows to provide the item’s product hierarchy as price attribute and supports condition finding. It used to support only condition finding from root node to leaf node ignoring the specified distance. Now it also considers the distance and supports direction leaf node to root node. See API Definition, Development Guide for SAP Variant Configuration and Pricing, and Product Hierarchies in Sales. |
Support Modular Pricing Procedures for Automatic Inclusion of Price Conditions | Pricing service supports new pricing conditions of type inclusion point in SAP S/4HANA Cloud. During runtime, those inclusion points trigger determination of a sub-procedure whose condition types are then inserted into the main pricing procedure. See Modular Pricing Procedures for Automatic Inclusion of Price Conditions, and SAP Note 2894167 . |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |