DataArea

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

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. 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 AcknowledgeSequenceScheduleType (Element AcknowledgeSequenceSchedule)

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>
   <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>