Skip to main content

2025.3 Release Notes

Set out below is a summary of the highlights, fixes and improvements in the 2025.3 on-premises version of Angles for SAP.

End User - Fixes and Improvements

Feature Description
Dynamic Safety Stock Coverage Profile Integration

What's New

Angles for SAP now intelligently incorporates dynamic safety stock coverage profiles into reschedule advice date calculations. This enhancement ensures that orders planned according to coverage profiles maintain their strategic safety stock replenishment timing while accommodating urgent demand requirements.

Key Capabilities

Enhanced Reschedule Logic for Coverage Profile Orders

  • Reschedule advice dates now consider both existing demand requirements and coverage profile replenishment schedules.

  • Orders planned due to dynamic safety stock coverage profiles can only be rescheduled to earlier dates when driven by existing demand.

  • Prevents inappropriate rescheduling beyond the planned safety stock replenishment date, preserving coverage profile integrity.

Key Benefits

Protected Safety Stock Strategy: Ensures that safety stock replenishment timing established by coverage profiles cannot be compromised by inappropriate reschedule recommendations, maintaining inventory strategy integrity.

Balanced Planning Decisions: Planners receive reschedule advice that optimally balances urgent demand requirements with strategic safety stock replenishment needs, preventing conflicts between operational and strategic objectives.
EA4IT Last Time Used Property for Field Management We have added a new "Last Time Used" property to the EA4IT fields object, displaying the most recent execution date when each field was used in angle displays, filters, pivots, or graphs. This enhancement enables administrators and consultants to identify fields that are defined in angles but not actively used by users, supporting informed cleanup and optimization decisions for better data model management.
ExchangeRate Module Optimization

The ExchangeRate module has been optimized to improve performance and structure. The existing single ExchangeRate class [TCURR] is continued and can be used as before. The following classes have been added as part of this change:

  • Exchange Rate Type: based on SAP Table [TCURV]

  • Exchange Rate Factor: based on SAP Table [TCURF]

  • Exchange Rate Quotation: based on SAP Table [TCURN]

  • Exchange Rate Spread: based on SAP Table [TCURS]

  • Currency Code: based on SAP Table [TCURC]

These classes can be used to validate exchange rate conversion calculations. New templates and help texts have been created for all the new classes.
Private Angle not able to be set to Favorite (Starred) When a user is authorized to manage private angles the user can see private angles from other users. Like with all other, own or published angles, a star icon was shown to mark these angles as favorite. Marking another users private angle as favorite however is not possible as part of the design, although the starred icon to do so was available. To avoid confusion we are now hiding the starred icon for other users created private angles.
[05315850] Field 'Expected Demand next x days' does not give the expected result It was found that field 'Expected Demand next x days' did not always give the expected result. Investigation revealed caching concurrency issues and incorrect boolean resets affected property calculations. This has now been resolved.
[05243807] Fixed discrepancy between SAP Net Value and A4S Sales Value calculations The Sales Value calculation in A4S was incorrectly including cancelled sales order line items, causing a mismatch between SAP's Net Value field and A4S calculated Sales Value. We have updated the calculation logic to properly exclude cancelled line items from the Sales Value computation.
[05328790] Automation Task Action History angle giving angle execution failure message Executing an EA4IT - Automation Task Action History angle could result in the following error: Conflict, ["reason":"_Query execution failed","message":"Invalid length parameter passed to the LEFT or SUBSTRING function_."]. This has now been resolved.
Quotations now use "Corrected quantity" as quantity for Order Network Calculation For the MRP relevance determination already the “Corrected quantity” of quotations was used to see whether there is still a relevant quantity left. But for the PIR consumption within the order network calculation, previously still the “Open quantity” was used, resulting in coupling for that amount to independent requirements, leaving a reduced quantity in the independent requirements that did not match the SAP MD04 overview. Now the “Quantity corrected” is used for the PIR consumption phase as well, so the open quantities that are not expected anymore in the quotation will also not consume from independent requirements.

 

 

Was this article helpful?

We're sorry to hear that.