The typical problem with what you're advocating is that in an enterprise environment typically your application is communicating with a number of external data sources that already make a bunch of assumptions about data, whether they're reasonable assumptions or not, and they typically expect that you'll be able to return them their data at the same level of granularity as they've provided it to you. E.g. if your client's 70s COBOL application gives you a list of their customers with addresses including a postcode field and then your application filters that or something and sends back a second list, it won't be acceptable to give them back addresses with the postcode simply concatenated into a text field with the other parts of the address.

The correct way to handle this is to be able to dynamically accept and store arbitrary granularity of data (and be able to translate that into a single text field at runtime if needed).