ItemStatus

Indicates whether an item is active, inactive, or in other various states.  Examples of values for this field include:	Active, Inactive, Hold, Deleted, Obsolete

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

Element information

Content

• Sequence [1..1]
  from type StatusBasisType
  Code [0..1]    Element for the communication of all codes.
  Description [0..1]    
  EffectiveDateTime [0..1]    This is the DateTime the associated object is made effective
  ReasonCode [0..1]    Identifies the reason for an activity
  Reason [0..*]    
  from type StatusABIEType
  TimePeriod [0..1]    An explicit period of time for the bucket.
  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 ItemDetailsBaseType
• Type ItemHeaderType via extension of ItemDetailsBaseType (Element ItemMasterHeader)
• Type ItemLocationType via extension of ItemDetailsBaseType (Element ItemLocation)

Sample instance

<ItemStatus>
   <Code>normalizedString</Code>
   <Description>string</Description>
   <EffectiveDateTime>2000-01-01</EffectiveDateTime>
   <ReasonCode>normalizedString</ReasonCode>
   <Reason>string</Reason>
   <TimePeriod>
      <InclusiveIndicator>true</InclusiveIndicator>
      <StartDateTime>2000-01-01</StartDateTime>
      <Duration>P1Y2M3DT10H</Duration>
   </TimePeriod>
   <UserArea>
      <!--any element-->
   </UserArea>
</ItemStatus>