Documentation for Open Applications Group (OAGIS)
Definition Type: ComplexType
Name: ProductionOrderDocumentReference
Namespace: http://www.openapplications.org/oagis
Type: oa:DocumentReference
Containing Schema: MfgComponents.xsd
Abstract
Collapse XSD Schema Diagram:
Drilldown into UserArea in schema meta_xsd Drilldown into LotSerial in schema components_xsd Drilldown into Site in schema components_xsd Drilldown into ItemId in schema mfgcomponents_xsd Drilldown into LineNumber in schema mfgcomponents_xsd Drilldown into Note in schema components_xsd Drilldown into Usage in schema components_xsd Drilldown into Status in schema components_xsd Drilldown into Name in schema components_xsd Drilldown into Description in schema components_xsd Drilldown into CommonReference in schema components_xsd Drilldown into SuffixId in schema mfgcomponents_xsd Drilldown into DocumentDate in schema mfgcomponents_xsd Drilldown into DocumentId in schema mfgcomponents_xsd Drilldown into DocumentReference in schema components_xsdXSD Diagram of ProductionOrderDocumentReference in schema mfgcomponents_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code: 
<xs:complexType name="ProductionOrderDocumentReference">
    <xs:complexContent>
        <xs:extension base="DocumentReference">
            <xs:sequence>
                <xs:element name="DocumentId" type="PartyProductionOrderIdType" minOccurs="0" />
                <xs:element name="DocumentDate" type="DateTimeAny" minOccurs="0">
                    <xs:annotation>
                        <xs:documentation source="http://www.openapplications.org/oagis">The Datetime of the referenced document.</xs:documentation>
                    </xs:annotation>
                </xs:element>
                <xs:element name="SuffixId" type="Id" minOccurs="0">
                    <xs:annotation>
                        <xs:documentation source="http://www.openapplications.org/oagis">This identifies a sub-component of the Production Order, Job Order, or Work Order, etc. being performed. The sub-component may have been split from the original Order. For Example:An order for 30 widgets, where 20 can be billed as "completed" and the remaining 10 can be moved to a sub-component of the same Order to be finished and billed for at a later time.  The sub-component may identify one of many sub-components (each an Order in its own right) that may make up a "master" Order. Kind of a parent/child relationship related collection</xs:documentation>
                    </xs:annotation>
                </xs:element>
                <xs:group ref="CommonReference" minOccurs="0" />
                <xs:element name="LineNumber" type="LineNumber" minOccurs="0" />
                <xs:element name="ItemId" type="PartyAssignedItemId" minOccurs="0" />
                <xs:element ref="Site" minOccurs="0" maxOccurs="unbounded" />
                <xs:element ref="LotSerial" minOccurs="0" />
                <xs:element ref="UserArea" minOccurs="0" />
            </xs:sequence>
        </xs:extension>
    </xs:complexContent>
</xs:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
DocumentId oa:DocumentId 0 (1)
DocumentDate oa:DocumentDate 0 (1)
SuffixId oa:SuffixId 0 (1)
Description oa:Description 0 unbounded
Name oa:Name 0 unbounded
Status oa:Status 0 (1)
Usage oa:Usage 0 (1)
Note oa:Note 0 unbounded
LineNumber oa:LineNumber 0 (1)
ItemId oa:ItemId 0 (1)
Site oa:Site 0 unbounded
LotSerial oa:LotSerial 0 (1)
UserArea oa:UserArea 0 (1)
<xs:group> oa:CommonReference 0 (1)
Collapse Derivation Tree:
Collapse References:
oa:ProductionOrderReference
Documentation for Open Applications Group (OAGIS)

Generated using Liquid Studio - Developer Bundle 21.0.0.0