Activity_Entity_Invl


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

General Information

[Next]
Name Activity_Entity_Invl
Entity Type Table
Description An entity acting as an input or output to an activity. Tracks what activity used and produced which data.
Submodel Activity
Entity Scope Project
Primary Key Id
Natural Key
Generalizations Transient_Association , IT_Object , Tracked_Object
Specializations


Columns

[Previous] [Next] [Top]
NameValue DomainProperty /
Storage Unit
DescriptionRequired /
Default
Type
End_Date DATE NA
End time of the association No
DATE
Entity_Role_Name STRING64 NA
A name that describes the role the entity plays in its involvement with the activity. No
VARCHAR2(64)
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)
Involved_Activity_Id Activity
The identifier of the activity for which the data role is either an input or output. Yes
NUMBER(38)
Involved_Activity_Tbl Meta_Entity
Activity type Yes
VARCHAR2(30)
Involved_Entity_Id Entity
The entity that is playing this data role for this activity. In other words, the entity that is "bound" to this data role. Yes
NUMBER(38)
Involved_Entity_Tbl Meta_Entity
Entity type Yes
VARCHAR2(30)
Involvement_Type R_Activity_Entity_Invl
The type of involvement an entity has with an activity, with respect to that activity. For example, "Input" means that the entity is involved as an input to the activity. "Output" means that the entity is involved as an output from the activity. "Incidental" means that the type of involvement is neither an input or output. Yes
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
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)


Referenced By

[Previous] [Next] [Top]
From EntityLinkDescriptionImplementation TechniqueRequired
Activity_Dataflow_Arc Flow_Source The identifier of the activity data role that is on the source side of this connection. Cascade Yes
Activity_Dataflow_Arc Flow_Destination The identifier of the activity data role that is on the destination side of this connection. Cascade Yes


Refers To

[Previous] [Next] [Top]
LinkTo EntityDescriptionImplementation TechniqueRequired
Involved_Activity Activity The identifier of the activity for which the data role is either an input or output. Cascade Yes
Involvement_Type R_Activity_Entity_Invl The type of involvement an entity has with an activity, with respect to that activity. For example, "Input" means that the entity is involved as an input to the activity. "Output" means that the entity is involved as an output from the activity. "Incidental" means that the type of involvement is neither an input or output. Restrict Yes
Involved_Entity Entity The entity that is playing this data role for this activity. In other words, the entity that is "bound" to this data role. Cascade Yes


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

Copyright © 2018 Schlumberger. All rights reserved.