Karnchana, As far as I see from your data, you model the following(please correct me if I am wrong): You model restaurant which has 2 rooms and they all are fas. The rooms are related to the restaurant via parent-child relationship. They all are located at the "TableServices" facility. - In the Map entity you define the total nr of tables and chairs in the restaurant and the 2 rooms(the "Private and Communal") - In the spot entity you model the capacity of each table/chair. And the tables/chairs are spots.
If I got it right then I would say this data structure is fine. However I would like to make the following remarks: Keep in mind that whatever you put in the spot entity is what can be booked. This means if for example you have the following record from your data: <AccommodationSpot accommSpotId="8" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-5"/> when you make reservation the WHOLE table will be BOOKED!All the 4 spaces as the spotId is unique! If you want to avoid this and make PARTIAL bookings I would suggest one of the following: 1) Generate as much SPOT records as needed to reach the total capacity of the table. In this case it will be: <AccommodationSpot accommSpotId="9" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="1" accomNumber="PrVIP-5"/> <AccommodationSpot accommSpotId="10" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="1" accomNumber="PrVIP-5"/> <AccommodationSpot accommSpotId="11" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="1" accomNumber="PrVIP-5"/> <AccommodationSpot accommSpotId="12" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="1" accomNumber="PrVIP-5"/> Now you can book spots 9,10,11 if you want 3 spaces and not 4 or just spot 12 if you want 1 space only. Well, this is not the best way for me....(too many records and not a real solution) 2) Think of making the tables fa related to their rooms with parent-child relationship. Then define new accommodationClass somethng like: 30_place_table and relate it to the table in the MAP. Then think of using no assign algorithm using this map record, which means you will not reserve spots anymore but products related to a given class. Of course this sort of algorithm would require more extentions of our CURRENT model so I am not sure if it will be the best for you... Regards:Valentina -- View this message in context: http://www.nabble.com/Question-on-spot-class-map-entities%28copied-from-jira-1590%29-tp15089930p15093655.html Sent from the OFBiz - User mailing list archive at Nabble.com.
