Get an Operational Location
get
/locations/{locationGid}/operationalLocations/{operationalLocationGid}
Request
Path Parameters
-
locationGid(required): string
Resource ID
-
operationalLocationGid(required): string
Resource ID
Query Parameters
-
expand: string
Comma-delimited string of child resource names that you want to expand so that the contents return with the parent in the same GET request.
-
fields: string
Comma-delimited string of field names that you wanted returned in a GET request.
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/vnd.oracle.resource+json;type=singular
Default Response
Default Response.
Root Schema : schema
Type:
Show Source
object
-
details:
details
-
domainName: string
Database domain where this data is stored.
-
links: array
links
Read Only:
true
-
operationalLocationGid: string
Sub location belonging to a main location. Sub location may only belong to one location.
Nested Schema : details
Type:
Show Source
object
-
items: array
items
-
links: array
links
Read Only:
true
Nested Schema : locations.operationalLocations.details
Type:
Show Source
object
-
domainName: string
Database domain where this data is stored.
-
exclusionRegionGid: string
If set, this operational location is not applicable when the opposite endpoint of the shipment is within the region.
-
inboundOutboundType: string
Indicates whether this operational location for the mapping of the service provider and location profile is used for importing (I), exporting (E), or both (B).
-
inclusionRegionGid: string
If set, this operational location is applicable only when the opposite endpoint of the shipment is within the region.
-
links: array
links
Read Only:
true
-
primaryLegLocProfileGid: string
The location on the main leg which will help indicate which operational location applies; usually Port of Exit or Port of Discharge.
-
primaryLegServprovGid: string
The service provider of the main leg which will help indicate which operational location applies.
-
seqNo: number
(int64)
Sequence to allow multiple data records for the same operational location.