DataArea

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

Element information

Content

• Sequence [1..1]
  1. Process [1..1]    The Process verb is used to request processing of the associated noun by the receiving application or business to party. In a typical external exchange scenario a Process BOD is considered to be a legally binding message. For example, if a customer sends a ProcessPurchaseOrder BOD to a supplier and the supplier acknowlegdes with a positive AcknowledgePurchaseOrder, then the customer is obligated to fullfil the agreement, unless of course other BODs are allowed to cancel or change the original order.
  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 ProcessProductionScheduleType (Element ProcessProductionSchedule)

Sample instance

<DataArea>
   <Process>
      <ActionCriteria>
         <ActionExpression actionCode="token">token</ActionExpression>
         <ChangeStatus>...
         </ChangeStatus>
      </ActionCriteria>
   </Process>
   <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>