I doubt that you need a generic load to transform a normal record into a crosstable-structure - especially within the final data-model and the UI. For some intermediate measures it might be useful but in a final application it's very hard to handle. Nearly everything is much easier possible with normal data-structures. In your case a base-table with:
OrderKey Order Date Status
should be sufficient to enable all relevant associations and selections. Date and Status would be linked with appropriate dimension-tables and providing month + year +++ to the dates and various upper/lower grouping & descriptions to the status.
On this base is much more possible, for example to count/rank/sort the number of Status per Order and/or calculating the offset between the Dates/Status and/or deriving any scoring within a chain of events and surely much more - just by using interrecord-functions like peek() and previous() within a sorted resident load, maybe with something like this:
t: load *, if(Order = previous(Order), Date - previous(Date), 0) as DateOffset;
if(Order = previous(Order), 1 + peek('OrderRank'), 1) as OrderRank
resident Source order by Order, Date desc;
left join(t) load Order, count(Date) as OrderCount
resident t group by Order;
%20-%20My%20new%20sheet%20_%20Sheet%20-%20Qlik%20Sense%20and%207%20mo.png){kind=link}
