DataArea

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

Element information

Content

• Sequence [1..1]
  1. Sync [1..1]    The Sync verb is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncBOD does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture.The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input.
  2. ProductionSchedule [1..*]    ProductionSchedule is generally used in the Process Manufacturing Industries to schedule a Production run or multiple production runs.

Attributes

None

Used in

• Type SyncProductionScheduleType (Element SyncProductionSchedule)

Sample instance

<DataArea>
   <Sync>
      <ActionCriteria>
         <ActionExpression actionCode="token">token</ActionExpression>
         <ChangeStatus>...
         </ChangeStatus>
      </ActionCriteria>
   </Sync>
   <ProductionSchedule>
      <ID/>
      <IDSet>
         <ID/>
      </IDSet>
      <Description/>
      <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>
      <DocumentDateTime></DocumentDateTime>
      <ReportTimePeriod>
         <InclusiveIndicator>true</InclusiveIndicator>
         <StartDateTime></StartDateTime>
         <StartTime>token</StartTime>
         <Duration>P1Y2M3DT10H</Duration>
         <EndDateTime></EndDateTime>
         <EndTime>token</EndTime>
      </ReportTimePeriod>
      <EquipmentElementLevel/>
      <ScheduleStateCode>normalizedString</ScheduleStateCode>
      <ProductionRequest>
         <ID/>
         <IDSet>...
         </IDSet>
         <Description/>
         <ProductProductionRuleID>normalizedString</ProductProductionRuleID>
         <Location>...
         </Location>
         <ReportTimePeriod>..................
         </ReportTimePeriod>
         <PriorityCode>normalizedString</PriorityCode>
         <SegmentRequirement>...
         </SegmentRequirement>
         <SegmentResponse>...
         </SegmentResponse>
         <RequestStateCode>normalizedString</RequestStateCode>
         <RequiredByRequestedSegmentResponseCode>normalizedString</RequiredByRequestedSegmentResponseCode>
         <Extension>.......................................
         </Extension>
      </ProductionRequest>
      <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>
   </ProductionSchedule>
</DataArea>