[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 LX / BPCS Tip of the Week: Pre-assigned lot numbers for multi-level SO release
In addition to assigning lot numbers in Shop Order Entry/Maintenance (SFC500) after the shop orders have been released, users can now pre-assign lot numbers during the Multi-level Shop Order Release process (SFC530) and the Multi-Level Back-flush process (LMP600) for sub-assemblies that are lot controlled items. The user has the choice of using the parent lot ID, using the next sequential generated lot ID, or not pre-assigning lot IDs. Multiple items per lot must be installed to use the parent lot number option.