Property master data – system description

Tables of the property master, the tax return address fields, the operator scope check, the searches and deletion blocked by contract references.

Property master: name, identifier, address, owner company, operating client, match value, label, address fields structured for the tourist tax return (default country HUN) and websites. The accommodation address of the tourist tax return is built on it.

Data model

Table names carry the installation's own prefix in the database.

TableRole
propertyproperty, structured address fields (IFA_COLUMNS), owner and operator company, match value, label
property_to_storewebsite link
companyowner / operator name
contractread: delete protection

Process

  1. List: filter by name and status; with owner and operator names.
  2. Save: name required; the operator must be an allowed company (error_operator_scope); addProperty/editProperty; websites only when sync_stores = 1. The tourist tax return's "new property" button pre-fills the operator via operator_company_id.
  3. Searches: labelsearch, companysearch (owner, searchActiveCompanyNames), companies (operator cascade).
  4. Delete: if any selected property is referenced by a contract, none is deleted.

Permissions

  • Function rights: list; edit (form, searches, status, header Add); save canSave() – with no add row, edit decides; delete; debug.
  • Content scope: only on the operator choice; the list is not narrowed.

Known limitations

  • The owner search does not filter by scope.
  • statusdelete is classified BASE but not implemented.
Related topics: property permissions