The logistics application
Similar to Production Orders in the standard application, the processes in our logistics application are status driven rather than transaction driven. This is why this part of the application does not have a journal with entries. The tables can have archived copies but they are not part of a normal registering or posting routine.
|
For the examples in this part of the chapter, we should change the default Role Center to |
Designing the table and posting schema
If we look at the structure of the logistics application, we can see that the typical posting transactions are missing. The application uses a status-driven workflow based on events which are defined in the triggers of the tables.
The logistics shipment and shipment details have a lot of similarity with the shipments from the warehouse. Still we have chosen...
