on 03-09-2023 11:15 AM
If you select a table, that table will be included in any queries that the object is used in. That may be ok if you do expect the table to be used whenever the object is used, but it can create unexpected results otherwise.
You don't have to associated a table. Leaving it unassociated will result in the parse error you got, but queries will run successfully, as long as at least one other object is included that is associated with a table.
I submitted a request years ago to more formally support unassociated objects: Improvement Request Details - Customer Influence (sap.com)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I complete agree with leaving them unassociated and suggest you add a suffix such as LIT (for literal) to these objects. Just remember going forward that LIT objects will produce this integrity error message that you can ignore. We use LIT because we also have objects with hard-coded literal values in addition to the various calculated dates.
User | Count |
---|---|
70 | |
9 | |
8 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.