SalesSchedgAgrmt (SAP Cloud SDK - Parent POM 3.41.0 API)

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

```
public class SalesSchedgAgrmt
extends VdmEntity<SalesSchedgAgrmt>
```
Sales Scheduling Agreement Header

Original entity name from the Odata EDM: A_SalesSchedgAgrmtType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class SalesSchedgAgrmt.SalesSchedgAgrmtBuilder
Helper class to allow for fluent creation of SalesSchedgAgrmt instances.

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

Field Summary

Fields
Modifier and Type	Field and Description
`static SalesSchedgAgrmtField<LocalDateTime>`	`AGRMT_VALDTY_END_DATE` Use with available fluent helpers to apply the AgrmtValdtyEndDate field to query operations.
`static SalesSchedgAgrmtField<LocalDateTime>`	`AGRMT_VALDTY_START_DATE` Use with available fluent helpers to apply the AgrmtValdtyStartDate field to query operations.
`static SalesSchedgAgrmtSelectable`	`ALL_FIELDS` Selector for all available fields of SalesSchedgAgrmt.
`static SalesSchedgAgrmtField<String>`	`CREATED_BY_USER` Use with available fluent helpers to apply the CreatedByUser field to query operations.
`static SalesSchedgAgrmtField<LocalDateTime>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static SalesSchedgAgrmtField<LocalTime>`	`CREATION_TIME` Use with available fluent helpers to apply the CreationTime field to query operations.
`static SalesSchedgAgrmtField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static SalesSchedgAgrmtField<LocalDateTime>`	`CUSTOMER_PURCHASE_ORDER_DATE` Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
`static SalesSchedgAgrmtField<String>`	`CUSTOMER_PURCHASE_ORDER_TYPE` Use with available fluent helpers to apply the CustomerPurchaseOrderType field to query operations.
`static SalesSchedgAgrmtField<String>`	`DELIV_SCHED_TYPE_MRP_RLVNCE_CODE` Use with available fluent helpers to apply the DelivSchedTypeMRPRlvnceCode field to query operations.
`static SalesSchedgAgrmtField<String>`	`DELIVERY_BLOCK_REASON` Use with available fluent helpers to apply the DeliveryBlockReason field to query operations.
`static SalesSchedgAgrmtField<String>`	`DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the DistributionChannel field to query operations.
`static SalesSchedgAgrmtField<String>`	`FISCAL_PERIOD` Use with available fluent helpers to apply the FiscalPeriod field to query operations.
`static SalesSchedgAgrmtField<String>`	`FISCAL_YEAR` Use with available fluent helpers to apply the FiscalYear field to query operations.
`static SalesSchedgAgrmtField<String>`	`HEADER_BILLING_BLOCK_REASON` Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
`static SalesSchedgAgrmtField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static SalesSchedgAgrmtField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static SalesSchedgAgrmtField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static SalesSchedgAgrmtField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static SalesSchedgAgrmtField<String>`	`INCOTERMS_VERSION` Use with available fluent helpers to apply the IncotermsVersion field to query operations.
`static SalesSchedgAgrmtField<LocalDateTime>`	`LAST_CHANGE_DATE` Use with available fluent helpers to apply the LastChangeDate field to query operations.
`static SalesSchedgAgrmtField<ZonedDateTime>`	`LAST_CHANGE_DATE_TIME` Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
`static SalesSchedgAgrmtField<String>`	`LAST_CHANGED_BY_USER` Use with available fluent helpers to apply the LastChangedByUser field to query operations.
`static SalesSchedgAgrmtField<String>`	`MATL_USAGE_INDICATOR` Use with available fluent helpers to apply the MatlUsageIndicator field to query operations.
`static SalesSchedgAgrmtField<String>`	`ORGANIZATION_DIVISION` Use with available fluent helpers to apply the OrganizationDivision field to query operations.
`static SalesSchedgAgrmtField<String>`	`OVERALL_BILLING_BLOCK_STATUS` Use with available fluent helpers to apply the OverallBillingBlockStatus field to query operations.
`static SalesSchedgAgrmtField<String>`	`OVERALL_DELIVERY_BLOCK_STATUS` Use with available fluent helpers to apply the OverallDeliveryBlockStatus field to query operations.
`static SalesSchedgAgrmtField<String>`	`OVERALL_DELIVERY_STATUS` Use with available fluent helpers to apply the OverallDeliveryStatus field to query operations.
`static SalesSchedgAgrmtField<String>`	`OVERALL_SD_DOCUMENT_REJECTION_STS` Use with available fluent helpers to apply the OverallSDDocumentRejectionSts field to query operations.
`static SalesSchedgAgrmtField<String>`	`OVERALL_SD_PROCESS_STATUS` Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
`static SalesSchedgAgrmtField<String>`	`PAYMENT_METHOD` Use with available fluent helpers to apply the PaymentMethod field to query operations.
`static SalesSchedgAgrmtField<LocalDateTime>`	`PRICING_DATE` Use with available fluent helpers to apply the PricingDate field to query operations.
`static SalesSchedgAgrmtField<String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static SalesSchedgAgrmtField<String>`	`SALES_DISTRICT` Use with available fluent helpers to apply the SalesDistrict field to query operations.
`static SalesSchedgAgrmtField<String>`	`SALES_GROUP` Use with available fluent helpers to apply the SalesGroup field to query operations.
`static SalesSchedgAgrmtField<String>`	`SALES_OFFICE` Use with available fluent helpers to apply the SalesOffice field to query operations.
`static SalesSchedgAgrmtField<String>`	`SALES_ORGANIZATION` Use with available fluent helpers to apply the SalesOrganization field to query operations.
`static SalesSchedgAgrmtField<LocalDateTime>`	`SALES_SCHEDG_AGRMT_DATE` Use with available fluent helpers to apply the SalesSchedgAgrmtDate field to query operations.
`static SalesSchedgAgrmtField<String>`	`SALES_SCHEDG_AGRMT_TYPE` Use with available fluent helpers to apply the SalesSchedgAgrmtType field to query operations.
`static SalesSchedgAgrmtField<String>`	`SALES_SCHEDULING_AGREEMENT` Use with available fluent helpers to apply the SalesSchedulingAgreement field to query operations.
`static SalesSchedgAgrmtField<String>`	`SD_DOCUMENT_REASON` Use with available fluent helpers to apply the SDDocumentReason field to query operations.
`static SalesSchedgAgrmtField<String>`	`SHIPPING_CONDITION` Use with available fluent helpers to apply the ShippingCondition field to query operations.
`static SalesSchedgAgrmtField<String>`	`SHIPPING_TYPE` Use with available fluent helpers to apply the ShippingType field to query operations.
`static SalesSchedgAgrmtField<String>`	`SOLD_TO_PARTY` Use with available fluent helpers to apply the SoldToParty field to query operations.
`static SalesSchedgAgrmtLink<SalesSchedgAgrmtItem>`	`TO_ITEM` Use with available fluent helpers to apply the to_Item navigation property to query operations.
`static SalesSchedgAgrmtLink<SalesSchedgAgrmtPartner>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static SalesSchedgAgrmtLink<SalesSchedgAgrmtPrcgElement>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static SalesSchedgAgrmtLink<SalesSchedgAgrmtText>`	`TO_TEXT` Use with available fluent helpers to apply the to_Text navigation property to query operations.
`static SalesSchedgAgrmtField<String>`	`TOTAL_BLOCK_STATUS` Use with available fluent helpers to apply the TotalBlockStatus field to query operations.
`static SalesSchedgAgrmtField<String>`	`TOTAL_CREDIT_CHECK_STATUS` Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
`static SalesSchedgAgrmtField<BigDecimal>`	`TOTAL_NET_AMOUNT` Use with available fluent helpers to apply the TotalNetAmount field to query operations.
`static SalesSchedgAgrmtField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.

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

Constructor Summary

Constructors
Constructor and Description
`SalesSchedgAgrmt()`
SalesSchedgAgrmt(String salesSchedulingAgreement, String salesSchedgAgrmtType, String createdByUser, String lastChangedByUser, LocalDateTime creationDate, LocalTime creationTime, LocalDateTime lastChangeDate, ZonedDateTime lastChangeDateTime, String salesOrganization, String distributionChannel, String organizationDivision, String salesGroup, String salesOffice, String soldToParty, LocalDateTime salesSchedgAgrmtDate, String sDDocumentReason, String purchaseOrderByCustomer, String customerPurchaseOrderType, LocalDateTime customerPurchaseOrderDate, String salesDistrict, BigDecimal totalNetAmount, String transactionCurrency, LocalDateTime pricingDate, String shippingType, String shippingCondition, String incotermsVersion, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String deliveryBlockReason, String delivSchedTypeMRPRlvnceCode, LocalDateTime agrmtValdtyStartDate, LocalDateTime agrmtValdtyEndDate, String matlUsageIndicator, String headerBillingBlockReason, String customerPaymentTerms, String paymentMethod, String fiscalYear, String fiscalPeriod, String overallSDProcessStatus, String overallSDDocumentRejectionSts, String totalBlockStatus, String overallDeliveryStatus, String overallDeliveryBlockStatus, String overallBillingBlockStatus, String totalCreditCheckStatus, List<SalesSchedgAgrmtItem> toItem, List<SalesSchedgAgrmtPartner> toPartner, List<SalesSchedgAgrmtPrcgElement> toPricingElement, List<SalesSchedgAgrmtText> toText)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addItem(SalesSchedgAgrmtItem... entity)` Adds elements to the list of associated SalesSchedgAgrmtItem entities.
`void`	`addPartner(SalesSchedgAgrmtPartner... entity)` Adds elements to the list of associated SalesSchedgAgrmtPartner entities.
`void`	`addPricingElement(SalesSchedgAgrmtPrcgElement... entity)` Adds elements to the list of associated SalesSchedgAgrmtPrcgElement entities.
`void`	`addText(SalesSchedgAgrmtText... entity)` Adds elements to the list of associated SalesSchedgAgrmtText entities.
`void`	`attachToService(String servicePath, HttpDestinationProperties destination)` Sets the service path and destination for the fetch commands of this entity.
`static SalesSchedgAgrmt.SalesSchedgAgrmtBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`List<SalesSchedgAgrmtItem>`	`fetchItem()` Fetches the SalesSchedgAgrmtItem entities (one to many) associated with this entity.
`List<SalesSchedgAgrmtPartner>`	`fetchPartner()` Fetches the SalesSchedgAgrmtPartner entities (one to many) associated with this entity.
`List<SalesSchedgAgrmtPrcgElement>`	`fetchPricingElement()` Fetches the SalesSchedgAgrmtPrcgElement entities (one to many) associated with this entity.
`List<SalesSchedgAgrmtText>`	`fetchText()` Fetches the SalesSchedgAgrmtText entities (one to many) associated with this entity.
`static <T> SalesSchedgAgrmtField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> SalesSchedgAgrmtField<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)`
`LocalDateTime`	`getAgrmtValdtyEndDate()` Constraints: Not nullable, Precision: 0
`LocalDateTime`	`getAgrmtValdtyStartDate()` Constraints: Not nullable, Precision: 0
`String`	`getCreatedByUser()` Constraints: Not nullable, Maximum length: 12
`LocalDateTime`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`LocalTime`	`getCreationTime()` Constraints: Not nullable, Precision: 0
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4
`LocalDateTime`	`getCustomerPurchaseOrderDate()` Constraints: Not nullable, Precision: 0
`String`	`getCustomerPurchaseOrderType()` Constraints: Not nullable, Maximum length: 4
`protected String`	`getDefaultServicePath()` Used by fluent helpers and navigation property methods to construct OData queries.
`String`	`getDeliveryBlockReason()` Constraints: Not nullable, Maximum length: 2
`String`	`getDelivSchedTypeMRPRlvnceCode()` Constraints: Not nullable, Maximum length: 1
`HttpDestinationProperties`	`getDestinationForFetch()` Convienence field for reusing the same destination with multiple queries (e.g.
`String`	`getDistributionChannel()` Constraints: Not nullable, Maximum length: 2
`protected String`	`getEntityCollection()` Used by fluent helpers and navigation property methods to construct OData queries.
`String`	`getFiscalPeriod()` Constraints: Not nullable, Maximum length: 3
`String`	`getFiscalYear()` Constraints: Not nullable, Maximum length: 4
`String`	`getHeaderBillingBlockReason()` Constraints: Not nullable, Maximum length: 2
`String`	`getIncotermsClassification()` Constraints: Not nullable, Maximum length: 3
`String`	`getIncotermsLocation1()` Constraints: Not nullable, Maximum length: 70
`String`	`getIncotermsLocation2()` Constraints: Not nullable, Maximum length: 70
`String`	`getIncotermsTransferLocation()` Constraints: Not nullable, Maximum length: 28
`String`	`getIncotermsVersion()` Constraints: Not nullable, Maximum length: 4
`io.vavr.control.Option<List<SalesSchedgAgrmtItem>>`	`getItemIfPresent()` Retrieval of associated SalesSchedgAgrmtItem entities (one to many).
`List<SalesSchedgAgrmtItem>`	`getItemOrFetch()` Retrieval of associated SalesSchedgAgrmtItem entities (one to many).
`protected Map<String,Object>`	`getKey()`
`LocalDateTime`	`getLastChangeDate()` Constraints: Not nullable, Precision: 0
`ZonedDateTime`	`getLastChangeDateTime()` Constraints: Not nullable, Precision: 7
`String`	`getLastChangedByUser()` Constraints: Not nullable, Maximum length: 12
`String`	`getMatlUsageIndicator()` Constraints: Not nullable, Maximum length: 3
`String`	`getOrganizationDivision()` Constraints: Not nullable, Maximum length: 2
`String`	`getOverallBillingBlockStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallDeliveryBlockStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallDeliveryStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallSDDocumentRejectionSts()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallSDProcessStatus()` Constraints: Not nullable, Maximum length: 1
`io.vavr.control.Option<List<SalesSchedgAgrmtPartner>>`	`getPartnerIfPresent()` Retrieval of associated SalesSchedgAgrmtPartner entities (one to many).
`List<SalesSchedgAgrmtPartner>`	`getPartnerOrFetch()` Retrieval of associated SalesSchedgAgrmtPartner entities (one to many).
`String`	`getPaymentMethod()` Constraints: Not nullable, Maximum length: 1
`LocalDateTime`	`getPricingDate()` Constraints: Not nullable, Precision: 0
`io.vavr.control.Option<List<SalesSchedgAgrmtPrcgElement>>`	`getPricingElementIfPresent()` Retrieval of associated SalesSchedgAgrmtPrcgElement entities (one to many).
`List<SalesSchedgAgrmtPrcgElement>`	`getPricingElementOrFetch()` Retrieval of associated SalesSchedgAgrmtPrcgElement entities (one to many).
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35
`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()` Constraints: Not nullable, Maximum length: 4
`LocalDateTime`	`getSalesSchedgAgrmtDate()` Constraints: Not nullable, Precision: 0
`String`	`getSalesSchedgAgrmtType()` Constraints: Not nullable, Maximum length: 4
`String`	`getSalesSchedulingAgreement()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getSDDocumentReason()` Constraints: Not nullable, Maximum length: 3
`String`	`getShippingCondition()` Constraints: Not nullable, Maximum length: 2
`String`	`getShippingType()` Constraints: Not nullable, Maximum length: 2
`String`	`getSoldToParty()` Constraints: Not nullable, Maximum length: 10
`io.vavr.control.Option<List<SalesSchedgAgrmtText>>`	`getTextIfPresent()` Retrieval of associated SalesSchedgAgrmtText entities (one to many).
`List<SalesSchedgAgrmtText>`	`getTextOrFetch()` Retrieval of associated SalesSchedgAgrmtText entities (one to many).
`String`	`getTotalBlockStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getTotalCreditCheckStatus()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getTotalNetAmount()` Constraints: Not nullable, Precision: 16, Scale: 3
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5
`Class<SalesSchedgAgrmt>`	`getType()`
`int`	`hashCode()`
`void`	`setAgrmtValdtyEndDate(LocalDateTime agrmtValdtyEndDate)` Constraints: Not nullable, Precision: 0
`void`	`setAgrmtValdtyStartDate(LocalDateTime agrmtValdtyStartDate)` Constraints: Not nullable, Precision: 0
`void`	`setCreatedByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setCreationTime(LocalTime creationTime)` Constraints: Not nullable, Precision: 0
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`void`	`setCustomerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)` Constraints: Not nullable, Precision: 0
`void`	`setCustomerPurchaseOrderType(String customerPurchaseOrderType)` Constraints: Not nullable, Maximum length: 4
`void`	`setDeliveryBlockReason(String deliveryBlockReason)` Constraints: Not nullable, Maximum length: 2
`void`	`setDelivSchedTypeMRPRlvnceCode(String delivSchedTypeMRPRlvnceCode)` Constraints: Not nullable, Maximum length: 1
`void`	`setDistributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2
`void`	`setFiscalPeriod(String fiscalPeriod)` Constraints: Not nullable, Maximum length: 3
`void`	`setFiscalYear(String fiscalYear)` Constraints: Not nullable, Maximum length: 4
`void`	`setHeaderBillingBlockReason(String headerBillingBlockReason)` Constraints: Not nullable, Maximum length: 2
`void`	`setIncotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3
`void`	`setIncotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70
`void`	`setIncotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70
`void`	`setIncotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28
`void`	`setIncotermsVersion(String incotermsVersion)` Constraints: Not nullable, Maximum length: 4
`void`	`setItem(List<SalesSchedgAgrmtItem> value)` Overwrites the list of associated SalesSchedgAgrmtItem entities for the loaded navigation property to_Item.
`void`	`setLastChangeDate(LocalDateTime lastChangeDate)` Constraints: Not nullable, Precision: 0
`void`	`setLastChangeDateTime(ZonedDateTime lastChangeDateTime)` Constraints: Not nullable, Precision: 7
`void`	`setLastChangedByUser(String lastChangedByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setMatlUsageIndicator(String matlUsageIndicator)` Constraints: Not nullable, Maximum length: 3
`void`	`setOrganizationDivision(String organizationDivision)` Constraints: Not nullable, Maximum length: 2
`void`	`setOverallBillingBlockStatus(String overallBillingBlockStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallDeliveryBlockStatus(String overallDeliveryBlockStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallDeliveryStatus(String overallDeliveryStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallSDProcessStatus(String overallSDProcessStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setPartner(List<SalesSchedgAgrmtPartner> value)` Overwrites the list of associated SalesSchedgAgrmtPartner entities for the loaded navigation property to_Partner.
`void`	`setPaymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1
`void`	`setPricingDate(LocalDateTime pricingDate)` Constraints: Not nullable, Precision: 0
`void`	`setPricingElement(List<SalesSchedgAgrmtPrcgElement> value)` Overwrites the list of associated SalesSchedgAgrmtPrcgElement entities for the loaded navigation property to_PricingElement.
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`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)` Constraints: Not nullable, Maximum length: 4
`void`	`setSalesSchedgAgrmtDate(LocalDateTime salesSchedgAgrmtDate)` Constraints: Not nullable, Precision: 0
`void`	`setSalesSchedgAgrmtType(String salesSchedgAgrmtType)` Constraints: Not nullable, Maximum length: 4
`void`	`setSalesSchedulingAgreement(String salesSchedulingAgreement)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setSDDocumentReason(String sDDocumentReason)` Constraints: Not nullable, Maximum length: 3
`protected void`	`setServicePathForFetch(String servicePathForFetch)` The service path only used for the fetch commands of this entity.
`void`	`setShippingCondition(String shippingCondition)` Constraints: Not nullable, Maximum length: 2
`void`	`setShippingType(String shippingType)` Constraints: Not nullable, Maximum length: 2
`void`	`setSoldToParty(String soldToParty)` Constraints: Not nullable, Maximum length: 10
`void`	`setText(List<SalesSchedgAgrmtText> value)` Overwrites the list of associated SalesSchedgAgrmtText entities for the loaded navigation property to_Text.
`void`	`setTotalBlockStatus(String totalBlockStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setTotalCreditCheckStatus(String totalCreditCheckStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setTotalNetAmount(BigDecimal totalNetAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5
`protected Map<String,Object>`	`toMapOfFields()`
`protected Map<String,Object>`	`toMapOfNavigationProperties()`
`String`	`toString()`

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

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

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

- Field Detail
  - ALL_FIELDS
```
public static final SalesSchedgAgrmtSelectable ALL_FIELDS
```
    Selector for all available fields of SalesSchedgAgrmt.
  - SALES_SCHEDULING_AGREEMENT
```
public static final SalesSchedgAgrmtField<String> SALES_SCHEDULING_AGREEMENT
```
    Use with available fluent helpers to apply the SalesSchedulingAgreement field to query operations.
  - SALES_SCHEDG_AGRMT_TYPE
```
public static final SalesSchedgAgrmtField<String> SALES_SCHEDG_AGRMT_TYPE
```
    Use with available fluent helpers to apply the SalesSchedgAgrmtType field to query operations.
  - CREATED_BY_USER
```
public static final SalesSchedgAgrmtField<String> CREATED_BY_USER
```
    Use with available fluent helpers to apply the CreatedByUser field to query operations.
  - LAST_CHANGED_BY_USER
```
public static final SalesSchedgAgrmtField<String> LAST_CHANGED_BY_USER
```
    Use with available fluent helpers to apply the LastChangedByUser field to query operations.
  - CREATION_DATE
```
public static final SalesSchedgAgrmtField<LocalDateTime> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - CREATION_TIME
```
public static final SalesSchedgAgrmtField<LocalTime> CREATION_TIME
```
    Use with available fluent helpers to apply the CreationTime field to query operations.
  - LAST_CHANGE_DATE
```
public static final SalesSchedgAgrmtField<LocalDateTime> LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the LastChangeDate field to query operations.
  - LAST_CHANGE_DATE_TIME
```
public static final SalesSchedgAgrmtField<ZonedDateTime> LAST_CHANGE_DATE_TIME
```
    Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
  - SALES_ORGANIZATION
```
public static final SalesSchedgAgrmtField<String> SALES_ORGANIZATION
```
    Use with available fluent helpers to apply the SalesOrganization field to query operations.
  - DISTRIBUTION_CHANNEL
```
public static final SalesSchedgAgrmtField<String> DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the DistributionChannel field to query operations.
  - ORGANIZATION_DIVISION
```
public static final SalesSchedgAgrmtField<String> ORGANIZATION_DIVISION
```
    Use with available fluent helpers to apply the OrganizationDivision field to query operations.
  - SALES_GROUP
```
public static final SalesSchedgAgrmtField<String> SALES_GROUP
```
    Use with available fluent helpers to apply the SalesGroup field to query operations.
  - SALES_OFFICE
```
public static final SalesSchedgAgrmtField<String> SALES_OFFICE
```
    Use with available fluent helpers to apply the SalesOffice field to query operations.
  - SOLD_TO_PARTY
```
public static final SalesSchedgAgrmtField<String> SOLD_TO_PARTY
```
    Use with available fluent helpers to apply the SoldToParty field to query operations.
  - SALES_SCHEDG_AGRMT_DATE
```
public static final SalesSchedgAgrmtField<LocalDateTime> SALES_SCHEDG_AGRMT_DATE
```
    Use with available fluent helpers to apply the SalesSchedgAgrmtDate field to query operations.
  - SD_DOCUMENT_REASON
```
public static final SalesSchedgAgrmtField<String> SD_DOCUMENT_REASON
```
    Use with available fluent helpers to apply the SDDocumentReason field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final SalesSchedgAgrmtField<String> PURCHASE_ORDER_BY_CUSTOMER
```
    Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
  - CUSTOMER_PURCHASE_ORDER_TYPE
```
public static final SalesSchedgAgrmtField<String> CUSTOMER_PURCHASE_ORDER_TYPE
```
    Use with available fluent helpers to apply the CustomerPurchaseOrderType field to query operations.
  - CUSTOMER_PURCHASE_ORDER_DATE
```
public static final SalesSchedgAgrmtField<LocalDateTime> CUSTOMER_PURCHASE_ORDER_DATE
```
    Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
  - SALES_DISTRICT
```
public static final SalesSchedgAgrmtField<String> SALES_DISTRICT
```
    Use with available fluent helpers to apply the SalesDistrict field to query operations.
  - TOTAL_NET_AMOUNT
```
public static final SalesSchedgAgrmtField<BigDecimal> TOTAL_NET_AMOUNT
```
    Use with available fluent helpers to apply the TotalNetAmount field to query operations.
  - TRANSACTION_CURRENCY
```
public static final SalesSchedgAgrmtField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - PRICING_DATE
```
public static final SalesSchedgAgrmtField<LocalDateTime> PRICING_DATE
```
    Use with available fluent helpers to apply the PricingDate field to query operations.
  - SHIPPING_TYPE
```
public static final SalesSchedgAgrmtField<String> SHIPPING_TYPE
```
    Use with available fluent helpers to apply the ShippingType field to query operations.
  - SHIPPING_CONDITION
```
public static final SalesSchedgAgrmtField<String> SHIPPING_CONDITION
```
    Use with available fluent helpers to apply the ShippingCondition field to query operations.
  - INCOTERMS_VERSION
```
public static final SalesSchedgAgrmtField<String> INCOTERMS_VERSION
```
    Use with available fluent helpers to apply the IncotermsVersion field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final SalesSchedgAgrmtField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final SalesSchedgAgrmtField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final SalesSchedgAgrmtField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final SalesSchedgAgrmtField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - DELIVERY_BLOCK_REASON
```
public static final SalesSchedgAgrmtField<String> DELIVERY_BLOCK_REASON
```
    Use with available fluent helpers to apply the DeliveryBlockReason field to query operations.
  - DELIV_SCHED_TYPE_MRP_RLVNCE_CODE
```
public static final SalesSchedgAgrmtField<String> DELIV_SCHED_TYPE_MRP_RLVNCE_CODE
```
    Use with available fluent helpers to apply the DelivSchedTypeMRPRlvnceCode field to query operations.
  - AGRMT_VALDTY_START_DATE
```
public static final SalesSchedgAgrmtField<LocalDateTime> AGRMT_VALDTY_START_DATE
```
    Use with available fluent helpers to apply the AgrmtValdtyStartDate field to query operations.
  - AGRMT_VALDTY_END_DATE
```
public static final SalesSchedgAgrmtField<LocalDateTime> AGRMT_VALDTY_END_DATE
```
    Use with available fluent helpers to apply the AgrmtValdtyEndDate field to query operations.
  - MATL_USAGE_INDICATOR
```
public static final SalesSchedgAgrmtField<String> MATL_USAGE_INDICATOR
```
    Use with available fluent helpers to apply the MatlUsageIndicator field to query operations.
  - HEADER_BILLING_BLOCK_REASON
```
public static final SalesSchedgAgrmtField<String> HEADER_BILLING_BLOCK_REASON
```
    Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final SalesSchedgAgrmtField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - PAYMENT_METHOD
```
public static final SalesSchedgAgrmtField<String> PAYMENT_METHOD
```
    Use with available fluent helpers to apply the PaymentMethod field to query operations.
  - FISCAL_YEAR
```
public static final SalesSchedgAgrmtField<String> FISCAL_YEAR
```
    Use with available fluent helpers to apply the FiscalYear field to query operations.
  - FISCAL_PERIOD
```
public static final SalesSchedgAgrmtField<String> FISCAL_PERIOD
```
    Use with available fluent helpers to apply the FiscalPeriod field to query operations.
  - OVERALL_SD_PROCESS_STATUS
```
public static final SalesSchedgAgrmtField<String> OVERALL_SD_PROCESS_STATUS
```
    Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
  - OVERALL_SD_DOCUMENT_REJECTION_STS
```
public static final SalesSchedgAgrmtField<String> OVERALL_SD_DOCUMENT_REJECTION_STS
```
    Use with available fluent helpers to apply the OverallSDDocumentRejectionSts field to query operations.
  - TOTAL_BLOCK_STATUS
```
public static final SalesSchedgAgrmtField<String> TOTAL_BLOCK_STATUS
```
    Use with available fluent helpers to apply the TotalBlockStatus field to query operations.
  - OVERALL_DELIVERY_STATUS
```
public static final SalesSchedgAgrmtField<String> OVERALL_DELIVERY_STATUS
```
    Use with available fluent helpers to apply the OverallDeliveryStatus field to query operations.
  - OVERALL_DELIVERY_BLOCK_STATUS
```
public static final SalesSchedgAgrmtField<String> OVERALL_DELIVERY_BLOCK_STATUS
```
    Use with available fluent helpers to apply the OverallDeliveryBlockStatus field to query operations.
  - OVERALL_BILLING_BLOCK_STATUS
```
public static final SalesSchedgAgrmtField<String> OVERALL_BILLING_BLOCK_STATUS
```
    Use with available fluent helpers to apply the OverallBillingBlockStatus field to query operations.
  - TOTAL_CREDIT_CHECK_STATUS
```
public static final SalesSchedgAgrmtField<String> TOTAL_CREDIT_CHECK_STATUS
```
    Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
  - TO_ITEM
```
public static final SalesSchedgAgrmtLink<SalesSchedgAgrmtItem> TO_ITEM
```
    Use with available fluent helpers to apply the to_Item navigation property to query operations.
  - TO_PARTNER
```
public static final SalesSchedgAgrmtLink<SalesSchedgAgrmtPartner> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final SalesSchedgAgrmtLink<SalesSchedgAgrmtPrcgElement> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
  - TO_TEXT
```
public static final SalesSchedgAgrmtLink<SalesSchedgAgrmtText> TO_TEXT
```
    Use with available fluent helpers to apply the to_Text navigation property to query operations.
- Constructor Detail
  - SalesSchedgAgrmt
```
public SalesSchedgAgrmt()
```
  - SalesSchedgAgrmt
```
public SalesSchedgAgrmt(@Nullable
                        String salesSchedulingAgreement,
                        @Nullable
                        String salesSchedgAgrmtType,
                        @Nullable
                        String createdByUser,
                        @Nullable
                        String lastChangedByUser,
                        @Nullable
                        LocalDateTime creationDate,
                        @Nullable
                        LocalTime creationTime,
                        @Nullable
                        LocalDateTime lastChangeDate,
                        @Nullable
                        ZonedDateTime lastChangeDateTime,
                        @Nullable
                        String salesOrganization,
                        @Nullable
                        String distributionChannel,
                        @Nullable
                        String organizationDivision,
                        @Nullable
                        String salesGroup,
                        @Nullable
                        String salesOffice,
                        @Nullable
                        String soldToParty,
                        @Nullable
                        LocalDateTime salesSchedgAgrmtDate,
                        @Nullable
                        String sDDocumentReason,
                        @Nullable
                        String purchaseOrderByCustomer,
                        @Nullable
                        String customerPurchaseOrderType,
                        @Nullable
                        LocalDateTime customerPurchaseOrderDate,
                        @Nullable
                        String salesDistrict,
                        @Nullable
                        BigDecimal totalNetAmount,
                        @Nullable
                        String transactionCurrency,
                        @Nullable
                        LocalDateTime pricingDate,
                        @Nullable
                        String shippingType,
                        @Nullable
                        String shippingCondition,
                        @Nullable
                        String incotermsVersion,
                        @Nullable
                        String incotermsClassification,
                        @Nullable
                        String incotermsTransferLocation,
                        @Nullable
                        String incotermsLocation1,
                        @Nullable
                        String incotermsLocation2,
                        @Nullable
                        String deliveryBlockReason,
                        @Nullable
                        String delivSchedTypeMRPRlvnceCode,
                        @Nullable
                        LocalDateTime agrmtValdtyStartDate,
                        @Nullable
                        LocalDateTime agrmtValdtyEndDate,
                        @Nullable
                        String matlUsageIndicator,
                        @Nullable
                        String headerBillingBlockReason,
                        @Nullable
                        String customerPaymentTerms,
                        @Nullable
                        String paymentMethod,
                        @Nullable
                        String fiscalYear,
                        @Nullable
                        String fiscalPeriod,
                        @Nullable
                        String overallSDProcessStatus,
                        @Nullable
                        String overallSDDocumentRejectionSts,
                        @Nullable
                        String totalBlockStatus,
                        @Nullable
                        String overallDeliveryStatus,
                        @Nullable
                        String overallDeliveryBlockStatus,
                        @Nullable
                        String overallBillingBlockStatus,
                        @Nullable
                        String totalCreditCheckStatus,
                        List<SalesSchedgAgrmtItem> toItem,
                        List<SalesSchedgAgrmtPartner> toPartner,
                        List<SalesSchedgAgrmtPrcgElement> toPricingElement,
                        List<SalesSchedgAgrmtText> toText)
```
- Method Detail
  - getType
```
@Nonnull
public Class<SalesSchedgAgrmt> getType()
```
    Specified by:
    
    getType in class VdmObject<SalesSchedgAgrmt>
    
    Returns:
    
    The class of this object.
  - setSalesSchedulingAgreement
```
public void setSalesSchedulingAgreement(@Nullable
                                        String salesSchedulingAgreement)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesSchedulingAgreement
    
    Parameters:
    
    salesSchedulingAgreement - The number that uniquely identifies the sales scheduling agreement.
  - setSalesSchedgAgrmtType
```
public void setSalesSchedgAgrmtType(@Nullable
                                    String salesSchedgAgrmtType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesSchedgAgrmtType
    
    Parameters:
    
    salesSchedgAgrmtType - A classification that distinguishes between different kinds of sales scheduling agreements.
  - setCreatedByUser
```
public void setCreatedByUser(@Nullable
                             String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Parameters:
    
    createdByUser - Name of Person Who Created Object
  - setLastChangedByUser
```
public void setLastChangedByUser(@Nullable
                                 String lastChangedByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: LastChangedByUser
    
    Parameters:
    
    lastChangedByUser - User Who Last Changed the Business Document
  - setCreationDate
```
public void setCreationDate(@Nullable
                            LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Parameters:
    
    creationDate - Date on Which Record Was Created
  - setCreationTime
```
public void setCreationTime(@Nullable
                            LocalTime creationTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
    
    Parameters:
    
    creationTime - Time at Which Record Was Created
  - setLastChangeDate
```
public void setLastChangeDate(@Nullable
                              LocalDateTime lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Parameters:
    
    lastChangeDate - Date of Last Change
  - setLastChangeDateTime
```
public void setLastChangeDateTime(@Nullable
                                  ZonedDateTime lastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Parameters:
    
    lastChangeDateTime - The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).
  - setSalesOrganization
```
public void setSalesOrganization(@Nullable
                                 String salesOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrganization
    
    You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
    
    Parameters:
    
    salesOrganization - An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.
  - setDistributionChannel
```
public void setDistributionChannel(@Nullable
                                   String distributionChannel)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DistributionChannel
    
    You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
    
    Parameters:
    
    distributionChannel - The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.
  - setOrganizationDivision
```
public void setOrganizationDivision(@Nullable
                                    String organizationDivision)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: OrganizationDivision
    
    A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
    
    Parameters:
    
    organizationDivision - A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.
  - setSalesGroup
```
public void setSalesGroup(@Nullable
                          String salesGroup)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SalesGroup
    
    By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
    
    Parameters:
    
    salesGroup - A group of sales people who are responsible for processing sales of certain products or services.
  - setSalesOffice
```
public void setSalesOffice(@Nullable
                           String salesOffice)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOffice
    
    When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
    
    Parameters:
    
    salesOffice - A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.
  - setSoldToParty
```
public void setSoldToParty(@Nullable
                           String soldToParty)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SoldToParty
    
    Parameters:
    
    soldToParty - Sold-to Party
  - setSalesSchedgAgrmtDate
```
public void setSalesSchedgAgrmtDate(@Nullable
                                    LocalDateTime salesSchedgAgrmtDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesSchedgAgrmtDate
    
    When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected. You can define the document date to meet the needs of your organization.For sales orders, for example, you can define the document date as the date when the order actually arrives at your offices. Alternatively, you could define it as the date when the order was written up by a field sales representative.The system proposes the current date. You can change it manually in the sales document.
    
    Parameters:
    
    salesSchedgAgrmtDate - The date on which you want the sales document (the sales order, for example) to become effective for sales management purposes.
  - setSDDocumentReason
```
public void setSDDocumentReason(@Nullable
                                String sDDocumentReason)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SDDocumentReason
    
    You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria.Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason.If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
    
    Parameters:
    
    sDDocumentReason - Indicates the reason for creating the sales document.
  - setPurchaseOrderByCustomer
```
public void setPurchaseOrderByCustomer(@Nullable
                                       String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    
    Parameters:
    
    purchaseOrderByCustomer - Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).
  - setCustomerPurchaseOrderType
```
public void setCustomerPurchaseOrderType(@Nullable
                                         String customerPurchaseOrderType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPurchaseOrderType
    
    You can record here whether the sales document arrived, for example, by telephone, mail, or fax.Enter one of the values predefined for your system.
    
    Parameters:
    
    customerPurchaseOrderType - The way in which the sales document (the inquiry or sales order, for example) arrives from the customer.
  - setCustomerPurchaseOrderDate
```
public void setCustomerPurchaseOrderDate(@Nullable
                                         LocalDateTime customerPurchaseOrderDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CustomerPurchaseOrderDate
    
    Parameters:
    
    customerPurchaseOrderDate - The date that appears on the customer's purchase order. This date can be, for example, the date on which the customer created the purchase order.
  - 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.
  - setTotalNetAmount
```
public void setTotalNetAmount(@Nullable
                              BigDecimal totalNetAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: TotalNetAmount
    
    Parameters:
    
    totalNetAmount - The total value of all items in the sales document, after any discounts and surcharges are taken into account. The value is expressed in the document currency.
  - setTransactionCurrency
```
public void setTransactionCurrency(@Nullable
                                   String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: TransactionCurrency
    
    The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
    
    Parameters:
    
    transactionCurrency - The currency that applies to the document (for example, to a sales order or an invoice).
  - setPricingDate
```
public void setPricingDate(@Nullable
                           LocalDateTime pricingDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PricingDate
    
    You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
    
    Parameters:
    
    pricingDate - The date that determines date-related pricing elements, such as conditions and foreign exchange rate.
  - setShippingType
```
public void setShippingType(@Nullable
                            String shippingType)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingType
    
    During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
    
    Parameters:
    
    shippingType - Shipping type (for example, by road or rail) that has been selected for the transportation of the goods for the shipment legs.
  - 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.
  - 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).
  - setIncotermsClassification
```
public void setIncotermsClassification(@Nullable
                                       String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Parameters:
    
    incotermsClassification - Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - setIncotermsTransferLocation
```
public void setIncotermsTransferLocation(@Nullable
                                         String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Parameters:
    
    incotermsTransferLocation - Additional information for the primary Incoterm.
  - setIncotermsLocation1
```
public void setIncotermsLocation1(@Nullable
                                  String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    
    1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Parameters:
    
    incotermsLocation1 - Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - setIncotermsLocation2
```
public void setIncotermsLocation2(@Nullable
                                  String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Parameters:
    
    incotermsLocation2 - Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:
  - setDeliveryBlockReason
```
public void setDeliveryBlockReason(@Nullable
                                   String deliveryBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryBlockReason
    
    The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
    
    Parameters:
    
    deliveryBlockReason - Indicates if an entire sales document (a sales order, for example) is blocked for delivery.
  - setDelivSchedTypeMRPRlvnceCode
```
public void setDelivSchedTypeMRPRlvnceCode(@Nullable
                                           String delivSchedTypeMRPRlvnceCode)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DelivSchedTypeMRPRlvnceCode
    
    The SAP System contains the following requirements planning settings:No delivery schedules are used.This indicator is default for all sales documents without delivery schedules.Only forecast delivery schedules are relevant for requirements planning. Forecast delivery schedules and JIT (just-in-time) delivery schedules are relevant for delivery, depending on their validity.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning and delivery, depending on their validity.Only forecast delivery schedules are relevant for requirements planning. Only JIT delivery schedules are relevant for delivery.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning, depending on their validity. Only JIT delivery schedules are relevant for delivery.JIT delivery schedules are not used.You have set material requirements planning indicator B (Forecast and JIT delivery schedules are relevant for requirements planning and delivery) in the scheduling agreement header. The forecast delivery schedule contains schedule lines from January 1 up to March 31. The JIT delivery schedule horizon covers the period up to January 31. The JIT delivery schedule is relevant for requirements planning and delivery within this horizon. As of February 1, the forecast delivery schedule is relevant for requirements planning and delivery.
    
    Parameters:
    
    delivSchedTypeMRPRlvnceCode - Specifies whether forecast delivery schedules or JIT delivery schedules are relevant for planning and/or delivery.
  - setAgrmtValdtyStartDate
```
public void setAgrmtValdtyStartDate(@Nullable
                                    LocalDateTime agrmtValdtyStartDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: AgrmtValdtyStartDate
    
    Parameters:
    
    agrmtValdtyStartDate - Valid-from Date
  - setAgrmtValdtyEndDate
```
public void setAgrmtValdtyEndDate(@Nullable
                                  LocalDateTime agrmtValdtyEndDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: AgrmtValdtyEndDate
    
    Parameters:
    
    agrmtValdtyEndDate - Valid-to Date
  - setMatlUsageIndicator
```
public void setMatlUsageIndicator(@Nullable
                                  String matlUsageIndicator)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: MatlUsageIndicator
    
    The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.The same material, but with different uses, can be sold to the same customer in separate items or orders.Enter whether the material is:A spare, or replacement partA samplePart of a series, used in repetitive manufacturing
    
    Parameters:
    
    matlUsageIndicator - Defines how the material is used.
  - setHeaderBillingBlockReason
```
public void setHeaderBillingBlockReason(@Nullable
                                        String headerBillingBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: HeaderBillingBlockReason
    
    The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
    
    Parameters:
    
    headerBillingBlockReason - Indicates if the entire sales document is blocked for billing.
  - setCustomerPaymentTerms
```
public void setCustomerPaymentTerms(@Nullable
                                    String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Parameters:
    
    customerPaymentTerms - Key for defining payment terms composed of cash discount percentages and payment periods.
  - setPaymentMethod
```
public void setPaymentMethod(@Nullable
                             String paymentMethod)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentMethod
    
    If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
    
    Parameters:
    
    paymentMethod - Payment method with which this item is to be paid.
  - setFiscalYear
```
public void setFiscalYear(@Nullable
                          String fiscalYear)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: FiscalYear
    
    Parameters:
    
    fiscalYear - Period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The fiscal year can be the same as the calendar year, but does not have to be.
  - setFiscalPeriod
```
public void setFiscalPeriod(@Nullable
                            String fiscalPeriod)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: FiscalPeriod
    
    Every business transaction is allocated to a posting period. The monthly debits and credits of the different business transactions are accumulated per posting period.Examples of period classifications:Per calendar month -> 12 posting periodsEvery 4 weeks -> 13 posting periodsWeekly -> 52 or 53 posting periods
    
    Parameters:
    
    fiscalPeriod - A posting period is a self-contained part of a fiscal year.
  - setOverallSDProcessStatus
```
public void setOverallSDProcessStatus(@Nullable
                                      String overallSDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDProcessStatus
    
    The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
    
    Parameters:
    
    overallSDProcessStatus - The processing status of the entire sales document.
  - setOverallSDDocumentRejectionSts
```
public void setOverallSDDocumentRejectionSts(@Nullable
                                             String overallSDDocumentRejectionSts)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDDocumentRejectionSts
    
    The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.
    
    Parameters:
    
    overallSDDocumentRejectionSts - Displays the rejection status of the entire sales document.
  - setTotalBlockStatus
```
public void setTotalBlockStatus(@Nullable
                                String totalBlockStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalBlockStatus
    
    The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
    
    Parameters:
    
    totalBlockStatus - Overall blocked status.
  - setOverallDeliveryStatus
```
public void setOverallDeliveryStatus(@Nullable
                                     String overallDeliveryStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallDeliveryStatus
    
    Parameters:
    
    overallDeliveryStatus - The delivery status of the sales document.
  - setOverallDeliveryBlockStatus
```
public void setOverallDeliveryBlockStatus(@Nullable
                                          String overallDeliveryBlockStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallDeliveryBlockStatus
    
    Item delivery block status + Document header delivery block + user status for header
    
    Parameters:
    
    overallDeliveryBlockStatus - The value of this field is calculated using the following values:
  - setOverallBillingBlockStatus
```
public void setOverallBillingBlockStatus(@Nullable
                                         String overallBillingBlockStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallBillingBlockStatus
    
    Billing block status of item + sales document billing block + user status header
    
    Parameters:
    
    overallBillingBlockStatus - The value of the overall billing block field is calculated using the:
  - setTotalCreditCheckStatus
```
public void setTotalCreditCheckStatus(@Nullable
                                      String totalCreditCheckStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalCreditCheckStatus
    
    Parameters:
    
    totalCreditCheckStatus - Overall Status of Credit Checks
  - getEntityCollection
```
protected String getEntityCollection()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Specified by:
    
    getEntityCollection in class VdmEntity<SalesSchedgAgrmt>
    
    Returns:
    
    EDMX name of the entity collection identifier.
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<SalesSchedgAgrmt>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<SalesSchedgAgrmt>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<SalesSchedgAgrmt>
  - field
```
@Nonnull
public static <T> SalesSchedgAgrmtField<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> SalesSchedgAgrmtField<T> field(@Nonnull
                                                                  String fieldName,
                                                                  @Nonnull
                                                                  TypeConverter<T,DomainT> typeConverter)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    DomainT - The type of the extension field as returned by the OData service.
    
    Parameters:
    
    typeConverter - A TypeConverter instance whose first generic type matches the Java type of the field
    
    fieldName - The name of the extension field as returned by the OData service.
    
    Returns:
    
    A representation of an extension field from this entity, holding a reference to the given TypeConverter.
  - getDestinationForFetch
```
@Nullable
public HttpDestinationProperties getDestinationForFetch()
```
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same destination with multiple queries (e.g. fetching associated entities).
    
    Overrides:
    
    getDestinationForFetch in class VdmEntity<SalesSchedgAgrmt>
    
    Returns:
    
    The stored destination for executing queries, or null if no such context has been set.
  - setServicePathForFetch
```
protected void setServicePathForFetch(@Nullable
                                      String servicePathForFetch)
```
    Description copied from class: VdmEntity
    
    The service path only used for the fetch commands of this entity.
    Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    setServicePathForFetch in class VdmEntity<SalesSchedgAgrmt>
  - attachToService
```
public void attachToService(@Nullable
                            String servicePath,
                            @Nonnull
                            HttpDestinationProperties destination)
```
    Description copied from class: VdmEntity
    
    Sets the service path and destination for the fetch commands of this entity. Also applies to any associated entities (navigation properties) that were previously fetched.
    Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    attachToService in class VdmEntity<SalesSchedgAgrmt>
    
    Parameters:
    
    servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were previously fetched. If a null value is provided and the service path has never been set, then the service path will be set to the default defined in the corresponding service interface.
    
    destination - New destination to apply to this entity and any associated entities that were previously fetched.
  - getDefaultServicePath
```
protected String getDefaultServicePath()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Overrides:
    
    getDefaultServicePath in class VdmEntity<SalesSchedgAgrmt>
    
    Returns:
    
    Default context path to the OData service. In other words, everything in between the protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)
  - toMapOfNavigationProperties
```
@Nonnull
protected Map<String,Object> toMapOfNavigationProperties()
```
    Overrides:
    
    toMapOfNavigationProperties in class VdmObject<SalesSchedgAgrmt>
  - fetchItem
```
@Nonnull
public List<SalesSchedgAgrmtItem> fetchItem()
                                              throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesSchedgAgrmtItem entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Item.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SalesSchedgAgrmtItem entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getItemOrFetch
```
@Nonnull
public List<SalesSchedgAgrmtItem> getItemOrFetch()
                                                   throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesSchedgAgrmtItem entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtItem entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getItemIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SalesSchedgAgrmtItem>> getItemIfPresent()
```
    Retrieval of associated SalesSchedgAgrmtItem entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property for an entity SalesSchedgAgrmt has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Item is already loaded, the result will contain the SalesSchedgAgrmtItem entities. If not, an Option with result state empty is returned.
  - setItem
```
public void setItem(@Nonnull
                    List<SalesSchedgAgrmtItem> value)
```
    Overwrites the list of associated SalesSchedgAgrmtItem entities for the loaded navigation property to_Item.
    If the navigation property to_Item of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtItem entities.
  - addItem
```
public void addItem(SalesSchedgAgrmtItem... entity)
```
    Adds elements to the list of associated SalesSchedgAgrmtItem entities. This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtItem entities.
  - fetchPartner
```
@Nonnull
public List<SalesSchedgAgrmtPartner> fetchPartner()
                                                    throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesSchedgAgrmtPartner entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Partner.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SalesSchedgAgrmtPartner entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPartnerOrFetch
```
@Nonnull
public List<SalesSchedgAgrmtPartner> getPartnerOrFetch()
                                                         throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesSchedgAgrmtPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPartner entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPartnerIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SalesSchedgAgrmtPartner>> getPartnerIfPresent()
```
    Retrieval of associated SalesSchedgAgrmtPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property for an entity SalesSchedgAgrmt has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Partner is already loaded, the result will contain the SalesSchedgAgrmtPartner entities. If not, an Option with result state empty is returned.
  - setPartner
```
public void setPartner(@Nonnull
                       List<SalesSchedgAgrmtPartner> value)
```
    Overwrites the list of associated SalesSchedgAgrmtPartner entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPartner entities.
  - addPartner
```
public void addPartner(SalesSchedgAgrmtPartner... entity)
```
    Adds elements to the list of associated SalesSchedgAgrmtPartner entities. This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPartner entities.
  - fetchPricingElement
```
@Nonnull
public List<SalesSchedgAgrmtPrcgElement> fetchPricingElement()
                                                               throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesSchedgAgrmtPrcgElement entities (one to many) associated with this entity. This corresponds to the OData navigation property to_PricingElement.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SalesSchedgAgrmtPrcgElement entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPricingElementOrFetch
```
@Nonnull
public List<SalesSchedgAgrmtPrcgElement> getPricingElementOrFetch()
                                                                    throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesSchedgAgrmtPrcgElement entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPrcgElement entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPricingElementIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SalesSchedgAgrmtPrcgElement>> getPricingElementIfPresent()
```
    Retrieval of associated SalesSchedgAgrmtPrcgElement entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property for an entity SalesSchedgAgrmt has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_PricingElement is already loaded, the result will contain the SalesSchedgAgrmtPrcgElement entities. If not, an Option with result state empty is returned.
  - setPricingElement
```
public void setPricingElement(@Nonnull
                              List<SalesSchedgAgrmtPrcgElement> value)
```
    Overwrites the list of associated SalesSchedgAgrmtPrcgElement entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPrcgElement entities.
  - addPricingElement
```
public void addPricingElement(SalesSchedgAgrmtPrcgElement... entity)
```
    Adds elements to the list of associated SalesSchedgAgrmtPrcgElement entities. This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPrcgElement entities.
  - fetchText
```
@Nonnull
public List<SalesSchedgAgrmtText> fetchText()
                                              throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesSchedgAgrmtText entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Text.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated SalesSchedgAgrmtText entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getTextOrFetch
```
@Nonnull
public List<SalesSchedgAgrmtText> getTextOrFetch()
                                                   throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesSchedgAgrmtText entities (one to many). This corresponds to the OData navigation property to_Text.
    If the navigation property to_Text of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtText entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getTextIfPresent
```
@Nonnull
public io.vavr.control.Option<List<SalesSchedgAgrmtText>> getTextIfPresent()
```
    Retrieval of associated SalesSchedgAgrmtText entities (one to many). This corresponds to the OData navigation property to_Text.
    If the navigation property for an entity SalesSchedgAgrmt has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Text is already loaded, the result will contain the SalesSchedgAgrmtText entities. If not, an Option with result state empty is returned.
  - setText
```
public void setText(@Nonnull
                    List<SalesSchedgAgrmtText> value)
```
    Overwrites the list of associated SalesSchedgAgrmtText entities for the loaded navigation property to_Text.
    If the navigation property to_Text of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtText entities.
  - addText
```
public void addText(SalesSchedgAgrmtText... entity)
```
    Adds elements to the list of associated SalesSchedgAgrmtText entities. This corresponds to the OData navigation property to_Text.
    If the navigation property to_Text of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtText entities.
  - builder
```
@Nonnull
public static SalesSchedgAgrmt.SalesSchedgAgrmtBuilder builder()
```
  - getSalesSchedulingAgreement
```
@Nullable
public String getSalesSchedulingAgreement()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesSchedulingAgreement
    
    Returns:
    
    The number that uniquely identifies the sales scheduling agreement.
  - getSalesSchedgAgrmtType
```
@Nullable
public String getSalesSchedgAgrmtType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesSchedgAgrmtType
    
    Returns:
    
    A classification that distinguishes between different kinds of sales scheduling agreements.
  - getCreatedByUser
```
@Nullable
public String getCreatedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Returns:
    
    Name of Person Who Created Object
  - getLastChangedByUser
```
@Nullable
public String getLastChangedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: LastChangedByUser
    
    Returns:
    
    User Who Last Changed the Business Document
  - getCreationDate
```
@Nullable
public LocalDateTime getCreationDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    Date on Which Record Was Created
  - getCreationTime
```
@Nullable
public LocalTime getCreationTime()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
    
    Returns:
    
    Time at Which Record Was Created
  - getLastChangeDate
```
@Nullable
public LocalDateTime getLastChangeDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Returns:
    
    Date of Last Change
  - getLastChangeDateTime
```
@Nullable
public ZonedDateTime getLastChangeDateTime()
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Returns:
    
    The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).
  - getSalesOrganization
```
@Nullable
public String getSalesOrganization()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrganization
    
    You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
    
    Returns:
    
    An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.
  - getDistributionChannel
```
@Nullable
public String getDistributionChannel()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DistributionChannel
    
    You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
    
    Returns:
    
    The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.
  - getOrganizationDivision
```
@Nullable
public String getOrganizationDivision()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: OrganizationDivision
    
    A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
    
    Returns:
    
    A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.
  - getSalesGroup
```
@Nullable
public String getSalesGroup()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SalesGroup
    
    By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
    
    Returns:
    
    A group of sales people who are responsible for processing sales of certain products or services.
  - getSalesOffice
```
@Nullable
public String getSalesOffice()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOffice
    
    When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
    
    Returns:
    
    A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.
  - getSoldToParty
```
@Nullable
public String getSoldToParty()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SoldToParty
    
    Returns:
    
    Sold-to Party
  - getSalesSchedgAgrmtDate
```
@Nullable
public LocalDateTime getSalesSchedgAgrmtDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesSchedgAgrmtDate
    
    When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected. You can define the document date to meet the needs of your organization.For sales orders, for example, you can define the document date as the date when the order actually arrives at your offices. Alternatively, you could define it as the date when the order was written up by a field sales representative.The system proposes the current date. You can change it manually in the sales document.
    
    Returns:
    
    The date on which you want the sales document (the sales order, for example) to become effective for sales management purposes.
  - getSDDocumentReason
```
@Nullable
public String getSDDocumentReason()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SDDocumentReason
    
    You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria.Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason.If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
    
    Returns:
    
    Indicates the reason for creating the sales document.
  - getPurchaseOrderByCustomer
```
@Nullable
public String getPurchaseOrderByCustomer()
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    
    Returns:
    
    Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).
  - getCustomerPurchaseOrderType
```
@Nullable
public String getCustomerPurchaseOrderType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPurchaseOrderType
    
    You can record here whether the sales document arrived, for example, by telephone, mail, or fax.Enter one of the values predefined for your system.
    
    Returns:
    
    The way in which the sales document (the inquiry or sales order, for example) arrives from the customer.
  - getCustomerPurchaseOrderDate
```
@Nullable
public LocalDateTime getCustomerPurchaseOrderDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CustomerPurchaseOrderDate
    
    Returns:
    
    The date that appears on the customer's purchase order. This date can be, for example, the date on which the customer created the purchase order.
  - 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.
  - getTotalNetAmount
```
@Nullable
public BigDecimal getTotalNetAmount()
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: TotalNetAmount
    
    Returns:
    
    The total value of all items in the sales document, after any discounts and surcharges are taken into account. The value is expressed in the document currency.
  - getTransactionCurrency
```
@Nullable
public String getTransactionCurrency()
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: TransactionCurrency
    
    The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
    
    Returns:
    
    The currency that applies to the document (for example, to a sales order or an invoice).
  - getPricingDate
```
@Nullable
public LocalDateTime getPricingDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PricingDate
    
    You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
    
    Returns:
    
    The date that determines date-related pricing elements, such as conditions and foreign exchange rate.
  - getShippingType
```
@Nullable
public String getShippingType()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingType
    
    During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
    
    Returns:
    
    Shipping type (for example, by road or rail) that has been selected for the transportation of the goods for the shipment legs.
  - 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.
  - 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).
  - getIncotermsClassification
```
@Nullable
public String getIncotermsClassification()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Returns:
    
    Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - getIncotermsTransferLocation
```
@Nullable
public String getIncotermsTransferLocation()
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Returns:
    
    Additional information for the primary Incoterm.
  - getIncotermsLocation1
```
@Nullable
public String getIncotermsLocation1()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    
    1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Returns:
    
    Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - getIncotermsLocation2
```
@Nullable
public String getIncotermsLocation2()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Returns:
    
    Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:
  - getDeliveryBlockReason
```
@Nullable
public String getDeliveryBlockReason()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryBlockReason
    
    The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
    
    Returns:
    
    Indicates if an entire sales document (a sales order, for example) is blocked for delivery.
  - getDelivSchedTypeMRPRlvnceCode
```
@Nullable
public String getDelivSchedTypeMRPRlvnceCode()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DelivSchedTypeMRPRlvnceCode
    
    The SAP System contains the following requirements planning settings:No delivery schedules are used.This indicator is default for all sales documents without delivery schedules.Only forecast delivery schedules are relevant for requirements planning. Forecast delivery schedules and JIT (just-in-time) delivery schedules are relevant for delivery, depending on their validity.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning and delivery, depending on their validity.Only forecast delivery schedules are relevant for requirements planning. Only JIT delivery schedules are relevant for delivery.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning, depending on their validity. Only JIT delivery schedules are relevant for delivery.JIT delivery schedules are not used.You have set material requirements planning indicator B (Forecast and JIT delivery schedules are relevant for requirements planning and delivery) in the scheduling agreement header. The forecast delivery schedule contains schedule lines from January 1 up to March 31. The JIT delivery schedule horizon covers the period up to January 31. The JIT delivery schedule is relevant for requirements planning and delivery within this horizon. As of February 1, the forecast delivery schedule is relevant for requirements planning and delivery.
    
    Returns:
    
    Specifies whether forecast delivery schedules or JIT delivery schedules are relevant for planning and/or delivery.
  - getAgrmtValdtyStartDate
```
@Nullable
public LocalDateTime getAgrmtValdtyStartDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: AgrmtValdtyStartDate
    
    Returns:
    
    Valid-from Date
  - getAgrmtValdtyEndDate
```
@Nullable
public LocalDateTime getAgrmtValdtyEndDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: AgrmtValdtyEndDate
    
    Returns:
    
    Valid-to Date
  - getMatlUsageIndicator
```
@Nullable
public String getMatlUsageIndicator()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: MatlUsageIndicator
    
    The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.The same material, but with different uses, can be sold to the same customer in separate items or orders.Enter whether the material is:A spare, or replacement partA samplePart of a series, used in repetitive manufacturing
    
    Returns:
    
    Defines how the material is used.
  - getHeaderBillingBlockReason
```
@Nullable
public String getHeaderBillingBlockReason()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: HeaderBillingBlockReason
    
    The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
    
    Returns:
    
    Indicates if the entire sales document is blocked for billing.
  - getCustomerPaymentTerms
```
@Nullable
public String getCustomerPaymentTerms()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Returns:
    
    Key for defining payment terms composed of cash discount percentages and payment periods.
  - getPaymentMethod
```
@Nullable
public String getPaymentMethod()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentMethod
    
    If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
    
    Returns:
    
    Payment method with which this item is to be paid.
  - getFiscalYear
```
@Nullable
public String getFiscalYear()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: FiscalYear
    
    Returns:
    
    Period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The fiscal year can be the same as the calendar year, but does not have to be.
  - getFiscalPeriod
```
@Nullable
public String getFiscalPeriod()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: FiscalPeriod
    
    Every business transaction is allocated to a posting period. The monthly debits and credits of the different business transactions are accumulated per posting period.Examples of period classifications:Per calendar month -> 12 posting periodsEvery 4 weeks -> 13 posting periodsWeekly -> 52 or 53 posting periods
    
    Returns:
    
    A posting period is a self-contained part of a fiscal year.
  - getOverallSDProcessStatus
```
@Nullable
public String getOverallSDProcessStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDProcessStatus
    
    The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
    
    Returns:
    
    The processing status of the entire sales document.
  - getOverallSDDocumentRejectionSts
```
@Nullable
public String getOverallSDDocumentRejectionSts()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDDocumentRejectionSts
    
    The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.
    
    Returns:
    
    Displays the rejection status of the entire sales document.
  - getTotalBlockStatus
```
@Nullable
public String getTotalBlockStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalBlockStatus
    
    The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
    
    Returns:
    
    Overall blocked status.
  - getOverallDeliveryStatus
```
@Nullable
public String getOverallDeliveryStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallDeliveryStatus
    
    Returns:
    
    The delivery status of the sales document.
  - getOverallDeliveryBlockStatus
```
@Nullable
public String getOverallDeliveryBlockStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallDeliveryBlockStatus
    
    Item delivery block status + Document header delivery block + user status for header
    
    Returns:
    
    The value of this field is calculated using the following values:
  - getOverallBillingBlockStatus
```
@Nullable
public String getOverallBillingBlockStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallBillingBlockStatus
    
    Billing block status of item + sales document billing block + user status header
    
    Returns:
    
    The value of the overall billing block field is calculated using the:
  - getTotalCreditCheckStatus
```
@Nullable
public String getTotalCreditCheckStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalCreditCheckStatus
    
    Returns:
    
    Overall Status of Credit Checks
  - toString
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class VdmObject<SalesSchedgAgrmt>
  - equals
```
public boolean equals(@Nullable
                      Object o)
```
    Overrides:
    
    equals in class VdmObject<SalesSchedgAgrmt>
  - canEqual
```
protected boolean canEqual(@Nullable
                           Object other)
```
    Overrides:
    
    canEqual in class VdmObject<SalesSchedgAgrmt>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<SalesSchedgAgrmt>

Class SalesSchedgAgrmt

Nested Class Summary

Field Summary

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

Constructor Summary

Method Summary

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

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

SALES_SCHEDULING_AGREEMENT

SALES_SCHEDG_AGRMT_TYPE

CREATED_BY_USER

LAST_CHANGED_BY_USER

CREATION_DATE

CREATION_TIME

LAST_CHANGE_DATE

LAST_CHANGE_DATE_TIME

SALES_ORGANIZATION

DISTRIBUTION_CHANNEL

ORGANIZATION_DIVISION

SALES_GROUP

SALES_OFFICE

SOLD_TO_PARTY

SALES_SCHEDG_AGRMT_DATE

SD_DOCUMENT_REASON

PURCHASE_ORDER_BY_CUSTOMER

CUSTOMER_PURCHASE_ORDER_TYPE

CUSTOMER_PURCHASE_ORDER_DATE

SALES_DISTRICT

TOTAL_NET_AMOUNT

TRANSACTION_CURRENCY

PRICING_DATE

SHIPPING_TYPE

SHIPPING_CONDITION

INCOTERMS_VERSION

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

DELIVERY_BLOCK_REASON

DELIV_SCHED_TYPE_MRP_RLVNCE_CODE

AGRMT_VALDTY_START_DATE

AGRMT_VALDTY_END_DATE

MATL_USAGE_INDICATOR

HEADER_BILLING_BLOCK_REASON

CUSTOMER_PAYMENT_TERMS

PAYMENT_METHOD

FISCAL_YEAR

FISCAL_PERIOD

OVERALL_SD_PROCESS_STATUS

OVERALL_SD_DOCUMENT_REJECTION_STS

TOTAL_BLOCK_STATUS

OVERALL_DELIVERY_STATUS

OVERALL_DELIVERY_BLOCK_STATUS

OVERALL_BILLING_BLOCK_STATUS

TOTAL_CREDIT_CHECK_STATUS

TO_ITEM

TO_PARTNER

TO_PRICING_ELEMENT

TO_TEXT

Constructor Detail

SalesSchedgAgrmt

SalesSchedgAgrmt

Method Detail

getType

setSalesSchedulingAgreement

setSalesSchedgAgrmtType

setCreatedByUser

setLastChangedByUser

setCreationDate

setCreationTime

setLastChangeDate

setLastChangeDateTime

setSalesOrganization

setDistributionChannel

setOrganizationDivision

setSalesGroup

setSalesOffice