DataArea

Is where the information that the BOD message carries is provided, in this case ReceiveLocationService.                                             The information consists of a Verb and one or more Nouns. The verb (Receive) indicates the action to be performed on the Noun (LocationService).

Element information

Content

• Sequence [1..1]
  1. Acknowledge [1..1]    The Acknowledge verb is used to acknowledge the application receipt of a Process request. This function conveys the result of the original request. An example of this is Acknowledge PO, where a Process PO has been issued and the corresponding business application acknowledges the receipt of the PO and responds with an acceptance or a counter offer.
  2. LocationService [1..*]    

Attributes

None

Used in

• Type AcknowledgeLocationServiceType (Element AcknowledgeLocationService)

Sample instance

<DataArea>
   <Acknowledge>
      <OriginalApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime></CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <ScenarioID>normalizedString</ScenarioID>
         <CorrelationID>normalizedString</CorrelationID>
         <BODID>normalizedString</BODID>
         <Extension>.......................................
         </Extension>
      </OriginalApplicationArea>
      <ResponseCriteria>
         <ResponseExpression actionCode="token">token</ResponseExpression>
         <ChangeStatus>...
         </ChangeStatus>
      </ResponseCriteria>
   </Acknowledge>
   <LocationService>
      <ID/>
      <IDSet>
         <ID/>
      </IDSet>
      <Location>
         <ID/>
         <IDSet>...
         </IDSet>
         <Name/>
         <Directions/>
         <Coordinate>...
         </Coordinate>
         <Address>...
         </Address>
         <Contact>...
         </Contact>
         <Communication>...
         </Communication>
         <PostalAddress>...
         </PostalAddress>
         <PhysicalAddress>...
         </PhysicalAddress>
         <Description/>
         <Note/>
         <TimeZoneCode>M0100</TimeZoneCode>
         <AvailableTimePeriod>..................
         </AvailableTimePeriod>
         <LocationEquipmentSpecification>...
         </LocationEquipmentSpecification>
         <EffectiveTimePeriod>..................
         </EffectiveTimePeriod>
         <Extension>.......................................
         </Extension>
      </Location>
      <ResultCode>normalizedString</ResultCode>
      <ProcessedLocation>
         <ID/>
         <IDSet>...
         </IDSet>
         <Name/>
         <Directions/>
         <Coordinate>...
         </Coordinate>
         <Address>...
         </Address>
         <Contact>...
         </Contact>
         <Communication>...
         </Communication>
         <LocationServiceMatchCode>normalizedString</LocationServiceMatchCode>
         <Extension>.......................................
         </Extension>
      </ProcessedLocation>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </LocationService>
</DataArea>