SalesOrderSimulation (SAP Cloud SDK - Parent POM 3.17.1 API)

java.lang.Object
- com.sap.cloud.sdk.datamodel.odata.helper.VdmObject<EntityT>
- - com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity<SalesOrderSimulation>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.salesordersimulate.SalesOrderSimulation

```
public class SalesOrderSimulation
extends VdmEntity<SalesOrderSimulation>
```
Sales Order Simulation (API)

Original entity name from the Odata EDM: A_SalesOrderSimulationType

Nested Class Summary

Nested Classes
Modifier and Type	Class and Description
`static class`	`SalesOrderSimulation.SalesOrderSimulationBuilder` Helper class to allow for fluent creation of SalesOrderSimulation instances.

Field Summary

Fields
Modifier and Type	Field and Description
`static SalesOrderSimulationSelectable`	`ALL_FIELDS` Selector for all available fields of SalesOrderSimulation.
`static SalesOrderSimulationField<Boolean>`	`COMPLETE_DELIVERY_IS_DEFINED` Use with available fluent helpers to apply the CompleteDeliveryIsDefined field to query operations.
`static SalesOrderSimulationField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static SalesOrderSimulationField<LocalDateTime>`	`CUSTOMER_PURCHASE_ORDER_DATE` Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
`static SalesOrderSimulationField<String>`	`CUSTOMER_PURCHASE_ORDER_TYPE` Use with available fluent helpers to apply the CustomerPurchaseOrderType field to query operations.
`static SalesOrderSimulationField<String>`	`DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the DistributionChannel field to query operations.
`static SalesOrderSimulationField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static SalesOrderSimulationField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static SalesOrderSimulationField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static SalesOrderSimulationField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static SalesOrderSimulationField<String>`	`INCOTERMS_VERSION` Use with available fluent helpers to apply the IncotermsVersion field to query operations.
`static SalesOrderSimulationField<String>`	`ORGANIZATION_DIVISION` Use with available fluent helpers to apply the OrganizationDivision field to query operations.
`static SalesOrderSimulationField<String>`	`PAYMENT_METHOD` Use with available fluent helpers to apply the PaymentMethod field to query operations.
`static SalesOrderSimulationField<LocalDateTime>`	`PRICING_DATE` Use with available fluent helpers to apply the PricingDate field to query operations.
`static SalesOrderSimulationField<String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static SalesOrderSimulationField<LocalDateTime>`	`REQUESTED_DELIVERY_DATE` Use with available fluent helpers to apply the RequestedDeliveryDate field to query operations.
`static SalesOrderSimulationField<String>`	`SALES_DISTRICT` Use with available fluent helpers to apply the SalesDistrict field to query operations.
`static SalesOrderSimulationField<String>`	`SALES_GROUP` Use with available fluent helpers to apply the SalesGroup field to query operations.
`static SalesOrderSimulationField<String>`	`SALES_OFFICE` Use with available fluent helpers to apply the SalesOffice field to query operations.
`static SalesOrderSimulationField<String>`	`SALES_ORDER` Use with available fluent helpers to apply the SalesOrder field to query operations.
`static SalesOrderSimulationField<LocalDateTime>`	`SALES_ORDER_DATE` Use with available fluent helpers to apply the SalesOrderDate field to query operations.
`static SalesOrderSimulationField<String>`	`SALES_ORDER_TYPE` Use with available fluent helpers to apply the SalesOrderType field to query operations.
`static SalesOrderSimulationField<String>`	`SALES_ORGANIZATION` Use with available fluent helpers to apply the SalesOrganization field to query operations.
`static SalesOrderSimulationField<String>`	`SD_DOCUMENT_REASON` Use with available fluent helpers to apply the SDDocumentReason field to query operations.
`static SalesOrderSimulationField<String>`	`SHIPPING_CONDITION` Use with available fluent helpers to apply the ShippingCondition field to query operations.
`static SalesOrderSimulationField<String>`	`SHIPPING_TYPE` Use with available fluent helpers to apply the ShippingType field to query operations.
`static SalesOrderSimulationField<String>`	`SOLD_TO_PARTY` Use with available fluent helpers to apply the SoldToParty field to query operations.
`static SalesOrderSimulationOneToOneLink<SalesOrderCreditSimulation>`	`TO_CREDIT` Use with available fluent helpers to apply the to_Credit navigation property to query operations.
`static SalesOrderSimulationLink<SalesOrderItemSimulation>`	`TO_ITEM` Use with available fluent helpers to apply the to_Item navigation property to query operations.
`static SalesOrderSimulationLink<SalesOrderPartnerSimulation>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static SalesOrderSimulationOneToOneLink<SalesOrderPricingSimulation>`	`TO_PRICING` Use with available fluent helpers to apply the to_Pricing navigation property to query operations.
`static SalesOrderSimulationLink<SalesOrderPrcgElmntSimln>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static SalesOrderSimulationField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
changedOriginalFields

Constructor Summary

Constructors
Constructor and Description
`SalesOrderSimulation()`
SalesOrderSimulation(String salesOrder, String salesOrderType, String salesOrganization, String distributionChannel, String organizationDivision, String salesGroup, String salesOffice, String salesDistrict, String soldToParty, String purchaseOrderByCustomer, String customerPurchaseOrderType, LocalDateTime customerPurchaseOrderDate, LocalDateTime salesOrderDate, String transactionCurrency, String sDDocumentReason, LocalDateTime pricingDate, LocalDateTime requestedDeliveryDate, String shippingCondition, Boolean completeDeliveryIsDefined, String shippingType, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String incotermsVersion, String customerPaymentTerms, String paymentMethod, SalesOrderCreditSimulation toCredit, List<SalesOrderItemSimulation> toItem, List<SalesOrderPartnerSimulation> toPartner, SalesOrderPricingSimulation toPricing, List<SalesOrderPrcgElmntSimln> toPricingElement)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addItem(SalesOrderItemSimulation... entity)` Adds elements to the list of associated SalesOrderItemSimulation entities.
`void`	`addPartner(SalesOrderPartnerSimulation... entity)` Adds elements to the list of associated SalesOrderPartnerSimulation entities.
`void`	`addPricingElement(SalesOrderPrcgElmntSimln... entity)` Adds elements to the list of associated SalesOrderPrcgElmntSimln entities.
`void`	`attachToService(String servicePath, HttpDestinationProperties destination)` Sets the service path and destination for the fetch commands of this entity.
`static SalesOrderSimulation.SalesOrderSimulationBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`SalesOrderCreditSimulation`	`fetchCredit()` Fetches the SalesOrderCreditSimulation entity (one to one) associated with this entity.
`List<SalesOrderItemSimulation>`	`fetchItem()` Fetches the SalesOrderItemSimulation entities (one to many) associated with this entity.
`List<SalesOrderPartnerSimulation>`	`fetchPartner()` Fetches the SalesOrderPartnerSimulation entities (one to many) associated with this entity.
`SalesOrderPricingSimulation`	`fetchPricing()` Fetches the SalesOrderPricingSimulation entity (one to one) associated with this entity.
`List<SalesOrderPrcgElmntSimln>`	`fetchPricingElement()` Fetches the SalesOrderPrcgElmntSimln entities (one to many) associated with this entity.
`static <T> SalesOrderSimulationField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> SalesOrderSimulationField<T>`	`field(String fieldName, TypeConverter<T,DomainT> typeConverter)` Use with available fluent helpers to apply an extension field to query operations.
`protected void`	`fromMap(Map<String,Object> inputValues)`
`Boolean`	`getCompleteDeliveryIsDefined()` Constraints: none
`io.vavr.control.Option<SalesOrderCreditSimulation>`	`getCreditIfPresent()` Retrieval of associated SalesOrderCreditSimulation entity (one to one).
`SalesOrderCreditSimulation`	`getCreditOrFetch()` Retrieval of associated SalesOrderCreditSimulation entity (one to one).
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4
`LocalDateTime`	`getCustomerPurchaseOrderDate()` Constraints: Not nullable, Precision: 0
`String`	`getCustomerPurchaseOrderType()` Constraints: Not nullable, Maximum length: 4
`protected String`	`getDefaultServicePath()` Used by fluent helpers and navigation property methods to construct OData queries.
`HttpDestinationProperties`	`getDestinationForFetch()` Convienence field for reusing the same destination with multiple queries (e.g.
`String`	`getDistributionChannel()` Constraints: Not nullable, Maximum length: 2
`protected String`	`getEntityCollection()` Used by fluent helpers and navigation property methods to construct OData queries.
`String`	`getIncotermsClassification()` Constraints: Not nullable, Maximum length: 3
`String`	`getIncotermsLocation1()` Constraints: Not nullable, Maximum length: 70
`String`	`getIncotermsLocation2()` Constraints: Not nullable, Maximum length: 70
`String`	`getIncotermsTransferLocation()` Constraints: Not nullable, Maximum length: 28
`String`	`getIncotermsVersion()` Constraints: Not nullable, Maximum length: 4
`io.vavr.control.Option<List<SalesOrderItemSimulation>>`	`getItemIfPresent()` Retrieval of associated SalesOrderItemSimulation entities (one to many).
`List<SalesOrderItemSimulation>`	`getItemOrFetch()` Retrieval of associated SalesOrderItemSimulation entities (one to many).
`protected Map<String,Object>`	`getKey()`
`String`	`getOrganizationDivision()` Constraints: Not nullable, Maximum length: 2
`io.vavr.control.Option<List<SalesOrderPartnerSimulation>>`	`getPartnerIfPresent()` Retrieval of associated SalesOrderPartnerSimulation entities (one to many).
`List<SalesOrderPartnerSimulation>`	`getPartnerOrFetch()` Retrieval of associated SalesOrderPartnerSimulation entities (one to many).
`String`	`getPaymentMethod()` Constraints: Not nullable, Maximum length: 1
`LocalDateTime`	`getPricingDate()` Constraints: Not nullable, Precision: 0
`io.vavr.control.Option<List<SalesOrderPrcgElmntSimln>>`	`getPricingElementIfPresent()` Retrieval of associated SalesOrderPrcgElmntSimln entities (one to many).
`List<SalesOrderPrcgElmntSimln>`	`getPricingElementOrFetch()` Retrieval of associated SalesOrderPrcgElmntSimln entities (one to many).
`io.vavr.control.Option<SalesOrderPricingSimulation>`	`getPricingIfPresent()` Retrieval of associated SalesOrderPricingSimulation entity (one to one).
`SalesOrderPricingSimulation`	`getPricingOrFetch()` Retrieval of associated SalesOrderPricingSimulation entity (one to one).
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35
`LocalDateTime`	`getRequestedDeliveryDate()` Constraints: Not nullable, Precision: 0
`String`	`getSalesDistrict()` Constraints: Not nullable, Maximum length: 6
`String`	`getSalesGroup()` Constraints: Not nullable, Maximum length: 3
`String`	`getSalesOffice()` Constraints: Not nullable, Maximum length: 4
`String`	`getSalesOrder()` (Key Field) Constraints: Not nullable, Maximum length: 10
`LocalDateTime`	`getSalesOrderDate()` Constraints: Not nullable, Precision: 0
`String`	`getSalesOrderType()` Constraints: Not nullable, Maximum length: 4
`String`	`getSalesOrganization()` Constraints: Not nullable, Maximum length: 4
`String`	`getSDDocumentReason()` Constraints: Not nullable, Maximum length: 3
`String`	`getShippingCondition()` Constraints: Not nullable, Maximum length: 2
`String`	`getShippingType()` Constraints: Not nullable, Maximum length: 2
`String`	`getSoldToParty()` Constraints: Not nullable, Maximum length: 10
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5
`Class<SalesOrderSimulation>`	`getType()`
`int`	`hashCode()`
`void`	`setCompleteDeliveryIsDefined(Boolean completeDeliveryIsDefined)` Constraints: none
`void`	`setCredit(SalesOrderCreditSimulation value)` Overwrites the associated SalesOrderCreditSimulation entity for the loaded navigation property to_Credit.
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`void`	`setCustomerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)` Constraints: Not nullable, Precision: 0
`void`	`setCustomerPurchaseOrderType(String customerPurchaseOrderType)` Constraints: Not nullable, Maximum length: 4
`void`	`setDistributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2
`void`	`setIncotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3
`void`	`setIncotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70
`void`	`setIncotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70
`void`	`setIncotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28
`void`	`setIncotermsVersion(String incotermsVersion)` Constraints: Not nullable, Maximum length: 4
`void`	`setItem(List<SalesOrderItemSimulation> value)` Overwrites the list of associated SalesOrderItemSimulation entities for the loaded navigation property to_Item.
`void`	`setOrganizationDivision(String organizationDivision)` Constraints: Not nullable, Maximum length: 2
`void`	`setPartner(List<SalesOrderPartnerSimulation> value)` Overwrites the list of associated SalesOrderPartnerSimulation entities for the loaded navigation property to_Partner.
`void`	`setPaymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1
`void`	`setPricing(SalesOrderPricingSimulation value)` Overwrites the associated SalesOrderPricingSimulation entity for the loaded navigation property to_Pricing.
`void`	`setPricingDate(LocalDateTime pricingDate)` Constraints: Not nullable, Precision: 0
`void`	`setPricingElement(List<SalesOrderPrcgElmntSimln> value)` Overwrites the list of associated SalesOrderPrcgElmntSimln entities for the loaded navigation property to_PricingElement.
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`void`	`setRequestedDeliveryDate(LocalDateTime requestedDeliveryDate)` Constraints: Not nullable, Precision: 0
`void`	`setSalesDistrict(String salesDistrict)` Constraints: Not nullable, Maximum length: 6
`void`	`setSalesGroup(String salesGroup)` Constraints: Not nullable, Maximum length: 3
`void`	`setSalesOffice(String salesOffice)` Constraints: Not nullable, Maximum length: 4
`void`	`setSalesOrder(String salesOrder)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setSalesOrderDate(LocalDateTime salesOrderDate)` Constraints: Not nullable, Precision: 0
`void`	`setSalesOrderType(String salesOrderType)` Constraints: Not nullable, Maximum length: 4
`void`	`setSalesOrganization(String salesOrganization)` Constraints: Not nullable, Maximum length: 4
`void`	`setSDDocumentReason(String sDDocumentReason)` Constraints: Not nullable, Maximum length: 3
`protected void`	`setServicePathForFetch(String servicePathForFetch)` The service path only used for the fetch commands of this entity.
`void`	`setShippingCondition(String shippingCondition)` Constraints: Not nullable, Maximum length: 2
`void`	`setShippingType(String shippingType)` Constraints: Not nullable, Maximum length: 2
`void`	`setSoldToParty(String soldToParty)` Constraints: Not nullable, Maximum length: 10
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5
`protected Map<String,Object>`	`toMapOfFields()`
`protected Map<String,Object>`	`toMapOfNavigationProperties()`
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields

Methods inherited from class java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, wait

- Field Detail
  - ALL_FIELDS
```
public static final SalesOrderSimulationSelectable ALL_FIELDS
```
    Selector for all available fields of SalesOrderSimulation.
  - SALES_ORDER
```
public static final SalesOrderSimulationField<String> SALES_ORDER
```
    Use with available fluent helpers to apply the SalesOrder field to query operations.
  - SALES_ORDER_TYPE
```
public static final SalesOrderSimulationField<String> SALES_ORDER_TYPE
```
    Use with available fluent helpers to apply the SalesOrderType field to query operations.
  - SALES_ORGANIZATION
```
public static final SalesOrderSimulationField<String> SALES_ORGANIZATION
```
    Use with available fluent helpers to apply the SalesOrganization field to query operations.
  - DISTRIBUTION_CHANNEL
```
public static final SalesOrderSimulationField<String> DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the DistributionChannel field to query operations.
  - ORGANIZATION_DIVISION
```
public static final SalesOrderSimulationField<String> ORGANIZATION_DIVISION
```
    Use with available fluent helpers to apply the OrganizationDivision field to query operations.
  - SALES_GROUP
```
public static final SalesOrderSimulationField<String> SALES_GROUP
```
    Use with available fluent helpers to apply the SalesGroup field to query operations.
  - SALES_OFFICE
```
public static final SalesOrderSimulationField<String> SALES_OFFICE
```
    Use with available fluent helpers to apply the SalesOffice field to query operations.
  - SALES_DISTRICT
```
public static final SalesOrderSimulationField<String> SALES_DISTRICT
```
    Use with available fluent helpers to apply the SalesDistrict field to query operations.
  - SOLD_TO_PARTY
```
public static final SalesOrderSimulationField<String> SOLD_TO_PARTY
```
    Use with available fluent helpers to apply the SoldToParty field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final SalesOrderSimulationField<String> PURCHASE_ORDER_BY_CUSTOMER
```
    Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
  - CUSTOMER_PURCHASE_ORDER_TYPE
```
public static final SalesOrderSimulationField<String> CUSTOMER_PURCHASE_ORDER_TYPE
```
    Use with available fluent helpers to apply the CustomerPurchaseOrderType field to query operations.
  - CUSTOMER_PURCHASE_ORDER_DATE
```
public static final SalesOrderSimulationField<LocalDateTime> CUSTOMER_PURCHASE_ORDER_DATE
```
    Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
  - SALES_ORDER_DATE
```
public static final SalesOrderSimulationField<LocalDateTime> SALES_ORDER_DATE
```
    Use with available fluent helpers to apply the SalesOrderDate field to query operations.
  - TRANSACTION_CURRENCY
```
public static final SalesOrderSimulationField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - SD_DOCUMENT_REASON
```
public static final SalesOrderSimulationField<String> SD_DOCUMENT_REASON
```
    Use with available fluent helpers to apply the SDDocumentReason field to query operations.
  - PRICING_DATE
```
public static final SalesOrderSimulationField<LocalDateTime> PRICING_DATE
```
    Use with available fluent helpers to apply the PricingDate field to query operations.
  - REQUESTED_DELIVERY_DATE
```
public static final SalesOrderSimulationField<LocalDateTime> REQUESTED_DELIVERY_DATE
```
    Use with available fluent helpers to apply the RequestedDeliveryDate field to query operations.
  - SHIPPING_CONDITION
```
public static final SalesOrderSimulationField<String> SHIPPING_CONDITION
```
    Use with available fluent helpers to apply the ShippingCondition field to query operations.
  - COMPLETE_DELIVERY_IS_DEFINED
```
public static final SalesOrderSimulationField<Boolean> COMPLETE_DELIVERY_IS_DEFINED
```
    Use with available fluent helpers to apply the CompleteDeliveryIsDefined field to query operations.
  - SHIPPING_TYPE
```
public static final SalesOrderSimulationField<String> SHIPPING_TYPE
```
    Use with available fluent helpers to apply the ShippingType field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final SalesOrderSimulationField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final SalesOrderSimulationField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final SalesOrderSimulationField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final SalesOrderSimulationField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - INCOTERMS_VERSION
```
public static final SalesOrderSimulationField<String> INCOTERMS_VERSION
```
    Use with available fluent helpers to apply the IncotermsVersion field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final SalesOrderSimulationField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - PAYMENT_METHOD
```
public static final SalesOrderSimulationField<String> PAYMENT_METHOD
```
    Use with available fluent helpers to apply the PaymentMethod field to query operations.
  - TO_CREDIT
```
public static final SalesOrderSimulationOneToOneLink<SalesOrderCreditSimulation> TO_CREDIT
```
    Use with available fluent helpers to apply the to_Credit navigation property to query operations.
  - TO_ITEM
```
public static final SalesOrderSimulationLink<SalesOrderItemSimulation> TO_ITEM
```
    Use with available fluent helpers to apply the to_Item navigation property to query operations.
  - TO_PARTNER
```
public static final SalesOrderSimulationLink<SalesOrderPartnerSimulation> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PRICING
```
public static final SalesOrderSimulationOneToOneLink<SalesOrderPricingSimulation> TO_PRICING
```
    Use with available fluent helpers to apply the to_Pricing navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final SalesOrderSimulationLink<SalesOrderPrcgElmntSimln> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
- Constructor Detail
  - SalesOrderSimulation
```
public SalesOrderSimulation()
```
  - SalesOrderSimulation
```
public SalesOrderSimulation(@Nullable
                            String salesOrder,
                            @Nullable
                            String salesOrderType,
                            @Nullable
                            String salesOrganization,
                            @Nullable
                            String distributionChannel,
                            @Nullable
                            String organizationDivision,
                            @Nullable
                            String salesGroup,
                            @Nullable
                            String salesOffice,
                            @Nullable
                            String salesDistrict,
                            @Nullable
                            String soldToParty,
                            @Nullable
                            String purchaseOrderByCustomer,
                            @Nullable
                            String customerPurchaseOrderType,
                            @Nullable
                            LocalDateTime customerPurchaseOrderDate,
                            @Nullable
                            LocalDateTime salesOrderDate,
                            @Nullable
                            String transactionCurrency,
                            @Nullable
                            String sDDocumentReason,
                            @Nullable
                            LocalDateTime pricingDate,
                            @Nullable
                            LocalDateTime requestedDeliveryDate,
                            @Nullable
                            String shippingCondition,
                            @Nullable
                            Boolean completeDeliveryIsDefined,
                            @Nullable
                            String shippingType,
                            @Nullable
                            String incotermsClassification,
                            @Nullable
                            String incotermsTransferLocation,
                            @Nullable
                            String incotermsLocation1,
                            @Nullable
                            String incotermsLocation2,
                            @Nullable
                            String incotermsVersion,
                            @Nullable
                            String customerPaymentTerms,
                            @Nullable
                            String paymentMethod,
                            @Nullable
                            SalesOrderCreditSimulation toCredit,
                            List<SalesOrderItemSimulation> toItem,
                            List<SalesOrderPartnerSimulation> toPartner,
                            @Nullable
                            SalesOrderPricingSimulation toPricing,
                            List<SalesOrderPrcgElmntSimln> toPricingElement)
```
- Method Detail
  - getType
```
@Nonnull
public Class<SalesOrderSimulation> getType()
```
    Specified by:
    
    getType in class VdmObject<SalesOrderSimulation>
    
    Returns:
    
    The class of this object.
  - setSalesOrder
```
public void setSalesOrder(@Nullable
                          String salesOrder)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesOrder
    
    Parameters:
    
    salesOrder - Sales Order
  - setSalesOrderType
```
public void setSalesOrderType(@Nullable
                              String salesOrderType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrderType
    
    Parameters:
    
    salesOrderType - Sales Order Type
  - setSalesOrganization
```
public void setSalesOrganization(@Nullable
                                 String salesOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrganization
    
    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.
    
    Parameters:
    
    salesOrganization - 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.
  - setDistributionChannel
```
public void setDistributionChannel(@Nullable
                                   String distributionChannel)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DistributionChannel
    
    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.
    
    Parameters:
    
    distributionChannel - The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.
  - setOrganizationDivision
```
public void setOrganizationDivision(@Nullable
                                    String organizationDivision)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: OrganizationDivision
    
    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.
    
    Parameters:
    
    organizationDivision - 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.
  - setSalesGroup
```
public void setSalesGroup(@Nullable
                          String salesGroup)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SalesGroup
    
    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.
    
    Parameters:
    
    salesGroup - A group of sales people who are responsible for processing sales of certain products or services.
  - setSalesOffice
```
public void setSalesOffice(@Nullable
                           String salesOffice)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOffice
    
    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.
    
    Parameters:
    
    salesOffice - A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.
  - setSalesDistrict
```
public void setSalesDistrict(@Nullable
                             String salesDistrict)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesDistrict
    
    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.
    
    Parameters:
    
    salesDistrict - A geographical sales district or region.
  - setSoldToParty
```
public void setSoldToParty(@Nullable
                           String soldToParty)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SoldToParty
    
    Parameters:
    
    soldToParty - The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders.
  - setPurchaseOrderByCustomer
```
public void setPurchaseOrderByCustomer(@Nullable
                                       String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    
    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).
    
    Parameters:
    
    purchaseOrderByCustomer - Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).
  - setCustomerPurchaseOrderType
```
public void setCustomerPurchaseOrderType(@Nullable
                                         String customerPurchaseOrderType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPurchaseOrderType
    
    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.
    
    Parameters:
    
    customerPurchaseOrderType - The way in which the sales document (the inquiry or sales order, for example) arrives from the customer.
  - setCustomerPurchaseOrderDate
```
public void setCustomerPurchaseOrderDate(@Nullable
                                         LocalDateTime customerPurchaseOrderDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CustomerPurchaseOrderDate
    
    Parameters:
    
    customerPurchaseOrderDate - 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.
  - setSalesOrderDate
```
public void setSalesOrderDate(@Nullable
                              LocalDateTime salesOrderDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesOrderDate
    
    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.
    
    Parameters:
    
    salesOrderDate - The date on which you want the sales document (the sales order, for example) to become effective for sales management purposes.
  - setTransactionCurrency
```
public void setTransactionCurrency(@Nullable
                                   String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: TransactionCurrency
    
    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.
    
    Parameters:
    
    transactionCurrency - The currency that applies to the document (for example, to a sales order or an invoice).
  - setSDDocumentReason
```
public void setSDDocumentReason(@Nullable
                                String sDDocumentReason)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SDDocumentReason
    
    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.
    
    Parameters:
    
    sDDocumentReason - Indicates the reason for creating the sales document.
  - setPricingDate
```
public void setPricingDate(@Nullable
                           LocalDateTime pricingDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PricingDate
    
    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.
    
    Parameters:
    
    pricingDate - The date that determines date-related pricing elements, such as conditions and foreign exchange rate.
  - setRequestedDeliveryDate
```
public void setRequestedDeliveryDate(@Nullable
                                     LocalDateTime requestedDeliveryDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: RequestedDeliveryDate
    
    As a rule, the system suggests the current date. However, if you change the requested delivery date in the header (for example, to a future date), and then create a new item, the system proposes the new date for any schedule lines you create. If you change the date of an existing schedule line, the system advises you that it will only apply the new date to further schedule lines you create and will not change the dates of other existing schedule lines.
    
    Parameters:
    
    requestedDeliveryDate - The date that the system automatically suggests as the delivery date for schedule lines when you create further items in the sales document.
  - setShippingCondition
```
public void setShippingCondition(@Nullable
                                 String shippingCondition)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingCondition
    
    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.
    
    Parameters:
    
    shippingCondition - General shipping strategy for the delivery of goods from the vendor to the customer.
  - setCompleteDeliveryIsDefined
```
public void setCompleteDeliveryIsDefined(@Nullable
                                         Boolean completeDeliveryIsDefined)
```
    Constraints: none
    Original property name from the Odata EDM: CompleteDeliveryIsDefined
    
    Parameters:
    
    completeDeliveryIsDefined - 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.
  - setShippingType
```
public void setShippingType(@Nullable
                            String shippingType)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingType
    
    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
    
    Parameters:
    
    shippingType - Shipping type (for example, by road or rail) that has been selected for the transportation of the goods for the shipment legs.
  - setIncotermsClassification
```
public void setIncotermsClassification(@Nullable
                                       String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    
    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.
    
    Parameters:
    
    incotermsClassification - Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - setIncotermsTransferLocation
```
public void setIncotermsTransferLocation(@Nullable
                                         String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    
    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").
    
    Parameters:
    
    incotermsTransferLocation - Additional information for the primary Incoterm.
  - setIncotermsLocation1
```
public void setIncotermsLocation1(@Nullable
                                  String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    
    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 & 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 & Freight Port of DestinationCIF Cost Insurance & 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.
    
    Parameters:
    
    incotermsLocation1 - Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - setIncotermsLocation2
```
public void setIncotermsLocation2(@Nullable
                                  String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    
    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 -> Business Partners -> Customers -> Billing Document -> Incoterms -> 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 & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Parameters:
    
    incotermsLocation2 - 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:
  - setIncotermsVersion
```
public void setIncotermsVersion(@Nullable
                                String incotermsVersion)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: IncotermsVersion
    
    Parameters:
    
    incotermsVersion - An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC).
  - setCustomerPaymentTerms
```
public void setCustomerPaymentTerms(@Nullable
                                    String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    
    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.
    
    Parameters:
    
    customerPaymentTerms - Key for defining payment terms composed of cash discount percentages and payment periods.
  - setPaymentMethod
```
public void setPaymentMethod(@Nullable
                             String paymentMethod)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentMethod
    
    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.
    
    Parameters:
    
    paymentMethod - Payment method with which this item is to be paid.
  - getEntityCollection
```
protected String getEntityCollection()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Specified by:
    
    getEntityCollection in class VdmEntity<SalesOrderSimulation>
    
    Returns:
    
    EDMX name of the entity collection identifier.
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<SalesOrderSimulation>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<SalesOrderSimulation>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<SalesOrderSimulation>
  - field
```
@Nonnull
public static <T> SalesOrderSimulationField<T> field(@Nonnull
                                                              String fieldName,
                                                              @Nonnull
                                                              Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    Parameters:
    
    fieldName - The name of the extension field as returned by the OData service.
    
    fieldType - The Java type to use for the extension field when performing value comparisons.
    
    Returns:
    
    A representation of an extension field from this entity.
  - field
```
@Nonnull
public static <T,DomainT> SalesOrderSimulationField<T> field(@Nonnull
                                                                      String fieldName,
                                                                      @Nonnull
                                                                      TypeConverter<T,DomainT> typeConverter)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    DomainT - The type of the extension field as returned by the OData service.
    
    Parameters:
    
    typeConverter - A TypeConverter instance whose first generic type matches the Java type of the field
    
    fieldName - The name of the extension field as returned by the OData service.
    
    Returns:
    
    A representation of an extension field from this entity, holding a reference to the given TypeConverter.
  - getDestinationForFetch
```
@Nullable
public HttpDestinationProperties getDestinationForFetch()
```
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same destination with multiple queries (e.g. fetching associated entities). New destination to apply to this entity
    
    Overrides:
    
    getDestinationForFetch in class VdmEntity<SalesOrderSimulation>
    
    Returns:
    
    The stored destination for executing queries, or null if no such context has been set.
  - setServicePathForFetch
```
protected void setServicePathForFetch(@Nullable
                                      String servicePathForFetch)
```
    Description copied from class: VdmEntity
    
    The service path only used for the fetch commands of this entity.
    Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    setServicePathForFetch in class VdmEntity<SalesOrderSimulation>
  - attachToService
```
public void attachToService(@Nullable
                            String servicePath,
                            @Nonnull
                            HttpDestinationProperties destination)
```
    Description copied from class: VdmEntity
    
    Sets the service path and destination for the fetch commands of this entity. Also applies to any associated entities (navigation properties) that were previously fetched.
    Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    attachToService in class VdmEntity<SalesOrderSimulation>
    
    Parameters:
    
    servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were previously fetched. If a null value is provided and the service path has never been set, then the service path will be set to the default defined in the corresponding service interface.
    
    destination - New destination to apply to this entity and any associated entities that were previously fetched.
  - getDefaultServicePath
```
protected String getDefaultServicePath()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Overrides:
    
    getDefaultServicePath in class VdmEntity<SalesOrderSimulation>
    
    Returns:
    
    Default context path to the OData service. In other words, everything in between the protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)
  - toMapOfNavigationProperties
```
@Nonnull
protected Map<String,Object> toMapOfNavigationProperties()
```
    Overrides:
    
    toMapOfNavigationProperties in class VdmObject<SalesOrderSimulation>
  - fetchCredit
```
@Nullable
public SalesOrderCreditSimulation fetchCredit()
                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderCreditSimulation entity (one to one) associated with this entity. This corresponds to the OData navigation property to_Credit.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated SalesOrderCreditSimulation entity, or null if an entity is not associated.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getCreditOrFetch
```
@Nullable
public SalesOrderCreditSimulation getCreditOrFetch()
                                                      throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderCreditSimulation entity (one to one). This corresponds to the OData navigation property to_Credit.
    If the navigation property to_Credit of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated SalesOrderCreditSimulation entity.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getCreditIfPresent
```
@Nonnull
public io.vavr.control.Option<SalesOrderCreditSimulation> getCreditIfPresent()
```
    Retrieval of associated SalesOrderCreditSimulation entity (one to one). This corresponds to the OData navigation property to_Credit.
    If the navigation property for an entity SalesOrderSimulation has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Credit is already loaded, the result will contain the SalesOrderCreditSimulation entity. If not, an Option with result state empty is returned.
  - setCredit
```
public void setCredit(SalesOrderCreditSimulation value)
```
    Overwrites the associated SalesOrderCreditSimulation entity for the loaded navigation property to_Credit.
    
    Parameters:
    
    value - New SalesOrderCreditSimulation entity.
  - fetchItem
```
@Nonnull
public List<SalesOrderItemSimulation> fetchItem()
                                                  throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderItemSimulation entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Item.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SalesOrderItemSimulation entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getItemOrFetch
```
@Nonnull
public List<SalesOrderItemSimulation> getItemOrFetch()
                                                       throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderItemSimulation entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated SalesOrderItemSimulation entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getItemIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SalesOrderItemSimulation>> getItemIfPresent()
```
    Retrieval of associated SalesOrderItemSimulation entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property for an entity SalesOrderSimulation has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Item is already loaded, the result will contain the SalesOrderItemSimulation entities. If not, an Option with result state empty is returned.
  - setItem
```
public void setItem(@Nonnull
                    List<SalesOrderItemSimulation> value)
```
    Overwrites the list of associated SalesOrderItemSimulation entities for the loaded navigation property to_Item.
    If the navigation property to_Item of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of SalesOrderItemSimulation entities.
  - addItem
```
public void addItem(SalesOrderItemSimulation... entity)
```
    Adds elements to the list of associated SalesOrderItemSimulation entities. This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of SalesOrderItemSimulation entities.
  - fetchPartner
```
@Nonnull
public List<SalesOrderPartnerSimulation> fetchPartner()
                                                        throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderPartnerSimulation entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Partner.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SalesOrderPartnerSimulation entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPartnerOrFetch
```
@Nonnull
public List<SalesOrderPartnerSimulation> getPartnerOrFetch()
                                                             throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderPartnerSimulation entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated SalesOrderPartnerSimulation entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPartnerIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SalesOrderPartnerSimulation>> getPartnerIfPresent()
```
    Retrieval of associated SalesOrderPartnerSimulation entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property for an entity SalesOrderSimulation has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Partner is already loaded, the result will contain the SalesOrderPartnerSimulation entities. If not, an Option with result state empty is returned.
  - setPartner
```
public void setPartner(@Nonnull
                       List<SalesOrderPartnerSimulation> value)
```
    Overwrites the list of associated SalesOrderPartnerSimulation entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of SalesOrderPartnerSimulation entities.
  - addPartner
```
public void addPartner(SalesOrderPartnerSimulation... entity)
```
    Adds elements to the list of associated SalesOrderPartnerSimulation entities. This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of SalesOrderPartnerSimulation entities.
  - fetchPricing
```
@Nullable
public SalesOrderPricingSimulation fetchPricing()
                                                   throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderPricingSimulation entity (one to one) associated with this entity. This corresponds to the OData navigation property to_Pricing.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated SalesOrderPricingSimulation entity, or null if an entity is not associated.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPricingOrFetch
```
@Nullable
public SalesOrderPricingSimulation getPricingOrFetch()
                                                        throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderPricingSimulation entity (one to one). This corresponds to the OData navigation property to_Pricing.
    If the navigation property to_Pricing of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated SalesOrderPricingSimulation entity.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPricingIfPresent
```
@Nonnull
public io.vavr.control.Option<SalesOrderPricingSimulation> getPricingIfPresent()
```
    Retrieval of associated SalesOrderPricingSimulation entity (one to one). This corresponds to the OData navigation property to_Pricing.
    If the navigation property for an entity SalesOrderSimulation has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Pricing is already loaded, the result will contain the SalesOrderPricingSimulation entity. If not, an Option with result state empty is returned.
  - setPricing
```
public void setPricing(SalesOrderPricingSimulation value)
```
    Overwrites the associated SalesOrderPricingSimulation entity for the loaded navigation property to_Pricing.
    
    Parameters:
    
    value - New SalesOrderPricingSimulation entity.
  - fetchPricingElement
```
@Nonnull
public List<SalesOrderPrcgElmntSimln> fetchPricingElement()
                                                            throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderPrcgElmntSimln entities (one to many) associated with this entity. This corresponds to the OData navigation property to_PricingElement.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SalesOrderPrcgElmntSimln entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPricingElementOrFetch
```
@Nonnull
public List<SalesOrderPrcgElmntSimln> getPricingElementOrFetch()
                                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderPrcgElmntSimln entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated SalesOrderPrcgElmntSimln entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPricingElementIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SalesOrderPrcgElmntSimln>> getPricingElementIfPresent()
```
    Retrieval of associated SalesOrderPrcgElmntSimln entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property for an entity SalesOrderSimulation has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_PricingElement is already loaded, the result will contain the SalesOrderPrcgElmntSimln entities. If not, an Option with result state empty is returned.
  - setPricingElement
```
public void setPricingElement(@Nonnull
                              List<SalesOrderPrcgElmntSimln> value)
```
    Overwrites the list of associated SalesOrderPrcgElmntSimln entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of SalesOrderPrcgElmntSimln entities.
  - addPricingElement
```
public void addPricingElement(SalesOrderPrcgElmntSimln... entity)
```
    Adds elements to the list of associated SalesOrderPrcgElmntSimln entities. This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesOrderSimulation is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of SalesOrderPrcgElmntSimln entities.
  - builder
```
public static SalesOrderSimulation.SalesOrderSimulationBuilder builder()
```
  - getSalesOrder
```
@Nullable
public String getSalesOrder()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesOrder
    
    Returns:
    
    Sales Order
  - getSalesOrderType
```
@Nullable
public String getSalesOrderType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrderType
    
    Returns:
    
    Sales Order Type
  - getSalesOrganization
```
@Nullable
public String getSalesOrganization()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrganization
    
    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.
    
    Returns:
    
    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.
  - getDistributionChannel
```
@Nullable
public String getDistributionChannel()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DistributionChannel
    
    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.
    
    Returns:
    
    The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.
  - getOrganizationDivision
```
@Nullable
public String getOrganizationDivision()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: OrganizationDivision
    
    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.
    
    Returns:
    
    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.
  - getSalesGroup
```
@Nullable
public String getSalesGroup()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SalesGroup
    
    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.
    
    Returns:
    
    A group of sales people who are responsible for processing sales of certain products or services.
  - getSalesOffice
```
@Nullable
public String getSalesOffice()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOffice
    
    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.
    
    Returns:
    
    A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.
  - getSalesDistrict
```
@Nullable
public String getSalesDistrict()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesDistrict
    
    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.
    
    Returns:
    
    A geographical sales district or region.
  - getSoldToParty
```
@Nullable
public String getSoldToParty()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SoldToParty
    
    Returns:
    
    The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders.
  - getPurchaseOrderByCustomer
```
@Nullable
public String getPurchaseOrderByCustomer()
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    
    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).
    
    Returns:
    
    Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).
  - getCustomerPurchaseOrderType
```
@Nullable
public String getCustomerPurchaseOrderType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPurchaseOrderType
    
    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.
    
    Returns:
    
    The way in which the sales document (the inquiry or sales order, for example) arrives from the customer.
  - getCustomerPurchaseOrderDate
```
@Nullable
public LocalDateTime getCustomerPurchaseOrderDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CustomerPurchaseOrderDate
    
    Returns:
    
    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.
  - getSalesOrderDate
```
@Nullable
public LocalDateTime getSalesOrderDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesOrderDate
    
    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.
    
    Returns:
    
    The date on which you want the sales document (the sales order, for example) to become effective for sales management purposes.
  - getTransactionCurrency
```
@Nullable
public String getTransactionCurrency()
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: TransactionCurrency
    
    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.
    
    Returns:
    
    The currency that applies to the document (for example, to a sales order or an invoice).
  - getSDDocumentReason
```
@Nullable
public String getSDDocumentReason()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SDDocumentReason
    
    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.
    
    Returns:
    
    Indicates the reason for creating the sales document.
  - getPricingDate
```
@Nullable
public LocalDateTime getPricingDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PricingDate
    
    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.
    
    Returns:
    
    The date that determines date-related pricing elements, such as conditions and foreign exchange rate.
  - getRequestedDeliveryDate
```
@Nullable
public LocalDateTime getRequestedDeliveryDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: RequestedDeliveryDate
    
    As a rule, the system suggests the current date. However, if you change the requested delivery date in the header (for example, to a future date), and then create a new item, the system proposes the new date for any schedule lines you create. If you change the date of an existing schedule line, the system advises you that it will only apply the new date to further schedule lines you create and will not change the dates of other existing schedule lines.
    
    Returns:
    
    The date that the system automatically suggests as the delivery date for schedule lines when you create further items in the sales document.
  - getShippingCondition
```
@Nullable
public String getShippingCondition()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingCondition
    
    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.
    
    Returns:
    
    General shipping strategy for the delivery of goods from the vendor to the customer.
  - getCompleteDeliveryIsDefined
```
@Nullable
public Boolean getCompleteDeliveryIsDefined()
```
    Constraints: none
    Original property name from the Odata EDM: CompleteDeliveryIsDefined
    
    Returns:
    
    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.
  - getShippingType
```
@Nullable
public String getShippingType()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingType
    
    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
    
    Returns:
    
    Shipping type (for example, by road or rail) that has been selected for the transportation of the goods for the shipment legs.
  - getIncotermsClassification
```
@Nullable
public String getIncotermsClassification()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    
    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.
    
    Returns:
    
    Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - getIncotermsTransferLocation
```
@Nullable
public String getIncotermsTransferLocation()
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    
    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").
    
    Returns:
    
    Additional information for the primary Incoterm.
  - getIncotermsLocation1
```
@Nullable
public String getIncotermsLocation1()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    
    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 & 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 & Freight Port of DestinationCIF Cost Insurance & 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.
    
    Returns:
    
    Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - getIncotermsLocation2
```
@Nullable
public String getIncotermsLocation2()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    
    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 -> Business Partners -> Customers -> Billing Document -> Incoterms -> 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 & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Returns:
    
    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:
  - getIncotermsVersion
```
@Nullable
public String getIncotermsVersion()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: IncotermsVersion
    
    Returns:
    
    An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC).
  - getCustomerPaymentTerms
```
@Nullable
public String getCustomerPaymentTerms()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    
    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.
    
    Returns:
    
    Key for defining payment terms composed of cash discount percentages and payment periods.
  - getPaymentMethod
```
@Nullable
public String getPaymentMethod()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentMethod
    
    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.
    
    Returns:
    
    Payment method with which this item is to be paid.
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<SalesOrderSimulation>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<SalesOrderSimulation>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<SalesOrderSimulation>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<SalesOrderSimulation>

Class SalesOrderSimulation

Nested Class Summary

Field Summary

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Constructor Summary

Method Summary

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

SALES_ORDER

SALES_ORDER_TYPE

SALES_ORGANIZATION

DISTRIBUTION_CHANNEL

ORGANIZATION_DIVISION

SALES_GROUP

SALES_OFFICE

SALES_DISTRICT

SOLD_TO_PARTY

PURCHASE_ORDER_BY_CUSTOMER

CUSTOMER_PURCHASE_ORDER_TYPE

CUSTOMER_PURCHASE_ORDER_DATE

SALES_ORDER_DATE

TRANSACTION_CURRENCY

SD_DOCUMENT_REASON

PRICING_DATE

REQUESTED_DELIVERY_DATE

SHIPPING_CONDITION

COMPLETE_DELIVERY_IS_DEFINED

SHIPPING_TYPE

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

INCOTERMS_VERSION

CUSTOMER_PAYMENT_TERMS

PAYMENT_METHOD

TO_CREDIT

TO_ITEM

TO_PARTNER

TO_PRICING

TO_PRICING_ELEMENT

Constructor Detail

SalesOrderSimulation

SalesOrderSimulation

Method Detail

getType

setSalesOrder

setSalesOrderType

setSalesOrganization

setDistributionChannel

setOrganizationDivision

setSalesGroup

setSalesOffice

setSalesDistrict

setSoldToParty

setPurchaseOrderByCustomer

setCustomerPurchaseOrderType

setCustomerPurchaseOrderDate

setSalesOrderDate

setTransactionCurrency

setSDDocumentReason

setPricingDate

setRequestedDeliveryDate

setShippingCondition

setCompleteDeliveryIsDefined

setShippingType

setIncotermsClassification

setIncotermsTransferLocation

setIncotermsLocation1

setIncotermsLocation2

setIncotermsVersion

setCustomerPaymentTerms

setPaymentMethod

getEntityCollection

getKey

toMapOfFields

fromMap

field