DataArea
Is where the information that the BOD message carries is provided, in this case ListBOM. The information consists of a Verb and one or more Nouns. The verb (List) indicates the action to be performed on the Noun (BOM).
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/ListBOM.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: ListBOMDataAreaType
Properties: Local, Qualified
Content
- Sequence
[1..1]
- List [1..1] In an effort to simpilify the usage of the verbs the List verb is being deprecated as of OAGIS 9.0, the List will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the Show verb which may serve the same function of the List verb has in the past. The purpose of the List verb is to enable a business software component to respond to a GetList request or to proactively send a listing of summary information containing many instances of occurrences of data for a noun to one or more other business software components.The results of a List may then be used as is, or they may be used to select a specific instance of a document or entity in order to issue a detail Get request.Although BODs based on this verb do not commonly cause updates to occur, there may be times when the component receiving the List 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 List verb is quite straight forward with a few exceptions. The List response to any GetList request needs to read the request carefully to ensure the response is returning the requested Data Types. The List needs to ensure the response to the GetList does not exceed the maxItems value.The List needs to find the specific Field Identifiers that are used for the Field-Based Selection or Range-Based Selection and process them accordingly. The attributes associated with the List BODs are as follows: o rsstart attribute is a number that idicates the starting record for the section of the resulting set returned in the list message. This value should always match the rsstart value in the originating GetList BOD. o rscount attribute is a number that indicates the number of records returned in the message. The subsequent request for additional records should have a rsstart value of rscount + 1. o rstotal attribute is a number that indicates the total number of records in the result set. o rscomplete attribute is a Boolean that indicates that the list provided exhaust the possible values. o rsref attribute is a string that represents the implementation-specific result set identifier for subsequent requests.
- BOM [1..*] When included in a hierarchy, the Components are position dependent for their meaning and applicability to the Bill of Material. The Bill of Material structure is broken down into three classifications or ways to represent the Item. An Item may be included by itself as in the first sub-grouping, or an Item may be represented as part of a set of options or as an option within a class of options. An example of an option would be CD-ROM for a laptop computer. Then each of the types of CD-ROM's for the option would be a separate Item. An example of an option class would be memory for a laptop. The options could then be 128, 256, or 512 megabytes of RAM. Each of these options would then have separate Item identifiers for memory modules that makes up the appropriate amount of memory. For 256 megabytes of RAM, this could be two 128 megabyte memory modules or one 256 megabyte.
Attributes
None
Used in
- Type ListBOMType (Element ListBOM)
Sample instance
<DataArea> <List> <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> </List> <BOM> <BOMHeader> <DocumentID>... </DocumentID> <AlternateDocumentID>... </AlternateDocumentID> <LastModificationDateTime>2000-01-01</LastModificationDateTime> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <DocumentReference>... </DocumentReference> <Attachment>... </Attachment> <Status>... </Status> <AlternateBOMReference>... </AlternateBOMReference> <ParentBOMReference>... </ParentBOMReference> <ChildBOMReference>... </ChildBOMReference> <RouteReference>... </RouteReference> <Name>string</Name> <UsageDescription>string</UsageDescription> <Type>normalizedString</Type> <EffectiveTimePeriod>... </EffectiveTimePeriod> <Location>... </Location> <TrackingIndicator>true</TrackingIndicator> <BatchSizeQuantity>1.0</BatchSizeQuantity> <UserArea> <!--any element--> </UserArea> </BOMHeader> <BOMItemData> <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> <Lot>... </Lot> <Type>normalizedString</Type> <EffectiveTimePeriod>... </EffectiveTimePeriod> <ExecutionTimePeriod>... </ExecutionTimePeriod> <FixedQuantityIndicator>true</FixedQuantityIndicator> <MaximumLotSizeQuantity>1.0</MaximumLotSizeQuantity> <MinimumLotSizeQuantity>1.0</MinimumLotSizeQuantity> <LotSizeMultipler>1.0</LotSizeMultipler> <LeadTimeDuration>P1Y2M3DT10H</LeadTimeDuration> <RequiredPercent>1.0</RequiredPercent> <BackFlushedIndicator>true</BackFlushedIndicator> <TrackingIndicator>true</TrackingIndicator> <ScrapIndicator>true</ScrapIndicator> <OperationReference>... </OperationReference> <RouteReference>... </RouteReference> <ParentItemID>... </ParentItemID> <ChildItemID>... </ChildItemID> <UserArea> <!--any element--> </UserArea> </BOMItemData> <BOMOption> <ID>normalizedString</ID> <Name>string</Name> <Description>string</Description> <Note>string</Note> <DefaultIndicator>true</DefaultIndicator> <ExclusiveIndicator>true</ExclusiveIndicator> <BOMItemData>... </BOMItemData> <UserArea> <!--any element--> </UserArea> </BOMOption> <BOMOptionClass> <ID>normalizedString</ID> <Name>string</Name> <ExclusiveIndicator>true</ExclusiveIndicator> <MandatoryIndicator>true</MandatoryIndicator> <Description>string</Description> <Note>string</Note> <BOMOption>... </BOMOption> <UserArea> <!--any element--> </UserArea> </BOMOptionClass> </BOM> </DataArea>