DebitMemoRequest (SAP S/4HANA Cloud SDK

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

public class DebitMemoRequest
extends VdmEntity<DebitMemoRequest>

Debit Memo Request (API)

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class DebitMemoRequest.DebitMemoRequestBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`DebitMemoRequest.DebitMemoRequestBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static DebitMemoRequestSelectable`	`ALL_FIELDS` Selector for all available fields of DebitMemoRequest.
`static DebitMemoRequestField<Calendar>`	`BILLING_DOCUMENT_DATE` Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
`static DebitMemoRequestField<String>`	`CREATED_BY_USER` Use with available fluent helpers to apply the CreatedByUser field to query operations.
`static DebitMemoRequestField<Calendar>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static DebitMemoRequestField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static DebitMemoRequestField<Calendar>`	`CUSTOMER_PURCHASE_ORDER_DATE` Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
`static DebitMemoRequestField<String>`	`CUSTOMER_PURCHASE_ORDER_TYPE` Use with available fluent helpers to apply the CustomerPurchaseOrderType field to query operations.
`static DebitMemoRequestField<String>`	`DEBIT_MEMO_REQUEST` Use with available fluent helpers to apply the DebitMemoRequest field to query operations.
`static DebitMemoRequestField<Calendar>`	`DEBIT_MEMO_REQUEST_DATE` Use with available fluent helpers to apply the DebitMemoRequestDate field to query operations.
`static DebitMemoRequestField<String>`	`DEBIT_MEMO_REQUEST_TYPE` Use with available fluent helpers to apply the DebitMemoRequestType field to query operations.
`static DebitMemoRequestField<String>`	`DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the DistributionChannel field to query operations.
`static DebitMemoRequestField<String>`	`HEADER_BILLING_BLOCK_REASON` Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
`static DebitMemoRequestField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static DebitMemoRequestField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static DebitMemoRequestField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static DebitMemoRequestField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static DebitMemoRequestField<String>`	`INCOTERMS_VERSION` Use with available fluent helpers to apply the IncotermsVersion field to query operations.
`static DebitMemoRequestField<Calendar>`	`LAST_CHANGE_DATE` Use with available fluent helpers to apply the LastChangeDate field to query operations.
`static DebitMemoRequestField<Calendar>`	`LAST_CHANGE_DATE_TIME` Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
`static DebitMemoRequestField<String>`	`ORGANIZATION_DIVISION` Use with available fluent helpers to apply the OrganizationDivision field to query operations.
`static DebitMemoRequestField<String>`	`OVERALL_ORD_RELTD_BILLG_STATUS` Use with available fluent helpers to apply the OverallOrdReltdBillgStatus field to query operations.
`static DebitMemoRequestField<String>`	`OVERALL_SD_DOCUMENT_REJECTION_STS` Use with available fluent helpers to apply the OverallSDDocumentRejectionSts field to query operations.
`static DebitMemoRequestField<String>`	`OVERALL_SD_PROCESS_STATUS` Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
`static DebitMemoRequestField<String>`	`PAYMENT_METHOD` Use with available fluent helpers to apply the PaymentMethod field to query operations.
`static DebitMemoRequestField<Calendar>`	`PRICING_DATE` Use with available fluent helpers to apply the PricingDate field to query operations.
`static DebitMemoRequestField<String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static DebitMemoRequestField<String>`	`SALES_DISTRICT` Use with available fluent helpers to apply the SalesDistrict field to query operations.
`static DebitMemoRequestField<String>`	`SALES_GROUP` Use with available fluent helpers to apply the SalesGroup field to query operations.
`static DebitMemoRequestField<String>`	`SALES_OFFICE` Use with available fluent helpers to apply the SalesOffice field to query operations.
`static DebitMemoRequestField<String>`	`SALES_ORGANIZATION` Use with available fluent helpers to apply the SalesOrganization field to query operations.
`static DebitMemoRequestField<String>`	`SD_DOCUMENT_REASON` Use with available fluent helpers to apply the SDDocumentReason field to query operations.
`static DebitMemoRequestField<Calendar>`	`SERVICES_RENDERED_DATE` Use with available fluent helpers to apply the ServicesRenderedDate field to query operations.
`static DebitMemoRequestField<String>`	`SOLD_TO_PARTY` Use with available fluent helpers to apply the SoldToParty field to query operations.
`static DebitMemoRequestLink<DebitMemoRequestItem>`	`TO_ITEM` Use with available fluent helpers to apply the to_Item navigation property to query operations.
`static DebitMemoRequestLink<DebitMemoReqPartner>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static DebitMemoRequestLink<DebitMemoReqPrcgElmnt>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static DebitMemoRequestField<String>`	`TOTAL_CREDIT_CHECK_STATUS` Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
`static DebitMemoRequestField<BigDecimal>`	`TOTAL_NET_AMOUNT` Use with available fluent helpers to apply the TotalNetAmount field to query operations.
`static DebitMemoRequestField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.

Constructor Summary

Constructors
Constructor and Description
`DebitMemoRequest()`
DebitMemoRequest(String debitMemoRequest, String debitMemoRequestType, String salesOrganization, String distributionChannel, String organizationDivision, String salesGroup, String salesOffice, String salesDistrict, String soldToParty, Calendar creationDate, String createdByUser, Calendar lastChangeDate, Calendar lastChangeDateTime, String purchaseOrderByCustomer, String customerPurchaseOrderType, Calendar customerPurchaseOrderDate, Calendar debitMemoRequestDate, BigDecimal totalNetAmount, String transactionCurrency, String sDDocumentReason, Calendar pricingDate, String headerBillingBlockReason, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String incotermsVersion, String customerPaymentTerms, String paymentMethod, Calendar billingDocumentDate, Calendar servicesRenderedDate, String overallSDProcessStatus, String totalCreditCheckStatus, String overallSDDocumentRejectionSts, String overallOrdReltdBillgStatus, ErpConfigContext erpConfigContext, List<DebitMemoRequestItem> toItem, List<DebitMemoReqPartner> toPartner, List<DebitMemoReqPrcgElmnt> toPricingElement)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addItem(DebitMemoRequestItem... entity)` Adds elements to the list of associated DebitMemoRequestItem entities.
`void`	`addPartner(DebitMemoReqPartner... entity)` Adds elements to the list of associated DebitMemoReqPartner entities.
`void`	`addPricingElement(DebitMemoReqPrcgElmnt... entity)` Adds elements to the list of associated DebitMemoReqPrcgElmnt entities.
`static DebitMemoRequest.DebitMemoRequestBuilder`	`builder()`
`boolean`	`equals(Object o)`
`List<DebitMemoRequestItem>`	`fetchItem()` Fetches the DebitMemoRequestItem entities (one to many) associated with this entity.
`List<DebitMemoReqPartner>`	`fetchPartner()` Fetches the DebitMemoReqPartner entities (one to many) associated with this entity.
`List<DebitMemoReqPrcgElmnt>`	`fetchPricingElement()` Fetches the DebitMemoReqPrcgElmnt entities (one to many) associated with this entity.
`static <T> DebitMemoRequestField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`Calendar`	`getBillingDocumentDate()` Constraints: Not nullable, Precision: 0 When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, the system proposes the billing date from the invoice date calendar.
`String`	`getCreatedByUser()` Constraints: Not nullable, Maximum length: 12
`Calendar`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4 It is used in sales orders, purchase orders, and invoices.
`Calendar`	`getCustomerPurchaseOrderDate()` Constraints: Not nullable, Precision: 0
`String`	`getCustomerPurchaseOrderType()` Constraints: Not nullable, Maximum length: 4 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.
`String`	`getDebitMemoRequest()` (Key Field) Constraints: Not nullable, Maximum length: 10
`Calendar`	`getDebitMemoRequestDate()` Constraints: Not nullable, Precision: 0 When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected.
`String`	`getDebitMemoRequestType()` Constraints: Not nullable, Maximum length: 4 The sales document type determines how the system processes the sales document.
`String`	`getDistributionChannel()` Constraints: Not nullable, Maximum length: 2 You can maintain information about customers and materials by sales organization and distribution channel.
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`String`	`getHeaderBillingBlockReason()` Constraints: Not nullable, Maximum length: 2 The system can propose the billing block according to the type of sales document.
`String`	`getIncotermsClassification()` Constraints: Not nullable, Maximum length: 3 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").
`String`	`getIncotermsLocation1()` Constraints: Not nullable, Maximum length: 70 1.
`String`	`getIncotermsLocation2()` Constraints: Not nullable, Maximum length: 70 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
`String`	`getIncotermsTransferLocation()` Constraints: Not nullable, Maximum length: 28 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").
`String`	`getIncotermsVersion()` Constraints: Not nullable, Maximum length: 4
`List<DebitMemoRequestItem>`	`getItemOrFetch()` Retrieval of associated DebitMemoRequestItem entities (one to many).
`com.google.common.base.Optional<List<DebitMemoRequestItem>>`	`getItemOrNull()` Retrieval of associated DebitMemoRequestItem entities (one to many).
`Calendar`	`getLastChangeDate()` Constraints: Not nullable, Precision: 0
`Calendar`	`getLastChangeDateTime()` Constraints: Not nullable, Precision: 7 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.
`String`	`getOrganizationDivision()` Constraints: Not nullable, Maximum length: 2 A product or service is always assigned to just one division.
`String`	`getOverallOrdReltdBillgStatus()` Constraints: Not nullable, Maximum length: 1 The overall billing status tells you whether the sales order or delivery is relevant for billing, and, if so, to what extent billing has taken place.
`String`	`getOverallSDDocumentRejectionSts()` Constraints: Not nullable, Maximum length: 1 The system determines the total status from the status of all individual items in the sales document.
`String`	`getOverallSDProcessStatus()` Constraints: Not nullable, Maximum length: 1 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.
`List<DebitMemoReqPartner>`	`getPartnerOrFetch()` Retrieval of associated DebitMemoReqPartner entities (one to many).
`com.google.common.base.Optional<List<DebitMemoReqPartner>>`	`getPartnerOrNull()` Retrieval of associated DebitMemoReqPartner entities (one to many).
`String`	`getPaymentMethod()` Constraints: Not nullable, Maximum length: 1 If you enter a payment method, then only this payment method can be used in automatic payment transactions.
`Calendar`	`getPricingDate()` Constraints: Not nullable, Precision: 0 You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date.
`List<DebitMemoReqPrcgElmnt>`	`getPricingElementOrFetch()` Retrieval of associated DebitMemoReqPrcgElmnt entities (one to many).
`com.google.common.base.Optional<List<DebitMemoReqPrcgElmnt>>`	`getPricingElementOrNull()` Retrieval of associated DebitMemoReqPrcgElmnt entities (one to many).
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35 The number creates the link between the customer purchase order and the sales document that you create.
`String`	`getSalesDistrict()` Constraints: Not nullable, Maximum length: 6 Each customer can be assigned to a sales district.
`String`	`getSalesGroup()` Constraints: Not nullable, Maximum length: 3 By using sales groups you can designate different areas of responsibility within a sales office.
`String`	`getSalesOffice()` Constraints: Not nullable, Maximum length: 4 When you create sales statistics, you can use a sales office as one of the selection criteria.
`String`	`getSalesOrganization()` Constraints: Not nullable, Maximum length: 4 You can assign any number of distribution channels and divisions to a sales organization.
`String`	`getSDDocumentReason()` Constraints: Not nullable, Maximum length: 3 You can freely define order reasons according to the needs of your organization.
`Calendar`	`getServicesRenderedDate()` Constraints: Not nullable, Precision: 0 If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field.
`String`	`getSoldToParty()` Constraints: Not nullable, Maximum length: 10
`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 The system proposes the document currency from the customer master record of the sold-to party.
`Class<DebitMemoRequest>`	`getType()`
`int`	`hashCode()`
`void`	`setBillingDocumentDate(Calendar billingDocumentDate)` Constraints: Not nullable, Precision: 0 When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, the system proposes the billing date from the invoice date calendar.
`void`	`setCreatedByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreationDate(Calendar creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4 It is used in sales orders, purchase orders, and invoices.
`void`	`setCustomerPurchaseOrderDate(Calendar customerPurchaseOrderDate)` Constraints: Not nullable, Precision: 0
`void`	`setCustomerPurchaseOrderType(String customerPurchaseOrderType)` Constraints: Not nullable, Maximum length: 4 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.
`void`	`setDebitMemoRequest(String debitMemoRequest)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setDebitMemoRequestDate(Calendar debitMemoRequestDate)` Constraints: Not nullable, Precision: 0 When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected.
`void`	`setDebitMemoRequestType(String debitMemoRequestType)` Constraints: Not nullable, Maximum length: 4 The sales document type determines how the system processes the sales document.
`void`	`setDistributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2 You can maintain information about customers and materials by sales organization and distribution channel.
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`void`	`setHeaderBillingBlockReason(String headerBillingBlockReason)` Constraints: Not nullable, Maximum length: 2 The system can propose the billing block according to the type of sales document.
`void`	`setIncotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3 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").
`void`	`setIncotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70 1.
`void`	`setIncotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70 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
`void`	`setIncotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28 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").
`void`	`setIncotermsVersion(String incotermsVersion)` Constraints: Not nullable, Maximum length: 4
`void`	`setItem(List<DebitMemoRequestItem> value)` Overwrites the list of associated DebitMemoRequestItem entities for the loaded navigation property to_Item.
`void`	`setLastChangeDate(Calendar lastChangeDate)` Constraints: Not nullable, Precision: 0
`void`	`setLastChangeDateTime(Calendar lastChangeDateTime)` Constraints: Not nullable, Precision: 7 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.
`void`	`setOrganizationDivision(String organizationDivision)` Constraints: Not nullable, Maximum length: 2 A product or service is always assigned to just one division.
`void`	`setOverallOrdReltdBillgStatus(String overallOrdReltdBillgStatus)` Constraints: Not nullable, Maximum length: 1 The overall billing status tells you whether the sales order or delivery is relevant for billing, and, if so, to what extent billing has taken place.
`void`	`setOverallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)` Constraints: Not nullable, Maximum length: 1 The system determines the total status from the status of all individual items in the sales document.
`void`	`setOverallSDProcessStatus(String overallSDProcessStatus)` Constraints: Not nullable, Maximum length: 1 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.
`void`	`setPartner(List<DebitMemoReqPartner> value)` Overwrites the list of associated DebitMemoReqPartner entities for the loaded navigation property to_Partner.
`void`	`setPaymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1 If you enter a payment method, then only this payment method can be used in automatic payment transactions.
`void`	`setPricingDate(Calendar pricingDate)` Constraints: Not nullable, Precision: 0 You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date.
`void`	`setPricingElement(List<DebitMemoReqPrcgElmnt> value)` Overwrites the list of associated DebitMemoReqPrcgElmnt entities for the loaded navigation property to_PricingElement.
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35 The number creates the link between the customer purchase order and the sales document that you create.
`void`	`setSalesDistrict(String salesDistrict)` Constraints: Not nullable, Maximum length: 6 Each customer can be assigned to a sales district.
`void`	`setSalesGroup(String salesGroup)` Constraints: Not nullable, Maximum length: 3 By using sales groups you can designate different areas of responsibility within a sales office.
`void`	`setSalesOffice(String salesOffice)` Constraints: Not nullable, Maximum length: 4 When you create sales statistics, you can use a sales office as one of the selection criteria.
`void`	`setSalesOrganization(String salesOrganization)` Constraints: Not nullable, Maximum length: 4 You can assign any number of distribution channels and divisions to a sales organization.
`void`	`setSDDocumentReason(String sDDocumentReason)` Constraints: Not nullable, Maximum length: 3 You can freely define order reasons according to the needs of your organization.
`void`	`setServicesRenderedDate(Calendar servicesRenderedDate)` Constraints: Not nullable, Precision: 0 If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field.
`void`	`setSoldToParty(String soldToParty)` Constraints: Not nullable, Maximum length: 10
`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 The system proposes the document currency from the customer master record of the sold-to party.
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField

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

- Field Detail
  - ALL_FIELDS
```
public static final DebitMemoRequestSelectable ALL_FIELDS
```
    Selector for all available fields of DebitMemoRequest.
  - DEBIT_MEMO_REQUEST
```
public static final DebitMemoRequestField<String> DEBIT_MEMO_REQUEST
```
    Use with available fluent helpers to apply the DebitMemoRequest field to query operations.
  - DEBIT_MEMO_REQUEST_TYPE
```
public static final DebitMemoRequestField<String> DEBIT_MEMO_REQUEST_TYPE
```
    Use with available fluent helpers to apply the DebitMemoRequestType field to query operations.
  - SALES_ORGANIZATION
```
public static final DebitMemoRequestField<String> SALES_ORGANIZATION
```
    Use with available fluent helpers to apply the SalesOrganization field to query operations.
  - DISTRIBUTION_CHANNEL
```
public static final DebitMemoRequestField<String> DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the DistributionChannel field to query operations.
  - ORGANIZATION_DIVISION
```
public static final DebitMemoRequestField<String> ORGANIZATION_DIVISION
```
    Use with available fluent helpers to apply the OrganizationDivision field to query operations.
  - SALES_GROUP
```
public static final DebitMemoRequestField<String> SALES_GROUP
```
    Use with available fluent helpers to apply the SalesGroup field to query operations.
  - SALES_OFFICE
```
public static final DebitMemoRequestField<String> SALES_OFFICE
```
    Use with available fluent helpers to apply the SalesOffice field to query operations.
  - SALES_DISTRICT
```
public static final DebitMemoRequestField<String> SALES_DISTRICT
```
    Use with available fluent helpers to apply the SalesDistrict field to query operations.
  - SOLD_TO_PARTY
```
public static final DebitMemoRequestField<String> SOLD_TO_PARTY
```
    Use with available fluent helpers to apply the SoldToParty field to query operations.
  - CREATION_DATE
```
public static final DebitMemoRequestField<Calendar> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - CREATED_BY_USER
```
public static final DebitMemoRequestField<String> CREATED_BY_USER
```
    Use with available fluent helpers to apply the CreatedByUser field to query operations.
  - LAST_CHANGE_DATE
```
public static final DebitMemoRequestField<Calendar> LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the LastChangeDate field to query operations.
  - LAST_CHANGE_DATE_TIME
```
public static final DebitMemoRequestField<Calendar> LAST_CHANGE_DATE_TIME
```
    Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final DebitMemoRequestField<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 DebitMemoRequestField<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 DebitMemoRequestField<Calendar> CUSTOMER_PURCHASE_ORDER_DATE
```
    Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
  - DEBIT_MEMO_REQUEST_DATE
```
public static final DebitMemoRequestField<Calendar> DEBIT_MEMO_REQUEST_DATE
```
    Use with available fluent helpers to apply the DebitMemoRequestDate field to query operations.
  - TOTAL_NET_AMOUNT
```
public static final DebitMemoRequestField<BigDecimal> TOTAL_NET_AMOUNT
```
    Use with available fluent helpers to apply the TotalNetAmount field to query operations.
  - TRANSACTION_CURRENCY
```
public static final DebitMemoRequestField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - SD_DOCUMENT_REASON
```
public static final DebitMemoRequestField<String> SD_DOCUMENT_REASON
```
    Use with available fluent helpers to apply the SDDocumentReason field to query operations.
  - PRICING_DATE
```
public static final DebitMemoRequestField<Calendar> PRICING_DATE
```
    Use with available fluent helpers to apply the PricingDate field to query operations.
  - HEADER_BILLING_BLOCK_REASON
```
public static final DebitMemoRequestField<String> HEADER_BILLING_BLOCK_REASON
```
    Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final DebitMemoRequestField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final DebitMemoRequestField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final DebitMemoRequestField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final DebitMemoRequestField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - INCOTERMS_VERSION
```
public static final DebitMemoRequestField<String> INCOTERMS_VERSION
```
    Use with available fluent helpers to apply the IncotermsVersion field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final DebitMemoRequestField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - PAYMENT_METHOD
```
public static final DebitMemoRequestField<String> PAYMENT_METHOD
```
    Use with available fluent helpers to apply the PaymentMethod field to query operations.
  - BILLING_DOCUMENT_DATE
```
public static final DebitMemoRequestField<Calendar> BILLING_DOCUMENT_DATE
```
    Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
  - SERVICES_RENDERED_DATE
```
public static final DebitMemoRequestField<Calendar> SERVICES_RENDERED_DATE
```
    Use with available fluent helpers to apply the ServicesRenderedDate field to query operations.
  - OVERALL_SD_PROCESS_STATUS
```
public static final DebitMemoRequestField<String> OVERALL_SD_PROCESS_STATUS
```
    Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
  - TOTAL_CREDIT_CHECK_STATUS
```
public static final DebitMemoRequestField<String> TOTAL_CREDIT_CHECK_STATUS
```
    Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
  - OVERALL_SD_DOCUMENT_REJECTION_STS
```
public static final DebitMemoRequestField<String> OVERALL_SD_DOCUMENT_REJECTION_STS
```
    Use with available fluent helpers to apply the OverallSDDocumentRejectionSts field to query operations.
  - OVERALL_ORD_RELTD_BILLG_STATUS
```
public static final DebitMemoRequestField<String> OVERALL_ORD_RELTD_BILLG_STATUS
```
    Use with available fluent helpers to apply the OverallOrdReltdBillgStatus field to query operations.
  - TO_ITEM
```
public static final DebitMemoRequestLink<DebitMemoRequestItem> TO_ITEM
```
    Use with available fluent helpers to apply the to_Item navigation property to query operations.
  - TO_PARTNER
```
public static final DebitMemoRequestLink<DebitMemoReqPartner> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final DebitMemoRequestLink<DebitMemoReqPrcgElmnt> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
- Constructor Detail
  - DebitMemoRequest
```
public DebitMemoRequest()
```
  - DebitMemoRequest
```
public DebitMemoRequest(@Nullable
                        String debitMemoRequest,
                        @Nullable
                        String debitMemoRequestType,
                        @Nullable
                        String salesOrganization,
                        @Nullable
                        String distributionChannel,
                        @Nullable
                        String organizationDivision,
                        @Nullable
                        String salesGroup,
                        @Nullable
                        String salesOffice,
                        @Nullable
                        String salesDistrict,
                        @Nullable
                        String soldToParty,
                        @Nullable
                        Calendar creationDate,
                        @Nullable
                        String createdByUser,
                        @Nullable
                        Calendar lastChangeDate,
                        @Nullable
                        Calendar lastChangeDateTime,
                        @Nullable
                        String purchaseOrderByCustomer,
                        @Nullable
                        String customerPurchaseOrderType,
                        @Nullable
                        Calendar customerPurchaseOrderDate,
                        @Nullable
                        Calendar debitMemoRequestDate,
                        @Nullable
                        BigDecimal totalNetAmount,
                        @Nullable
                        String transactionCurrency,
                        @Nullable
                        String sDDocumentReason,
                        @Nullable
                        Calendar pricingDate,
                        @Nullable
                        String headerBillingBlockReason,
                        @Nullable
                        String incotermsClassification,
                        @Nullable
                        String incotermsTransferLocation,
                        @Nullable
                        String incotermsLocation1,
                        @Nullable
                        String incotermsLocation2,
                        @Nullable
                        String incotermsVersion,
                        @Nullable
                        String customerPaymentTerms,
                        @Nullable
                        String paymentMethod,
                        @Nullable
                        Calendar billingDocumentDate,
                        @Nullable
                        Calendar servicesRenderedDate,
                        @Nullable
                        String overallSDProcessStatus,
                        @Nullable
                        String totalCreditCheckStatus,
                        @Nullable
                        String overallSDDocumentRejectionSts,
                        @Nullable
                        String overallOrdReltdBillgStatus,
                        @Nullable
                        ErpConfigContext erpConfigContext,
                        List<DebitMemoRequestItem> toItem,
                        List<DebitMemoReqPartner> toPartner,
                        List<DebitMemoReqPrcgElmnt> toPricingElement)
```
- Method Detail
  - getType
```
public Class<DebitMemoRequest> getType()
```
    Specified by:
    
    getType in class VdmObject<DebitMemoRequest>
    
    Returns:
    
    The class of this object.
  - field
```
public static <T> DebitMemoRequestField<T> field(String fieldName,
                                                 Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    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.
  - fetchItem
```
public List<DebitMemoRequestItem> fetchItem()
                                     throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the DebitMemoRequestItem 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 DebitMemoRequestItem 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
```
public List<DebitMemoRequestItem> getItemOrFetch()
                                          throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated DebitMemoRequestItem entities (one to many).
    If the navigation property to_Item of a queried DebitMemoRequest 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 DebitMemoRequestItem 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.
  - getItemOrNull
```
public com.google.common.base.Optional<List<DebitMemoRequestItem>> getItemOrNull()
```
    Retrieval of associated DebitMemoRequestItem entities (one to many).
    If the navigation property to_Item for an entity DebitMemoRequest has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_Item is already loaded, the result will contain the DebitMemoRequestItem entities. If not, a null value state is returned.
  - setItem
```
public void setItem(@NonNull
                    List<DebitMemoRequestItem> value)
```
    Overwrites the list of associated DebitMemoRequestItem entities for the loaded navigation property to_Item.
    If the navigation property to_Item of a queried DebitMemoRequest 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 DebitMemoRequestItem entities.
  - addItem
```
public void addItem(DebitMemoRequestItem... entity)
```
    Adds elements to the list of associated DebitMemoRequestItem entities.
    If the navigation property to_Item of a queried DebitMemoRequest 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 DebitMemoRequestItem entities.
  - fetchPartner
```
public List<DebitMemoReqPartner> fetchPartner()
                                       throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the DebitMemoReqPartner 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 DebitMemoReqPartner 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
```
public List<DebitMemoReqPartner> getPartnerOrFetch()
                                            throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated DebitMemoReqPartner entities (one to many).
    If the navigation property to_Partner of a queried DebitMemoRequest 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 DebitMemoReqPartner 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.
  - getPartnerOrNull
```
public com.google.common.base.Optional<List<DebitMemoReqPartner>> getPartnerOrNull()
```
    Retrieval of associated DebitMemoReqPartner entities (one to many).
    If the navigation property to_Partner for an entity DebitMemoRequest has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_Partner is already loaded, the result will contain the DebitMemoReqPartner entities. If not, a null value state is returned.
  - setPartner
```
public void setPartner(@NonNull
                       List<DebitMemoReqPartner> value)
```
    Overwrites the list of associated DebitMemoReqPartner entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried DebitMemoRequest 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 DebitMemoReqPartner entities.
  - addPartner
```
public void addPartner(DebitMemoReqPartner... entity)
```
    Adds elements to the list of associated DebitMemoReqPartner entities.
    If the navigation property to_Partner of a queried DebitMemoRequest 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 DebitMemoReqPartner entities.
  - fetchPricingElement
```
public List<DebitMemoReqPrcgElmnt> fetchPricingElement()
                                                throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the DebitMemoReqPrcgElmnt 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 DebitMemoReqPrcgElmnt 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
```
public List<DebitMemoReqPrcgElmnt> getPricingElementOrFetch()
                                                     throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated DebitMemoReqPrcgElmnt entities (one to many).
    If the navigation property to_PricingElement of a queried DebitMemoRequest 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 DebitMemoReqPrcgElmnt 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.
  - getPricingElementOrNull
```
public com.google.common.base.Optional<List<DebitMemoReqPrcgElmnt>> getPricingElementOrNull()
```
    Retrieval of associated DebitMemoReqPrcgElmnt entities (one to many).
    If the navigation property to_PricingElement for an entity DebitMemoRequest has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_PricingElement is already loaded, the result will contain the DebitMemoReqPrcgElmnt entities. If not, a null value state is returned.
  - setPricingElement
```
public void setPricingElement(@NonNull
                              List<DebitMemoReqPrcgElmnt> value)
```
    Overwrites the list of associated DebitMemoReqPrcgElmnt entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried DebitMemoRequest 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 DebitMemoReqPrcgElmnt entities.
  - addPricingElement
```
public void addPricingElement(DebitMemoReqPrcgElmnt... entity)
```
    Adds elements to the list of associated DebitMemoReqPrcgElmnt entities.
    If the navigation property to_PricingElement of a queried DebitMemoRequest 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 DebitMemoReqPrcgElmnt entities.
  - builder
```
public static DebitMemoRequest.DebitMemoRequestBuilder builder()
```
  - getDebitMemoRequest
```
@Nullable
public String getDebitMemoRequest()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Debit Memo Request
  - getDebitMemoRequestType
```
@Nullable
public String getDebitMemoRequestType()
```
    Constraints: Not nullable, Maximum length: 4
    The sales document type determines how the system processes the sales document. For example, depending on the sales document type, the system determines which screens to present and which data to ask you for.
    
    Returns:
    
    A classification that distinguishes between different types of sales document.
  - getSalesOrganization
```
@Nullable
public String getSalesOrganization()
```
    Constraints: Not nullable, Maximum length: 4
    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
    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
    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
    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
    When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
    
    Returns:
    
    A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.
  - getSalesDistrict
```
@Nullable
public String getSalesDistrict()
```
    Constraints: Not nullable, Maximum length: 6
    Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
    
    Returns:
    
    A geographical sales district or region.
  - getSoldToParty
```
@Nullable
public String getSoldToParty()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders.
  - getCreationDate
```
@Nullable
public Calendar getCreationDate()
```
    Constraints: Not nullable, Precision: 0
    
    Returns:
    
    Date on Which Record Was Created
  - getCreatedByUser
```
@Nullable
public String getCreatedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    
    Returns:
    
    Name of Person Who Created Object
  - getLastChangeDate
```
@Nullable
public Calendar getLastChangeDate()
```
    Constraints: Not nullable, Precision: 0
    
    Returns:
    
    Date of Last Change
  - getLastChangeDateTime
```
@Nullable
public Calendar getLastChangeDateTime()
```
    Constraints: Not nullable, Precision: 7
    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).
  - getPurchaseOrderByCustomer
```
@Nullable
public String getPurchaseOrderByCustomer()
```
    Constraints: Not nullable, Maximum length: 35
    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
    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 Calendar getCustomerPurchaseOrderDate()
```
    Constraints: Not nullable, Precision: 0
    
    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.
  - getDebitMemoRequestDate
```
@Nullable
public Calendar getDebitMemoRequestDate()
```
    Constraints: Not nullable, Precision: 0
    When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected. You can define the document date to meet the needs of your organization.For sales orders, for example, you can define the document date as the date when the order actually arrives at your offices. Alternatively, you could define it as the date when the order was written up by a field sales representative.The system proposes the current date. You can change it manually in the sales document.
    
    Returns:
    
    The date on which you want the sales document (the sales order, for example) to become effective for sales management purposes.
  - getTotalNetAmount
```
@Nullable
public BigDecimal getTotalNetAmount()
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    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
    The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
    
    Returns:
    
    The currency that applies to the document (for example, to a sales order or an invoice).
  - getSDDocumentReason
```
@Nullable
public String getSDDocumentReason()
```
    Constraints: Not nullable, Maximum length: 3
    You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria.Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason.If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
    
    Returns:
    
    Indicates the reason for creating the sales document.
  - getPricingDate
```
@Nullable
public Calendar getPricingDate()
```
    Constraints: Not nullable, Precision: 0
    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.
  - getHeaderBillingBlockReason
```
@Nullable
public String getHeaderBillingBlockReason()
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - getIncotermsClassification
```
@Nullable
public String getIncotermsClassification()
```
    Constraints: Not nullable, Maximum length: 3
    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
    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
    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
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Returns:
    
    Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:
  - getIncotermsVersion
```
@Nullable
public String getIncotermsVersion()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC).
  - getCustomerPaymentTerms
```
@Nullable
public String getCustomerPaymentTerms()
```
    Constraints: Not nullable, Maximum length: 4
    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
    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.
  - getBillingDocumentDate
```
@Nullable
public Calendar getBillingDocumentDate()
```
    Constraints: Not nullable, Precision: 0
    When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
    
    Returns:
    
    Date on which billing is processed and posted to Accounting.
  - getServicesRenderedDate
```
@Nullable
public Calendar getServicesRenderedDate()
```
    Constraints: Not nullable, Precision: 0
    If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field. If you provide a service, however, and you are billing hours, you can enter a date manually. You can use the date of services rendered as one of the selection criteria when you process billing documents collectively.
    
    Returns:
    
    The date of services rendered that determines when the system calculates taxes (for example, sales tax) for the material.
  - getOverallSDProcessStatus
```
@Nullable
public String getOverallSDProcessStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
    
    Returns:
    
    The processing status of the entire sales document.
  - getTotalCreditCheckStatus
```
@Nullable
public String getTotalCreditCheckStatus()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Overall Status of Credit Checks
  - getOverallSDDocumentRejectionSts
```
@Nullable
public String getOverallSDDocumentRejectionSts()
```
    Constraints: Not nullable, Maximum length: 1
    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.
  - getOverallOrdReltdBillgStatus
```
@Nullable
public String getOverallOrdReltdBillgStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The overall billing status tells you whether the sales order or delivery is relevant for billing, and, if so, to what extent billing has taken place.
    
    Returns:
    
    The overall billing status of the sales order or delivery.
  - getErpConfigContext
```
@Nullable
public ErpConfigContext getErpConfigContext()
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Returns:
    
    The stored ERP system context for executing queries, or null if no such context has been set.
  - setDebitMemoRequest
```
public void setDebitMemoRequest(@Nullable
                                String debitMemoRequest)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    debitMemoRequest -
  - setDebitMemoRequestType
```
public void setDebitMemoRequestType(@Nullable
                                    String debitMemoRequestType)
```
    Constraints: Not nullable, Maximum length: 4
    The sales document type determines how the system processes the sales document. For example, depending on the sales document type, the system determines which screens to present and which data to ask you for.
    
    Parameters:
    
    debitMemoRequestType -
  - setSalesOrganization
```
public void setSalesOrganization(@Nullable
                                 String salesOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    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 -
  - setDistributionChannel
```
public void setDistributionChannel(@Nullable
                                   String distributionChannel)
```
    Constraints: Not nullable, Maximum length: 2
    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 -
  - setOrganizationDivision
```
public void setOrganizationDivision(@Nullable
                                    String organizationDivision)
```
    Constraints: Not nullable, Maximum length: 2
    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 -
  - setSalesGroup
```
public void setSalesGroup(@Nullable
                          String salesGroup)
```
    Constraints: Not nullable, Maximum length: 3
    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 -
  - setSalesOffice
```
public void setSalesOffice(@Nullable
                           String salesOffice)
```
    Constraints: Not nullable, Maximum length: 4
    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 -
  - setSalesDistrict
```
public void setSalesDistrict(@Nullable
                             String salesDistrict)
```
    Constraints: Not nullable, Maximum length: 6
    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 -
  - setSoldToParty
```
public void setSoldToParty(@Nullable
                           String soldToParty)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    soldToParty -
  - setCreationDate
```
public void setCreationDate(@Nullable
                            Calendar creationDate)
```
    Constraints: Not nullable, Precision: 0
    
    Parameters:
    
    creationDate -
  - setCreatedByUser
```
public void setCreatedByUser(@Nullable
                             String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    
    Parameters:
    
    createdByUser -
  - setLastChangeDate
```
public void setLastChangeDate(@Nullable
                              Calendar lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    
    Parameters:
    
    lastChangeDate -
  - setLastChangeDateTime
```
public void setLastChangeDateTime(@Nullable
                                  Calendar lastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    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 -
  - setPurchaseOrderByCustomer
```
public void setPurchaseOrderByCustomer(@Nullable
                                       String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    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 -
  - setCustomerPurchaseOrderType
```
public void setCustomerPurchaseOrderType(@Nullable
                                         String customerPurchaseOrderType)
```
    Constraints: Not nullable, Maximum length: 4
    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 -
  - setCustomerPurchaseOrderDate
```
public void setCustomerPurchaseOrderDate(@Nullable
                                         Calendar customerPurchaseOrderDate)
```
    Constraints: Not nullable, Precision: 0
    
    Parameters:
    
    customerPurchaseOrderDate -
  - setDebitMemoRequestDate
```
public void setDebitMemoRequestDate(@Nullable
                                    Calendar debitMemoRequestDate)
```
    Constraints: Not nullable, Precision: 0
    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:
    
    debitMemoRequestDate -
  - setTotalNetAmount
```
public void setTotalNetAmount(@Nullable
                              BigDecimal totalNetAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    Parameters:
    
    totalNetAmount -
  - setTransactionCurrency
```
public void setTransactionCurrency(@Nullable
                                   String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    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 -
  - setSDDocumentReason
```
public void setSDDocumentReason(@Nullable
                                String sDDocumentReason)
```
    Constraints: Not nullable, Maximum length: 3
    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 -
  - setPricingDate
```
public void setPricingDate(@Nullable
                           Calendar pricingDate)
```
    Constraints: Not nullable, Precision: 0
    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 -
  - setHeaderBillingBlockReason
```
public void setHeaderBillingBlockReason(@Nullable
                                        String headerBillingBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    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 -
  - setIncotermsClassification
```
public void setIncotermsClassification(@Nullable
                                       String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    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 -
  - setIncotermsTransferLocation
```
public void setIncotermsTransferLocation(@Nullable
                                         String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    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 -
  - setIncotermsLocation1
```
public void setIncotermsLocation1(@Nullable
                                  String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    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 -
  - setIncotermsLocation2
```
public void setIncotermsLocation2(@Nullable
                                  String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    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 -
  - setIncotermsVersion
```
public void setIncotermsVersion(@Nullable
                                String incotermsVersion)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    incotermsVersion -
  - setCustomerPaymentTerms
```
public void setCustomerPaymentTerms(@Nullable
                                    String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    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 -
  - setPaymentMethod
```
public void setPaymentMethod(@Nullable
                             String paymentMethod)
```
    Constraints: Not nullable, Maximum length: 1
    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 -
  - setBillingDocumentDate
```
public void setBillingDocumentDate(@Nullable
                                   Calendar billingDocumentDate)
```
    Constraints: Not nullable, Precision: 0
    When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
    
    Parameters:
    
    billingDocumentDate -
  - setServicesRenderedDate
```
public void setServicesRenderedDate(@Nullable
                                    Calendar servicesRenderedDate)
```
    Constraints: Not nullable, Precision: 0
    If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field. If you provide a service, however, and you are billing hours, you can enter a date manually. You can use the date of services rendered as one of the selection criteria when you process billing documents collectively.
    
    Parameters:
    
    servicesRenderedDate -
  - setOverallSDProcessStatus
```
public void setOverallSDProcessStatus(@Nullable
                                      String overallSDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    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 -
  - setTotalCreditCheckStatus
```
public void setTotalCreditCheckStatus(@Nullable
                                      String totalCreditCheckStatus)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    totalCreditCheckStatus -
  - setOverallSDDocumentRejectionSts
```
public void setOverallSDDocumentRejectionSts(@Nullable
                                             String overallSDDocumentRejectionSts)
```
    Constraints: Not nullable, Maximum length: 1
    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 -
  - setOverallOrdReltdBillgStatus
```
public void setOverallOrdReltdBillgStatus(@Nullable
                                          String overallOrdReltdBillgStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The overall billing status tells you whether the sales order or delivery is relevant for billing, and, if so, to what extent billing has taken place.
    
    Parameters:
    
    overallOrdReltdBillgStatus -
  - setErpConfigContext
```
public void setErpConfigContext(@Nullable
                                ErpConfigContext erpConfigContext)
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Parameters:
    
    erpConfigContext -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<DebitMemoRequest>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<DebitMemoRequest>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<DebitMemoRequest>

Class DebitMemoRequest

Nested Class Summary

Field Summary

Constructor Summary

Method Summary

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

DEBIT_MEMO_REQUEST

DEBIT_MEMO_REQUEST_TYPE

SALES_ORGANIZATION

DISTRIBUTION_CHANNEL

ORGANIZATION_DIVISION

SALES_GROUP

SALES_OFFICE

SALES_DISTRICT

SOLD_TO_PARTY

CREATION_DATE

CREATED_BY_USER

LAST_CHANGE_DATE

LAST_CHANGE_DATE_TIME

PURCHASE_ORDER_BY_CUSTOMER

CUSTOMER_PURCHASE_ORDER_TYPE

CUSTOMER_PURCHASE_ORDER_DATE

DEBIT_MEMO_REQUEST_DATE

TOTAL_NET_AMOUNT

TRANSACTION_CURRENCY

SD_DOCUMENT_REASON

PRICING_DATE

HEADER_BILLING_BLOCK_REASON

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

INCOTERMS_VERSION

CUSTOMER_PAYMENT_TERMS

PAYMENT_METHOD

BILLING_DOCUMENT_DATE

SERVICES_RENDERED_DATE

OVERALL_SD_PROCESS_STATUS

TOTAL_CREDIT_CHECK_STATUS

OVERALL_SD_DOCUMENT_REJECTION_STS

OVERALL_ORD_RELTD_BILLG_STATUS

TO_ITEM

TO_PARTNER

TO_PRICING_ELEMENT

Constructor Detail

DebitMemoRequest

DebitMemoRequest

Method Detail

getType

field

fetchItem

getItemOrFetch

getItemOrNull

setItem

addItem

fetchPartner

getPartnerOrFetch

getPartnerOrNull

setPartner

addPartner

fetchPricingElement

getPricingElementOrFetch

getPricingElementOrNull

setPricingElement

addPricingElement

builder

getDebitMemoRequest

getDebitMemoRequestType

getSalesOrganization

getDistributionChannel

getOrganizationDivision

getSalesGroup

getSalesOffice

getSalesDistrict

getSoldToParty

getCreationDate

getCreatedByUser