Definition Type: Element
Name: SyncLocation
Namespace: http://www.openapplications.org/oagis/9
Type: nsA:SyncLocationType
Containing Schema: SyncLocation.xsd
Abstract
Documentation:
The purpose of the Sync Location is to enable a mechanism to ensure that the physical location identifiers are synchronized between the business applications that require this to communicate clearly. This is particularly critical when only the codes that identify locations are used. Without the meaning of the codes clearly communicated, the integration is not effective. This BOD enables the Location codes to be synchronized among business applications. This BOD may also be initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example, a MRP, Inventory, or Manufacturing business application could use this to communicate Location information.
Collapse XSD Schema Diagram:
Drilldown into DataArea in schema synclocation_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 SyncLocationType in schema synclocation_xsdXSD Diagram of SyncLocation in schema synclocation_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code:
<xsd:element name="SyncLocation" type="SyncLocationType">
    <xsd:annotation>
        <xsd:documentation source="http://www.openapplications.org/oagis/9">The purpose of the Sync Location is to enable a mechanism to ensure that the physical location identifiers are synchronized between the business applications that require this to communicate clearly.  This is particularly critical when only the codes that identify locations are used.  Without the meaning of the codes clearly communicated, the integration is not effective.  This BOD enables the Location codes to be synchronized among business applications.

This BOD may also be initiated by the sending system upon some event occurring.

There are many possible business applications in several environments that may use this capability. For example, a MRP, Inventory, or Manufacturing business application could use this to communicate Location information.
</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: