Navision table schema

There isn't such a thing but after a while you will realize that naming conventions make this unnecessary.

F.e. a non-standard example - if there would be a car renting solution there would be a master table called Car. It's primary key would be No. and it would have a Description field, maybe a Description 2 as well. It's movements were called Car Ledger Entry or Car Entry (Entry is for sure) and those entries were created by a Car Journal Line. Both would reference the car as Car No., would have Posting Date, Document No., Description, Quantity, the renting fee would be called Unit Something (f.e. Unit Fee) for one car and Something Amount (f.e. Fee Amount) for the whole line. If there were multiple lines in one transaction you would have a document like Car Renting Header and Car Renting Line and probably posted versions of the table as well. The header would either have No. or Document Type, No. as primary key and the line would reference it as Document Type, Document No., Line No. And so on.

In NDT you see relationships between objects