CustomerSalesArea (SAP Cloud SDK - Parent POM 2.25.0 API)

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

```
public class CustomerSalesArea
extends VdmEntity<CustomerSalesArea>
```
Customer Sales Area

Original entity name from the Odata EDM: A_CustomerSalesAreaType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class CustomerSalesArea.CustomerSalesAreaBuilder
Helper class to allow for fluent creation of CustomerSalesArea instances.

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

Field Summary

Fields
Modifier and Type	Field and Description
`static CustomerSalesAreaField<String>`	`ACCOUNT_BY_CUSTOMER` Use with available fluent helpers to apply the AccountByCustomer field to query operations.
`static CustomerSalesAreaSelectable`	`ALL_FIELDS` Selector for all available fields of CustomerSalesArea.
`static CustomerSalesAreaField<String>`	`AUTHORIZATION_GROUP` Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
`static CustomerSalesAreaField<String>`	`BILLING_IS_BLOCKED_FOR_CUSTOMER` Use with available fluent helpers to apply the BillingIsBlockedForCustomer field to query operations.
`static CustomerSalesAreaField<Boolean>`	`COMPLETE_DELIVERY_IS_DEFINED` Use with available fluent helpers to apply the CompleteDeliveryIsDefined field to query operations.
`static CustomerSalesAreaField<String>`	`CURRENCY` Use with available fluent helpers to apply the Currency field to query operations.
`static CustomerSalesAreaField<String>`	`CUSTOMER` Use with available fluent helpers to apply the Customer field to query operations.
`static CustomerSalesAreaField<String>`	`CUSTOMER_ABC_CLASSIFICATION` Use with available fluent helpers to apply the CustomerABCClassification field to query operations.
`static CustomerSalesAreaField<String>`	`CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP` Use with available fluent helpers to apply the CustomerAccountAssignmentGroup field to query operations.
`static CustomerSalesAreaField<String>`	`CUSTOMER_ACCOUNT_GROUP` Use with available fluent helpers to apply the CustomerAccountGroup field to query operations.
`static CustomerSalesAreaField<String>`	`CUSTOMER_GROUP` Use with available fluent helpers to apply the CustomerGroup field to query operations.
`static CustomerSalesAreaField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static CustomerSalesAreaField<String>`	`CUSTOMER_PRICE_GROUP` Use with available fluent helpers to apply the CustomerPriceGroup field to query operations.
`static CustomerSalesAreaField<String>`	`CUSTOMER_PRICING_PROCEDURE` Use with available fluent helpers to apply the CustomerPricingProcedure field to query operations.
`static CustomerSalesAreaField<Boolean>`	`DELETION_INDICATOR` Use with available fluent helpers to apply the DeletionIndicator field to query operations.
`static CustomerSalesAreaField<String>`	`DELIVERY_IS_BLOCKED_FOR_CUSTOMER` Use with available fluent helpers to apply the DeliveryIsBlockedForCustomer field to query operations.
`static CustomerSalesAreaField<String>`	`DELIVERY_PRIORITY` Use with available fluent helpers to apply the DeliveryPriority field to query operations.
`static CustomerSalesAreaField<String>`	`DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the DistributionChannel field to query operations.
`static CustomerSalesAreaField<String>`	`DIVISION` Use with available fluent helpers to apply the Division field to query operations.
`static CustomerSalesAreaField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static CustomerSalesAreaField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static CustomerSalesAreaField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static CustomerSalesAreaField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static CustomerSalesAreaField<String>`	`INCOTERMS_VERSION` Use with available fluent helpers to apply the IncotermsVersion field to query operations.
`static CustomerSalesAreaField<String>`	`INVOICE_DATE` Use with available fluent helpers to apply the InvoiceDate field to query operations.
`static CustomerSalesAreaField<String>`	`ITEM_ORDER_PROBABILITY_IN_PERCENT` Use with available fluent helpers to apply the ItemOrderProbabilityInPercent field to query operations.
`static CustomerSalesAreaField<Boolean>`	`ORDER_COMBINATION_IS_ALLOWED` Use with available fluent helpers to apply the OrderCombinationIsAllowed field to query operations.
`static CustomerSalesAreaField<String>`	`ORDER_IS_BLOCKED_FOR_CUSTOMER` Use with available fluent helpers to apply the OrderIsBlockedForCustomer field to query operations.
`static CustomerSalesAreaField<String>`	`PARTIAL_DELIVERY_IS_ALLOWED` Use with available fluent helpers to apply the PartialDeliveryIsAllowed field to query operations.
`static CustomerSalesAreaField<String>`	`PRICE_LIST_TYPE` Use with available fluent helpers to apply the PriceListType field to query operations.
`static CustomerSalesAreaField<String>`	`SALES_DISTRICT` Use with available fluent helpers to apply the SalesDistrict field to query operations.
`static CustomerSalesAreaField<String>`	`SALES_GROUP` Use with available fluent helpers to apply the SalesGroup field to query operations.
`static CustomerSalesAreaField<String>`	`SALES_OFFICE` Use with available fluent helpers to apply the SalesOffice field to query operations.
`static CustomerSalesAreaField<String>`	`SALES_ORGANIZATION` Use with available fluent helpers to apply the SalesOrganization field to query operations.
`static CustomerSalesAreaField<String>`	`SHIPPING_CONDITION` Use with available fluent helpers to apply the ShippingCondition field to query operations.
`static CustomerSalesAreaField<String>`	`SUPPLYING_PLANT` Use with available fluent helpers to apply the SupplyingPlant field to query operations.
`static CustomerSalesAreaLink<CustSalesPartnerFunc>`	`TO_PARTNER_FUNCTION` Use with available fluent helpers to apply the to_PartnerFunction navigation property to query operations.
`static CustomerSalesAreaLink<CustomerSalesAreaTax>`	`TO_SALES_AREA_TAX` Use with available fluent helpers to apply the to_SalesAreaTax navigation property to query operations.

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

Constructor Summary

Constructors
Constructor and Description
`CustomerSalesArea()`
CustomerSalesArea(String customer, String salesOrganization, String distributionChannel, String division, String accountByCustomer, String authorizationGroup, String billingIsBlockedForCustomer, Boolean completeDeliveryIsDefined, String currency, String customerABCClassification, String customerAccountAssignmentGroup, String customerGroup, String customerPaymentTerms, String customerPriceGroup, String customerPricingProcedure, String deliveryIsBlockedForCustomer, String deliveryPriority, String incotermsClassification, String incotermsLocation2, String incotermsVersion, String incotermsLocation1, Boolean deletionIndicator, String incotermsTransferLocation, String invoiceDate, String itemOrderProbabilityInPercent, Boolean orderCombinationIsAllowed, String orderIsBlockedForCustomer, String partialDeliveryIsAllowed, String priceListType, String salesGroup, String salesOffice, String shippingCondition, String supplyingPlant, String salesDistrict, String customerAccountGroup, List<CustSalesPartnerFunc> toPartnerFunction, List<CustomerSalesAreaTax> toSalesAreaTax)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods Deprecated Methods
Modifier and Type	Method and Description
`void`	`addPartnerFunction(CustSalesPartnerFunc... entity)` Adds elements to the list of associated CustSalesPartnerFunc entities.
`void`	`addSalesAreaTax(CustomerSalesAreaTax... entity)` Adds elements to the list of associated CustomerSalesAreaTax entities.
`void`	`attachToService(String servicePath, ErpConfigContext configContext)` Sets the service path and ERP configuration context for the fetch commands of this entity.
`static CustomerSalesArea.CustomerSalesAreaBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`List<CustSalesPartnerFunc>`	`fetchPartnerFunction()` Fetches the CustSalesPartnerFunc entities (one to many) associated with this entity.
`List<CustomerSalesAreaTax>`	`fetchSalesAreaTax()` Fetches the CustomerSalesAreaTax entities (one to many) associated with this entity.
`static <T> CustomerSalesAreaField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> CustomerSalesAreaField<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`	`getAccountByCustomer()` Constraints: Not nullable, Maximum length: 12
`String`	`getAuthorizationGroup()` Constraints: Not nullable, Maximum length: 4
`String`	`getBillingIsBlockedForCustomer()` Constraints: Not nullable, Maximum length: 2
`Boolean`	`getCompleteDeliveryIsDefined()` Constraints: none
`String`	`getCurrency()` Constraints: Not nullable, Maximum length: 5
`String`	`getCustomer()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getCustomerABCClassification()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerAccountAssignmentGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerAccountGroup()` Constraints: Not nullable, Maximum length: 4
`String`	`getCustomerGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4
`String`	`getCustomerPriceGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerPricingProcedure()` Constraints: Not nullable, Maximum length: 2
`protected String`	`getDefaultServicePath()`
`Boolean`	`getDeletionIndicator()` Constraints: none
`String`	`getDeliveryIsBlockedForCustomer()` Constraints: Not nullable, Maximum length: 2
`String`	`getDeliveryPriority()` Constraints: Not nullable, Maximum length: 2
`String`	`getDistributionChannel()` (Key Field) Constraints: Not nullable, Maximum length: 2
`String`	`getDivision()` (Key Field) Constraints: Not nullable, Maximum length: 2
`protected String`	`getEntityCollection()`
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g.
`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
`String`	`getInvoiceDate()` Constraints: Not nullable, Maximum length: 2
`String`	`getItemOrderProbabilityInPercent()` Constraints: Not nullable, Maximum length: 3
`protected Map<String,Object>`	`getKey()`
`Boolean`	`getOrderCombinationIsAllowed()` Constraints: none
`String`	`getOrderIsBlockedForCustomer()` Constraints: Not nullable, Maximum length: 2
`String`	`getPartialDeliveryIsAllowed()` Constraints: Not nullable, Maximum length: 1
`Optional<List<CustSalesPartnerFunc>>`	`getPartnerFunctionIfPresent()` Retrieval of associated CustSalesPartnerFunc entities (one to many).
`List<CustSalesPartnerFunc>`	`getPartnerFunctionOrFetch()` Retrieval of associated CustSalesPartnerFunc entities (one to many).
`String`	`getPriceListType()` Constraints: Not nullable, Maximum length: 2
`Optional<List<CustomerSalesAreaTax>>`	`getSalesAreaTaxIfPresent()` Retrieval of associated CustomerSalesAreaTax entities (one to many).
`List<CustomerSalesAreaTax>`	`getSalesAreaTaxOrFetch()` Retrieval of associated CustomerSalesAreaTax entities (one to many).
`String`	`getSalesDistrict()` Constraints: Not nullable, Maximum length: 6
`String`	`getSalesGroup()` Constraints: Not nullable, Maximum length: 3
`String`	`getSalesOffice()` Constraints: Not nullable, Maximum length: 4
`String`	`getSalesOrganization()` (Key Field) Constraints: Not nullable, Maximum length: 4
`String`	`getShippingCondition()` Constraints: Not nullable, Maximum length: 2
`String`	`getSupplyingPlant()` Constraints: Not nullable, Maximum length: 4
`Class<CustomerSalesArea>`	`getType()`
`int`	`hashCode()`
`void`	`setAccountByCustomer(String accountByCustomer)` Constraints: Not nullable, Maximum length: 12
`void`	`setAuthorizationGroup(String authorizationGroup)` Constraints: Not nullable, Maximum length: 4
`void`	`setBillingIsBlockedForCustomer(String billingIsBlockedForCustomer)` Constraints: Not nullable, Maximum length: 2
`void`	`setCompleteDeliveryIsDefined(Boolean completeDeliveryIsDefined)` Constraints: none
`void`	`setCurrency(String currency)` Constraints: Not nullable, Maximum length: 5
`void`	`setCustomer(String customer)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setCustomerABCClassification(String customerABCClassification)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerAccountAssignmentGroup(String customerAccountAssignmentGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerAccountGroup(String customerAccountGroup)` Constraints: Not nullable, Maximum length: 4
`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`	`setCustomerPricingProcedure(String customerPricingProcedure)` Constraints: Not nullable, Maximum length: 2
`void`	`setDeletionIndicator(Boolean deletionIndicator)` Constraints: none
`void`	`setDeliveryIsBlockedForCustomer(String deliveryIsBlockedForCustomer)` Constraints: Not nullable, Maximum length: 2
`void`	`setDeliveryPriority(String deliveryPriority)` Constraints: Not nullable, Maximum length: 2
`void`	`setDistributionChannel(String distributionChannel)` (Key Field) Constraints: Not nullable, Maximum length: 2
`void`	`setDivision(String division)` (Key Field) Constraints: Not nullable, Maximum length: 2
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Deprecated. Use `attachToService(String, ErpConfigContext)` instead.
`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`	`setInvoiceDate(String invoiceDate)` Constraints: Not nullable, Maximum length: 2
`void`	`setItemOrderProbabilityInPercent(String itemOrderProbabilityInPercent)` Constraints: Not nullable, Maximum length: 3
`void`	`setOrderCombinationIsAllowed(Boolean orderCombinationIsAllowed)` Constraints: none
`void`	`setOrderIsBlockedForCustomer(String orderIsBlockedForCustomer)` Constraints: Not nullable, Maximum length: 2
`void`	`setPartialDeliveryIsAllowed(String partialDeliveryIsAllowed)` Constraints: Not nullable, Maximum length: 1
`void`	`setPartnerFunction(List<CustSalesPartnerFunc> value)` Overwrites the list of associated CustSalesPartnerFunc entities for the loaded navigation property to_PartnerFunction.
`void`	`setPriceListType(String priceListType)` Constraints: Not nullable, Maximum length: 2
`void`	`setSalesAreaTax(List<CustomerSalesAreaTax> value)` Overwrites the list of associated CustomerSalesAreaTax entities for the loaded navigation property to_SalesAreaTax.
`void`	`setSalesDistrict(String salesDistrict)` Constraints: Not nullable, Maximum length: 6
`void`	`setSalesGroup(String salesGroup)` Constraints: Not nullable, Maximum length: 3
`void`	`setSalesOffice(String salesOffice)` Constraints: Not nullable, Maximum length: 4
`void`	`setSalesOrganization(String salesOrganization)` (Key Field) Constraints: Not nullable, Maximum length: 4
`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`	`setSupplyingPlant(String supplyingPlant)` Constraints: Not nullable, Maximum length: 4
`protected Map<String,Object>`	`toMapOfFields()`
`protected Map<String,Object>`	`toMapOfNavigationProperties()`
`String`	`toString()`

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

Methods inherited from class com.sap.cloud.sdk.s4hana.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 CustomerSalesAreaSelectable ALL_FIELDS
```
    Selector for all available fields of CustomerSalesArea.
  - CUSTOMER
```
public static final CustomerSalesAreaField<String> CUSTOMER
```
    Use with available fluent helpers to apply the Customer field to query operations.
  - SALES_ORGANIZATION
```
public static final CustomerSalesAreaField<String> SALES_ORGANIZATION
```
    Use with available fluent helpers to apply the SalesOrganization field to query operations.
  - DISTRIBUTION_CHANNEL
```
public static final CustomerSalesAreaField<String> DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the DistributionChannel field to query operations.
  - DIVISION
```
public static final CustomerSalesAreaField<String> DIVISION
```
    Use with available fluent helpers to apply the Division field to query operations.
  - ACCOUNT_BY_CUSTOMER
```
public static final CustomerSalesAreaField<String> ACCOUNT_BY_CUSTOMER
```
    Use with available fluent helpers to apply the AccountByCustomer field to query operations.
  - AUTHORIZATION_GROUP
```
public static final CustomerSalesAreaField<String> AUTHORIZATION_GROUP
```
    Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
  - BILLING_IS_BLOCKED_FOR_CUSTOMER
```
public static final CustomerSalesAreaField<String> BILLING_IS_BLOCKED_FOR_CUSTOMER
```
    Use with available fluent helpers to apply the BillingIsBlockedForCustomer field to query operations.
  - COMPLETE_DELIVERY_IS_DEFINED
```
public static final CustomerSalesAreaField<Boolean> COMPLETE_DELIVERY_IS_DEFINED
```
    Use with available fluent helpers to apply the CompleteDeliveryIsDefined field to query operations.
  - CURRENCY
```
public static final CustomerSalesAreaField<String> CURRENCY
```
    Use with available fluent helpers to apply the Currency field to query operations.
  - CUSTOMER_ABC_CLASSIFICATION
```
public static final CustomerSalesAreaField<String> CUSTOMER_ABC_CLASSIFICATION
```
    Use with available fluent helpers to apply the CustomerABCClassification field to query operations.
  - CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
```
public static final CustomerSalesAreaField<String> CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
```
    Use with available fluent helpers to apply the CustomerAccountAssignmentGroup field to query operations.
  - CUSTOMER_GROUP
```
public static final CustomerSalesAreaField<String> CUSTOMER_GROUP
```
    Use with available fluent helpers to apply the CustomerGroup field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final CustomerSalesAreaField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - CUSTOMER_PRICE_GROUP
```
public static final CustomerSalesAreaField<String> CUSTOMER_PRICE_GROUP
```
    Use with available fluent helpers to apply the CustomerPriceGroup field to query operations.
  - CUSTOMER_PRICING_PROCEDURE
```
public static final CustomerSalesAreaField<String> CUSTOMER_PRICING_PROCEDURE
```
    Use with available fluent helpers to apply the CustomerPricingProcedure field to query operations.
  - DELIVERY_IS_BLOCKED_FOR_CUSTOMER
```
public static final CustomerSalesAreaField<String> DELIVERY_IS_BLOCKED_FOR_CUSTOMER
```
    Use with available fluent helpers to apply the DeliveryIsBlockedForCustomer field to query operations.
  - DELIVERY_PRIORITY
```
public static final CustomerSalesAreaField<String> DELIVERY_PRIORITY
```
    Use with available fluent helpers to apply the DeliveryPriority field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final CustomerSalesAreaField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_LOCATION2
```
public static final CustomerSalesAreaField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - INCOTERMS_VERSION
```
public static final CustomerSalesAreaField<String> INCOTERMS_VERSION
```
    Use with available fluent helpers to apply the IncotermsVersion field to query operations.
  - INCOTERMS_LOCATION1
```
public static final CustomerSalesAreaField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - DELETION_INDICATOR
```
public static final CustomerSalesAreaField<Boolean> DELETION_INDICATOR
```
    Use with available fluent helpers to apply the DeletionIndicator field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final CustomerSalesAreaField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INVOICE_DATE
```
public static final CustomerSalesAreaField<String> INVOICE_DATE
```
    Use with available fluent helpers to apply the InvoiceDate field to query operations.
  - ITEM_ORDER_PROBABILITY_IN_PERCENT
```
public static final CustomerSalesAreaField<String> ITEM_ORDER_PROBABILITY_IN_PERCENT
```
    Use with available fluent helpers to apply the ItemOrderProbabilityInPercent field to query operations.
  - ORDER_COMBINATION_IS_ALLOWED
```
public static final CustomerSalesAreaField<Boolean> ORDER_COMBINATION_IS_ALLOWED
```
    Use with available fluent helpers to apply the OrderCombinationIsAllowed field to query operations.
  - ORDER_IS_BLOCKED_FOR_CUSTOMER
```
public static final CustomerSalesAreaField<String> ORDER_IS_BLOCKED_FOR_CUSTOMER
```
    Use with available fluent helpers to apply the OrderIsBlockedForCustomer field to query operations.
  - PARTIAL_DELIVERY_IS_ALLOWED
```
public static final CustomerSalesAreaField<String> PARTIAL_DELIVERY_IS_ALLOWED
```
    Use with available fluent helpers to apply the PartialDeliveryIsAllowed field to query operations.
  - PRICE_LIST_TYPE
```
public static final CustomerSalesAreaField<String> PRICE_LIST_TYPE
```
    Use with available fluent helpers to apply the PriceListType field to query operations.
  - SALES_GROUP
```
public static final CustomerSalesAreaField<String> SALES_GROUP
```
    Use with available fluent helpers to apply the SalesGroup field to query operations.
  - SALES_OFFICE
```
public static final CustomerSalesAreaField<String> SALES_OFFICE
```
    Use with available fluent helpers to apply the SalesOffice field to query operations.
  - SHIPPING_CONDITION
```
public static final CustomerSalesAreaField<String> SHIPPING_CONDITION
```
    Use with available fluent helpers to apply the ShippingCondition field to query operations.
  - SUPPLYING_PLANT
```
public static final CustomerSalesAreaField<String> SUPPLYING_PLANT
```
    Use with available fluent helpers to apply the SupplyingPlant field to query operations.
  - SALES_DISTRICT
```
public static final CustomerSalesAreaField<String> SALES_DISTRICT
```
    Use with available fluent helpers to apply the SalesDistrict field to query operations.
  - CUSTOMER_ACCOUNT_GROUP
```
public static final CustomerSalesAreaField<String> CUSTOMER_ACCOUNT_GROUP
```
    Use with available fluent helpers to apply the CustomerAccountGroup field to query operations.
  - TO_PARTNER_FUNCTION
```
public static final CustomerSalesAreaLink<CustSalesPartnerFunc> TO_PARTNER_FUNCTION
```
    Use with available fluent helpers to apply the to_PartnerFunction navigation property to query operations.
  - TO_SALES_AREA_TAX
```
public static final CustomerSalesAreaLink<CustomerSalesAreaTax> TO_SALES_AREA_TAX
```
    Use with available fluent helpers to apply the to_SalesAreaTax navigation property to query operations.
- Constructor Detail
  - CustomerSalesArea
```
public CustomerSalesArea()
```
  - CustomerSalesArea
```
public CustomerSalesArea(@Nullable
                         String customer,
                         @Nullable
                         String salesOrganization,
                         @Nullable
                         String distributionChannel,
                         @Nullable
                         String division,
                         @Nullable
                         String accountByCustomer,
                         @Nullable
                         String authorizationGroup,
                         @Nullable
                         String billingIsBlockedForCustomer,
                         @Nullable
                         Boolean completeDeliveryIsDefined,
                         @Nullable
                         String currency,
                         @Nullable
                         String customerABCClassification,
                         @Nullable
                         String customerAccountAssignmentGroup,
                         @Nullable
                         String customerGroup,
                         @Nullable
                         String customerPaymentTerms,
                         @Nullable
                         String customerPriceGroup,
                         @Nullable
                         String customerPricingProcedure,
                         @Nullable
                         String deliveryIsBlockedForCustomer,
                         @Nullable
                         String deliveryPriority,
                         @Nullable
                         String incotermsClassification,
                         @Nullable
                         String incotermsLocation2,
                         @Nullable
                         String incotermsVersion,
                         @Nullable
                         String incotermsLocation1,
                         @Nullable
                         Boolean deletionIndicator,
                         @Nullable
                         String incotermsTransferLocation,
                         @Nullable
                         String invoiceDate,
                         @Nullable
                         String itemOrderProbabilityInPercent,
                         @Nullable
                         Boolean orderCombinationIsAllowed,
                         @Nullable
                         String orderIsBlockedForCustomer,
                         @Nullable
                         String partialDeliveryIsAllowed,
                         @Nullable
                         String priceListType,
                         @Nullable
                         String salesGroup,
                         @Nullable
                         String salesOffice,
                         @Nullable
                         String shippingCondition,
                         @Nullable
                         String supplyingPlant,
                         @Nullable
                         String salesDistrict,
                         @Nullable
                         String customerAccountGroup,
                         List<CustSalesPartnerFunc> toPartnerFunction,
                         List<CustomerSalesAreaTax> toSalesAreaTax)
```
- Method Detail
  - getType
```
@Nonnull
public Class<CustomerSalesArea> getType()
```
    Specified by:
    
    getType in class VdmObject<CustomerSalesArea>
    
    Returns:
    
    The class of this object.
  - setCustomer
```
public void setCustomer(@Nullable
                        String customer)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Customer
    
    Parameters:
    
    customer - Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.
  - setSalesOrganization
```
public void setSalesOrganization(@Nullable
                                 String salesOrganization)
```
    (Key Field) 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)
```
    (Key Field) 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.
  - setDivision
```
public void setDivision(@Nullable
                        String division)
```
    (Key Field) Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: Division
    
    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:
    
    division - 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.
  - setAccountByCustomer
```
public void setAccountByCustomer(@Nullable
                                 String accountByCustomer)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: AccountByCustomer
    
    Parameters:
    
    accountByCustomer - This field contains the account number your company is listed under at the customer or vendor.
  - setAuthorizationGroup
```
public void setAuthorizationGroup(@Nullable
                                  String authorizationGroup)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: AuthorizationGroup
    
    In order to carry out a specific activity, the user must have authorization for the combination of the activity and the authorization group.
    
    Parameters:
    
    authorizationGroup - The authorization group enables you protect access to certain objects.
  - setBillingIsBlockedForCustomer
```
public void setBillingIsBlockedForCustomer(@Nullable
                                           String billingIsBlockedForCustomer)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: BillingIsBlockedForCustomer
    
    If you enter a blocking indicator, billing that is already underway is continued. However, you cannot process the document further.Enter one of the values predefined for your system. If you want to block billing for a customer throughout an entire sales organization, you must enter a blocking indicator for each sales area in which the sales organization is defined.You can block billing for a customer if, for example, there are credit-related or legal problems to be resolved.
    
    Parameters:
    
    billingIsBlockedForCustomer - Indicates if further billing activities are blocked for the customer. The block applies throughout the specified sales area.
  - 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.
  - setCurrency
```
public void setCurrency(@Nullable
                        String currency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: Currency
    
    Parameters:
    
    currency - Customer's currency for a sales area. This currency will be used to settle the customer's charges for the given sales organization.
  - setCustomerABCClassification
```
public void setCustomerABCClassification(@Nullable
                                         String customerABCClassification)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerABCClassification
    
    Parameters:
    
    customerABCClassification - Customer classification (ABC analysis)
  - 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.
  - 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.
  - 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.
  - 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.
  - setCustomerPricingProcedure
```
public void setCustomerPricingProcedure(@Nullable
                                        String customerPricingProcedure)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerPricingProcedure
    
    You can define different pricing procedures for your system. A pricing procedure determines the type and sequence of conditions that the system uses for pricing in, for example, a sales order.
    
    Parameters:
    
    customerPricingProcedure - Determines which pricing procedure the system should apply when you create a sales document for the customer.
  - setDeliveryIsBlockedForCustomer
```
public void setDeliveryIsBlockedForCustomer(@Nullable
                                            String deliveryIsBlockedForCustomer)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryIsBlockedForCustomer
    
    If you enter a blocking indicator, delivery processing that is already underway is continued. However, no new processing can take place.Enter one of the values predefined for your system. If you want to block delivery processing for a customer within a particular sales organization, you must enter a blocking indicator for each sales area in which the sales organization is defined.You can block delivery processing for a customer if, for example, there are credit-related or legal problems to be resolved.
    
    Parameters:
    
    deliveryIsBlockedForCustomer - Indicates if further delivery processing is blocked for the customer. The block applies throughout the specified sales area.
  - setDeliveryPriority
```
public void setDeliveryPriority(@Nullable
                                String deliveryPriority)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryPriority
    
    You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
    
    Parameters:
    
    deliveryPriority - The delivery priority assigned to an item.
  - 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).
  - 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).
  - 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:
  - setDeletionIndicator
```
public void setDeletionIndicator(@Nullable
                                 Boolean deletionIndicator)
```
    Constraints: none
    Original property name from the Odata EDM: DeletionIndicator
    
    Parameters:
    
    deletionIndicator - Indicates that all data in the master record will be deleted for the specified sales area. Before the deletion is made, the system checks for dependent data that would prevent the deletion.
  - 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.
  - setInvoiceDate
```
public void setInvoiceDate(@Nullable
                           String invoiceDate)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: InvoiceDate
    
    If, for example, a customer wants to consolidate the invoices you send out, you can predefine the billing schedule in a calendar in the system. During billing, the system automatically proposes the appropriate billing date from the calendar.The system proposes the billing schedule from the customer master record of the payer. You can change the value manually in the sales document.
    
    Parameters:
    
    invoiceDate - Identifies the calendar that determines the schedule of billing dates for the customer.
  - setItemOrderProbabilityInPercent
```
public void setItemOrderProbabilityInPercent(@Nullable
                                             String itemOrderProbabilityInPercent)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: ItemOrderProbabilityInPercent
    
    The system combines the probability factors from the sales document type and from the customer master record of the sold-to party.If probability is 80% for the sales document type and 50% in the customer master record, the system combines the two values. In this case, the system takes 50% of 80% and proposes 40% for the item.The system proposes the probability. You can change the value manually for the item.You can generate requirements from quotations. Accordingly, the probability of quotation items affects how requirements are passed on. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.
    
    Parameters:
    
    itemOrderProbabilityInPercent - The probability (expressed as a percentage) of the customer confirming the inquiry or quotation item as part of a sales order.
  - setOrderCombinationIsAllowed
```
public void setOrderCombinationIsAllowed(@Nullable
                                         Boolean orderCombinationIsAllowed)
```
    Constraints: none
    Original property name from the Odata EDM: OrderCombinationIsAllowed
    
    The system proposes the indicator from the customer master record. You can change the value manually in the sales document at both header and item level.
    
    Parameters:
    
    orderCombinationIsAllowed - Indicates whether you are allowed to combine orders during delivery processing.
  - setOrderIsBlockedForCustomer
```
public void setOrderIsBlockedForCustomer(@Nullable
                                         String orderIsBlockedForCustomer)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: OrderIsBlockedForCustomer
    
    You can define blocks according to the needs of your organization. If you enter a blocking indicator, sales order processing that is already underway is continued. However, no new processing can occur.Enter one of the values predefined for your system. If you want to block sales order processing for a customer within a particular sales organization, you must enter a blocking indicator for each sales area in which the sale organization is defined.You can block sales order processing for a customer if, for example, there are credit-related or legal problems to be resolved.
    
    Parameters:
    
    orderIsBlockedForCustomer - Indicates if further sales order processing is blocked for the customer. The block applies throughout the specified sales area.
  - setPartialDeliveryIsAllowed
```
public void setPartialDeliveryIsAllowed(@Nullable
                                        String partialDeliveryIsAllowed)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PartialDeliveryIsAllowed
    
    You use this field to control partial deliveries at the item level. If the customer allows partial delivery, you can choose from different partial delivery options. For example, you can specify whether the customer allows you to make one delivery attempt only on the requested delivery date or whether unlimited delivery attempts are possible.When partial delivery indicator 'D' is set, the order can never have status 'fully delivered'. You must complete each item by entering a reason for rejection. This could be applied to scheduling agreements, for example.You can enter a value in this field only if the customer allows partial deliveries for the entire sales document.
    
    Parameters:
    
    partialDeliveryIsAllowed - Specifies whether the customer requires full or partial delivery for the item.
  - 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).
  - 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.
  - 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.
  - setSupplyingPlant
```
public void setSupplyingPlant(@Nullable
                              String supplyingPlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SupplyingPlant
    
    This plant is automatically copied into the sales order item as the default value.If there is no default value when you process the sales order item, enter a delivering plant.The value proposed in the item is eitherfrom the customer master record of the goods recipient, orfrom the material master recordThe system checks whether it can propose a value (and for your own plants, whether the material has been created in the plant). If the system can propose a value, the plant is copied to the sales order item where you can change it as required.
    
    Parameters:
    
    supplyingPlant - Plant from which the goods should be delivered to the customer.
  - 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.
  - setCustomerAccountGroup
```
public void setCustomerAccountGroup(@Nullable
                                    String customerAccountGroup)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerAccountGroup
    
    in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
    
    Parameters:
    
    customerAccountGroup - The account group is a classifying feature within customer master records. The account group determines:
  - getEntityCollection
```
protected String getEntityCollection()
```
    Specified by:
    
    getEntityCollection in class VdmEntity<CustomerSalesArea>
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<CustomerSalesArea>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<CustomerSalesArea>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<CustomerSalesArea>
  - field
```
@Nonnull
public static <T> CustomerSalesAreaField<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> CustomerSalesAreaField<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.
  - getErpConfigContext
```
@Nullable
public ErpConfigContext getErpConfigContext()
```
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities). New ERP configuration context to apply to this entity
    
    Overrides:
    
    getErpConfigContext in class VdmEntity<CustomerSalesArea>
    
    Returns:
    
    The stored ERP system context for executing queries, or null if no such context has been set.
  - setErpConfigContext
```
@Deprecated
public void setErpConfigContext(@Nullable
                                            ErpConfigContext erpConfigContext)
```
    Deprecated. Use attachToService(String, ErpConfigContext) instead.
    
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Overrides:
    
    setErpConfigContext in class VdmEntity<CustomerSalesArea>
    
    Parameters:
    
    erpConfigContext - New ERP configuration context to apply to this entity
  - 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<CustomerSalesArea>
  - attachToService
```
public void attachToService(@Nullable
                            String servicePath,
                            @Nullable
                            ErpConfigContext configContext)
```
    Description copied from class: VdmEntity
    
    Sets the service path and ERP configuration context for the fetch commands of this entity. Ensures that both are set to some value by using defaults if null values are provided in the arguments. Existing values are preserved if null values are provided in the arguments. 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<CustomerSalesArea>
    
    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.
    
    configContext - Optional parameter. New ERP configuration context to apply to this entity and any associated entities that were previously fetched. If a null value is provided and the ERP configuration context has never been set, then the ERP configuration context will be set to a new instance of ErpConfigContext.
  - getDefaultServicePath
```
protected String getDefaultServicePath()
```
    Overrides:
    
    getDefaultServicePath in class VdmEntity<CustomerSalesArea>
  - toMapOfNavigationProperties
```
@Nonnull
protected Map<String,Object> toMapOfNavigationProperties()
```
    Overrides:
    
    toMapOfNavigationProperties in class VdmObject<CustomerSalesArea>
  - fetchPartnerFunction
```
@Nonnull
public List<CustSalesPartnerFunc> fetchPartnerFunction()
                                                         throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustSalesPartnerFunc entities (one to many) associated with this entity. This corresponds to the OData navigation property to_PartnerFunction.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated CustSalesPartnerFunc 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.
  - getPartnerFunctionOrFetch
```
@Nonnull
public List<CustSalesPartnerFunc> getPartnerFunctionOrFetch()
                                                              throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustSalesPartnerFunc entities (one to many). This corresponds to the OData navigation property to_PartnerFunction.
    If the navigation property to_PartnerFunction of a queried CustomerSalesArea 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 CustSalesPartnerFunc 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.
  - getPartnerFunctionIfPresent
```
@Nonnull
public Optional<List<CustSalesPartnerFunc>> getPartnerFunctionIfPresent()
```
    Retrieval of associated CustSalesPartnerFunc entities (one to many). This corresponds to the OData navigation property to_PartnerFunction.
    If the navigation property for an entity CustomerSalesArea has not been resolved yet, this method will not query further information. Instead its Optional result state will be empty.
    
    Returns:
    
    If the information for navigation property to_PartnerFunction is already loaded, the result will contain the CustSalesPartnerFunc entities. If not, an Optional with result state empty is returned.
  - setPartnerFunction
```
public void setPartnerFunction(@Nonnull
                               List<CustSalesPartnerFunc> value)
```
    Overwrites the list of associated CustSalesPartnerFunc entities for the loaded navigation property to_PartnerFunction.
    If the navigation property to_PartnerFunction of a queried CustomerSalesArea 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 CustSalesPartnerFunc entities.
  - addPartnerFunction
```
public void addPartnerFunction(CustSalesPartnerFunc... entity)
```
    Adds elements to the list of associated CustSalesPartnerFunc entities. This corresponds to the OData navigation property to_PartnerFunction.
    If the navigation property to_PartnerFunction of a queried CustomerSalesArea 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 CustSalesPartnerFunc entities.
  - fetchSalesAreaTax
```
@Nonnull
public List<CustomerSalesAreaTax> fetchSalesAreaTax()
                                                      throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustomerSalesAreaTax entities (one to many) associated with this entity. This corresponds to the OData navigation property to_SalesAreaTax.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated CustomerSalesAreaTax 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.
  - getSalesAreaTaxOrFetch
```
@Nonnull
public List<CustomerSalesAreaTax> getSalesAreaTaxOrFetch()
                                                           throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustomerSalesAreaTax entities (one to many). This corresponds to the OData navigation property to_SalesAreaTax.
    If the navigation property to_SalesAreaTax of a queried CustomerSalesArea 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 CustomerSalesAreaTax 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.
  - getSalesAreaTaxIfPresent
```
@Nonnull
public Optional<List<CustomerSalesAreaTax>> getSalesAreaTaxIfPresent()
```
    Retrieval of associated CustomerSalesAreaTax entities (one to many). This corresponds to the OData navigation property to_SalesAreaTax.
    If the navigation property for an entity CustomerSalesArea has not been resolved yet, this method will not query further information. Instead its Optional result state will be empty.
    
    Returns:
    
    If the information for navigation property to_SalesAreaTax is already loaded, the result will contain the CustomerSalesAreaTax entities. If not, an Optional with result state empty is returned.
  - setSalesAreaTax
```
public void setSalesAreaTax(@Nonnull
                            List<CustomerSalesAreaTax> value)
```
    Overwrites the list of associated CustomerSalesAreaTax entities for the loaded navigation property to_SalesAreaTax.
    If the navigation property to_SalesAreaTax of a queried CustomerSalesArea 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 CustomerSalesAreaTax entities.
  - addSalesAreaTax
```
public void addSalesAreaTax(CustomerSalesAreaTax... entity)
```
    Adds elements to the list of associated CustomerSalesAreaTax entities. This corresponds to the OData navigation property to_SalesAreaTax.
    If the navigation property to_SalesAreaTax of a queried CustomerSalesArea 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 CustomerSalesAreaTax entities.
  - builder
```
public static CustomerSalesArea.CustomerSalesAreaBuilder builder()
```
  - getCustomer
```
@Nullable
public String getCustomer()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Customer
    
    Returns:
    
    Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.
  - getSalesOrganization
```
@Nullable
public String getSalesOrganization()
```
    (Key Field) 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()
```
    (Key Field) 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.
  - getDivision
```
@Nullable
public String getDivision()
```
    (Key Field) Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: Division
    
    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.
  - getAccountByCustomer
```
@Nullable
public String getAccountByCustomer()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: AccountByCustomer
    
    Returns:
    
    This field contains the account number your company is listed under at the customer or vendor.
  - getAuthorizationGroup
```
@Nullable
public String getAuthorizationGroup()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: AuthorizationGroup
    
    In order to carry out a specific activity, the user must have authorization for the combination of the activity and the authorization group.
    
    Returns:
    
    The authorization group enables you protect access to certain objects.
  - getBillingIsBlockedForCustomer
```
@Nullable
public String getBillingIsBlockedForCustomer()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: BillingIsBlockedForCustomer
    
    If you enter a blocking indicator, billing that is already underway is continued. However, you cannot process the document further.Enter one of the values predefined for your system. If you want to block billing for a customer throughout an entire sales organization, you must enter a blocking indicator for each sales area in which the sales organization is defined.You can block billing for a customer if, for example, there are credit-related or legal problems to be resolved.
    
    Returns:
    
    Indicates if further billing activities are blocked for the customer. The block applies throughout the specified sales area.
  - 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.
  - getCurrency
```
@Nullable
public String getCurrency()
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: Currency
    
    Returns:
    
    Customer's currency for a sales area. This currency will be used to settle the customer's charges for the given sales organization.
  - getCustomerABCClassification
```
@Nullable
public String getCustomerABCClassification()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerABCClassification
    
    Returns:
    
    Customer classification (ABC analysis)
  - 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.
  - 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.
  - 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.
  - 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.
  - getCustomerPricingProcedure
```
@Nullable
public String getCustomerPricingProcedure()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerPricingProcedure
    
    You can define different pricing procedures for your system. A pricing procedure determines the type and sequence of conditions that the system uses for pricing in, for example, a sales order.
    
    Returns:
    
    Determines which pricing procedure the system should apply when you create a sales document for the customer.
  - getDeliveryIsBlockedForCustomer
```
@Nullable
public String getDeliveryIsBlockedForCustomer()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryIsBlockedForCustomer
    
    If you enter a blocking indicator, delivery processing that is already underway is continued. However, no new processing can take place.Enter one of the values predefined for your system. If you want to block delivery processing for a customer within a particular sales organization, you must enter a blocking indicator for each sales area in which the sales organization is defined.You can block delivery processing for a customer if, for example, there are credit-related or legal problems to be resolved.
    
    Returns:
    
    Indicates if further delivery processing is blocked for the customer. The block applies throughout the specified sales area.
  - getDeliveryPriority
```
@Nullable
public String getDeliveryPriority()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryPriority
    
    You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
    
    Returns:
    
    The delivery priority assigned to an item.
  - 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).
  - 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).
  - 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:
  - getDeletionIndicator
```
@Nullable
public Boolean getDeletionIndicator()
```
    Constraints: none
    Original property name from the Odata EDM: DeletionIndicator
    
    Returns:
    
    Indicates that all data in the master record will be deleted for the specified sales area. Before the deletion is made, the system checks for dependent data that would prevent the deletion.
  - 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.
  - getInvoiceDate
```
@Nullable
public String getInvoiceDate()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: InvoiceDate
    
    If, for example, a customer wants to consolidate the invoices you send out, you can predefine the billing schedule in a calendar in the system. During billing, the system automatically proposes the appropriate billing date from the calendar.The system proposes the billing schedule from the customer master record of the payer. You can change the value manually in the sales document.
    
    Returns:
    
    Identifies the calendar that determines the schedule of billing dates for the customer.
  - getItemOrderProbabilityInPercent
```
@Nullable
public String getItemOrderProbabilityInPercent()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: ItemOrderProbabilityInPercent
    
    The system combines the probability factors from the sales document type and from the customer master record of the sold-to party.If probability is 80% for the sales document type and 50% in the customer master record, the system combines the two values. In this case, the system takes 50% of 80% and proposes 40% for the item.The system proposes the probability. You can change the value manually for the item.You can generate requirements from quotations. Accordingly, the probability of quotation items affects how requirements are passed on. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.
    
    Returns:
    
    The probability (expressed as a percentage) of the customer confirming the inquiry or quotation item as part of a sales order.
  - getOrderCombinationIsAllowed
```
@Nullable
public Boolean getOrderCombinationIsAllowed()
```
    Constraints: none
    Original property name from the Odata EDM: OrderCombinationIsAllowed
    
    The system proposes the indicator from the customer master record. You can change the value manually in the sales document at both header and item level.
    
    Returns:
    
    Indicates whether you are allowed to combine orders during delivery processing.
  - getOrderIsBlockedForCustomer
```
@Nullable
public String getOrderIsBlockedForCustomer()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: OrderIsBlockedForCustomer
    
    You can define blocks according to the needs of your organization. If you enter a blocking indicator, sales order processing that is already underway is continued. However, no new processing can occur.Enter one of the values predefined for your system. If you want to block sales order processing for a customer within a particular sales organization, you must enter a blocking indicator for each sales area in which the sale organization is defined.You can block sales order processing for a customer if, for example, there are credit-related or legal problems to be resolved.
    
    Returns:
    
    Indicates if further sales order processing is blocked for the customer. The block applies throughout the specified sales area.
  - getPartialDeliveryIsAllowed
```
@Nullable
public String getPartialDeliveryIsAllowed()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PartialDeliveryIsAllowed
    
    You use this field to control partial deliveries at the item level. If the customer allows partial delivery, you can choose from different partial delivery options. For example, you can specify whether the customer allows you to make one delivery attempt only on the requested delivery date or whether unlimited delivery attempts are possible.When partial delivery indicator 'D' is set, the order can never have status 'fully delivered'. You must complete each item by entering a reason for rejection. This could be applied to scheduling agreements, for example.You can enter a value in this field only if the customer allows partial deliveries for the entire sales document.
    
    Returns:
    
    Specifies whether the customer requires full or partial delivery for the item.
  - 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).
  - 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.
  - 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.
  - getSupplyingPlant
```
@Nullable
public String getSupplyingPlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SupplyingPlant
    
    This plant is automatically copied into the sales order item as the default value.If there is no default value when you process the sales order item, enter a delivering plant.The value proposed in the item is eitherfrom the customer master record of the goods recipient, orfrom the material master recordThe system checks whether it can propose a value (and for your own plants, whether the material has been created in the plant). If the system can propose a value, the plant is copied to the sales order item where you can change it as required.
    
    Returns:
    
    Plant from which the goods should be delivered to the customer.
  - 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.
  - getCustomerAccountGroup
```
@Nullable
public String getCustomerAccountGroup()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerAccountGroup
    
    in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
    
    Returns:
    
    The account group is a classifying feature within customer master records. The account group determines:
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<CustomerSalesArea>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<CustomerSalesArea>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<CustomerSalesArea>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<CustomerSalesArea>

Class CustomerSalesArea

Nested Class Summary

Field Summary

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

Constructor Summary

Method Summary

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

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

CUSTOMER

SALES_ORGANIZATION

DISTRIBUTION_CHANNEL

DIVISION

ACCOUNT_BY_CUSTOMER

AUTHORIZATION_GROUP

BILLING_IS_BLOCKED_FOR_CUSTOMER

COMPLETE_DELIVERY_IS_DEFINED

CURRENCY

CUSTOMER_ABC_CLASSIFICATION

CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP

CUSTOMER_GROUP

CUSTOMER_PAYMENT_TERMS

CUSTOMER_PRICE_GROUP

CUSTOMER_PRICING_PROCEDURE

DELIVERY_IS_BLOCKED_FOR_CUSTOMER

DELIVERY_PRIORITY

INCOTERMS_CLASSIFICATION

INCOTERMS_LOCATION2

INCOTERMS_VERSION

INCOTERMS_LOCATION1

DELETION_INDICATOR

INCOTERMS_TRANSFER_LOCATION

INVOICE_DATE

ITEM_ORDER_PROBABILITY_IN_PERCENT

ORDER_COMBINATION_IS_ALLOWED

ORDER_IS_BLOCKED_FOR_CUSTOMER

PARTIAL_DELIVERY_IS_ALLOWED

PRICE_LIST_TYPE

SALES_GROUP

SALES_OFFICE

SHIPPING_CONDITION

SUPPLYING_PLANT

SALES_DISTRICT

CUSTOMER_ACCOUNT_GROUP

TO_PARTNER_FUNCTION

TO_SALES_AREA_TAX

Constructor Detail

CustomerSalesArea

CustomerSalesArea

Method Detail

getType

setCustomer

setSalesOrganization

setDistributionChannel

setDivision

setAccountByCustomer

setAuthorizationGroup

setBillingIsBlockedForCustomer

setCompleteDeliveryIsDefined

setCurrency

setCustomerABCClassification

setCustomerAccountAssignmentGroup

setCustomerGroup

setCustomerPaymentTerms

setCustomerPriceGroup

setCustomerPricingProcedure

setDeliveryIsBlockedForCustomer

setDeliveryPriority

setIncotermsClassification

setIncotermsLocation2

setIncotermsVersion

setIncotermsLocation1

setDeletionIndicator

setIncotermsTransferLocation

setInvoiceDate

setItemOrderProbabilityInPercent

setOrderCombinationIsAllowed

setOrderIsBlockedForCustomer