Geography Overview
Geography Overview
Geography is something related to details about geographical areas around the world, including countries, cities and specific sites where Maersk operates. Geography is all about the details of the whole hierarchy that how each entity (continent, country, state etc) is being created, updated, searched and stored through the Maersk portal.
Geography hierarchy
Portal
Continent
Continent is the highest level of hierarchy.
Search you can search a continent from the below mentioned fields:
· Name
· GeoID
· Name+GeoID
· Code
· Name+GeoID+Code
· Code+CodeType (CodeType alone not valid)
· Name+GeoID+Code+CodeType
· Status
· Name+GeoID+Code+CodeType+status
Create
minimum requirement to create a continent is:
· Name
· Continent Code
Valid from, valid To, Statusàactive is autofilled and GeoID is autoassigned.
Rest you can also add description, workaround reason, alternate names, LNS GeoID, LNS Code.
Update
atleast one thing from the below fields need to be updated for updating the continent.
· Name
· Description
· WorkaroundReason
· Alternate Names
Country
Country is the 2nd highest level of hierarchy.
Search
you can search a country from the below mentioned fields:
· Name
· GeoID
· Name+GeoID
· Code
· Name+GeoID+Code
· Code+CodeType (CodeType alone not valid)
· Name+GeoID+Code+CodeType
· Parent name
· Name+GeoID+Code+CodeType+parent name+status
· Status
· Name+GeoID+Code+CodeType+status
Create
minimum requirement to create a country is:
· Name
· TimeZone
· Dialing Code
· Parent details
· RKTS Code
· RKTS Code
· Restricted(yes/no)
Valid from, valid To, Statusàactive is autofilled and GeoID, CW1, CW1F is autoassigned.
Note- if validTo Date becomes today’s date so entity will become automatically inactive.
Rest you can also add description, workaround reason, PostalCodeFlag, State/province, DayLightSavingTime, DialingCodeDescription, alternate names, LNS GeoID, LNS Code, FIPS, HSUD CODE, HSUD Number, INLC, MEPC, RKTS, BDA.
State
State is the 3rd highest level of hierarchy.
Search
Minimum requirements:
Name/GeoID/ Code/ParentName/Timezone
Search fields:
· Name
· GeoID
· Name+GeoID
· Code
· Name+GeoID+Code
· Code+CodeType (CodeType alone not valid)
· Name+GeoID+Code+CodeType
· Parent name
· Name+GeoID+Code+CodeType+parent name
· TimeZone
· Name+GeoID+Code+CodeType+parent name+TimeZone
· Status
· Name+GeoID+Code+CodeType+parent name+TimeZone+status
Create
minimum requirement to create a state is:
· Name
· TimeZone
· Parent details
· State/province Code
· ISO Territory
Valid from, valid To, Statusàactive is autofilled and GeoID is autoassigned.
Rest you can also add description, workaround reason, DayLightSavingTime, alternate names, LNS GeoID, LNS Code, FIPS, HSUD CODE, HSUD Number, INLC, MEPC, ISO Territory, LNS State, LNS ProvinceRKTS, BDA.
City
City is the 4th highest level of hierarchy.
Search
Minimum requirements:
Name/GeoID/ Code/ParentName/Timezone
Search fields:
· Name
· GeoID
· Name+GeoID
· Code
· Name+GeoID+Code
· Code+CodeType (CodeType alone not valid)
· Name+GeoID+Code+CodeType
· Parent name
· Name+GeoID+Code+CodeType+parent name
· ParentType+ParentName (parentType alone not valid)
· Name+GeoID+Code+CodeType+parent name+parent type
· TimeZone
· Name+GeoID+Code+CodeType+parent name+TimeZone
· Status
· Name+GeoID+Code+CodeType+parent name+TimeZone+status
Create
minimum requirements to create a city
· Name
· OlsonTimeZone
· TimeZone
· Latitude
· Longitude
· Parent details
· RKST Code
· BDA must have one active pool
Valid from, valid To, Status, PortFlag, Is Maersk Cityàactive is autofilled and GeoID is autoassigned.
Rest you can also add description, workaround reason, DayLightSavingTime, HSUD Name, alternate names, LNS GeoID, LNS Code, FIPS, HSUD CODE, HSUD Number, INLC, MEPC, ISO Territory, LNS State, LNS ProvinceRKTS, BDA.
Postal Code
POSTALCODE is the lowest level of hierarchy.
Search
Minimum requirements:
Name/Code/GeoID/ParentName
Search fields:
· Name
· GeoID
· Name+GeoID
· Code
· Name+GeoID+Code
· Parent name
· Name+GeoID+Code+parent name
· Status
· Name+GeoID+Code +parent name +status
Create Minimum requirements to create a postal code
· Name
· Parent details
· Postal Code
Valid from, valid To, Status is autofilled and GeoID is autoassigned.
Rest you can also add description and bda also.
BDA Type
Search fields
- BDA Group Type
- Code
- BDA Group Type+Code
- Name
- BDA Group Type+Code+Name
- Owner
- BDA Group Type+Code+Name+Owner
- Content Type
- BDA Group Type+Code+Name+Owner+Content Type
Create
Minimum requirements to create a BDA Type:
· Name
· Code
· Owner
· BDA Group Type
· Content Type
Valid from, valid To is autofilled in Content Type
BDA
Search fields
- Name
- GeoID
- Name+GeoID
- Code
- Name+GeoID+Code
- CodeType+Code
- Name+GeoID+Code+CodeType
- BDAType
- Name+GeoID+Code+CodeType+BDAType
- Status
- Name+GeoID+Code+CodeType+BDAType+Status
Create
Minimum requirements to create a BDA Type:
· Name
· BDA Type
· BDA Code
Valid from, valid To, Status is autofilled and GeoID is autoassigned.
Rest you can also add Locations and Parent BDA also.
TimeZone
Search feilds
· Name
· Code
· UTC Offset Mins
Create Minimum requirements to create a TimeZone:
· Name
· Code
· UTC Offset Mins
Rest you can also add Description also.
DaylightSaving Time
Search Fields
· Code
· Name
Create
Minimum requirements to create a DaylightSaving Time:
· Code
· Name
· Start Time
· End Time
· Standard Time Difference
Rest you can also add description, year and DST Displacements description.
Important points for different types of codes: RKST
· 2 characters for country
· 5 characters for city
· 7 characters for facility
Codes need to be unique- Codes can be same across all geography entities but code type should be unique.
(Values for different codes can be same for example continent code and LNS Code can have same value, but no two values of same codes can be same for example no two continents can have same Continent code.)
Data Model for Geography
ER Diagram of V1
ER Diagram explanation & table connectivity
V1
ER Diagram simplified explanation for yellow box connections
ER Diagram simplified explanation for green box connections
Tables:
· entity_type: Stores entity name and type. We made this so that for the purposes where we just require to store the entity name and its types, we don’t need to link the complete entity details.
· parent_rel: Stores the parent child relationship for all entities by linking to entity_type but here the linkage is twice one for parent and other for child. In this way work of all 7 entities in hierarchy is done in one.
· idl: IDL is incremental data load, which we do whenever we move/migrate application. it does not happen frequently. When we integrate with any MnA/merge applications/move current infra to new infra we capture this information.
· History tables: stores what all changes done to which entity and at what time & date.
Flow Chart of geography overview:
Flow Chart for code of continent creation:
Flow Chart for code of country creation:
Flow Chart for code of state creation: