DebitMemoRequest.DebitMemoRequestBuilder (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.debitmemorequest.DebitMemoRequest.DebitMemoRequestBuilder

Enclosing class:

DebitMemoRequest
```
public static final class DebitMemoRequest.DebitMemoRequestBuilder
extends Object
```
Helper class to allow for fluent creation of DebitMemoRequest instances.

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`DebitMemoRequest.DebitMemoRequestBuilder`	`billingDocumentDate(LocalDateTime billingDocumentDate)` Constraints: Not nullable, Precision: 0
`DebitMemoRequest`	`build()`
`DebitMemoRequest.DebitMemoRequestBuilder`	`createdByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`DebitMemoRequest.DebitMemoRequestBuilder`	`creationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)` Constraints: Not nullable, Precision: 0
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerPurchaseOrderType(String customerPurchaseOrderType)` Constraints: Not nullable, Maximum length: 4
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification1(String customerTaxClassification1)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification2(String customerTaxClassification2)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification3(String customerTaxClassification3)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification4(String customerTaxClassification4)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification5(String customerTaxClassification5)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification6(String customerTaxClassification6)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification7(String customerTaxClassification7)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification8(String customerTaxClassification8)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`customerTaxClassification9(String customerTaxClassification9)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`debitMemoRequest(String debitMemoRequest)` (Key Field) Constraints: Not nullable, Maximum length: 10
`DebitMemoRequest.DebitMemoRequestBuilder`	`debitMemoRequestDate(LocalDateTime debitMemoRequestDate)` Constraints: Not nullable, Precision: 0
`DebitMemoRequest.DebitMemoRequestBuilder`	`debitMemoRequestType(String debitMemoRequestType)` Constraints: Not nullable, Maximum length: 4
`DebitMemoRequest.DebitMemoRequestBuilder`	`distributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2
`DebitMemoRequest.DebitMemoRequestBuilder`	`headerBillingBlockReason(String headerBillingBlockReason)` Constraints: Not nullable, Maximum length: 2
`DebitMemoRequest.DebitMemoRequestBuilder`	`incotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3
`DebitMemoRequest.DebitMemoRequestBuilder`	`incotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70
`DebitMemoRequest.DebitMemoRequestBuilder`	`incotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70
`DebitMemoRequest.DebitMemoRequestBuilder`	`incotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28
`DebitMemoRequest.DebitMemoRequestBuilder`	`incotermsVersion(String incotermsVersion)` Constraints: Not nullable, Maximum length: 4
`DebitMemoRequest.DebitMemoRequestBuilder`	`item(DebitMemoRequestItem... value)` Navigation property to_Item for DebitMemoRequest to multiple DebitMemoRequestItem.
`DebitMemoRequest.DebitMemoRequestBuilder`	`lastChangeDate(LocalDateTime lastChangeDate)` Constraints: Not nullable, Precision: 0
`DebitMemoRequest.DebitMemoRequestBuilder`	`lastChangeDateTime(ZonedDateTime lastChangeDateTime)` Constraints: Not nullable, Precision: 7
`DebitMemoRequest.DebitMemoRequestBuilder`	`organizationDivision(String organizationDivision)` Constraints: Not nullable, Maximum length: 2
`DebitMemoRequest.DebitMemoRequestBuilder`	`overallOrdReltdBillgStatus(String overallOrdReltdBillgStatus)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`overallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`overallSDProcessStatus(String overallSDProcessStatus)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`partner(DebitMemoReqPartner... value)` Navigation property to_Partner for DebitMemoRequest to multiple DebitMemoReqPartner.
`DebitMemoRequest.DebitMemoRequestBuilder`	`paymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`pricingDate(LocalDateTime pricingDate)` Constraints: Not nullable, Precision: 0
`DebitMemoRequest.DebitMemoRequestBuilder`	`pricingElement(DebitMemoReqPrcgElmnt... value)` Navigation property to_PricingElement for DebitMemoRequest to multiple DebitMemoReqPrcgElmnt.
`DebitMemoRequest.DebitMemoRequestBuilder`	`purchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`DebitMemoRequest.DebitMemoRequestBuilder`	`referenceSDDocument(String referenceSDDocument)` Constraints: Not nullable, Maximum length: 10
`DebitMemoRequest.DebitMemoRequestBuilder`	`referenceSDDocumentCategory(String referenceSDDocumentCategory)` Constraints: Not nullable, Maximum length: 4
`DebitMemoRequest.DebitMemoRequestBuilder`	`salesDistrict(String salesDistrict)` Constraints: Not nullable, Maximum length: 6
`DebitMemoRequest.DebitMemoRequestBuilder`	`salesGroup(String salesGroup)` Constraints: Not nullable, Maximum length: 3
`DebitMemoRequest.DebitMemoRequestBuilder`	`salesOffice(String salesOffice)` Constraints: Not nullable, Maximum length: 4
`DebitMemoRequest.DebitMemoRequestBuilder`	`salesOrganization(String salesOrganization)` Constraints: Not nullable, Maximum length: 4
`DebitMemoRequest.DebitMemoRequestBuilder`	`sDDocumentReason(String sDDocumentReason)` Constraints: Not nullable, Maximum length: 3
`DebitMemoRequest.DebitMemoRequestBuilder`	`servicesRenderedDate(LocalDateTime servicesRenderedDate)` Constraints: Not nullable, Precision: 0
`DebitMemoRequest.DebitMemoRequestBuilder`	`soldToParty(String soldToParty)` Constraints: Not nullable, Maximum length: 10
`DebitMemoRequest.DebitMemoRequestBuilder`	`text(DebitMemoReqText... value)` Navigation property to_Text for DebitMemoRequest to multiple DebitMemoReqText.
`String`	`toString()`
`DebitMemoRequest.DebitMemoRequestBuilder`	`totalCreditCheckStatus(String totalCreditCheckStatus)` Constraints: Not nullable, Maximum length: 1
`DebitMemoRequest.DebitMemoRequestBuilder`	`totalNetAmount(BigDecimal totalNetAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`DebitMemoRequest.DebitMemoRequestBuilder`	`transactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5

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

- Method Detail
  - item
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder item(DebitMemoRequestItem... value)
```
    Navigation property to_Item for DebitMemoRequest to multiple DebitMemoRequestItem.
    
    Parameters:
    
    value - The DebitMemoRequestItems to build this DebitMemoRequest with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - partner
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder partner(DebitMemoReqPartner... value)
```
    Navigation property to_Partner for DebitMemoRequest to multiple DebitMemoReqPartner.
    
    Parameters:
    
    value - The DebitMemoReqPartners to build this DebitMemoRequest with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - pricingElement
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder pricingElement(DebitMemoReqPrcgElmnt... value)
```
    Navigation property to_PricingElement for DebitMemoRequest to multiple DebitMemoReqPrcgElmnt.
    
    Parameters:
    
    value - The DebitMemoReqPrcgElmnts to build this DebitMemoRequest with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - text
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder text(DebitMemoReqText... value)
```
    Navigation property to_Text for DebitMemoRequest to multiple DebitMemoReqText.
    
    Parameters:
    
    value - The DebitMemoReqTexts to build this DebitMemoRequest with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - debitMemoRequest
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder debitMemoRequest(@Nullable
                                                                          String debitMemoRequest)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: DebitMemoRequest
    
    Returns:
    
    this.
  - debitMemoRequestType
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder debitMemoRequestType(@Nullable
                                                                              String debitMemoRequestType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: DebitMemoRequestType
    
    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:
    
    this.
  - salesOrganization
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder salesOrganization(@Nullable
                                                                           String salesOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrganization
    
    You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
    
    Returns:
    
    this.
  - distributionChannel
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder distributionChannel(@Nullable
                                                                             String distributionChannel)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DistributionChannel
    
    You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
    
    Returns:
    
    this.
  - organizationDivision
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder organizationDivision(@Nullable
                                                                              String organizationDivision)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: OrganizationDivision
    
    A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
    
    Returns:
    
    this.
  - salesGroup
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder salesGroup(@Nullable
                                                                    String salesGroup)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SalesGroup
    
    By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
    
    Returns:
    
    this.
  - salesOffice
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder salesOffice(@Nullable
                                                                     String salesOffice)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOffice
    
    When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
    
    Returns:
    
    this.
  - salesDistrict
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder salesDistrict(@Nullable
                                                                       String salesDistrict)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesDistrict
    
    Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
    
    Returns:
    
    this.
  - soldToParty
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder soldToParty(@Nullable
                                                                     String soldToParty)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SoldToParty
    
    Returns:
    
    this.
  - creationDate
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder creationDate(@Nullable
                                                                      LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    this.
  - createdByUser
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder createdByUser(@Nullable
                                                                       String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Returns:
    
    this.
  - lastChangeDate
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder lastChangeDate(@Nullable
                                                                        LocalDateTime lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Returns:
    
    this.
  - lastChangeDateTime
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder lastChangeDateTime(@Nullable
                                                                            ZonedDateTime lastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Returns:
    
    this.
  - purchaseOrderByCustomer
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder purchaseOrderByCustomer(@Nullable
                                                                                 String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    
    Returns:
    
    this.
  - customerPurchaseOrderType
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerPurchaseOrderType(@Nullable
                                                                                   String customerPurchaseOrderType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPurchaseOrderType
    
    You can record here whether the sales document arrived, for example, by telephone, mail, or fax.Enter one of the values predefined for your system.
    
    Returns:
    
    this.
  - customerPurchaseOrderDate
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerPurchaseOrderDate(@Nullable
                                                                                   LocalDateTime customerPurchaseOrderDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CustomerPurchaseOrderDate
    
    Returns:
    
    this.
  - debitMemoRequestDate
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder debitMemoRequestDate(@Nullable
                                                                              LocalDateTime debitMemoRequestDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: DebitMemoRequestDate
    
    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:
    
    this.
  - totalNetAmount
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder totalNetAmount(@Nullable
                                                                        BigDecimal totalNetAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: TotalNetAmount
    
    Returns:
    
    this.
  - transactionCurrency
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder transactionCurrency(@Nullable
                                                                             String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: TransactionCurrency
    
    The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
    
    Returns:
    
    this.
  - sDDocumentReason
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder sDDocumentReason(@Nullable
                                                                          String sDDocumentReason)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SDDocumentReason
    
    You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria.Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason.If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
    
    Returns:
    
    this.
  - pricingDate
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder pricingDate(@Nullable
                                                                     LocalDateTime pricingDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PricingDate
    
    You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
    
    Returns:
    
    this.
  - customerTaxClassification1
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification1(@Nullable
                                                                                    String customerTaxClassification1)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification1
    
    The system copies the tax classification from the tax information stored in the customer master record of the goods recipient. During pricing, the system uses the tax classification and the country key (which identifies the customer location) to determine the relevant taxes. You can enter a different (alternative) tax classification in the order.
    
    Returns:
    
    this.
  - customerTaxClassification2
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification2(@Nullable
                                                                                    String customerTaxClassification2)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification2
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    this.
  - customerTaxClassification3
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification3(@Nullable
                                                                                    String customerTaxClassification3)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification3
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    this.
  - customerTaxClassification4
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification4(@Nullable
                                                                                    String customerTaxClassification4)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification4
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    this.
  - customerTaxClassification5
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification5(@Nullable
                                                                                    String customerTaxClassification5)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification5
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    this.
  - customerTaxClassification6
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification6(@Nullable
                                                                                    String customerTaxClassification6)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification6
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    this.
  - customerTaxClassification7
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification7(@Nullable
                                                                                    String customerTaxClassification7)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification7
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    this.
  - customerTaxClassification8
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification8(@Nullable
                                                                                    String customerTaxClassification8)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification8
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    this.
  - customerTaxClassification9
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerTaxClassification9(@Nullable
                                                                                    String customerTaxClassification9)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification9
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    this.
  - headerBillingBlockReason
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder headerBillingBlockReason(@Nullable
                                                                                  String headerBillingBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: HeaderBillingBlockReason
    
    The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
    
    Returns:
    
    this.
  - incotermsClassification
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder incotermsClassification(@Nullable
                                                                                 String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Returns:
    
    this.
  - incotermsTransferLocation
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder incotermsTransferLocation(@Nullable
                                                                                   String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Returns:
    
    this.
  - incotermsLocation1
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder incotermsLocation1(@Nullable
                                                                            String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    
    1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Returns:
    
    this.
  - incotermsLocation2
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder incotermsLocation2(@Nullable
                                                                            String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Returns:
    
    this.
  - incotermsVersion
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder incotermsVersion(@Nullable
                                                                          String incotermsVersion)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: IncotermsVersion
    
    Returns:
    
    this.
  - customerPaymentTerms
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder customerPaymentTerms(@Nullable
                                                                              String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Returns:
    
    this.
  - paymentMethod
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder paymentMethod(@Nullable
                                                                       String paymentMethod)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentMethod
    
    If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
    
    Returns:
    
    this.
  - billingDocumentDate
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder billingDocumentDate(@Nullable
                                                                             LocalDateTime billingDocumentDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BillingDocumentDate
    
    You can use the billing date as one of the selection criteria when you process billing documents collectively.If invoice dates are defined for the customer, 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.If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document.If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone.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:
    
    this.
  - servicesRenderedDate
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder servicesRenderedDate(@Nullable
                                                                              LocalDateTime servicesRenderedDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ServicesRenderedDate
    
    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:
    
    this.
  - referenceSDDocument
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder referenceSDDocument(@Nullable
                                                                             String referenceSDDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceSDDocument
    
    Returns:
    
    this.
  - referenceSDDocumentCategory
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder referenceSDDocumentCategory(@Nullable
                                                                                     String referenceSDDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ReferenceSDDocumentCategory
    
    Returns:
    
    this.
  - overallSDProcessStatus
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder overallSDProcessStatus(@Nullable
                                                                                String overallSDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDProcessStatus
    
    The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
    
    Returns:
    
    this.
  - totalCreditCheckStatus
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder totalCreditCheckStatus(@Nullable
                                                                                String totalCreditCheckStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: TotalCreditCheckStatus
    
    Returns:
    
    this.
  - overallSDDocumentRejectionSts
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder overallSDDocumentRejectionSts(@Nullable
                                                                                       String overallSDDocumentRejectionSts)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDDocumentRejectionSts
    
    The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.
    
    Returns:
    
    this.
  - overallOrdReltdBillgStatus
```
@Nonnull
public DebitMemoRequest.DebitMemoRequestBuilder overallOrdReltdBillgStatus(@Nullable
                                                                                    String overallOrdReltdBillgStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallOrdReltdBillgStatus
    
    The overall billing status tells you whether the sales order or delivery is relevant for billing, and, if so, to what extent billing has taken place.
    
    Returns:
    
    this.
  - build
```
@Nonnull
public DebitMemoRequest build()
```
  - toString
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class Object

Class DebitMemoRequest.DebitMemoRequestBuilder

Method Summary

Methods inherited from class java.lang.Object

Method Detail

item

partner

pricingElement

text

debitMemoRequest

debitMemoRequestType

salesOrganization

distributionChannel

organizationDivision

salesGroup

salesOffice

salesDistrict

soldToParty

creationDate

createdByUser

lastChangeDate

lastChangeDateTime

purchaseOrderByCustomer

customerPurchaseOrderType

customerPurchaseOrderDate

debitMemoRequestDate

totalNetAmount

transactionCurrency

sDDocumentReason

pricingDate

customerTaxClassification1

customerTaxClassification2

customerTaxClassification3

customerTaxClassification4

customerTaxClassification5

customerTaxClassification6

customerTaxClassification7

customerTaxClassification8

customerTaxClassification9

headerBillingBlockReason

incotermsClassification

incotermsTransferLocation

incotermsLocation1

incotermsLocation2

incotermsVersion

customerPaymentTerms

paymentMethod

billingDocumentDate

servicesRenderedDate

referenceSDDocument

referenceSDDocumentCategory

overallSDProcessStatus

totalCreditCheckStatus

overallSDDocumentRejectionSts

overallOrdReltdBillgStatus

build

toString