<?xml version="1.0" encoding="utf-8"?>
<edmx:Edmx Version="1.0" xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:sap="http://www.sap.com/Protocols/SAPData">
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_COMMON',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="com.sap.vocabularies.Common.v1" Alias="Common"/>
 </edmx:Reference>
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_CAPABILITIES',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="Org.OData.Capabilities.V1" Alias="Capabilities"/>
 </edmx:Reference>
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_COMMUNICATION',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="com.sap.vocabularies.Communication.v1" Alias="Communication"/>
 </edmx:Reference>
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_AGGREGATION',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="Org.OData.Aggregation.V1" Alias="Aggregation"/>
 </edmx:Reference>
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_PERSONALDATA',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="com.sap.vocabularies.PersonalData.v1" Alias="PersonalData"/>
 </edmx:Reference>
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_VALIDATION',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="Org.OData.Validation.V1" Alias="Validation"/>
 </edmx:Reference>
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_ANALYTICS',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="com.sap.vocabularies.Analytics.v1" Alias="Analytics"/>
 </edmx:Reference>
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_MEASURES',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="Org.OData.Measures.V1" Alias="Measures"/>
 </edmx:Reference>
 <edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_UI',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
  <edmx:Include Namespace="com.sap.vocabularies.UI.v1" Alias="UI"/>
 </edmx:Reference>
 <edmx:DataServices m:DataServiceVersion="2.0">
  <Schema Namespace="API_SALES_ORDER_SRV" xml:lang="en" sap:schema-version="1" xmlns="http://schemas.microsoft.com/ado/2008/09/edm">
   <EntityType Name="A_SalesOrderType" sap:label="Sales Order Header" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order"/>
    <Property Name="SalesOrderType" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Sales Order Type"/>
    <Property Name="SalesOrganization" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Sales Organization">
     <Documentation>
      <Summary>An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.</Summary>
      <LongDescription>You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="DistributionChannel" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Distribution Channel">
     <Documentation>
      <Summary>The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.</Summary>
      <LongDescription>You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="OrganizationDivision" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Division">
     <Documentation>
      <Summary>A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.</Summary>
      <LongDescription>A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SalesGroup" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Sales Group">
     <Documentation>
      <Summary>A group of sales people who are responsible for processing sales of certain products or services.</Summary>
      <LongDescription>By using sales groups you can designate different areas of responsibility within a sales office.  When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SalesOffice" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Sales Office">
     <Documentation>
      <Summary>A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.</Summary>
      <LongDescription>When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SalesDistrict" Type="Edm.String" MaxLength="6" sap:display-format="UpperCase" sap:label="Sales District">
     <Documentation>
      <Summary>A geographical sales district or region.</Summary>
      <LongDescription>Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SoldToParty" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Sold-to Party">
     <Documentation>
      <Summary>The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="CreationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Created On" sap:quickinfo="Date on Which Record Was Created" sap:creatable="false" sap:updatable="false"/>
    <Property Name="CreatedByUser" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Created By" sap:quickinfo="Name of Person Who Created Object" sap:creatable="false" sap:updatable="false"/>
    <Property Name="LastChangeDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Changed On" sap:quickinfo="Date of Last Change" sap:creatable="false" sap:updatable="false"/>
    <Property Name="SenderBusinessSystemName" Type="Edm.String" MaxLength="60" sap:label="Ext. Bus. Syst. ID" sap:quickinfo="External Business System ID" sap:creatable="false" sap:updatable="false"/>
    <Property Name="ExternalDocumentID" Type="Edm.String" MaxLength="40" sap:display-format="UpperCase" sap:label="External Document ID" sap:creatable="false" sap:updatable="false"/>
    <Property Name="LastChangeDateTime" Type="Edm.DateTimeOffset" Precision="7" ConcurrencyMode="Fixed" sap:label="Time Stamp" sap:quickinfo="UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).</Summary>
      <LongDescription>In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ExternalDocLastChangeDateTime" Type="Edm.DateTimeOffset" Precision="7" sap:label="External Revision" sap:quickinfo="Timestamp for Revision of External Calls" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PurchaseOrderByCustomer" Type="Edm.String" MaxLength="35" sap:label="Customer Reference">
     <Documentation>
      <Summary>Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).</Summary>
      <LongDescription>The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PurchaseOrderByShipToParty" Type="Edm.String" MaxLength="35" sap:label="Purchase Order No." sap:quickinfo="Ship-to Party's Purchase Order Number">
     <Documentation>
      <Summary>Number used by the end customer for unique identification of the purchasing document (e.g. inquiry or purchase).</Summary>
      <LongDescription>The number is the link between the end customer's purchase order and the sales documents that you have created. You can use the end customer's number for correspondence with the customer, in particular for finding certain document information. If the number refers to a purchase order, you can also print documents that you wish to send to the end customer, such as the delivery note.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerPurchaseOrderType" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Purchase Order Type" sap:quickinfo="Customer Purchase Order Type">
     <Documentation>
      <Summary>The way in which the sales document (the inquiry or sales order, for example) arrives from the customer.</Summary>
      <LongDescription>You can record here whether the sales document arrived, for example, by telephone, mail, or fax.Enter one of the values predefined for your system.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerPurchaseOrderDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Customer Ref. Date" sap:quickinfo="Customer Reference Date">
     <Documentation>
      <Summary>The date that appears on the customer's purchase order. This date can be, for example, the date on which the customer created the purchase order.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="SalesOrderDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Document Date" sap:quickinfo="Document Date (Date Received/Sent)">
     <Documentation>
      <Summary>The date on which you want the sales document (the sales order, for example) to become effective for sales management purposes.</Summary>
      <LongDescription>When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected. You can define the document date to meet the needs of your organization.For sales orders, for example, you can define the document date as the date when the order actually arrives at your offices. Alternatively, you could define it as the date when the order was written up by a field sales representative.The system proposes the current date. You can change it manually in the sales document.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="TotalNetAmount" Type="Edm.Decimal" Precision="16" Scale="3" sap:unit="TransactionCurrency" sap:label="Net Value" sap:quickinfo="Net Value of the Sales Order in Document Currency" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The total value of all items in the sales document, after any discounts and surcharges are taken into account. The value is expressed in the document currency.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="TransactionCurrency" Type="Edm.String" MaxLength="5" sap:label="Document Currency" sap:quickinfo="SD Document Currency" sap:semantics="currency-code">
     <Documentation>
      <Summary>The currency that applies to the document (for example, to a sales order or an invoice).</Summary>
      <LongDescription>The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SDDocumentReason" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Order Reason" sap:quickinfo="Order Reason (Reason for the Business Transaction)">
     <Documentation>
      <Summary>Indicates the reason for creating the sales document.</Summary>
      <LongDescription>You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria.Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason.If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PricingDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Pricing Date" sap:quickinfo="Date for Pricing and Exchange Rate">
     <Documentation>
      <Summary>The date that determines date-related pricing elements, such as conditions and foreign exchange rate.</Summary>
      <LongDescription>You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PriceDetnExchangeRate" Type="Edm.Decimal" Precision="9" Scale="5" sap:label="Exchange Rate" sap:quickinfo="Exchange Rate for Price Determination"/>
    <Property Name="RequestedDeliveryDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Requested Delivery Date">
     <Documentation>
      <Summary>The date on which the customer would like ordered goods to be delivered.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ShippingCondition" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Shipping Conditions">
     <Documentation>
      <Summary>General shipping strategy for the delivery of goods from the vendor to the customer.</Summary>
      <LongDescription>You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CompleteDeliveryIsDefined" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Complete Delivery" sap:quickinfo="Complete Delivery Defined for Each Sales Order?">
     <Documentation>
      <Summary>Indicates whether a sales order must be delivered completely in a single delivery or whether the order can be partially delivered and completed over a number of deliveries.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ShippingType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Shipping Type">
     <Documentation>
      <Summary>Shipping type (for example, by road or rail) that has been selected for the transportation of the goods for the shipment legs.</Summary>
      <LongDescription>During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination</LongDescription>
     </Documentation>
    </Property>
    <Property Name="HeaderBillingBlockReason" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Billing Block" sap:quickinfo="Billing Block in SD Document">
     <Documentation>
      <Summary>Indicates if the entire sales document is blocked for billing.</Summary>
      <LongDescription>The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="DeliveryBlockReason" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Delivery Block" sap:quickinfo="Delivery Block (Document Header)">
     <Documentation>
      <Summary>Indicates if an entire sales document (a sales order, for example) is blocked for delivery.</Summary>
      <LongDescription>The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="DeliveryDateTypeRule" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Deliv Date Rule" sap:quickinfo="Delivery Date Rule">
     <Documentation>
      <Summary>Indicates when the ordered goods should be delivered.</Summary>
      <LongDescription>You can choose one of the following options:The goods should be delivered on the requested delivery date or later. Note that there is no guarantee that the goods will not be delivered earlier.The goods must be delivered exactly on the confirmed delivery date.The goods must be delivered by the confirmed delivery date (that is, on the date or earlier).You can set the delivery date rule on header level to set a default for any items that you create afterwards.In Transportation Management (TM), this field has the following implications:If you want the goods to be delivered on the requested delivery date or later, the delivery date/time is used as the earliest requested delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered on the confirmed delivery date, the start of the delivery date is used as the earliest acceptable delivery date/time and the end of the delivery date as the latest acceptable delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered by the confirmed delivery date, the end of the delivery date is used as the latest acceptable delivery date/time of the freight unit which contains the sales order item.Note: If you want to the goods to be delivered on or by the confirmed delivery date, the system ignores the rule for pick-up and delivery window and the condition for pick-up and delivery window determination which you have defined in the freight unit type for the delivery stop.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsClassification" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Incoterms" sap:quickinfo="Incoterms (Part 1)">
     <Documentation>
      <Summary>Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).</Summary>
      <LongDescription>Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsTransferLocation" Type="Edm.String" MaxLength="28" sap:label="Incoterms (Part 2)">
     <Documentation>
      <Summary>Additional information for the primary Incoterm.</Summary>
      <LongDescription>If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsLocation1" Type="Edm.String" MaxLength="70" sap:label="Incoterms Location 1">
     <Documentation>
      <Summary>Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:</Summary>
      <LongDescription>1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description  Location 1 EXW Ex Works  Place of DeliveryFCA Free Carrier  Place of DeliveryCPT Carriage Paid To  Place of DestinationCIP Carriage &amp; Insurance Paid To  Place of DestinationDAF Delivered at Frontier  Place of DeliveryDDP Delivered Duty Paid  Place of DestinationDDU Delivered Duty Unpaid  Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost &amp; Freight Port of DestinationCIF Cost Insurance &amp; Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsLocation2" Type="Edm.String" MaxLength="70" sap:label="Incoterms Location 2">
     <Documentation>
      <Summary>Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:</Summary>
      <LongDescription>No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -&gt; Business Partners -&gt; Customers -&gt; Billing Document -&gt; Incoterms -&gt; Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage &amp; Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost &amp; Freight Port of DestinationCIF Cost Insurance &amp; Freight Port of Destination</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsVersion" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Incoterms Version">
     <Documentation>
      <Summary>An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="CustomerPriceGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Customer Price Group">
     <Documentation>
      <Summary>A grouping of customers who share the same pricing requirements.</Summary>
      <LongDescription>You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PriceListType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Price List Type">
     <Documentation>
      <Summary>Identifies a price list or other condition type (for example, a surcharge or discount).</Summary>
      <LongDescription>You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerPaymentTerms" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Terms of Payment" sap:quickinfo="Terms of Payment Key">
     <Documentation>
      <Summary>Key for defining payment terms composed of cash discount percentages and payment periods.</Summary>
      <LongDescription>It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PaymentMethod" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Payment Method">
     <Documentation>
      <Summary>Payment method with which this item is to be paid.</Summary>
      <LongDescription>If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="FixedValueDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Fixed Value Date">
     <Documentation>
      <Summary>The date on which the terms of payment related to the sales document become effective.</Summary>
      <LongDescription>If you enter a date in this field, you cannot enter a value in the additional value days field.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="AssignmentReference" Type="Edm.String" MaxLength="18" sap:label="Assignment" sap:quickinfo="Assignment Number">
     <Documentation>
      <Summary>The allocation is additional information in the customer line item of the journal entry.</Summary>
      <LongDescription>The line items of an account are displayed in sort sequence according to the content of the field.The allocation number is set in the billing document in accordance with control in document flow and transferred to the financial journal entry.It is possible to set the customer purchase order number, the customer order number, the delivery number or the external delivery number as allocation numbers.The field is a separating criterion in the billing document.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ReferenceSDDocument" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Reference Document" sap:quickinfo="Document Number of the Reference Document">
     <Documentation>
      <Summary>Identifies the sales order to which the delivery refers.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ReferenceSDDocumentCategory" Type="Edm.String" MaxLength="4" sap:label="Preceding Doc.Categ." sap:quickinfo="Document Category of Preceding SD Document" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Specifies the sales document category of the preceding sales, delivery, or billing document.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AccountingDocExternalReference" Type="Edm.String" MaxLength="16" sap:display-format="UpperCase" sap:label="Reference" sap:quickinfo="Reference Document Number">
     <Documentation>
      <Summary>The reference document number contains the document number with the business partner</Summary>
      <LongDescription>The reference document number serves as a search criterion when displaying or changing documents.  In correspondence, the refererence document number is sometimes printed instead of the document number.The reference number is set in the document flow according to control and taken into the financial journal entry.You can set the customer order number, the order number, the delivery number, the billing number or the external delivery number as reference number.The field is a seperation criterion in the billing document.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerAccountAssignmentGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Acct Assmt Grp Cust." sap:quickinfo="Account Assignment Group for this Customer">
     <Documentation>
      <Summary>The account assignment group to which the system automatically posts the sales document.</Summary>
      <LongDescription>The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="AccountingExchangeRate" Type="Edm.Decimal" Precision="9" Scale="5" sap:label="Exchng. Rate Accntg." sap:quickinfo="Exchange rate for FI postings">
     <Documentation>
      <Summary>The exchange rate that the system applies when you create an invoice.</Summary>
      <LongDescription>Your system is configured in such a way that it expects:No prefix (leading sign) for direct ratesA "" as prefix (leading sign) for direct ratesNo prefix for indirect ratesA "" as prefix for indirect rates</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Customer Group">
     <Documentation>
      <Summary>Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AdditionalCustomerGroup1" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 1">
     <Documentation>
      <Summary>Specifies a customer-defined group of customers.</Summary>
      <LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="AdditionalCustomerGroup2" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 2">
     <Documentation>
      <Summary>Specifies a customer-defined group of customers.</Summary>
      <LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="AdditionalCustomerGroup3" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 3">
     <Documentation>
      <Summary>Specifies a customer-defined group of customers.</Summary>
      <LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="AdditionalCustomerGroup4" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 4">
     <Documentation>
      <Summary>Specifies a customer-defined group of customers.</Summary>
      <LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="AdditionalCustomerGroup5" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 5">
     <Documentation>
      <Summary>Specifies a customer-defined group of customers.</Summary>
      <LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SlsDocIsRlvtForProofOfDeliv" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Relevant for POD" sap:quickinfo="Relevant for POD processing">
     <Documentation>
      <Summary>This indicator controls proof of delivery (POD) processing.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification1" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Alt.Tax Classific." sap:quickinfo="Alternative Tax Classification">
     <Documentation>
      <Summary>Indicates whether the system takes account of taxes that are related to the customer for pricing (such as value-added tax).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the goods recipient. During pricing, the system uses the tax classification and the country key (which identifies the customer location) to determine the relevant taxes. You can enter a different (alternative) tax classification in the order.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification2" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Class.2 Customer" sap:quickinfo="Tax Classification 2 for Customer">
     <Documentation>
      <Summary>Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification3" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Class.3 Customer" sap:quickinfo="Tax Classification 3 for Customer">
     <Documentation>
      <Summary>Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification4" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Class.4 Customer" sap:quickinfo="Tax Classification 4 for Customer">
     <Documentation>
      <Summary>Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification5" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Class.5 Customer" sap:quickinfo="Tax Classification 5 for Customer">
     <Documentation>
      <Summary>Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification6" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Class.6 Customer" sap:quickinfo="Tax Classification 6 for Customer">
     <Documentation>
      <Summary>Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification7" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Class.7 Customer" sap:quickinfo="Tax Classification 7 for Customer">
     <Documentation>
      <Summary>Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification8" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Class.8 Customer" sap:quickinfo="Tax Classification 8 for Customer">
     <Documentation>
      <Summary>Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerTaxClassification9" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Class.9 Customer" sap:quickinfo="Tax Classification 9 for Customer">
     <Documentation>
      <Summary>Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).</Summary>
      <LongDescription>The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="TaxDepartureCountry" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Tax Depart. Country" sap:quickinfo="Tax Departure Country">
     <Documentation>
      <Summary>For tax determination, the country of departure is used as the plant country.</Summary>
      <LongDescription>A different country needs to be entered for certain internal European transactions (chain transactions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="VATRegistrationCountry" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Tax Dest. Country" sap:quickinfo="Tax Destination Country">
     <Documentation>
      <Summary>For tax determination, the country of the ship-to party is used as the tax country of destination.</Summary>
      <LongDescription>A different country needs to be entered for certain internal European transactions (chain transactions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SalesOrderApprovalReason" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Apprvl Req. Rsn ID" sap:quickinfo="Approval Request Reason ID" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>States in which cases an approval is needed.</Summary>
      <LongDescription>Whenever an approval request reason is set and the corresponding workflow is defined, the sales document is considered relevant for approvals. The approval request reason consists of an ID and a description.You define that for customer ABC, sales quotations always have to be approved. The system automatically sets this reason when a sales quotation for this customer is created. It cannot be released without sending it to an approver first.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SalesDocApprovalStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Approval Status" sap:quickinfo="Document Approval Status" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>States whether a sales document is relevant for approvals and, if so, which approval stage it is in.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="OverallSDProcessStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Overall Status" sap:quickinfo="Overall Processing Status (Header/All Items)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The processing status of the entire sales document.</Summary>
      <LongDescription>The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="TotalCreditCheckStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Credit Status" sap:quickinfo="Overall Status of Credit Checks" sap:creatable="false" sap:updatable="false"/>
    <Property Name="OverallTotalDeliveryStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Ovrl Delivery Status" sap:quickinfo="Overall Delivery Status (All Items)" sap:creatable="false" sap:updatable="false"/>
    <Property Name="OverallSDDocumentRejectionSts" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Rejection Status" sap:quickinfo="Rejection Status (All Items)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Displays the rejection status of the entire sales document.</Summary>
      <LongDescription>The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.</LongDescription>
     </Documentation>
    </Property>
    <NavigationProperty Name="to_Item" Relationship="API_SALES_ORDER_SRV.assoc_42CCE6159E335C5B7697EE6BC8D37107" FromRole="FromRole_assoc_42CCE6159E335C5B7697EE6BC8D37107" ToRole="ToRole_assoc_42CCE6159E335C5B7697EE6BC8D37107"/>
    <NavigationProperty Name="to_Partner" Relationship="API_SALES_ORDER_SRV.assoc_E0F0B75CE5743C11AC56990C6083E0BA" FromRole="FromRole_assoc_E0F0B75CE5743C11AC56990C6083E0BA" ToRole="ToRole_assoc_E0F0B75CE5743C11AC56990C6083E0BA"/>
    <NavigationProperty Name="to_PaymentPlanItemDetails" Relationship="API_SALES_ORDER_SRV.assoc_44F7AAFBAB4403914DD21D2B054AE91D" FromRole="FromRole_assoc_44F7AAFBAB4403914DD21D2B054AE91D" ToRole="ToRole_assoc_44F7AAFBAB4403914DD21D2B054AE91D"/>
    <NavigationProperty Name="to_PricingElement" Relationship="API_SALES_ORDER_SRV.assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21" FromRole="FromRole_assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21" ToRole="ToRole_assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21"/>
    <NavigationProperty Name="to_Text" Relationship="API_SALES_ORDER_SRV.assoc_D06EF7DEC5E9B78C200493F21B05A94E" FromRole="FromRole_assoc_D06EF7DEC5E9B78C200493F21B05A94E" ToRole="ToRole_assoc_D06EF7DEC5E9B78C200493F21B05A94E"/>
   </EntityType>
   <EntityType Name="A_SalesOrderHeaderPartnerType" sap:label="Header Partner" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="PartnerFunction"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PartnerFunction" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Partner Function">
     <Documentation>
      <Summary>The abbreviated form of the name that identifies the partner function.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="Customer" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
     <Documentation>
      <Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="Supplier" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
     <Documentation>
      <Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="Personnel" Type="Edm.String" MaxLength="8" sap:display-format="NonNegative" sap:label="Personnel Number">
     <Documentation>
      <Summary>The personnel number is the only feature within a client which is unique to an employee. You have to enter a personnel number before you can display and maintain an employee's master data and time data.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ContactPerson" Type="Edm.String" MaxLength="10" sap:display-format="NonNegative" sap:label="Contact Person" sap:quickinfo="Number of contact person">
     <Documentation>
      <Summary>The number that uniquely identifies the contact person.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <NavigationProperty Name="to_SalesOrder" Relationship="API_SALES_ORDER_SRV.assoc_8F721694C94560109555442071763439" FromRole="FromRole_assoc_8F721694C94560109555442071763439" ToRole="ToRole_assoc_8F721694C94560109555442071763439"/>
   </EntityType>
   <EntityType Name="A_SalesOrderHeaderPrElementType" sap:label="Header Pricing Element" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="PricingProcedureStep"/>
     <PropertyRef Name="PricingProcedureCounter"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PricingProcedureStep" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Step Number">
     <Documentation>
      <Summary>Number that determines the sequence of the condition within a procedure.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="PricingProcedureCounter" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Counter" sap:quickinfo="Condition Counter">
     <Documentation>
      <Summary>Access number of the conditions within a step in the pricing procedure.</Summary>
      <LongDescription>During automatic pricing, the system takes into account the sequence specified by the counter.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionType" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Condition Type">
     <Documentation>
      <Summary>The key that uniquely identifies the condition.</Summary>
      <LongDescription>The condition type indicates, for example, whether, during pricing, the system applies a price, a discount, a surcharge, or other pricing elements, such as freight costs and sales taxes. For each of these pricing elements, there is a condition type defined in the system.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PricingDateTime" Type="Edm.String" MaxLength="14" sap:display-format="UpperCase" sap:label="Valid From" sap:quickinfo="Timestamp for Pricing" sap:creatable="false" sap:updatable="false"/>
    <Property Name="ConditionCalculationType" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Calculation Type" sap:quickinfo="Calculation Type for Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.</Summary>
      <LongDescription>The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionBaseValue" Type="Edm.Decimal" Precision="24" Scale="9" sap:label="Condition Basis" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Defines the value in a business document that the system uses together with the condition amount to calculate the condition value for the price condition.</Summary>
      <LongDescription>During the pricing process in a business document, for each condition type used in the pricing procedure, the system calculates the condition value as follows:For several calculation types (for example, A, C, D, E, F, H, I, J, K, M, N, O, P, W), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, A, C, D, E, F, H, I, M, N, O, P), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, C, D, E, F, H, I, M, N, O, P), the value of the condition basis refers to a unit of measure. If the unit of measure of the conditions basis differs from the unit of measure of the price condition (condition unit), the system automatically converts it into the unit of measure of the condition unit. For calculation types C, M, N, O, and P, the item quantity is the default value for the condition basis.For several calculation types (for example, A, B, H, I, J, K, W), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.For several calculation types (for example, A, B, H, I), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.Note: The standard number of decimal places for a currency is two.Currencies that use a different number of decimal places must in addition be entered into table TCURX, where you can explicitly define the number of decimal places, for example, zero decimals for Japanese yen JPY.Deviations are preconfigured depending on the currency, for example, zero decimals for Japanese yen JPY.If you have defined scales, the system uses the condition basis to determine the valid scale line with the corresponding condition amount.In usage-based pricing models, the usage corresponds to the condition basis.The condition basis can be aQuantityWeightVolumeCurrency AmountA sales order includes an item with a quantity of 120 pieces:The determined list price of USD 101 (condition amount) multiplied with the quantity of 120 pieces (condition basis) results in a condition value of USD 12120.Two discounts are applied to the item of this sales order:The first discount (-1 USD / PC) is based on the quantity ordered that is the condition basis equals the item quantity and the result is - 120 USD.The second discount (- 2 %) is calculated as a percentage which is applied to the results of the list price (USD 12120) and the first discount (- 120 USD). Its result (12000 USD) is the condition basis for the second discount. The result of the second discount is - 240 USD.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionRateValue" Type="Edm.Decimal" Precision="24" Scale="9" sap:label="Amount" sap:quickinfo="Condition Amount or Percentage">
     <Documentation>
      <Summary>Determines how the system calculates prices using a specific condition.</Summary>
      <LongDescription>Depending on the condition type, it can be a fixed amount, a percentage, or per mille. If the condition includes a pricing scale, the condition amount or percentage displays the first line of the scale.The following examples illustrate how you can use the condition amount or percentage in different condition types:If you create a condition that includes prices (for example, prices for a material), you enter an amount.If you create a condition based on percentage, such as discounts or surcharges (for example, a customer-specific discount), you enter the value of a percentage. If the condition is a discount, the system automatically enters a minus sign behind the amount and a percent sign in the Condition Unit field.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionCurrency" Type="Edm.String" MaxLength="5" sap:label="Currency" sap:quickinfo="Currency Key" sap:semantics="currency-code">
     <Documentation>
      <Summary>Currency key for amounts in the system.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionQuantity" Type="Edm.Decimal" Precision="5" Scale="0" sap:unit="ConditionQuantityUnit" sap:label="Pricing Unit" sap:quickinfo="Condition Pricing Unit">
     <Documentation>
      <Summary>The quantity on which the amount or percentage is based. The quantity is expressed in sales units (for example, bottles).</Summary>
      <LongDescription>You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionQuantityUnit" Type="Edm.String" MaxLength="3" sap:label="Condition Unit" sap:quickinfo="Condition Unit in the Document" sap:semantics="unit-of-measure">
     <Documentation>
      <Summary>Quantity unit, to which the condition amount or percentage refers.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionQuantitySAPUnit" Type="Edm.String" MaxLength="3" sap:label="SAP Condition Qty" sap:quickinfo="SAP Unit Code for Condition Quantity">
     <Documentation>
      <Summary>Unit of measure (SAP unit code) for the condition quantity.</Summary>
      <LongDescription>For the condition quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionQuantityISOUnit" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="ISO Condition Qty" sap:quickinfo="ISO Unit Code for Condition Quantity">
     <Documentation>
      <Summary>Unit of measure (ISO code) for the condition quantity.</Summary>
      <LongDescription>For the condition quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionCategory" Type="Edm.String" MaxLength="1" sap:label="Condition Category" sap:quickinfo="Condition Category (Examples: Tax, Freight, Price, Cost)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionIsForStatistics" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Statistical" sap:quickinfo="Condition is used for statistics" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="PricingScaleType" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Scale Type" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicator that controls the validity of the scale value or percentage:</Summary>
      <LongDescription>From a certain quantity or value (base scale)Up to a certain quantity or value (to-scale)Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionOrigin" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Condition Origin" sap:quickinfo="Origin of the Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates where the condition originated (for example, whether you entered the condition manually or whether the system determined it automatically).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="IsGroupCondition" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Group Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates whether the system calculates the scale base value or the condition value taking all related items of the business document into account.</Summary>
      <LongDescription>For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.A sales order contains two items. Both items belong to the material group 01.Material Quantity Material groupA 150 01B 100 01The group condition indicator is set in the definition of the condition type for material group discounts. The condition record for material group 01 includes the following pricing scale:Scale quantity Discountfrom 1 pc -1%from 200 pc -2%Neither item alone qualifies for the 2% discount. However, when the items are combined as part of a group condition, the combined quantity creates a basis of 250 pieces. This basis then exceeds the scale value of 200 pieces, which is necessary to qualify for the higher discount.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionRecord" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Condition Record No." sap:quickinfo="Number of the Condition Record" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Number that uniquely identifies a condition record.</Summary>
      <LongDescription>The system uses the condition record number to store and retrieve information during processing (pricing, for example).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionSequentialNumber" Type="Edm.String" MaxLength="3" sap:display-format="NonNegative" sap:label="Sequent.No. of Cond." sap:quickinfo="Sequential Number of the Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The sequential number that uniquely identifies the condition if a condition supplement exists.</Summary>
      <LongDescription>If you have assigned a condition supplement to the condition, the system automatically assigns the number.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="TaxCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Tax Code" sap:quickinfo="Tax on Sales/Purchases Code" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.</Summary>
      <LongDescription>Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="WithholdingTaxCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="W/Tax Code" sap:quickinfo="Withholding Tax Code" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>One or more "withholding tax codes" are assigned to each withholding tax type. One of the things these codes determine is the various percentage rates for the withholding tax type.</Summary>
      <LongDescription>Note that when processing a business transaction, no more than one withholding tax code can be assigned per withholding tax type. If the business transaction is subject to more than one withholding taxes, these must be represented in the system by defining various withholding tax types.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CndnRoundingOffDiffAmount" Type="Edm.Decimal" Precision="6" Scale="3" sap:unit="TransactionCurrency" sap:label="Cond.Rounding Diff." sap:quickinfo="Rounding-Off Difference of the Condition" sap:creatable="false" sap:updatable="false"/>
    <Property Name="ConditionAmount" Type="Edm.Decimal" Precision="16" Scale="3" sap:unit="TransactionCurrency" sap:label="Value" sap:quickinfo="Condition Value" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The value, resulting from pricing, for a particular condition, total, or subtotal in a document.</Summary>
      <LongDescription>This value is used as a total for the condition in the pricing procedure.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="TransactionCurrency" Type="Edm.String" MaxLength="5" sap:label="Document Currency" sap:quickinfo="SD Document Currency" sap:semantics="currency-code">
     <Documentation>
      <Summary>The currency that applies to the document (for example, to a sales order or an invoice).</Summary>
      <LongDescription>The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionControl" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Condition Control" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates whether the prices or values in a condition are fixed or whether and in what way they changed.</Summary>
      <LongDescription>The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionInactiveReason" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Inactive Condition" sap:quickinfo="Condition is Inactive" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates if the condition is active.</Summary>
      <LongDescription>A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionClass" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Condition Class" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Preliminary structuring of condition types, for example, in surcharges and discounts or prices.</Summary>
      <LongDescription>Allows standardized processing of individual condition classes within the system.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PrcgProcedureCounterForHeader" Type="Edm.String" MaxLength="3" sap:display-format="NonNegative" sap:label="Counter" sap:quickinfo="Condition Counter (Header)" sap:creatable="false" sap:updatable="false"/>
    <Property Name="FactorForConditionBasisValue" Type="Edm.Double" sap:label="Condition Factor" sap:quickinfo="Factor for Condition Base Value" sap:creatable="false" sap:updatable="false"/>
    <Property Name="StructureCondition" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Structure Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Controls whether the condition type is a duplicated condition or a cumulated condition.</Summary>
      <LongDescription>This control is only helpful when you use bill of materials or configurable materials:'  ' - None'A' - Duplication Condition: A duplicated condition is duplicated into all assigned items.'B' - Cumulation Condition: A cumulated condition contains the net value of all assigned items.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PeriodFactorForCndnBasisValue" Type="Edm.Double" sap:label="Condition Factor" sap:quickinfo="Factor for Condition Basis (Period)" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PricingScaleBasis" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Scale Basis" sap:quickinfo="Scale Basis Indicator" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionScaleBasisValue" Type="Edm.Decimal" Precision="24" Scale="9" sap:label="Scale Base Val." sap:quickinfo="Scale Base Value" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>A value or quantity that the system uses to access a pricing scale to determine a scale level.</Summary>
      <LongDescription>The scale base value can be a condition value or the value of a quantity, weight, and so on that has been entered in the document.You create a price condition based on a simple quantity scale with scale type A: Base scale:Quantity Price per Unit10 12 USD100 11 USD1000 10 USDA sales order item with 150 units qualifies for the condition scale quantity of 100 units and the price per unit of USD 11. In this case, the scale base value that determines the price is 150.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionScaleBasisUnit" Type="Edm.String" MaxLength="3" sap:label="Scale Unit of Meas." sap:quickinfo="Condition Scale Unit of Measure" sap:creatable="false" sap:updatable="false" sap:semantics="unit-of-measure">
     <Documentation>
      <Summary>Unit of measure to which the quantity scale refers.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionScaleBasisCurrency" Type="Edm.String" MaxLength="5" sap:label="Scale Currency" sap:creatable="false" sap:updatable="false" sap:semantics="currency-code">
     <Documentation>
      <Summary>Specifies a currency for a pricing scale in a condition record.</Summary>
      <LongDescription>If a pricing scale is based on a value instead of a quantity, you can specify a currency for the value. In the standard version of the SAP System, this field is only relevant in condition records for the following discounts:Price groupPrice group/Material pricing groupYou apply a price group discount to customers in a particular foreign country. When you create a condition record for this discount and enter values in the pricing scale, you can also enter the corresponding foreign currency. During pricing, the system then calculates discounts based on scale values in the foreign currency. The discount amount is then converted into the currency you are using in the sales document.After you enter a currency in this field and save the condition record, you cannot change the currency without deleting the record and creating it again.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CndnIsRelevantForIntcoBilling" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Intercomp.Billing" sap:quickinfo="Condition for Intercompany Billing" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicator that defines a condition as relevant for the intercompany process.</Summary>
      <LongDescription>Intercompany conditions are usually statistical in the sales order and the customer invoice and not statistical in the intercompany invoice.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionIsManuallyChanged" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Changed Manually" sap:quickinfo="Condition Changed Manually" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>If this flag is set, the condition has been manually or automatically changed or created (by entry in the condition screen).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionIsForConfiguration" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="UsedforVariantConfig" sap:quickinfo="Condition Used for Variant Configuration" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>A condition that is relevant for variant configuration.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="VariantCondition" Type="Edm.String" MaxLength="26" sap:label="Variant Key" sap:quickinfo="Variant Condition Key" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Freely definable attribute that determines the valid price components of a configurable material.</Summary>
      <LongDescription>To model the price for a variant of a configurable material, you typically use a larger number of variant condition keys.In a business document, the price for a selected variant is realized as surcharges and discounts specific for this variant: The sales price of a bike depends on the material that is used to produce the frame. You define a characteristic FRAME_MATERIAL that can have the values steel, aluminum, and carbon with the following surcharges:Steel: 0.0 USD per pieceAluminum: + 300 USD per pieceCarbon: + 1000 USD per pieceYou define three different variant condition keys FRAME_STEEL, FRAME_ALU, and FRAME_CARBON and maintain the above-mentioned surcharges as condition records. During order creation, you select the variant of the bike with the carbon frame. This will lead to a surcharge of 1000 USD that corresponds to the variant condition key FRAME_CARBON.</LongDescription>
     </Documentation>
    </Property>
    <NavigationProperty Name="to_SalesOrder" Relationship="API_SALES_ORDER_SRV.assoc_C516ABBC5925268953A9AC7D6F836887" FromRole="FromRole_assoc_C516ABBC5925268953A9AC7D6F836887" ToRole="ToRole_assoc_C516ABBC5925268953A9AC7D6F836887"/>
   </EntityType>
   <EntityType Name="A_SalesOrderItemType" sap:label="Sales Order Item" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="SalesOrderItem"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order" sap:creatable="false" sap:updatable="false"/>
    <Property Name="SalesOrderItem" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="NonNegative" sap:text="SalesOrderItemText" sap:label="Item" sap:quickinfo="Sales Order Item"/>
    <Property Name="HigherLevelItem" Type="Edm.String" MaxLength="6" sap:display-format="NonNegative" sap:label="Higher-Level Item" sap:quickinfo="Higher-Level Item in Bill of Material Structures">
     <Documentation>
      <Summary>The number of the higher-level item to which this item belongs in a hierarchy.</Summary>
      <LongDescription>Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item.Enter the number of a higher-level item.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SalesOrderItemCategory" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Item Category" sap:quickinfo="Sales Document Item Category">
     <Documentation>
      <Summary>A classification that distinguishes between different types of item (for example, free of charge items and text items) and determines how the system processes the item.</Summary>
      <LongDescription>The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document.If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SalesOrderItemText" Type="Edm.String" MaxLength="40" sap:label="Item Description" sap:quickinfo="Short Text for Sales Order Item">
     <Documentation>
      <Summary>A short description of the item.</Summary>
      <LongDescription>Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations.The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PurchaseOrderByCustomer" Type="Edm.String" MaxLength="35" sap:label="Customer Reference">
     <Documentation>
      <Summary>Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).</Summary>
      <LongDescription>The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PurchaseOrderByShipToParty" Type="Edm.String" MaxLength="35" sap:label="Purchase Order No." sap:quickinfo="Ship-to Party's Purchase Order Number">
     <Documentation>
      <Summary>Number used by the end customer for unique identification of the purchasing document (e.g. inquiry or purchase).</Summary>
      <LongDescription>The number is the link between the end customer's purchase order and the sales documents that you have created. You can use the end customer's number for correspondence with the customer, in particular for finding certain document information. If the number refers to a purchase order, you can also print documents that you wish to send to the end customer, such as the delivery note.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ExternalItemID" Type="Edm.String" MaxLength="40" sap:display-format="UpperCase" sap:label="External Item ID" sap:creatable="false" sap:updatable="false"/>
    <Property Name="Material" Type="Edm.String" MaxLength="40" sap:display-format="UpperCase" sap:label="Material" sap:quickinfo="Material Number">
     <Documentation>
      <Summary>Alphanumeric key uniquely identifying the material.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="MaterialByCustomer" Type="Edm.String" MaxLength="35" sap:display-format="UpperCase" sap:label="Customer Material" sap:quickinfo="Material Number Used by Customer">
     <Documentation>
      <Summary>Uniquely identifies the material from the customer's point of view.</Summary>
      <LongDescription>If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such asMinimum delivery quantityPartial delivery conditionsEnter a value from an existing customer-material info record.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PricingDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Pricing Date" sap:quickinfo="Date for Pricing and Exchange Rate">
     <Documentation>
      <Summary>The date that determines date-related pricing elements, such as conditions and foreign exchange rate.</Summary>
      <LongDescription>You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PricingReferenceMaterial" Type="Edm.String" MaxLength="40" sap:display-format="UpperCase" sap:label="Pricing Ref. Matl" sap:quickinfo="Pricing Reference Material">
     <Documentation>
      <Summary>Material master record that the system uses as a reference for pricing purposes.</Summary>
      <LongDescription>The conditions that apply to the pricing reference material also apply to the material in whose material master record the pricing reference material is stored.A pricing reference material must always have its own material master record.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="RequestedQuantity" Type="Edm.Decimal" Precision="15" Scale="3" sap:unit="RequestedQuantityUnit" sap:label="Requested Quantity"/>
    <Property Name="RequestedQuantityUnit" Type="Edm.String" MaxLength="3" sap:label="Requested Qty Unit" sap:quickinfo="Requested Quantity Unit" sap:semantics="unit-of-measure"/>
    <Property Name="RequestedQuantitySAPUnit" Type="Edm.String" MaxLength="3" sap:label="SAP Code Req. Qty" sap:quickinfo="SAP Unit Code for Requested Quantity">
     <Documentation>
      <Summary>Unit of measure (SAP code) for the requested quantity.</Summary>
      <LongDescription>For the requested quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="RequestedQuantityISOUnit" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="ISO Code Req. Qty" sap:quickinfo="ISO Unit Code for Requested Quantity">
     <Documentation>
      <Summary>Unit of measure (ISO code) for the requested quantity.</Summary>
      <LongDescription>For the requested quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemGrossWeight" Type="Edm.Decimal" Precision="15" Scale="3" sap:unit="ItemWeightUnit" sap:label="Gross Weight" sap:quickinfo="Gross Weight of the Item" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The total gross weight of the item. The gross weight represents the net weight plus the weight of packaging.</Summary>
      <LongDescription>The system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record.If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the gross weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the gross weight using the target quantity.You can change the value manually at the item level.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemNetWeight" Type="Edm.Decimal" Precision="15" Scale="3" sap:unit="ItemWeightUnit" sap:label="Net Weight" sap:quickinfo="Net Weight of the Item" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The total net weight for the item. The net weight represents the gross weight less the weight of packaging.</Summary>
      <LongDescription>The system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the net weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the net weight using the target quantity.You can change the value manually at the item level.The gross weight of a refrigerator and its packaging (a cardboard box including protective padding) is 350 pounds. The packaging weighs 25 pounds. In this case, the net weight is 325 pounds.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemWeightUnit" Type="Edm.String" MaxLength="3" sap:label="Unit of Weight" sap:creatable="false" sap:updatable="false" sap:semantics="unit-of-measure">
     <Documentation>
      <Summary>Unit referring to the gross weight or net weight of the material.</Summary>
      <LongDescription>If you specify a weight, you must enter the corresponding unit of weight here.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemWeightSAPUnit" Type="Edm.String" MaxLength="3" sap:label="SAP Code Item Weight" sap:quickinfo="SAP Unit Code for Item Weight">
     <Documentation>
      <Summary>Unit of measure (SAP code) for the item weight.</Summary>
      <LongDescription>For the item weight, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemWeightISOUnit" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="ISO Code Item Weight" sap:quickinfo="ISO Unit Code for Item Weight">
     <Documentation>
      <Summary>Unit of measure (ISO code) for the item weight.</Summary>
      <LongDescription>For the item weight, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemVolume" Type="Edm.Decimal" Precision="15" Scale="3" sap:unit="ItemVolumeUnit" sap:label="Volume" sap:quickinfo="Volume of the item" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The total volume for the item.</Summary>
      <LongDescription>The system calculates the volume based on the order quantity for the item and the volume proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the volume. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the volume using the target quantity.You can change the value manually at the item level.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemVolumeUnit" Type="Edm.String" MaxLength="3" sap:label="Volume Unit" sap:creatable="false" sap:updatable="false" sap:semantics="unit-of-measure">
     <Documentation>
      <Summary>Unit referring to the volume of the material.</Summary>
      <LongDescription>If you specify a volume, you have to enter the corresponding volume unit here.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemVolumeSAPUnit" Type="Edm.String" MaxLength="3" sap:label="SAP Code f Item Vol." sap:quickinfo="SAP Unit Code for Item Volume">
     <Documentation>
      <Summary>Unit of measure (SAP code) for the item volume.</Summary>
      <LongDescription>For the item volume, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemVolumeISOUnit" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="ISO Unit Item Volume" sap:quickinfo="ISO Unit Code for Item Volume">
     <Documentation>
      <Summary>Unit of measure (ISO code) for the item volume.</Summary>
      <LongDescription>For the item volume, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="TransactionCurrency" Type="Edm.String" MaxLength="5" sap:label="Document Currency" sap:quickinfo="SD Document Currency" sap:creatable="false" sap:updatable="false" sap:semantics="currency-code">
     <Documentation>
      <Summary>The currency that applies to the document (for example, to a sales order or an invoice).</Summary>
      <LongDescription>The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="NetAmount" Type="Edm.Decimal" Precision="16" Scale="3" sap:unit="TransactionCurrency" sap:label="Net Value" sap:quickinfo="Net Value of the Order Item in Document Currency" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The net value of the item, after any discounts and surcharges are taken into account. Sales taxes are not included. The value is expressed in the document currency.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="MaterialGroup" Type="Edm.String" MaxLength="9" sap:display-format="UpperCase" sap:label="Material Group">
     <Documentation>
      <Summary>Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.</Summary>
      <LongDescription>You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps</LongDescription>
     </Documentation>
    </Property>
    <Property Name="MaterialPricingGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Material Price Grp" sap:quickinfo="Material Price Group">
     <Documentation>
      <Summary>A way of grouping materials to which you want to apply the same  condition.</Summary>
      <LongDescription>You can create condition records for a material price group using the following condition types:Material price group (for example, all non-food products)A combination of customer and material price groupA combination of customer price group and material price group (for example, all wholesale customers and all non-food products)</LongDescription>
     </Documentation>
    </Property>
    <Property Name="Batch" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Batch" sap:quickinfo="Batch Number">
     <Documentation>
      <Summary>Assigns a material that is manufactured in batches or production lots to a specific batch.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ProductionPlant" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Plant" sap:quickinfo="Plant (Own or External)">
     <Documentation>
      <Summary>Key that uniquely identifies a plant.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="StorageLocation" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Storage Location">
     <Documentation>
      <Summary>Number of the storage location in which the material is stored. A plant may contain one or more storage locations.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="DeliveryGroup" Type="Edm.String" MaxLength="3" sap:display-format="NonNegative" sap:label="Delivery Group" sap:quickinfo="Delivery Group (Items are delivered together)">
     <Documentation>
      <Summary>A combination of items that should be delivered together.</Summary>
      <LongDescription>The system uses delivery groups to check the availability of items that should be delivered together. The delivery date of the latest schedule line in the delivery group is taken as the general date for the whole group.During sales order processing, you can enter a number (up to three digits) that identifies a delivery group. The number is freely definable.If necessary, the system adjusts requirements that have already been created and changes the material availability dates for individual items to the delivery date that it has determined for the group.If a typewriter is usually delivered with a case, you can define the two items as a delivery group.If an item has more than one schedule line with a confirmed quantity, then the system deletes all undelivered schedule lines up to the last one. The system automatically carries over the quantities from the deleted schedule lines into the last one. If necessary, the system changes the delivery date of the last schedule line to that of the delivery group.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ShippingPoint" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Shipping Point" sap:quickinfo="Shipping Point / Receiving Point">
     <Documentation>
      <Summary>The physical location (for example, a warehouse or collection of loading ramps) from which you ship the item.</Summary>
      <LongDescription>You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ShippingType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Shipping Type">
     <Documentation>
      <Summary>Shipping type (for example, by road or rail) that has been selected for the transportation of the goods for the shipment legs.</Summary>
      <LongDescription>During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination</LongDescription>
     </Documentation>
    </Property>
    <Property Name="DeliveryPriority" Type="Edm.String" MaxLength="2" sap:display-format="NonNegative" sap:label="Delivery Priority">
     <Documentation>
      <Summary>The delivery priority assigned to an item.</Summary>
      <LongDescription>You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="DeliveryDateTypeRule" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Deliv Date Rule" sap:quickinfo="Delivery Date Rule">
     <Documentation>
      <Summary>Indicates when the ordered goods should be delivered.</Summary>
      <LongDescription>You can choose one of the following options:The goods should be delivered on the requested delivery date or later. Note that there is no guarantee that the goods will not be delivered earlier.The goods must be delivered exactly on the confirmed delivery date.The goods must be delivered by the confirmed delivery date (that is, on the date or earlier).You can set the delivery date rule on header level to set a default for any items that you create afterwards.In Transportation Management (TM), this field has the following implications:If you want the goods to be delivered on the requested delivery date or later, the delivery date/time is used as the earliest requested delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered on the confirmed delivery date, the start of the delivery date is used as the earliest acceptable delivery date/time and the end of the delivery date as the latest acceptable delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered by the confirmed delivery date, the end of the delivery date is used as the latest acceptable delivery date/time of the freight unit which contains the sales order item.Note: If you want to the goods to be delivered on or by the confirmed delivery date, the system ignores the rule for pick-up and delivery window and the condition for pick-up and delivery window determination which you have defined in the freight unit type for the delivery stop.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsClassification" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Incoterms" sap:quickinfo="Incoterms (Part 1)">
     <Documentation>
      <Summary>Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).</Summary>
      <LongDescription>Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsTransferLocation" Type="Edm.String" MaxLength="28" sap:label="Incoterms (Part 2)">
     <Documentation>
      <Summary>Additional information for the primary Incoterm.</Summary>
      <LongDescription>If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsLocation1" Type="Edm.String" MaxLength="70" sap:label="Incoterms Location 1">
     <Documentation>
      <Summary>Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:</Summary>
      <LongDescription>1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description  Location 1 EXW Ex Works  Place of DeliveryFCA Free Carrier  Place of DeliveryCPT Carriage Paid To  Place of DestinationCIP Carriage &amp; Insurance Paid To  Place of DestinationDAF Delivered at Frontier  Place of DeliveryDDP Delivered Duty Paid  Place of DestinationDDU Delivered Duty Unpaid  Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost &amp; Freight Port of DestinationCIF Cost Insurance &amp; Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IncotermsLocation2" Type="Edm.String" MaxLength="70" sap:label="Incoterms Location 2">
     <Documentation>
      <Summary>Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:</Summary>
      <LongDescription>No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -&gt; Business Partners -&gt; Customers -&gt; Billing Document -&gt; Incoterms -&gt; Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage &amp; Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost &amp; Freight Port of DestinationCIF Cost Insurance &amp; Freight Port of Destination</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ProductTaxClassification1" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="ProductTaxClassification2" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="ProductTaxClassification3" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="ProductTaxClassification4" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="ProductTaxClassification5" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="ProductTaxClassification6" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="ProductTaxClassification7" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="ProductTaxClassification8" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="ProductTaxClassification9" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classifc. Mat." sap:quickinfo="Tax Classification for Material"/>
    <Property Name="MatlAccountAssignmentGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Acct Assmt Grp Mat." sap:quickinfo="Account Assignment Group for Material">
     <Documentation>
      <Summary>Group of materials with the same accounting requirements.</Summary>
      <LongDescription>Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerPaymentTerms" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Terms of Payment" sap:quickinfo="Terms of Payment Key">
     <Documentation>
      <Summary>Key for defining payment terms composed of cash discount percentages and payment periods.</Summary>
      <LongDescription>It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="FixedValueDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Fixed Value Date">
     <Documentation>
      <Summary>The date on which the terms of payment related to the sales document become effective.</Summary>
      <LongDescription>If you enter a date in this field, you cannot enter a value in the additional value days field.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CustomerGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Customer Group">
     <Documentation>
      <Summary>Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="SalesDocumentRjcnReason" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Reason for Rejection" sap:quickinfo="Reason for Rejection of Sales Documents">
     <Documentation>
      <Summary>The reason for rejecting a sales document (for example, a sales quotation or a sales order).</Summary>
      <LongDescription>The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection:Inquiries and quotations: no further references by other documentsSales orders: no further delivery of itemsContracts: no further creation of release ordersCredit and debit memo requests: no further processing of credit or debit memosEnter one of the values predefined for your system.If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ItemBillingBlockReason" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Billing Block" sap:quickinfo="Billing Block for Item">
     <Documentation>
      <Summary>Indicates if the item is blocked for billing.</Summary>
      <LongDescription>To block an item for billing, enter one of the values predefined for your system.You can block an item for billing so that, for example, terms of payment or prices can be checked before further processing takes place.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="SlsDocIsRlvtForProofOfDeliv" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Relevant for POD" sap:quickinfo="Relevant for POD processing">
     <Documentation>
      <Summary>This indicator controls proof of delivery (POD) processing.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="WBSElement" Type="Edm.String" MaxLength="24" sap:display-format="NonNegative" sap:label="WBS Element" sap:quickinfo="Work Breakdown Structure Element (WBS Element)">
     <Documentation>
      <Summary>Key that identifies a WBS element.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ProfitCenter" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Profit Center">
     <Documentation>
      <Summary>Key which together with the controlling area uniquely identifies a profit center.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AccountingExchangeRate" Type="Edm.Decimal" Precision="9" Scale="5" sap:label="Exchng. Rate Accntg." sap:quickinfo="Exchange rate for FI postings">
     <Documentation>
      <Summary>The exchange rate that the system applies when you create an invoice.</Summary>
      <LongDescription>Your system is configured in such a way that it expects:No prefix (leading sign) for direct ratesA "" as prefix (leading sign) for direct ratesNo prefix for indirect ratesA "" as prefix for indirect rates</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ReferenceSDDocument" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Reference Document" sap:quickinfo="Document Number of the Reference Document">
     <Documentation>
      <Summary>Identifies the sales order to which the delivery refers.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ReferenceSDDocumentItem" Type="Edm.String" MaxLength="6" sap:display-format="NonNegative" sap:label="Reference Item" sap:quickinfo="Item Number of the Reference Item">
     <Documentation>
      <Summary>The number of the sales order item to which the delivery item refers.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="SDProcessStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Overall Status" sap:quickinfo="Overall Processing Status (Item)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Displays the overall processing status of the item.</Summary>
      <LongDescription>The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="DeliveryStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Delivery Status" sap:quickinfo="Delivery Status (Item)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Displays the delivery status of the item.</Summary>
      <LongDescription>The status line tells you if the item is not yet delivered, is partly delivered, is completely delivered, or is not relevant for delivery.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="OrderRelatedBillingStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Ord. Rel. Billg Sts" sap:quickinfo="Order-Related Billing Status (Item)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The order-related billing status shows to what extent an item has been processed for billing.</Summary>
      <LongDescription>You determine whether an item is billed as an order-related or delivery-related item when you define item category defaults through the Customizing menus.Credit and debit memo items, for example, are billed as order-related items.</LongDescription>
     </Documentation>
    </Property>
    <NavigationProperty Name="to_Partner" Relationship="API_SALES_ORDER_SRV.assoc_5EBE73B545500EE6B48597931F7D5C56" FromRole="FromRole_assoc_5EBE73B545500EE6B48597931F7D5C56" ToRole="ToRole_assoc_5EBE73B545500EE6B48597931F7D5C56"/>
    <NavigationProperty Name="to_PricingElement" Relationship="API_SALES_ORDER_SRV.assoc_A18E7EFDF1ADD05474B187D10B62BDBF" FromRole="FromRole_assoc_A18E7EFDF1ADD05474B187D10B62BDBF" ToRole="ToRole_assoc_A18E7EFDF1ADD05474B187D10B62BDBF"/>
    <NavigationProperty Name="to_SalesOrder" Relationship="API_SALES_ORDER_SRV.assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD" FromRole="FromRole_assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD" ToRole="ToRole_assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD"/>
    <NavigationProperty Name="to_ScheduleLine" Relationship="API_SALES_ORDER_SRV.assoc_31BB747044FCC7AA5DA94B21FD458954" FromRole="FromRole_assoc_31BB747044FCC7AA5DA94B21FD458954" ToRole="ToRole_assoc_31BB747044FCC7AA5DA94B21FD458954"/>
    <NavigationProperty Name="to_Text" Relationship="API_SALES_ORDER_SRV.assoc_3604F4165550FA74B882A4F3345D936F" FromRole="FromRole_assoc_3604F4165550FA74B882A4F3345D936F" ToRole="ToRole_assoc_3604F4165550FA74B882A4F3345D936F"/>
   </EntityType>
   <EntityType Name="A_SalesOrderItemPartnerType" sap:label="Item Partner" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="SalesOrderItem"/>
     <PropertyRef Name="PartnerFunction"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order" sap:creatable="false" sap:updatable="false"/>
    <Property Name="SalesOrderItem" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="NonNegative" sap:label="Item" sap:quickinfo="Sales Order Item" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PartnerFunction" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Partner Function">
     <Documentation>
      <Summary>The abbreviated form of the name that identifies the partner function.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="Customer" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
     <Documentation>
      <Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="Supplier" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
     <Documentation>
      <Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="Personnel" Type="Edm.String" MaxLength="8" sap:display-format="NonNegative" sap:label="Personnel Number">
     <Documentation>
      <Summary>The personnel number is the only feature within a client which is unique to an employee. You have to enter a personnel number before you can display and maintain an employee's master data and time data.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ContactPerson" Type="Edm.String" MaxLength="10" sap:display-format="NonNegative" sap:label="Contact Person" sap:quickinfo="Number of contact person">
     <Documentation>
      <Summary>The number that uniquely identifies the contact person.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <NavigationProperty Name="to_SalesOrder" Relationship="API_SALES_ORDER_SRV.assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00" FromRole="FromRole_assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00" ToRole="ToRole_assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00"/>
    <NavigationProperty Name="to_SalesOrderItem" Relationship="API_SALES_ORDER_SRV.assoc_2E7827BA025D2DC7290DEA3E71FF39FB" FromRole="FromRole_assoc_2E7827BA025D2DC7290DEA3E71FF39FB" ToRole="ToRole_assoc_2E7827BA025D2DC7290DEA3E71FF39FB"/>
   </EntityType>
   <EntityType Name="A_SalesOrderItemPrElementType" sap:label="Item Pricing Element" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="SalesOrderItem"/>
     <PropertyRef Name="PricingProcedureStep"/>
     <PropertyRef Name="PricingProcedureCounter"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order" sap:creatable="false" sap:updatable="false"/>
    <Property Name="SalesOrderItem" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="NonNegative" sap:label="Item" sap:quickinfo="Sales Order Item" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PricingProcedureStep" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Step Number">
     <Documentation>
      <Summary>Number that determines the sequence of the condition within a procedure.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="PricingProcedureCounter" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Counter" sap:quickinfo="Condition Counter">
     <Documentation>
      <Summary>Access number of the conditions within a step in the pricing procedure.</Summary>
      <LongDescription>During automatic pricing, the system takes into account the sequence specified by the counter.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionType" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Condition Type">
     <Documentation>
      <Summary>The key that uniquely identifies the condition.</Summary>
      <LongDescription>The condition type indicates, for example, whether, during pricing, the system applies a price, a discount, a surcharge, or other pricing elements, such as freight costs and sales taxes. For each of these pricing elements, there is a condition type defined in the system.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PricingDateTime" Type="Edm.String" MaxLength="14" sap:display-format="UpperCase" sap:label="Valid From" sap:quickinfo="Timestamp for Pricing" sap:creatable="false" sap:updatable="false"/>
    <Property Name="ConditionCalculationType" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Calculation Type" sap:quickinfo="Calculation Type for Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.</Summary>
      <LongDescription>The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionBaseValue" Type="Edm.Decimal" Precision="24" Scale="9" sap:label="Condition Basis" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Defines the value in a business document that the system uses together with the condition amount to calculate the condition value for the price condition.</Summary>
      <LongDescription>During the pricing process in a business document, for each condition type used in the pricing procedure, the system calculates the condition value as follows:For several calculation types (for example, A, C, D, E, F, H, I, J, K, M, N, O, P, W), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, A, C, D, E, F, H, I, M, N, O, P), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, C, D, E, F, H, I, M, N, O, P), the value of the condition basis refers to a unit of measure. If the unit of measure of the conditions basis differs from the unit of measure of the price condition (condition unit), the system automatically converts it into the unit of measure of the condition unit. For calculation types C, M, N, O, and P, the item quantity is the default value for the condition basis.For several calculation types (for example, A, B, H, I, J, K, W), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.For several calculation types (for example, A, B, H, I), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.Note: The standard number of decimal places for a currency is two.Currencies that use a different number of decimal places must in addition be entered into table TCURX, where you can explicitly define the number of decimal places, for example, zero decimals for Japanese yen JPY.Deviations are preconfigured depending on the currency, for example, zero decimals for Japanese yen JPY.If you have defined scales, the system uses the condition basis to determine the valid scale line with the corresponding condition amount.In usage-based pricing models, the usage corresponds to the condition basis.The condition basis can be aQuantityWeightVolumeCurrency AmountA sales order includes an item with a quantity of 120 pieces:The determined list price of USD 101 (condition amount) multiplied with the quantity of 120 pieces (condition basis) results in a condition value of USD 12120.Two discounts are applied to the item of this sales order:The first discount (-1 USD / PC) is based on the quantity ordered that is the condition basis equals the item quantity and the result is - 120 USD.The second discount (- 2 %) is calculated as a percentage which is applied to the results of the list price (USD 12120) and the first discount (- 120 USD). Its result (12000 USD) is the condition basis for the second discount. The result of the second discount is - 240 USD.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionRateValue" Type="Edm.Decimal" Precision="24" Scale="9" sap:label="Amount" sap:quickinfo="Condition Amount or Percentage">
     <Documentation>
      <Summary>Determines how the system calculates prices using a specific condition.</Summary>
      <LongDescription>Depending on the condition type, it can be a fixed amount, a percentage, or per mille. If the condition includes a pricing scale, the condition amount or percentage displays the first line of the scale.The following examples illustrate how you can use the condition amount or percentage in different condition types:If you create a condition that includes prices (for example, prices for a material), you enter an amount.If you create a condition based on percentage, such as discounts or surcharges (for example, a customer-specific discount), you enter the value of a percentage. If the condition is a discount, the system automatically enters a minus sign behind the amount and a percent sign in the Condition Unit field.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionCurrency" Type="Edm.String" MaxLength="5" sap:label="Currency" sap:quickinfo="Currency Key" sap:semantics="currency-code">
     <Documentation>
      <Summary>Currency key for amounts in the system.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionQuantity" Type="Edm.Decimal" Precision="5" Scale="0" sap:unit="ConditionQuantityUnit" sap:label="Pricing Unit" sap:quickinfo="Condition Pricing Unit">
     <Documentation>
      <Summary>The quantity on which the amount or percentage is based. The quantity is expressed in sales units (for example, bottles).</Summary>
      <LongDescription>You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionQuantityUnit" Type="Edm.String" MaxLength="3" sap:label="Condition Unit" sap:quickinfo="Condition Unit in the Document" sap:semantics="unit-of-measure">
     <Documentation>
      <Summary>Quantity unit, to which the condition amount or percentage refers.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionQuantitySAPUnit" Type="Edm.String" MaxLength="3" sap:label="SAP Condition Qty" sap:quickinfo="SAP Unit Code for Condition Quantity">
     <Documentation>
      <Summary>Unit of measure (SAP unit code) for the condition quantity.</Summary>
      <LongDescription>For the condition quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionQuantityISOUnit" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="ISO Condition Qty" sap:quickinfo="ISO Unit Code for Condition Quantity">
     <Documentation>
      <Summary>Unit of measure (ISO code) for the condition quantity.</Summary>
      <LongDescription>For the condition quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionCategory" Type="Edm.String" MaxLength="1" sap:label="Condition Category" sap:quickinfo="Condition Category (Examples: Tax, Freight, Price, Cost)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionIsForStatistics" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Statistical" sap:quickinfo="Condition is used for statistics" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="PricingScaleType" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Scale Type" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicator that controls the validity of the scale value or percentage:</Summary>
      <LongDescription>From a certain quantity or value (base scale)Up to a certain quantity or value (to-scale)Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="IsRelevantForAccrual" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Accruals" sap:quickinfo="Condition is Relevant for Accrual  (e.g. Freight)" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.</Summary>
      <LongDescription>If you mark this indicator, the condition appears in the document as a statistical condition.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CndnIsRelevantForInvoiceList" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Invoice List Cond." sap:quickinfo="Condition for Invoice List" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates that the condition type is relevant for internal costing.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionOrigin" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Condition Origin" sap:quickinfo="Origin of the Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates where the condition originated (for example, whether you entered the condition manually or whether the system determined it automatically).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="IsGroupCondition" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Group Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates whether the system calculates the scale base value or the condition value taking all related items of the business document into account.</Summary>
      <LongDescription>For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.A sales order contains two items. Both items belong to the material group 01.Material Quantity Material groupA 150 01B 100 01The group condition indicator is set in the definition of the condition type for material group discounts. The condition record for material group 01 includes the following pricing scale:Scale quantity Discountfrom 1 pc -1%from 200 pc -2%Neither item alone qualifies for the 2% discount. However, when the items are combined as part of a group condition, the combined quantity creates a basis of 250 pieces. This basis then exceeds the scale value of 200 pieces, which is necessary to qualify for the higher discount.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionRecord" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Condition Record No." sap:quickinfo="Number of the Condition Record" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Number that uniquely identifies a condition record.</Summary>
      <LongDescription>The system uses the condition record number to store and retrieve information during processing (pricing, for example).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionSequentialNumber" Type="Edm.String" MaxLength="3" sap:display-format="NonNegative" sap:label="Sequent.No. of Cond." sap:quickinfo="Sequential Number of the Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The sequential number that uniquely identifies the condition if a condition supplement exists.</Summary>
      <LongDescription>If you have assigned a condition supplement to the condition, the system automatically assigns the number.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="TaxCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Tax Code" sap:quickinfo="Tax on Sales/Purchases Code" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.</Summary>
      <LongDescription>Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="WithholdingTaxCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="W/Tax Code" sap:quickinfo="Withholding Tax Code" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>One or more "withholding tax codes" are assigned to each withholding tax type. One of the things these codes determine is the various percentage rates for the withholding tax type.</Summary>
      <LongDescription>Note that when processing a business transaction, no more than one withholding tax code can be assigned per withholding tax type. If the business transaction is subject to more than one withholding taxes, these must be represented in the system by defining various withholding tax types.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CndnRoundingOffDiffAmount" Type="Edm.Decimal" Precision="6" Scale="3" sap:unit="TransactionCurrency" sap:label="Cond.Rounding Diff." sap:quickinfo="Rounding-Off Difference of the Condition" sap:creatable="false" sap:updatable="false"/>
    <Property Name="ConditionAmount" Type="Edm.Decimal" Precision="16" Scale="3" sap:unit="TransactionCurrency" sap:label="Value" sap:quickinfo="Condition Value" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The value, resulting from pricing, for a particular condition, total, or subtotal in a document.</Summary>
      <LongDescription>This value is used as a total for the condition in the pricing procedure.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="TransactionCurrency" Type="Edm.String" MaxLength="5" sap:label="Document Currency" sap:quickinfo="SD Document Currency" sap:semantics="currency-code">
     <Documentation>
      <Summary>The currency that applies to the document (for example, to a sales order or an invoice).</Summary>
      <LongDescription>The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionControl" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Condition Control" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates whether the prices or values in a condition are fixed or whether and in what way they changed.</Summary>
      <LongDescription>The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionInactiveReason" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Inactive Condition" sap:quickinfo="Condition is Inactive" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates if the condition is active.</Summary>
      <LongDescription>A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionClass" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Condition Class" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Preliminary structuring of condition types, for example, in surcharges and discounts or prices.</Summary>
      <LongDescription>Allows standardized processing of individual condition classes within the system.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PrcgProcedureCounterForHeader" Type="Edm.String" MaxLength="3" sap:display-format="NonNegative" sap:label="Counter" sap:quickinfo="Condition Counter (Header)" sap:creatable="false" sap:updatable="false"/>
    <Property Name="FactorForConditionBasisValue" Type="Edm.Double" sap:label="Condition Factor" sap:quickinfo="Factor for Condition Base Value" sap:creatable="false" sap:updatable="false"/>
    <Property Name="StructureCondition" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Structure Condition" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Controls whether the condition type is a duplicated condition or a cumulated condition.</Summary>
      <LongDescription>This control is only helpful when you use bill of materials or configurable materials:'  ' - None'A' - Duplication Condition: A duplicated condition is duplicated into all assigned items.'B' - Cumulation Condition: A cumulated condition contains the net value of all assigned items.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PeriodFactorForCndnBasisValue" Type="Edm.Double" sap:label="Condition Factor" sap:quickinfo="Factor for Condition Basis (Period)" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PricingScaleBasis" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Scale Basis" sap:quickinfo="Scale Basis Indicator" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionScaleBasisValue" Type="Edm.Decimal" Precision="24" Scale="9" sap:label="Scale Base Val." sap:quickinfo="Scale Base Value" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>A value or quantity that the system uses to access a pricing scale to determine a scale level.</Summary>
      <LongDescription>The scale base value can be a condition value or the value of a quantity, weight, and so on that has been entered in the document.You create a price condition based on a simple quantity scale with scale type A: Base scale:Quantity Price per Unit10 12 USD100 11 USD1000 10 USDA sales order item with 150 units qualifies for the condition scale quantity of 100 units and the price per unit of USD 11. In this case, the scale base value that determines the price is 150.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionScaleBasisUnit" Type="Edm.String" MaxLength="3" sap:label="Scale Unit of Meas." sap:quickinfo="Condition Scale Unit of Measure" sap:creatable="false" sap:updatable="false" sap:semantics="unit-of-measure">
     <Documentation>
      <Summary>Unit of measure to which the quantity scale refers.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionScaleBasisCurrency" Type="Edm.String" MaxLength="5" sap:label="Scale Currency" sap:creatable="false" sap:updatable="false" sap:semantics="currency-code">
     <Documentation>
      <Summary>Specifies a currency for a pricing scale in a condition record.</Summary>
      <LongDescription>If a pricing scale is based on a value instead of a quantity, you can specify a currency for the value. In the standard version of the SAP System, this field is only relevant in condition records for the following discounts:Price groupPrice group/Material pricing groupYou apply a price group discount to customers in a particular foreign country. When you create a condition record for this discount and enter values in the pricing scale, you can also enter the corresponding foreign currency. During pricing, the system then calculates discounts based on scale values in the foreign currency. The discount amount is then converted into the currency you are using in the sales document.After you enter a currency in this field and save the condition record, you cannot change the currency without deleting the record and creating it again.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="CndnIsRelevantForIntcoBilling" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Intercomp.Billing" sap:quickinfo="Condition for Intercompany Billing" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicator that defines a condition as relevant for the intercompany process.</Summary>
      <LongDescription>Intercompany conditions are usually statistical in the sales order and the customer invoice and not statistical in the intercompany invoice.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConditionIsManuallyChanged" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Changed Manually" sap:quickinfo="Condition Changed Manually" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>If this flag is set, the condition has been manually or automatically changed or created (by entry in the condition screen).</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ConditionIsForConfiguration" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="UsedforVariantConfig" sap:quickinfo="Condition Used for Variant Configuration" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>A condition that is relevant for variant configuration.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="VariantCondition" Type="Edm.String" MaxLength="26" sap:label="Variant Key" sap:quickinfo="Variant Condition Key" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Freely definable attribute that determines the valid price components of a configurable material.</Summary>
      <LongDescription>To model the price for a variant of a configurable material, you typically use a larger number of variant condition keys.In a business document, the price for a selected variant is realized as surcharges and discounts specific for this variant: The sales price of a bike depends on the material that is used to produce the frame. You define a characteristic FRAME_MATERIAL that can have the values steel, aluminum, and carbon with the following surcharges:Steel: 0.0 USD per pieceAluminum: + 300 USD per pieceCarbon: + 1000 USD per pieceYou define three different variant condition keys FRAME_STEEL, FRAME_ALU, and FRAME_CARBON and maintain the above-mentioned surcharges as condition records. During order creation, you select the variant of the bike with the carbon frame. This will lead to a surcharge of 1000 USD that corresponds to the variant condition key FRAME_CARBON.</LongDescription>
     </Documentation>
    </Property>
    <NavigationProperty Name="to_SalesOrder" Relationship="API_SALES_ORDER_SRV.assoc_3BF40B19B8B1DF0736F165DBAFECEE42" FromRole="FromRole_assoc_3BF40B19B8B1DF0736F165DBAFECEE42" ToRole="ToRole_assoc_3BF40B19B8B1DF0736F165DBAFECEE42"/>
    <NavigationProperty Name="to_SalesOrderItem" Relationship="API_SALES_ORDER_SRV.assoc_0FC12A865A38C45D885A046A7BD1FA20" FromRole="FromRole_assoc_0FC12A865A38C45D885A046A7BD1FA20" ToRole="ToRole_assoc_0FC12A865A38C45D885A046A7BD1FA20"/>
   </EntityType>
   <EntityType Name="A_SalesOrderItemTextType" sap:label="Item Text" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="SalesOrderItem"/>
     <PropertyRef Name="Language"/>
     <PropertyRef Name="LongTextID"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order" sap:creatable="false" sap:updatable="false"/>
    <Property Name="SalesOrderItem" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="NonNegative" sap:label="Item" sap:quickinfo="Sales Order Item" sap:creatable="false" sap:updatable="false"/>
    <Property Name="Language" Type="Edm.String" Nullable="false" MaxLength="2" sap:label="Language Key">
     <Documentation>
      <Summary>The language key indicates</Summary>
      <LongDescription>- the language in which texts are displayed,- the language in which you enter texts,- the language in which the system prints texts.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="LongTextID" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Text ID">
     <Documentation>
      <Summary>The text ID defines the various types of texts related to a text object. For example, the object "TEXT" (standard texts) can have the following text IDs:</Summary>
      <LongDescription>ST for user-specific standard texts (individual texts)SYST for cross-application system textsvarious IDs for specific application departments. You must have the appropriate access authorization in order to access these texts.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="LongText" Type="Edm.String" sap:label="String" sap:heading="" sap:sortable="false" sap:filterable="false"/>
    <NavigationProperty Name="to_SalesOrder" Relationship="API_SALES_ORDER_SRV.assoc_802E52C3F27DB910494E51738146B8F5" FromRole="FromRole_assoc_802E52C3F27DB910494E51738146B8F5" ToRole="ToRole_assoc_802E52C3F27DB910494E51738146B8F5"/>
    <NavigationProperty Name="to_SalesOrderItem" Relationship="API_SALES_ORDER_SRV.assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0" FromRole="FromRole_assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0" ToRole="ToRole_assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0"/>
   </EntityType>
   <EntityType Name="A_SalesOrderScheduleLineType" sap:label="Item Schedule Line" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="SalesOrderItem"/>
     <PropertyRef Name="ScheduleLine"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Document" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The number that uniquely identifies the sales document.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="SalesOrderItem" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="NonNegative" sap:label="Sales Document Item" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The number that uniquely identifies the item in the sales document.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ScheduleLine" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="NonNegative" sap:label="Schedule Line Number">
     <Documentation>
      <Summary>The number that uniquely identifies the schedule line in the sales document.</Summary>
      <LongDescription>When an item has more than one schedule line, the system automatically assigns a unique number to each line. The number is displayed in the details screens for schedule lines.The schedule line number serves internal purposes and does not, for example, determine the sequence of schedule lines in the overview screen. The schedule lines on the overview screen are sorted by date.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="RequestedDeliveryDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Delivery Date" sap:quickinfo="Requested Delivery Date"/>
    <Property Name="ConfirmedDeliveryDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Delivery Date" sap:quickinfo="Confirmed Delivery Date"/>
    <Property Name="OrderQuantityUnit" Type="Edm.String" MaxLength="3" sap:label="Sales Unit" sap:semantics="unit-of-measure">
     <Documentation>
      <Summary>Unit of measure  in which the material is sold.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="OrderQuantitySAPUnit" Type="Edm.String" MaxLength="3" sap:label="SAP Order Quantity" sap:quickinfo="SAP Unit Code for Order Quantity">
     <Documentation>
      <Summary>Unit of measure (SAP code) for the order quantity.</Summary>
      <LongDescription>For the order quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="OrderQuantityISOUnit" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="ISO Order Quantity" sap:quickinfo="ISO Unit Code for Order Quantity">
     <Documentation>
      <Summary>Unit of measure (ISO code) for the order quantity.</Summary>
      <LongDescription>For the order quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ScheduleLineOrderQuantity" Type="Edm.Decimal" Precision="13" Scale="3" sap:unit="OrderQuantityUnit" sap:label="Order Quantity" sap:quickinfo="Order Quantity in Sales Units">
     <Documentation>
      <Summary>Required order quantity in an individual schedule line.</Summary>
      <LongDescription>If you change the required order quantity in the schedule line, the system re-rounds the quantities, determines the rounded quantity, and re-runs the availability check based on the rounded quantity. The required order quantity remains as the orginal quantity (before rounding) in the schedule line.If the system does not round up the quantity, this means that the required order quantity matches the rounded quantity.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="ConfdOrderQtyByMatlAvailCheck" Type="Edm.Decimal" Precision="13" Scale="3" sap:unit="OrderQuantityUnit" sap:label="Confirmed Quantity">
     <Documentation>
      <Summary>The item quantity that the system confirms for shipping after checking inventory availability.</Summary>
      <LongDescription>The confirmed quantity can differ from the order quantity (for example, insufficient stock is available to meet the customer's request). If the availability of inventory changes during delivery processing, the confirmed quantity can also differ from the delivered quantity that the customer actually receives.If you change the order quantity (for example, if you create new schedule lines for the item), the system updates the confirmed quantity (depending on availability).</LongDescription>
     </Documentation>
    </Property>
    <Property Name="DeliveredQtyInOrderQtyUnit" Type="Edm.Decimal" Precision="13" Scale="3" sap:unit="OrderQuantityUnit" sap:label="Delivered Quantity"/>
    <Property Name="OpenConfdDelivQtyInOrdQtyUnit" Type="Edm.Decimal" Precision="13" Scale="3" sap:unit="OrderQuantityUnit" sap:label="Open Quantity" sap:quickinfo="Open Confirmed Delivery Quantity"/>
    <Property Name="CorrectedQtyInOrderQtyUnit" Type="Edm.Decimal" Precision="13" Scale="3" sap:unit="OrderQuantityUnit" sap:label="Corr.qty" sap:quickinfo="Corrected quantity in sales unit">
     <Documentation>
      <Summary>Rounded quantity of the required quantity in the schedule line in the sales order.</Summary>
      <LongDescription>The system rounds the quantity using the rounding profiles from the customer-material info record or the material master record. The profile can be switched on for each customer.If you change the rounded quantity, the system automatically performs an availability check and/or delivery scheduling and updates the confirmed quantity. The rounded quantity is cumulated in the total order quantity of the item. The required order quantity remains as the original quantity (before rounding) in the schedule line.If the system does not round the quantity, the rounded quantity of the required order quantity in the schedule line is valid.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="DelivBlockReasonForSchedLine" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Delivery Block" sap:quickinfo="Schedule Line Blocked for Delivery">
     <Documentation>
      <Summary>Indicates if a schedule line for the item is blocked for delivery.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
   </EntityType>
   <EntityType Name="A_SalesOrderTextType" sap:label="Header Text" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="Language"/>
     <PropertyRef Name="LongTextID"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order" sap:creatable="false" sap:updatable="false"/>
    <Property Name="Language" Type="Edm.String" Nullable="false" MaxLength="2" sap:label="Language Key">
     <Documentation>
      <Summary>The language key indicates</Summary>
      <LongDescription>- the language in which texts are displayed,- the language in which you enter texts,- the language in which the system prints texts.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="LongTextID" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Text ID">
     <Documentation>
      <Summary>The text ID defines the various types of texts related to a text object. For example, the object "TEXT" (standard texts) can have the following text IDs:</Summary>
      <LongDescription>ST for user-specific standard texts (individual texts)SYST for cross-application system textsvarious IDs for specific application departments. You must have the appropriate access authorization in order to access these texts.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="LongText" Type="Edm.String" sap:label="String" sap:heading="" sap:sortable="false" sap:filterable="false"/>
    <NavigationProperty Name="to_SalesOrder" Relationship="API_SALES_ORDER_SRV.assoc_9211CD1FA0A3B03DDB30735294259743" FromRole="FromRole_assoc_9211CD1FA0A3B03DDB30735294259743" ToRole="ToRole_assoc_9211CD1FA0A3B03DDB30735294259743"/>
   </EntityType>
   <EntityType Name="A_SlsOrdPaymentPlanItemDetailsType" sap:label="Header Payment Plan" sap:content-version="1">
    <Key>
     <PropertyRef Name="SalesOrder"/>
     <PropertyRef Name="PaymentPlanItem"/>
    </Key>
    <Property Name="SalesOrder" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Sales Order" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PaymentPlanItem" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="NonNegative" sap:label="Item" sap:quickinfo="Item for billing plan/invoice plan/payment cards"/>
    <Property Name="PaymentPlan" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Bill. Plan. No." sap:quickinfo="Billing Plan Number / Invoicing Plan Number" sap:creatable="false" sap:updatable="false"/>
    <Property Name="ElectronicPaymentType" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="EPayt Type" sap:quickinfo="Electronic Payment: Payment Type">
     <Documentation>
      <Summary>Specifies the type of electronic payment.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ElectronicPayment" Type="Edm.String" MaxLength="25" sap:display-format="UpperCase" sap:label="Account Number" sap:quickinfo="Electronic Payment: Account Number">
     <Documentation>
      <Summary>The account number of the electronic payment. Along with the electronic payment type, this number uniquely identifies the payment.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="EPaytValidityStartDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="EPayt Valid from" sap:quickinfo="Electronic Payment: Valid from">
     <Documentation>
      <Summary>Date as of which the payment account is valid.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="EPaytValidityEndDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="EPayt Valid to" sap:quickinfo="Electronic Payment: Valid to">
     <Documentation>
      <Summary>Date up to which the payment account is valid.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="ElectronicPaymentHolderName" Type="Edm.String" MaxLength="40" sap:label="Account Holder" sap:quickinfo="Electronic Payment: Name of Account Holder">
     <Documentation>
      <Summary>The name of the person or company on the electronic payment account.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AuthorizedAmountInAuthznCrcy" Type="Edm.Decimal" Precision="16" Scale="3" sap:unit="AuthorizationCurrency" sap:label="Authorized Amount" sap:quickinfo="Electronic Payment: Authorized Amount">
     <Documentation>
      <Summary>Specifies the amount authorized by the clearing house. It may differ from the requested authorization amount, as in the case of partial authorization.</Summary>
      <LongDescription>The system uses the authorized amount to determine whether to block the sales order or delivery.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="AuthorizationCurrency" Type="Edm.String" MaxLength="5" sap:label="Currency" sap:quickinfo="Currency Key" sap:creatable="false" sap:updatable="false" sap:semantics="currency-code">
     <Documentation>
      <Summary>Currency key for amounts in the system.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AuthorizationByDigitalPaytSrvc" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Auth. Number" sap:quickinfo="Electronic Payment: Authorization Number">
     <Documentation>
      <Summary>Number assigned to a successful authorization by the clearing house.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AuthorizationByAcquirer" Type="Edm.String" MaxLength="15" sap:display-format="UpperCase" sap:label="Auth. Ref. Code" sap:quickinfo="Electronic Payment: Authorization Reference Code" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Reference code assigned to an authorization by the clearing house to aid in tracking the transaction to which the authorization belongs.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AuthorizationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="EPayt Auth. Date" sap:quickinfo="Electronic Payment: Authorization Date" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Date on which the SAP system requested the authorization.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AuthorizationTime" Type="Edm.Time" Precision="0" sap:label="EPayt Auth. Time" sap:quickinfo="Electronic Payment: Authorization Time" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Time at which the SAP system requested the authorization.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="AuthorizationStatusName" Type="Edm.String" MaxLength="40" sap:label="Text" sap:quickinfo="Payment cards: Result text" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Contains the text describing the various responses that you receive from the clearing house in the authorization and settlement processes.</Summary>
      <LongDescription>The clearing house checks the information they receive from you on the payment card and cardholder, and return responses that refer to errors and problems which occur during these checks.Create a text in the SAP System that matches the clearing house response.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="EPaytByDigitalPaymentSrvc" Type="Edm.String" MaxLength="25" sap:display-format="UpperCase" sap:label="EPayt Token" sap:quickinfo="Token for Digital Payment Integration in SD"/>
    <Property Name="ElectronicPaymentCallStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Call Status" sap:quickinfo="Electronic Payment: Call Status" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates whether you successfully reached the clearing house's computer system for authorization, and whether you received an answer.</Summary>
      <LongDescription>There are four types of responses:Not relevantExternal system not reachedExternal system reached: no responseExternal system reached: response received</LongDescription>
     </Documentation>
    </Property>
    <Property Name="EPaytAuthorizationResult" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Rsp to Auth. Check" sap:quickinfo="Electronic Payment: Response to Authorization Checks" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates the status of the authorization for this payment based on the authorization response sent back by the clearing house.</Summary>
      <LongDescription>The SAP System recognizes only three responses:Checks successfulUnsuccessful: authorize laterUnsuccessful: block authorization</LongDescription>
     </Documentation>
    </Property>
    <Property Name="EPaytToBeAuthorizedAmount" Type="Edm.Decimal" Precision="16" Scale="3" sap:unit="AuthorizationCurrency" sap:label="Amt to Be Auth." sap:quickinfo="Electronic Payment: Amount to Be Authorized" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>The sum of all the authorization amounts in the payment plan. This is the amount sent to the clearing house for authorization.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="EPaytAuthorizationIsExpired" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Auth. Expired" sap:quickinfo="Electronic Payment: Authorization Expired" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates whether the authorization has expired.</Summary>
      <LongDescription>Note that the system determines whether an authorization has expired based on the validity period. This validity period is valid for all authorizations in the SAP System.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="EPaytAmountIsChanged" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Amount Changed" sap:quickinfo="Electronic Payment: Amount Changed" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates whether the authorization amount has been changed manually.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="PreauthorizationIsRequested" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Preauthorization" sap:quickinfo="Electronic Payment: Preauthorization" sap:creatable="false" sap:updatable="false">
     <Documentation>
      <Summary>Indicates whether a transaction has been preauthorized.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="PaymentServiceProvider" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Paymnt Serv. Provid." sap:quickinfo="Payment Service Provider for Digital Payments"/>
    <Property Name="PaymentByPaymentServicePrvdr" Type="Edm.String" MaxLength="40" sap:label="Payment Identifier" sap:quickinfo="Digital Payments: Payment ID from Payment Service Provider"/>
    <Property Name="TransactionByPaytSrvcPrvdr" Type="Edm.String" MaxLength="40" sap:display-format="UpperCase" sap:label="PSP Transaction ID" sap:quickinfo="SAP Digital Payments: Transaction ID of PSP"/>
    <Property Name="MerchantByClearingHouse" Type="Edm.String" MaxLength="15" sap:display-format="UpperCase" sap:label="Merchant ID" sap:quickinfo="Electronic Payment: Merchant ID at Clearing House">
     <Documentation>
      <Summary>The unique number issued by the clearing house to identify a merchant for settling payment.</Summary>
      <LongDescription/>
     </Documentation>
    </Property>
    <Property Name="PaymentCardAuthznRelationID" Type="Edm.String" MaxLength="44" sap:display-format="UpperCase" sap:label="Auth. Rel. ID" sap:quickinfo="Unique identifier of a previous successful authorization"/>
    <Property Name="MaximumToBeAuthorizedAmount" Type="Edm.Decimal" Precision="16" Scale="3" sap:unit="AuthorizationCurrency" sap:label="Billing Value" sap:quickinfo="Value to be billed/calc. on date in billing/invoice plan">
     <Documentation>
      <Summary>Specifies the value to be billed which the system determines for the billing date on the basis of the billing rule assigned to it.</Summary>
      <LongDescription>In the case of a contract, this is a total amount. For a project, this is a partial amount of the overall billing value which is determined on the basis of a percentage.</LongDescription>
     </Documentation>
    </Property>
    <Property Name="PaytPlnForAuthorizationItem" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Higher-level plan" sap:quickinfo="Higher-level payment card plan number for billing" sap:creatable="false" sap:updatable="false"/>
    <Property Name="PaytPlnItmForAuthorizationItem" Type="Edm.String" MaxLength="6" sap:display-format="NonNegative" sap:label="Higher-level item" sap:quickinfo="Higher-level item in billing plan" sap:creatable="false" sap:updatable="false"/>
    <NavigationProperty Name="to_SalesOrder" Relationship="API_SALES_ORDER_SRV.assoc_11F73D17E966CAF8365A0A85432C45F3" FromRole="FromRole_assoc_11F73D17E966CAF8365A0A85432C45F3" ToRole="ToRole_assoc_11F73D17E966CAF8365A0A85432C45F3"/>
   </EntityType>
   <ComplexType Name="FunctionResult">
    <Property Name="Boolean" Type="Edm.Boolean" Nullable="false" sap:label="Indicator" sap:heading="Flag" sap:quickinfo="General Flag" sap:creatable="false" sap:updatable="false" sap:sortable="false" sap:filterable="false"/>
   </ComplexType>
   <Association Name="assoc_3BF40B19B8B1DF0736F165DBAFECEE42" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemPrElementType" Multiplicity="1" Role="FromRole_assoc_3BF40B19B8B1DF0736F165DBAFECEE42"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="ToRole_assoc_3BF40B19B8B1DF0736F165DBAFECEE42"/>
   </Association>
   <Association Name="assoc_0FC12A865A38C45D885A046A7BD1FA20" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemPrElementType" Multiplicity="1" Role="FromRole_assoc_0FC12A865A38C45D885A046A7BD1FA20"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="1" Role="ToRole_assoc_0FC12A865A38C45D885A046A7BD1FA20"/>
   </Association>
   <Association Name="assoc_8F721694C94560109555442071763439" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderHeaderPartnerType" Multiplicity="1" Role="FromRole_assoc_8F721694C94560109555442071763439"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="ToRole_assoc_8F721694C94560109555442071763439"/>
   </Association>
   <Association Name="assoc_E0F0B75CE5743C11AC56990C6083E0BA" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="FromRole_assoc_E0F0B75CE5743C11AC56990C6083E0BA"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderHeaderPartnerType" Multiplicity="*" Role="ToRole_assoc_E0F0B75CE5743C11AC56990C6083E0BA"/>
   </Association>
   <Association Name="assoc_44F7AAFBAB4403914DD21D2B054AE91D" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="FromRole_assoc_44F7AAFBAB4403914DD21D2B054AE91D"/>
    <End Type="API_SALES_ORDER_SRV.A_SlsOrdPaymentPlanItemDetailsType" Multiplicity="*" Role="ToRole_assoc_44F7AAFBAB4403914DD21D2B054AE91D"/>
   </Association>
   <Association Name="assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="FromRole_assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderHeaderPrElementType" Multiplicity="*" Role="ToRole_assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21"/>
   </Association>
   <Association Name="assoc_D06EF7DEC5E9B78C200493F21B05A94E" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="FromRole_assoc_D06EF7DEC5E9B78C200493F21B05A94E"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderTextType" Multiplicity="*" Role="ToRole_assoc_D06EF7DEC5E9B78C200493F21B05A94E"/>
   </Association>
   <Association Name="assoc_42CCE6159E335C5B7697EE6BC8D37107" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="FromRole_assoc_42CCE6159E335C5B7697EE6BC8D37107"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="*" Role="ToRole_assoc_42CCE6159E335C5B7697EE6BC8D37107"/>
   </Association>
   <Association Name="assoc_802E52C3F27DB910494E51738146B8F5" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemTextType" Multiplicity="1" Role="FromRole_assoc_802E52C3F27DB910494E51738146B8F5"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="ToRole_assoc_802E52C3F27DB910494E51738146B8F5"/>
   </Association>
   <Association Name="assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemTextType" Multiplicity="1" Role="FromRole_assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="1" Role="ToRole_assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0"/>
   </Association>
   <Association Name="assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemPartnerType" Multiplicity="1" Role="FromRole_assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="ToRole_assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00"/>
   </Association>
   <Association Name="assoc_2E7827BA025D2DC7290DEA3E71FF39FB" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemPartnerType" Multiplicity="1" Role="FromRole_assoc_2E7827BA025D2DC7290DEA3E71FF39FB"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="1" Role="ToRole_assoc_2E7827BA025D2DC7290DEA3E71FF39FB"/>
   </Association>
   <Association Name="assoc_9211CD1FA0A3B03DDB30735294259743" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderTextType" Multiplicity="1" Role="FromRole_assoc_9211CD1FA0A3B03DDB30735294259743"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="ToRole_assoc_9211CD1FA0A3B03DDB30735294259743"/>
   </Association>
   <Association Name="assoc_5EBE73B545500EE6B48597931F7D5C56" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="1" Role="FromRole_assoc_5EBE73B545500EE6B48597931F7D5C56"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemPartnerType" Multiplicity="*" Role="ToRole_assoc_5EBE73B545500EE6B48597931F7D5C56"/>
   </Association>
   <Association Name="assoc_A18E7EFDF1ADD05474B187D10B62BDBF" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="1" Role="FromRole_assoc_A18E7EFDF1ADD05474B187D10B62BDBF"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemPrElementType" Multiplicity="*" Role="ToRole_assoc_A18E7EFDF1ADD05474B187D10B62BDBF"/>
   </Association>
   <Association Name="assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="1" Role="FromRole_assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="ToRole_assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD"/>
   </Association>
   <Association Name="assoc_31BB747044FCC7AA5DA94B21FD458954" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="1" Role="FromRole_assoc_31BB747044FCC7AA5DA94B21FD458954"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderScheduleLineType" Multiplicity="*" Role="ToRole_assoc_31BB747044FCC7AA5DA94B21FD458954"/>
   </Association>
   <Association Name="assoc_3604F4165550FA74B882A4F3345D936F" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemType" Multiplicity="1" Role="FromRole_assoc_3604F4165550FA74B882A4F3345D936F"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderItemTextType" Multiplicity="*" Role="ToRole_assoc_3604F4165550FA74B882A4F3345D936F"/>
   </Association>
   <Association Name="assoc_11F73D17E966CAF8365A0A85432C45F3" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SlsOrdPaymentPlanItemDetailsType" Multiplicity="1" Role="FromRole_assoc_11F73D17E966CAF8365A0A85432C45F3"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="ToRole_assoc_11F73D17E966CAF8365A0A85432C45F3"/>
   </Association>
   <Association Name="assoc_C516ABBC5925268953A9AC7D6F836887" sap:content-version="1">
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderHeaderPrElementType" Multiplicity="1" Role="FromRole_assoc_C516ABBC5925268953A9AC7D6F836887"/>
    <End Type="API_SALES_ORDER_SRV.A_SalesOrderType" Multiplicity="1" Role="ToRole_assoc_C516ABBC5925268953A9AC7D6F836887"/>
   </Association>
   <EntityContainer Name="API_SALES_ORDER_SRV_Entities" m:IsDefaultEntityContainer="true" sap:message-scope-supported="true" sap:supported-formats="atom json xlsx">
    <EntitySet Name="A_SalesOrder" EntityType="API_SALES_ORDER_SRV.A_SalesOrderType" sap:content-version="1"/>
    <EntitySet Name="A_SalesOrderHeaderPartner" EntityType="API_SALES_ORDER_SRV.A_SalesOrderHeaderPartnerType" sap:content-version="1"/>
    <EntitySet Name="A_SalesOrderHeaderPrElement" EntityType="API_SALES_ORDER_SRV.A_SalesOrderHeaderPrElementType" sap:content-version="1"/>
    <EntitySet Name="A_SalesOrderItem" EntityType="API_SALES_ORDER_SRV.A_SalesOrderItemType" sap:content-version="1"/>
    <EntitySet Name="A_SalesOrderItemPartner" EntityType="API_SALES_ORDER_SRV.A_SalesOrderItemPartnerType" sap:content-version="1"/>
    <EntitySet Name="A_SalesOrderItemPrElement" EntityType="API_SALES_ORDER_SRV.A_SalesOrderItemPrElementType" sap:content-version="1"/>
    <EntitySet Name="A_SalesOrderItemText" EntityType="API_SALES_ORDER_SRV.A_SalesOrderItemTextType" sap:content-version="1"/>
    <EntitySet Name="A_SalesOrderScheduleLine" EntityType="API_SALES_ORDER_SRV.A_SalesOrderScheduleLineType" sap:content-version="1"/>
    <EntitySet Name="A_SalesOrderText" EntityType="API_SALES_ORDER_SRV.A_SalesOrderTextType" sap:content-version="1"/>
    <EntitySet Name="A_SlsOrdPaymentPlanItemDetails" EntityType="API_SALES_ORDER_SRV.A_SlsOrdPaymentPlanItemDetailsType" sap:content-version="1"/>
    <AssociationSet Name="assoc_802E52C3F27DB910494E51738146B8F5" Association="API_SALES_ORDER_SRV.assoc_802E52C3F27DB910494E51738146B8F5" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItemText" Role="FromRole_assoc_802E52C3F27DB910494E51738146B8F5"/>
     <End EntitySet="A_SalesOrder" Role="ToRole_assoc_802E52C3F27DB910494E51738146B8F5"/>
    </AssociationSet>
    <AssociationSet Name="assoc_8F721694C94560109555442071763439" Association="API_SALES_ORDER_SRV.assoc_8F721694C94560109555442071763439" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderHeaderPartner" Role="FromRole_assoc_8F721694C94560109555442071763439"/>
     <End EntitySet="A_SalesOrder" Role="ToRole_assoc_8F721694C94560109555442071763439"/>
    </AssociationSet>
    <AssociationSet Name="assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00" Association="API_SALES_ORDER_SRV.assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItemPartner" Role="FromRole_assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00"/>
     <End EntitySet="A_SalesOrder" Role="ToRole_assoc_DC6F0BF95AA2ABDAA77BD5D5D7640C00"/>
    </AssociationSet>
    <AssociationSet Name="assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD" Association="API_SALES_ORDER_SRV.assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItem" Role="FromRole_assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD"/>
     <End EntitySet="A_SalesOrder" Role="ToRole_assoc_1E8A9B3CA2EE8DAD94F8F581B21EABBD"/>
    </AssociationSet>
    <AssociationSet Name="assoc_2E7827BA025D2DC7290DEA3E71FF39FB" Association="API_SALES_ORDER_SRV.assoc_2E7827BA025D2DC7290DEA3E71FF39FB" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItemPartner" Role="FromRole_assoc_2E7827BA025D2DC7290DEA3E71FF39FB"/>
     <End EntitySet="A_SalesOrderItem" Role="ToRole_assoc_2E7827BA025D2DC7290DEA3E71FF39FB"/>
    </AssociationSet>
    <AssociationSet Name="assoc_A18E7EFDF1ADD05474B187D10B62BDBF" Association="API_SALES_ORDER_SRV.assoc_A18E7EFDF1ADD05474B187D10B62BDBF" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItem" Role="FromRole_assoc_A18E7EFDF1ADD05474B187D10B62BDBF"/>
     <End EntitySet="A_SalesOrderItemPrElement" Role="ToRole_assoc_A18E7EFDF1ADD05474B187D10B62BDBF"/>
    </AssociationSet>
    <AssociationSet Name="assoc_42CCE6159E335C5B7697EE6BC8D37107" Association="API_SALES_ORDER_SRV.assoc_42CCE6159E335C5B7697EE6BC8D37107" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrder" Role="FromRole_assoc_42CCE6159E335C5B7697EE6BC8D37107"/>
     <End EntitySet="A_SalesOrderItem" Role="ToRole_assoc_42CCE6159E335C5B7697EE6BC8D37107"/>
    </AssociationSet>
    <AssociationSet Name="assoc_0FC12A865A38C45D885A046A7BD1FA20" Association="API_SALES_ORDER_SRV.assoc_0FC12A865A38C45D885A046A7BD1FA20" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItemPrElement" Role="FromRole_assoc_0FC12A865A38C45D885A046A7BD1FA20"/>
     <End EntitySet="A_SalesOrderItem" Role="ToRole_assoc_0FC12A865A38C45D885A046A7BD1FA20"/>
    </AssociationSet>
    <AssociationSet Name="assoc_D06EF7DEC5E9B78C200493F21B05A94E" Association="API_SALES_ORDER_SRV.assoc_D06EF7DEC5E9B78C200493F21B05A94E" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrder" Role="FromRole_assoc_D06EF7DEC5E9B78C200493F21B05A94E"/>
     <End EntitySet="A_SalesOrderText" Role="ToRole_assoc_D06EF7DEC5E9B78C200493F21B05A94E"/>
    </AssociationSet>
    <AssociationSet Name="assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21" Association="API_SALES_ORDER_SRV.assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrder" Role="FromRole_assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21"/>
     <End EntitySet="A_SalesOrderHeaderPrElement" Role="ToRole_assoc_5C52AA5C0E6EBBDD6C9EA9E0A4FFAE21"/>
    </AssociationSet>
    <AssociationSet Name="assoc_3BF40B19B8B1DF0736F165DBAFECEE42" Association="API_SALES_ORDER_SRV.assoc_3BF40B19B8B1DF0736F165DBAFECEE42" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItemPrElement" Role="FromRole_assoc_3BF40B19B8B1DF0736F165DBAFECEE42"/>
     <End EntitySet="A_SalesOrder" Role="ToRole_assoc_3BF40B19B8B1DF0736F165DBAFECEE42"/>
    </AssociationSet>
    <AssociationSet Name="assoc_3604F4165550FA74B882A4F3345D936F" Association="API_SALES_ORDER_SRV.assoc_3604F4165550FA74B882A4F3345D936F" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItem" Role="FromRole_assoc_3604F4165550FA74B882A4F3345D936F"/>
     <End EntitySet="A_SalesOrderItemText" Role="ToRole_assoc_3604F4165550FA74B882A4F3345D936F"/>
    </AssociationSet>
    <AssociationSet Name="assoc_31BB747044FCC7AA5DA94B21FD458954" Association="API_SALES_ORDER_SRV.assoc_31BB747044FCC7AA5DA94B21FD458954" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItem" Role="FromRole_assoc_31BB747044FCC7AA5DA94B21FD458954"/>
     <End EntitySet="A_SalesOrderScheduleLine" Role="ToRole_assoc_31BB747044FCC7AA5DA94B21FD458954"/>
    </AssociationSet>
    <AssociationSet Name="assoc_44F7AAFBAB4403914DD21D2B054AE91D" Association="API_SALES_ORDER_SRV.assoc_44F7AAFBAB4403914DD21D2B054AE91D" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrder" Role="FromRole_assoc_44F7AAFBAB4403914DD21D2B054AE91D"/>
     <End EntitySet="A_SlsOrdPaymentPlanItemDetails" Role="ToRole_assoc_44F7AAFBAB4403914DD21D2B054AE91D"/>
    </AssociationSet>
    <AssociationSet Name="assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0" Association="API_SALES_ORDER_SRV.assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItemText" Role="FromRole_assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0"/>
     <End EntitySet="A_SalesOrderItem" Role="ToRole_assoc_CAC77A6CEA49335D6F6A2CC8AC8469E0"/>
    </AssociationSet>
    <AssociationSet Name="assoc_11F73D17E966CAF8365A0A85432C45F3" Association="API_SALES_ORDER_SRV.assoc_11F73D17E966CAF8365A0A85432C45F3" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SlsOrdPaymentPlanItemDetails" Role="FromRole_assoc_11F73D17E966CAF8365A0A85432C45F3"/>
     <End EntitySet="A_SalesOrder" Role="ToRole_assoc_11F73D17E966CAF8365A0A85432C45F3"/>
    </AssociationSet>
    <AssociationSet Name="assoc_C516ABBC5925268953A9AC7D6F836887" Association="API_SALES_ORDER_SRV.assoc_C516ABBC5925268953A9AC7D6F836887" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderHeaderPrElement" Role="FromRole_assoc_C516ABBC5925268953A9AC7D6F836887"/>
     <End EntitySet="A_SalesOrder" Role="ToRole_assoc_C516ABBC5925268953A9AC7D6F836887"/>
    </AssociationSet>
    <AssociationSet Name="assoc_E0F0B75CE5743C11AC56990C6083E0BA" Association="API_SALES_ORDER_SRV.assoc_E0F0B75CE5743C11AC56990C6083E0BA" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrder" Role="FromRole_assoc_E0F0B75CE5743C11AC56990C6083E0BA"/>
     <End EntitySet="A_SalesOrderHeaderPartner" Role="ToRole_assoc_E0F0B75CE5743C11AC56990C6083E0BA"/>
    </AssociationSet>
    <AssociationSet Name="assoc_9211CD1FA0A3B03DDB30735294259743" Association="API_SALES_ORDER_SRV.assoc_9211CD1FA0A3B03DDB30735294259743" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderText" Role="FromRole_assoc_9211CD1FA0A3B03DDB30735294259743"/>
     <End EntitySet="A_SalesOrder" Role="ToRole_assoc_9211CD1FA0A3B03DDB30735294259743"/>
    </AssociationSet>
    <AssociationSet Name="assoc_5EBE73B545500EE6B48597931F7D5C56" Association="API_SALES_ORDER_SRV.assoc_5EBE73B545500EE6B48597931F7D5C56" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
     <End EntitySet="A_SalesOrderItem" Role="FromRole_assoc_5EBE73B545500EE6B48597931F7D5C56"/>
     <End EntitySet="A_SalesOrderItemPartner" Role="ToRole_assoc_5EBE73B545500EE6B48597931F7D5C56"/>
    </AssociationSet>
    <FunctionImport Name="rejectApprovalRequest" ReturnType="API_SALES_ORDER_SRV.FunctionResult" m:HttpMethod="POST">
     <Parameter Name="SalesOrder" Type="Edm.String" Mode="In" MaxLength="11000"/>
    </FunctionImport>
    <FunctionImport Name="releaseApprovalRequest" ReturnType="API_SALES_ORDER_SRV.FunctionResult" m:HttpMethod="POST">
     <Parameter Name="SalesOrder" Type="Edm.String" Mode="In" MaxLength="11000"/>
    </FunctionImport>
   </EntityContainer>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Common.ApplyMultiUnitBehaviorForSortingAndFiltering" Bool="true"/>
    <Annotation Term="Aggregation.ApplySupported">
     <Record>
      <PropertyValue Property="Transformations">
       <Collection>
        <String>aggregate</String>
        <String>groupby</String>
        <String>filter</String>
       </Collection>
      </PropertyValue>
      <PropertyValue Property="Rollup" EnumMember="None"/>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderItemText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.FilterRestrictions">
     <Record>
      <PropertyValue Property="FilterExpressionRestrictions">
       <Collection>
        <Record>
         <PropertyValue Property="Property" PropertyPath="LongText"/>
         <PropertyValue Property="AllowedExpressions" String="SearchExpression"/>
        </Record>
       </Collection>
      </PropertyValue>
      <PropertyValue Property="NonFilterableProperties">
       <Collection>
        <PropertyPath>LongText</PropertyPath>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.SortRestrictions">
     <Record>
      <PropertyValue Property="NonSortableProperties">
       <Collection>
        <PropertyPath>LongText</PropertyPath>
        <PropertyPath>LongText</PropertyPath>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.FilterRestrictions">
     <Record>
      <PropertyValue Property="FilterExpressionRestrictions">
       <Collection>
        <Record>
         <PropertyValue Property="Property" PropertyPath="LongText"/>
         <PropertyValue Property="AllowedExpressions" String="SearchExpression"/>
        </Record>
       </Collection>
      </PropertyValue>
      <PropertyValue Property="NonFilterableProperties">
       <Collection>
        <PropertyPath>LongText</PropertyPath>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.SortRestrictions">
     <Record>
      <PropertyValue Property="NonSortableProperties">
       <Collection>
        <PropertyPath>LongText</PropertyPath>
        <PropertyPath>LongText</PropertyPath>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderValAddedSrvc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.FilterRestrictions">
     <Record>
      <PropertyValue Property="NonFilterableProperties">
       <Collection>
        <PropertyPath>ValueAddedServiceLongText</PropertyPath>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.SortRestrictions">
     <Record>
      <PropertyValue Property="NonSortableProperties">
       <Collection>
        <PropertyPath>ValueAddedServiceLongText</PropertyPath>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderHeaderPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads the header partners of all sales orders."/>
      <PropertyValue Property="LongDescription" String="Reads the partner data from the headers of all sales orders in the system. The data is relevant for all items for which no item-specific partners are maintained."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads the header partners of a specific sales order and with a specific partner function."/>
        <PropertyValue Property="LongDescription" String="Reads the data of partners with a specific partner function from the header of a specific sales order. Consumers must pass the following key fields: sales order ID and partner function."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Inserts the header partners of a specific sales order and with a specific partner function."/>
      <PropertyValue Property="LongDescription" String="Inserts the data of partners with a specific partner function from the header of a specific sales order. Consumers must pass the following key fields: sales order ID and partner function."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates the header partners of a specific sales order and with a specific partner function."/>
      <PropertyValue Property="LongDescription" String="Updates the data of partners with a specific partner function from the header of a specific sales order. Consumers must pass the following key fields: sales order ID and partner function."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes the header partners of a specific sales order and with a specific partner function."/>
      <PropertyValue Property="LongDescription" String="Deletes the data of partners with a specific partner function from the header of a specific sales order. Consumers must pass the following key fields: sales order ID and partner function."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order header for a specific header partner."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order header data for a specific header partner function. Consumers must pass the following key fields: partner function and the sales order ID."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Inserts the sales order header for a specific header partner."/>
           <PropertyValue Property="LongDescription" String="Inserts the sales order header data for a specific header partner function. Consumers must pass the following key fields: partner function and the sales order ID."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrder" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads all sales order headers."/>
      <PropertyValue Property="LongDescription" String="Reads the header data of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads the header of a specific sales order."/>
        <PropertyValue Property="LongDescription" String="Reads the header data of a specific sales order. Consumers must pass the sales order ID (key field)."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Creates a sales order."/>
      <PropertyValue Property="LongDescription" String="Creates a sales order header using deep insert requests. This means consumers can create a sales order with all possible sub-entities (for example, header partners or items)."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Updates the header data of a specific sales order. Consumers must pass the sales order ID (key field)."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Deletes the header data of a specific sales order. Consumers must pass the sales order ID (key field)."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Partner"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the header partners of a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Reads the partner data from the header of a specific sales order. Consumers must pass the sales order ID (key field). The data is relevant for all items for which no item-specific partners are maintained."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Partner"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Inserts the header partners of a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Inserts the partner data from the header of a specific sales order. Consumers must pass the sales order ID (key field). The data is relevant for all items for which no item-specific partners are maintained."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PricingElement"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the header pricing element of a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Reads the pricing element data from the header of a specific sales order. Consumers must pass the sales order ID (key field)."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PricingElement"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Inserts the header pricing element of a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Inserts the pricing element data from the header of a specific sales order. Consumers must pass the sales order ID (key field)."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Text"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the header texts of a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Reads the text data from the header of a specific sales order. Consumers must pass the sales order ID (key field)."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Text"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Inserts the header texts of a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Inserts the text data from the header of a specific sales order. Consumers must pass the sales order ID (key field)."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Item"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads all items of a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Reads all item data of a specific sales order. Consumers must pass the sales order ID (key field)."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Item"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Creates a sales order item for a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Creates a sales order item for a specific sales order using deep insert requests. This means consumers can create an item with all possible sub-entities (for example, item partners or item texts)."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PaymentPlanItemDetails"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the header payment plan of a specific sales order."/>
           <PropertyValue Property="LongDescription" String="Reads the payment plan data from the header of a specific sales order. Consumers must pass the sales order ID (key field)."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderHeaderPrElement" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads the header pricing elements of all sales orders."/>
      <PropertyValue Property="LongDescription" String="Reads the pricing element data from the headers of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads the header pricing element for a specific sales order."/>
        <PropertyValue Property="LongDescription" String="Reads the pricing element data from the header of a specific sales order. Consumers must pass the following key fields: sales order ID, pricing procedure step, and pricing procedure counter."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Inserts a header pricing element for a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Inserts the pricing element data from the header of a specific sales order. Consumers must pass the following key fields: sales order ID, pricing procedure step, and pricing procedure counter."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates a header pricing element for a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Updates the pricing element data from the header of a specific sales order. Consumers must pass the following key fields: sales order ID, pricing procedure step, and pricing procedure counter."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes a header pricing element for a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Deletes the pricing element data from the header of a specific sales order. Consumers must pass the following key fields: sales order ID, pricing procedure step, and pricing procedure counter."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order header for a specific pricing element."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order header data for a specific pricing element. Consumers must pass the following key fields: sales order ID, pricing procedure step, and pricing procedure counter."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Inserts the sales order header for a specific pricing element."/>
           <PropertyValue Property="LongDescription" String="Inserts the sales order header data for a specific pricing element. Consumers must pass the following key fields: sales order ID, pricing procedure step, and pricing procedure counter."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderItem" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads all sales order items."/>
      <PropertyValue Property="LongDescription" String="Reads the item data of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads a specific sales order item."/>
        <PropertyValue Property="LongDescription" String="Reads the data of a specific sales order item. Consumers must pass the following key fields: sales order ID and item number."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Creates a sales order item."/>
      <PropertyValue Property="LongDescription" String="Creates a sales order item using a deep insert request. This means consumers can create an item with all possible sub-entities (for example, item partners or item texts)."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates a specific sales order item."/>
      <PropertyValue Property="LongDescription" String="Updates the data of a specific sales order item. Consumers must pass the following key fields: sales order ID and item number."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes a specific sales order item."/>
      <PropertyValue Property="LongDescription" String="Deletes the data of a specific sales order item. Consumers must pass the following key fields: sales order ID and item number."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Partner"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the item partners of a specific sales order item."/>
           <PropertyValue Property="LongDescription" String="Reads the partner data for a specific item of a specific sales order. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Partner"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Inserts the item partners of a specific sales order item."/>
           <PropertyValue Property="LongDescription" String="Inserts the partner data for a specific item of a specific sales order. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PricingElement"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the pricing element of a specific sales order item."/>
           <PropertyValue Property="LongDescription" String="Reads the pricing element data for a specific item of a specific sales order. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PricingElement"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Inserts the pricing element of a specific sales order item."/>
           <PropertyValue Property="LongDescription" String="Inserts the pricing element data for a specific item of a specific sales order. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_ScheduleLine"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the schedule lines of a specific sales order item."/>
           <PropertyValue Property="LongDescription" String="Reads the schedule line data for a specific item. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_ScheduleLine"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Creates schedule lines for a specific sales order item."/>
           <PropertyValue Property="LongDescription" String="Creates the schedule line data for a specific item. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Text"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the text of a specific sales order item."/>
           <PropertyValue Property="LongDescription" String="Reads the text data for a specific item. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Text"/>
         <PropertyValue Property="InsertRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Inserts the text of a specific sales order item."/>
           <PropertyValue Property="LongDescription" String="Inserts the text data for a specific item. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order header for a specific item."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order header data for a specific item. Consumers must pass the following key fields: sales order ID and item number."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderItemPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads the item partners for all sales orders."/>
      <PropertyValue Property="LongDescription" String="Reads the partner data from the items of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads the item partners of a specific item and with a specific partner function in a specific sales order."/>
        <PropertyValue Property="LongDescription" String="Reads the item partners with a specific partner function of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, and partner function."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Inserts the item partners of a specific item and with a specific partner function in a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Inserts the item partners with a specific partner function of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, and partner function."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates the item partners of a specific item and with a specific partner function in a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Updates the item partners with a specific partner function of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, and partner function."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes the item partners of a specific item and with a specific partner function in a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Deletes the item partners with a specific partner function of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, and partner function."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order header for a specific partner function of a sales order item."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order header data for a specific item partner function. Consumers must pass the following key fields: sales order ID, item number, and partner function."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrderItem"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order item for a specific partner function of a sales order item."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order item data for a specific item partner function. Consumers must pass the following key fields: sales order ID, item number, and partner function."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderItemPrElement" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads the item pricing elements of all sales orders."/>
      <PropertyValue Property="LongDescription" String="Reads the pricing element data from the items of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads the item pricing element of a specific item and with specific pricing details in a specific sales order."/>
        <PropertyValue Property="LongDescription" String="Reads an item pricing element of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, pricing procedure step, and pricing procedure counter."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Inserts an item pricing element."/>
      <PropertyValue Property="LongDescription" String="Inserts an item pricing element of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, pricing procedure step, and pricing procedure counter."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates an item pricing element."/>
      <PropertyValue Property="LongDescription" String="Updates an item pricing element of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, pricing procedure step, and pricing procedure counter."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes an item pricing element."/>
      <PropertyValue Property="LongDescription" String="Deletes an item pricing element of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, pricing procedure step, and pricing procedure counter."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order header for a specific pricing element."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order header data for a specific pricing element of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, pricing procedure step, and pricing procedure counter."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrderItem"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order item for a specific pricing element."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order item data for a specific pricing element of a specific sales order item. Consumers must pass the following key fields: sales order ID, item number, pricing procedure step, and pricing procedure counter."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderItemText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads item texts of all sales orders."/>
      <PropertyValue Property="LongDescription" String="Reads the text data from the items of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads a specific item text."/>
        <PropertyValue Property="LongDescription" String="Reads a specific item text in a specific language. Consumers must pass the following key fields: sales order ID, item number, language, and text ID."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Inserts a specific item text."/>
      <PropertyValue Property="LongDescription" String="Inserts a specific item text in a specific language. Consumers must pass the following key fields: sales order ID, item number, language, and text ID."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates a specific item text."/>
      <PropertyValue Property="LongDescription" String="Updates a specific item text in a specific language. Consumers must pass the following key fields: sales order ID, sales order item number, language, and text ID."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes a specific item text."/>
      <PropertyValue Property="LongDescription" String="Deletes a specific item text in a specific language. Consumers must pass the following key fields: sales order ID, item number, language, and text ID."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order header for a specific text of a sales order item."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order header data for a specific text of a specific sales order item in a specific language. Consumers must pass the following key fields: sales order ID, item number, language, and text ID."/>
          </Record>
         </PropertyValue>
        </Record>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrderItem"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order item for a specific item text."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order item data for a specific text in a specific language. Consumers must pass the following key fields: sales order ID, item number, language, and text ID."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderScheduleLine" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads the schedule lines of all sales orders."/>
      <PropertyValue Property="LongDescription" String="Reads the schedule line data from the items of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads a specific schedule line."/>
        <PropertyValue Property="LongDescription" String="Reads the schedule line data from a specific item of a specific sales order. Consumers must pass the following key fields: sales order ID, sales order item, and schedule line number."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Creates a schedule line."/>
      <PropertyValue Property="LongDescription" String="Creates the schedule line data for a specific item of a specific sales order. Consumers must pass the following key fields: sales order ID, sales order item."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates a specific schedule line."/>
      <PropertyValue Property="LongDescription" String="Updates the schedule line data from a specific item of a specific sales order. Consumers must pass the following key fields: sales order ID, sales order item, and schedule line number."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes a specific schedule line."/>
      <PropertyValue Property="LongDescription" String="Deletes the schedule line data from a specific item of a specific sales order. Consumers must pass the following key fields: sales order ID, sales order item, and schedule line number."/>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SalesOrderText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads the header texts of all sales orders."/>
      <PropertyValue Property="LongDescription" String="Reads the text data from the headers of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads a specific header text for a specific sales order."/>
        <PropertyValue Property="LongDescription" String="Reads the text data from the header of a specific sales order. Consumers must pass the following key fields: sales order ID, language, and text ID."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.InsertRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Inserts a specific header text for a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Inserts the text data from the header of a specific sales order. Consumers must pass the following key fields: sales order ID, language, and text ID."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates a specific header text for a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Updates the text data from the header of a specific sales order. Consumers must pass the following key fields: sales order ID, language, and text ID."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes a specific header text for a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Deletes the text data from the header of a specific sales order. Consumers must pass the following key fields: sales order ID, language, and text ID."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order header for a specific header text."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order header data for a specific header text. Consumers must pass the following key fields: sales order ID, language, and text ID."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities/A_SlsOrdPaymentPlanItemDetails" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Capabilities.ReadRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Reads the payment plans of all sales orders."/>
      <PropertyValue Property="LongDescription" String="Reads the payment plan data from the header of all sales orders in the system."/>
      <PropertyValue Property="ReadByKeyRestrictions">
       <Record>
        <PropertyValue Property="Description" String="Reads a specific payment plan item of a specific sales order."/>
        <PropertyValue Property="LongDescription" String="Reads the payment plan data from the header of a specific sales order."/>
       </Record>
      </PropertyValue>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.UpdateRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Updates a specific payment plan item of a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Updates the payment plan data from the header of a specific sales order."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.DeleteRestrictions">
     <Record>
      <PropertyValue Property="Description" String="Deletes a specific payment plan item of a specific sales order."/>
      <PropertyValue Property="LongDescription" String="Deletes the payment plan data from the header of a specific sales order."/>
     </Record>
    </Annotation>
    <Annotation Term="Capabilities.NavigationRestrictions">
     <Record>
      <PropertyValue Property="RestrictedProperties">
       <Collection>
        <Record>
         <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesOrder"/>
         <PropertyValue Property="ReadRestrictions">
          <Record>
           <PropertyValue Property="Description" String="Reads the sales order header for a specific payment plan item."/>
           <PropertyValue Property="LongDescription" String="Reads the sales order header data for a specific payment plan item. Consumers must pass the following key fields: sales order ID and payment plan item ID."/>
          </Record>
         </PropertyValue>
        </Record>
       </Collection>
      </PropertyValue>
     </Record>
    </Annotation>
   </Annotations>
   <Annotations Target="API_SALES_ORDER_SRV.API_SALES_ORDER_SRV_Entities" xmlns="http://docs.oasis-open.org/odata/ns/edm">
    <Annotation Term="Org.OData.Capabilities.V1.BatchSupport">
     <Record Type="Org.OData.Capabilities.V1.BatchSupportType">
      <PropertyValue Property="ReferencesAcrossChangeSetsSupported" Bool="true"/>
     </Record>
    </Annotation>
   </Annotations>
   <atom:link rel="self" href="https://host:port/sap/opu/odata/sap/API_SALES_ORDER_SRV/$metadata" xmlns:atom="http://www.w3.org/2005/Atom"/>
   <atom:link rel="latest-version" href="https://host:port/sap/opu/odata/sap/API_SALES_ORDER_SRV/$metadata" xmlns:atom="http://www.w3.org/2005/Atom"/>
  </Schema>
 </edmx:DataServices>
</edmx:Edmx>
