Description
When importing a schema for an Oracle database view which is available via a synonym (original view located in another schema than connected to) then the attributes in the imported metadata are not in their original order.
(I also made the experience that a built-in schema entered manually for a db component does not show the attributes in the order they were stored as soon as the schema is reopened again!)