Hi Hans, First of all thank you for your comments and suggestions. Maybe as you offered I will create issue for this later.
It is true accommodation classes,spots could be used for theater seats etc but I also think they could be used for room renting as well. For example we could define the room types as accommodation classes and through accommodation maps relate to these classes the rooms which are fixed assets. I don`t think the current implementation supports room types renting unless we define the room type as a fixed asset(I mean to reserve room type without assigning an actual room number/fixed asset. I think this could be achieved only if we define the room type as a fixed asset because in this way we would be able to increase its used capacity?) Or maybe there is some better way? About reservations - for RENTAL_ORDER_ITEMS right now we create workeffort record from which we extract information like:start,end dates reservMaxPersons,reserv2reservNthPPPerc,reserv2ndPPPerc then we use part of this information for the TechDataCalendars. My idea about reservation is not much different - the only difference is that we won`t use workeffort record + TechDataCalendars to store rental related information like from, thru dates etc but AccommodationSpot(or it could have some other name) entity which will be specifically for reservation data. I guess most of the fields of the workeffort entity won`t be necessary for the rental data while all the AccommodationSpot fields will be used. And if we use an entity which has from and thru dates maybe we will be able to implement hourly reservations? I think right now the only way is the Shi Yusen`s approach, which is probably not the best solution for hourly reservation - it creates too many records and it is not very flexible? Thanks : Valentina :) -- View this message in context: http://www.nabble.com/Stop-using-techdata-calendar-tf4292733.html#a12416807 Sent from the OFBiz - Dev mailing list archive at Nabble.com.
