| Name | Activity_BA_Invl |
|---|---|
| Entity Type | Table |
| Description | The record of the involvement of one business associate with one activity. There should be one such involvement record for each involvement which must be individually tracked. For example, if Grey Wolf was the drilling contractor from April to June and again from August to November and the Sharper Bit company served in that role from June to August, this would probably be three distinct involvements. |
| Submodel | Activity |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Activity_Id , Business_Associate_Id , Activity_Role , Existence_Kind , Version |
| Generalizations | Transient_Association , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Activity_Id | Activity |
|
The associated Activity of this involvement. | Yes |
NUMBER(38) |
| Activity_Role | R_BA_Activity_Role |
|
The role played by the business associate in the activity. | Yes |
VARCHAR2(64) |
| Activity_Tbl | Meta_Entity |
|
Activity type | Yes |
VARCHAR2(30) |
| Business_Associate_Id | Business_Associate |
|
The Business Associate associated with this involvement. | Yes |
NUMBER(38) |
| Contact_Situation | STRING128 | NA |
Textual description of situations at which the business associate should be contacted. | No |
VARCHAR2(128) |
| 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) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Rank | int | No_Unit |
The ordered instance number of a particular role for a particular activity. For example, on a given drilling activity two different drilling contractors might have been used in the Activity_Role = "driller". | Yes 1 |
NUMBER(10) |
| Remarks | STRING2000 | NA |
Remarks or comments concerning the involvement of the business associate with the activity. | No |
VARCHAR2(2000) |
| Role_Template_Id | Act_Tmpl_BA_Role |
|
Optional business associate involvement role template. | No |
NUMBER(38) |
| 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) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Activity_BA_Invl_Interest | Activity_BA_Invl | The activity BA involvement to which these interests refer | Cascade | Yes |
| Perforation_Summary_DOV | Activity_BA_Invl | READ ONLY: Unique identifier for the activity BA involvement. | Cascade | No |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Activity | Activity | The associated Activity of this involvement. | Cascade | Yes |
| Role_Template | Act_Tmpl_BA_Role | Optional business associate involvement role template. | Restrict | No |
| Business_Associate | Business_Associate | The Business Associate associated with this involvement. | Cascade | Yes |
| Activity_Role | R_BA_Activity_Role | The role played by the business associate in the activity. | Restrict | Yes |