Entity_Doc_Involvement


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

General Information

[Next]
Name Entity_Doc_Involvement
Entity Type Table
Description The involvement of a document with an entity.
Submodel Utility
Entity Scope Project
Primary Key Id
Natural Key Index_Reference , Index_Type , Entity_Id , Start_Index , End_Index , Document_Id , Existence_Kind , Version
Generalizations Transient_Association , IT_Object , Tracked_Object
Specializations


Columns

[Previous] [Next] [Top]
NameValue DomainProperty /
Storage Unit
DescriptionRequired /
Default
Type
Document_Id Document
The document that is to be associated with an Entity Yes
NUMBER(38)
End_Date DATE NA
End time of the association No
DATE
End_Index double No_Unit
The end index for this document Involvement. If the entity the document is associated with is a depth indexed entity then this will be a depth. Likewise if the entity is time based then this index will be a date/time No
NUMBER
Entity_Id Entity
The Entity that the document is to be associated with. Yes
NUMBER(38)
Entity_Tbl Meta_Entity
Entity type Yes
VARCHAR2(30)
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)
Index_Reference CODE NA
The reference point for the Index. For example if the start_index for a photograph of a crack in a pipeline is 30 miles along the pipeline from Compressor Station #6 then the Index_Reference would be Compressor Station #6 No
VARCHAR2(64)
Index_Type R_Property
The index type for the involvement. Examples of this would be Length, Depth etc No
VARCHAR2(64)
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)
Produced_By STRING64 NA
The name of application role that created the entity, for data created programmatically. No
VARCHAR2(64)
SDAT_Label int No_Unit
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. No
NUMBER(10)
Start_Date DATE NA
Start time of the association. No
DATE
Start_Index double No_Unit
The start index for this document Involvement. If the entity the document is associated with is a depth indexed entity then this will be a depth. Likewise if the entity is time based then this index will be a date/time No
NUMBER
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
Index_Type R_Property The index type for the involvement. Examples of this would be Length, Depth etc Restrict No
Entity Entity The Entity that the document is to be associated with. Cascade Yes
Document Document The document that is to be associated with an Entity Cascade Yes


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

Copyright © 2018 Schlumberger. All rights reserved.