BA_Group


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

General Information

[Next]
Name BA_Group
Entity Type View
Description An arbitrary grouping of business associates. Examples include work teams of people and loose aggregations of companies such as consortiums.
Submodel Business_Associate
Entity Scope Shared
Primary Key Id
Natural Key Unique_Identifier , Business_Associate_Type , Existence_Kind , Version
Generalizations Business_Associate , Entity , IT_Object , Tracked_Object
Specializations


Columns

[Previous] [Next] [Top]
NameValue DomainProperty /
Storage Unit
DescriptionRequired /
Default
Type
Business_Associate_Type R_Business_Associate
A mnemonic code or abbreviation that uniquely identifies the types of Business Associate. Examples of type are corporation, sole proprietor, partnership, or individual. Note that types must form a valid combination with BA Sub Types. The Sub Types are Company, Person, BA Group, and Generic BA. A valid combination is Company/Corporation. An example of an invalid combination is Person/Corporation. This rule is enforced via a lookup against the R_Valid_BA_Type table. Yes
VARCHAR2(64)
Current_Flag boolean NA
An indicator that identifies if a business associate is eligible for current activity. If true, the business associate should appear in drop down lists and be available to users for inclusion in new relationships and activities. If false, the business associate should not be made available to users for inclusion in new relationships or activities. If false, the business associate is kept for the purpose of reporting history and to maintain data integrity. No
NUMBER(1)
End_Date DATE NA
The last date that a business associate exists or is active, for example, the date a company is dissolved. 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)
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)
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)
Start_Date DATE NA
The first date that a business associate exists or is active, for example, the date of incorporation of a company. No
DATE
Sub_Type Meta_Entity
Sub type of Business_Associate No
VARCHAR2(30)
Unique_Identifier STRING128 NA
An identifier, defined and constructed by users of the database, that allows business associates to be uniquely identified for the purpose of matching and loading data. For example, a user has a text file with information on thousands of employees to be loaded. A unique id concatenating last name, first name, middle initial, and birth date is constructed and stored in this field. As records are loaded, an exact match found on this combined data indicates a duplicate and the record is skipped or updated. USAGE NOTE: This column is currently used in a natural key for Business Associate, which also includes the columns: Name and BA Type. Please ensure that, when loading data, a value is placed in Unique Identifier that is truly unique across all sub-types (Person, Company, BA_Group, Generic_BA) of Business Associate. No
VARCHAR2(128)
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
WG_Survey_2D Geomarket The geomarket responsible for the sales and marketing of the survey. Cascade No
WG_Survey_3D Geomarket The geomarket responsible for the sales and marketing of the survey. Cascade No


Refers To

[Previous] [Next] [Top]
LinkTo EntityDescriptionImplementation TechniqueRequired
Business_Associate_Type R_Business_Associate _ Restrict Yes


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

Copyright © 2018 Schlumberger. All rights reserved.