Billing Address
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..∞
Name 0..∞
Attention Of Name 0..∞
Care Of Name 0..∞
Address Line 0..∞
Building Number 0..1
Building Name 0..1
Block Name 0..1
Street Name 0..1
Street Type Code 0..1
Floor 0..1
Unit 0..1
Stair Case 0..1
Door 0..1
Post Office Box 0..1
Delivery Point Identifier 0..∞
Plot Identifier 0..1
City Name 0..1
City Sub Division Name 0..∞
Country Sub Division Code 0..∞
Country Code 0..1
Postal Code 0..1
Status 0..1
Preference 0..∞
Geographical Coordinate 0..∞
Usage 0..∞
Extension 1..1
UML Class Model
You can save the file locally and use it, for example, in PowerPoint.
SVG File
@startuml
class BillingAddress {
String TypeCode
CodeList ActionCode
String LanguageCode
String Identifier
String UUID
String SourceIdentifier
String PartyIdentifier
String Name
String AttentionOfName
String CareOfName
String AddressLine
String BuildingNumber
String BuildingName
String BlockName
String StreetName
String StreetTypeCode
String Floor
String Unit
String StairCase
String Door
String PostOfficeBox
String DeliveryPointIdentifier
String PlotIdentifier
String CityName
String CitySubDivisionName
String CountrySubDivisionCode
String CountryCode
String PostalCode
}
class "IdentifierSet"{}
class "RelatedIdentifier"{}
class "Status"{}
class "Preference"{}
class "GeographicalCoordinate"{}
class "Usage"{}
BillingAddress o-d- "0...∞" "IdentifierSet"
BillingAddress o-r- "0...∞" "RelatedIdentifier"
BillingAddress o-u- "0...1" "Status"
BillingAddress o-l- "0...∞" "Preference"
BillingAddress o-d- "0...∞" "GeographicalCoordinate"
BillingAddress o-u- "0...∞" "Usage"
hide circle
@enduml
Where Used
Following is a list of components that have Billing Address as a child component.
- Access Request Party
- Advisor Party
- Analysing Party
- Approved By Party
- 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
- Check From Party
- Child Party
- Cleaned By Party
- Competitor Party
- Concerned Party
- Configuration End User Party
- Contributor Party
- Created By Party
- Created For Party
- Creator Party
- Credit Card
- 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
- Distributor Party
- End User Party
- Final Agent Financial Party
- Final Party
- Financial Party
- Financial Party Reference
- First Agent Party
- Forwarding Agent Party
- Initiating Party
- Inspection Party
- Inspector Party
- Intermediary Financial Party
- Invoicee Party
- Invoicer Party
- Involved Party
- Issuing Party
- Manufacturing Party
- Mark Owner Party
- Operator Party
- Originator Party
- Owner Party
- Parent Party
- Party
- Party Master
- Party Reference
- Pay From Party
- Payee Party
- Payee Party Reference
- Payor Party
- Plan From Party Reference
- Plan To Party Reference
- Port Authority Party
- Procurement Card
- Provider Party
- Publisher Party
- Purchasing Party
- Received By Party
- Recipient Party
- Registrar Party
- Remit To Party
- Requester Party
- Requesting Party Reference
- Responsible Supplier
- Retailer Party
- Reviewer Party
- Route Stop Party
- Sales Party Master
- Sales Party Reference
- Sample Preparer Party
- Screen Party
- Screen Perform By Party
- Service Advisor Party
- Ship From Party
- Ship From Party Reference
- Ship To Party
- Ship To Party Reference
- Shipper Party
- Signatory Party
- Sold To Party
- Sold To Party Reference
- Steward Party
- Submitting Party
- Supplier Party
- Supplier Party Master
- Supplier Party Reference
- Ultimate Recipient Party
- Vendor Party
- Warehouse Party
Feedback
OAGi and its members welcome your feedback.
UUID: a67d92a58bcd4adeb324ce83d60a6f9f
connectSpec (OAGIS) Version 10.12