DataArea
Is where the information that the BOD message carries is provided, in this case AcknowledgeProductAvailability. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ProductAvailability).
See http://www.openapplications.org/oagis/9.
Element information
Namespace: http://www.openapplications.org/oagis/9
Schema document: org_openapplications_oagis/9_4_1/Developer/BODs/AcknowledgeProductAvailability.xsd
Other elements with the same name: DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea
Type: AcknowledgeProductAvailabilityDataAreaType
Properties: Local, Qualified
Content
- Sequence
[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.
- ProductAvailability [1..*] Product Availability represents information on the availability of a specified item at a specified inventory location for a specified date. Product availability is typically needed in the processing of customer sales orders. It is used in this context as the object of an inquiry function. Where the ItemQuantity indicates the number of Iterms requested and the AvailableQuantity indicates the number of items available.
Attributes
None
Used in
- Type AcknowledgeProductAvailabilityType (Element AcknowledgeProductAvailability)
Sample instance
<DataArea> <Acknowledge> <OriginalApplicationArea> <Sender>... </Sender> <Receiver>... </Receiver> <CreationDateTime>2000-01-01</CreationDateTime> <Signature> <!--any element--> </Signature> <BODID>normalizedString</BODID> <UserArea> <!--any element--> </UserArea> </OriginalApplicationArea> <ResponseCriteria> <ResponseExpression actionCode="Accepted">token</ResponseExpression> <ChangeStatus>... </ChangeStatus> </ResponseCriteria> </Acknowledge> <ProductAvailability> <DocumentID> <ID>normalizedString</ID> <RevisionID>normalizedString</RevisionID> <VariationID>normalizedString</VariationID> </DocumentID> <AlternateDocumentID> <ID>normalizedString</ID> <RevisionID>normalizedString</RevisionID> <VariationID>normalizedString</VariationID> </AlternateDocumentID> <LastModificationDateTime>2000-01-01</LastModificationDateTime> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <DocumentReference> <DocumentID>... </DocumentID> <AlternateDocumentID>... </AlternateDocumentID> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <StatusCode>normalizedString</StatusCode> <Status>... </Status> <LineNumber>normalizedString</LineNumber> <ItemIDs>... </ItemIDs> <Facility>... </Facility> <SerializedLot>... </SerializedLot> <SalesOrderReference>... </SalesOrderReference> <PurchaseOrderReference>... </PurchaseOrderReference> <GroupName>string</GroupName> <SequenceCode>normalizedString</SequenceCode> <StepID>normalizedString</StepID> <StepType>normalizedString</StepType> <IssuingParty>... </IssuingParty> <OperationReference>... </OperationReference> <ReleaseNumber>normalizedString</ReleaseNumber> <ScheduleLineNumber>normalizedString</ScheduleLineNumber> <SubLineNumber>normalizedString</SubLineNumber> <ShipUnitReference>... </ShipUnitReference> <EffectiveTimePeriod>... </EffectiveTimePeriod> <Item>... </Item> <ID>normalizedString</ID> <SealID>normalizedString</SealID> <Type>normalizedString</Type> <FreightItemID>normalizedString</FreightItemID> <ShippingTrackingID>normalizedString</ShippingTrackingID> <Quantity>1.0</Quantity> <UserArea> <!--any element--> </UserArea> </DocumentReference> <Attachment> <EmbeddedData mimeCode="normalizedString">GpM7</EmbeddedData> <URI>http://www.example.com/</URI> <ISBN>normalizedString</ISBN> <FileName>string</FileName> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <FileType>normalizedString</FileType> <FileSizeQuantity>1.0</FileSizeQuantity> <Title>string</Title> <UserArea> <!--any element--> </UserArea> </Attachment> <Item> <ItemID>... </ItemID> <CustomerItemID>... </CustomerItemID> <ManufacturerItemID>... </ManufacturerItemID> <SupplierItemID>... </SupplierItemID> <UPCID>normalizedString</UPCID> <EPCID>normalizedString</EPCID> <ServiceIndicator>true</ServiceIndicator> <Description>string</Description> <Note>string</Note> <Classification>... </Classification> <Specification>... </Specification> <HazardousMaterial>... </HazardousMaterial> <Packaging>... </Packaging> <CountryOfOriginCode>normalizedString</CountryOfOriginCode> <RFID>normalizedString</RFID> <SerialNumber>normalizedString</SerialNumber> <Lot>... </Lot> <UserArea> <!--any element--> </UserArea> </Item> <SerialNumber>normalizedString</SerialNumber> <SerializedLot> <ItemQuantity>1.0</ItemQuantity> <Lot>... </Lot> <Disposition>... </Disposition> <SerialNumber>normalizedString</SerialNumber> <ParentSerialNumber>normalizedString</ParentSerialNumber> <Description>string</Description> <Note>string</Note> <UserArea> <!--any element--> </UserArea> </SerializedLot> <UID>normalizedString</UID> <RFID>normalizedString</RFID> <Quantity>1.0</Quantity> <GLEntityID>normalizedString</GLEntityID> <Facility> <IDs>... </IDs> <Name>string</Name> <Description>string</Description> <Note>string</Note> <Address>... </Address> <Coordinate>... </Coordinate> <UserArea> <!--any element--> </UserArea> </Facility> <Status> <Code>normalizedString</Code> <Description>string</Description> <EffectiveDateTime>2000-01-01</EffectiveDateTime> <ReasonCode>normalizedString</ReasonCode> <Reason>string</Reason> <TimePeriod>... </TimePeriod> <UserArea> <!--any element--> </UserArea> </Status> <ReasonCode>normalizedString</ReasonCode> <TransactionDateTime>2000-01-01</TransactionDateTime> <ProductLineClassification> <Codes> </Codes> <Description>string</Description> <Note>string</Note> <UserArea> <!--any element--> </UserArea> </ProductLineClassification> <RequiredQuantity>1.0</RequiredQuantity> <RequiredDateTime>2000-01-01</RequiredDateTime> <PurchaseOrderReference> <DocumentID>... </DocumentID> <AlternateDocumentID>... </AlternateDocumentID> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <StatusCode>normalizedString</StatusCode> <Status>... </Status> <ReleaseNumber>normalizedString</ReleaseNumber> <LineNumber>normalizedString</LineNumber> <ScheduleLineNumber>normalizedString</ScheduleLineNumber> <SubLineNumber>normalizedString</SubLineNumber> <UserArea> <!--any element--> </UserArea> </PurchaseOrderReference> <SalesOrderReference> <DocumentID>... </DocumentID> <AlternateDocumentID>... </AlternateDocumentID> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <StatusCode>normalizedString</StatusCode> <Status>... </Status> <ReleaseNumber>normalizedString</ReleaseNumber> <LineNumber>normalizedString</LineNumber> <ScheduleLineNumber>normalizedString</ScheduleLineNumber> <SubLineNumber>normalizedString</SubLineNumber> <UserArea> <!--any element--> </UserArea> </SalesOrderReference> <ProductionOrderReference> <DocumentID>... </DocumentID> <AlternateDocumentID>... </AlternateDocumentID> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <StatusCode>normalizedString</StatusCode> <Status>... </Status> <LineNumber>normalizedString</LineNumber> <ItemIDs>... </ItemIDs> <Facility>... </Facility> <SerializedLot>... </SerializedLot> <SalesOrderReference>... </SalesOrderReference> <PurchaseOrderReference>... </PurchaseOrderReference> <UserArea> <!--any element--> </UserArea> </ProductionOrderReference> <AvailableQuantity>1.0</AvailableQuantity> <AvailableDateTime>2000-01-01</AvailableDateTime> <AllowSubstitutionIndicator>true</AllowSubstitutionIndicator> <SubstituteItem> <ItemID>... </ItemID> <CustomerItemID>... </CustomerItemID> <ManufacturerItemID>... </ManufacturerItemID> <SupplierItemID>... </SupplierItemID> <UPCID>normalizedString</UPCID> <EPCID>normalizedString</EPCID> <ServiceIndicator>true</ServiceIndicator> <Description>string</Description> <Note>string</Note> <Classification>... </Classification> <Specification>... </Specification> <HazardousMaterial>... </HazardousMaterial> <Packaging>... </Packaging> <UID>normalizedString</UID> <RFID>normalizedString</RFID> <SerialNumber>normalizedString</SerialNumber> <ReferenceDesignatorID>normalizedString</ReferenceDesignatorID> <FindNumber>normalizedString</FindNumber> <LotSerial>... </LotSerial> <SerializedLot>... </SerializedLot> <Quantity>1.0</Quantity> <UserArea> <!--any element--> </UserArea> </SubstituteItem> <UserArea> <!--any element--> </UserArea> </ProductAvailability> </DataArea>