Table and Table Descriptor Attributes
The second row lists the table attributes required in the file. The Table attribute row must begin with lsh_table=
If the second row is not present or contains null values, the system assumes that the filename (without extension) is the Table Name and follows the normal Oracle LSH default behavior for the attribute values. The attributes and their required order in the file are: Name, Description, Oracle Name, SAS Name, SAS Label, Process Type, Allow Snapshot?, Blinding Flag?, Blinding Status, SAS Library Name, Is Target?, Target as Dataset?, SDTM Identifier
Some attributes have associated reference codelists and allow either the actual values for the associated reference codelist (RC) columns or the decode values defined in the "Meaning" attribute of the _RC lookup. For example, "select meaning from cdr_lookups where lookup_code='< RC>' so that YES or Yes or $YESNO$YES are acceptable values.
The table below outlines the applicable values for each attribute that has an associated reference codelist.
Note:
Processing types that require audit keys are not supported.
Table 7-1 Table Attributes with Reference Codelist Values
Attribute | Values |
---|---|
Processing Type |
Staging with Audit, Staging without Audit, Transactional High Throughput, Transactional without Audit |
Allow Snapshot |
Yes, No |
Blinding Flag |
Yes, No |
Blinding Status |
Blinded, Unblinded |
Is Target |
Yes, No |
Target as dataset |
Yes, No |
Data Type |
Date, Number, Varchar2 |
Nullable |
Nullable Yes, No |
SDTM Identifier |
SUBJECT/SUBJECTVISIT |
Parent topic: Text Load Set Table Descriptors