| Name | Transfer_of_Interest |
|---|---|
| Entity Type | Table |
| Description | A transfer of interest is when one interest set partner transfers its share or a portion of its share in an interest set to another business associate. Before the transfer of interest record can be created, there must be a record for the new business partner in the Interest_Set_Partner table. |
| Submodel | Interest_Set |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Transfer_From_Partner_Id , Transfer_To_Partner_Id , Transfer_Effective_Date , Existence_Kind , Version |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| 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) |
| Instrument_Id | Instrument |
|
The instrument in which this transfer of interest is recorded. | No |
NUMBER(38) |
| Interest_Percent | double | Percent % |
The amount of interest that was transferred from one partner to another. | No |
NUMBER |
| 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) |
| Processing_Order | int | No_Unit |
In the cases where multiple transfers of interest are effective on the same date, this attribute can be used to specify the order in which the transfer should take place. For example, there may be one transfer of interest for A to B, and then a second transfer of interest from B to C. The transfer from A to B has to occur before the transfer from B to C so that B exists in the record and has something to transfer. | No |
NUMBER(10) |
| 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) |
| Transfer_Approval_Date | DATE | NA |
The date the transfer of interest was approved. Applicable mostly in cases where interest is governed by a regulatory or governmental agency. | No |
DATE |
| Transfer_Effective_Date | DATE | NA |
The effective date of the transfer of interest. Note, if this record references an instrument record, the effective date should be in sync with the effective date of the referenced instrument. | No |
DATE |
| Transfer_From_Partner_Id | Interest_Set_Partner |
|
The interest set partner that transferred a share of its interest to another partner. | Yes |
NUMBER(38) |
| Transfer_To_Partner_Id | Interest_Set_Partner |
|
The interest set partner to whom the interest was transferred. | Yes |
NUMBER(38) |
| 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 |
|---|---|---|---|---|
| Transfer_From_Partner | Interest_Set_Partner | The interest set partner that transferred a share of its interest to another partner. | Cascade | Yes |
| Transfer_To_Partner | Interest_Set_Partner | The interest set partner to whom the interest was transferred. | Cascade | Yes |
| Instrument | Instrument | The instrument in which this transfer of interest is recorded. | Restrict | No |