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

Recommended Reading:

Definitive XML Schema

 

Web Service Contract Design and Versioning for SOA

 

Advanced XML Applications

 

ChangeSalesOrder

The purpose of the Change SalesOrder is to request that another business application component make changes to an existing Sales Order.

Processing Note:  This change must refer to the original document and/or item ordered.  The change processing assumes replacement of fields sent, with the exception of the fields that uniquely identify the document and/or its line, schedule or subline. These include the DocumentId and the LineNumber for the Line, Subline, and Schedule.

If any of the Field Identifiers above require changing, that constitutes a cancellation of the request and/or the addition of another Sales Order.

This BOD commonly causes updates to occur

Element information

Type: ChangeSalesOrderType

Properties: Global, Qualified, ID: oagis-id-c2ac6fd7e4284f44a07122d55ce589b0

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

<ChangeSalesOrder 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>
      <Change>
         <ActionCriteria>...
         </ActionCriteria>
      </Change>
      <SalesOrder>
         <SalesOrderHeader>...
         </SalesOrderHeader>
         <SalesOrderLine>...
         </SalesOrderLine>
      </SalesOrder>
   </DataArea>
</ChangeSalesOrder>

Site developed and hosted by Datypic, Inc.

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