Definition Type: Element
Name: ShowEngineeringChangeOrder
Namespace: http://www.openapplications.org/oagis/9
Type: nsA:ShowEngineeringChangeOrderType
Containing Schema: ShowEngineeringChangeOrder.xsd
Abstract
Documentation:
The purpose of the ShowEngineeringChangeOrder is to communicate to a business application module or system the sending systems representation of a specified Engineering Change Order. This request may be used as a response to a Get request or as a push notification of an event. This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario. There are many possible business applications in several environments that may use this capability. For example, a PDM, MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Engineering Change Document.
Collapse XSD Schema Diagram:
Drilldown into DataArea in schema showengineeringchangeorder_xsd Drilldown into ApplicationArea in schema meta_xsd Drilldown into languageCode in schema meta_xsd Drilldown into systemEnvironmentCode in schema meta_xsd Drilldown into versionID in schema meta_xsd Drilldown into releaseID in schema meta_xsd Drilldown into BusinessObjectDocumentType in schema meta_xsd Drilldown into ShowEngineeringChangeOrderType in schema showengineeringchangeorder_xsdXSD Diagram of ShowEngineeringChangeOrder in schema showengineeringchangeorder_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code:
<xsd:element name="ShowEngineeringChangeOrder" type="ShowEngineeringChangeOrderType">
    <xsd:annotation>
        <xsd:documentation source="http://www.openapplications.org/oagis/9">The purpose of the ShowEngineeringChangeOrder is to communicate to a business application module or system the sending systems representation of a specified Engineering Change Order.  This request may be used as a response to a Get request or as a push notification of an event.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, a PDM, MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Engineering Change Document.
</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
ApplicationArea nsA:ApplicationArea (1) (1)
DataArea nsA:DataArea (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
releaseID nsA:releaseID Required
versionID nsA:versionID Optional
systemEnvironmentCode nsA:systemEnvironmentCode Production Optional
languageCode nsA:languageCode en-US Optional
Collapse Derivation Tree: