Contact
Contacts are the point of communication with the given party. In the case of an organization it may be the requisitioner, the buyer, customer service, etc.
Child Components
Type Code 0..1
Action Code 0..1
Language Code 0..1
Identifier 0..∞
UUID 0..1
Source Identifier 0..1
Party Identifier 0..1
Identifier Set 0..∞
Related Identifier 0..∞
Person Name 0..1
Description 0..∞
Gender Code 0..1
Marital Status Code 0..1
Birth Date Time 0..1
Death Date Time 0..1
Age Measure 0..∞
Language Code 0..∞
Nationality Country Code 0..1
Address 0..∞
Communication 0..∞
Role Code 0..∞
Job Title 0..1
Responsibility 0..∞
Organization Unit Identifier 0..1
Telephone Communication 0..∞
EMail Address Communication 0..∞
Internet Address Communication 0..∞
Preference 0..1
Effective Time Period 0..1
Extension 1..1
UML Class Model
You can save the file locally and use it, for example, in PowerPoint.
SVG File
@startuml
class Contact {
String TypeCode
CodeList ActionCode
String LanguageCode
String Identifier
String UUID
String SourceIdentifier
String PartyIdentifier
String Description
CodeList GenderCode
CodeList MaritalStatusCode
String BirthDateTime
String DeathDateTime
String AgeMeasure
String LanguageCode
String NationalityCountryCode
String RoleCode
String JobTitle
String Responsibility
String OrganizationUnitIdentifier
}
class "IdentifierSet"{}
class "RelatedIdentifier"{}
class "PersonName"{}
class "Address"{}
class "Communication"{}
class "TelephoneCommunication"{}
class "EMailAddressCommunication"{}
class "InternetAddressCommunication"{}
class "Preference"{}
class "EffectiveTimePeriod"{}
Contact o-d- "0...∞" "IdentifierSet"
Contact o-r- "0...∞" "RelatedIdentifier"
Contact o-u- "0...1" "PersonName"
Contact o-l- "0...∞" "Address"
Contact o-d- "0...∞" "Communication"
Contact o-u- "0...∞" "TelephoneCommunication"
Contact o-d- "0...∞" "EMailAddressCommunication"
Contact o-u- "0...∞" "InternetAddressCommunication"
Contact o-d- "0...1" "Preference"
Contact o-u- "0...1" "EffectiveTimePeriod"
hide circle
@enduml
Where Used
Following is a list of components that have Contact as a child component.
- Access Request Party
- Advisor Party
- Analysing Party
- Anchoring Point Location
- Approved By Party
- Approved For Use Enterprise Unit
- Authorizing Party
- Bill To Party
- Bill To Party Reference
- Branch Party
- Broker Party
- Business Partner Party Master
- Business Partner Reference
- Buyer Party
- Carrier Party
- Carrier Party Reference
- Catalog Party
- Certification Party
- Change Request Header
- Change Request Line
- Check From Party
- Child Party
- Cleaned By Party
- Commercial Invoice Header
- Competitor Party
- Concerned Party
- Configuration End User Party
- Contract Header
- Contract Line
- Contributor Party
- Created By Party
- Created For Party
- Creator Party
- Credit Party
- Creditor Party
- Customer Party
- Customer Party Master
- Customer Party Reference
- Debtor Party
- Declarant Party
- Declaring Party
- Deliver To Party
- Deliver To Party Reference
- Depositor Party
- Discount Allowance Pricing
- Distributor Party
- End User Party
- Enterprise Unit
- Final Agent Financial Party
- Final Party
- Financial Party
- Financial Party Reference
- Financing
- First Agent Party
- Forwarding Agent Party
- Freight Invoice Header
- Freight Invoice Line
- Freight Invoice Sub Line
- In Queue Location
- Incorporation Location
- Initiating Party
- Inspection Party
- Inspector Party
- Install Use Location
- Intermediary Financial Party
- Intermediate Ship To Party Location
- Invoice Header
- Invoice Line
- Invoice Sub Line
- Invoicee Party
- Invoicer Party
- Involved Party
- Issuing Party
- Line Feed Location
- Loading Location
- Location
- Location Master
- Manufacturing Party
- Mark Owner Party
- Move Product Forecast Header
- Move Product Forecast Line
- Move Product Header
- Move Product Line
- Operating Location
- Operator Party
- Opportunity Header
- Originator Party
- Out Queue Location
- Owner Party
- Parent Party
- Parent Sample Location
- Party
- Party Master
- Party Reference
- Party Tax Profile
- Pay From Party
- Payee Party
- Payee Party Reference
- Payment Plan Term
- Payor Party
- Place Of Ownership Transfer Location
- Plan From Party Reference
- Plan To Party Reference
- Port Authority Party
- Processed Location
- Provider Party
- Publisher Party
- Purchase Order Header
- Purchase Order Line
- Purchase Order Sub Line
- Purchasing Party
- Quote Header
- Quote Line
- Quote Sub Line
- Received By Party
- Receiving Location
- Recipient Party
- Registrar Party
- Remit To Party
- Remittance Advice Header
- Request Sub Line
- Requester Party
- Requesting Party Reference
- Requisition Header
- Requisition Line
- Requisition Sub Line
- Responsible Supplier
- Retailer Party
- Reviewer Party
- RFQ Header
- RFQ Line
- RFQ Sub Line
- Route Stop Party
- Sales Lead Header
- Sales Order Header
- Sales Order Line
- Sales Order Sub Line
- Sales Party Master
- Sales Party Reference
- Sales Task
- Sample Location
- Sample Preparer Party
- Screen Location
- Screen Party
- Screen Perform By Party
- Service Advisor Party
- Services Discount Allowance Pricing
- Ship From Location
- Ship From Party
- Ship From Party Reference
- Ship To Location
- Ship To Party
- Ship To Party Reference
- Shipper Party
- Shippers Letter Of Instruction Header
- Signatory Party
- Site Location
- Sold To Party
- Sold To Party Reference
- Solicitation
- Station Location
- Steward Party
- Submitting Party
- Supplier Party
- Supplier Party Master
- Supplier Party Reference
- Ultimate Recipient Party
- Vendor Party
- Warehouse Location
- Warehouse Party
- Warranty Claim Header
- Warranty Claim Line
- Work Location
- Work Order Header
- Work Order Line
- Work Order Sub Line
Feedback
OAGi and its members welcome your feedback.
UUID: 49e83f51cb454e6bb821ef931bee3482
connectSpec (OAGIS) Version 10.12