| Name | Activity_BA_Invl_Interest |
|---|---|
| Entity Type | Table |
| Description | The definition of the interest that a BA has in a particular Activity |
| Submodel | Activity |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Transient_Association , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Activity_BA_Invl_Id | Activity_BA_Invl |
|
The activity BA involvement to which these interests refer | Yes |
NUMBER(38) |
| End_Date | DATE | NA |
End time of the association | 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) |
| Interest_Percent | double | Percent % |
The percent of interest Business Associate holds in the Well | No |
NUMBER |
| Interest_Type | R_Interest |
|
The type of interest, for example Working interest or Operating interest. | 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) |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Interest_Type | R_Interest | The type of interest, for example Working interest or Operating interest. | Restrict | Yes |
| Activity_BA_Invl | Activity_BA_Invl | The activity BA involvement to which these interests refer | Cascade | Yes |