SalesOrder (SAP Cloud SDK - Parent POM 3.39.0 API)

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

```
public class SalesOrder
extends VdmEntity<SalesOrder>
```
Sales Order Header

Original entity name from the Odata EDM: A_SalesOrderType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class SalesOrder.SalesOrderBuilder
Helper class to allow for fluent creation of SalesOrder instances.

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

Field Summary

Fields
Modifier and Type	Field and Description
`static SalesOrderField<String>`	`ACCOUNTING_DOC_EXTERNAL_REFERENCE` Use with available fluent helpers to apply the AccountingDocExternalReference field to query operations.
`static SalesOrderField<BigDecimal>`	`ACCOUNTING_EXCHANGE_RATE` Use with available fluent helpers to apply the AccountingExchangeRate field to query operations.
`static SalesOrderField<String>`	`ADDITIONAL_CUSTOMER_GROUP1` Use with available fluent helpers to apply the AdditionalCustomerGroup1 field to query operations.
`static SalesOrderField<String>`	`ADDITIONAL_CUSTOMER_GROUP2` Use with available fluent helpers to apply the AdditionalCustomerGroup2 field to query operations.
`static SalesOrderField<String>`	`ADDITIONAL_CUSTOMER_GROUP3` Use with available fluent helpers to apply the AdditionalCustomerGroup3 field to query operations.
`static SalesOrderField<String>`	`ADDITIONAL_CUSTOMER_GROUP4` Use with available fluent helpers to apply the AdditionalCustomerGroup4 field to query operations.
`static SalesOrderField<String>`	`ADDITIONAL_CUSTOMER_GROUP5` Use with available fluent helpers to apply the AdditionalCustomerGroup5 field to query operations.
`static SalesOrderSelectable`	`ALL_FIELDS` Selector for all available fields of SalesOrder.
`static SalesOrderField<String>`	`ASSIGNMENT_REFERENCE` Use with available fluent helpers to apply the AssignmentReference field to query operations.
`static SalesOrderField<Boolean>`	`COMPLETE_DELIVERY_IS_DEFINED` Use with available fluent helpers to apply the CompleteDeliveryIsDefined field to query operations.
`static SalesOrderField<String>`	`CREATED_BY_USER` Use with available fluent helpers to apply the CreatedByUser field to query operations.
`static SalesOrderField<LocalDateTime>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP` Use with available fluent helpers to apply the CustomerAccountAssignmentGroup field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_GROUP` Use with available fluent helpers to apply the CustomerGroup field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_PRICE_GROUP` Use with available fluent helpers to apply the CustomerPriceGroup field to query operations.
`static SalesOrderField<LocalDateTime>`	`CUSTOMER_PURCHASE_ORDER_DATE` Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_PURCHASE_ORDER_TYPE` Use with available fluent helpers to apply the CustomerPurchaseOrderType field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION1` Use with available fluent helpers to apply the CustomerTaxClassification1 field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION2` Use with available fluent helpers to apply the CustomerTaxClassification2 field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION3` Use with available fluent helpers to apply the CustomerTaxClassification3 field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION4` Use with available fluent helpers to apply the CustomerTaxClassification4 field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION5` Use with available fluent helpers to apply the CustomerTaxClassification5 field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION6` Use with available fluent helpers to apply the CustomerTaxClassification6 field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION7` Use with available fluent helpers to apply the CustomerTaxClassification7 field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION8` Use with available fluent helpers to apply the CustomerTaxClassification8 field to query operations.
`static SalesOrderField<String>`	`CUSTOMER_TAX_CLASSIFICATION9` Use with available fluent helpers to apply the CustomerTaxClassification9 field to query operations.
`static SalesOrderField<String>`	`DELIVERY_BLOCK_REASON` Use with available fluent helpers to apply the DeliveryBlockReason field to query operations.
`static SalesOrderField<String>`	`DELIVERY_DATE_TYPE_RULE` Use with available fluent helpers to apply the DeliveryDateTypeRule field to query operations.
`static SalesOrderField<String>`	`DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the DistributionChannel field to query operations.
`static SalesOrderField<ZonedDateTime>`	`EXTERNAL_DOC_LAST_CHANGE_DATE_TIME` Use with available fluent helpers to apply the ExternalDocLastChangeDateTime field to query operations.
`static SalesOrderField<String>`	`EXTERNAL_DOCUMENT_ID` Use with available fluent helpers to apply the ExternalDocumentID field to query operations.
`static SalesOrderField<LocalDateTime>`	`FIXED_VALUE_DATE` Use with available fluent helpers to apply the FixedValueDate field to query operations.
`static SalesOrderField<String>`	`HEADER_BILLING_BLOCK_REASON` Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
`static SalesOrderField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static SalesOrderField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static SalesOrderField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static SalesOrderField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static SalesOrderField<String>`	`INCOTERMS_VERSION` Use with available fluent helpers to apply the IncotermsVersion field to query operations.
`static SalesOrderField<LocalDateTime>`	`LAST_CHANGE_DATE` Use with available fluent helpers to apply the LastChangeDate field to query operations.
`static SalesOrderField<ZonedDateTime>`	`LAST_CHANGE_DATE_TIME` Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
`static SalesOrderField<String>`	`ORGANIZATION_DIVISION` Use with available fluent helpers to apply the OrganizationDivision field to query operations.
`static SalesOrderField<String>`	`OVERALL_DELIVERY_STATUS` Use with available fluent helpers to apply the OverallDeliveryStatus field to query operations.
`static SalesOrderField<String>`	`OVERALL_ORD_RELTD_BILLG_STATUS` Use with available fluent helpers to apply the OverallOrdReltdBillgStatus field to query operations.
`static SalesOrderField<String>`	`OVERALL_SD_DOC_REFERENCE_STATUS` Use with available fluent helpers to apply the OverallSDDocReferenceStatus field to query operations.
`static SalesOrderField<String>`	`OVERALL_SD_DOCUMENT_REJECTION_STS` Use with available fluent helpers to apply the OverallSDDocumentRejectionSts field to query operations.
`static SalesOrderField<String>`	`OVERALL_SD_PROCESS_STATUS` Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
`static SalesOrderField<String>`	`OVERALL_TOTAL_DELIVERY_STATUS` Use with available fluent helpers to apply the OverallTotalDeliveryStatus field to query operations.
`static SalesOrderField<String>`	`PAYMENT_METHOD` Use with available fluent helpers to apply the PaymentMethod field to query operations.
`static SalesOrderField<BigDecimal>`	`PRICE_DETN_EXCHANGE_RATE` Use with available fluent helpers to apply the PriceDetnExchangeRate field to query operations.
`static SalesOrderField<String>`	`PRICE_LIST_TYPE` Use with available fluent helpers to apply the PriceListType field to query operations.
`static SalesOrderField<LocalDateTime>`	`PRICING_DATE` Use with available fluent helpers to apply the PricingDate field to query operations.
`static SalesOrderField<String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static SalesOrderField<String>`	`PURCHASE_ORDER_BY_SHIP_TO_PARTY` Use with available fluent helpers to apply the PurchaseOrderByShipToParty field to query operations.
`static SalesOrderField<String>`	`REFERENCE_SD_DOCUMENT` Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
`static SalesOrderField<String>`	`REFERENCE_SD_DOCUMENT_CATEGORY` Use with available fluent helpers to apply the ReferenceSDDocumentCategory field to query operations.
`static SalesOrderField<LocalDateTime>`	`REQUESTED_DELIVERY_DATE` Use with available fluent helpers to apply the RequestedDeliveryDate field to query operations.
`static SalesOrderField<String>`	`SALES_DISTRICT` Use with available fluent helpers to apply the SalesDistrict field to query operations.
`static SalesOrderField<String>`	`SALES_DOC_APPROVAL_STATUS` Use with available fluent helpers to apply the SalesDocApprovalStatus field to query operations.
`static SalesOrderField<String>`	`SALES_GROUP` Use with available fluent helpers to apply the SalesGroup field to query operations.
`static SalesOrderField<String>`	`SALES_OFFICE` Use with available fluent helpers to apply the SalesOffice field to query operations.
`static SalesOrderField<String>`	`SALES_ORDER` Use with available fluent helpers to apply the SalesOrder field to query operations.
`static SalesOrderField<String>`	`SALES_ORDER_APPROVAL_REASON` Use with available fluent helpers to apply the SalesOrderApprovalReason field to query operations.
`static SalesOrderField<LocalDateTime>`	`SALES_ORDER_DATE` Use with available fluent helpers to apply the SalesOrderDate field to query operations.
`static SalesOrderField<String>`	`SALES_ORDER_TYPE` Use with available fluent helpers to apply the SalesOrderType field to query operations.
`static SalesOrderField<String>`	`SALES_ORGANIZATION` Use with available fluent helpers to apply the SalesOrganization field to query operations.
`static SalesOrderField<String>`	`SD_DOCUMENT_REASON` Use with available fluent helpers to apply the SDDocumentReason field to query operations.
`static SalesOrderField<String>`	`SENDER_BUSINESS_SYSTEM_NAME` Use with available fluent helpers to apply the SenderBusinessSystemName field to query operations.
`static SalesOrderField<String>`	`SHIPPING_CONDITION` Use with available fluent helpers to apply the ShippingCondition field to query operations.
`static SalesOrderField<String>`	`SHIPPING_TYPE` Use with available fluent helpers to apply the ShippingType field to query operations.
`static SalesOrderField<Boolean>`	`SLS_DOC_IS_RLVT_FOR_PROOF_OF_DELIV` Use with available fluent helpers to apply the SlsDocIsRlvtForProofOfDeliv field to query operations.
`static SalesOrderField<String>`	`SOLD_TO_PARTY` Use with available fluent helpers to apply the SoldToParty field to query operations.
`static SalesOrderField<String>`	`TAX_DEPARTURE_COUNTRY` Use with available fluent helpers to apply the TaxDepartureCountry field to query operations.
`static SalesOrderLink<SalesOrderItem>`	`TO_ITEM` Use with available fluent helpers to apply the to_Item navigation property to query operations.
`static SalesOrderLink<SalesOrderHeaderPartner>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static SalesOrderLink<SlsOrdPaymentPlanItemDetails>`	`TO_PAYMENT_PLAN_ITEM_DETAILS` Use with available fluent helpers to apply the to_PaymentPlanItemDetails navigation property to query operations.
`static SalesOrderLink<SalesOrderHeaderPrElement>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static SalesOrderLink<SalesOrderText>`	`TO_TEXT` Use with available fluent helpers to apply the to_Text navigation property to query operations.
`static SalesOrderField<String>`	`TOTAL_BLOCK_STATUS` Use with available fluent helpers to apply the TotalBlockStatus field to query operations.
`static SalesOrderField<String>`	`TOTAL_CREDIT_CHECK_STATUS` Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
`static SalesOrderField<BigDecimal>`	`TOTAL_NET_AMOUNT` Use with available fluent helpers to apply the TotalNetAmount field to query operations.
`static SalesOrderField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.
`static SalesOrderField<String>`	`VAT_REGISTRATION_COUNTRY` Use with available fluent helpers to apply the VATRegistrationCountry field to query operations.

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

Constructor Summary

Constructors
Constructor and Description
`SalesOrder()`
SalesOrder(String salesOrder, String salesOrderType, String salesOrganization, String distributionChannel, String organizationDivision, String salesGroup, String salesOffice, String salesDistrict, String soldToParty, LocalDateTime creationDate, String createdByUser, LocalDateTime lastChangeDate, String senderBusinessSystemName, String externalDocumentID, ZonedDateTime lastChangeDateTime, ZonedDateTime externalDocLastChangeDateTime, String purchaseOrderByCustomer, String purchaseOrderByShipToParty, String customerPurchaseOrderType, LocalDateTime customerPurchaseOrderDate, LocalDateTime salesOrderDate, BigDecimal totalNetAmount, String overallDeliveryStatus, String totalBlockStatus, String overallOrdReltdBillgStatus, String overallSDDocReferenceStatus, String transactionCurrency, String sDDocumentReason, LocalDateTime pricingDate, BigDecimal priceDetnExchangeRate, LocalDateTime requestedDeliveryDate, String shippingCondition, Boolean completeDeliveryIsDefined, String shippingType, String headerBillingBlockReason, String deliveryBlockReason, String deliveryDateTypeRule, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String incotermsVersion, String customerPriceGroup, String priceListType, String customerPaymentTerms, String paymentMethod, LocalDateTime fixedValueDate, String assignmentReference, String referenceSDDocument, String referenceSDDocumentCategory, String accountingDocExternalReference, String customerAccountAssignmentGroup, BigDecimal accountingExchangeRate, String customerGroup, String additionalCustomerGroup1, String additionalCustomerGroup2, String additionalCustomerGroup3, String additionalCustomerGroup4, String additionalCustomerGroup5, Boolean slsDocIsRlvtForProofOfDeliv, String customerTaxClassification1, String customerTaxClassification2, String customerTaxClassification3, String customerTaxClassification4, String customerTaxClassification5, String customerTaxClassification6, String customerTaxClassification7, String customerTaxClassification8, String customerTaxClassification9, String taxDepartureCountry, String vATRegistrationCountry, String salesOrderApprovalReason, String salesDocApprovalStatus, String overallSDProcessStatus, String totalCreditCheckStatus, String overallTotalDeliveryStatus, String overallSDDocumentRejectionSts, List<SalesOrderItem> toItem, List<SalesOrderHeaderPartner> toPartner, List<SlsOrdPaymentPlanItemDetails> toPaymentPlanItemDetails, List<SalesOrderHeaderPrElement> toPricingElement, List<SalesOrderText> toText)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addItem(SalesOrderItem... entity)` Adds elements to the list of associated SalesOrderItem entities.
`void`	`addPartner(SalesOrderHeaderPartner... entity)` Adds elements to the list of associated SalesOrderHeaderPartner entities.
`void`	`addPaymentPlanItemDetails(SlsOrdPaymentPlanItemDetails... entity)` Adds elements to the list of associated SlsOrdPaymentPlanItemDetails entities.
`void`	`addPricingElement(SalesOrderHeaderPrElement... entity)` Adds elements to the list of associated SalesOrderHeaderPrElement entities.
`void`	`addText(SalesOrderText... entity)` Adds elements to the list of associated SalesOrderText entities.
`void`	`attachToService(String servicePath, HttpDestinationProperties destination)` Sets the service path and destination for the fetch commands of this entity.
`static SalesOrder.SalesOrderBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`List<SalesOrderItem>`	`fetchItem()` Fetches the SalesOrderItem entities (one to many) associated with this entity.
`List<SalesOrderHeaderPartner>`	`fetchPartner()` Fetches the SalesOrderHeaderPartner entities (one to many) associated with this entity.
`List<SlsOrdPaymentPlanItemDetails>`	`fetchPaymentPlanItemDetails()` Fetches the SlsOrdPaymentPlanItemDetails entities (one to many) associated with this entity.
`List<SalesOrderHeaderPrElement>`	`fetchPricingElement()` Fetches the SalesOrderHeaderPrElement entities (one to many) associated with this entity.
`List<SalesOrderText>`	`fetchText()` Fetches the SalesOrderText entities (one to many) associated with this entity.
`static <T> SalesOrderField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> SalesOrderField<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)`
`String`	`getAccountingDocExternalReference()` Constraints: Not nullable, Maximum length: 16
`BigDecimal`	`getAccountingExchangeRate()` Constraints: Not nullable, Precision: 9, Scale: 5
`String`	`getAdditionalCustomerGroup1()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalCustomerGroup2()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalCustomerGroup3()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalCustomerGroup4()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalCustomerGroup5()` Constraints: Not nullable, Maximum length: 3
`String`	`getAssignmentReference()` Constraints: Not nullable, Maximum length: 18
`Boolean`	`getCompleteDeliveryIsDefined()` Constraints: none
`String`	`getCreatedByUser()` Constraints: Not nullable, Maximum length: 12
`LocalDateTime`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`String`	`getCustomerAccountAssignmentGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4
`String`	`getCustomerPriceGroup()` Constraints: Not nullable, Maximum length: 2
`LocalDateTime`	`getCustomerPurchaseOrderDate()` Constraints: Not nullable, Precision: 0
`String`	`getCustomerPurchaseOrderType()` Constraints: Not nullable, Maximum length: 4
`String`	`getCustomerTaxClassification1()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification2()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification3()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification4()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification5()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification6()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification7()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification8()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification9()` Constraints: Not nullable, Maximum length: 1
`protected String`	`getDefaultServicePath()` Used by fluent helpers and navigation property methods to construct OData queries.
`String`	`getDeliveryBlockReason()` Constraints: Not nullable, Maximum length: 2
`String`	`getDeliveryDateTypeRule()` Constraints: Not nullable, Maximum length: 1
`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.
`ZonedDateTime`	`getExternalDocLastChangeDateTime()` Constraints: Not nullable, Precision: 7
`String`	`getExternalDocumentID()` Constraints: Not nullable, Maximum length: 40
`LocalDateTime`	`getFixedValueDate()` Constraints: Not nullable, Precision: 0
`String`	`getHeaderBillingBlockReason()` Constraints: Not nullable, Maximum length: 2
`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<SalesOrderItem>>`	`getItemIfPresent()` Retrieval of associated SalesOrderItem entities (one to many).
`List<SalesOrderItem>`	`getItemOrFetch()` Retrieval of associated SalesOrderItem entities (one to many).
`protected Map<String,Object>`	`getKey()`
`LocalDateTime`	`getLastChangeDate()` Constraints: Not nullable, Precision: 0
`ZonedDateTime`	`getLastChangeDateTime()` Constraints: Not nullable, Precision: 7
`String`	`getOrganizationDivision()` Constraints: Not nullable, Maximum length: 2
`String`	`getOverallDeliveryStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallOrdReltdBillgStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallSDDocReferenceStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallSDDocumentRejectionSts()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallSDProcessStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallTotalDeliveryStatus()` Constraints: Not nullable, Maximum length: 1
`io.vavr.control.Option<List<SalesOrderHeaderPartner>>`	`getPartnerIfPresent()` Retrieval of associated SalesOrderHeaderPartner entities (one to many).
`List<SalesOrderHeaderPartner>`	`getPartnerOrFetch()` Retrieval of associated SalesOrderHeaderPartner entities (one to many).
`String`	`getPaymentMethod()` Constraints: Not nullable, Maximum length: 1
`io.vavr.control.Option<List<SlsOrdPaymentPlanItemDetails>>`	`getPaymentPlanItemDetailsIfPresent()` Retrieval of associated SlsOrdPaymentPlanItemDetails entities (one to many).
`List<SlsOrdPaymentPlanItemDetails>`	`getPaymentPlanItemDetailsOrFetch()` Retrieval of associated SlsOrdPaymentPlanItemDetails entities (one to many).
`BigDecimal`	`getPriceDetnExchangeRate()` Constraints: Not nullable, Precision: 9, Scale: 5
`String`	`getPriceListType()` Constraints: Not nullable, Maximum length: 2
`LocalDateTime`	`getPricingDate()` Constraints: Not nullable, Precision: 0
`io.vavr.control.Option<List<SalesOrderHeaderPrElement>>`	`getPricingElementIfPresent()` Retrieval of associated SalesOrderHeaderPrElement entities (one to many).
`List<SalesOrderHeaderPrElement>`	`getPricingElementOrFetch()` Retrieval of associated SalesOrderHeaderPrElement entities (one to many).
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35
`String`	`getPurchaseOrderByShipToParty()` Constraints: Not nullable, Maximum length: 35
`String`	`getReferenceSDDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getReferenceSDDocumentCategory()` Constraints: Not nullable, Maximum length: 4
`LocalDateTime`	`getRequestedDeliveryDate()` Constraints: Not nullable, Precision: 0
`String`	`getSalesDistrict()` Constraints: Not nullable, Maximum length: 6
`String`	`getSalesDocApprovalStatus()` Constraints: Not nullable, Maximum length: 1
`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
`String`	`getSalesOrderApprovalReason()` Constraints: Not nullable, Maximum length: 4
`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`	`getSenderBusinessSystemName()` Constraints: Not nullable, Maximum length: 60
`String`	`getShippingCondition()` Constraints: Not nullable, Maximum length: 2
`String`	`getShippingType()` Constraints: Not nullable, Maximum length: 2
`Boolean`	`getSlsDocIsRlvtForProofOfDeliv()` Constraints: none
`String`	`getSoldToParty()` Constraints: Not nullable, Maximum length: 10
`String`	`getTaxDepartureCountry()` Constraints: Not nullable, Maximum length: 3
`io.vavr.control.Option<List<SalesOrderText>>`	`getTextIfPresent()` Retrieval of associated SalesOrderText entities (one to many).
`List<SalesOrderText>`	`getTextOrFetch()` Retrieval of associated SalesOrderText entities (one to many).
`String`	`getTotalBlockStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getTotalCreditCheckStatus()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getTotalNetAmount()` Constraints: Not nullable, Precision: 16, Scale: 3
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5
`Class<SalesOrder>`	`getType()`
`String`	`getVATRegistrationCountry()` Constraints: Not nullable, Maximum length: 3
`int`	`hashCode()`
`void`	`setAccountingDocExternalReference(String accountingDocExternalReference)` Constraints: Not nullable, Maximum length: 16
`void`	`setAccountingExchangeRate(BigDecimal accountingExchangeRate)` Constraints: Not nullable, Precision: 9, Scale: 5
`void`	`setAdditionalCustomerGroup1(String additionalCustomerGroup1)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalCustomerGroup2(String additionalCustomerGroup2)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalCustomerGroup3(String additionalCustomerGroup3)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalCustomerGroup4(String additionalCustomerGroup4)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalCustomerGroup5(String additionalCustomerGroup5)` Constraints: Not nullable, Maximum length: 3
`void`	`setAssignmentReference(String assignmentReference)` Constraints: Not nullable, Maximum length: 18
`void`	`setCompleteDeliveryIsDefined(Boolean completeDeliveryIsDefined)` Constraints: none
`void`	`setCreatedByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setCustomerAccountAssignmentGroup(String customerAccountAssignmentGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerGroup(String customerGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`void`	`setCustomerPriceGroup(String customerPriceGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)` Constraints: Not nullable, Precision: 0
`void`	`setCustomerPurchaseOrderType(String customerPurchaseOrderType)` Constraints: Not nullable, Maximum length: 4
`void`	`setCustomerTaxClassification1(String customerTaxClassification1)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification2(String customerTaxClassification2)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification3(String customerTaxClassification3)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification4(String customerTaxClassification4)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification5(String customerTaxClassification5)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification6(String customerTaxClassification6)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification7(String customerTaxClassification7)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification8(String customerTaxClassification8)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification9(String customerTaxClassification9)` Constraints: Not nullable, Maximum length: 1
`void`	`setDeliveryBlockReason(String deliveryBlockReason)` Constraints: Not nullable, Maximum length: 2
`void`	`setDeliveryDateTypeRule(String deliveryDateTypeRule)` Constraints: Not nullable, Maximum length: 1
`void`	`setDistributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2
`void`	`setExternalDocLastChangeDateTime(ZonedDateTime externalDocLastChangeDateTime)` Constraints: Not nullable, Precision: 7
`void`	`setExternalDocumentID(String externalDocumentID)` Constraints: Not nullable, Maximum length: 40
`void`	`setFixedValueDate(LocalDateTime fixedValueDate)` Constraints: Not nullable, Precision: 0
`void`	`setHeaderBillingBlockReason(String headerBillingBlockReason)` 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<SalesOrderItem> value)` Overwrites the list of associated SalesOrderItem entities for the loaded navigation property to_Item.
`void`	`setLastChangeDate(LocalDateTime lastChangeDate)` Constraints: Not nullable, Precision: 0
`void`	`setLastChangeDateTime(ZonedDateTime lastChangeDateTime)` Constraints: Not nullable, Precision: 7
`void`	`setOrganizationDivision(String organizationDivision)` Constraints: Not nullable, Maximum length: 2
`void`	`setOverallDeliveryStatus(String overallDeliveryStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallOrdReltdBillgStatus(String overallOrdReltdBillgStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallSDDocReferenceStatus(String overallSDDocReferenceStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallSDProcessStatus(String overallSDProcessStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallTotalDeliveryStatus(String overallTotalDeliveryStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setPartner(List<SalesOrderHeaderPartner> value)` Overwrites the list of associated SalesOrderHeaderPartner entities for the loaded navigation property to_Partner.
`void`	`setPaymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1
`void`	`setPaymentPlanItemDetails(List<SlsOrdPaymentPlanItemDetails> value)` Overwrites the list of associated SlsOrdPaymentPlanItemDetails entities for the loaded navigation property to_PaymentPlanItemDetails.
`void`	`setPriceDetnExchangeRate(BigDecimal priceDetnExchangeRate)` Constraints: Not nullable, Precision: 9, Scale: 5
`void`	`setPriceListType(String priceListType)` Constraints: Not nullable, Maximum length: 2
`void`	`setPricingDate(LocalDateTime pricingDate)` Constraints: Not nullable, Precision: 0
`void`	`setPricingElement(List<SalesOrderHeaderPrElement> value)` Overwrites the list of associated SalesOrderHeaderPrElement entities for the loaded navigation property to_PricingElement.
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`void`	`setPurchaseOrderByShipToParty(String purchaseOrderByShipToParty)` Constraints: Not nullable, Maximum length: 35
`void`	`setReferenceSDDocument(String referenceSDDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setReferenceSDDocumentCategory(String referenceSDDocumentCategory)` Constraints: Not nullable, Maximum length: 4
`void`	`setRequestedDeliveryDate(LocalDateTime requestedDeliveryDate)` Constraints: Not nullable, Precision: 0
`void`	`setSalesDistrict(String salesDistrict)` Constraints: Not nullable, Maximum length: 6
`void`	`setSalesDocApprovalStatus(String salesDocApprovalStatus)` Constraints: Not nullable, Maximum length: 1
`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`	`setSalesOrderApprovalReason(String salesOrderApprovalReason)` Constraints: Not nullable, Maximum length: 4
`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
`void`	`setSenderBusinessSystemName(String senderBusinessSystemName)` Constraints: Not nullable, Maximum length: 60
`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`	`setSlsDocIsRlvtForProofOfDeliv(Boolean slsDocIsRlvtForProofOfDeliv)` Constraints: none
`void`	`setSoldToParty(String soldToParty)` Constraints: Not nullable, Maximum length: 10
`void`	`setTaxDepartureCountry(String taxDepartureCountry)` Constraints: Not nullable, Maximum length: 3
`void`	`setText(List<SalesOrderText> value)` Overwrites the list of associated SalesOrderText entities for the loaded navigation property to_Text.
`void`	`setTotalBlockStatus(String totalBlockStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setTotalCreditCheckStatus(String totalCreditCheckStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setTotalNetAmount(BigDecimal totalNetAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5
`void`	`setVATRegistrationCountry(String vATRegistrationCountry)` Constraints: Not nullable, Maximum length: 3
`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 SalesOrderSelectable ALL_FIELDS
```
    Selector for all available fields of SalesOrder.
  - SALES_ORDER
```
public static final SalesOrderField<String> SALES_ORDER
```
    Use with available fluent helpers to apply the SalesOrder field to query operations.
  - SALES_ORDER_TYPE
```
public static final SalesOrderField<String> SALES_ORDER_TYPE
```
    Use with available fluent helpers to apply the SalesOrderType field to query operations.
  - SALES_ORGANIZATION
```
public static final SalesOrderField<String> SALES_ORGANIZATION
```
    Use with available fluent helpers to apply the SalesOrganization field to query operations.
  - DISTRIBUTION_CHANNEL
```
public static final SalesOrderField<String> DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the DistributionChannel field to query operations.
  - ORGANIZATION_DIVISION
```
public static final SalesOrderField<String> ORGANIZATION_DIVISION
```
    Use with available fluent helpers to apply the OrganizationDivision field to query operations.
  - SALES_GROUP
```
public static final SalesOrderField<String> SALES_GROUP
```
    Use with available fluent helpers to apply the SalesGroup field to query operations.
  - SALES_OFFICE
```
public static final SalesOrderField<String> SALES_OFFICE
```
    Use with available fluent helpers to apply the SalesOffice field to query operations.
  - SALES_DISTRICT
```
public static final SalesOrderField<String> SALES_DISTRICT
```
    Use with available fluent helpers to apply the SalesDistrict field to query operations.
  - SOLD_TO_PARTY
```
public static final SalesOrderField<String> SOLD_TO_PARTY
```
    Use with available fluent helpers to apply the SoldToParty field to query operations.
  - CREATION_DATE
```
public static final SalesOrderField<LocalDateTime> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - CREATED_BY_USER
```
public static final SalesOrderField<String> CREATED_BY_USER
```
    Use with available fluent helpers to apply the CreatedByUser field to query operations.
  - LAST_CHANGE_DATE
```
public static final SalesOrderField<LocalDateTime> LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the LastChangeDate field to query operations.
  - SENDER_BUSINESS_SYSTEM_NAME
```
public static final SalesOrderField<String> SENDER_BUSINESS_SYSTEM_NAME
```
    Use with available fluent helpers to apply the SenderBusinessSystemName field to query operations.
  - EXTERNAL_DOCUMENT_ID
```
public static final SalesOrderField<String> EXTERNAL_DOCUMENT_ID
```
    Use with available fluent helpers to apply the ExternalDocumentID field to query operations.
  - LAST_CHANGE_DATE_TIME
```
public static final SalesOrderField<ZonedDateTime> LAST_CHANGE_DATE_TIME
```
    Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
  - EXTERNAL_DOC_LAST_CHANGE_DATE_TIME
```
public static final SalesOrderField<ZonedDateTime> EXTERNAL_DOC_LAST_CHANGE_DATE_TIME
```
    Use with available fluent helpers to apply the ExternalDocLastChangeDateTime field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final SalesOrderField<String> PURCHASE_ORDER_BY_CUSTOMER
```
    Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
  - PURCHASE_ORDER_BY_SHIP_TO_PARTY
```
public static final SalesOrderField<String> PURCHASE_ORDER_BY_SHIP_TO_PARTY
```
    Use with available fluent helpers to apply the PurchaseOrderByShipToParty field to query operations.
  - CUSTOMER_PURCHASE_ORDER_TYPE
```
public static final SalesOrderField<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 SalesOrderField<LocalDateTime> CUSTOMER_PURCHASE_ORDER_DATE
```
    Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
  - SALES_ORDER_DATE
```
public static final SalesOrderField<LocalDateTime> SALES_ORDER_DATE
```
    Use with available fluent helpers to apply the SalesOrderDate field to query operations.
  - TOTAL_NET_AMOUNT
```
public static final SalesOrderField<BigDecimal> TOTAL_NET_AMOUNT
```
    Use with available fluent helpers to apply the TotalNetAmount field to query operations.
  - OVERALL_DELIVERY_STATUS
```
public static final SalesOrderField<String> OVERALL_DELIVERY_STATUS
```
    Use with available fluent helpers to apply the OverallDeliveryStatus field to query operations.
  - TOTAL_BLOCK_STATUS
```
public static final SalesOrderField<String> TOTAL_BLOCK_STATUS
```
    Use with available fluent helpers to apply the TotalBlockStatus field to query operations.
  - OVERALL_ORD_RELTD_BILLG_STATUS
```
public static final SalesOrderField<String> OVERALL_ORD_RELTD_BILLG_STATUS
```
    Use with available fluent helpers to apply the OverallOrdReltdBillgStatus field to query operations.
  - OVERALL_SD_DOC_REFERENCE_STATUS
```
public static final SalesOrderField<String> OVERALL_SD_DOC_REFERENCE_STATUS
```
    Use with available fluent helpers to apply the OverallSDDocReferenceStatus field to query operations.
  - TRANSACTION_CURRENCY
```
public static final SalesOrderField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - SD_DOCUMENT_REASON
```
public static final SalesOrderField<String> SD_DOCUMENT_REASON
```
    Use with available fluent helpers to apply the SDDocumentReason field to query operations.
  - PRICING_DATE
```
public static final SalesOrderField<LocalDateTime> PRICING_DATE
```
    Use with available fluent helpers to apply the PricingDate field to query operations.
  - PRICE_DETN_EXCHANGE_RATE
```
public static final SalesOrderField<BigDecimal> PRICE_DETN_EXCHANGE_RATE
```
    Use with available fluent helpers to apply the PriceDetnExchangeRate field to query operations.
  - REQUESTED_DELIVERY_DATE
```
public static final SalesOrderField<LocalDateTime> REQUESTED_DELIVERY_DATE
```
    Use with available fluent helpers to apply the RequestedDeliveryDate field to query operations.
  - SHIPPING_CONDITION
```
public static final SalesOrderField<String> SHIPPING_CONDITION
```
    Use with available fluent helpers to apply the ShippingCondition field to query operations.
  - COMPLETE_DELIVERY_IS_DEFINED
```
public static final SalesOrderField<Boolean> COMPLETE_DELIVERY_IS_DEFINED
```
    Use with available fluent helpers to apply the CompleteDeliveryIsDefined field to query operations.
  - SHIPPING_TYPE
```
public static final SalesOrderField<String> SHIPPING_TYPE
```
    Use with available fluent helpers to apply the ShippingType field to query operations.
  - HEADER_BILLING_BLOCK_REASON
```
public static final SalesOrderField<String> HEADER_BILLING_BLOCK_REASON
```
    Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
  - DELIVERY_BLOCK_REASON
```
public static final SalesOrderField<String> DELIVERY_BLOCK_REASON
```
    Use with available fluent helpers to apply the DeliveryBlockReason field to query operations.
  - DELIVERY_DATE_TYPE_RULE
```
public static final SalesOrderField<String> DELIVERY_DATE_TYPE_RULE
```
    Use with available fluent helpers to apply the DeliveryDateTypeRule field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final SalesOrderField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final SalesOrderField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final SalesOrderField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final SalesOrderField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - INCOTERMS_VERSION
```
public static final SalesOrderField<String> INCOTERMS_VERSION
```
    Use with available fluent helpers to apply the IncotermsVersion field to query operations.
  - CUSTOMER_PRICE_GROUP
```
public static final SalesOrderField<String> CUSTOMER_PRICE_GROUP
```
    Use with available fluent helpers to apply the CustomerPriceGroup field to query operations.
  - PRICE_LIST_TYPE
```
public static final SalesOrderField<String> PRICE_LIST_TYPE
```
    Use with available fluent helpers to apply the PriceListType field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final SalesOrderField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - PAYMENT_METHOD
```
public static final SalesOrderField<String> PAYMENT_METHOD
```
    Use with available fluent helpers to apply the PaymentMethod field to query operations.
  - FIXED_VALUE_DATE
```
public static final SalesOrderField<LocalDateTime> FIXED_VALUE_DATE
```
    Use with available fluent helpers to apply the FixedValueDate field to query operations.
  - ASSIGNMENT_REFERENCE
```
public static final SalesOrderField<String> ASSIGNMENT_REFERENCE
```
    Use with available fluent helpers to apply the AssignmentReference field to query operations.
  - REFERENCE_SD_DOCUMENT
```
public static final SalesOrderField<String> REFERENCE_SD_DOCUMENT
```
    Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
  - REFERENCE_SD_DOCUMENT_CATEGORY
```
public static final SalesOrderField<String> REFERENCE_SD_DOCUMENT_CATEGORY
```
    Use with available fluent helpers to apply the ReferenceSDDocumentCategory field to query operations.
  - ACCOUNTING_DOC_EXTERNAL_REFERENCE
```
public static final SalesOrderField<String> ACCOUNTING_DOC_EXTERNAL_REFERENCE
```
    Use with available fluent helpers to apply the AccountingDocExternalReference field to query operations.
  - CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
```
public static final SalesOrderField<String> CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
```
    Use with available fluent helpers to apply the CustomerAccountAssignmentGroup field to query operations.
  - ACCOUNTING_EXCHANGE_RATE
```
public static final SalesOrderField<BigDecimal> ACCOUNTING_EXCHANGE_RATE
```
    Use with available fluent helpers to apply the AccountingExchangeRate field to query operations.
  - CUSTOMER_GROUP
```
public static final SalesOrderField<String> CUSTOMER_GROUP
```
    Use with available fluent helpers to apply the CustomerGroup field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP1
```
public static final SalesOrderField<String> ADDITIONAL_CUSTOMER_GROUP1
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup1 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP2
```
public static final SalesOrderField<String> ADDITIONAL_CUSTOMER_GROUP2
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup2 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP3
```
public static final SalesOrderField<String> ADDITIONAL_CUSTOMER_GROUP3
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup3 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP4
```
public static final SalesOrderField<String> ADDITIONAL_CUSTOMER_GROUP4
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup4 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP5
```
public static final SalesOrderField<String> ADDITIONAL_CUSTOMER_GROUP5
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup5 field to query operations.
  - SLS_DOC_IS_RLVT_FOR_PROOF_OF_DELIV
```
public static final SalesOrderField<Boolean> SLS_DOC_IS_RLVT_FOR_PROOF_OF_DELIV
```
    Use with available fluent helpers to apply the SlsDocIsRlvtForProofOfDeliv field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION1
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION1
```
    Use with available fluent helpers to apply the CustomerTaxClassification1 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION2
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION2
```
    Use with available fluent helpers to apply the CustomerTaxClassification2 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION3
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION3
```
    Use with available fluent helpers to apply the CustomerTaxClassification3 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION4
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION4
```
    Use with available fluent helpers to apply the CustomerTaxClassification4 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION5
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION5
```
    Use with available fluent helpers to apply the CustomerTaxClassification5 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION6
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION6
```
    Use with available fluent helpers to apply the CustomerTaxClassification6 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION7
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION7
```
    Use with available fluent helpers to apply the CustomerTaxClassification7 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION8
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION8
```
    Use with available fluent helpers to apply the CustomerTaxClassification8 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION9
```
public static final SalesOrderField<String> CUSTOMER_TAX_CLASSIFICATION9
```
    Use with available fluent helpers to apply the CustomerTaxClassification9 field to query operations.
  - TAX_DEPARTURE_COUNTRY
```
public static final SalesOrderField<String> TAX_DEPARTURE_COUNTRY
```
    Use with available fluent helpers to apply the TaxDepartureCountry field to query operations.
  - VAT_REGISTRATION_COUNTRY
```
public static final SalesOrderField<String> VAT_REGISTRATION_COUNTRY
```
    Use with available fluent helpers to apply the VATRegistrationCountry field to query operations.
  - SALES_ORDER_APPROVAL_REASON
```
public static final SalesOrderField<String> SALES_ORDER_APPROVAL_REASON
```
    Use with available fluent helpers to apply the SalesOrderApprovalReason field to query operations.
  - SALES_DOC_APPROVAL_STATUS
```
public static final SalesOrderField<String> SALES_DOC_APPROVAL_STATUS
```
    Use with available fluent helpers to apply the SalesDocApprovalStatus field to query operations.
  - OVERALL_SD_PROCESS_STATUS
```
public static final SalesOrderField<String> OVERALL_SD_PROCESS_STATUS
```
    Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
  - TOTAL_CREDIT_CHECK_STATUS
```
public static final SalesOrderField<String> TOTAL_CREDIT_CHECK_STATUS
```
    Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
  - OVERALL_TOTAL_DELIVERY_STATUS
```
public static final SalesOrderField<String> OVERALL_TOTAL_DELIVERY_STATUS
```
    Use with available fluent helpers to apply the OverallTotalDeliveryStatus field to query operations.
  - OVERALL_SD_DOCUMENT_REJECTION_STS
```
public static final SalesOrderField<String> OVERALL_SD_DOCUMENT_REJECTION_STS
```
    Use with available fluent helpers to apply the OverallSDDocumentRejectionSts field to query operations.
  - TO_ITEM
```
public static final SalesOrderLink<SalesOrderItem> TO_ITEM
```
    Use with available fluent helpers to apply the to_Item navigation property to query operations.
  - TO_PARTNER
```
public static final SalesOrderLink<SalesOrderHeaderPartner> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PAYMENT_PLAN_ITEM_DETAILS
```
public static final SalesOrderLink<SlsOrdPaymentPlanItemDetails> TO_PAYMENT_PLAN_ITEM_DETAILS
```
    Use with available fluent helpers to apply the to_PaymentPlanItemDetails navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final SalesOrderLink<SalesOrderHeaderPrElement> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
  - TO_TEXT
```
public static final SalesOrderLink<SalesOrderText> TO_TEXT
```
    Use with available fluent helpers to apply the to_Text navigation property to query operations.
- Constructor Detail
  - SalesOrder
```
public SalesOrder()
```
  - SalesOrder
```
public SalesOrder(@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
                  LocalDateTime creationDate,
                  @Nullable
                  String createdByUser,
                  @Nullable
                  LocalDateTime lastChangeDate,
                  @Nullable
                  String senderBusinessSystemName,
                  @Nullable
                  String externalDocumentID,
                  @Nullable
                  ZonedDateTime lastChangeDateTime,
                  @Nullable
                  ZonedDateTime externalDocLastChangeDateTime,
                  @Nullable
                  String purchaseOrderByCustomer,
                  @Nullable
                  String purchaseOrderByShipToParty,
                  @Nullable
                  String customerPurchaseOrderType,
                  @Nullable
                  LocalDateTime customerPurchaseOrderDate,
                  @Nullable
                  LocalDateTime salesOrderDate,
                  @Nullable
                  BigDecimal totalNetAmount,
                  @Nullable
                  String overallDeliveryStatus,
                  @Nullable
                  String totalBlockStatus,
                  @Nullable
                  String overallOrdReltdBillgStatus,
                  @Nullable
                  String overallSDDocReferenceStatus,
                  @Nullable
                  String transactionCurrency,
                  @Nullable
                  String sDDocumentReason,
                  @Nullable
                  LocalDateTime pricingDate,
                  @Nullable
                  BigDecimal priceDetnExchangeRate,
                  @Nullable
                  LocalDateTime requestedDeliveryDate,
                  @Nullable
                  String shippingCondition,
                  @Nullable
                  Boolean completeDeliveryIsDefined,
                  @Nullable
                  String shippingType,
                  @Nullable
                  String headerBillingBlockReason,
                  @Nullable
                  String deliveryBlockReason,
                  @Nullable
                  String deliveryDateTypeRule,
                  @Nullable
                  String incotermsClassification,
                  @Nullable
                  String incotermsTransferLocation,
                  @Nullable
                  String incotermsLocation1,
                  @Nullable
                  String incotermsLocation2,
                  @Nullable
                  String incotermsVersion,
                  @Nullable
                  String customerPriceGroup,
                  @Nullable
                  String priceListType,
                  @Nullable
                  String customerPaymentTerms,
                  @Nullable
                  String paymentMethod,
                  @Nullable
                  LocalDateTime fixedValueDate,
                  @Nullable
                  String assignmentReference,
                  @Nullable
                  String referenceSDDocument,
                  @Nullable
                  String referenceSDDocumentCategory,
                  @Nullable
                  String accountingDocExternalReference,
                  @Nullable
                  String customerAccountAssignmentGroup,
                  @Nullable
                  BigDecimal accountingExchangeRate,
                  @Nullable
                  String customerGroup,
                  @Nullable
                  String additionalCustomerGroup1,
                  @Nullable
                  String additionalCustomerGroup2,
                  @Nullable
                  String additionalCustomerGroup3,
                  @Nullable
                  String additionalCustomerGroup4,
                  @Nullable
                  String additionalCustomerGroup5,
                  @Nullable
                  Boolean slsDocIsRlvtForProofOfDeliv,
                  @Nullable
                  String customerTaxClassification1,
                  @Nullable
                  String customerTaxClassification2,
                  @Nullable
                  String customerTaxClassification3,
                  @Nullable
                  String customerTaxClassification4,
                  @Nullable
                  String customerTaxClassification5,
                  @Nullable
                  String customerTaxClassification6,
                  @Nullable
                  String customerTaxClassification7,
                  @Nullable
                  String customerTaxClassification8,
                  @Nullable
                  String customerTaxClassification9,
                  @Nullable
                  String taxDepartureCountry,
                  @Nullable
                  String vATRegistrationCountry,
                  @Nullable
                  String salesOrderApprovalReason,
                  @Nullable
                  String salesDocApprovalStatus,
                  @Nullable
                  String overallSDProcessStatus,
                  @Nullable
                  String totalCreditCheckStatus,
                  @Nullable
                  String overallTotalDeliveryStatus,
                  @Nullable
                  String overallSDDocumentRejectionSts,
                  List<SalesOrderItem> toItem,
                  List<SalesOrderHeaderPartner> toPartner,
                  List<SlsOrdPaymentPlanItemDetails> toPaymentPlanItemDetails,
                  List<SalesOrderHeaderPrElement> toPricingElement,
                  List<SalesOrderText> toText)
```
- Method Detail
  - getType
```
@Nonnull
public Class<SalesOrder> getType()
```
    Specified by:
    
    getType in class VdmObject<SalesOrder>
    
    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.
  - setCreationDate
```
public void setCreationDate(@Nullable
                            LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Parameters:
    
    creationDate - Date on Which Record Was Created
  - setCreatedByUser
```
public void setCreatedByUser(@Nullable
                             String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Parameters:
    
    createdByUser - Name of Person Who Created Object
  - setLastChangeDate
```
public void setLastChangeDate(@Nullable
                              LocalDateTime lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Parameters:
    
    lastChangeDate - Date of Last Change
  - setSenderBusinessSystemName
```
public void setSenderBusinessSystemName(@Nullable
                                        String senderBusinessSystemName)
```
    Constraints: Not nullable, Maximum length: 60
    Original property name from the Odata EDM: SenderBusinessSystemName
    
    Parameters:
    
    senderBusinessSystemName - External Business System ID
  - setExternalDocumentID
```
public void setExternalDocumentID(@Nullable
                                  String externalDocumentID)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: ExternalDocumentID
    
    Parameters:
    
    externalDocumentID - External Document ID
  - setLastChangeDateTime
```
public void setLastChangeDateTime(@Nullable
                                  ZonedDateTime lastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Parameters:
    
    lastChangeDateTime - The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).
  - setExternalDocLastChangeDateTime
```
public void setExternalDocLastChangeDateTime(@Nullable
                                             ZonedDateTime externalDocLastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: ExternalDocLastChangeDateTime
    
    Parameters:
    
    externalDocLastChangeDateTime - Timestamp for Revision of External Calls
  - 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).
  - setPurchaseOrderByShipToParty
```
public void setPurchaseOrderByShipToParty(@Nullable
                                          String purchaseOrderByShipToParty)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByShipToParty
    
    The number is the link between the end customer's purchase order and the sales documents that you have created. You can use the end customer's number for correspondence with the customer, in particular for finding certain document information. If the number refers to a purchase order, you can also print documents that you wish to send to the end customer, such as the delivery note.
    
    Parameters:
    
    purchaseOrderByShipToParty - Number used by the end customer for unique identification of the purchasing document (e.g. inquiry or purchase).
  - 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.
  - setTotalNetAmount
```
public void setTotalNetAmount(@Nullable
                              BigDecimal totalNetAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: TotalNetAmount
    
    Parameters:
    
    totalNetAmount - The total value of all items in the sales document, after any discounts and surcharges are taken into account. The value is expressed in the document currency.
  - setOverallDeliveryStatus
```
public void setOverallDeliveryStatus(@Nullable
                                     String overallDeliveryStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallDeliveryStatus
    
    Parameters:
    
    overallDeliveryStatus - The delivery status of the sales document.
  - setTotalBlockStatus
```
public void setTotalBlockStatus(@Nullable
                                String totalBlockStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalBlockStatus
    
    The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
    
    Parameters:
    
    totalBlockStatus - Overall blocked status.
  - setOverallOrdReltdBillgStatus
```
public void setOverallOrdReltdBillgStatus(@Nullable
                                          String overallOrdReltdBillgStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallOrdReltdBillgStatus
    
    The overall billing status tells you whether the sales order or delivery is relevant for billing, and, if so, to what extent billing has taken place.
    
    Parameters:
    
    overallOrdReltdBillgStatus - The overall billing status of the sales order or delivery.
  - setOverallSDDocReferenceStatus
```
public void setOverallSDDocReferenceStatus(@Nullable
                                           String overallSDDocReferenceStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDDocReferenceStatus
    
    The status message tells you whether one or more other sales documents have referenced this document partially, completely, or not at all.If you create a sales order by copying one item from a quotation that contains a number of items, the reference status for the quotation says that it has been only partially referenced.
    
    Parameters:
    
    overallSDDocReferenceStatus - The reference status of the sales document as it relates to other sales documents.
  - 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.
  - setPriceDetnExchangeRate
```
public void setPriceDetnExchangeRate(@Nullable
                                     BigDecimal priceDetnExchangeRate)
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: PriceDetnExchangeRate
    
    Parameters:
    
    priceDetnExchangeRate - Exchange Rate for Price Determination
  - setRequestedDeliveryDate
```
public void setRequestedDeliveryDate(@Nullable
                                     LocalDateTime requestedDeliveryDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: RequestedDeliveryDate
    
    Parameters:
    
    requestedDeliveryDate - The date on which the customer would like ordered goods to be delivered.
  - 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.
  - setHeaderBillingBlockReason
```
public void setHeaderBillingBlockReason(@Nullable
                                        String headerBillingBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: HeaderBillingBlockReason
    
    The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
    
    Parameters:
    
    headerBillingBlockReason - Indicates if the entire sales document is blocked for billing.
  - setDeliveryBlockReason
```
public void setDeliveryBlockReason(@Nullable
                                   String deliveryBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryBlockReason
    
    The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
    
    Parameters:
    
    deliveryBlockReason - Indicates if an entire sales document (a sales order, for example) is blocked for delivery.
  - setDeliveryDateTypeRule
```
public void setDeliveryDateTypeRule(@Nullable
                                    String deliveryDateTypeRule)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DeliveryDateTypeRule
    
    You can choose one of the following options:The goods should be delivered on the requested delivery date or later. Note that there is no guarantee that the goods will not be delivered earlier.The goods must be delivered exactly on the confirmed delivery date.The goods must be delivered by the confirmed delivery date (that is, on the date or earlier).You can set the delivery date rule on header level to set a default for any items that you create afterwards.In Transportation Management (TM), this field has the following implications:If you want the goods to be delivered on the requested delivery date or later, the delivery date/time is used as the earliest requested delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered on the confirmed delivery date, the start of the delivery date is used as the earliest acceptable delivery date/time and the end of the delivery date as the latest acceptable delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered by the confirmed delivery date, the end of the delivery date is used as the latest acceptable delivery date/time of the freight unit which contains the sales order item.Note: If you want to the goods to be delivered on or by the confirmed delivery date, the system ignores the rule for pick-up and delivery window and the condition for pick-up and delivery window determination which you have defined in the freight unit type for the delivery stop.
    
    Parameters:
    
    deliveryDateTypeRule - Indicates when the ordered goods should be delivered.
  - 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).
  - setCustomerPriceGroup
```
public void setCustomerPriceGroup(@Nullable
                                  String customerPriceGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerPriceGroup
    
    You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.
    
    Parameters:
    
    customerPriceGroup - A grouping of customers who share the same pricing requirements.
  - setPriceListType
```
public void setPriceListType(@Nullable
                             String priceListType)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: PriceListType
    
    You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.
    
    Parameters:
    
    priceListType - Identifies a price list or other condition type (for example, a surcharge or discount).
  - 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.
  - setFixedValueDate
```
public void setFixedValueDate(@Nullable
                              LocalDateTime fixedValueDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: FixedValueDate
    
    If you enter a date in this field, you cannot enter a value in the additional value days field.
    
    Parameters:
    
    fixedValueDate - The date on which the terms of payment related to the sales document become effective.
  - setAssignmentReference
```
public void setAssignmentReference(@Nullable
                                   String assignmentReference)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: AssignmentReference
    
    The line items of an account are displayed in sort sequence according to the content of the field.The allocation number is set in the billing document in accordance with control in document flow and transferred to the financial journal entry.It is possible to set the customer purchase order number, the customer order number, the delivery number or the external delivery number as allocation numbers.The field is a separating criterion in the billing document.
    
    Parameters:
    
    assignmentReference - The allocation is additional information in the customer line item of the journal entry.
  - setReferenceSDDocument
```
public void setReferenceSDDocument(@Nullable
                                   String referenceSDDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceSDDocument
    
    Parameters:
    
    referenceSDDocument - Identifies the sales order to which the delivery refers.
  - setReferenceSDDocumentCategory
```
public void setReferenceSDDocumentCategory(@Nullable
                                           String referenceSDDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ReferenceSDDocumentCategory
    
    Parameters:
    
    referenceSDDocumentCategory - Specifies the sales document category of the preceding sales, delivery, or billing document.
  - setAccountingDocExternalReference
```
public void setAccountingDocExternalReference(@Nullable
                                              String accountingDocExternalReference)
```
    Constraints: Not nullable, Maximum length: 16
    Original property name from the Odata EDM: AccountingDocExternalReference
    
    The reference document number serves as a search criterion when displaying or changing documents. In correspondence, the refererence document number is sometimes printed instead of the document number.The reference number is set in the document flow according to control and taken into the financial journal entry.You can set the customer order number, the order number, the delivery number, the billing number or the external delivery number as reference number.The field is a seperation criterion in the billing document.
    
    Parameters:
    
    accountingDocExternalReference - The reference document number contains the document number with the business partner
  - setCustomerAccountAssignmentGroup
```
public void setCustomerAccountAssignmentGroup(@Nullable
                                              String customerAccountAssignmentGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerAccountAssignmentGroup
    
    The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
    
    Parameters:
    
    customerAccountAssignmentGroup - The account assignment group to which the system automatically posts the sales document.
  - setAccountingExchangeRate
```
public void setAccountingExchangeRate(@Nullable
                                      BigDecimal accountingExchangeRate)
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: AccountingExchangeRate
    
    Your system is configured in such a way that it expects:No prefix (leading sign) for direct ratesA "" as prefix (leading sign) for direct ratesNo prefix for indirect ratesA "" as prefix for indirect rates
    
    Parameters:
    
    accountingExchangeRate - The exchange rate that the system applies when you create an invoice.
  - setCustomerGroup
```
public void setCustomerGroup(@Nullable
                             String customerGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerGroup
    
    Parameters:
    
    customerGroup - Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics.
  - setAdditionalCustomerGroup1
```
public void setAdditionalCustomerGroup1(@Nullable
                                        String additionalCustomerGroup1)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup1
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup1 - Specifies a customer-defined group of customers.
  - setAdditionalCustomerGroup2
```
public void setAdditionalCustomerGroup2(@Nullable
                                        String additionalCustomerGroup2)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup2
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup2 - Specifies a customer-defined group of customers.
  - setAdditionalCustomerGroup3
```
public void setAdditionalCustomerGroup3(@Nullable
                                        String additionalCustomerGroup3)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup3
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup3 - Specifies a customer-defined group of customers.
  - setAdditionalCustomerGroup4
```
public void setAdditionalCustomerGroup4(@Nullable
                                        String additionalCustomerGroup4)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup4
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup4 - Specifies a customer-defined group of customers.
  - setAdditionalCustomerGroup5
```
public void setAdditionalCustomerGroup5(@Nullable
                                        String additionalCustomerGroup5)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup5
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup5 - Specifies a customer-defined group of customers.
  - setSlsDocIsRlvtForProofOfDeliv
```
public void setSlsDocIsRlvtForProofOfDeliv(@Nullable
                                           Boolean slsDocIsRlvtForProofOfDeliv)
```
    Constraints: none
    Original property name from the Odata EDM: SlsDocIsRlvtForProofOfDeliv
    
    Parameters:
    
    slsDocIsRlvtForProofOfDeliv - This indicator controls proof of delivery (POD) processing.
  - setCustomerTaxClassification1
```
public void setCustomerTaxClassification1(@Nullable
                                          String customerTaxClassification1)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification1
    
    The system copies the tax classification from the tax information stored in the customer master record of the goods recipient. During pricing, the system uses the tax classification and the country key (which identifies the customer location) to determine the relevant taxes. You can enter a different (alternative) tax classification in the order.
    
    Parameters:
    
    customerTaxClassification1 - Indicates whether the system takes account of taxes that are related to the customer for pricing (such as value-added tax).
  - setCustomerTaxClassification2
```
public void setCustomerTaxClassification2(@Nullable
                                          String customerTaxClassification2)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification2
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification2 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification3
```
public void setCustomerTaxClassification3(@Nullable
                                          String customerTaxClassification3)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification3
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification3 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification4
```
public void setCustomerTaxClassification4(@Nullable
                                          String customerTaxClassification4)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification4
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification4 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification5
```
public void setCustomerTaxClassification5(@Nullable
                                          String customerTaxClassification5)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification5
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification5 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification6
```
public void setCustomerTaxClassification6(@Nullable
                                          String customerTaxClassification6)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification6
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification6 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification7
```
public void setCustomerTaxClassification7(@Nullable
                                          String customerTaxClassification7)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification7
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification7 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification8
```
public void setCustomerTaxClassification8(@Nullable
                                          String customerTaxClassification8)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification8
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification8 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification9
```
public void setCustomerTaxClassification9(@Nullable
                                          String customerTaxClassification9)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification9
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification9 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setTaxDepartureCountry
```
public void setTaxDepartureCountry(@Nullable
                                   String taxDepartureCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: TaxDepartureCountry
    
    A different country or region needs to be entered for certain internal European transactions (chain transactions).
    
    Parameters:
    
    taxDepartureCountry - For tax determination, the country or region of departure is used as the plant country/region.
  - setVATRegistrationCountry
```
public void setVATRegistrationCountry(@Nullable
                                      String vATRegistrationCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: VATRegistrationCountry
    
    A different country or region needs to be entered for certain internal European transactions (chain transactions).
    
    Parameters:
    
    vATRegistrationCountry - For tax determination, the country or region of the ship-to party is used as the tax country or region of destination.
  - setSalesOrderApprovalReason
```
public void setSalesOrderApprovalReason(@Nullable
                                        String salesOrderApprovalReason)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrderApprovalReason
    
    Whenever an approval request reason is set and the corresponding workflow is defined, the sales document is considered relevant for approvals. The approval request reason consists of an ID and a description.You define that for customer ABC, sales quotations always have to be approved. The system automatically sets this reason when a sales quotation for this customer is created. It cannot be released without sending it to an approver first.
    
    Parameters:
    
    salesOrderApprovalReason - States in which cases an approval is needed.
  - setSalesDocApprovalStatus
```
public void setSalesDocApprovalStatus(@Nullable
                                      String salesDocApprovalStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SalesDocApprovalStatus
    
    Parameters:
    
    salesDocApprovalStatus - States whether a sales document is relevant for approvals and, if so, which approval stage it is in.
  - setOverallSDProcessStatus
```
public void setOverallSDProcessStatus(@Nullable
                                      String overallSDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDProcessStatus
    
    The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
    
    Parameters:
    
    overallSDProcessStatus - The processing status of the entire sales document.
  - setTotalCreditCheckStatus
```
public void setTotalCreditCheckStatus(@Nullable
                                      String totalCreditCheckStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalCreditCheckStatus
    
    Parameters:
    
    totalCreditCheckStatus - Overall Status of Credit Checks
  - setOverallTotalDeliveryStatus
```
public void setOverallTotalDeliveryStatus(@Nullable
                                          String overallTotalDeliveryStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallTotalDeliveryStatus
    
    Parameters:
    
    overallTotalDeliveryStatus - Overall Delivery Status (All Items)
  - setOverallSDDocumentRejectionSts
```
public void setOverallSDDocumentRejectionSts(@Nullable
                                             String overallSDDocumentRejectionSts)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDDocumentRejectionSts
    
    The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.
    
    Parameters:
    
    overallSDDocumentRejectionSts - Displays the rejection status of the entire sales document.
  - 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<SalesOrder>
    
    Returns:
    
    EDMX name of the entity collection identifier.
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<SalesOrder>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<SalesOrder>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<SalesOrder>
  - field
```
@Nonnull
public static <T> SalesOrderField<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> SalesOrderField<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<SalesOrder>
    
    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<SalesOrder>
  - 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<SalesOrder>
    
    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<SalesOrder>
    
    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<SalesOrder>
  - fetchItem
```
@Nonnull
public List<SalesOrderItem> fetchItem()
                                        throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderItem 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 SalesOrderItem 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<SalesOrderItem> getItemOrFetch()
                                             throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderItem entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried SalesOrder 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 SalesOrderItem 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<SalesOrderItem>> getItemIfPresent()
```
    Retrieval of associated SalesOrderItem entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property for an entity SalesOrder 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 SalesOrderItem entities. If not, an Option with result state empty is returned.
  - setItem
```
public void setItem(@Nonnull
                    List<SalesOrderItem> value)
```
    Overwrites the list of associated SalesOrderItem entities for the loaded navigation property to_Item.
    If the navigation property to_Item of a queried SalesOrder 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 SalesOrderItem entities.
  - addItem
```
public void addItem(SalesOrderItem... entity)
```
    Adds elements to the list of associated SalesOrderItem entities. This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried SalesOrder 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 SalesOrderItem entities.
  - fetchPartner
```
@Nonnull
public List<SalesOrderHeaderPartner> fetchPartner()
                                                    throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderHeaderPartner 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 SalesOrderHeaderPartner 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<SalesOrderHeaderPartner> getPartnerOrFetch()
                                                         throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderHeaderPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesOrder 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 SalesOrderHeaderPartner 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<SalesOrderHeaderPartner>> getPartnerIfPresent()
```
    Retrieval of associated SalesOrderHeaderPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property for an entity SalesOrder 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 SalesOrderHeaderPartner entities. If not, an Option with result state empty is returned.
  - setPartner
```
public void setPartner(@Nonnull
                       List<SalesOrderHeaderPartner> value)
```
    Overwrites the list of associated SalesOrderHeaderPartner entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesOrder 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 SalesOrderHeaderPartner entities.
  - addPartner
```
public void addPartner(SalesOrderHeaderPartner... entity)
```
    Adds elements to the list of associated SalesOrderHeaderPartner entities. This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesOrder 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 SalesOrderHeaderPartner entities.
  - fetchPaymentPlanItemDetails
```
@Nonnull
public List<SlsOrdPaymentPlanItemDetails> fetchPaymentPlanItemDetails()
                                                                        throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SlsOrdPaymentPlanItemDetails entities (one to many) associated with this entity. This corresponds to the OData navigation property to_PaymentPlanItemDetails.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SlsOrdPaymentPlanItemDetails 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.
  - getPaymentPlanItemDetailsOrFetch
```
@Nonnull
public List<SlsOrdPaymentPlanItemDetails> getPaymentPlanItemDetailsOrFetch()
                                                                             throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SlsOrdPaymentPlanItemDetails entities (one to many). This corresponds to the OData navigation property to_PaymentPlanItemDetails.
    If the navigation property to_PaymentPlanItemDetails of a queried SalesOrder 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 SlsOrdPaymentPlanItemDetails 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.
  - getPaymentPlanItemDetailsIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SlsOrdPaymentPlanItemDetails>> getPaymentPlanItemDetailsIfPresent()
```
    Retrieval of associated SlsOrdPaymentPlanItemDetails entities (one to many). This corresponds to the OData navigation property to_PaymentPlanItemDetails.
    If the navigation property for an entity SalesOrder 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_PaymentPlanItemDetails is already loaded, the result will contain the SlsOrdPaymentPlanItemDetails entities. If not, an Option with result state empty is returned.
  - setPaymentPlanItemDetails
```
public void setPaymentPlanItemDetails(@Nonnull
                                      List<SlsOrdPaymentPlanItemDetails> value)
```
    Overwrites the list of associated SlsOrdPaymentPlanItemDetails entities for the loaded navigation property to_PaymentPlanItemDetails.
    If the navigation property to_PaymentPlanItemDetails of a queried SalesOrder 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 SlsOrdPaymentPlanItemDetails entities.
  - addPaymentPlanItemDetails
```
public void addPaymentPlanItemDetails(SlsOrdPaymentPlanItemDetails... entity)
```
    Adds elements to the list of associated SlsOrdPaymentPlanItemDetails entities. This corresponds to the OData navigation property to_PaymentPlanItemDetails.
    If the navigation property to_PaymentPlanItemDetails of a queried SalesOrder 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 SlsOrdPaymentPlanItemDetails entities.
  - fetchPricingElement
```
@Nonnull
public List<SalesOrderHeaderPrElement> fetchPricingElement()
                                                             throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderHeaderPrElement 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 SalesOrderHeaderPrElement 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<SalesOrderHeaderPrElement> getPricingElementOrFetch()
                                                                  throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderHeaderPrElement entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesOrder 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 SalesOrderHeaderPrElement 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<SalesOrderHeaderPrElement>> getPricingElementIfPresent()
```
    Retrieval of associated SalesOrderHeaderPrElement entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property for an entity SalesOrder 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 SalesOrderHeaderPrElement entities. If not, an Option with result state empty is returned.
  - setPricingElement
```
public void setPricingElement(@Nonnull
                              List<SalesOrderHeaderPrElement> value)
```
    Overwrites the list of associated SalesOrderHeaderPrElement entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesOrder 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 SalesOrderHeaderPrElement entities.
  - addPricingElement
```
public void addPricingElement(SalesOrderHeaderPrElement... entity)
```
    Adds elements to the list of associated SalesOrderHeaderPrElement entities. This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesOrder 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 SalesOrderHeaderPrElement entities.
  - fetchText
```
@Nonnull
public List<SalesOrderText> fetchText()
                                        throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderText entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Text.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SalesOrderText 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.
  - getTextOrFetch
```
@Nonnull
public List<SalesOrderText> getTextOrFetch()
                                             throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderText entities (one to many). This corresponds to the OData navigation property to_Text.
    If the navigation property to_Text of a queried SalesOrder 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 SalesOrderText 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.
  - getTextIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SalesOrderText>> getTextIfPresent()
```
    Retrieval of associated SalesOrderText entities (one to many). This corresponds to the OData navigation property to_Text.
    If the navigation property for an entity SalesOrder 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_Text is already loaded, the result will contain the SalesOrderText entities. If not, an Option with result state empty is returned.
  - setText
```
public void setText(@Nonnull
                    List<SalesOrderText> value)
```
    Overwrites the list of associated SalesOrderText entities for the loaded navigation property to_Text.
    If the navigation property to_Text of a queried SalesOrder 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 SalesOrderText entities.
  - addText
```
public void addText(SalesOrderText... entity)
```
    Adds elements to the list of associated SalesOrderText entities. This corresponds to the OData navigation property to_Text.
    If the navigation property to_Text of a queried SalesOrder 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 SalesOrderText entities.
  - builder
```
@Nonnull
public static SalesOrder.SalesOrderBuilder 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.
  - getCreationDate
```
@Nullable
public LocalDateTime getCreationDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    Date on Which Record Was Created
  - getCreatedByUser
```
@Nullable
public String getCreatedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Returns:
    
    Name of Person Who Created Object
  - getLastChangeDate
```
@Nullable
public LocalDateTime getLastChangeDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Returns:
    
    Date of Last Change
  - getSenderBusinessSystemName
```
@Nullable
public String getSenderBusinessSystemName()
```
    Constraints: Not nullable, Maximum length: 60
    Original property name from the Odata EDM: SenderBusinessSystemName
    
    Returns:
    
    External Business System ID
  - getExternalDocumentID
```
@Nullable
public String getExternalDocumentID()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: ExternalDocumentID
    
    Returns:
    
    External Document ID
  - getLastChangeDateTime
```
@Nullable
public ZonedDateTime getLastChangeDateTime()
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Returns:
    
    The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).
  - getExternalDocLastChangeDateTime
```
@Nullable
public ZonedDateTime getExternalDocLastChangeDateTime()
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: ExternalDocLastChangeDateTime
    
    Returns:
    
    Timestamp for Revision of External Calls
  - 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).
  - getPurchaseOrderByShipToParty
```
@Nullable
public String getPurchaseOrderByShipToParty()
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByShipToParty
    
    The number is the link between the end customer's purchase order and the sales documents that you have created. You can use the end customer's number for correspondence with the customer, in particular for finding certain document information. If the number refers to a purchase order, you can also print documents that you wish to send to the end customer, such as the delivery note.
    
    Returns:
    
    Number used by the end customer for unique identification of the purchasing document (e.g. inquiry or purchase).
  - 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.
  - getTotalNetAmount
```
@Nullable
public BigDecimal getTotalNetAmount()
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: TotalNetAmount
    
    Returns:
    
    The total value of all items in the sales document, after any discounts and surcharges are taken into account. The value is expressed in the document currency.
  - getOverallDeliveryStatus
```
@Nullable
public String getOverallDeliveryStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallDeliveryStatus
    
    Returns:
    
    The delivery status of the sales document.
  - getTotalBlockStatus
```
@Nullable
public String getTotalBlockStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalBlockStatus
    
    The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
    
    Returns:
    
    Overall blocked status.
  - getOverallOrdReltdBillgStatus
```
@Nullable
public String getOverallOrdReltdBillgStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallOrdReltdBillgStatus
    
    The overall billing status tells you whether the sales order or delivery is relevant for billing, and, if so, to what extent billing has taken place.
    
    Returns:
    
    The overall billing status of the sales order or delivery.
  - getOverallSDDocReferenceStatus
```
@Nullable
public String getOverallSDDocReferenceStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDDocReferenceStatus
    
    The status message tells you whether one or more other sales documents have referenced this document partially, completely, or not at all.If you create a sales order by copying one item from a quotation that contains a number of items, the reference status for the quotation says that it has been only partially referenced.
    
    Returns:
    
    The reference status of the sales document as it relates to other sales documents.
  - 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.
  - getPriceDetnExchangeRate
```
@Nullable
public BigDecimal getPriceDetnExchangeRate()
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: PriceDetnExchangeRate
    
    Returns:
    
    Exchange Rate for Price Determination
  - getRequestedDeliveryDate
```
@Nullable
public LocalDateTime getRequestedDeliveryDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: RequestedDeliveryDate
    
    Returns:
    
    The date on which the customer would like ordered goods to be delivered.
  - 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.
  - getHeaderBillingBlockReason
```
@Nullable
public String getHeaderBillingBlockReason()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: HeaderBillingBlockReason
    
    The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
    
    Returns:
    
    Indicates if the entire sales document is blocked for billing.
  - getDeliveryBlockReason
```
@Nullable
public String getDeliveryBlockReason()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryBlockReason
    
    The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
    
    Returns:
    
    Indicates if an entire sales document (a sales order, for example) is blocked for delivery.
  - getDeliveryDateTypeRule
```
@Nullable
public String getDeliveryDateTypeRule()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DeliveryDateTypeRule
    
    You can choose one of the following options:The goods should be delivered on the requested delivery date or later. Note that there is no guarantee that the goods will not be delivered earlier.The goods must be delivered exactly on the confirmed delivery date.The goods must be delivered by the confirmed delivery date (that is, on the date or earlier).You can set the delivery date rule on header level to set a default for any items that you create afterwards.In Transportation Management (TM), this field has the following implications:If you want the goods to be delivered on the requested delivery date or later, the delivery date/time is used as the earliest requested delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered on the confirmed delivery date, the start of the delivery date is used as the earliest acceptable delivery date/time and the end of the delivery date as the latest acceptable delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered by the confirmed delivery date, the end of the delivery date is used as the latest acceptable delivery date/time of the freight unit which contains the sales order item.Note: If you want to the goods to be delivered on or by the confirmed delivery date, the system ignores the rule for pick-up and delivery window and the condition for pick-up and delivery window determination which you have defined in the freight unit type for the delivery stop.
    
    Returns:
    
    Indicates when the ordered goods should be delivered.
  - 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).
  - getCustomerPriceGroup
```
@Nullable
public String getCustomerPriceGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerPriceGroup
    
    You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.
    
    Returns:
    
    A grouping of customers who share the same pricing requirements.
  - getPriceListType
```
@Nullable
public String getPriceListType()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: PriceListType
    
    You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.
    
    Returns:
    
    Identifies a price list or other condition type (for example, a surcharge or discount).
  - 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.
  - getFixedValueDate
```
@Nullable
public LocalDateTime getFixedValueDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: FixedValueDate
    
    If you enter a date in this field, you cannot enter a value in the additional value days field.
    
    Returns:
    
    The date on which the terms of payment related to the sales document become effective.
  - getAssignmentReference
```
@Nullable
public String getAssignmentReference()
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: AssignmentReference
    
    The line items of an account are displayed in sort sequence according to the content of the field.The allocation number is set in the billing document in accordance with control in document flow and transferred to the financial journal entry.It is possible to set the customer purchase order number, the customer order number, the delivery number or the external delivery number as allocation numbers.The field is a separating criterion in the billing document.
    
    Returns:
    
    The allocation is additional information in the customer line item of the journal entry.
  - getReferenceSDDocument
```
@Nullable
public String getReferenceSDDocument()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceSDDocument
    
    Returns:
    
    Identifies the sales order to which the delivery refers.
  - getReferenceSDDocumentCategory
```
@Nullable
public String getReferenceSDDocumentCategory()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ReferenceSDDocumentCategory
    
    Returns:
    
    Specifies the sales document category of the preceding sales, delivery, or billing document.
  - getAccountingDocExternalReference
```
@Nullable
public String getAccountingDocExternalReference()
```
    Constraints: Not nullable, Maximum length: 16
    Original property name from the Odata EDM: AccountingDocExternalReference
    
    The reference document number serves as a search criterion when displaying or changing documents. In correspondence, the refererence document number is sometimes printed instead of the document number.The reference number is set in the document flow according to control and taken into the financial journal entry.You can set the customer order number, the order number, the delivery number, the billing number or the external delivery number as reference number.The field is a seperation criterion in the billing document.
    
    Returns:
    
    The reference document number contains the document number with the business partner
  - getCustomerAccountAssignmentGroup
```
@Nullable
public String getCustomerAccountAssignmentGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerAccountAssignmentGroup
    
    The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
    
    Returns:
    
    The account assignment group to which the system automatically posts the sales document.
  - getAccountingExchangeRate
```
@Nullable
public BigDecimal getAccountingExchangeRate()
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: AccountingExchangeRate
    
    Your system is configured in such a way that it expects:No prefix (leading sign) for direct ratesA "" as prefix (leading sign) for direct ratesNo prefix for indirect ratesA "" as prefix for indirect rates
    
    Returns:
    
    The exchange rate that the system applies when you create an invoice.
  - getCustomerGroup
```
@Nullable
public String getCustomerGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerGroup
    
    Returns:
    
    Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics.
  - getAdditionalCustomerGroup1
```
@Nullable
public String getAdditionalCustomerGroup1()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup1
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup2
```
@Nullable
public String getAdditionalCustomerGroup2()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup2
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup3
```
@Nullable
public String getAdditionalCustomerGroup3()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup3
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup4
```
@Nullable
public String getAdditionalCustomerGroup4()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup4
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup5
```
@Nullable
public String getAdditionalCustomerGroup5()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: AdditionalCustomerGroup5
    
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getSlsDocIsRlvtForProofOfDeliv
```
@Nullable
public Boolean getSlsDocIsRlvtForProofOfDeliv()
```
    Constraints: none
    Original property name from the Odata EDM: SlsDocIsRlvtForProofOfDeliv
    
    Returns:
    
    This indicator controls proof of delivery (POD) processing.
  - getCustomerTaxClassification1
```
@Nullable
public String getCustomerTaxClassification1()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification1
    
    The system copies the tax classification from the tax information stored in the customer master record of the goods recipient. During pricing, the system uses the tax classification and the country key (which identifies the customer location) to determine the relevant taxes. You can enter a different (alternative) tax classification in the order.
    
    Returns:
    
    Indicates whether the system takes account of taxes that are related to the customer for pricing (such as value-added tax).
  - getCustomerTaxClassification2
```
@Nullable
public String getCustomerTaxClassification2()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification2
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification3
```
@Nullable
public String getCustomerTaxClassification3()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification3
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification4
```
@Nullable
public String getCustomerTaxClassification4()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification4
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification5
```
@Nullable
public String getCustomerTaxClassification5()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification5
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification6
```
@Nullable
public String getCustomerTaxClassification6()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification6
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification7
```
@Nullable
public String getCustomerTaxClassification7()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification7
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification8
```
@Nullable
public String getCustomerTaxClassification8()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification8
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification9
```
@Nullable
public String getCustomerTaxClassification9()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification9
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getTaxDepartureCountry
```
@Nullable
public String getTaxDepartureCountry()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: TaxDepartureCountry
    
    A different country or region needs to be entered for certain internal European transactions (chain transactions).
    
    Returns:
    
    For tax determination, the country or region of departure is used as the plant country/region.
  - getVATRegistrationCountry
```
@Nullable
public String getVATRegistrationCountry()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: VATRegistrationCountry
    
    A different country or region needs to be entered for certain internal European transactions (chain transactions).
    
    Returns:
    
    For tax determination, the country or region of the ship-to party is used as the tax country or region of destination.
  - getSalesOrderApprovalReason
```
@Nullable
public String getSalesOrderApprovalReason()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrderApprovalReason
    
    Whenever an approval request reason is set and the corresponding workflow is defined, the sales document is considered relevant for approvals. The approval request reason consists of an ID and a description.You define that for customer ABC, sales quotations always have to be approved. The system automatically sets this reason when a sales quotation for this customer is created. It cannot be released without sending it to an approver first.
    
    Returns:
    
    States in which cases an approval is needed.
  - getSalesDocApprovalStatus
```
@Nullable
public String getSalesDocApprovalStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SalesDocApprovalStatus
    
    Returns:
    
    States whether a sales document is relevant for approvals and, if so, which approval stage it is in.
  - getOverallSDProcessStatus
```
@Nullable
public String getOverallSDProcessStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDProcessStatus
    
    The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
    
    Returns:
    
    The processing status of the entire sales document.
  - getTotalCreditCheckStatus
```
@Nullable
public String getTotalCreditCheckStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalCreditCheckStatus
    
    Returns:
    
    Overall Status of Credit Checks
  - getOverallTotalDeliveryStatus
```
@Nullable
public String getOverallTotalDeliveryStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallTotalDeliveryStatus
    
    Returns:
    
    Overall Delivery Status (All Items)
  - getOverallSDDocumentRejectionSts
```
@Nullable
public String getOverallSDDocumentRejectionSts()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDDocumentRejectionSts
    
    The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.
    
    Returns:
    
    Displays the rejection status of the entire sales document.
  - toString
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class VdmObject<SalesOrder>
  - equals
```
public boolean equals(@Nullable
                      Object o)
```
    Overrides:
    
    equals in class VdmObject<SalesOrder>
  - canEqual
```
protected boolean canEqual(@Nullable
                           Object other)
```
    Overrides:
    
    canEqual in class VdmObject<SalesOrder>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<SalesOrder>

Class SalesOrder

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

CREATION_DATE

CREATED_BY_USER

LAST_CHANGE_DATE

SENDER_BUSINESS_SYSTEM_NAME

EXTERNAL_DOCUMENT_ID

LAST_CHANGE_DATE_TIME

EXTERNAL_DOC_LAST_CHANGE_DATE_TIME

PURCHASE_ORDER_BY_CUSTOMER

PURCHASE_ORDER_BY_SHIP_TO_PARTY

CUSTOMER_PURCHASE_ORDER_TYPE

CUSTOMER_PURCHASE_ORDER_DATE

SALES_ORDER_DATE

TOTAL_NET_AMOUNT

OVERALL_DELIVERY_STATUS

TOTAL_BLOCK_STATUS

OVERALL_ORD_RELTD_BILLG_STATUS

OVERALL_SD_DOC_REFERENCE_STATUS

TRANSACTION_CURRENCY

SD_DOCUMENT_REASON

PRICING_DATE

PRICE_DETN_EXCHANGE_RATE

REQUESTED_DELIVERY_DATE

SHIPPING_CONDITION

COMPLETE_DELIVERY_IS_DEFINED

SHIPPING_TYPE

HEADER_BILLING_BLOCK_REASON

DELIVERY_BLOCK_REASON

DELIVERY_DATE_TYPE_RULE

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

INCOTERMS_VERSION

CUSTOMER_PRICE_GROUP

PRICE_LIST_TYPE

CUSTOMER_PAYMENT_TERMS

PAYMENT_METHOD

FIXED_VALUE_DATE

ASSIGNMENT_REFERENCE

REFERENCE_SD_DOCUMENT

REFERENCE_SD_DOCUMENT_CATEGORY

ACCOUNTING_DOC_EXTERNAL_REFERENCE

CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP

ACCOUNTING_EXCHANGE_RATE

CUSTOMER_GROUP

ADDITIONAL_CUSTOMER_GROUP1

ADDITIONAL_CUSTOMER_GROUP2

ADDITIONAL_CUSTOMER_GROUP3

ADDITIONAL_CUSTOMER_GROUP4

ADDITIONAL_CUSTOMER_GROUP5

SLS_DOC_IS_RLVT_FOR_PROOF_OF_DELIV

CUSTOMER_TAX_CLASSIFICATION1

CUSTOMER_TAX_CLASSIFICATION2

CUSTOMER_TAX_CLASSIFICATION3

CUSTOMER_TAX_CLASSIFICATION4

CUSTOMER_TAX_CLASSIFICATION5

CUSTOMER_TAX_CLASSIFICATION6

CUSTOMER_TAX_CLASSIFICATION7

CUSTOMER_TAX_CLASSIFICATION8

CUSTOMER_TAX_CLASSIFICATION9