Definition Type: Element
Name: GetLocationService
Namespace: http://www.openapplications.org/oagis/9
Type: nsA:GetLocationServiceType
Containing Schema: GetLocationService.xsd
Abstract
Documentation:
The purpose of RequestLocationService is to enable a mechanism to ensure that the physical locations owned by the business applications are validated, geocoded, and standardized based on information returned by location service providers. This BOD may be initiated by the sending system upon some event occurring, such as receiving a request submitted by another system for certain location service. There are many possible business applications in several environments that may use this capability. For example, the customer management, the supplier management, or HRMS business applications could use this to receive processed location information from location service providers.
Collapse XSD Schema Diagram:
Drilldown into DataArea in schema getlocationservice_xsd Drilldown into ApplicationArea in schema meta_xsd Drilldown into languageCode in schema meta_xsd Drilldown into systemEnvironmentCode in schema meta_xsd Drilldown into versionID in schema meta_xsd Drilldown into releaseID in schema meta_xsd Drilldown into BusinessObjectDocumentType in schema meta_xsd Drilldown into GetLocationServiceType in schema getlocationservice_xsdXSD Diagram of GetLocationService in schema getlocationservice_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code:
<xsd:element name="GetLocationService" type="GetLocationServiceType">
    <xsd:annotation>
        <xsd:documentation source="http://www.openapplications.org/oagis">The purpose of  RequestLocationService is to enable a mechanism to ensure that the physical locations owned by the business applications are validated, geocoded, and standardized based on information returned by location service providers.

This BOD may be initiated by the sending system upon some event occurring, such as receiving a request submitted by another system for certain location service.

There are many possible business applications in several environments that may use this capability. For example, the customer management, the supplier management, or HRMS business applications could use this to receive processed location information from location service providers.</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
ApplicationArea nsA:ApplicationArea (1) (1)
DataArea nsA:DataArea (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
releaseID nsA:releaseID Required
versionID nsA:versionID Optional
systemEnvironmentCode nsA:systemEnvironmentCode Production Optional
languageCode nsA:languageCode en-US Optional
Collapse Derivation Tree: