Log_Channel_Alias


[Columns] [Composed Of] [Referenced By] [Refers To]

General Information

[Next]
Name Log_Channel_Alias
Entity Type Table
Description Set of alternate names or IDs for a Log_Channel.
Submodel Well_Log
Entity Scope Project
Primary Key Id
Natural Key Log_Channel_Id , Alias_Name , Alias_Type , Start_Date , Existence_Kind , Version
Generalizations Abstract_Alias , Entity , IT_Object , Tracked_Object
Specializations


Columns

[Previous] [Next] [Top]
NameValue DomainProperty /
Storage Unit
DescriptionRequired /
Default
Type
Alias_Name STRING255 NA
An alternative name Yes
VARCHAR2(255)
Alias_Type R_Log_Channel_Alias
The type of alias for the log channel. Yes
VARCHAR2(64)
End_Date DATE NA
End of the effective period for the Alias No
DATE
Existence_Kind REF_EXISTENCE_KIND NA
A reference value that describes the state of existence in the lifecycle of the entity, for example, Planned, Predicted, Required, Simulated, and Actual. Yes
Actual
VARCHAR2(64)
GUID STRING128 NA
Globally Unique IDentifier for an instance of a class. USAGE NOTES: There are two cases: 1) GUID is not populated or used; and 2) it is populated with a value that is globally unique. If the GUID is populated there are two means of doing so for a given project: 2a) Seabed automatically generates and populates the GUID when an instance is created (valid only on Oracle based systems); and 2b) the GUID is generated and populated by an application (other than Seabed) on instance creation. Whether Seabed automatically generates GUIDs for a project is determined by the Auto_GUID flag in SDS_Account. Note that techniques 2a and 2b can coexist in the same project. When GUIDs are automatically generated an application can override the automatically generated GUID with its own GUID by simply supplying the GUID value. Applications that generate their own GUIDs and populate the GUID column will function correctly on projects which have automatic GUID generation turned on. No
VARCHAR2(128)
Id ID No_Unit
Unique identifier for this entity. Yes
NUMBER(38)
Insert_Date DATE NA
Date the entity was created in the repository No
DATE
Insert_User STRING64 NA
The name of the user responsible for the creation of this entity in the repository. No
VARCHAR2(64)
Log_Channel_Id Log_Channel
An association used to define a number of aliases for a log channel. Yes
NUMBER(38)
Name ENTITY_NAME NA
The name given to any object or data item, e.g. name of Well, name of Field, etc. No
VARCHAR2(255)
Original_Source STRING64 NA
The name of the person, Organization or project source that originally provided this entity, e.g. "IHS-EnergyData" or "FinderUpper Stratton Deeper Pool 15" No
VARCHAR2(64)
Produced_By STRING64 NA
The name of application role that created the entity, for data created programmatically. No
VARCHAR2(64)
Remarks STRING2000 NA
Any type of remarks added to an entity instance. No
VARCHAR2(2000)
SDAT_Label int No_Unit
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. No
NUMBER(10)
Source STRING64 NA
Name of the person or organization responsible for this entitys E and P content and quality. Not the data technologist or IT expert creating the entity, for which see IT_Object.Insert_User and Update_User. No
VARCHAR2(64)
Start_Date DATE NA
Effective date of the Alias No
DATE
Update_Date DATE NA
Date of the most-recent modification to the entity. No
DATE
Update_User STRING64 NA
The name of the user responsible for the last modification to this entity. No
VARCHAR2(64)
Version STRING255 NA
The form or variant of the entity. Yes
1
VARCHAR2(255)


Refers To

[Previous] [Next] [Top]
LinkTo EntityDescriptionImplementation TechniqueRequired
Alias_Type R_Log_Channel_Alias The type of alias for the log channel. Restrict Yes
Log_Channel Log_Channel An association used to define a number of aliases for a log channel. Cascade Yes


[Seabed Objects] [Entities in Schema Seabed] [Index]

Copyright © 2018 Schlumberger. All rights reserved.