InventoryItemIDs

Provides the identifiers that an instance of inventory is known.

See http://www.openapplications.org/platform/1.

Element information

Content

• Sequence [1..1]
  from type ItemIDsType
  from group ItemIDsGroup
  Sequence [0..1]
  1. ItemID [0..*]    Is the primary item Identifier associated with the given item within the scope of the given integration as provided by the Party or entity that has created this document instance.
  2. CustomerItemID [0..1]    Is the identifier provided by the customer for the item.
  3. ManufacturerItemID [0..1]    Is the identifier provided by Manufacturer for the Item. One example may be the model number.
  4. SupplierItemID [0..1]    Is the identifier provided by the supplier for the item.
  5. UPCID [0..1]    Allows an instance of an item to have a UPC identifier associated.
  6. EPCID [0..1]    Allows an instance of an item to communicate the ElectronicProductCodeID that it was assigned. The ElectronicProductCodeID is one of the major RadioFrequency Identifiers used.
  from type InventoryItemIDsBaseType
  from group ItemInstanceIDsGroup
  Sequence [0..1]
  1. RFID [0..*]    Allows an instance of an item to carry any radio frequency identifier (RFID) that maybe used by a supply chain.
  2. Choice [1..1]
     • SerialNumber [0..*]    Unique serial number assigned to the given item instance by the manufacturer.
     • LotSerial [0..*]    LotSerial is being depricated in favor of SerializedLot as of 9.2 release. This can be used in three ways: specify multiple serial numbers for a given lot, or specify multiple lots without serial numbers, or specify multiple serial numbers without a LotID. Typically, the parent element that uses LotSerial also provides the ability to provide a single lot number and serial number pair, which can be used for the cases where there are no multiple lots or serial numbers involved
  LotIDs [0..1]    Identifies the Lot Identifiers of all of the lots that are contained in the associated set of items.
  1. UserArea [0..1]    Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS.This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document through the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline.

Attributes

None

Used in

• Type RejectionDetailsType (Element RejectionDetails)

Sample instance

<InventoryItemIDs>
   <ItemID>
      <ID>normalizedString</ID>
      <RevisionID>normalizedString</RevisionID>
      <VariationID>normalizedString</VariationID>
   </ItemID>
   <CustomerItemID>
      <ID>normalizedString</ID>
      <RevisionID>normalizedString</RevisionID>
      <VariationID>normalizedString</VariationID>
   </CustomerItemID>
   <ManufacturerItemID>
      <ID>normalizedString</ID>
      <RevisionID>normalizedString</RevisionID>
      <VariationID>normalizedString</VariationID>
   </ManufacturerItemID>
   <SupplierItemID>
      <ID>normalizedString</ID>
      <RevisionID>normalizedString</RevisionID>
      <VariationID>normalizedString</VariationID>
   </SupplierItemID>
   <UPCID>normalizedString</UPCID>
   <EPCID>normalizedString</EPCID>
   <RFID>normalizedString</RFID>
   <SerialNumber>normalizedString</SerialNumber>
   <LotIDs>
      <ID>normalizedString</ID>
   </LotIDs>
   <UserArea>
      <!--any element-->
   </UserArea>
</InventoryItemIDs>