DataArea

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

Element information

Content

• Sequence [1..1]
  1. Show [1..1]    The Show verb is used when sending the information about a specific instance of a business document or entity. The Show verb may be used to respond to a Get request or it can be used in a publish scenario, where it pushes information to other applications based on a business event.Although BODs based on this verb do not commonly cause updates to occur, there may be times when the component receiving the Show decides to use the information it receives to update. This is entirely the decision of the receiving software component and is not forbidden.The behavior of the Show verb is quite straight forward with one exception. The Show response to any Get request needs to read the request carefully to ensure the response is returning the requested Data Types.
  2. SequenceSchedule [1..*]    A Sequence Schedule is used to indicate sequencial scheduling of ordered items in the manufacturing process. Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application.

Attributes

None

Used in

• Type ShowSequenceScheduleType (Element ShowSequenceSchedule)

Sample instance

<DataArea>
   <Show>
      <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>
   </Show>
   <SequenceSchedule>
      <SequenceScheduleHeader>
         <ID/>
         <RevisionID>normalizedString</RevisionID>
         <VariationID>normalizedString</VariationID>
         <DocumentIDSet>...
         </DocumentIDSet>
         <LastModificationDateTime></LastModificationDateTime>
         <DocumentDateTime></DocumentDateTime>
         <Description/>
         <Note/>
         <DocumentReference>...
         </DocumentReference>
         <Attachment>...
         </Attachment>
         <Status>...
         </Status>
         <RespondingScheduleReference>...
         </RespondingScheduleReference>
         <EffectiveTimePeriod>..................
         </EffectiveTimePeriod>
         <DateCode>normalizedString</DateCode>
         <ScheduleTypeCode>normalizedString</ScheduleTypeCode>
         <Party>...
         </Party>
         <ShipToParty>...
         </ShipToParty>
         <SoldToParty>...
         </SoldToParty>
         <BillToParty>...
         </BillToParty>
         <ShipFromParty>...
         </ShipFromParty>
         <SupplierParty>...
         </SupplierParty>
         <Extension>.......................................
         </Extension>
      </SequenceScheduleHeader>
      <SequenceScheduleEvent>
         <LineNumberID/>
         <LineIDSet>...
         </LineIDSet>
         <Description/>
         <Note/>
         <DocumentReference>...
         </DocumentReference>
         <Attachment>...
         </Attachment>
         <RequiredDateTime></RequiredDateTime>
         <BeginSequenceCodes>...
         </BeginSequenceCodes>
         <EndSequenceCode>normalizedString</EndSequenceCode>
         <SequenceScheduleLine>...
         </SequenceScheduleLine>
         <Extension>.......................................
         </Extension>
      </SequenceScheduleEvent>
   </SequenceSchedule>
</DataArea>