Schema Central > OAGIS® 10 > SyncEngineeringChangeOrder.xsd > SyncEngineeringChangeOrder
Advanced search
Need XML Help?

Recommended Reading:

Definitive XML Schema

 

Web Service Contract Design and Versioning for SOA

 

Advanced XML Applications

 

SyncEngineeringChangeOrder

The purpose of the SyncEngineeringChangeOrder is to communicate to a business application module or system the need to initiate the creation of an Engineering Change Document.

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.

Element information

Type: SyncEngineeringChangeOrderType

Properties: Global, Qualified, ID: oagis-id-2080056e9da64474b09120ee55064b8e

Content

Attributes

NameOccTypeDescriptionNotes
releaseID [1..1]NormalizedStringTypeOAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on.from type BusinessObjectDocumentType
versionID [0..1]NormalizedStringTypeIndicates the version of the given BOD definition.from type BusinessObjectDocumentType
systemEnvironmentCode [0..1]SystemEnvironmentCodeContentTypeIndicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s).Default value is "Production". from type BusinessObjectDocumentType
languageCode [0..1]LanguageCodeContentTypeIndicates the language that the contents of the BOD is in unless otherwise stated.Default value is "en-US". from type BusinessObjectDocumentType

Sample instance

<SyncEngineeringChangeOrder releaseID="normalizedString">
   <ApplicationArea>
      <Sender>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <TaskID>normalizedString</TaskID>
         <ReferenceID>normalizedString</ReferenceID>
         <ConfirmationCodes>...
         </ConfirmationCodes>
         <AuthorizationID>normalizedString</AuthorizationID>
      </Sender>
      <Receiver>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <ID/>
      </Receiver>
      <CreationDateTime></CreationDateTime>
      <Signature>
         <!--any element-->
      </Signature>
      <ScenarioID>normalizedString</ScenarioID>
      <CorrelationID>normalizedString</CorrelationID>
      <BODID>normalizedString</BODID>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </ApplicationArea>
   <DataArea>
      <Sync>
         <ActionCriteria>...
         </ActionCriteria>
      </Sync>
      <EngineeringChangeOrder>
         <EngineeringChangeHeader>...
         </EngineeringChangeHeader>
         <EngineeringChangeDetail>...
         </EngineeringChangeDetail>
         <Extension>.......................................
         </Extension>
      </EngineeringChangeOrder>
   </DataArea>
</SyncEngineeringChangeOrder>

Site developed and hosted by Datypic, Inc.

Please report errors or comments about this site to contrib@functx.com