OAGIS9BODs

Element information

Content

• Sequence [1..1]
  1. AcknowledgeAllocateResource [1..1]    The AcknowledgeAllocateResource may be used to obtain limited information Acknowledgeing about documents that match certain selection criteria in a GetAcknowledgeAllocateResource. Additional information about a specific AllocateResource may be obtained through ShowAllocateResource by using the Acknowledgeing information to populate a GetAllocateResource request.
  2. AcknowledgeConfirmWIP [1..1]    The purpose of the AcknowledgeConfirmWIP is to respond to a request for the data necessary to perform a confirmation of the movement of WIP (Work in Progress).
  3. AcknowledgeCostingActivity [1..1]    In an effort to simpilify the usage of the verbs the AcknowledgeCostingActivity BOD is being deprecated as of OAGIS 9.0, the AcknowledgeCostingActivity will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the PostCostingActivity BOD which may serve the same function of the AcknowledgeCostingActivity BOD. The purpose of the AcknowledgeCostingActivity BOD is to enable the update of Activityinformation from a production or manufacturing application to a costing application. This is necessary for applications that are based on a Dual Cycle Accounting model. This Dual Cycle Accounting model does not capture the details of the Activities that caused entries to be made in the general ledger application, but instead captures them in a separate overall costing application. This BOD commonly causes updates to occur and may be used as part of a large integration scenario or as a single tool for updating data. For Single Cycle accounting systems, the PostJournalEntry BOD will be used to ensure that the costing information flows from the Manufacturing Application to the Financial Application. In most cases either PostJournal or AcknowledgeActivity will be used when the Financial applications are included with Logistics, but both Business Service Requests will not be used in the same integration scenario.
  4. AcknowledgeCredit [1..1]    The purpose of the AcknowledgeCredit is for the order management application to request credit data for a trading partner from the credit management function. The AcknowledgeCredit does not imply any update, it is only an inquiry function. The ShowCredit discussed in the next chapter will be the response back to the order management application. Discussed in a later chapter is the UpdateCredit. The UpdateCredit may be used in both directions between the order management and the accounts receivable application. Its purpose is to keep order, shipment and open item amounts current. Finally, the ChangeCreditStatus is used to update the order management application with any changes in business status for a particular trading partner.
  5. AcknowledgeCreditStatus [1..1]    The purpose of the AcknowledgeCreditStatus Business Object Document is to acknowledge receipt of the CreditStatus
  6. AcknowledgeCreditTransfer [1..1]    The purpose of the AcknowledgeCreditTransfer is to enable an application to request specific CreditTransfer information from another business application module. The response to the AcknowledgeCreditTransfer is the AcknowledgeCreditTransfer.
  7. AcknowledgeCreditTransferIST [1..1]    The purpose of the AcknowledgeCreditTransferIST is to enable an application to request specific CreditTransferIST information from another business application module. The response to the AcknowledgeCreditTransferIST is the AcknowledgeCreditTransferIST.
  8. AcknowledgeDebitTransfer [1..1]    The purpose of the AcknowledgeDebitTransfer is to enable an application to request specific DebitTransfer information from another business application module. The response to the AcknowledgeDebitTransfer is the AcknowledgeDebitTransfer.
  9. AcknowledgeDebitTransferIST [1..1]    The purpose of the AcknowledgeDebitTransferIST is to enable an application to request specific DebitTransferIST information from another business application module. The response to the AcknowledgeDebitTransferIST is the AcknowledgeDebitTransferIST.
  10. AcknowledgeDispatchList [1..1]    The purpose of the AcknowledgeDispatchList Business Object Document is to acknowledge receipt of the DispatchList
  11. AcknowledgeEmployeeWorkTime [1..1]    The purpose of the AcknowledgeEmployeeWorkTime is to Acknowledge work time information for an employee from a data collection application to an ERP Human Resource application.
  12. AcknowledgeEngineeringChangeOrder [1..1]    The purpose of the AcknowledgeEngineeringChangeOrder Business Object Document is to acknowledge receipt of the EngineeringChangeOrder
  13. AcknowledgeEngineeringWorkDocument [1..1]    The purpose of the AcknowledgeEngineeringWorkDocument is to enable an application to provide EngineeringWorkDocument from another business application module. The AcknowledgeEngineeringWorkDocument is provided in response to the ProcessEngineeringWorkDocument in order to accept or reject the request to process.
  14. AcknowledgeInspectDelivery [1..1]    The purpose of the AcknowledgeInspectDelivery is to supply InspectDelivery information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example; 1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information. 3. A Laboratory Information System could send quality information to an Inventory application, 4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
  15. AcknowledgeInventoryBalance [1..1]    The purpose of the ChangeInventoryBalance is to enable the communication of a Change in the InventoryBalance data that exists on separate Inventory databases. This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure. This is data that describes the ITEM as it exists at a specific location. It is
  16. AcknowledgeInventoryConsumption [1..1]    The purpose of the AcknowledgeInventoryConsumption is to inform a seller or provider about InventoryConsumption of items.
  17. AcknowledgeInventoryCount [1..1]    The purpose of the AcknowledgeInventoryCount is to transmit an inventory count to ERP from the actual physical inventory location. This count may be a cycle count or a physical count. This BOD may also apply to planned or unplanned inventory counts.
  18. AcknowledgeInvoice [1..1]    The purpose of the AcknowledgeInvoice Business Object Document is to acknowledge receipt of the Invoice
  19. AcknowledgeIssueInventory [1..1]    The purpose of the AcknowledgeIssueInventory is to respond to a ProcessIssueInventor, where an unplanned issue of an item to a miscellaneous location. Possible reasons for this include: 1. The material is defective and needs replacing, 2. The material is used up and needs replenishment.
  20. AcknowledgeJournalEntry [1..1]    The purpose of the AcknowledgeJournalEntry is to enable an application or component to respond to a ProcessJournalEntry. The response to the AcknowledgeJournalEntry is the response to the ProcessJournalEntry.
  21. AcknowledgeMaintenanceOrder [1..1]    The purpose of the AcknowledgeMaintenanceOrder Business Object Document is to acknowledge receipt of the MaintenanceOrder
  22. AcknowledgeMatchDocument [1..1]    The AcknowledgeMatchDocument provides the ability to request an application/ system to create a MatchDocument
  23. AcknowledgeMergeWIP [1..1]    The purpose of the AcknowledgeMergeWIP BOD is to notify a Manufacturing Application of the creation of a single production lot from multiple production lots of a product being made on a production order. The business environment most likely to require this capability is a lot based discrete manufacturing scenario. This BOD communicates the originating lots, the resulting lot, lot quantities, and the processing step at which this event occurred, along with the time at which this event occurred.
  24. AcknowledgeMoveInventory [1..1]    The purpose of the AcknowledgeMoveInventory is to give the organization the ability to do a quantity movement of materials from one organizational unit to another organizational unit.
  25. AcknowledgeMoveWIP [1..1]    The purpose of the AcknowledgeMoveWIP is to notify a Manufacturing Application of the progression through the production processing steps or operations of a product being made on a production order. The business environments most likely to require this capability are any type of manufacturing scenario. This BOD communicates which processing step the product is coming from and which step it is being moved to, along with the quantity moving and the time this event occurred. This BOD assumes that the applications involved in this business scenario will have already synchronized the production item and its BOM/Routing information.
  26. AcknowledgeOnlineOrder [1..1]    The purpose of the AcknowledgeOnlineOrder is to enable an application to provide online shopping OnlineOrders from another business application module. The AcknowledgeOnlineOrder is provided in response to the ProcessOnlineOrder in order to accept or reject the request to process the OnlineOrder.
  27. AcknowledgeOperation [1..1]    The purpose of the AcknowledgeOperation is to enable an application to provide online shopping Operations from another business application module. The AcknowledgeOperation is provided in response to the ProcessOperation in order to accept or reject the request to process the Operation.
  28. AcknowledgeOpportunity [1..1]    The purpose of the AcknowledgeOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The AcknowledgeOpportunity is provided in response to the ProcessOpportunity in order to accept or reject the request to process.
  29. AcknowledgePaymentStatus [1..1]    The purpose of the AcknowledgePaymentStatus is to provide the results of an application to process specific PaymentStatus information by the ProcessPaymentStatus. This typically a transaction that occurs between a company and a Bank in order to remit payment to company that has provided goods or services. This is the response to the ProcessPaymentStatus.
  30. AcknowledgePaymentStatusIST [1..1]    The purpose of the AcknowledgePaymentStatusIST is to provide the results of an application to process specific PaymentStatusIST information by the ProcessPaymentStatusIST. This typically a transaction that occurs between a company and a Bank in order to remit payment to company that has provided goods or services. This is the response to the ProcessPaymentStatusIST.
  31. AcknowledgePickList [1..1]    The purpose of the AcknowledgePickList is to Acknowledge the details of an individual Picking List from a plant level to an ERP system. This BOD will usually cause Acknowledges to occur.
  32. AcknowledgeProductAvailability [1..1]    The AcknowledgeProductAvailability may be used to obtain limited information Acknowledgeing about documents that match certain selection criteria in a GetAcknowledgeProductAvailability. Additional information about a specific ProductAvailability may be obtained through ShowProductAvailability by using the Acknowledgeing information to populate a GetProductAvailability request.
  33. AcknowledgeProductionOrder [1..1]    The purpose of the AcknowledgeProductionOrder Business Object Document is to acknowledge receipt of the ProductionOrder
  34. AcknowledgePurchaseOrder [1..1]    The purpose of the AcknowledgePurchaseOrder Business Object Document is to acknowledge receipt of the Purchase Order and to reflect any changes. Commonly, the acknowledgment is generated by an order management application and transmitted to a purchasing or procurement application.
  35. AcknowledgeQuote [1..1]    The purpose of the AcknowledgeQuote Business Object Document is to acknowledge receipt of the Quote
  36. AcknowledgeReceiveDelivery [1..1]    The AcknowledgeReceiveDelivery may be used to notify the shipping business partner that the shipment has been received by the customer or consignee destination, and alert them to any discovered discrepancies. The acknowledgement may contain the full detail of the receipt as created by the receiving party or just the discrepancies and other exception conditions. The AcknowledgeReceiveDelivery BOD supports receipt acknowledgements at either the line item level and/or the ship unit level. Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents.
  37. AcknowledgeReceiveItem [1..1]    The purpose of the AcknowledgeInventoryTransfer is to give the organization the ability to do a quantity movement of materials from one organizational unit to another organizational unit.
  38. AcknowledgeRecoverWIP [1..1]    The purpose of the AcknowledgeRecoverWIP is to notify a Manufacturing Application of the creation of usable production materials from material previously considered to be unsuitable for production use. This is most often likely to represent a return to production of scrap material. The business environments most likely to require this capability are any type of manufacturing scenario. This BOD communicates what is being recovered, the quantity being recovered, and the processing step at which the recovered material is to re-enter the production process, along with the time at which this event occurred.
  39. AcknowledgeRequireProduct [1..1]    The purpose of the AcknowledgeRequireProduct Business Object Document is to acknowledge receipt of the RequireProduct
  40. AcknowledgeRequisition [1..1]    The purpose of the AcknowledgeRequisition Business Object Document is to acknowledge receipt of the Requisition
  41. AcknowledgeRFQ [1..1]    The purpose of the AcknowledgeRFQ Business Object Document is to acknowledge receipt of the RFQ
  42. AcknowledgeRiskControlLibrary [1..1]    The purpose of the AcknowledgeRiskControlLibrary is to notify a Manufacturing Application of the creation of usable production materials from material previously considered to be unsuitable for production use. This is most often likely to represent a return to production of scrap material. The business environments most likely to require this capability are any type of manufacturing scenario. This BOD communicates what is being recovered, the quantity being recovered, and the processing step at which the recovered material is to re-enter the production process, along with the time at which this event occurred.
  43. AcknowledgeSalesLead [1..1]    The purpose of the AcknowledgeSalesLead is to enable an application to provide SalesLead information from one business application to another business application. The AcknowledgeSalesLead is provided in response to the ProcessCart in order to accept or reject the request to process.
  44. AcknowledgeSalesOrder [1..1]    The purpose of the AcknowledgeSalesOrder Business Object Document is to acknowledge receipt of the SalesOrder
  45. AcknowledgeShipment [1..1]    The purpose of the AcknowledgeShipment Business Object Document is to acknowledge receipt of the Shipment
  46. AcknowledgeShipmentUnit [1..1]    The purpose of the AcknowledgeShipmentUnit is to enable an application to respond to a ShipmentUnit information from another business application module in order to accept or reject the request to Process. The AcknowledgeShipmentUnit is typically published from the business application that is is receiving the request to Process the ShipmentUnit information This may also occur across enterprises. The AcknowledgeShipmentUnit is the response for the ProcessShipmentUnit to indicate success or failure. If the receiving system needs to make changes to the ShipmentUnit then the ChangeShipmentUnit can be used a coresponding RespondShipmentUnit accepts the changes or indicates additional changes.
  47. AcknowledgeSplitWIP [1..1]    The purpose of the AcknowledgeSplitWIP is to notify a Manufacturing Application of the creation of multiple production lots from a single production lot of a product being made on a production order. The business environment most likely to require this capability is a lot based discrete manufacturing scenario. This BOD communicates the originating lot, the resulting lots, their quantities, and the processing step at which this event occurred, along with the time at which this event occurred.
  48. AcknowledgeWIPStatus [1..1]    The AcknowledgeWIPStatus is used to receive the results of the ProcessWIPStatus.
  49. AddPurchaseOrder [1..1]    AddPurchaseOrder is being deprecated as of OAGIS 9.0. AddPurchaseOrder will be made available for the next three releases. OAGi recommend using ProcessPurchaseOrder for all new development. The purpose of the Add PurchaseOrder Business Service Request is to communicate from one business application to one or more other business applications that a Purchase Order has been added or needs to be added, depending on the business case. There are many possible business applications in several environments that may use this capabilit
  50. AddQuote [1..1]    AddQuote is being deprecated as of OAGIS 9.0. AddQuote will be made available for the next three releases. OAGi recommend using ProcessQuote for all new development. The purpose of the AddQuote is to communicate from one business application to one or more other business applications that additional data related to a quote has been added or needs to be added, depending on the business case.
  51. AddRequisition [1..1]    AddRequisition is being deprecated as of OAGIS 9.0. AddRequisition will be made available for the next three releases. OAGi recommend using ProcessRequisition for all new development. The purpose of the AddRequisition is to send demand for goods or services to another business application for consideration of buying or in some way obtaining the requested items.
  52. AddRFQ [1..1]    AddRFQ is being deprecated as of OAGIS 9.0. AddRFQ will be made available for the next three releases. OAGi recommend using ProcessRFQ for all new development. The purpose of the AddRFQ is to communicate from one business application to one or more other business applications that additional data related to a Request for Quote has been added or needs to be added, depending on the business case
  53. AddSalesOrder [1..1]    AddSalesOrder is being deprecated as of OAGIS 9.0. AddSalesOrder will be made available for the next three releases. OAGi recommend using ProcessSalesOrder for all new development. The purpose of the Add Salesorder is to communicate from one business application to one or more other business applications that a Sales Order has been added or needs to be added, depending on the business case. This BOD commonly causes updates to occur.
  54. AllocateCostingActivity [1..1]    In an effort to simpilify the usage of the verbs the AllocateCostingActivity BOD is being deprecated as of OAGIS 9.0, the AllocateCostingActivity will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the PostCostingActivity BOD which may serve the same function of the AllocateCostingActivity BOD. The purpose of the AllocateCostingActivity BOD is to enable the update of Activityinformation from a production or manufacturing application to a costing application. This is necessary for applications that are based on a Dual Cycle Accounting model. This Dual Cycle Accounting model does not capture the details of the Activities that caused entries to be made in the general ledger application, but instead captures them in a separate overall costing application. This BOD commonly causes updates to occur and may be used as part of a large integration scenario or as a single tool for updating data. For Single Cycle accounting systems, the PostJournalEntry BOD will be used to ensure that the costing information flows from the Manufacturing Application to the Financial Application. In most cases either PostJournal or AllocateActivity will be used when the Financial applications are included with Logistics, but both Business Service Requests will not be used in the same integration scenario.
  55. CancelDispatchList [1..1]    The purpose of the CancelDispatchList is to publish to a business application or system the need to cancel an DispatchList or one or more of its elements
  56. CancelEmployeeWorkTime [1..1]    The purpose of the CancelEmployeeWorkTime is to Cancel work time information for an employee from a data collection application to an ERP Human Resource application.
  57. CancelEngineeringChangeOrder [1..1]    The purpose of the CancelEngineeringChangeOrder is to publish to a business application or system the need to cancel an EngineeringChangeOrder or one or more of its elements
  58. CancelEngineeringWorkDocument [1..1]    The purpose of the CancelEngineeringWorkDocument is to enable an application to provide EngineeringWorkDocument from another business application module. The CancelEngineeringWorkDocument is provided in response to the ProcessCart in order to request a Cancel to process the cart. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  59. CancelInspectDelivery [1..1]    The purpose of the CancelInspectDelivery is to supply InspectDelivery information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example; 1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information. 3. A Laboratory Information System could send quality information to an Inventory application, 4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
  60. CancelInventoryBalance [1..1]    The purpose of the ChangeInventoryBalance is to enable the communication of a Change in the InventoryBalance data that exists on separate Inventory databases. This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure. This is data that describes the ITEM as it exists at a specific location. It is
  61. CancelInvoice [1..1]    The purpose of the CancelInvoice is to publish to a business application or system the need to cancel an Invoice or one or more of its elements
  62. CancelMaintenanceOrder [1..1]    The purpose of the CamcelMaintenanceOrder is to publish to a business application or system the need to cancel a Maintenance Order or one or more of its operations. One possible scenario is the cancellation of Maintenance Order from field devices, service trucks, production system, etc.
  63. CancelPickList [1..1]    The purpose of the CancelPickList is to Cancel the details of an individual Picking List from a plant level to an ERP system. This BOD will usually cause Cancels to occur.
  64. CancelProductionOrder [1..1]    The purpose of the CancelProductionOrder is to notify a Manufacturing Application of the need to cancel a previous order to make a product in a specific quantity, for a specific need by date. This BOD may be used to cancel an entire Production Order, or a specific line on the production order. Processing Note: This cancel must refer to the original document and/or item ordered. To cancel the entire order, include only the Header information for the instance of the Production Order you wish to cancel. To cancel a line or several lines, each line to be cancelled must be included in the request.
  65. CancelPurchaseOrder [1..1]    The purpose of the Cancel PurchaseOrder is to communicate from one business application to one or more other business applications that a previous Purchase Order or Purchase Order line is no longer needed. Processing Note: This cancel must refer to the original document and/or item ordered. To cancel the entire order, include only the Purchase Order Header information for the instance of the Purchase Order you wish to cancel. To cancel a line or several lines, each line to be cancelled must be included. This BOD commonly causes updates to occur and may be used as part of a larger integration scenario or as a single tool for communicating demand.
  66. CancelQuote [1..1]    The purpose of the CancelQuote is to publish to a business application or system the need to cancel an entire Quote or one or more of its line items.
  67. CancelReceiveDelivery [1..1]    The CancelReceiveDelivery may be used to Cancel the receiver's internal receiving and order management business applications to indicate that the requested material has arrived, including any unexpected quantity, condition or other exception discrepancies. There are many other possible business applications in several environments that may use this capability. For example: 1. A Purchasing application may use this BOD to notify an Accounts Payable application of a specific delivery. This will enable the Accounts Payable application to accurately calculate the amount it needs to pay a business partner. 2. A Purchasing application could use this to notify a MRP, Inventory, or Manufacturing business application that a delivery has occurred and the goods are available for use or inspection, etc. 3. An MRP/Inventory system could use this BSR to communicate changes on a physical receipt in inventory to the Purchasing system. The CancelReceiveDelivery supports receipts at either the line item level and/or the ship unit level. Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents.
  68. CancelRequireProduct [1..1]    The purpose of the CancelRequireProduct is to communicate from one business application to one or more other business applications that a previously requested item is no longer required. Processing Note: This cancel must refer to the original item requested. To cancel the item(s), each item to be cancelled must be included.
  69. CancelRequisition [1..1]    The purpose of the CancelRequisition is to communicate from one business application to one or more other business applications that a previous requisition or requisition line item is no longer needed.
  70. CancelRFQ [1..1]    The purpose of the CancelRFQ is to publish to a business application or system the need to cancel an entire Request for Quote or one or more of its line items.
  71. CancelSalesOrder [1..1]    The purpose of the Cancel SalesOrder is to communicate from one business application to one or more other business applications that a previous Sales Order, line, or schedule is no longer needed. Processing Note: This cancel must refer to the original document, item, and schedule. To cancel the entire order, include only the Salesorder Header information for the instance of the Salesorder you wish to cancel. To cancel a SalesOrder Line or SalesOrder Schedule, each line or schedule to be cancelled must be included in the occurrence of the BOD with the Corresponding LineNumber. If a schedule is to be cancelled, the line that the schedule refers to MUST be included or the schedule can not be found.
  72. ChangeConfirmWIP [1..1]    The purpose of the ChangeConfirmWIP is to respond to a request for the data necessary to perform a confirmation of the movement of WIP (Work in Progress).
  73. ChangeCredit [1..1]    The purpose of the ChangeCredit is to Change the Credit Management functionality within the customer order management or the accounts receivable application. The ChangeCredit will also transmit changes in the accounts receivable open item balances to the credit management function of the customer order management application.
  74. ChangeCreditStatus [1..1]    The purpose of the ChangeCreditStatus is to notify the customer order management application that the overall credit status of a trading partner has changed or status on specific order(s) are to be changed.
  75. ChangeDispatchList [1..1]    The purpose of the ChangeDispatchList is to notify another application about a change in the DispatchList
  76. ChangeEmployeeWorkTime [1..1]    The purpose of the ChangeEmployeeWorkTime is to Change work time information for an employee from a data collection application to an ERP Human Resource application.
  77. ChangeEngineeringChangeOrder [1..1]    The purpose of the ChangeEngineeringChangeOrder is to notify another application about a change in the EngineeringChangeOrder
  78. ChangeEngineeringWorkDocument [1..1]    The purpose of the ChangeEngineeringWorkDocument is to enable an application to provide EngineeringWorkDocument from another business application module. The ChangeEngineeringWorkDocument is provided in response to the ProcessCart in order to request a change to process the cart. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  79. ChangeInspectDelivery [1..1]    The purpose of the ChangeInspectDelivery is to supply InspectDelivery information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example; 1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information. 3. A Laboratory Information System could send quality information to an Inventory application, 4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
  80. ChangeInventoryBalance [1..1]    The purpose of the ChangeInventoryBalance is to enable the communication of a Change in the InventoryBalance data that exists on separate Inventory databases. This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure. This is data that describes the ITEM as it exists at a specific location. It is
  81. ChangeInvoice [1..1]    The purpose of the ChangeInvoice is to notify another application about a change in the Invoice
  82. ChangeMaintenanceOrder [1..1]    The purpose of the ChangeMaintenanceOrder is to notify another application about a change in the MaintenanceOrder
  83. ChangeOnlineOrder [1..1]    The purpose of the ChangeOnlineOrder is to enable an application to provide online shopping OnlineOrders from another business application module. The ChangeOnlineOrder is provided in response to the ProcessOnlineOrder in order to request a change to process the OnlineOrder. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  84. ChangeOpportunity [1..1]    The purpose of the ChangeOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The ChangeOpportunityis provided in response to the ProcessCart in order to request a change to process the cart. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  85. ChangePickList [1..1]    The purpose of the ChangePickList is to Change the details of an individual Picking List from a plant level to an ERP system. This BOD will usually cause Changes to occur.
  86. ChangeProductionOrder [1..1]    The purpose of the ChangeProductionOrder is to notify another application about a change in the ProductionOrder
  87. ChangePurchaseOrder [1..1]    The purpose of the Change Purchaseorder is to request another business application to make changes to an existing Purchase Order. This change must refer to the original document and/or item ordered. The change processing assumes replacement of fields sent, with the exception the identifying fields of the Purchase Order. If any of these key fields require changing, (i.e. the PurchaseOrder Document Id or a LineNumber) that constitutes a cancellation of the request and/or the addition of another Purchase Order.
  88. ChangeQuote [1..1]    The purpose of the ChangeQuote is to request that another business application component make changes to an existing Quote
  89. ChangeReceiveDelivery [1..1]    The ChangeReceiveDelivery may be used to Change the receiver's internal receiving and order management business applications to indicate that the requested material has arrived, including any unexpected quantity, condition or other exception discrepancies. There are many other possible business applications in several environments that may use this capability. For example: 1. A Purchasing application may use this BOD to notify an Accounts Payable application of a specific delivery. This will enable the Accounts Payable application to accurately calculate the amount it needs to pay a business partner. 2. A Purchasing application could use this to notify a MRP, Inventory, or Manufacturing business application that a delivery has occurred and the goods are available for use or inspection, etc. 3. An MRP/Inventory system could use this BSR to communicate changes on a physical receipt in inventory to the Purchasing system. The ChangeReceiveDelivery supports receipts at either the line item level and/or the ship unit level. Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents.
  90. ChangeRequireProduct [1..1]    The purpose of the ChangeRequireProduct is to notify another application about a change in the RequireProduct
  91. ChangeRequisition [1..1]    The purpose of the ChangeRequisition is to communicate changes to an existing request for goods or services. This change must refer to the original document and/or item requested. The change processing assumes replacement of fields sent, with the exception of: the key fields for the Order and Line. If any of the Field Identifiers above require changing, that constitutes a cancellation of the request and/or the addition of another Requisition.
  92. ChangeRFQ [1..1]    The purpose of the ChangeRFQ is to request that another business application component make changes to an existing Request for Quote.
  93. ChangeSalesLead [1..1]    The purpose of the ChangeSalesLead is to enable an application to provide SalesLead information from one business application to another business application. The ChangeSalesLeadis provided in response to the ProcessCart in order to request a change to process the cart. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  94. ChangeSalesOrder [1..1]    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
  95. CreateMaintenanceOrder [1..1]    In an effort to simpilify the usage of the verbs the CreateMaintenanceOrder BOD is being deprecated as of OAGIS 9.0, the CreateMaintenanceOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ProcessMaintenanceOrder BOD which may serve the same function of the CreateMaintenanceOrder BOD. The purpose of the CreateMaintenanceOrder is to publish to a business application component or system the need to create or update a Maintenance Order. One possible scenario is the synchronization of Maintenance Order between field devices, service trucks, etc. with a CMMS system.
  96. CreateProductionOrder [1..1]    CreateProductionOrder is being deprecated as of OAGIS 9.0. CreateProductionOrder will be made available for the next three releases. OAGi recommend using ProcessProductionOrder for all new development. The purpose of the CreateProductionOrder is to notify a Manufacturing Application of the need to make a product in a specific quantity, for a specific need by date. The business environments most likely to require this capability are an Engineer to Order or a Configure to Order manufacturing scenario. This BOD communicates what the product configuration is and what choices have been made from the configuration
  97. CreateRequisition [1..1]    The purpose of the CreateRequisition is to notify another business application of the need to order parts in a specific quantity, for a specific need by date.
  98. GetActualLedger [1..1]    The purpose of the GetActualLedger is to enable an enterprise application to request detailed accounting ledger actual data.
  99. GetAllocateResource [1..1]    The purpose of the GetAllocateResource is to enable an application to request specific AllocateResource information from another business application module. The response to the GetAllocateResource is the ShowAllocateResource.
  100. GetBOM [1..1]    The purpose of the GetBOM is to enable an application to request specific Item Bill of Material information from another business application module. The response to the GetBOM is the ShowBOM. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate Item Bill of Material information.
  101. GetBudgetLedger [1..1]    The purpose of the GetBudgetLedger is to request budget amounts from all possible source applications throughout an enterprise to a general ledger or budget application.
  102. GetCarrierRoute [1..1]    The purpose of the GetCarrierRoute is to enable an application to request specific Carrier Route information from another business application module. The response to the GetCarrierRoute is the ShowCarrierRoute.
  103. GetCatalog [1..1]    The purpose of the GetCatalog is to enable a business application module or system to request catalog information. The Catalog information that is requested by the GetCatalog may include · Item Identifiers · Specifications · Pricing Information agreed on either · Purchase Agreements · Price Lists · Availability and Delivery Information · Related Items and accessories There are many possible business applications in several environments that may use this capability. Some examples of usage scenarios are: · Manufacturer exchanging catalogs with distributors/ suppliers/e-marketplaces · Distributors/ Suppliers/ e-marketplaces exchanging catalogs with Buyers or other trading partners It may also be necessary to support Component Supplier Management (CSM) scenarios. In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog. The Catalog exchange scenario can be implemented either as a simple scenario using a single BOD, or in the case or large catalogs involving complex pricing scenarios or partner specific details, as multiple BODs.
  104. GetChartOfAccounts [1..1]    The purpose of the GetChartOfAccounts is to enable an application to request specific ChartOfAccounts information from another business application module. The response to the GetChartOfAccounts is the ShowChartOfAccounts.
  105. GetConfirmWIP [1..1]    The purpose of the GetConfirmWIP is to enable the requesting of data necessary to perform a confirmation of the movement of WIP (Work in Progress).
  106. GetCostingActivity [1..1]    The purpose of the GetCostingActivity is to enable an application to request specific CostingActivity information from another business application module. The response to the GetCostingActivity is the ShowCostingActivity.
  107. GetCredit [1..1]    The purpose of the GetCredit is for the order management application to request credit data for a trading partner from the credit management function. The GetCredit does not imply any update, it is only an inquiry function. The ShowCredit discussed in the next chapter will be the response back to the order management application. Discussed in a later chapter is the UpdateCredit. The UpdateCredit may be used in both directions between the order management and the accounts receivable application. Its purpose is to keep order, shipment and open item amounts current. Finally, the ChangeCreditStatus is used to update the order management application with any changes in business status for a particular trading partner.
  108. GetCreditStatus [1..1]    The purpose of the GetCreditStatus is to enable an application to request specific CreditStatus information from another business application module. The response to the GetCreditStatus is the ShowCreditStatus.
  109. GetCreditTransfer [1..1]    The purpose of the GetCreditTransfer is to enable an application to request specific CreditTransfer information from another business application module. The response to the GetCreditTransfer is the ShowCreditTransfer.
  110. GetCreditTransferIST [1..1]    The purpose of the GetCreditTransferIST is to enable an application to request specific CreditTransferIST information from another business application module. The response to the GetCreditTransferIST is the ShowCreditTransferIST.
  111. GetCurrencyExchangeRate [1..1]    The purpose of the GetCurrencyExchangeRate is to enable an application to request specific CurrencyExchangeRate information from another business application module. The response to the GetCurrencyExchangeRate is the ShowCurrencyExchangeRate.
  112. GetCustomerPartyMaster [1..1]    The purpose of the GetCustomerPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases. The GetCustomerPartyMaster allows a business application to request information about a given party. The ShowCustomerPartyMaster is the response to this request providing the specific information requested.
  113. GetDebitTransfer [1..1]    The purpose of the GetDebitTransfer is to enable an application to request specific DebitTransfer information from another business application module. The response to the GetDebitTransfer is the ShowDebitTransfer.
  114. GetDebitTransferIST [1..1]    The purpose of the GetDebitTransferIST is to enable an application to request specific DebitTransferIST information from another business application module. The response to the GetDebitTransferIST is the ShowDebitTransferIST.
  115. GetDispatchList [1..1]    The purpose of the GetDispatchList is to enable a business application module to request this information from another business application. The reply to this BOD is the ShowDispatchList.
  116. GetEmployeeWorkSchedule [1..1]    The purpose of the GetEmployeeWorkSchedule is to enable an application to request specific EmployeeWorkSchedule information from another business application module. The response to the GetEmployeeWorkSchedule is the ShowEmployeeWorkSchedule.
  117. GetEmployeeWorkTime [1..1]    The purpose of the GetEmployeeWorkTime is to enable an application to request specific EmployeeWorkTime information from another business application module. The response to the GetEmployeeWorkTime is the ShowEmployeeWorkTime.
  118. GetEngineeringChangeOrder [1..1]    The purpose of the Get EngineeringChangeOrder is to communicate to a business application module or system the need to request a Show EngineeringChangeOrder for the Engineering Change Document specified in the Message. 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 request an Engineering Change Document.
  119. GetEngineeringWorkDocument [1..1]    The purpose of the GetEngineeringWorkDocument is to enable an application to request specific EngineeringWorkDocument from another business application module. The response to the GetEngineeringWorkDocument is the ShowEngineeringWorkDocument.
  120. GetField [1..1]    The purpose of the GetField is to enable an application to request specific Field information from another business application module. The response to the GetField is the ShowField.
  121. GetInspectDelivery [1..1]    The purpose of the GetInspectDelivery is to enable an application to request specific InspectDelivery information from another business application module. The response to the GetInspectDelivery is the ShowInspectDelivery.
  122. GetInventoryBalance [1..1]    The purpose of the GetInventoryBalance is to enable an application to request specific InventoryBalance information from another business application module. The response to the GetInventoryBalance is the ShowInventoryBalance.
  123. GetInventoryConsumption [1..1]    The most common use of the GetInventoryConsumption is to request a buyer's usage information about an item or product for the supplier of such item or product. This BOD will not create or update either buyer's or supplier's inventory records. The receiver of the request is responsible to make effective use of this information. The BOD can be used in the following ways: (1) for a supplier of goods to request from the buyer, the consumptn status of goods (2) for a vendor to request from the retailer if retail sales of goods have been made; and (3) for inventory systems to request consumptn status from plant data collection and warehouse management systems. This is an outline of the business flow that this BOD supports: (1) Overall purchase, replenishment or vendor managed inventory agreement is in place and/or a Get Consumptn message is sent by the supplier. (2) Show Consumptn Message is returned the to supplier, distributor or third party logistics provider, that material has been consumed. This is done in response to events such as these (and/or the Get message), depending on implementation context: · Material is replenished to line side at manufacturing facitliy. · Material is assembled into final product. · Material is purchased and removed from facility by customer. (3) Supplier, distributor, third party logistics provider replenishes material, using information provided in the Show Consumptn message, the demand and shipment forecasts, and the terms of the overall purchase or vendor managed inventory agreement.
  124. GetInventoryCount [1..1]    The purpose of the GetInventoryCount is to request an occurrences of a Inventory Count information from an ERP system. This count may be a cycle count or a physical count. This BOD may also apply to planned or unplanned inventory counts.
  125. GetInvoice [1..1]    The purpose of the GetInvoice is to enable a request of an invoice. This BOD may be used as a request by a Customer to its Supplier. The SHowInvoice BOD would be the expected response.
  126. GetInvoiceLedgerEntry [1..1]    The purpose of the GetInvoiceLedgerEntry is to enable an application to request specific InvoiceLedgerEntry information from another business application module. The response to the GetInvoiceLedgerEntry is the ShowInvoiceLedgerEntry.
  127. GetIssueInventory [1..1]    The purpose of the GetIssueInventory is to request inventory issue information against an order, from an ERP system into a PDC system to confirm the IssueInventory transaction (BOD).
  128. GetItemMaster [1..1]    The purpose of the GetItemMaster is to enable a business application module to request information concerning a specific ITEM from another business application. The reply to this BOD is the ShowItemMaster. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to request item information.
  129. GetJournalEntry [1..1]    The purpose of the GetJournalEntry is to enable an application or component to request a JournalEntry document from another business application or component. The response to the GetJournalEntry is is the ListJournalEntry. The GetJournalEntry also enables the retrieval of information across several documents by using selection fields. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  130. GetListActualLedger [1..1]    In an effort to simpilify the usage of the verbs the GetListActualLedger BOD is being deprecated as of OAGIS 9.0, the GetListActualLedger will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetActualLedger BOD which may serve the same function of the GetListActualLedger BOD. The purpose of the GetListActualLedger is to request information containing summary information for one or more ledgers.. The response to this request is ListActualLedger.
  131. GetListBOM [1..1]    In an effort to simpilify the usage of the verbs the GetListBOM BOD is being deprecated as of OAGIS 9.0, the GetListBOM will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetBOM BOD which may serve the same function of the GetListBOM BOD. The purpose of the GetListBOM is to enable an application or component to request a summary list of Bill of Material information from another business application or component. The response to the GetListBOM is the ListBOM The GwtListBOM also enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all Bills of Material for a specific ITEM. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate Item Bill of Material information.
  132. GetListInventoryCount [1..1]    In an effort to simpilify the usage of the verbs the GetListInventoryCount BOD is being deprecated as of OAGIS 9.0, the GetListInventoryCount will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetInventoryCount BOD which may serve the same function of the GetListInventoryCount BOD. The purpose of the GetListInventoryCount is to to enable a business application to request several occurrences of summary Inventory Count information from an ERP system. This count may be a cycle count or a physical count. This BOD may also apply to planned or unplanned inventory counts.
  133. GetListItemMaster [1..1]    In an effort to simpilify the usage of the verbs the GetListItemMaster BOD is being deprecated as of OAGIS 9.0, the GetListItemMaster will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetItemMaster BOD which may serve the same function of the GetListItemMaster BOD. The purpose of the GetListItemMaster is to enable a business application module to request summary information concerning an ItemMaster or ITEMs from another business application. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project. The response to this request is the ListItemMaster. This BOD does not usually cause updates to occur.
  134. GetListMaintenanceOrder [1..1]    In an effort to simpilify the usage of the verbs the GetListMaintenanceOrder BOD is being deprecated as of OAGIS 9.0, the GetListMaintenanceOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetMaintenanceOrder BOD which may serve the same function of the GetListMaintenanceOrder BOD. The purpose of the GetList MaintenanceOrder Business Object Document is to enable a business application module to request information containing summary information for one or more MaintenanceOrder. The response to this request is the List. The GetListMaintenanceOrder enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all Resource Component occurrences for a specific MaintenanceOperation. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  135. GetListPickList [1..1]    In an effort to simpilify the usage of the verbs the GetListPickList BOD is being deprecated as of OAGIS 9.0, the GetListPickList will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetPickList BOD which may serve the same function of the GetListPickList BOD. The purpose of the GetListPickList is to enable a business application to request summary information for one or more Picking Lists from an ERP system. If a List of documents is requested, that list will be used so a selection and Get request of a specific picking list can be made, if necessary.
  136. GetListProductionOrder [1..1]    In an effort to simpilify the usage of the verbs the GetListProductionOrder BOD is being deprecated as of OAGIS 9.0, the GetListProductionOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetProductionOrder BOD which may serve the same function of the GetListProductionOrder BOD. The purpose of the GetListProductionOrder is to enable an business software component to request summary Production Order information from another business application module. The response to this request is the ListProductionOrder. The GetListProductionOrder also enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all ProductionOrder Lines for a specific Item. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  137. GetListPurchaseOrder [1..1]    In an effort to simpilify the usage of the verbs the GetListPurchaseOrder BOD is being deprecated as of OAGIS 9.0, the GetListPurchaseOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetPurchaseOrder BOD which may serve the same function of the GetListPurchaseOrder BOD. The purpose of the GetList PurchaseOrder is to enable a business application to request information containing summary information for one or more Purchase Orders from another business application. The GetList PurchaseOrder also enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all PurchaseOrder Lines for a specific ItemId. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project. This BOD does not usually cause updates to occur. It may be used as part of a large integration scenario or as a single tool for requesting information on existing demands for goods or services. Examples include: 1. A Plant Data Collection application could use this BOD to request information from a Purchasing application. 2. A MRP, Inventory or Manufacturing business application could use this to obtain order information.
  138. GetListQuote [1..1]    In an effort to simpilify the usage of the verbs the GetListQuote BOD is being deprecated as of OAGIS 9.0, the GetListQuote will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetQuote BOD which may serve the same function of the GetListQuote BOD. The purpose of the GetListQuote is to enable a business application module to request information containing summary information for one or more Quotes. The response to this request is List Quote. The GetListQuote also enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all SalesInformation Component occurrences for a specific Quote Line. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  139. GetListReceiveDelivery [1..1]    In an effort to simpilify the usage of the verbs the GetListReceiveDelivery BOD is being deprecated as of OAGIS 9.0, the GetListReceiveDelivery will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetReceiveDelivery BOD which may serve the same function of the GetListReceiveDelivery BOD. The GetListReceiveDelivery may be used to request information about a set of expected (unreceived) or previously received goods deliveries meeting certain selection criteria. The response to the GetListReceiveDelivery request is ListReceiveDelivery.
  140. GetListRequisition [1..1]    The purpose of the GetListRequisition is to enable a business application to request summary information for one or more requisitions from another business application. The GetListRequisition also enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all Requisition Lines for a specific OrderItem. This type of functionality will be limited to the capabilities of the responding application and needs to be determined during the implementation project
  141. GetListRFQ [1..1]    In an effort to simpilify the usage of the verbs the GetListRFQ BOD is being deprecated as of OAGIS 9.0, the GetListRFQ will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetRFQ BOD which may serve the same function of the GetListRFQ BOD. The purpose of the GetllistRFQ is to enable a business application module to request information containing summary information for one or more Request for RFQs. The response to this request is ListRFQ. The GetllistRFQ also enables the retrieval of information across several documents by using selection fields.
  142. GetListRouting [1..1]    In an effort to simpilify the usage of the verbs the GetListRouting BOD is being deprecated as of OAGIS 9.0, the GetListRouting will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetRouting BOD which may serve the same function of the GetListRouting BOD. The purpose of the GetListRouting is to communicate to a business application component or module a request for a summary list of a Routing structure or structures to be returned in a ListRouting.
  143. GetListSalesOrder [1..1]    In an effort to simpilify the usage of the verbs the GetListSalesOrder BOD is being deprecated as of OAGIS 9.0, the GetListSalesOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetSalesOrder BOD which may serve the same function of the GetListSalesOrder BOD. The purpose of the GetList SalesOrder is to enable a business application module to request information containing summary information for one or more SalesOrder from another business application. The response to this request is the List SalesOrder. The GetList SalesOrder also enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all SalesOrder Lines for a specific ITEM. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project. This BOD does not usually cause updates to occur. It may be used as part of a large integration scenario or as a single tool for requesting information on existing demands for goods or services. For example, a Sales Automation application may use this BOD to ask for information from a Customer Order application.
  144. GetListUOMGroup [0..1]    In an effort to simpilify the usage of the verbs the GetListUOMGroup BOD is being deprecated as of OAGIS 9.0, the GetListUOMGroup will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the GetUOMGroup BOD which may serve the same function of the GetListUOMGroup BOD. The purpose of the GetListUnitOfMeasure is to communicate to a business application component or module a request for a summary list of a UnitOfMeasure Groups to be returned in a ListUnitOfMeasure. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to request alternate UOM information for one or more items.
  145. GetLocation [1..1]    The purpose of the GetLocation is to enable an application to request specific Location information from another business application module. The response to the GetLocation is the ShowLocation.
  146. GetLocationService [1..1]    The purpose of RequestLocationService is to enable a mechanism to ensure that the physical locations owned by the business applications are validated, geocoded, and standardized based on information returned by location service providers. This BOD may be initiated by the sending system upon some event occurring, such as receiving a request submitted by another system for certain location service. There are many possible business applications in several environments that may use this capability. For example, the customer management, the supplier management, or HRMS business applications could use this to receive processed location information from location service providers.
  147. GetMaintenanceOrder [1..1]    The purpose of the GetMaintenanceOrder is to enable a business applications module to request this information from another business application. The response to this BOD is the ShowMaintenanceOrder.
  148. GetMatchDocument [1..1]    The purpose of the GetMatchDocument is to enable a business application module to request information concerning invoice matching from another business application. The reply to this BOD is the ShowMatchDocument. This BOD does not usually cause updates to occur. There are several possible business applications in several environments that may use this capability. The description and the pictures below visualize the possible use of this BOD. In certain application suites, purchase order and invoice matching functionality exists in the purchasing application, while in other suites this functionality exists in the accounts payable application. The invoice matching process may include several document types, including the following: Two way match - Purchase Order and the Invoice Three way match - Purchase Order, Invoice, and the Receipt Four way match - Purchase Order, Invoice, Receipt, and Inspection results Note: For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching. When matching takes place in the purchasing application, the purchasing application may have to request the accounts payable application to provide the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched. This is the generally the situation when the invoice is initially entered into the accounts payable application. Note that in some situations, accounts payable will send invoices to the purchasing application unsolicited. In others, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters. When matching takes place in the accounts payable application, the purchasing application must inform the accounts payable application of the purchasing transactions (purchase orders, goods receiving notes and inspection tickets) to which the invoice (in accounts payable) is to be matched. Alternatively, the accounts payable application can request the information. The purpose of the GetMatchDocument is to enable both the accounts payable application and the purchasing application to request the transactions that are required to be matched. In both cases, the receiving application will use the ShowMatchDocument to return the requested information.
  149. GetMergeWIP [1..1]    The purpose of the GetMergeWIP is to enable an application to request specific MergeWIP information from another business application module. The response to the GetMergeWIP is the ShowMergeWIP.
  150. GetMoveInventory [1..1]    The purpose of the GetMoveInventory is to enable an application or component to request an MoveInventory document from another business application or component. The response to the GetMoveInventory is is the ListMoveInventory. The GetMoveInventory also enables the retrieval of information across several documents by using selection fields. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  151. GetMoveWIP [1..1]    The purpose of the GetMoveWIP is to enable an application to request specific MoveWIP information from another business application module. The response to the GetMoveWIP is the ShowMoveWIP.
  152. GetOnlineOrder [1..1]    The purpose of the GetOnlineOrder is to enable an application to request specific online shopping OnlineOrder from another business application module. The response to the GetOnlineOrder is the ShowOnlineOrder.
  153. GetOnlineSession [1..1]    The purpose of the GetOnlineSession is to enable an application to request specific online OnlineSession from another business application module. The response to the GetOnlineSession is the ShowOnlineSession.
  154. GetOperation [1..1]    The purpose of the GetOperation is to enable an application to request specific online shopping Operation from another business application module. The response to the GetOperation is the ShowOperation.
  155. GetOpportunity [1..1]    The purpose of the GetOpportunity is to enable an application to request a specific Opportunity information from one business application to another business application. The response to the GetOpportunity is the ShowOpportunity.
  156. GetPartyMaster [1..1]    The purpose of the GetPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases. The GetPartyMaster allows a business application to request information about a given party. The ShowPartyMaster is the response to this request providing the specific information requested.
  157. GetPayable [1..1]    The purpose of the GetPayable is to facilitate keeping party information synchronized that exists on separate data bases. The GetPayable allows a business application to request information about a given party. The ShowPayable is the response to this request providing the specific information requested.
  158. GetPaymentStatus [1..1]    The purpose of the GetPaymentStatus is to enable an application to request specific PaymentStatus information from another business application module. This typically a transaction that occurs between a company and a Bank in order to remit PaymentStatus to company that has provide goods or services. The response to the GetPaymentStatus is the ShowPaymentStatus.
  159. GetPaymentStatusIST [1..1]    The purpose of the GetPaymentStatusIST is to enable an application to request specific PaymentStatusIST information from another business application module. This typically a transaction that occurs between a company and a Bank in order to remit PaymentStatusIST to company that has provide goods or services. The response to the GetPaymentStatusIST is the ShowPaymentStatusIST.
  160. GetPersonnel [1..1]    The purpose of the GetPersonnel is to request Personnel data for a worker.
  161. GetPickList [1..1]    The purpose of the GetPickList is to enable a request for the retrieval of a single Picking List from an ERP system. The reply to this request is the ShowPickList. Individual lines from a Picking List are not selectable with this BOD. Only the complete document is selected and returned.
  162. GetPlanningSchedule [1..1]    Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party. Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional Data Type PlanningScheduleException. The purpose of the GetPlanningSchedule is to enable a business applications module to request this Planning Schedule information from another business application. The response to this BOD is ShowPlanningSchedule.
  163. GetPriceList [1..1]    The purpose of the GetPriceList is to enable a business application module or system to request information concerning new or existing product price lists. This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in an Order Management to Manufacturing application integration scenario. There are many possible business applications in several environments that may use this capability. For example, a Manufacturing, distributor or reseller business application could use this to communicate the price change or request a price list. It may also be necessary to support Component Supplier Management (CSM) scenarios. In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog. A customer purchases the product from the Catalog provider. They have the capability to do comparison shopping from the catalog. Supplier Certification may be provided by the Catalog provider. This definition of price list is intended to support simple pricing scenario, especially pricing that may accompany a published price list. It is not intended to support complex pricing environments that may be needed to support features such as; · Deals and Promotions · Coupons and Sales Incentives · Rebates and Accruals This functionality will be addressed in a subsequent release. It is a working assumption that the representation of complex qualifications, coupons and sales incentives are rarely communicated between systems.
  164. GetProductAvailability [1..1]    The purpose of the GetProductAvailability is to enable requests of product availability data by an Order Management business application to an Available to Promise (ATP) or Production business application. The business process scenario is the Order Management application interacting with the Available to Promise or Production application in order to determine availability of a product for the customer. This scenario is commonly referred to as Make to Order or Build to Order. The response to this request is the ShowProductAvailability.
  165. GetProductionOrder [1..1]    The purpose of the GetProductionOrder is to enable an business application module to request specific Production Order information from another business application module. The reply to this is the ShowProductionOrder.
  166. GetProjectAccounting [1..1]    The purpose of the GetProjectAccounting is to enable an application to request specific ProjectAccounting information from another business application module. The response to the GetProjectAccounting is the ShowProjectAccounting.
  167. GetProjectMaster [1..1]    The purpose of the GetProjectMaster is to enable an application to request specific ProjectMaster information from another business application module. The response to the GetProjectMaster is the ShowProjectMaster.
  168. GetPurchaseOrder [1..1]    The purpose of the Get PurchaseOrder is to enable a business application module to request information concerning a specific purchase order from another business application. The reply to this BOD is the Show PurchaseOrder. There are several environments that may use this capability. For example, an MRP application may use this BOD to ask for information from a Order Management application, or a Plant Data Collection application may also use this BOD to request information from a Order Management application. This may als happen across business parties. This BOD does not usually cause updates to occur.
  169. GetQuote [1..1]    The purpose of the GetQuote is to enable a business applications module to request this Quote information from another business application. The response to this BOD is ShowQuote.
  170. GetReceivable [1..1]    The purpose of the GetReceivable is to enable an application to request specific Receivable information from another business application module. The response to the GetReceivable is the ShowReceivable.
  171. GetReceiveDelivery [1..1]    The GetReceiveDelivery may be used to request information about a specific expected (unreceived) or previously received goods delivery. The response to the GetReceiveDelivery request is ShowReceiveDelivery. For expected deliveries, the ShowReceiveDelivery document content may act as a receiving template or checklist to identify the quantity and shipping configuration of the expected goods. The ShowReceiveDelivery supports describing shipment content at either the line item level and/or the ship unit level. Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents.
  172. GetReceiveItem [1..1]    The purpose of the GetReceiveItem is to enable an application or component to request an ReceiveItem document from another business application or component. The response to the GetReceiveItem is is the ListReceiveItem. The GetReceiveItem also enables the retrieval of information across several documents by using selection fields. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  173. GetRecoverWIP [1..1]    The purpose of the GetRecoverWIP is to enable an application to request specific RecoverWIP information from another business application module. The response to the GetRecoverWIP is the ShowRecoverWIP.
  174. GetRequireProduct [1..1]    The purpose of the GetRequireProduct is to enable an application to request specific RequireProduct information from another business application module. The response to the GetRequireProduct is the ShowRequireProduct.
  175. GetRequisition [1..1]    The purpose of the GetRequisition is to enable a business application to request information concerning a specific requisition from another business application. The reply to this BOD is the ShowRequisition.
  176. GetRFQ [1..1]    The purpose of the GetRFQ document is to enable a business applications module to request Request for Quote information from another business application. The response to this BOD is ShowRFQ.
  177. GetRiskControlLibrary [1..1]    The purpose of the GetRiskControlLibrary is to enable an application to request specific RiskControlLibrary information from another business application module. The response to the GetRiskControlLibrary is the ShowRiskControlLibrary.
  178. GetRouting [1..1]    The purpose of the GetRouting is to communicate to a business application module or system a request for an existing Routing structure to be returned in a ShowRouting.
  179. GetSalesLead [1..1]    The purpose of the GetSalesLead is to enable an application to request a specific SalesLead information from one business application to another business application. The response to the GetSalesLead is the ShowSalesLead.
  180. GetSalesOrder [1..1]    The purpose of the Get SalesOrder is to enable a business application module to request information concerning a specific sales order from another business application. The reply to this BOD is the Show SalesOrder. There are several possible business applications in several environments that may use this capability. For example, a Sales Automation application may use this BOD to ask for information from a Customer Order application.
  181. GetSequenceSchedule [1..1]    Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application. The purpose of the GetSequenceSchedule is to enable a business applications module to request this SequenceSchedule information from another business application. The response to this BOD is ShowSequenceSchedule.
  182. GetShipment [1..1]    The purpose of the GetShipment is to enable an application to request specific Shipment information from another business application module. The response to the GetShipment is the ShowShipment.
  183. GetShipmentSchedule [1..1]    Commonly, the ship schedule is generated by a material planning application and transmitted to an order or material planning application. The purpose of the GetShipmentSchedule is to enable a business applications module to request this ShipmentSchedule information from another business application. The response to this BOD is ShowShipmentSchedule.
  184. GetShipmentUnit [1..1]    The purpose of the GetShipmentUnit is to enable an application to request specific ShipmentUnit information from another business application module. The response to the GetShipmentUnit is the ShowShipmentUnit.
  185. GetSplitWIP [1..1]    The purpose of the GetSplitWIP is to enable an application to request specific SplitWIP information from another business application module. The response to the GetSplitWIP is the ShowSplitWIP.
  186. GetSupplierPartyMaster [1..1]    The purpose of the GetSupplierPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases. The GetSupplierPartyMaster allows a business application to request information about a given party. The ShowSupplierPartyMaster is the response to this request providing the specific information requested.
  187. GetUOMGroup [0..1]    The purpose of the GetUOMGroup is to communicate to a business application component or module a request for an existingUOMGroup to be returned in a ShowUOMGroup. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to request alternate UOM information for one or more items.
  188. GetWIPStatus [1..1]    The purpose of the GetWIPStatus is to notify a Manufacturing Application of the progress of a production order at a point in time. The business environments most likely to require this capability are any type of manufacturing scenario where BODs for individual manufacturing transactions and events are not utilized. This BOD communicates what quantities of end product reside at which processing steps along with the time this snapshot view was taken. The response to this BOD is ShowWIPStatus.
  189. IssueMoveInventory [1..1]    The purpose of the IssueMoveInventory is to give the organization the ability to do a quantity movement of materials from one organizational unit to another organizational unit.
  190. ListActualLedger [1..1]    In an effort to simpilify the usage of the verbs the ListActualLedger BOD is being deprecated as of OAGIS 9.0, the ListActualLedger will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowActualLedger BOD which may serve the same function of the ListActualLedger BOD. The purpose of the ListActualLedger is to publish one or more summary listings of ledger information. This may be in response to a GetListActualLedger request or to published proactively as a listing of summary ledger information for a business event.
  191. ListBOM [1..1]    In an effort to simpilify the usage of the verbs the ListBOM BOD is being deprecated as of OAGIS 9.0, the ListBOM will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowBOM BOD which may serve the same function of the ListBOM BOD. The purpose of the ListBOM is to communicate one or more summary listings of BOM information to another business application component. This may be the result of a GetList request or it may be initiated by some other business event.
  192. ListInventoryCount [1..1]    In an effort to simpilify the usage of the verbs the ListInventoryCount BOD is being deprecated as of OAGIS 9.0, the ListInventoryCount will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowInventoryCount BOD which may serve the same function of the ListInventoryCount BOD. The purpose of the ListInventoryCount is the response to the GetListInventoryCount request for several occurrences of summary Inventory Count information from an ERP system. This count may be a cycle count or a physical count. This BOD may also apply to planned or unplanned inventory counts.
  193. ListItemMaster [1..1]    In an effort to simpilify the usage of the verbs the ListItemMaster BOD is being deprecated as of OAGIS 9.0, the ListItemMaster will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowItemMaster BOD which may serve the same function of the ListItemMaster BOD. The purpose of the ListItemMaster is to enable a business application module to respond to a GetListItemMaster request or to proactively send a listing of summary information about ITEMs to one or more other applications. There are many possible business applications in several environments that may use this capability. For example, a MRP, Inventory, or Manufacturing business application could use this to request item information. The picture below visualizes a possible use of this BOD.
  194. ListMaintenanceOrder [1..1]    In an effort to simpilify the usage of the verbs the ListMaintenanceOrder BOD is being deprecated as of OAGIS 9.0, the ListMaintenanceOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowMaintenanceOrder BOD which may serve the same function of the ListMaintenanceOrder BOD. The purpose of the ListMaintenanceOrder is to publish one or more summary listings of Maintenance Order information to other business application component. This may be in response to a GetListMaintenanceOrder request or to proactively publish a listing of summary Maintenance Order information for a business event. When a receiving application receives this BOD, the information can be used as is or it may be used to initiate a selection of a specific Maintenance Order through the GetMaintenanceOrder request. The processing is designed to provide multiple occurrences of summary data.
  195. ListPickList [1..1]    In an effort to simpilify the usage of the verbs the ListPickList BOD is being deprecated as of OAGIS 9.0, the ListPickList will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowPickList BOD which may serve the same function of the ListPickList BOD. The purpose of the ListPickList is to provide a list of Picking Lists from an ERP system to another application. This BOD may be initiated in response to a GetListPickList request or upon some business event. When a receiving application receives this BOD, the information can be used as is or it may be used to initiate a selection of a specific PickList through the GetPickList request. The processing is designed to provide multiple occurrences of summary data. This BOD will not usually cause updates to occur.
  196. ListProductionOrder [1..1]    In an effort to simpilify the usage of the verbs the ListProductionOrder BOD is being deprecated as of OAGIS 9.0, the ListProductionOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowProductionOrder BOD which may serve the same function of the ListProductionOrder BOD. The purpose of the ListProductionOrder is to enable an business software component to respond to a GetListProductionOrder request or to proactively send a listing of summary information about Production Orders to another business software component
  197. ListPurchaseOrder [1..1]    In an effort to simpilify the usage of the verbs the ListPurchaseOrder BOD is being deprecated as of OAGIS 9.0, the ListPurchaseOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowPurchaseOrder BOD which may serve the same function of the ListPurchaseOrder BOD. The purpose of the List PurchaseOrder is to send information relative to demand for goods or services to another business application. This may be in response to a GetList PurchaseOrder request, or it may be a notification vehicle, initiated upon an event in a business application. The List verb describes the behavior of supplying one or several documents in a summary format to the requesting business application. These listings of information may be supplied for Purchase Orders, PO Lines, or PO Sub-Lines. This BOD usually does not cause updates to occur and may be used as part of a larger integration scenario or as a single tool for communicating demand. There are many possible business applications in several environments that may use this capability. For example: 1. A PO application could use this BOD to send information to a Plant Data Collection application. 3. A MRP, Inventory or Manufacturing business application could use this to obtain order information.
  198. ListQuote [1..1]    In an effort to simpilify the usage of the verbs the ListQuote BOD is being deprecated as of OAGIS 9.0, the ListQuote will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowQuote BOD which may serve the same function of the ListQuote BOD. The purpose of the List Quote is to publish one or more summary listings of Quote information to other business application component. This may be in response to a GetListQuote request or to proactively publish a listing of summary Quote information for a business event.
  199. ListReceiveDelivery [1..1]    In an effort to simpilify the usage of the verbs the ListReceiveDelivery BOD is being deprecated as of OAGIS 9.0, the ListReceiveDelivery will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowReceiveDelivery BOD which may serve the same function of the ListReceiveDelivery BOD. The ListReceiveDelivery document may be used to obtain limited information listing about a expected (unreceived) or previously received goods deliveries that match certain selection criteria in a GetListReceiveDelivery request. Additional information about a specific ReceiveDelivery may be obtained through ShowReceiveDelivery by using the listing information to populate a GetReceiveDelivery request.
  200. ListRequisition [1..1]    In an effort to simpilify the usage of the verbs the ListRequisition BOD is being deprecated as of OAGIS 9.0, the ListRequisition will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowRequisition BOD which may serve the same function of the ListRequisition BOD. The purpose of the ListRequisition is to send information relative to demand for goods or services to another business application. This may be in response to a GetListRequisition request, or it may be a notification vehicle, initiated upon an event in a business application. The List verb describes the behavior of supplying one or several documents in a summary format to the requesting business application. These listings of information may be supplied for requisition documents, or requisition lines and/or requisition sub lines.
  201. ListRFQ [1..1]    In an effort to simpilify the usage of the verbs the ListRFQ BOD is being deprecated as of OAGIS 9.0, the ListRFQ will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowRFQ BOD which may serve the same function of the ListRFQ BOD. The purpose of the ListRFQ is to publish one or more summary listings of Request for RFQ information to other business application component. This may be in response to a GetListRFQ request or to proactively publish a listing of summary Request for RFQ information for a business event.
  202. ListRouting [1..1]    In an effort to simpilify the usage of the verbs the ListRouting BOD is being deprecated as of OAGIS 9.0, the ListRouting will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowRouting BOD which may serve the same function of the ListRouting BOD. The purpose of the ListRouting is to communicate one or more summary listings of Routing information to another business application component. This may be the result of a GetList request or it may be initiated by some other business event.
  203. ListSalesOrder [1..1]    In an effort to simpilify the usage of the verbs the ListSalesOrder BOD is being deprecated as of OAGIS 9.0, the ListSalesOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowSalesOrder BOD which may serve the same function of the ListSalesOrder BOD. The purpose of the List SalesOrder is to enable a business application module to respond to a GetList SalesOrder request or to proactively send a listing of summary information about sales orders to one or more other applications. This BOD does not usually cause updates to occur. It may be used as part of a large integration scenario or as a single tool for sending information concerning existing demands for goods or services. For example, a Customer Order application may use this BOD to respond to a request for information from a Sales Automation application.
  204. ListUOMGroup [0..1]    In an effort to simpilify the usage of the verbs the ListUOMGroup BOD is being deprecated as of OAGIS 9.0, the ListUOMGroup will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the ShowUOMGroup BOD which may serve the same function of the ListUOMGroup BOD. The purpose of the ListUOMGroup is to supply Unit-of-Measure Group summary information to another business application module. This may be the result of a GetListUOMGroup request or some initiated by some other business event. When a receiving application receives this BOD, the information can be used as is or it may be used to initiate a selection of a specific UOMGroup through the GetUOMGroup request. The processing is designed to provide multiple occurrences of summary data. This BOD usually does not cause updates to occur. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to request alternate UOM information for one or more items.
  205. LoadActualLedger [1..1]    The purpose of the LoadActualLedger is to enable an enterprise application to request detailed accounting ledger actual data.
  206. LoadBudgetLedger [1..1]    The purpose of the LoadBudgetLedger is to transmit budget amounts from all possible source applications throughout an enterprise to a general ledger or budget application.
  207. LoadInvoiceLedgerEntry [1..1]    In certain application suites, purchase order / invoice matching functionality exists in the purchasing application, while in other suites this functionality exists in the accounts payable application. The invoice matching process may include several document types, including the following: · Two way match - Purchase Order and the Invoice · Three way match - Purchase Order, Invoice, and the Receipt · Four way match - Purchase Order, Invoice, Receipt, and Inspection results Note: For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching. When matching takes place in the purchasing application, the accounts payable application may have to inform the purchasing application of the unapproved supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched if the invoice is initially entered into the accounts payable application. Note that in some situations, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters. The purpose of the LoadInvoiceLedgerEntry is to transmit data to create an unapproved open item in either a payables application or a purchasing application. The scope of the LoadInvoiceLedgerEntry indicates that the supplier's invoice has not yet been approved and the invoice is to be used as part of the invoice matching process. OAGIS has already defined the scenario for invoices that are approved for payment in a separate BOD namely LoadPayable.
  208. LoadMatchDocument [1..1]    In certain application suites, purchase order / invoice matching functionality exists in the purchasing application, while in other suites this functionality exists in the accounts payable application. The invoice matching process may include several document types, including the following: Two way match - Purchase Order and the Invoice Three way match - Purchase Order, Invoice, and the Receipt Four way match - Purchase Order, Invoice, Receipt, and Inspection results For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching. When matching takes place in the purchasing application, the accounts payable application may have to inform the purchasing application of the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched if the invoice is initially entered into the accounts payable application. Note that in some situations, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters. When matching takes place in the accounts payable application, the purchasing application must inform the accounts payable application of the purchasing transactions (purchase orders, goods receiving notes and inspection tickets) to which the invoice (in accounts payable) is to be matched. These integration scenarios have been developed for document matching to occur at the line level within the PuchaseOrder document and the Invoice document. This may be a one to one relationship, or it may be a many to one relationship from Invoice to PuchaseOrder or from the PuchaseOrder to the Invoice. Charges not associated with a specific Invoice line match be matched individually. The LoadMatchDocument is for use both by the accounts payable application and the purchasing application in exchanging the transactions that are required to be matched. Discussed in a later chapter are the UpdateMatchDocument. The purpose of UpdateMatchDocument is for the accounts payable application to send successful matching notification or a match fail.notification to a purchasing application.
  209. LoadPayable [1..1]    The purpose of the LoadPayable is to transmit data to create a payable open item in a payables application from the purchasing information generated in a purchasing application. The LoadPayable may also update the General Ledger, depending on the specific architecture of the financial applications. The scope of the LoadPayable indicates that the supplier's invoice is ready to be paid and has already been approved before the information moves to the accounts payable application. An approved invoice is also known as the voucher. OAGIS will define the scenario of invoices that get matched within the accounts payable application in a separate Business Service Request later. Some financial applications have the general ledger and accounts payable databases tightly integrated where updates to the accounts payable application are automatically reflected in the general ledger balances. The LoadPayable will transmit all information needed for both the accounts payable and the general ledger. Other applications allow the general ledger balances to be updated separately from the accounts payable. The second model illustrates that the combination of the LoadPayable and PostJournalEntry will accomplish this scenario.
  210. LoadProjectAccounting [1..1]    The purpose of the LoadProjectAccounting is to enable all relevant sub-systems that submit single sided transactions to send information to a Project Accounting Application. This would include, but not necessarily be limited to: · Accounts Payable · Accounts Receivable · Budget · Order Management · Purchasing · Time and Labor · Travel and Expense The LoadProjectAccounting will cause common data to be loaded in a project accounting application.
  211. LoadReceivable [1..1]    The purpose of the LoadReceiveable is to transmit data to create a receivable open item in a receivable application from the billing information generated in an order management application. The LoadReceiveable may also update the General Ledger, depending on the specific architecture of the accounting application. The scope of the LoadReceiveable is to create a BOD to recognize customer obligation (accounts receivable asset). Specific transactions include: 1. Sales Invoice 2. Credit Memo 3. Debit Memo 4. Charge Back The LoadReceiveable may also be used for transaction that do not originate from an order management application. The following two models illustrate that the LoadReceiveable may, in some cases, be adequate to update the financial applications, i.e., Receivables and General Ledger, and in other cases, will also require the PostJournal Business Object Document (BOD) to assure the General Ledger account balances are updated. In the model above, the receivable application is a sub-ledger of the general ledger. Updates to G/L balances occur via the receivables module, therefore the Load Receivable contains both receivable and general ledger transaction information.This other model illustrates the environment that sometime exists when General Ledger updates occur directly from the Order Management application. The reconciliation between the receivable and general ledger is a function within the financial applications and not of the integration space. This model allows the G/L balances to be updated in either detail or summarized form. The scope of the role of the receivable application includes functions such as: · Allowing Cash Application · Dunning · Dispute management
  212. PostCostingActivity [1..1]    In an effort to simpilify the usage of the verbs the PostCostingActivity BOD is being deprecated as of OAGIS 9.0, the PostCostingActivity will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS. As such for all new development we recommend that you use the PostCostingActivity BOD which may serve the same function of the PostCostingActivity BOD. The purpose of the PostCostingActivity BOD is to enable the update of Activityinformation from a production or manufacturing application to a costing application. This is necessary for applications that are based on a Dual Cycle Accounting model. This Dual Cycle Accounting model does not capture the details of the Activities that caused entries to be made in the general ledger application, but instead captures them in a separate overall costing application. This BOD commonly causes updates to occur and may be used as part of a large integration scenario or as a single tool for updating data. For Single Cycle accounting systems, the PostJournalEntry BOD will be used to ensure that the costing information flows from the Manufacturing Application to the Financial Application. In most cases either PostJournal or PostActivity will be used when the Financial applications are included with Logistics, but both Business Service Requests will not be used in the same integration scenario.
  213. PostJournalEntry [1..1]    The purpose of the PostJournal is to transmit data necessary to create a journal entry from any sub ledger business application to a general ledger application. Many applications in the enterprise environment create data that cause changes in the account balances of a general ledger application. Some components that have activity which will be reflected in a general ledger application are: 1. Benefits 2. Costing 3. Human Resources 4. Inventory Control 5. Manufacturing 6. Payroll 7. Production 8. Treasury By no means is this a complete list of all the components that create activity which generate a journal entry. Many tasks that occur within the enterprise applications cause the creation of a General Ledger journal entry. Tasks relate directly to the Component. For example, the adjustment of inventory value is a task that occurs within the Inventory Control Component. Some of the tasks that would be catalysts for changes in a general ledger include: 1. Receiving Inventory 2. Issuing Inventory 3. Transferring Inventory 4. Adjusting Inventory Value 5. Adjusting Inventory Count 6. Calculating Material Variances 7. Calculating Labor Variances 8. Calculating Overhead Variances
  214. PostMatchDocument [1..1]    The PostMatchDocument provides the ability to request an application/ system to create a MatchDocument
  215. ProcessAllocateResource [1..1]    The purpose of the ProcessAllocateResource is to notify a Manufacturing Application of the use of required labor or machine time on a production order making a product. The business environments most likely to require this capability are any type of manufacturing scenario. This BOD communicates what machine was utilized or which person performed the work and their labor skill class, along with the amount of time worked and at what time this event occurred.
  216. ProcessConfirmWIP [1..1]    The purpose of the ProcessConfirmWIP is to respond to a request for the data necessary to perform a confirmation of the movement of WIP (Work in Progress).
  217. ProcessCredit [1..1]    The purpose of the ProcessCredit is for the order management application to request credit data for a trading partner from the credit management function. The ProcessCredit does not imply any update, it is only an inquiry function. The ShowCredit discussed in the next chapter will be the response back to the order management application. Discussed in a later chapter is the UpdateCredit. The UpdateCredit may be used in both directions between the order management and the accounts receivable application. Its purpose is to keep order, shipment and open item amounts current. Finally, the ChangeCreditStatus is used to update the order management application with any changes in business status for a particular trading partner.
  218. ProcessCreditStatus [1..1]    The ProcessCreditStatus provides the ability to request an application/ system to create a CreditStatus
  219. ProcessCreditTransfer [1..1]    The purpose of the ProcessCreditTransfer is to enable an application to request specific CreditTransfer information from another business application module. The response to the ProcessCreditTransfer is the ProcessCreditTransfer.
  220. ProcessCreditTransferIST [1..1]    The purpose of the ProcessCreditTransferIST is to enable an application to request specific CreditTransferIST information from another business application module. The response to the ProcessCreditTransferIST is the ProcessCreditTransferIST.
  221. ProcessDebitTransfer [1..1]    The purpose of the ProcessDebitTransfer is to enable an application to request specific DebitTransfer information from another business application module. The response to the ProcessDebitTransfer is the ProcessDebitTransfer.
  222. ProcessDebitTransferIST [1..1]    The purpose of the ProcessDebitTransferIST is to enable an application to request specific DebitTransferIST information from another business application module. The response to the ProcessDebitTransferIST is the ProcessDebitTransferIST.
  223. ProcessDispatchList [1..1]    The ProcessDispatchList provides the ability to request an application/ system to create a DispatchList
  224. ProcessEmployeeWorkTime [1..1]    The purpose of the ProcessEmployeeWorkTime is to Process work time information for an employee from a data collection application to an ERP Human Resource application.
  225. ProcessEngineeringChangeOrder [1..1]    The ProcessEngineeringChangeOrder provides the ability to request an application/ system to create an EngineeringChangeOrder
  226. ProcessEngineeringWorkDocument [1..1]    The purpose of the ProcessEngineeringWorkDocument is to enable an application to provide EngineeringWorkDocument from another business application module. The ProcessEngineeringWorkDocument is provided in a a publishe/subscribe or broadcast buiness exchange where an application other than the owner or the master of the given information provides it to the business applications that owns the data in order to have it process or perform a function with the information.
  227. ProcessInspectDelivery [1..1]    The purpose of the ProcessInspectDelivery is to supply InspectDelivery information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example; 1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information. 3. A Laboratory Information System could send quality information to an Inventory application, 4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
  228. ProcessInventoryBalance [1..1]    The purpose of the ProcessInventoryBalance is to enable the communicate the need of processing of InventoryBalance data that exists on separate Inventory systems, where the two systems are peers. This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure. This is data that describes the ITEM as it exists at a specific location.
  229. ProcessInventoryConsumption [1..1]    The purpose of the ProcessInventoryConsumption is to inform a seller or provider about InventoryConsumption of items.
  230. ProcessInventoryCount [1..1]    The purpose of the ProcessInventoryCount is to transmit an inventory count to ERP from the actual physical inventory location. This count may be a cycle count or a physical count. This BOD may also apply to planned or unplanned inventory counts.
  231. ProcessInvoice [1..1]    The purpose of the ProcessInvoice is to transmit an invoice from a supplier to a customer. Indicating that the receiver of the Invoice is to Process the Invoice for payment.
  232. ProcessIssueInventory [1..1]    The purpose of the ProcessIssueInventory is to reflect an unplanned issue of an item to a miscellaneous location. Possible reasons for this include: 1. Somebody broke the material, 2. The material is defective and needs replacing, 3. The material is used up and needs replenishment.
  233. ProcessMaintenanceOrder [1..1]    The ProcessMaintenanceOrder provides the ability to request an application/ system to create a MaintenanceOrder
  234. ProcessMergeWIP [1..1]    The purpose of the ProcessMergeWIP BOD is to notify a Manufacturing Application of the creation of a single production lot from multiple production lots of a product being made on a production order. The business environment most likely to require this capability is a lot based discrete manufacturing scenario. This BOD communicates the originating lots, the resulting lot, lot quantities, and the processing step at which this event occurred, along with the time at which this event occurred.
  235. ProcessMoveInventory [1..1]    The purpose of the ProcessMoveInventory is to give the organization the ability to do a quantity movement of materials from one organizational unit to another organizational unit.
  236. ProcessMoveWIP [1..1]    The purpose of the ProcessMoveWIP is to notify a Manufacturing Application of the progression through the production processing steps or operations of a product being made on a production order. The business environments most likely to require this capability are any type of manufacturing scenario. This BOD communicates which processing step the product is coming from and which step it is being moved to, along with the quantity moving and the time this event occurred. This BOD assumes that the applications involved in this business scenario will have already synchronized the production item and its BOM/Routing information.
  237. ProcessOnlineOrder [1..1]    The purpose of the ProcessOnlineOrder is to enable an application to provide online shopping OnlineOrders from another business application module. The ProcessOnlineOrder is provided in a a publishe/subscribe or broadcast buiness exchange where an application other than the owner or the master of the given information provides it to the business applications that owns the data in order to have it process or perform a function with the information.
  238. ProcessOperation [1..1]    The purpose of the ProcessOperation is to enable an application to provide online shopping Operations from another business application module. The ProcessOperation is provided in a a publishe/subscribe or broadcast buiness exchange where an application other than the owner or the master of the given information provides it to the business applications that owns the data in order to have it process or perform a function with the information.
  239. ProcessOpportunity [1..1]    The purpose of the ProcessOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The ProcessOpportunity is provided in a a publishe/subscribe or broadcast buiness exchange where an application other than the owner or the master of the given information provides it to the business applications that owns the data in order to have it process or perform a function with the information.
  240. ProcessPaymentStatus [1..1]    The purpose of the ProcessPaymentStatus is to enable an application to request specific PaymentStatus information to be processed by another business application module. This typically a transaction that occurs between a company and a Bank in order to remit PaymentStatus to company that has provided goods or services. The response to the ProcessPaymentStatus is the AcknowledgePaymentStatus.
  241. ProcessPaymentStatusIST [1..1]    The purpose of the ProcessPaymentStatusIST is to enable an application to request specific PaymentStatusIST information to be processed by another business application module. This typically a transaction that occurs between a company and a Bank in order to remit PaymentStatusIST to company that has provided goods or services. The response to the ProcessPaymentStatusIST is the AcknowledgePaymentStatusIST.
  242. ProcessPickList [1..1]    The purpose of the ProcessPickList is to Process the details of an individual Picking List from a plant level to an ERP system. This BOD will usually cause Processs to occur.
  243. ProcessProductAvailability [1..1]    The purpose of the ProcessProductAvailability is to enable an application or component to request the reservations for products from another business application or component. The response to the ProcessProductAvailability is the ListProductAvailability. The ProcessProductAvailability also enables the retrieval of information across several documents by using selection fields. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  244. ProcessProductionOrder [1..1]    The ProcessProductionOrder provides the ability to request an application/ system to create a ProductionOrder
  245. ProcessPurchaseOrder [1..1]    The purpose of the Process PurchaseOrder Business Object Document is to transmit a purchase order to a supplier's order management application.
  246. ProcessQuote [1..1]    The ProcessQuote provides the ability to request an application/ system to create a Quote
  247. ProcessReceiveDelivery [1..1]    The ProcessReceiveDelivery provides the ability to request an application/ system to create a ReceiveDelivery
  248. ProcessReceiveItem [1..1]    The purpose of the ProcessInventoryTransfer is to give the organization the ability to do a quantity movement of materials from one organizational unit to another organizational unit.
  249. ProcessRecoverWIP [1..1]    The purpose of the ProcessRecoverWIP is to notify a Manufacturing Application of the creation of usable production materials from material previously considered to be unsuitable for production use. This is most often likely to represent a return to production of scrap material. The business environments most likely to require this capability are any type of manufacturing scenario. This BOD communicates what is being recovered, the quantity being recovered, and the processing step at which the recovered material is to re-enter the production process, along with the time at which this event occurred.
  250. ProcessRequireProduct [1..1]    The ProcessRequireProduct provides the ability to request an application/ system to create a RequireProduct
  251. ProcessRequisition [1..1]    The ProcessRequisition provides the ability to request an application/ system to create a Requisition
  252. ProcessRFQ [1..1]    The ProcessRFQ provides the ability to request an application/ system to create a RFQ
  253. ProcessRiskControlLibrary [1..1]    The purpose of the ProcessRiskControlLibrary is to notify a Manufacturing Application of the creation of usable production materials from material previously considered to be unsuitable for production use. This is most often likely to represent a return to production of scrap material. The business environments most likely to require this capability are any type of manufacturing scenario. This BOD communicates what is being recovered, the quantity being recovered, and the processing step at which the recovered material is to re-enter the production process, along with the time at which this event occurred.
  254. ProcessSalesLead [1..1]    The purpose of the ProcessSalesLead is to enable an application to provide SalesLead information from one business application to another business application. The ProcessSalesLead is provided in a a publishe/subscribe or broadcast buiness exchange where an application other than the owner or the master of the given information provides it to the business applications that owns the data in order to have it process or perform a function with the information.
  255. ProcessSalesOrder [1..1]    The ProcessSalesOrder provides the ability to request an application/ system to create a SalesOrder
  256. ProcessShipment [1..1]    The ProcessShipment provides the ability to request an application/ system to create a Shipment
  257. ProcessShipmentUnit [1..1]    The purpose of the ProcessShipmentUnit is to enable an application to provide a ShipmentUnit information from another business application module in order for that module to perform the task at hand.. The ProcessShipmentUnit is typically published from the business application that is is requesting that the master or owner of the ShipmentUnit information to process the contained update. This may also occur across enterprises. The respons to the ProcessShipmentUnit is the AcknowledgeShipmentUnit to indicate success or failure. If the receiving system needs to make changes to the ShipmentUnit then the ChangeShipmentUnit can be used a coresponding RespondShipmentUnit accepts the changes or indicates additional changes.
  258. ProcessSplitWIP [1..1]    The purpose of the ProcessSplitWIP is to notify a Manufacturing Application of the creation of multiple production lots from a single production lot of a product being made on a production order. The business environment most likely to require this capability is a lot based discrete manufacturing scenario. This BOD communicates the originating lot, the resulting lots, their quantities, and the processing step at which this event occurred, along with the time at which this event occurred.
  259. ProcessWIPStatus [1..1]    The purpose of the Process WIPStatus is to enable an application or component to process a change to the WIPStatus. An AcknowledgeWIPStatus maybe provided as a result of this processing to report the results.
  260. ReceiveMoveInventory [1..1]    The purpose of the ReceiveMoveInventory is to give the organization the ability to do a quantity movement of materials from one organizational unit to another organizational unit.
  261. ReceiveProductionOrder [1..1]    ReceiveProductionOrder is being deprecated as of OAGIS 9.0. ReceiveProductionOrder will be made available for the next three releases. OAGi recommend using ProcessProductionOrder for all new development. The environment for this BOD can be within the enterprise or outside the enterprise. The purpose of the ReceiveProductionOrder is to supply information which the ERP system requires to do receipt posting against a Production Order.
  262. ReceivePurchaseOrder [1..1]    ReceivePurchaseOrder is being deprecated as of OAGIS 9.0. ReceivePurchaseOrder will be made available for the next three releases. OAGi recommend using ProcessReceiveItem for all new development. The purpose of the Receive PurchaseOrder is to supply the information that a business application module requires to do receipt posting to against a Purchase Order. There are several possible business applications in several environments that may use this capability. This BOD may be used individually, or as part of a larger interface scenario.
  263. RespondConfirmWIP [1..1]    The purpose of the RespondConfirmWIP is to respond to a request for the data necessary to perform a confirmation of the movement of WIP (Work in Progress).
  264. RespondCredit [1..1]    The purpose of the RespondCredit is to Respond the Credit Management functionality within the customer order management or the accounts receivable application. The RespondCredit will also transmit changes in the accounts receivable open item balances to the credit management function of the customer order management application.
  265. RespondCreditStatus [1..1]    The purpose of the RespondCreditStatus is to supply CreditStatus information to another business application module.
  266. RespondDispatchList [1..1]    The purpose of the RespondDispatchList is to communicate the response to a DispatchList message from one business application to one or more other business applications
  267. RespondEmployeeWorkTime [1..1]    The purpose of the RespondEmployeeWorkTime is to Respond work time information for an employee from a data collection application to an ERP Human Resource application.
  268. RespondEngineeringChangeOrder [1..1]    The purpose of the RespondEngineeringChangeOrder is to communicate the response to a EngineeringChangeOrder message from one business application to one or more other business applications
  269. RespondEngineeringWorkDocument [1..1]    The purpose of the RespondEngineeringWorkDocument is to enable an application to provide EngineeringWorkDocument from another business application module. The RespondEngineeringWorkDocument is the response to the Change provides a response to the request to change the original Process.
  270. RespondInspectDelivery [1..1]    The purpose of the RespondInspectDelivery is to supply InspectDelivery information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example; 1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information. 3. A Laboratory Information System could send quality information to an Inventory application, 4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
  271. RespondInventoryBalance [1..1]    The purpose of the ChangeInventoryBalance is to enable the communication of a Change in the InventoryBalance data that exists on separate Inventory databases. This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure. This is data that describes the ITEM as it exists at a specific location. It is
  272. RespondInvoice [1..1]    The purpose of the RespondInvoice is to communicate the response to a Invoice message from one business application to one or more other business applications
  273. RespondMaintenanceOrder [1..1]    The purpose of the RespondMaintenanceOrder is to communicate the response to a MaintenanceOrder message from one business application to one or more other business applications
  274. RespondOnlineOrder [1..1]    The purpose of the RespondOnlineOrder is to enable an application to provide online shopping OnlineOrders from another business application module. The RespondOnlineOrder is the response to the Change provides a response to the request to change the original Process.
  275. RespondOpportunity [1..1]    The purpose of the RespondOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The RespondOpportunity is the response to the Change provides a response to the request to change the original Process.
  276. RespondPickList [1..1]    The purpose of the RespondPickList is to Respond the details of an individual Picking List from a plant level to an ERP system. This BOD will usually cause Responds to occur.
  277. RespondProductionOrder [1..1]    The purpose of the RespondProductionOrder is to communicate the response to a ProductionOrder message from one business application to one or more other business applications
  278. RespondPurchaseOrder [1..1]    The purpose of the RespondPurchaseOrder is to communicate the response to a PurchaseOrder message from one business application to one or more other business applications
  279. RespondQuote [1..1]    The purpose of the RespondQuote is to communicate from one business application to one or more other business applications that a additional data related to a quote has been added or needs to be added, depending on the business case.
  280. RespondReceiveDelivery [1..1]    The RespondReceiveDelivery may be used to update the Respondr's internal receiving and order management business applications to indicate that the requested material has arrived, including any unexpected quantity, condition or other exception discrepancies. The RespondReceiveDelivery supports receiving at either the line item level and/or the ship unit level. Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents.
  281. RespondRequireProduct [1..1]    The purpose of the RespondRequireProduct is to communicate the response to a RequireProduct message from one business application to one or more other business applications
  282. RespondRequisition [1..1]    The purpose of the RespondRequisition is to communicate the response to a Requisition message from one business application to one or more other business applications
  283. RespondRFQ [1..1]    The purpose of the RespondRFQ is to communicate from one business application to one or more other business applications that additional data related to a Request for Quote is available.
  284. RespondSalesLead [1..1]    The purpose of the RespondSalesLead is to enable an application to provide SalesLead information from one business application to another business application. The RespondSalesLead is the response to the Change provides a response to the request to change the original Process.
  285. RespondSalesOrder [1..1]    The purpose of the RespondSalesOrder is to communicate the response to a SalesOrder message from one business application to one or more other business applications
  286. ShowActualLedger [1..1]    The purpose of the ShowActualLedger is to communicate to an enterprise application the sending systems representation of ledger information specifically requested. This may be in response to a GetActualLedger request or to proactively publish a listing of ledger information for a business event.
  287. ShowAllocateResource [1..1]    The purpose of the ShowAllocateResource is to supply AllocateResource information to another business application module.
  288. ShowBOM [1..1]    The purpose of the ShowBOM is to supply Item Bill of Material information to another business application module. This BOD may also be initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate Item Bill of Material information.
  289. ShowBudgetLedger [1..1]    The purpose of the ShowBudgetLedger is to receive budget amounts from all possible source applications throughout an enterprise to a general ledger or budget application. In response to a request for them in the form of a GetBudgetLedger.
  290. ShowCarrierRoute [1..1]    The purpose of the ShowCarrierRoute is to enable an application to provide a specific Carrier Route information from another business application module. The response to the GetCarrierRoute is the ShowCarrierRoute.
  291. ShowCatalog [1..1]    The purpose of the ShowCatalog is to supply a business application module or system with requested catalog information. In communicating Catalog information, the ShowCatalogmay cause other information to be coordinated including, but not limited to · Item Identifiers · Specifications · Pricing Information agreed on either · Purchase Agreements · Price Lists · Availability and Delivery Information · Related Items and accessories There are many possible business applications in several environments that may use this capability. Some examples of usage scenarios are: · Manufacturer exchanging catalogs with distributors/ suppliers/ e-marketplaces · Distributors/ Suppliers/ e-marketplaces exchanging catalogs with Buyers or other trading partners It may also be necessary to support Component Supplier Management (CSM) scenarios. In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog.
  292. ShowChartOfAccounts [1..1]    The purpose of the ShowChartOfAccounts is to supply ChartOfAccounts information to another business application module.
  293. ShowConfirmWIP [1..1]    The purpose of the ShowConfirmWIP is to respond to a request for the data necessary to perform a confirmation of the movement of WIP (Work in Progress).
  294. ShowCostingActivity [1..1]    The purpose of the ShowCostingActivity is to supply CostingActivity information to another business application module.
  295. ShowCredit [1..1]    The purpose of the ShowCredit is to provide credit information concerning a trading partner. The ShowCredit is the reply required by the GetCredit BOD. This BOD type may also be used as an information mechanism that is triggered by a business event and not a Get request.
  296. ShowCreditStatus [1..1]    The purpose of the ShowCreditStatus is to supply CreditStatus information to another business application module.
  297. ShowCreditTransfer [1..1]    The purpose of the ShowCreditTransfer is to enable an application to request specific CreditTransfer information from another business application module. The response to the ShowCreditTransfer is the ShowCreditTransfer.
  298. ShowCreditTransferIST [1..1]    The purpose of the ShowCreditTransferIST is to enable an application to request specific CreditTransferIST information from another business application module. The response to the ShowCreditTransferIST is the ShowCreditTransferIST.
  299. ShowCurrencyExchangeRate [1..1]    The purpose of the ShowCurrencyExchangeRate is to supply CurrencyExchangeRate information to another business application module.
  300. ShowCustomerPartyMaster [1..1]    The ShowCustomerPartyMaster is the response to the GetCustomerPartyMaster request.
  301. ShowDebitTransfer [1..1]    The purpose of the ShowDebitTransfer is to enable an application to request specific DebitTransfer information from another business application module. The response to the ShowDebitTransfer is the ShowDebitTransfer.
  302. ShowDebitTransferIST [1..1]    The purpose of the ShowDebitTransferIST is to enable an application to request specific DebitTransferIST information from another business application module. The response to the ShowDebitTransferIST is the ShowDebitTransferIST.
  303. ShowDispatchList [1..1]    The purpose of the ShowDispatchList is to communicate to a business application module or system the sending systems representation of dispatch list (finite schedule) information. This request may be used as a response to a GetDispatchList request or as a push notification of an event.
  304. ShowEmployeeWorkSchedule [1..1]    The purpose of the ShowEmployeeWorkSchedule is to supply EmployeeWorkSchedule information to another business application module.
  305. ShowEmployeeWorkTime [1..1]    The purpose of the ShowEmployeeWorkTime is to supply EmployeeWorkTime information to another business application module.
  306. ShowEngineeringChangeOrder [1..1]    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.
  307. ShowEngineeringWorkDocument [1..1]    The purpose of the ShowEngineeringWorkDocument is to enable an application to provide a specific EngineeringWorkDocument from another business application module. The response to the GetEngineeringWorkDocument is the ShowEngineeringWorkDocument.
  308. ShowField [1..1]    The purpose of the ShowField is to supply Field information to another business application module.
  309. ShowInspectDelivery [1..1]    The purpose of the ShowInspectDelivery is to supply InspectDelivery information to another business application module.
  310. ShowInventoryBalance [1..1]    The purpose of the ShowInventoryBalance is to supply InventoryBalance information to another business application module.
  311. ShowInventoryConsumption [1..1]    The most common use of the ShowInventoryConsumption is to share a buyer's usage information about an item or product with the supplier of such item or product. This BOD will not create or update either buyer's or supplier's inventory records. The receiver of the request is responsible to make effective use of this information. The BOD can be used in the following ways: (1) for a buyer of goods to inform the supplier that goods have been consumed, and replenishment will likely be required; (2) for a retailer to inform the vendor that retail sales of goods have been made; and (3) for plant data collection systems and warehouse management systems to inform inventory systems that goods have been consumed and inventory records should be adjusted accordingly. This is an outline of the business flow that this BOD supports: (1) Overall purchase, replenishment or vendor managed inventory agreement is in place. (2) Message is sent to supplier, distributor or third party logistics provider, that material has been consumed. This is done in response to events such as these, depending on implementation context: · Material is replenished to line side at manufacturing facitliy. · Material is assembled into final product. · Material is purchased and removed from facility by customer. (3) Supplier, distributor, third party logistics provider replenishes material, using information provided in the ShowInventoryConsumption message, the demand and shipment forecasts, and the terms of the overall purchase or vendor managed inventory agreement.
  312. ShowInventoryCount [1..1]    The purpose of the ShowInventoryCount is to response to the Get request an occurrences of a Inventory Count information from an ERP system. This count may be a cycle count or a physical count. This BOD may also apply to planned or unplanned inventory counts.
  313. ShowInvoice [1..1]    The purpose of the ShowInvoice is to transmit an invoice from a supplier to a customer. This BOD may be used as a response to a GetInvoice request or as a push notification of an event
  314. ShowInvoiceLedgerEntry [1..1]    The purpose of the ShowInvoiceLedgerEntry is to supply InvoiceLedgerEntry information to another business application module.
  315. ShowIssueInventory [1..1]    The purpose of the ShowIssueInventory is to supply inventory issue information against an order, from an ERP system into a PDC system to confirm the IssueInventory transaction (BOD).
  316. ShowItemMaster [1..1]    The purpose of the ShowItemMaster is to supply ITEM Information to another business application module. This request may be used as a response to a GetItemMaster request or as the result of some other business event. This BOD does not usually cause updates to occur. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to request item information.
  317. ShowJournalEntry [1..1]    The purpose of the ShowJournalEntry is to enable an application or component to request a JournalEntry document from another business application or component. The response to the ShowJournalEntry is is the ListJournalEntry. The ShowJournalEntry also enables the retrieval of information across several documents by using selection fields. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  318. ShowLocation [1..1]    The purpose of the ShowLocation is to supply Location information to another business application module.
  319. ShowLocationService [1..1]    The purpose of ShowLocationService is to enable a mechanism to ensure that the physical locations owned by the business applications are validated, geocoded, and standardized based on information returned by location service providers. This BOD may be initiated by the sending system upon some event occurring, such as receiving a request submitted by another system for certain location service. There are many possible business applications in several environments that may use this capability. For example, the customer management, the supplier management, or HRMS business applications could use this to receive processed location information from location service providers.
  320. ShowMaintenanceOrder [1..1]    The purpose of the ShowMaintenanceOrder is to communicate to a business application module or system the sending systems representation of maintenance order information. This request may be used as a response to a GetMaintenanceOrder request or as a push notification of an event.
  321. ShowMatchDocument [1..1]    In certain application suites, purchase order / invoice matching functionality exists in the purchasing application, while in other suites this functionality exists in the accounts payable application. The invoice matching process may include several document types, including the following: Two way match - Purchase Order and the Invoice Three way match - Purchase Order, Invoice, and the Receipt Four way match - Purchase Order, Invoice, Receipt, and Inspection results For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching. When matching takes place in the purchasing application, the accounts payable application may have to inform the purchasing application of the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched if the invoice is initially entered into the accounts payable application. Note that in some situations, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters. When matching takes place in the accounts payable application, the purchasing application must inform the accounts payable application of the purchasing transactions (purchase orders, goods receiving notes and inspection tickets) to which the invoice (in accounts payable) is to be matched. These integration scenarios have been developed for document matching to occur at the line level within the PurchaseOrder document and the Invoice document. This may be a one to one relationship, or it may be a many to one relationship from Invoice to PurchaseOrder or from the PurchaseOrder to the Invoice. Charges not associated with a specific Invoice line match be matched individually. The purpose of the ShowMatchDocument is to enable the accounts payable application and the purchasing application to exchange information required either by request or initiated by some business event.
  322. ShowMergeWIP [1..1]    The purpose of the ShowMergeWIP is to supply MergeWIP information to another business application module.
  323. ShowMoveInventory [1..1]    The purpose of the ShowMoveInventory is to enable an application or component to request an MoveInventory document from another business application or component. The response to the ShowMoveInventory is is the ListMoveInventory. The ShowMoveInventory also enables the retrieval of information across several documents by using selection fields. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  324. ShowMoveWIP [1..1]    The purpose of the ShowMoveWIP is to supply MoveWIP information to another business application module.
  325. ShowOnlineOrder [1..1]    The purpose of the ShowOnlineOrder is to enable an application to request specific online shopping OnlineOrder from another business application module. The response to the GetOnlineOrder is the ShowOnlineOrder.
  326. ShowOnlineSession [1..1]    The purpose of the ShowOnlineSession is to enable an application to request specific online OnlineSession from another business application module. The response to the GetOnlineSession is the ShowOnlineSession.
  327. ShowOperation [1..1]    The purpose of the ShowOperation is to enable an application to request specific online shopping Operation from another business application module. The response to the GetOperation is the ShowOperation.
  328. ShowOpportunity [1..1]    The purpose of the ShowOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The response to the GetOpportunity is the ShowOpportunity.
  329. ShowPartyMaster [1..1]    ShowPartyMaster is the response to a request for information about a PartyMaster. The request is provided as the GetPartyMaster.
  330. ShowPayable [1..1]    ShowPayable is the response to a request for information about Payables. The request is provided by the GetPayable BOD.
  331. ShowPaymentStatus [1..1]    The purpose of the ShowPaymentStatus is to enable an application to respond with specific PaymentStatus information from another business application module. This typically a transaction that occurs between a company and a Bank in order to remit PaymentStatus to company that has provide goods or services. This tpically provided in response to the GetPaymentStatus.
  332. ShowPaymentStatusIST [1..1]    The purpose of the ShowPaymentStatusIST is to enable an application to respond with specific PaymentStatusIST information from another business application module. This typically a transaction that occurs between a company and a Bank in order to remit PaymentStatusIST to company that has provide goods or services. This tpically provided in response to the GetPaymentStatusIST.
  333. ShowPersonnel [1..1]    The purpose of the ShowPersonnel is to provide Personnel data for a worker to a requesting business application. This BOD may be in response to a GetPersonnel request, or it may be triggered by a business event.
  334. ShowPickList [1..1]    The purpose of the ShowPickList is to show the details of an individual Picking List from an ERP system. This BOD may be sent in response to a GetPickList or it may be initiated upon some business event.
  335. ShowPlanningSchedule [1..1]    Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party. Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional Data Type PlanningScheduleException. Customers can use this PlanningSchedule to communicate demand requirement in three different ways. It can be as specific as the Item level or at the Commodity code level, which is higher than item. Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional component FeatureValues. The purpose of the ShowPlanningSchedule is to communicate to a business application module or system the sending systems representation of PlanningSchedule information. This request may be used as a response to a GetPlanningSchedule request or as a push notification of an event.
  336. ShowPriceList [1..1]    The purpose of the ShowPriceList is to supply a business application module or system with information concerning new or existing product price lists. 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 Manufacturing, distributor or reseller business application could use this to communicate the price change or request a price list. It may also be necessary to support Component Supplier Management (CSM) scenarios. In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog. A customer purchases the product from the Catalog provider. They have the capability to do comparison shopping from the catalog. Supplier Certification may be provided by the Catalog provider. This definition of price list is intended to support simple pricing scenario, especially pricing that may accompany a published price list. It is not intended to support complex pricing environments that may be needed to support features such as; · Deals and Promotions · Coupons and Sales Incentives · Rebates and Accruals This functionality will be addressed in a subsequent release. It is a working assumption that the representation of complex qualifications, coupons and sales incentives are rarely communicated between systems.
  337. ShowProductAvailability [1..1]    The purpose of the ShowProductAvailability is to respond to a GetProductAvailability request or to initiate the passing of product availability data from a Production or Available to Promise (ATP) business application to an Order Management business application. The business process scenario is the Order Management application interacting with the Available to Promise or Production application in order to determine availability of a product for the customer. This scenario is commonly referred to as Make to Order or Build to Order.
  338. ShowProductionOrder [1..1]    The purpose of the ShowProductionOrder is to supply Production Order information to another business application module.
  339. ShowProjectAccounting [1..1]    The purpose of the ShowProjectAccounting is to supply ProjectAccounting information to another business application module.
  340. ShowProjectMaster [1..1]    The purpose of the ShowProjectMaster is to supply ProjectMaster information to another business application module.
  341. ShowPurchaseOrder [1..1]    The purpose of the Show PurchaseOrder is to supply Purchase Order Information to another business application module. This request may be used as a response to a Get PurchaseOrder request or as a push notification of an event. There are many possible business applications in several environments that may use this capability. Examples include: 1. A Order Management application could use this BOD to send information to a Plant Data Collection application. 2. An MRP, Inventory or Manufacturing business application could use this to obtain order information. 3. The Order Management application can notify the MRP/Inventory application when a vendor gives or changes a promise day.
  342. ShowQuote [1..1]    The purpose of the ShowQuote is to communicate to a business application module or system the sending systems representation of Quote information. This request may be used as a response to a GetQuote request.
  343. ShowReceivable [1..1]    The purpose of the ShowReceivable is to supply Receivable information to another business application module.
  344. ShowReceiveDelivery [1..1]    The ShowReceiveDelivery may be used to obtain information about a specific expected (unreceived) or previously received goods delivery. The ShowReceiveDelivery may be issued in response to a GetReceiveDelivery request, or emitted asynchronously for notification upon some business event. For expected deliveries, the ShowReceiveDelivery document content may act as a receiving template or checklist to identify the quantity and shipping configuration of the expected goods. In this manner the ShowReceiveDelivery may be considered logically equivalent to the Advance Ship Notice information in a ShowShipment document. This similarity is by design, as the receiver's ShowReceiveDelivery may be directly derived from shipper's ShowShipment content after the receiver's business logic has appropriately validated the Advance Ship Notification information. The ShowReceiveDelivery supports describing shipment content at either the line item level and/or the ship unit level. Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents.
  345. ShowReceiveItem [1..1]    The purpose of the ShowReceiveItem is to enable an application or component to request an ReceiveItem document from another business application or component. The response to the ShowReceiveItem is is the ListReceiveItem. The ShowReceiveItem also enables the retrieval of information across several documents by using selection fields. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
  346. ShowRecoverWIP [1..1]    The purpose of the ShowRecoverWIP is to supply RecoverWIP information to another business application module.
  347. ShowRequireProduct [1..1]    The purpose of the ShowRequireProduct is to supply RequireProduct information to another business application module.
  348. ShowRequisition [1..1]    The purpose of the ShowRequisition is to send information relative to demand for goods or services to another business application. This may be in response to a GetRequisition request, or it may be a notification vehicle, initiated upon an event in a business application.
  349. ShowRFQ [1..1]    The purpose of the ShowRFQ is to communicate to a business application module or system the sending systems representation of Request for Quote information. This request may be used as a response to a GetRFQ request.
  350. ShowRiskControlLibrary [1..1]    The purpose of the ShowRiskControlLibrary is to supply RiskControlLibrary information to another business application module.
  351. ShowRouting [1..1]    The purpose of the ShowRouting is to communicate to a business application module or system the relevant information about a specific Routing. The Show Routing is in response to a GetRouting request.
  352. ShowSalesLead [1..1]    The purpose of the ShowSalesLead is to enable an application to provide SalesLead information from one business application to another business application. The response to the GetSalesLead is the ShowSalesLead.
  353. ShowSalesOrder [1..1]    The purpose of the Show SalesOrder is to supply Sales Order Information to another business application module. This request may be used as a response to a Get Salesorder request or as a push notification of an event. This BOD does not usually cause updates to occur.
  354. ShowSequenceSchedule [1..1]    Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application. The purpose of the ShowSequenceSchedule is to communicate to a business application module or system the sending systems representation of SequenceSchedule information. This request may be used as a response to a GetSequenceSchedule request or as a push notification of an event.
  355. ShowShipment [1..1]    A Shipment is a business document that details the intent to transport a specific quantity of material goods from a supplier to a single customer business partner destination. The Shipment has been modeled after similar proprietary documents on popular business software packages (SAP's Delivery Note, Oracle Applications' Delivery document, etc.) A Shipment is typically derived from the shipping schedule associated with a customer's purchase or sales order, once overall demand and various other business factors which prioritize the availability of the supplier's goods inventory have been evaluated. The Shipment document is designed to have a dynamic structure and content. Initial shipment planning information can be updated and significant detail (actual picked inventory attributes, ship unit packaging, etc.) may be added during the execution phase of the supplier's order fulfillment and shipping business processes. The final form of the Shipment document can provide detail about the carrier and level of service used to transport the material, the exact quantity and attributes of the material shipped, and how that material is physically packaged and identified for transport. To aid the customer's planning and receiving business processes, the supplier may transmit the final Shipment document to customer in advance so that they can prepare for carrier arrival and then efficiently accept and utilize the ordered material. In this use case, the Shipment document may function as a traditional Advance Ship Notice (ASN). A ShipUnit is a data element that identifies and describes a specific collection of goods inventory that is packaged by a supplier for carrier transportation to a customer business partner destination. A ShipUnit is generally the smallest "thing" that can be individually moved and tracked throughout a carrier's transportation network. The physical size, inventory, content and internal nested container complexity within a ShipUnit is arbitrary. The ShipUnit component was specifically designed to be transportation mode independent. It may be used to represent any uniquely identifiable and trackable assembly, container or vessel including, but not limited to: a parcel express package; a pallet of identical or mixed items; a truck trailer, rail car or an ocean cargo container. This BOD does not usually cause updates to occur. Shipment Characteristics A Shipment document does not necessarily have a one-to-one relationship with any customer purchase/sales order document, line item or line item schedule. For shipping efficiency, a Shipment document may consolidate inventory shipment requests from a variety of different orders that have the same ultimate physical destination. In fact, there may be no customer sale at all, as when the supplier is simply transferring inventory from one warehouse site to another within their enterprise to maintain optimum stocking levels. A Shipment typically involves a minimum of three business partner entities: Supplier, Carrier, and Customer in the most common business transaction scenario. However these partner titles are more useful as descriptions of the basic roles in the Shipment process. The actual number and relationship of the potential business partners/parties involved in the transaction is intended to be flexible in usage to accommodate agents working on behalf of partners and unique or complex scenarios. The ShipUnit component identify and describe the physical shipping container(s) and internal packaging structure of the delivered goods. ShipUnit component are typically constructed to describe the result of an inventory picking and packing operation. The ShipUnit structure complements the line-item oriented summary information provided in the Shipment's ShipItem and InventoryDetail component with detailed information to accurately describe complex shipping unit assemblies and item packaging. This robust level of detail is often demanded by customers to improve the efficiency of their receiving operations. If the supplier provides trustworthy ship unit packaging information in advance, the customer does not have to spend valuable receiving personnel time breaking down the containers to inspect and tally each inventory item. The general industry trend toward smaller just-in-time deliveries of only the required amount of goods, customer-imposed packaging configurations and requirements, and suppliers performing value-added light assembly customization at the time of shipment is driving the need for more detailed information about the product as it is actually delivered.
  356. ShowShipmentSchedule [1..1]    Commonly, the ship schedule is generated by a material planning application and transmitted to an order or material planning application. The purpose of the ShowShipmentSchedule is to communicate to a business application module or system the sending systems representation of ShipmentSchedule information. This request may be used as a response to a GetShipmentSchedule request or as a push notification of an event.
  357. ShowShipmentUnit [1..1]    The purpose of the ShowShipmentUnit is to enable an application to provide a Show ShipmentUnit information from another business application module. The ShowShipmentUnit is the response to the GetShipmentUnit.
  358. ShowSplitWIP [1..1]    The purpose of the ShowSplitWIP is to supply SplitWIP information to another business application module.
  359. ShowSupplierPartyMaster [1..1]    The ShowSupplierPartyMaster is the response for more information about the SupplierPartyMaster data. The request is provided in the GetSupplierPartyMaster BOD.
  360. ShowUOMGroup [0..1]    The purpose of the ShowUOMGroup is to supply Unit-of-Measure Group relationship information to another business application module. This request may be issued as a response to a GetUOMGroup request or as the result of some other business event. There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to request alternate UOM information for one or more items.
  361. ShowWIPStatus [1..1]    The purpose of the ShowWIPStatus is to notify a Manufacturing Application of the progress of a production order at a point in time. The business environments most likely to require this capability are any type of manufacturing scenario where BODs for individual manufacturing transactions and events are not utilized. This BOD communicates what quantities of end product reside at which processing steps along with the time this snapshot view was taken.
  362. SyncAllocateResource [1..1]    The purpose of the SyncAllocateResource is to supply AllocateResource information to another business application module. Where the allocation of resources is provided by the system of record.
  363. SyncBOM [1..1]    The purpose of the SynBOM is to communicate to a business application module or system the need to initiate the creation of a Bill of Material structure. 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, an MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Bill of Material.
  364. SyncCarrierRoute [1..1]    The purpose of the SyncCarrierRoute is to enable an application to provide Carrier Route information from another business application module. The SyncCarrierRoute is typiically provided in a publish/subscribe or broadcast environment. Where the sending system is the master application of the information being provided, where the information is sent to other business applications that need to know the information.
  365. SyncCatalog [1..1]    SyncCatalog is used to synchronize catalog information across systems. The Sync indicates that the send of the SyncCatalog is the owner of the information being passed, additionally it is understood that the receiver of the SyncCatalog is a sub-system that must accept the data as provided by the owne of the information.
  366. SyncChartOfAccounts [1..1]    The purpose of the SyncChartOfAccounts is to distribute general ledger chart of accounts code identifiers to other applications to store for validation purposes.
  367. SyncCredit [1..1]    SyncCredit is used to synchronize Credit information with other applications
  368. SyncCreditStatus [1..1]    The purpose of the SyncCreditStatus is to supply CreditStatus information to another business application module.
  369. SyncCurrencyExchangeRate [1..1]    The purpose of the SyncCurrencyExchangeRate is to enable the passing of updates of currency exchange rates to other applications that have exchange rate tables.
  370. SyncCustomerPartyMaster [1..1]    The purpose of the SyncCustomerPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases. The SyncCustomerPartyMaster allows the adding of new party and the modification of previously established CustomerPartyMaster.
  371. SyncDispatchList [1..1]    The purpose of the SyncDispatchList is to synchronize dispatch list (finite schedule) information.
  372. SyncEmployeeWorkSchedule [1..1]    The purpose of the SyncEmployeeWorkSchedule is to enable the synchronization of Employee Work Schedule data that exists on separate data bases. The SyncEmployeeWorkSchedule allows the adding of new Employee Work Schedules as well as the modification of previously established Employee Work Schedules.
  373. SyncEmployeeWorkTime [1..1]    The purpose of the SyncEmployeeWorkTime is to Sync work time information for an employee from a data collection application to an ERP Human Resource application.
  374. SyncEngineeringChangeOrder [1..1]    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.
  375. SyncEngineeringWorkDocument [1..1]    The purpose of the SyncEngineeringWorkDocument is to enable an application to provide EngineeringWorkDocument from another business application module. The SyncEngineeringWorkDocument is typically provided in a a publishe/subscribe or broadcast buiness exchange wher the owner or the master of the given information provides it to the other business applications that need to know the information or have expressed interest..
  376. SyncField [1..1]    The purpose of the SyncField is to enable the validation of data that exists on separate application's data bases. This BOD can cause on-line validation to occur or may be a single tool for synchronizing data.
  377. SyncInspectDelivery [1..1]    The purpose of the SyncInspectDelivery is to supply InspectDelivery information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example; 1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information. 3. A Laboratory Information System could send quality information to an Inventory application, 4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
  378. SyncInventoryBalance [1..1]    The purpose of the SyncInventoryBalance is to enable the synchronization of InventoryBalance data that exists on separate Item Master databases. This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure. This is data that describes the ITEM as it exists at a specific location. The primary focus of this BOD is to synchronize the quantity of an item by stocking location.
  379. SyncInventoryConsumption [1..1]    The purpose of the SyncInventoryConsumption is to inform a seller or provider about InventoryConsumption of items.
  380. SyncInventoryCount [1..1]    The purpose of the SyncInventoryCount is to transmit an inventory count to ERP from the actual physical inventory location. This count may be a cycle count or a physical count. This BOD may also apply to planned or unplanned inventory counts.
  381. SyncInvoice [1..1]    The purpose of the SyncInvoice is to transmit an invoice from a supplier to a customer. This information is passed in order to keep the customer updated on the number of Invoices they have.
  382. SyncItemMaster [1..1]    The purpose of the SyncItemMaster is to supply Item information for goods or services to another business application module. This BOD may also be initiated by the sending system upon some event occurring. This BOD is not for synchronizing ITEM quantities at each inventory location. The SyncInventoryBalance Business Object Document is used for this purpose. There are many possible business applications in several environments that may use this capability. For example, a MRP, Inventory, or Manufacturing business application could use this to communicate item information. This BOD can be used to synchronize items used in finished goods, raw materials, work-in-process or components in a bill of materials.
  383. SyncLocation [1..1]    The purpose of the Sync Location is to enable a mechanism to ensure that the physical location identifiers are synchronized between the business applications that require this to communicate clearly. This is particularly critical when only the codes that identify locations are used. Without the meaning of the codes clearly communicated, the integration is not effective. This BOD enables the Location codes to be synchronized among business applications. This BOD may also be initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example, a MRP, Inventory, or Manufacturing business application could use this to communicate Location information.
  384. SyncMaintenanceOrder [1..1]    The purpose of the SyncMaintenanceOrder is to ensure that all business software components in a specific integration instance have the current Maintenance Order information. This BOD is commonly used to publish the need to create or update a Maintenance Order in a publish and subscribe integration environment. One possible scenario is the synchronization of Maintenance Order between field devices, service trucks, etc. with a CMMS system.
  385. SyncOnlineOrder [1..1]    The purpose of the SyncOnlineOrder is to enable an application to provide online shopping OnlineOrders from another business application module. The SyncOnlineOrder is provided in a a publishe/subscribe or broadcast buiness exchange wher the owner or the master of the given information provides it to the other business applications that need to know the information or have expressed interest.
  386. SyncOperation [1..1]    The purpose of the SyncOperation is to enable an application to provide online shopping Operations from another business application module. The SyncOperation is provided in a a publishe/subscribe or broadcast buiness exchange wher the owner or the master of the given information provides it to the other business applications that need to know the information or have expressed interest.
  387. SyncOpportunity [1..1]    The purpose of the SyncOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The SyncOpportunity is provided in a a publishe/subscribe or broadcast buiness exchange wher the owner or the master of the given information provides it to the other business applications that need to know the information or have expressed interest.
  388. SyncPartyMaster [1..1]    The purpose of the SyncPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases. The SyncPartyMaster allows the adding of new party and the modification of previously established PartyMaster.
  389. SyncPersonnel [1..1]    The purpose of the SyncPersonnel is to enable the synchronization of employee data that exists on separate data bases between manufacturing and human resource applications. The SyncPersonnel allows the adding of new employees and their relevant data as well as the modification of previously established employees. The SyncPersonnel is used to facilitate the maintenance of human resource data in a manufacturing work force planning module. This enables the workforce planning module to use current personnel information when creating finite production schedules. The SyncPersonnel can also be used by a project accounting application or a work order management application to assign qualified personnel or to perform resource planning.
  390. SyncPickList [1..1]    The purpose of the SyncPickList is to Sync the details of an individual Picking List from a plant level to an ERP system. This BOD will usually cause Syncs to occur.
  391. SyncPlanningSchedule [1..1]    Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party. Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional component PlanningScheduleException . The purpose of the SyncPlanningSchedule is to communicate requirement information (part number, quantity, etc.) between a customer and their supplier on a regular basis, for example daily, weekly etc, or for a user-defined time bucket type definition (Component FexibileBucket) that is sent as part of this PlanningSchedule. SyncPlanningSchedule allows the adding of new requirements and the modification of previously established requirements. Customers can use this PlanningSchedule to communicate demand requirement in three different ways. It can be as specific as the Item level or at the Commodity code level, which is higher than item. Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional component FeatureValue.
  392. SyncPriceList [1..1]    The purpose of the SyncPriceList is to communicate to a business application module or system the need to initiate the creation of product price list information as well as update existing price lists. 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 Manufacturing, distributor or reseller business application could use this to communicate the price change or request a price list. It may also be necessary to support Component Supplier Management (CSM) scenarios. In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog. A customer purchases the product from the Catalog provider. They have the capability to do comparison shopping from the catalog. Supplier Certification may be provided by the Catalog provider. This definition of price list is intended to support simple pricing scenario, especially pricing that may accompany a published price list. It is not intended to support complex pricing environments that may be needed to support features such as; · Deals and Promotions · Coupons and Sales Incentives · Rebates and Accruals This functionality will be addressed in a subsequent release. It is a working assumption that the representation of complex qualifications, coupons and sales incentives are rarely communicated between systems.
  393. SyncProductionOrder [1..1]    The purpose of the SyncProductionOrder is to ensure that all business software components in a specific integration instance have the current Production Order information. This BOD is commonly used in a publish and subscribe integration environment. This BOD commonly causes updates to occur.
  394. SyncProjectMaster [1..1]    The purpose of the SyncProjectMaster is to enable all relevant sub-systems that submit transactions to the project accounting application to maintain valid values for the key project fields. The target applications for this update would include, but not necessarily be limited to: · Accounts Payable · Accounts Receivable · Budget · Order Management · Purchasing · Time and Labor · Travel and Expense
  395. SyncPurchaseOrder [1..1]    The purpose of the Sync PurchaseOrder is to facilitate keeping purchase order information synchronized on separate data bases throughout an enterprise. The Sync PurchaseOrder allows the adding of new purchase orders and the modification of previously established purchase orders.
  396. SyncQuote [1..1]    The purpose of the SyncQuote is to ensure that all business software components in a specific integration instance have the current Quote information. This BOD is commonly used to publish the need to create or update a Quote in a publish and subscribe integration environment.
  397. SyncRequisition [1..1]    SyncRequisition is used to synchronize Requisition information with other applications
  398. SyncRFQ [1..1]    The purpose of the SyncRFQ is to ensure that all business software components in a specific integration instance have the current Request for Quote information. This BOD is commonly used to publish the need to create or update a Request for Quote in a publish and subscribe integration environment.
  399. SyncRiskControlLibrary [1..1]    The purpose of the SyncRiskControlLibrary is to supply RiskControlLibrary information to another business application module.
  400. SyncRouting [1..1]    The purpose of the SyncRouting is to communicate to a business application component or system the need to create a new Routing or to update an existing Routing structure. This BOD may be necessary to address the Make to Order, Assemble to Order, and Finished Goods business ordering scenarios in a Logistics to Manufacturing application integration scenario.
  401. SyncSalesLead [1..1]    The purpose of the SyncSalesLead is to enable an application to provide SalesLead information from one business application to another business application. The SyncSalesLead is provided in a a publishe/subscribe or broadcast buiness exchange wher the owner or the master of the given information provides it to the other business applications that need to know the information or have expressed interest.
  402. SyncSalesOrder [1..1]    The purpose of the Sync SalesOrder is to facilitate keeping sales or customer order information synchronized on separate data bases throughout an enterprise. The Sync SalesOrder allows the adding of new sales orders and the modification of previously established sales orders. This BOD commonly causes updates to occur.
  403. SyncSequenceSchedule [1..1]    The purpose of the SyncSequenceSchedule is to enable the exchange of sequence schedule information authorizing a sequenced shipment of parts for specific trading partners and addresses. Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application.
  404. SyncShipment [1..1]    SyncShipment is used to synchronize Shipment information with other applications
  405. SyncShipmentSchedule [1..1]    The purpose of the SyncShipmentSchedule is to enable the exchange of shipment schedule information, authorizing a shipment quantity and date for specific trading partners and addresses. Commonly, the ship schedule is generated by a material planning application and transmitted to an order or material planning application.
  406. SyncShipmentUnit [1..1]    The purpose of the SyncShipmentUnit is to enable an application to provide a ShipmentUnit information from another business application module. The SyncShipmentUnit is typically published from the business application that is the master or owner of the ShipmentUnit information to other systems needing to know about the changes to the ShipmentUnit information.
  407. SyncSupplierPartyMaster [1..1]    SyncSupplerPartyMaster is used to synchronize SupplierPartyMaster data across systems. Using the Sync indicates that the sender of the Sync is the owner of the date and the receiver of the Sync is a sub-system that must accept the data as provided.
  408. SyncUOMGroup [0..1]    The purpose of the SyncUOMGroup is to supply a set of Unit-Of-Measure relationships to another business application module. This BOD addresses the need for applications to exchange item-independent alternative UOM information beyond the stocking UOM. See the Item UOM Integration Scenario for more detailed information.
  409. UpdateConfirmWIP [1..1]    The purpose of the UpdateConfirmWIP is to confirm receipt of WIP (Work in Process) materials.
  410. UpdateCredit [1..1]    The purpose of the UpdateCredit is to update the Credit Management functionality within the customer order management or the accounts receivable application. The UpdateCredit will also transmit changes in the accounts receivable open item balances to the credit management function of the customer order management application.
  411. UpdateCreditStatus [1..1]    The purpose of the UpdateCreditStatus is to supply CreditStatus information to another business application module.
  412. UpdateDispatchList [1..1]    The purpose of the UpdateDispatchList is to synchronize dispatch list (finite schedule) information.
  413. UpdateEmployeeWorkTime [1..1]    The purpose of the UpdateEmployeeWorkTime is to update work time information for an employee from a data collection application to an ERP Human Resource application.
  414. UpdateEngineeringChangeOrder [1..1]    The purpose of the UpdateEngineeringChangeOrder to communicate to a business application module or system that the synchronization of a specified engineering change document has been completed successfully. 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.
  415. UpdateEngineeringWorkDocument [1..1]    The purpose of the UpdateEngineeringWorkDocument is to enable an application to provide EngineeringWorkDocument from another business application module. The UpdateEngineeringWorkDocument is provided in response to the ProcessCart in order to request a Update to process the cart. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  416. UpdateInspectDelivery [1..1]    The purpose of the UpdateInspectDelivery is to supply InspectDelivery information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example; 1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information. 3. A Laboratory Information System could send quality information to an Inventory application, 4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
  417. UpdateInventoryBalance [1..1]    The purpose of the ChangeInventoryBalance is to enable the communication of a Change in the InventoryBalance data that exists on separate Inventory databases. This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure. This is data that describes the ITEM as it exists at a specific location. It is
  418. UpdateInventoryCount [1..1]    The purpose of the UpdateInventoryCount is to transmit an inventory count to ERP from the actual physical inventory location. This count may be a cycle count or a physical count. This BOD may also apply to planned or unplanned inventory counts.
  419. UpdateInvoice [1..1]    The purpose of the UpdateInvoice is to notify another application about a Update in the Invoice
  420. UpdateMaintenanceOrder [1..1]    The purpose of the UpdateMaintenanceOrder is to publish to a business application component or system the need to create or update a Maintenance Order. One possible scenario is the synchronization of Maintenance Order between field devices, service trucks, etc. with a CMMS system.
  421. UpdateMatchDocument [1..1]    In certain application suites, purchase order / invoice matching functionality exists in the purchasing application, while in other suites this functionality exists in the accounts payable application. The invoice matching process may include several document types, including the following: - Two way match - Purchase Order and the Invoice - Three way match - Purchase Order, Invoice, and the Receipt - Four way match - Purchase Order, Invoice, Receipt, and Inspection results For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching. When matching takes place in the purchasing application, the accounts payable application may have to inform the purchasing application of the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched if the invoice is initially entered into the accounts payable application. Note that in some situations, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters. When matching takes place in the accounts payable application, the purchasing application must inform the accounts payable application of the purchasing transactions (purchase orders, goods receiving notes and inspection tickets) to which the invoice (in accounts payable) is to be matched. These integration scenarios have been developed for document matching to occur at the line level within the PuchaseOrder document and the Invoice document. This may be a one to one relationship, or it may be a many to one relationship from Invoice to PuchaseOrder or from the PuchaseOrder to the Invoice. Charges not associated with a specific Invoice line match be matched individually. The LoadMatchDocument is for use both by the accounts payable application and the purchasing application in exchanging the transactions that are required to be matched. The purpose of UpdateMatchDocument is for the accounts payable application to send successful matching notification or a match fail.notification to a purchasing application.
  422. UpdateOnlineOrder [1..1]    The purpose of the UpdateOnlineOrder is to enable an application to provide online shopping OnlineOrders from another business application module. The UpdateOnlineOrder is provided in response to the ProcessOnlineOrder in order to request a Update to process the OnlineOrder. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  423. UpdateOpportunity [1..1]    The purpose of the UpdateOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The UpdateOpportunityis provided in response to the ProcessCart in order to request a Update to process the cart. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  424. UpdatePickList [1..1]    The purpose of the UpdatePickList is to update the details of an individual Picking List from a plant level to an ERP system. This BOD will usually cause updates to occur.
  425. UpdateProductionOrder [1..1]    The purpose of the UpdateProductionOrder is to notify another application about a Update in the ProductionOrder
  426. UpdatePurchaseOrder [1..1]    The purpose of the Update Purchaseorder is to request another business application to make Updates to an existing Purchase Order. This Update must refer to the original document and/or item ordered. The Update processing assumes replacement of fields sent, with the exception the identifying fields of the Purchase Order. If any of these key fields require changing, (i.e. the PurchaseOrder Document Id or a LineNumber) that constitutes a cancellation of the request and/or the addition of another Purchase Order.
  427. UpdateQuote [1..1]    The purpose of the UpdateQuote is to request that another business application component make Updates to an existing Quote
  428. UpdateReceiveDelivery [1..1]    The UpdateReceiveDelivery may be used to update the receiver's internal receiving and order management business applications to indicate that the requested material has arrived, including any unexpected quantity, condition or other exception discrepancies. There are many other possible business applications in several environments that may use this capability. For example: 1. A Purchasing application may use this BOD to notify an Accounts Payable application of a specific delivery. This will enable the Accounts Payable application to accurately calculate the amount it needs to pay a business partner. 2. A Purchasing application could use this to notify a MRP, Inventory, or Manufacturing business application that a delivery has occurred and the goods are available for use or inspection, etc. 3. An MRP/Inventory system could use this BSR to communicate changes on a physical receipt in inventory to the Purchasing system. The UpdateReceiveDelivery supports receipts at either the line item level and/or the ship unit level. Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents.
  429. UpdateRequireProduct [1..1]    The purpose of the UpdateRequireProduct is to enable a business application such as Order Management to reserve a quantity of goods or services for a specific date and time. The business process scenario is the Order Management application interacting with the Available to Promise or Production application in order to determine availability of a product for the customer. This scenario is commonly referred to as Make to Order or Build to Order. The UpdateRequireProduct accomplishes this task in a two step process within this one request: 1. First the receiving business application checks to see if an item is available in sufficient quantity by a specific date and time. 2. The receiving business application then reserves that quantity of inventory for that specific date and time combination if the product is available. If the product requested is not available, The responding application may send one of two responses: 1. A ConfirmBOD to confirm the denial of the request. 2. A ShowProductAvailability to communicate an alternative product availability. This may be OrderItem, Date, or Quantity, or a combination of these. This may also be accompanied with a message in the Note field Identifier stating that this is an alternative. If the product requested is available: The responding application may send a ConfirmBOD to confirm the execution of the request. This BOD will likely cause updates to occur. This BOD may be used individually, or as part of a larger interface scenario. The GetProductAvailability and ShowProductAvailability may be used before an UpdateRequireProduct, but they are not required.
  430. UpdateRequisition [1..1]    The purpose of the UpdateRequisition is to communicate Updates to an existing request for goods or services. This Update must refer to the original document and/or item requested. The Update processing assumes replacement of fields sent, with the exception of: the key fields for the Order and Line. If any of the Field Identifiers above require changing, that constitutes a cancellation of the request and/or the addition of another Requisition.
  431. UpdateRFQ [1..1]    The purpose of the UpdateRFQ is to publish to a business application or system the need to Update an entire Request for Quote or one or more of its line items.
  432. UpdateSalesLead [1..1]    The purpose of the UpdateSalesLead is to enable an application to provide SalesLead information from one business application to another business application. The UpdateSalesLeadis provided in response to the ProcessCart in order to request a Update to process the cart. The Chagne is directed from the owner of the information (the receiver of the Process) the originator of the Process.
  433. UpdateSalesOrder [1..1]    The purpose of the Update SalesOrder is to request that another business application component make Updates to an existing Sales Order. Processing Note: This Update must refer to the original document and/or item ordered. The Update 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

Attributes

None

Sample instance

<OAGIS9BODs>
   <AcknowledgeAllocateResource releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <AllocateResource>...
         </AllocateResource>
      </DataArea>
   </AcknowledgeAllocateResource>
   <AcknowledgeConfirmWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <ConfirmWIP>...
         </ConfirmWIP>
      </DataArea>
   </AcknowledgeConfirmWIP>
   <AcknowledgeCostingActivity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <CostingActivity>...
         </CostingActivity>
      </DataArea>
   </AcknowledgeCostingActivity>
   <AcknowledgeCredit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <Credit>...
         </Credit>
      </DataArea>
   </AcknowledgeCredit>
   <AcknowledgeCreditStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <CreditStatus>...
         </CreditStatus>
      </DataArea>
   </AcknowledgeCreditStatus>
   <AcknowledgeCreditTransfer releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <CreditTransfer>...
         </CreditTransfer>
      </DataArea>
   </AcknowledgeCreditTransfer>
   <AcknowledgeCreditTransferIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <CreditTransferIST>...
         </CreditTransferIST>
      </DataArea>
   </AcknowledgeCreditTransferIST>
   <AcknowledgeDebitTransfer releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <DebitTransfer>...
         </DebitTransfer>
      </DataArea>
   </AcknowledgeDebitTransfer>
   <AcknowledgeDebitTransferIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <DebitTransferIST>...
         </DebitTransferIST>
      </DataArea>
   </AcknowledgeDebitTransferIST>
   <AcknowledgeDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </AcknowledgeDispatchList>
   <AcknowledgeEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </AcknowledgeEmployeeWorkTime>
   <AcknowledgeEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </AcknowledgeEngineeringChangeOrder>
   <AcknowledgeEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </AcknowledgeEngineeringWorkDocument>
   <AcknowledgeInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </AcknowledgeInspectDelivery>
   <AcknowledgeInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </AcknowledgeInventoryBalance>
   <AcknowledgeInventoryConsumption releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <InventoryConsumption>...
         </InventoryConsumption>
      </DataArea>
   </AcknowledgeInventoryConsumption>
   <AcknowledgeInventoryCount releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <InventoryCount>...
         </InventoryCount>
      </DataArea>
   </AcknowledgeInventoryCount>
   <AcknowledgeInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <Invoice>...
         </Invoice>
      </DataArea>
   </AcknowledgeInvoice>
   <AcknowledgeIssueInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <IssueInventory>...
         </IssueInventory>
      </DataArea>
   </AcknowledgeIssueInventory>
   <AcknowledgeJournalEntry releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <JournalEntry>...
         </JournalEntry>
      </DataArea>
   </AcknowledgeJournalEntry>
   <AcknowledgeMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </AcknowledgeMaintenanceOrder>
   <AcknowledgeMatchDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <MatchDocument>...
         </MatchDocument>
      </DataArea>
   </AcknowledgeMatchDocument>
   <AcknowledgeMergeWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <MergeWIP>...
         </MergeWIP>
      </DataArea>
   </AcknowledgeMergeWIP>
   <AcknowledgeMoveInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <MoveInventory>...
         </MoveInventory>
      </DataArea>
   </AcknowledgeMoveInventory>
   <AcknowledgeMoveWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <MoveWIP>...
         </MoveWIP>
      </DataArea>
   </AcknowledgeMoveWIP>
   <AcknowledgeOnlineOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <OnlineOrder>...
         </OnlineOrder>
      </DataArea>
   </AcknowledgeOnlineOrder>
   <AcknowledgeOperation releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <Operation>...
         </Operation>
      </DataArea>
   </AcknowledgeOperation>
   <AcknowledgeOpportunity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <Opportunity>...
         </Opportunity>
      </DataArea>
   </AcknowledgeOpportunity>
   <AcknowledgePaymentStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <PaymentStatus>...
         </PaymentStatus>
      </DataArea>
   </AcknowledgePaymentStatus>
   <AcknowledgePaymentStatusIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <PaymentStatusIST>...
         </PaymentStatusIST>
      </DataArea>
   </AcknowledgePaymentStatusIST>
   <AcknowledgePickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <PickList>...
         </PickList>
      </DataArea>
   </AcknowledgePickList>
   <AcknowledgeProductAvailability releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <ProductAvailability>...
         </ProductAvailability>
      </DataArea>
   </AcknowledgeProductAvailability>
   <AcknowledgeProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </AcknowledgeProductionOrder>
   <AcknowledgePurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </AcknowledgePurchaseOrder>
   <AcknowledgeQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <Quote>...
         </Quote>
      </DataArea>
   </AcknowledgeQuote>
   <AcknowledgeReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </AcknowledgeReceiveDelivery>
   <AcknowledgeReceiveItem releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <ReceiveItem>...
         </ReceiveItem>
      </DataArea>
   </AcknowledgeReceiveItem>
   <AcknowledgeRecoverWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <RecoverWIP>...
         </RecoverWIP>
      </DataArea>
   </AcknowledgeRecoverWIP>
   <AcknowledgeRequireProduct releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <RequireProduct>...
         </RequireProduct>
      </DataArea>
   </AcknowledgeRequireProduct>
   <AcknowledgeRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <Requisition>...
         </Requisition>
      </DataArea>
   </AcknowledgeRequisition>
   <AcknowledgeRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <RFQ>...
         </RFQ>
      </DataArea>
   </AcknowledgeRFQ>
   <AcknowledgeRiskControlLibrary releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <RiskControlLibrary>...
         </RiskControlLibrary>
      </DataArea>
   </AcknowledgeRiskControlLibrary>
   <AcknowledgeSalesLead releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <SalesLead>...
         </SalesLead>
      </DataArea>
   </AcknowledgeSalesLead>
   <AcknowledgeSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </AcknowledgeSalesOrder>
   <AcknowledgeShipment releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <Shipment>...
         </Shipment>
      </DataArea>
   </AcknowledgeShipment>
   <AcknowledgeShipmentUnit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <ShipmentUnit>...
         </ShipmentUnit>
      </DataArea>
   </AcknowledgeShipmentUnit>
   <AcknowledgeSplitWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <SplitWIP>...
         </SplitWIP>
      </DataArea>
   </AcknowledgeSplitWIP>
   <AcknowledgeWIPStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Acknowledge>...
         </Acknowledge>
         <WIPStatus>...
         </WIPStatus>
      </DataArea>
   </AcknowledgeWIPStatus>
   <AddPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Add>
         </Add>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </AddPurchaseOrder>
   <AddQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Add>
         </Add>
         <Quote>...
         </Quote>
      </DataArea>
   </AddQuote>
   <AddRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Add>
         </Add>
         <Requisition>...
         </Requisition>
      </DataArea>
   </AddRequisition>
   <AddRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Add>
         </Add>
         <RFQ>...
         </RFQ>
      </DataArea>
   </AddRFQ>
   <AddSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Add>
         </Add>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </AddSalesOrder>
   <AllocateCostingActivity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Allocate>
         </Allocate>
         <CostingActivity>...
         </CostingActivity>
      </DataArea>
   </AllocateCostingActivity>
   <CancelDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </CancelDispatchList>
   <CancelEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </CancelEmployeeWorkTime>
   <CancelEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </CancelEngineeringChangeOrder>
   <CancelEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </CancelEngineeringWorkDocument>
   <CancelInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </CancelInspectDelivery>
   <CancelInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </CancelInventoryBalance>
   <CancelInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <Invoice>...
         </Invoice>
      </DataArea>
   </CancelInvoice>
   <CancelMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </CancelMaintenanceOrder>
   <CancelPickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <PickList>...
         </PickList>
      </DataArea>
   </CancelPickList>
   <CancelProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </CancelProductionOrder>
   <CancelPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </CancelPurchaseOrder>
   <CancelQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <Quote>...
         </Quote>
      </DataArea>
   </CancelQuote>
   <CancelReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </CancelReceiveDelivery>
   <CancelRequireProduct releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <RequireProduct>...
         </RequireProduct>
      </DataArea>
   </CancelRequireProduct>
   <CancelRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <Requisition>...
         </Requisition>
      </DataArea>
   </CancelRequisition>
   <CancelRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <RFQ>...
         </RFQ>
      </DataArea>
   </CancelRFQ>
   <CancelSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Cancel>
         </Cancel>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </CancelSalesOrder>
   <ChangeConfirmWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <ConfirmWIP>...
         </ConfirmWIP>
      </DataArea>
   </ChangeConfirmWIP>
   <ChangeCredit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <Credit>...
         </Credit>
      </DataArea>
   </ChangeCredit>
   <ChangeCreditStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <CreditStatus>...
         </CreditStatus>
      </DataArea>
   </ChangeCreditStatus>
   <ChangeDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </ChangeDispatchList>
   <ChangeEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </ChangeEmployeeWorkTime>
   <ChangeEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </ChangeEngineeringChangeOrder>
   <ChangeEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </ChangeEngineeringWorkDocument>
   <ChangeInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </ChangeInspectDelivery>
   <ChangeInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </ChangeInventoryBalance>
   <ChangeInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <Invoice>...
         </Invoice>
      </DataArea>
   </ChangeInvoice>
   <ChangeMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </ChangeMaintenanceOrder>
   <ChangeOnlineOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <OnlineOrder>...
         </OnlineOrder>
      </DataArea>
   </ChangeOnlineOrder>
   <ChangeOpportunity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <Opportunity>...
         </Opportunity>
      </DataArea>
   </ChangeOpportunity>
   <ChangePickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <PickList>...
         </PickList>
      </DataArea>
   </ChangePickList>
   <ChangeProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </ChangeProductionOrder>
   <ChangePurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </ChangePurchaseOrder>
   <ChangeQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <Quote>...
         </Quote>
      </DataArea>
   </ChangeQuote>
   <ChangeReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </ChangeReceiveDelivery>
   <ChangeRequireProduct releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <RequireProduct>...
         </RequireProduct>
      </DataArea>
   </ChangeRequireProduct>
   <ChangeRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <Requisition>...
         </Requisition>
      </DataArea>
   </ChangeRequisition>
   <ChangeRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <RFQ>...
         </RFQ>
      </DataArea>
   </ChangeRFQ>
   <ChangeSalesLead releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <SalesLead>...
         </SalesLead>
      </DataArea>
   </ChangeSalesLead>
   <ChangeSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Change>
         </Change>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </ChangeSalesOrder>
   <CreateMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Create>
         </Create>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </CreateMaintenanceOrder>
   <CreateProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Create>
         </Create>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </CreateProductionOrder>
   <CreateRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Create>
         </Create>
         <Requisition>...
         </Requisition>
      </DataArea>
   </CreateRequisition>
   <GetActualLedger releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ActualLedger>...
         </ActualLedger>
      </DataArea>
   </GetActualLedger>
   <GetAllocateResource releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <AllocateResource>...
         </AllocateResource>
      </DataArea>
   </GetAllocateResource>
   <GetBOM releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <BOM>...
         </BOM>
      </DataArea>
   </GetBOM>
   <GetBudgetLedger releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <BudgetLedger>...
         </BudgetLedger>
      </DataArea>
   </GetBudgetLedger>
   <GetCarrierRoute releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <CarrierRoute>...
         </CarrierRoute>
      </DataArea>
   </GetCarrierRoute>
   <GetCatalog releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Catalog>...
         </Catalog>
      </DataArea>
   </GetCatalog>
   <GetChartOfAccounts releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ChartOfAccounts>...
         </ChartOfAccounts>
      </DataArea>
   </GetChartOfAccounts>
   <GetConfirmWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ConfirmWIP>...
         </ConfirmWIP>
      </DataArea>
   </GetConfirmWIP>
   <GetCostingActivity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <CostingActivity>...
         </CostingActivity>
      </DataArea>
   </GetCostingActivity>
   <GetCredit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Credit>...
         </Credit>
      </DataArea>
   </GetCredit>
   <GetCreditStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <CreditStatus>...
         </CreditStatus>
      </DataArea>
   </GetCreditStatus>
   <GetCreditTransfer releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <CreditTransfer>...
         </CreditTransfer>
      </DataArea>
   </GetCreditTransfer>
   <GetCreditTransferIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <CreditTransferIST>...
         </CreditTransferIST>
      </DataArea>
   </GetCreditTransferIST>
   <GetCurrencyExchangeRate releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <CurrencyExchangeRate>...
         </CurrencyExchangeRate>
      </DataArea>
   </GetCurrencyExchangeRate>
   <GetCustomerPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <CustomerPartyMaster>...
         </CustomerPartyMaster>
      </DataArea>
   </GetCustomerPartyMaster>
   <GetDebitTransfer releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <DebitTransfer>...
         </DebitTransfer>
      </DataArea>
   </GetDebitTransfer>
   <GetDebitTransferIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <DebitTransferIST>...
         </DebitTransferIST>
      </DataArea>
   </GetDebitTransferIST>
   <GetDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </GetDispatchList>
   <GetEmployeeWorkSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <EmployeeWorkSchedule>...
         </EmployeeWorkSchedule>
      </DataArea>
   </GetEmployeeWorkSchedule>
   <GetEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </GetEmployeeWorkTime>
   <GetEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </GetEngineeringChangeOrder>
   <GetEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </GetEngineeringWorkDocument>
   <GetField releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Field>...
         </Field>
      </DataArea>
   </GetField>
   <GetInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </GetInspectDelivery>
   <GetInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </GetInventoryBalance>
   <GetInventoryConsumption releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <InventoryConsumption>...
         </InventoryConsumption>
      </DataArea>
   </GetInventoryConsumption>
   <GetInventoryCount releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <InventoryCount>...
         </InventoryCount>
      </DataArea>
   </GetInventoryCount>
   <GetInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Invoice>...
         </Invoice>
      </DataArea>
   </GetInvoice>
   <GetInvoiceLedgerEntry releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <InvoiceLedgerEntry>...
         </InvoiceLedgerEntry>
      </DataArea>
   </GetInvoiceLedgerEntry>
   <GetIssueInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <IssueInventory>...
         </IssueInventory>
      </DataArea>
   </GetIssueInventory>
   <GetItemMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ItemMaster>...
         </ItemMaster>
      </DataArea>
   </GetItemMaster>
   <GetJournalEntry releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <JournalEntry>...
         </JournalEntry>
      </DataArea>
   </GetJournalEntry>
   <GetListActualLedger releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <ActualLedger>...
         </ActualLedger>
      </DataArea>
   </GetListActualLedger>
   <GetListBOM releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <BOM>...
         </BOM>
      </DataArea>
   </GetListBOM>
   <GetListInventoryCount releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <InventoryCount>...
         </InventoryCount>
      </DataArea>
   </GetListInventoryCount>
   <GetListItemMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <ItemMaster>...
         </ItemMaster>
      </DataArea>
   </GetListItemMaster>
   <GetListMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </GetListMaintenanceOrder>
   <GetListPickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <PickList>...
         </PickList>
      </DataArea>
   </GetListPickList>
   <GetListProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </GetListProductionOrder>
   <GetListPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </GetListPurchaseOrder>
   <GetListQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <Quote>...
         </Quote>
      </DataArea>
   </GetListQuote>
   <GetListReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </GetListReceiveDelivery>
   <GetListRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <Requisition>...
         </Requisition>
      </DataArea>
   </GetListRequisition>
   <GetListRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <RFQ>...
         </RFQ>
      </DataArea>
   </GetListRFQ>
   <GetListRouting releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <Routing>...
         </Routing>
      </DataArea>
   </GetListRouting>
   <GetListSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </GetListSalesOrder>
   <GetListUOMGroup releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <GetList>
         </GetList>
         <UOMGroup>...
         </UOMGroup>
      </DataArea>
   </GetListUOMGroup>
   <GetLocation releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Location>...
         </Location>
      </DataArea>
   </GetLocation>
   <GetLocationService releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <LocationService>...
         </LocationService>
      </DataArea>
   </GetLocationService>
   <GetMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </GetMaintenanceOrder>
   <GetMatchDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <MatchDocument>...
         </MatchDocument>
      </DataArea>
   </GetMatchDocument>
   <GetMergeWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <MergeWIP>...
         </MergeWIP>
      </DataArea>
   </GetMergeWIP>
   <GetMoveInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <MoveInventory>...
         </MoveInventory>
      </DataArea>
   </GetMoveInventory>
   <GetMoveWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <MoveWIP>...
         </MoveWIP>
      </DataArea>
   </GetMoveWIP>
   <GetOnlineOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <OnlineOrder>...
         </OnlineOrder>
      </DataArea>
   </GetOnlineOrder>
   <GetOnlineSession releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <OnlineSession>...
         </OnlineSession>
      </DataArea>
   </GetOnlineSession>
   <GetOperation releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Operation>...
         </Operation>
      </DataArea>
   </GetOperation>
   <GetOpportunity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Opportunity>...
         </Opportunity>
      </DataArea>
   </GetOpportunity>
   <GetPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <PartyMaster>...
         </PartyMaster>
      </DataArea>
   </GetPartyMaster>
   <GetPayable releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Payable>...
         </Payable>
      </DataArea>
   </GetPayable>
   <GetPaymentStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <PaymentStatus>...
         </PaymentStatus>
      </DataArea>
   </GetPaymentStatus>
   <GetPaymentStatusIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <PaymentStatusIST>...
         </PaymentStatusIST>
      </DataArea>
   </GetPaymentStatusIST>
   <GetPersonnel releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Personnel>...
         </Personnel>
      </DataArea>
   </GetPersonnel>
   <GetPickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <PickList>...
         </PickList>
      </DataArea>
   </GetPickList>
   <GetPlanningSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <PlanningSchedule>...
         </PlanningSchedule>
      </DataArea>
   </GetPlanningSchedule>
   <GetPriceList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <PriceList>...
         </PriceList>
      </DataArea>
   </GetPriceList>
   <GetProductAvailability releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ProductAvailability>...
         </ProductAvailability>
      </DataArea>
   </GetProductAvailability>
   <GetProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </GetProductionOrder>
   <GetProjectAccounting releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ProjectAccounting>...
         </ProjectAccounting>
      </DataArea>
   </GetProjectAccounting>
   <GetProjectMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ProjectMaster>...
         </ProjectMaster>
      </DataArea>
   </GetProjectMaster>
   <GetPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </GetPurchaseOrder>
   <GetQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Quote>...
         </Quote>
      </DataArea>
   </GetQuote>
   <GetReceivable releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Receivable>...
         </Receivable>
      </DataArea>
   </GetReceivable>
   <GetReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </GetReceiveDelivery>
   <GetReceiveItem releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ReceiveItem>...
         </ReceiveItem>
      </DataArea>
   </GetReceiveItem>
   <GetRecoverWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <RecoverWIP>...
         </RecoverWIP>
      </DataArea>
   </GetRecoverWIP>
   <GetRequireProduct releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <RequireProduct>...
         </RequireProduct>
      </DataArea>
   </GetRequireProduct>
   <GetRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Requisition>...
         </Requisition>
      </DataArea>
   </GetRequisition>
   <GetRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <RFQ>...
         </RFQ>
      </DataArea>
   </GetRFQ>
   <GetRiskControlLibrary releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <RiskControlLibrary>...
         </RiskControlLibrary>
      </DataArea>
   </GetRiskControlLibrary>
   <GetRouting releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Routing>...
         </Routing>
      </DataArea>
   </GetRouting>
   <GetSalesLead releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <SalesLead>...
         </SalesLead>
      </DataArea>
   </GetSalesLead>
   <GetSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </GetSalesOrder>
   <GetSequenceSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <SequenceSchedule>...
         </SequenceSchedule>
      </DataArea>
   </GetSequenceSchedule>
   <GetShipment releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <Shipment>...
         </Shipment>
      </DataArea>
   </GetShipment>
   <GetShipmentSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ShipmentSchedule>...
         </ShipmentSchedule>
      </DataArea>
   </GetShipmentSchedule>
   <GetShipmentUnit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <ShipmentUnit>...
         </ShipmentUnit>
      </DataArea>
   </GetShipmentUnit>
   <GetSplitWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <SplitWIP>...
         </SplitWIP>
      </DataArea>
   </GetSplitWIP>
   <GetSupplierPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <SupplierPartyMaster>...
         </SupplierPartyMaster>
      </DataArea>
   </GetSupplierPartyMaster>
   <GetUOMGroup releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <UOMGroup>...
         </UOMGroup>
      </DataArea>
   </GetUOMGroup>
   <GetWIPStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Get>
         </Get>
         <WIPStatus>...
         </WIPStatus>
      </DataArea>
   </GetWIPStatus>
   <IssueMoveInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Issue>
         </Issue>
         <MoveInventory>...
         </MoveInventory>
      </DataArea>
   </IssueMoveInventory>
   <ListActualLedger releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <ActualLedger>...
         </ActualLedger>
      </DataArea>
   </ListActualLedger>
   <ListBOM releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <BOM>...
         </BOM>
      </DataArea>
   </ListBOM>
   <ListInventoryCount releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <InventoryCount>...
         </InventoryCount>
      </DataArea>
   </ListInventoryCount>
   <ListItemMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <ItemMaster>...
         </ItemMaster>
      </DataArea>
   </ListItemMaster>
   <ListMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </ListMaintenanceOrder>
   <ListPickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <PickList>...
         </PickList>
      </DataArea>
   </ListPickList>
   <ListProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </ListProductionOrder>
   <ListPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </ListPurchaseOrder>
   <ListQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <Quote>...
         </Quote>
      </DataArea>
   </ListQuote>
   <ListReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </ListReceiveDelivery>
   <ListRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <Requisition>...
         </Requisition>
      </DataArea>
   </ListRequisition>
   <ListRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <RFQ>...
         </RFQ>
      </DataArea>
   </ListRFQ>
   <ListRouting releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <Routing>...
         </Routing>
      </DataArea>
   </ListRouting>
   <ListSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </ListSalesOrder>
   <ListUOMGroup releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <List>...
         </List>
         <UOMGroup>...
         </UOMGroup>
      </DataArea>
   </ListUOMGroup>
   <LoadActualLedger releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Load>
         </Load>
         <ActualLedger>...
         </ActualLedger>
      </DataArea>
   </LoadActualLedger>
   <LoadBudgetLedger releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Load>
         </Load>
         <BudgetLedger>...
         </BudgetLedger>
      </DataArea>
   </LoadBudgetLedger>
   <LoadInvoiceLedgerEntry releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Load>
         </Load>
         <InvoiceLedgerEntry>...
         </InvoiceLedgerEntry>
      </DataArea>
   </LoadInvoiceLedgerEntry>
   <LoadMatchDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Load>
         </Load>
         <MatchDocument>...
         </MatchDocument>
      </DataArea>
   </LoadMatchDocument>
   <LoadPayable releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Load>
         </Load>
         <Payable>...
         </Payable>
      </DataArea>
   </LoadPayable>
   <LoadProjectAccounting releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Load>
         </Load>
         <ProjectAccounting>...
         </ProjectAccounting>
      </DataArea>
   </LoadProjectAccounting>
   <LoadReceivable releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Load>
         </Load>
         <Receivable>...
         </Receivable>
      </DataArea>
   </LoadReceivable>
   <PostCostingActivity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Post>
         </Post>
         <CostingActivity>...
         </CostingActivity>
      </DataArea>
   </PostCostingActivity>
   <PostJournalEntry releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Post>
         </Post>
         <JournalEntry>...
         </JournalEntry>
      </DataArea>
   </PostJournalEntry>
   <PostMatchDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Post>
         </Post>
         <MatchDocument>...
         </MatchDocument>
      </DataArea>
   </PostMatchDocument>
   <ProcessAllocateResource releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <AllocateResource>...
         </AllocateResource>
      </DataArea>
   </ProcessAllocateResource>
   <ProcessConfirmWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <ConfirmWIP>...
         </ConfirmWIP>
      </DataArea>
   </ProcessConfirmWIP>
   <ProcessCredit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <Credit>...
         </Credit>
      </DataArea>
   </ProcessCredit>
   <ProcessCreditStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <CreditStatus>...
         </CreditStatus>
      </DataArea>
   </ProcessCreditStatus>
   <ProcessCreditTransfer releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <CreditTransfer>...
         </CreditTransfer>
      </DataArea>
   </ProcessCreditTransfer>
   <ProcessCreditTransferIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <CreditTransferIST>...
         </CreditTransferIST>
      </DataArea>
   </ProcessCreditTransferIST>
   <ProcessDebitTransfer releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <DebitTransfer>...
         </DebitTransfer>
      </DataArea>
   </ProcessDebitTransfer>
   <ProcessDebitTransferIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <DebitTransferIST>...
         </DebitTransferIST>
      </DataArea>
   </ProcessDebitTransferIST>
   <ProcessDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </ProcessDispatchList>
   <ProcessEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </ProcessEmployeeWorkTime>
   <ProcessEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </ProcessEngineeringChangeOrder>
   <ProcessEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </ProcessEngineeringWorkDocument>
   <ProcessInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </ProcessInspectDelivery>
   <ProcessInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </ProcessInventoryBalance>
   <ProcessInventoryConsumption releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <InventoryConsumption>...
         </InventoryConsumption>
      </DataArea>
   </ProcessInventoryConsumption>
   <ProcessInventoryCount releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <InventoryCount>...
         </InventoryCount>
      </DataArea>
   </ProcessInventoryCount>
   <ProcessInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <Invoice>...
         </Invoice>
      </DataArea>
   </ProcessInvoice>
   <ProcessIssueInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <IssueInventory>...
         </IssueInventory>
      </DataArea>
   </ProcessIssueInventory>
   <ProcessMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </ProcessMaintenanceOrder>
   <ProcessMergeWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <MergeWIP>...
         </MergeWIP>
      </DataArea>
   </ProcessMergeWIP>
   <ProcessMoveInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <MoveInventory>...
         </MoveInventory>
      </DataArea>
   </ProcessMoveInventory>
   <ProcessMoveWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <MoveWIP>...
         </MoveWIP>
      </DataArea>
   </ProcessMoveWIP>
   <ProcessOnlineOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <OnlineOrder>...
         </OnlineOrder>
      </DataArea>
   </ProcessOnlineOrder>
   <ProcessOperation releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <Operation>...
         </Operation>
      </DataArea>
   </ProcessOperation>
   <ProcessOpportunity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <Opportunity>...
         </Opportunity>
      </DataArea>
   </ProcessOpportunity>
   <ProcessPaymentStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <PaymentStatus>...
         </PaymentStatus>
      </DataArea>
   </ProcessPaymentStatus>
   <ProcessPaymentStatusIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <PaymentStatusIST>...
         </PaymentStatusIST>
      </DataArea>
   </ProcessPaymentStatusIST>
   <ProcessPickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <PickList>...
         </PickList>
      </DataArea>
   </ProcessPickList>
   <ProcessProductAvailability releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <ProductAvailability>...
         </ProductAvailability>
      </DataArea>
   </ProcessProductAvailability>
   <ProcessProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </ProcessProductionOrder>
   <ProcessPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </ProcessPurchaseOrder>
   <ProcessQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <Quote>...
         </Quote>
      </DataArea>
   </ProcessQuote>
   <ProcessReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </ProcessReceiveDelivery>
   <ProcessReceiveItem releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <ReceiveItem>...
         </ReceiveItem>
      </DataArea>
   </ProcessReceiveItem>
   <ProcessRecoverWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <RecoverWIP>...
         </RecoverWIP>
      </DataArea>
   </ProcessRecoverWIP>
   <ProcessRequireProduct releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <RequireProduct>...
         </RequireProduct>
      </DataArea>
   </ProcessRequireProduct>
   <ProcessRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <Requisition>...
         </Requisition>
      </DataArea>
   </ProcessRequisition>
   <ProcessRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <RFQ>...
         </RFQ>
      </DataArea>
   </ProcessRFQ>
   <ProcessRiskControlLibrary releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <RiskControlLibrary>...
         </RiskControlLibrary>
      </DataArea>
   </ProcessRiskControlLibrary>
   <ProcessSalesLead releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <SalesLead>...
         </SalesLead>
      </DataArea>
   </ProcessSalesLead>
   <ProcessSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </ProcessSalesOrder>
   <ProcessShipment releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <Shipment>...
         </Shipment>
      </DataArea>
   </ProcessShipment>
   <ProcessShipmentUnit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <ShipmentUnit>...
         </ShipmentUnit>
      </DataArea>
   </ProcessShipmentUnit>
   <ProcessSplitWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <SplitWIP>...
         </SplitWIP>
      </DataArea>
   </ProcessSplitWIP>
   <ProcessWIPStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Process>
         </Process>
         <WIPStatus>...
         </WIPStatus>
      </DataArea>
   </ProcessWIPStatus>
   <ReceiveMoveInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Receive>
         </Receive>
         <MoveInventory>...
         </MoveInventory>
      </DataArea>
   </ReceiveMoveInventory>
   <ReceiveProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Receive>
         </Receive>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </ReceiveProductionOrder>
   <ReceivePurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Receive>
         </Receive>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </ReceivePurchaseOrder>
   <RespondConfirmWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <ConfirmWIP>...
         </ConfirmWIP>
      </DataArea>
   </RespondConfirmWIP>
   <RespondCredit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <Credit>...
         </Credit>
      </DataArea>
   </RespondCredit>
   <RespondCreditStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <CreditStatus>...
         </CreditStatus>
      </DataArea>
   </RespondCreditStatus>
   <RespondDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </RespondDispatchList>
   <RespondEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </RespondEmployeeWorkTime>
   <RespondEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </RespondEngineeringChangeOrder>
   <RespondEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </RespondEngineeringWorkDocument>
   <RespondInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </RespondInspectDelivery>
   <RespondInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </RespondInventoryBalance>
   <RespondInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <Invoice>...
         </Invoice>
      </DataArea>
   </RespondInvoice>
   <RespondMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </RespondMaintenanceOrder>
   <RespondOnlineOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <OnlineOrder>...
         </OnlineOrder>
      </DataArea>
   </RespondOnlineOrder>
   <RespondOpportunity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <Opportunity>...
         </Opportunity>
      </DataArea>
   </RespondOpportunity>
   <RespondPickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <PickList>...
         </PickList>
      </DataArea>
   </RespondPickList>
   <RespondProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </RespondProductionOrder>
   <RespondPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </RespondPurchaseOrder>
   <RespondQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <Quote>...
         </Quote>
      </DataArea>
   </RespondQuote>
   <RespondReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </RespondReceiveDelivery>
   <RespondRequireProduct releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <RequireProduct>...
         </RequireProduct>
      </DataArea>
   </RespondRequireProduct>
   <RespondRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <Requisition>...
         </Requisition>
      </DataArea>
   </RespondRequisition>
   <RespondRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <RFQ>...
         </RFQ>
      </DataArea>
   </RespondRFQ>
   <RespondSalesLead releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <SalesLead>...
         </SalesLead>
      </DataArea>
   </RespondSalesLead>
   <RespondSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Respond>...
         </Respond>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </RespondSalesOrder>
   <ShowActualLedger releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ActualLedger>...
         </ActualLedger>
      </DataArea>
   </ShowActualLedger>
   <ShowAllocateResource releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <AllocateResource>...
         </AllocateResource>
      </DataArea>
   </ShowAllocateResource>
   <ShowBOM releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <BOM>...
         </BOM>
      </DataArea>
   </ShowBOM>
   <ShowBudgetLedger releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <BudgetLedger>...
         </BudgetLedger>
      </DataArea>
   </ShowBudgetLedger>
   <ShowCarrierRoute releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <CarrierRoute>...
         </CarrierRoute>
      </DataArea>
   </ShowCarrierRoute>
   <ShowCatalog releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Catalog>...
         </Catalog>
      </DataArea>
   </ShowCatalog>
   <ShowChartOfAccounts releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ChartOfAccounts>...
         </ChartOfAccounts>
      </DataArea>
   </ShowChartOfAccounts>
   <ShowConfirmWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ConfirmWIP>...
         </ConfirmWIP>
      </DataArea>
   </ShowConfirmWIP>
   <ShowCostingActivity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <CostingActivity>...
         </CostingActivity>
      </DataArea>
   </ShowCostingActivity>
   <ShowCredit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Credit>...
         </Credit>
      </DataArea>
   </ShowCredit>
   <ShowCreditStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <CreditStatus>...
         </CreditStatus>
      </DataArea>
   </ShowCreditStatus>
   <ShowCreditTransfer releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <CreditTransfer>...
         </CreditTransfer>
      </DataArea>
   </ShowCreditTransfer>
   <ShowCreditTransferIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <CreditTransferIST>...
         </CreditTransferIST>
      </DataArea>
   </ShowCreditTransferIST>
   <ShowCurrencyExchangeRate releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <CurrencyExchangeRate>...
         </CurrencyExchangeRate>
      </DataArea>
   </ShowCurrencyExchangeRate>
   <ShowCustomerPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <CustomerPartyMaster>...
         </CustomerPartyMaster>
      </DataArea>
   </ShowCustomerPartyMaster>
   <ShowDebitTransfer releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <DebitTransfer>...
         </DebitTransfer>
      </DataArea>
   </ShowDebitTransfer>
   <ShowDebitTransferIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <DebitTransferIST>...
         </DebitTransferIST>
      </DataArea>
   </ShowDebitTransferIST>
   <ShowDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </ShowDispatchList>
   <ShowEmployeeWorkSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <EmployeeWorkSchedule>...
         </EmployeeWorkSchedule>
      </DataArea>
   </ShowEmployeeWorkSchedule>
   <ShowEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </ShowEmployeeWorkTime>
   <ShowEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </ShowEngineeringChangeOrder>
   <ShowEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </ShowEngineeringWorkDocument>
   <ShowField releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Field>...
         </Field>
      </DataArea>
   </ShowField>
   <ShowInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </ShowInspectDelivery>
   <ShowInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </ShowInventoryBalance>
   <ShowInventoryConsumption releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <InventoryConsumption>...
         </InventoryConsumption>
      </DataArea>
   </ShowInventoryConsumption>
   <ShowInventoryCount releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <InventoryCount>...
         </InventoryCount>
      </DataArea>
   </ShowInventoryCount>
   <ShowInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Invoice>...
         </Invoice>
      </DataArea>
   </ShowInvoice>
   <ShowInvoiceLedgerEntry releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <InvoiceLedgerEntry>...
         </InvoiceLedgerEntry>
      </DataArea>
   </ShowInvoiceLedgerEntry>
   <ShowIssueInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <IssueInventory>...
         </IssueInventory>
      </DataArea>
   </ShowIssueInventory>
   <ShowItemMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ItemMaster>...
         </ItemMaster>
      </DataArea>
   </ShowItemMaster>
   <ShowJournalEntry releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <JournalEntry>...
         </JournalEntry>
      </DataArea>
   </ShowJournalEntry>
   <ShowLocation releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Location>...
         </Location>
      </DataArea>
   </ShowLocation>
   <ShowLocationService releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <LocationService>...
         </LocationService>
      </DataArea>
   </ShowLocationService>
   <ShowMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </ShowMaintenanceOrder>
   <ShowMatchDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <MatchDocument>...
         </MatchDocument>
      </DataArea>
   </ShowMatchDocument>
   <ShowMergeWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <MergeWIP>...
         </MergeWIP>
      </DataArea>
   </ShowMergeWIP>
   <ShowMoveInventory releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <MoveInventory>...
         </MoveInventory>
      </DataArea>
   </ShowMoveInventory>
   <ShowMoveWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <MoveWIP>...
         </MoveWIP>
      </DataArea>
   </ShowMoveWIP>
   <ShowOnlineOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <OnlineOrder>...
         </OnlineOrder>
      </DataArea>
   </ShowOnlineOrder>
   <ShowOnlineSession releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <OnlineSession>...
         </OnlineSession>
      </DataArea>
   </ShowOnlineSession>
   <ShowOperation releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Operation>...
         </Operation>
      </DataArea>
   </ShowOperation>
   <ShowOpportunity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Opportunity>...
         </Opportunity>
      </DataArea>
   </ShowOpportunity>
   <ShowPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <PartyMaster>...
         </PartyMaster>
      </DataArea>
   </ShowPartyMaster>
   <ShowPayable releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Payable>...
         </Payable>
      </DataArea>
   </ShowPayable>
   <ShowPaymentStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <PaymentStatus>...
         </PaymentStatus>
      </DataArea>
   </ShowPaymentStatus>
   <ShowPaymentStatusIST releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <PaymentStatusIST>...
         </PaymentStatusIST>
      </DataArea>
   </ShowPaymentStatusIST>
   <ShowPersonnel releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Personnel>...
         </Personnel>
      </DataArea>
   </ShowPersonnel>
   <ShowPickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <PickList>...
         </PickList>
      </DataArea>
   </ShowPickList>
   <ShowPlanningSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <PlanningSchedule>...
         </PlanningSchedule>
      </DataArea>
   </ShowPlanningSchedule>
   <ShowPriceList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <PriceList>...
         </PriceList>
      </DataArea>
   </ShowPriceList>
   <ShowProductAvailability releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ProductAvailability>...
         </ProductAvailability>
      </DataArea>
   </ShowProductAvailability>
   <ShowProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </ShowProductionOrder>
   <ShowProjectAccounting releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ProjectAccounting>...
         </ProjectAccounting>
      </DataArea>
   </ShowProjectAccounting>
   <ShowProjectMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ProjectMaster>...
         </ProjectMaster>
      </DataArea>
   </ShowProjectMaster>
   <ShowPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </ShowPurchaseOrder>
   <ShowQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Quote>...
         </Quote>
      </DataArea>
   </ShowQuote>
   <ShowReceivable releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Receivable>...
         </Receivable>
      </DataArea>
   </ShowReceivable>
   <ShowReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </ShowReceiveDelivery>
   <ShowReceiveItem releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ReceiveItem>...
         </ReceiveItem>
      </DataArea>
   </ShowReceiveItem>
   <ShowRecoverWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <RecoverWIP>...
         </RecoverWIP>
      </DataArea>
   </ShowRecoverWIP>
   <ShowRequireProduct releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <RequireProduct>...
         </RequireProduct>
      </DataArea>
   </ShowRequireProduct>
   <ShowRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Requisition>...
         </Requisition>
      </DataArea>
   </ShowRequisition>
   <ShowRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <RFQ>...
         </RFQ>
      </DataArea>
   </ShowRFQ>
   <ShowRiskControlLibrary releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <RiskControlLibrary>...
         </RiskControlLibrary>
      </DataArea>
   </ShowRiskControlLibrary>
   <ShowRouting releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Routing>...
         </Routing>
      </DataArea>
   </ShowRouting>
   <ShowSalesLead releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <SalesLead>...
         </SalesLead>
      </DataArea>
   </ShowSalesLead>
   <ShowSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </ShowSalesOrder>
   <ShowSequenceSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <SequenceSchedule>...
         </SequenceSchedule>
      </DataArea>
   </ShowSequenceSchedule>
   <ShowShipment releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <Shipment>...
         </Shipment>
      </DataArea>
   </ShowShipment>
   <ShowShipmentSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ShipmentSchedule>...
         </ShipmentSchedule>
      </DataArea>
   </ShowShipmentSchedule>
   <ShowShipmentUnit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <ShipmentUnit>...
         </ShipmentUnit>
      </DataArea>
   </ShowShipmentUnit>
   <ShowSplitWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <SplitWIP>...
         </SplitWIP>
      </DataArea>
   </ShowSplitWIP>
   <ShowSupplierPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <SupplierPartyMaster>...
         </SupplierPartyMaster>
      </DataArea>
   </ShowSupplierPartyMaster>
   <ShowUOMGroup releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <UOMGroup>...
         </UOMGroup>
      </DataArea>
   </ShowUOMGroup>
   <ShowWIPStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Show>...
         </Show>
         <WIPStatus>...
         </WIPStatus>
      </DataArea>
   </ShowWIPStatus>
   <SyncAllocateResource releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <AllocateResource>...
         </AllocateResource>
      </DataArea>
   </SyncAllocateResource>
   <SyncBOM releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <BOM>...
         </BOM>
      </DataArea>
   </SyncBOM>
   <SyncCarrierRoute releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <CarrierRoute>...
         </CarrierRoute>
      </DataArea>
   </SyncCarrierRoute>
   <SyncCatalog releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Catalog>...
         </Catalog>
      </DataArea>
   </SyncCatalog>
   <SyncChartOfAccounts releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <ChartOfAccounts>...
         </ChartOfAccounts>
      </DataArea>
   </SyncChartOfAccounts>
   <SyncCredit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Credit>...
         </Credit>
      </DataArea>
   </SyncCredit>
   <SyncCreditStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <CreditStatus>...
         </CreditStatus>
      </DataArea>
   </SyncCreditStatus>
   <SyncCurrencyExchangeRate releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <CurrencyExchangeRate>...
         </CurrencyExchangeRate>
      </DataArea>
   </SyncCurrencyExchangeRate>
   <SyncCustomerPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <CustomerPartyMaster>...
         </CustomerPartyMaster>
      </DataArea>
   </SyncCustomerPartyMaster>
   <SyncDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </SyncDispatchList>
   <SyncEmployeeWorkSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <EmployeeWorkSchedule>...
         </EmployeeWorkSchedule>
      </DataArea>
   </SyncEmployeeWorkSchedule>
   <SyncEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </SyncEmployeeWorkTime>
   <SyncEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </SyncEngineeringChangeOrder>
   <SyncEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </SyncEngineeringWorkDocument>
   <SyncField releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Field>...
         </Field>
      </DataArea>
   </SyncField>
   <SyncInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </SyncInspectDelivery>
   <SyncInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </SyncInventoryBalance>
   <SyncInventoryConsumption releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <InventoryConsumption>...
         </InventoryConsumption>
      </DataArea>
   </SyncInventoryConsumption>
   <SyncInventoryCount releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <InventoryCount>...
         </InventoryCount>
      </DataArea>
   </SyncInventoryCount>
   <SyncInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Invoice>...
         </Invoice>
      </DataArea>
   </SyncInvoice>
   <SyncItemMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <ItemMaster>...
         </ItemMaster>
      </DataArea>
   </SyncItemMaster>
   <SyncLocation releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Location>...
         </Location>
      </DataArea>
   </SyncLocation>
   <SyncMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </SyncMaintenanceOrder>
   <SyncOnlineOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <OnlineOrder>...
         </OnlineOrder>
      </DataArea>
   </SyncOnlineOrder>
   <SyncOperation releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Operation>...
         </Operation>
      </DataArea>
   </SyncOperation>
   <SyncOpportunity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Opportunity>...
         </Opportunity>
      </DataArea>
   </SyncOpportunity>
   <SyncPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <PartyMaster>...
         </PartyMaster>
      </DataArea>
   </SyncPartyMaster>
   <SyncPersonnel releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Personnel>...
         </Personnel>
      </DataArea>
   </SyncPersonnel>
   <SyncPickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <PickList>...
         </PickList>
      </DataArea>
   </SyncPickList>
   <SyncPlanningSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <PlanningSchedule>...
         </PlanningSchedule>
      </DataArea>
   </SyncPlanningSchedule>
   <SyncPriceList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <PriceList>...
         </PriceList>
      </DataArea>
   </SyncPriceList>
   <SyncProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </SyncProductionOrder>
   <SyncProjectMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <ProjectMaster>...
         </ProjectMaster>
      </DataArea>
   </SyncProjectMaster>
   <SyncPurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </SyncPurchaseOrder>
   <SyncQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Quote>...
         </Quote>
      </DataArea>
   </SyncQuote>
   <SyncRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Requisition>...
         </Requisition>
      </DataArea>
   </SyncRequisition>
   <SyncRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <RFQ>...
         </RFQ>
      </DataArea>
   </SyncRFQ>
   <SyncRiskControlLibrary releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <RiskControlLibrary>...
         </RiskControlLibrary>
      </DataArea>
   </SyncRiskControlLibrary>
   <SyncRouting releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Routing>...
         </Routing>
      </DataArea>
   </SyncRouting>
   <SyncSalesLead releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <SalesLead>...
         </SalesLead>
      </DataArea>
   </SyncSalesLead>
   <SyncSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </SyncSalesOrder>
   <SyncSequenceSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <SequenceSchedule>...
         </SequenceSchedule>
      </DataArea>
   </SyncSequenceSchedule>
   <SyncShipment releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <Shipment>...
         </Shipment>
      </DataArea>
   </SyncShipment>
   <SyncShipmentSchedule releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <ShipmentSchedule>...
         </ShipmentSchedule>
      </DataArea>
   </SyncShipmentSchedule>
   <SyncShipmentUnit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <ShipmentUnit>...
         </ShipmentUnit>
      </DataArea>
   </SyncShipmentUnit>
   <SyncSupplierPartyMaster releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <SupplierPartyMaster>...
         </SupplierPartyMaster>
      </DataArea>
   </SyncSupplierPartyMaster>
   <SyncUOMGroup releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Sync>
         </Sync>
         <UOMGroup>...
         </UOMGroup>
      </DataArea>
   </SyncUOMGroup>
   <UpdateConfirmWIP releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <ConfirmWIP>...
         </ConfirmWIP>
      </DataArea>
   </UpdateConfirmWIP>
   <UpdateCredit releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <Credit>...
         </Credit>
      </DataArea>
   </UpdateCredit>
   <UpdateCreditStatus releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <CreditStatus>...
         </CreditStatus>
      </DataArea>
   </UpdateCreditStatus>
   <UpdateDispatchList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <DispatchList>...
         </DispatchList>
      </DataArea>
   </UpdateDispatchList>
   <UpdateEmployeeWorkTime releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <EmployeeWorkTime>...
         </EmployeeWorkTime>
      </DataArea>
   </UpdateEmployeeWorkTime>
   <UpdateEngineeringChangeOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <EngineeringChangeOrder>...
         </EngineeringChangeOrder>
      </DataArea>
   </UpdateEngineeringChangeOrder>
   <UpdateEngineeringWorkDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <EngineeringWorkDocument>...
         </EngineeringWorkDocument>
      </DataArea>
   </UpdateEngineeringWorkDocument>
   <UpdateInspectDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <InspectDelivery>...
         </InspectDelivery>
      </DataArea>
   </UpdateInspectDelivery>
   <UpdateInventoryBalance releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <InventoryBalance>...
         </InventoryBalance>
      </DataArea>
   </UpdateInventoryBalance>
   <UpdateInventoryCount releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <InventoryCount>...
         </InventoryCount>
      </DataArea>
   </UpdateInventoryCount>
   <UpdateInvoice releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <Invoice>...
         </Invoice>
      </DataArea>
   </UpdateInvoice>
   <UpdateMaintenanceOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <MaintenanceOrder>...
         </MaintenanceOrder>
      </DataArea>
   </UpdateMaintenanceOrder>
   <UpdateMatchDocument releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <MatchDocument>...
         </MatchDocument>
      </DataArea>
   </UpdateMatchDocument>
   <UpdateOnlineOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <OnlineOrder>...
         </OnlineOrder>
      </DataArea>
   </UpdateOnlineOrder>
   <UpdateOpportunity releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <Opportunity>...
         </Opportunity>
      </DataArea>
   </UpdateOpportunity>
   <UpdatePickList releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <PickList>...
         </PickList>
      </DataArea>
   </UpdatePickList>
   <UpdateProductionOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <ProductionOrder>...
         </ProductionOrder>
      </DataArea>
   </UpdateProductionOrder>
   <UpdatePurchaseOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <PurchaseOrder>...
         </PurchaseOrder>
      </DataArea>
   </UpdatePurchaseOrder>
   <UpdateQuote releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <Quote>...
         </Quote>
      </DataArea>
   </UpdateQuote>
   <UpdateReceiveDelivery releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <ReceiveDelivery>...
         </ReceiveDelivery>
      </DataArea>
   </UpdateReceiveDelivery>
   <UpdateRequireProduct releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <RequireProduct>...
         </RequireProduct>
      </DataArea>
   </UpdateRequireProduct>
   <UpdateRequisition releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <Requisition>...
         </Requisition>
      </DataArea>
   </UpdateRequisition>
   <UpdateRFQ releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <RFQ>...
         </RFQ>
      </DataArea>
   </UpdateRFQ>
   <UpdateSalesLead releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <SalesLead>...
         </SalesLead>
      </DataArea>
   </UpdateSalesLead>
   <UpdateSalesOrder releaseID="normalizedString">
      <ApplicationArea>
         <Sender>...
         </Sender>
         <Receiver>...
         </Receiver>
         <CreationDateTime>2000-01-01</CreationDateTime>
         <Signature>
            <!--any element-->
         </Signature>
         <BODID>normalizedString</BODID>
         <UserArea>
            <!--any element-->
         </UserArea>
      </ApplicationArea>
      <DataArea>
         <Update>
         </Update>
         <SalesOrder>...
         </SalesOrder>
      </DataArea>
   </UpdateSalesOrder>
</OAGIS9BODs>