[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration]
[EasyDNNnews:IfExists:Payment]
[EasyDNNnews:Price][EasyDNNnews:EndIf:Payment]
[EasyDNNnewsLocalizedText:Eventdate]:
[EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent]
[EasyDNNnews:IfExists:EventLocation]
[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]
[EasyDNNnews:EndIf:EventLocation]
[EasyDNNnews:IfExists:EventRegistration]
- [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
- [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
- [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
[EasyDNNnews:IfExists:Payment]- [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
[EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage]
[EasyDNNnews:EndIf:EventRegistration]
[EasyDNNnews:IfExists:EventSignUp]
[EasyDNNnewsLocalizedText:AreYouGoing]
[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
[EasyDNNnews:EndIf:Event]
Infor LN & Baan Tip: Backflushing of Materials & Hours
Why do I sometimes see small decimal quantities remaining after backflush?
This behavior is largely caused by differences in decimal quantities allowed in inventory units versus the display format of the data. Having different display formats with different rounding for material quantities and warehouse line quantities means that since these quantities interact, if one is rounded more strictly and the other is not, then the rounded quantity is being propagated to the other quantity, thus resulting in a loss of decimals. As a result, it is advised to not use different formats and rounding settings for material quantities and warehouse line quantities.