DebitMemoRequestItem (SAP S/4HANA Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.helper.Entity<DebitMemoRequestItem>
- - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.processdebitmemorequests.DebitMemoRequestItem

public class DebitMemoRequestItem
extends Entity<DebitMemoRequestItem>

Debit Memo Request Item (API)

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class DebitMemoRequestItem.DebitMemoRequestItemBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`DebitMemoRequestItem.DebitMemoRequestItemBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static EntityField<DebitMemoRequestItem,String>`	`BATCH` Use with available fluent helpers to apply the Batch field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`DEBIT_MEMO_REQUEST` Use with available fluent helpers to apply the DebitMemoRequest field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`DEBIT_MEMO_REQUEST_ITEM` Use with available fluent helpers to apply the DebitMemoRequestItem field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`DEBIT_MEMO_REQUEST_ITEM_CATEGORY` Use with available fluent helpers to apply the DebitMemoRequestItemCategory field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`DEBIT_MEMO_REQUEST_ITEM_TEXT` Use with available fluent helpers to apply the DebitMemoRequestItemText field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`HIGHER_LEVEL_ITEM` Use with available fluent helpers to apply the HigherLevelItem field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`ITEM_BILLING_BLOCK_REASON` Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
`static EntityField<DebitMemoRequestItem,BigDecimal>`	`ITEM_GROSS_WEIGHT` Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
`static EntityField<DebitMemoRequestItem,BigDecimal>`	`ITEM_NET_WEIGHT` Use with available fluent helpers to apply the ItemNetWeight field to query operations.
`static EntityField<DebitMemoRequestItem,BigDecimal>`	`ITEM_VOLUME` Use with available fluent helpers to apply the ItemVolume field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`ITEM_VOLUME_UNIT` Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`ITEM_WEIGHT_UNIT` Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`MATERIAL` Use with available fluent helpers to apply the Material field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`MATERIAL_BY_CUSTOMER` Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`MATERIAL_GROUP` Use with available fluent helpers to apply the MaterialGroup field to query operations.
`static EntityField<DebitMemoRequestItem,BigDecimal>`	`NET_AMOUNT` Use with available fluent helpers to apply the NetAmount field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`ORDER_RELATED_BILLING_STATUS` Use with available fluent helpers to apply the OrderRelatedBillingStatus field to query operations.
`static EntityField<DebitMemoRequestItem,Calendar>`	`PRICING_DATE` Use with available fluent helpers to apply the PricingDate field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static EntityField<DebitMemoRequestItem,BigDecimal>`	`REQUESTED_QUANTITY` Use with available fluent helpers to apply the RequestedQuantity field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`REQUESTED_QUANTITY_UNIT` Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`S_D_PROCESS_STATUS` Use with available fluent helpers to apply the SDProcessStatus field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`SALES_DOCUMENT_RJCN_REASON` Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
`static EntityField<DebitMemoRequestItem,String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.

Constructor Summary

Constructors
Constructor and Description
`DebitMemoRequestItem()`
DebitMemoRequestItem(String debitMemoRequest, String debitMemoRequestItem, String higherLevelItem, String debitMemoRequestItemCategory, String debitMemoRequestItemText, String purchaseOrderByCustomer, String material, String materialByCustomer, Calendar pricingDate, BigDecimal requestedQuantity, String requestedQuantityUnit, BigDecimal itemGrossWeight, BigDecimal itemNetWeight, String itemWeightUnit, BigDecimal itemVolume, String itemVolumeUnit, String transactionCurrency, BigDecimal netAmount, String materialGroup, String batch, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String customerPaymentTerms, String itemBillingBlockReason, String salesDocumentRjcnReason, String sDProcessStatus, String orderRelatedBillingStatus, ErpConfigContext erpConfigContext)

Method Summary

Methods
Modifier and Type	Method and Description
`static DebitMemoRequestItem.DebitMemoRequestItemBuilder`	`builder()`
`boolean`	`equals(Object o)`
`DebitMemoRequest`	`fetchDebitMemoRequest()` Fetches the DebitMemoRequest entity (one to one) associated with this entity.
`List<DebitMemoReqItemPartner>`	`fetchPartner()` Fetches the DebitMemoReqItemPartner entities (one to many) associated with this entity.
`List<DebitMemoReqItemPrcgElmnt>`	`fetchPricingElement()` Fetches the DebitMemoReqItemPrcgElmnt entities (one to many) associated with this entity.
`static <T> EntityField<DebitMemoRequestItem,T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`String`	`getBatch()` Constraints: Not nullable, Maximum length: 10
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4
`String`	`getDebitMemoRequest()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getDebitMemoRequestItem()` (Key Field) Constraints: Not nullable, Maximum length: 6
`String`	`getDebitMemoRequestItemCategory()` Constraints: Not nullable, Maximum length: 4
`String`	`getDebitMemoRequestItemText()` Constraints: Not nullable, Maximum length: 40
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g.
`String`	`getHigherLevelItem()` Constraints: Not nullable, Maximum length: 6
`String`	`getIncotermsClassification()` Constraints: Not nullable, Maximum length: 3
`String`	`getIncotermsLocation1()` Constraints: Not nullable, Maximum length: 70
`String`	`getIncotermsLocation2()` Constraints: Not nullable, Maximum length: 70
`String`	`getIncotermsTransferLocation()` Constraints: Not nullable, Maximum length: 28
`String`	`getItemBillingBlockReason()` Constraints: Not nullable, Maximum length: 2
`BigDecimal`	`getItemGrossWeight()` Constraints: Not nullable, Precision: 15, Scale: 3
`BigDecimal`	`getItemNetWeight()` Constraints: Not nullable, Precision: 15, Scale: 3
`BigDecimal`	`getItemVolume()` Constraints: Not nullable, Precision: 15, Scale: 3
`String`	`getItemVolumeUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getItemWeightUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getMaterial()` Constraints: Not nullable, Maximum length: 40
`String`	`getMaterialByCustomer()` Constraints: Not nullable, Maximum length: 35
`String`	`getMaterialGroup()` Constraints: Not nullable, Maximum length: 9
`BigDecimal`	`getNetAmount()` Constraints: Not nullable, Precision: 16, Scale: 3
`String`	`getOrderRelatedBillingStatus()` Constraints: Not nullable, Maximum length: 1
`Calendar`	`getPricingDate()` Constraints: Not nullable, Precision: 0
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35
`BigDecimal`	`getRequestedQuantity()` Constraints: Not nullable, Precision: 15, Scale: 3
`String`	`getRequestedQuantityUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getSalesDocumentRjcnReason()` Constraints: Not nullable, Maximum length: 2
`String`	`getSDProcessStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5
`Class<DebitMemoRequestItem>`	`getType()`
`int`	`hashCode()`
`void`	`setBatch(String batch)` Constraints: Not nullable, Maximum length: 10
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`void`	`setDebitMemoRequest(String debitMemoRequest)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setDebitMemoRequestItem(String debitMemoRequestItem)` (Key Field) Constraints: Not nullable, Maximum length: 6
`void`	`setDebitMemoRequestItemCategory(String debitMemoRequestItemCategory)` Constraints: Not nullable, Maximum length: 4
`void`	`setDebitMemoRequestItemText(String debitMemoRequestItemText)` Constraints: Not nullable, Maximum length: 40
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Convienence field for reusing the same ERP system context with multiple queries (e.g.
`void`	`setHigherLevelItem(String higherLevelItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setIncotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3
`void`	`setIncotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70
`void`	`setIncotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70
`void`	`setIncotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28
`void`	`setItemBillingBlockReason(String itemBillingBlockReason)` Constraints: Not nullable, Maximum length: 2
`void`	`setItemGrossWeight(BigDecimal itemGrossWeight)` Constraints: Not nullable, Precision: 15, Scale: 3
`void`	`setItemNetWeight(BigDecimal itemNetWeight)` Constraints: Not nullable, Precision: 15, Scale: 3
`void`	`setItemVolume(BigDecimal itemVolume)` Constraints: Not nullable, Precision: 15, Scale: 3
`void`	`setItemVolumeUnit(String itemVolumeUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setItemWeightUnit(String itemWeightUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setMaterial(String material)` Constraints: Not nullable, Maximum length: 40
`void`	`setMaterialByCustomer(String materialByCustomer)` Constraints: Not nullable, Maximum length: 35
`void`	`setMaterialGroup(String materialGroup)` Constraints: Not nullable, Maximum length: 9
`void`	`setNetAmount(BigDecimal netAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`void`	`setOrderRelatedBillingStatus(String orderRelatedBillingStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setPricingDate(Calendar pricingDate)` Constraints: Not nullable, Precision: 0
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`void`	`setRequestedQuantity(BigDecimal requestedQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3
`void`	`setRequestedQuantityUnit(String requestedQuantityUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setSalesDocumentRjcnReason(String salesDocumentRjcnReason)` Constraints: Not nullable, Maximum length: 2
`void`	`setSDProcessStatus(String sDProcessStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.Entity
getField, getField, getFieldNames, hasField, hasField

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

- Field Detail
  - DEBIT_MEMO_REQUEST
```
public static final EntityField<DebitMemoRequestItem,String> DEBIT_MEMO_REQUEST
```
    Use with available fluent helpers to apply the DebitMemoRequest field to query operations.
  - DEBIT_MEMO_REQUEST_ITEM
```
public static final EntityField<DebitMemoRequestItem,String> DEBIT_MEMO_REQUEST_ITEM
```
    Use with available fluent helpers to apply the DebitMemoRequestItem field to query operations.
  - HIGHER_LEVEL_ITEM
```
public static final EntityField<DebitMemoRequestItem,String> HIGHER_LEVEL_ITEM
```
    Use with available fluent helpers to apply the HigherLevelItem field to query operations.
  - DEBIT_MEMO_REQUEST_ITEM_CATEGORY
```
public static final EntityField<DebitMemoRequestItem,String> DEBIT_MEMO_REQUEST_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the DebitMemoRequestItemCategory field to query operations.
  - DEBIT_MEMO_REQUEST_ITEM_TEXT
```
public static final EntityField<DebitMemoRequestItem,String> DEBIT_MEMO_REQUEST_ITEM_TEXT
```
    Use with available fluent helpers to apply the DebitMemoRequestItemText field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final EntityField<DebitMemoRequestItem,String> PURCHASE_ORDER_BY_CUSTOMER
```
    Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
  - MATERIAL
```
public static final EntityField<DebitMemoRequestItem,String> MATERIAL
```
    Use with available fluent helpers to apply the Material field to query operations.
  - MATERIAL_BY_CUSTOMER
```
public static final EntityField<DebitMemoRequestItem,String> MATERIAL_BY_CUSTOMER
```
    Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
  - PRICING_DATE
```
public static final EntityField<DebitMemoRequestItem,Calendar> PRICING_DATE
```
    Use with available fluent helpers to apply the PricingDate field to query operations.
  - REQUESTED_QUANTITY
```
public static final EntityField<DebitMemoRequestItem,BigDecimal> REQUESTED_QUANTITY
```
    Use with available fluent helpers to apply the RequestedQuantity field to query operations.
  - REQUESTED_QUANTITY_UNIT
```
public static final EntityField<DebitMemoRequestItem,String> REQUESTED_QUANTITY_UNIT
```
    Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
  - ITEM_GROSS_WEIGHT
```
public static final EntityField<DebitMemoRequestItem,BigDecimal> ITEM_GROSS_WEIGHT
```
    Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
  - ITEM_NET_WEIGHT
```
public static final EntityField<DebitMemoRequestItem,BigDecimal> ITEM_NET_WEIGHT
```
    Use with available fluent helpers to apply the ItemNetWeight field to query operations.
  - ITEM_WEIGHT_UNIT
```
public static final EntityField<DebitMemoRequestItem,String> ITEM_WEIGHT_UNIT
```
    Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
  - ITEM_VOLUME
```
public static final EntityField<DebitMemoRequestItem,BigDecimal> ITEM_VOLUME
```
    Use with available fluent helpers to apply the ItemVolume field to query operations.
  - ITEM_VOLUME_UNIT
```
public static final EntityField<DebitMemoRequestItem,String> ITEM_VOLUME_UNIT
```
    Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
  - TRANSACTION_CURRENCY
```
public static final EntityField<DebitMemoRequestItem,String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - NET_AMOUNT
```
public static final EntityField<DebitMemoRequestItem,BigDecimal> NET_AMOUNT
```
    Use with available fluent helpers to apply the NetAmount field to query operations.
  - MATERIAL_GROUP
```
public static final EntityField<DebitMemoRequestItem,String> MATERIAL_GROUP
```
    Use with available fluent helpers to apply the MaterialGroup field to query operations.
  - BATCH
```
public static final EntityField<DebitMemoRequestItem,String> BATCH
```
    Use with available fluent helpers to apply the Batch field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final EntityField<DebitMemoRequestItem,String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final EntityField<DebitMemoRequestItem,String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final EntityField<DebitMemoRequestItem,String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final EntityField<DebitMemoRequestItem,String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final EntityField<DebitMemoRequestItem,String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - ITEM_BILLING_BLOCK_REASON
```
public static final EntityField<DebitMemoRequestItem,String> ITEM_BILLING_BLOCK_REASON
```
    Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
  - SALES_DOCUMENT_RJCN_REASON
```
public static final EntityField<DebitMemoRequestItem,String> SALES_DOCUMENT_RJCN_REASON
```
    Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
  - S_D_PROCESS_STATUS
```
public static final EntityField<DebitMemoRequestItem,String> S_D_PROCESS_STATUS
```
    Use with available fluent helpers to apply the SDProcessStatus field to query operations.
  - ORDER_RELATED_BILLING_STATUS
```
public static final EntityField<DebitMemoRequestItem,String> ORDER_RELATED_BILLING_STATUS
```
    Use with available fluent helpers to apply the OrderRelatedBillingStatus field to query operations.
- Constructor Detail
  - DebitMemoRequestItem
```
@Generated(value="lombok")
public DebitMemoRequestItem()
```
  - DebitMemoRequestItem
```
@ConstructorProperties(value={"debitMemoRequest","debitMemoRequestItem","higherLevelItem","debitMemoRequestItemCategory","debitMemoRequestItemText","purchaseOrderByCustomer","material","materialByCustomer","pricingDate","requestedQuantity","requestedQuantityUnit","itemGrossWeight","itemNetWeight","itemWeightUnit","itemVolume","itemVolumeUnit","transactionCurrency","netAmount","materialGroup","batch","incotermsClassification","incotermsTransferLocation","incotermsLocation1","incotermsLocation2","customerPaymentTerms","itemBillingBlockReason","salesDocumentRjcnReason","sDProcessStatus","orderRelatedBillingStatus","erpConfigContext"})
@Generated(value="lombok")
public DebitMemoRequestItem(@Nullable
                                                              String debitMemoRequest,
                                                              @Nullable
                                                              String debitMemoRequestItem,
                                                              @Nullable
                                                              String higherLevelItem,
                                                              @Nullable
                                                              String debitMemoRequestItemCategory,
                                                              @Nullable
                                                              String debitMemoRequestItemText,
                                                              @Nullable
                                                              String purchaseOrderByCustomer,
                                                              @Nullable
                                                              String material,
                                                              @Nullable
                                                              String materialByCustomer,
                                                              @Nullable
                                                              Calendar pricingDate,
                                                              @Nullable
                                                              BigDecimal requestedQuantity,
                                                              @Nullable
                                                              String requestedQuantityUnit,
                                                              @Nullable
                                                              BigDecimal itemGrossWeight,
                                                              @Nullable
                                                              BigDecimal itemNetWeight,
                                                              @Nullable
                                                              String itemWeightUnit,
                                                              @Nullable
                                                              BigDecimal itemVolume,
                                                              @Nullable
                                                              String itemVolumeUnit,
                                                              @Nullable
                                                              String transactionCurrency,
                                                              @Nullable
                                                              BigDecimal netAmount,
                                                              @Nullable
                                                              String materialGroup,
                                                              @Nullable
                                                              String batch,
                                                              @Nullable
                                                              String incotermsClassification,
                                                              @Nullable
                                                              String incotermsTransferLocation,
                                                              @Nullable
                                                              String incotermsLocation1,
                                                              @Nullable
                                                              String incotermsLocation2,
                                                              @Nullable
                                                              String customerPaymentTerms,
                                                              @Nullable
                                                              String itemBillingBlockReason,
                                                              @Nullable
                                                              String salesDocumentRjcnReason,
                                                              @Nullable
                                                              String sDProcessStatus,
                                                              @Nullable
                                                              String orderRelatedBillingStatus,
                                                              ErpConfigContext erpConfigContext)
```
- Method Detail
  - getType
```
public Class<DebitMemoRequestItem> getType()
```
    Specified by:
    
    getType in class Entity<DebitMemoRequestItem>
    
    Returns:
    The class of this entity.
  - field
```
public static <T> EntityField<DebitMemoRequestItem,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.
  - fetchDebitMemoRequest
```
public DebitMemoRequest fetchDebitMemoRequest()
                                       throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the DebitMemoRequest entity (one to one) associated with this entity. This corresponds to the OData navigation property to_DebitMemoRequest.
    
    Returns:
    The single associated DebitMemoRequest entity, or null if an entity is not associated.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException
  - fetchPartner
```
public List<DebitMemoReqItemPartner> fetchPartner()
                                           throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the DebitMemoReqItemPartner entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Partner.
    
    Returns:
    List containing one or more associated DebitMemoReqItemPartner entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException
  - fetchPricingElement
```
public List<DebitMemoReqItemPrcgElmnt> fetchPricingElement()
                                                    throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the DebitMemoReqItemPrcgElmnt entities (one to many) associated with this entity. This corresponds to the OData navigation property to_PricingElement.
    
    Returns:
    List containing one or more associated DebitMemoReqItemPrcgElmnt entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException
  - builder
```
@Generated(value="lombok")
public static DebitMemoRequestItem.DebitMemoRequestItemBuilder builder()
```
  - getDebitMemoRequest
```
@Nullable
@Generated(value="lombok")
public String getDebitMemoRequest()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Returns:
    Debit Memo Request
  - getDebitMemoRequestItem
```
@Nullable
@Generated(value="lombok")
public String getDebitMemoRequestItem()
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    
    Returns:
    Debit Memo Request Item
  - getHigherLevelItem
```
@Nullable
@Generated(value="lombok")
public String getHigherLevelItem()
```
    Constraints: Not nullable, Maximum length: 6
    Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item. Enter the number of a higher-level item.
    
    Returns:
    The number of the higher-level item to which this item belongs in a hierarchy.
  - getDebitMemoRequestItemCategory
```
@Nullable
@Generated(value="lombok")
public String getDebitMemoRequestItemCategory()
```
    Constraints: Not nullable, Maximum length: 4
    The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document. If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.
    
    Returns:
    A classification that distinguishes between different types of item (for example, free of charge items and text items) and determines how the system processes the item.
  - getDebitMemoRequestItemText
```
@Nullable
@Generated(value="lombok")
public String getDebitMemoRequestItemText()
```
    Constraints: Not nullable, Maximum length: 40
    Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations. The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
    
    Returns:
    A short description of the item.
  - getPurchaseOrderByCustomer
```
@Nullable
@Generated(value="lombok")
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).
  - getMaterial
```
@Nullable
@Generated(value="lombok")
public String getMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    
    Returns:
    Alphanumeric key uniquely identifying the material.
  - getMaterialByCustomer
```
@Nullable
@Generated(value="lombok")
public String getMaterialByCustomer()
```
    Constraints: Not nullable, Maximum length: 35
    If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such as Minimum delivery quantity Partial delivery conditions Enter a value from an existing customer-material info record.
    
    Returns:
    Uniquely identifies the material from the customer's point of view.
  - getPricingDate
```
@Nullable
@Generated(value="lombok")
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 Proposal In 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.
  - getRequestedQuantity
```
@Nullable
@Generated(value="lombok")
public BigDecimal getRequestedQuantity()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    
    Returns:
    Requested Quantity
  - getRequestedQuantityUnit
```
@Nullable
@Generated(value="lombok")
public String getRequestedQuantityUnit()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    Requested Quantity Unit
  - getItemGrossWeight
```
@Nullable
@Generated(value="lombok")
public BigDecimal getItemGrossWeight()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the gross weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the gross weight using the target quantity. You can change the value manually at the item level.
    
    Returns:
    The total gross weight of the item. The gross weight represents the net weight plus the weight of packaging.
  - getItemNetWeight
```
@Nullable
@Generated(value="lombok")
public BigDecimal getItemNetWeight()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the net weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the net weight using the target quantity. You can change the value manually at the item level. The gross weight of a refrigerator and its packaging (a cardboard box including protective padding) is 350 pounds. The packaging weighs 25 pounds. In this case, the net weight is 325 pounds.
    
    Returns:
    The total net weight for the item. The net weight represents the gross weight less the weight of packaging.
  - getItemWeightUnit
```
@Nullable
@Generated(value="lombok")
public String getItemWeightUnit()
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a weight, you must enter the corresponding unit of weight here.
    
    Returns:
    Unit referring to the gross weight or net weight of the material.
  - getItemVolume
```
@Nullable
@Generated(value="lombok")
public BigDecimal getItemVolume()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the volume based on the order quantity for the item and the volume proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the volume. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the volume using the target quantity. You can change the value manually at the item level.
    
    Returns:
    The total volume for the item.
  - getItemVolumeUnit
```
@Nullable
@Generated(value="lombok")
public String getItemVolumeUnit()
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a volume, you have to enter the corresponding volume unit here.
    
    Returns:
    Unit referring to the volume of the material.
  - getTransactionCurrency
```
@Nullable
@Generated(value="lombok")
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).
  - getNetAmount
```
@Nullable
@Generated(value="lombok")
public BigDecimal getNetAmount()
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    Returns:
    The net value of the item, after any discounts and surcharges are taken into account. Sales taxes are not included. The value is expressed in the document currency.
  - getMaterialGroup
```
@Nullable
@Generated(value="lombok")
public String getMaterialGroup()
```
    Constraints: Not nullable, Maximum length: 9
    You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
    
    Returns:
    Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.
  - getBatch
```
@Nullable
@Generated(value="lombok")
public String getBatch()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    Assigns a material that is manufactured in batches or production lots to a specific batch.
  - getIncotermsClassification
```
@Nullable
@Generated(value="lombok")
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
@Generated(value="lombok")
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
@Generated(value="lombok")
public String getIncotermsLocation1()
```
    Constraints: Not nullable, Maximum length: 70
    1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms 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 Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If 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
@Generated(value="lombok")
public String getIncotermsLocation2()
```
    Constraints: Not nullable, Maximum length: 70
    No Version: This field is disabled Incoterm Version 2000 This 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 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF 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:
  - getCustomerPaymentTerms
```
@Nullable
@Generated(value="lombok")
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 management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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.
  - getItemBillingBlockReason
```
@Nullable
@Generated(value="lombok")
public String getItemBillingBlockReason()
```
    Constraints: Not nullable, Maximum length: 2
    To block an item for billing, enter one of the values predefined for your system. You can block an item for billing so that, for example, terms of payment or prices can be checked before further processing takes place.
    
    Returns:
    Indicates if the item is blocked for billing.
  - getSalesDocumentRjcnReason
```
@Nullable
@Generated(value="lombok")
public String getSalesDocumentRjcnReason()
```
    Constraints: Not nullable, Maximum length: 2
    The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection: Inquiries and quotations: no further references by other documents Sales orders: no further delivery of items Contracts: no further creation of release orders Credit and debit memo requests: no further processing of credit or debit memos Enter one of the values predefined for your system. If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
    
    Returns:
    The reason for rejecting a quotation or a sales order.
  - getSDProcessStatus
```
@Nullable
@Generated(value="lombok")
public String getSDProcessStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
    
    Returns:
    Displays the overall processing status of the item.
  - getOrderRelatedBillingStatus
```
@Nullable
@Generated(value="lombok")
public String getOrderRelatedBillingStatus()
```
    Constraints: Not nullable, Maximum length: 1
    You determine whether an item is billed as an order-related or delivery-related item when you define item category defaults through the Customizing menus. Credit and debit memo items, for example, are billed as order-related items.
    
    Returns:
    The order-related billing status shows to what extent an item has been processed for billing.
  - getErpConfigContext
```
@Generated(value="lombok")
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
```
@Generated(value="lombok")
public void setDebitMemoRequest(@Nullable
                                      String debitMemoRequest)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    debitMemoRequest -
  - setDebitMemoRequestItem
```
@Generated(value="lombok")
public void setDebitMemoRequestItem(@Nullable
                                          String debitMemoRequestItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    debitMemoRequestItem -
  - setHigherLevelItem
```
@Generated(value="lombok")
public void setHigherLevelItem(@Nullable
                                     String higherLevelItem)
```
    Constraints: Not nullable, Maximum length: 6
    Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item. Enter the number of a higher-level item.
    
    Parameters:
    higherLevelItem -
  - setDebitMemoRequestItemCategory
```
@Generated(value="lombok")
public void setDebitMemoRequestItemCategory(@Nullable
                                                  String debitMemoRequestItemCategory)
```
    Constraints: Not nullable, Maximum length: 4
    The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document. If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.
    
    Parameters:
    debitMemoRequestItemCategory -
  - setDebitMemoRequestItemText
```
@Generated(value="lombok")
public void setDebitMemoRequestItemText(@Nullable
                                              String debitMemoRequestItemText)
```
    Constraints: Not nullable, Maximum length: 40
    Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations. The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
    
    Parameters:
    debitMemoRequestItemText -
  - setPurchaseOrderByCustomer
```
@Generated(value="lombok")
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 -
  - setMaterial
```
@Generated(value="lombok")
public void setMaterial(@Nullable
                              String material)
```
    Constraints: Not nullable, Maximum length: 40
    
    Parameters:
    material -
  - setMaterialByCustomer
```
@Generated(value="lombok")
public void setMaterialByCustomer(@Nullable
                                        String materialByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such as Minimum delivery quantity Partial delivery conditions Enter a value from an existing customer-material info record.
    
    Parameters:
    materialByCustomer -
  - setPricingDate
```
@Generated(value="lombok")
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 Proposal In 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 -
  - setRequestedQuantity
```
@Generated(value="lombok")
public void setRequestedQuantity(@Nullable
                                       BigDecimal requestedQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    
    Parameters:
    requestedQuantity -
  - setRequestedQuantityUnit
```
@Generated(value="lombok")
public void setRequestedQuantityUnit(@Nullable
                                           String requestedQuantityUnit)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    requestedQuantityUnit -
  - setItemGrossWeight
```
@Generated(value="lombok")
public void setItemGrossWeight(@Nullable
                                     BigDecimal itemGrossWeight)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the gross weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the gross weight using the target quantity. You can change the value manually at the item level.
    
    Parameters:
    itemGrossWeight -
  - setItemNetWeight
```
@Generated(value="lombok")
public void setItemNetWeight(@Nullable
                                   BigDecimal itemNetWeight)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the net weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the net weight using the target quantity. You can change the value manually at the item level. The gross weight of a refrigerator and its packaging (a cardboard box including protective padding) is 350 pounds. The packaging weighs 25 pounds. In this case, the net weight is 325 pounds.
    
    Parameters:
    itemNetWeight -
  - setItemWeightUnit
```
@Generated(value="lombok")
public void setItemWeightUnit(@Nullable
                                    String itemWeightUnit)
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a weight, you must enter the corresponding unit of weight here.
    
    Parameters:
    itemWeightUnit -
  - setItemVolume
```
@Generated(value="lombok")
public void setItemVolume(@Nullable
                                BigDecimal itemVolume)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the volume based on the order quantity for the item and the volume proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the volume. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the volume using the target quantity. You can change the value manually at the item level.
    
    Parameters:
    itemVolume -
  - setItemVolumeUnit
```
@Generated(value="lombok")
public void setItemVolumeUnit(@Nullable
                                    String itemVolumeUnit)
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a volume, you have to enter the corresponding volume unit here.
    
    Parameters:
    itemVolumeUnit -
  - setTransactionCurrency
```
@Generated(value="lombok")
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 -
  - setNetAmount
```
@Generated(value="lombok")
public void setNetAmount(@Nullable
                               BigDecimal netAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    Parameters:
    netAmount -
  - setMaterialGroup
```
@Generated(value="lombok")
public void setMaterialGroup(@Nullable
                                   String materialGroup)
```
    Constraints: Not nullable, Maximum length: 9
    You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
    
    Parameters:
    materialGroup -
  - setBatch
```
@Generated(value="lombok")
public void setBatch(@Nullable
                           String batch)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    batch -
  - setIncotermsClassification
```
@Generated(value="lombok")
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
```
@Generated(value="lombok")
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
```
@Generated(value="lombok")
public void setIncotermsLocation1(@Nullable
                                        String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms 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 Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If 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
```
@Generated(value="lombok")
public void setIncotermsLocation2(@Nullable
                                        String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    No Version: This field is disabled Incoterm Version 2000 This 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 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
    
    Parameters:
    incotermsLocation2 -
  - setCustomerPaymentTerms
```
@Generated(value="lombok")
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 management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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 -
  - setItemBillingBlockReason
```
@Generated(value="lombok")
public void setItemBillingBlockReason(@Nullable
                                            String itemBillingBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    To block an item for billing, enter one of the values predefined for your system. You can block an item for billing so that, for example, terms of payment or prices can be checked before further processing takes place.
    
    Parameters:
    itemBillingBlockReason -
  - setSalesDocumentRjcnReason
```
@Generated(value="lombok")
public void setSalesDocumentRjcnReason(@Nullable
                                             String salesDocumentRjcnReason)
```
    Constraints: Not nullable, Maximum length: 2
    The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection: Inquiries and quotations: no further references by other documents Sales orders: no further delivery of items Contracts: no further creation of release orders Credit and debit memo requests: no further processing of credit or debit memos Enter one of the values predefined for your system. If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
    
    Parameters:
    salesDocumentRjcnReason -
  - setSDProcessStatus
```
@Generated(value="lombok")
public void setSDProcessStatus(@Nullable
                                     String sDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
    
    Parameters:
    sDProcessStatus -
  - setOrderRelatedBillingStatus
```
@Generated(value="lombok")
public void setOrderRelatedBillingStatus(@Nullable
                                               String orderRelatedBillingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    You determine whether an item is billed as an order-related or delivery-related item when you define item category defaults through the Customizing menus. Credit and debit memo items, for example, are billed as order-related items.
    
    Parameters:
    orderRelatedBillingStatus -
  - setErpConfigContext
```
@Generated(value="lombok")
public void setErpConfigContext(ErpConfigContext erpConfigContext)
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Parameters:
    erpConfigContext -
  - toString
```
@Generated(value="lombok")
public String toString()
```
    Overrides:
    
    toString in class Entity<DebitMemoRequestItem>
  - equals
```
@Generated(value="lombok")
public boolean equals(Object o)
```
    Overrides:
    
    equals in class Entity<DebitMemoRequestItem>
  - hashCode
```
@Generated(value="lombok")
public int hashCode()
```
    Overrides:
    
    hashCode in class Entity<DebitMemoRequestItem>

Class DebitMemoRequestItem

Nested Class Summary

Field Summary

Constructor Summary

Method Summary

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

Methods inherited from class java.lang.Object

Field Detail

DEBIT_MEMO_REQUEST

DEBIT_MEMO_REQUEST_ITEM

HIGHER_LEVEL_ITEM

DEBIT_MEMO_REQUEST_ITEM_CATEGORY

DEBIT_MEMO_REQUEST_ITEM_TEXT

PURCHASE_ORDER_BY_CUSTOMER

MATERIAL

MATERIAL_BY_CUSTOMER

PRICING_DATE

REQUESTED_QUANTITY

REQUESTED_QUANTITY_UNIT

ITEM_GROSS_WEIGHT

ITEM_NET_WEIGHT

ITEM_WEIGHT_UNIT

ITEM_VOLUME

ITEM_VOLUME_UNIT

TRANSACTION_CURRENCY

NET_AMOUNT

MATERIAL_GROUP

BATCH

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

CUSTOMER_PAYMENT_TERMS

ITEM_BILLING_BLOCK_REASON

SALES_DOCUMENT_RJCN_REASON

S_D_PROCESS_STATUS

ORDER_RELATED_BILLING_STATUS

Constructor Detail

DebitMemoRequestItem

DebitMemoRequestItem

Method Detail

getType

field

fetchDebitMemoRequest

fetchPartner

fetchPricingElement

builder

getDebitMemoRequest

getDebitMemoRequestItem

getHigherLevelItem

getDebitMemoRequestItemCategory

getDebitMemoRequestItemText

getPurchaseOrderByCustomer

getMaterial

getMaterialByCustomer

getPricingDate

getRequestedQuantity

getRequestedQuantityUnit

getItemGrossWeight

getItemNetWeight

getItemWeightUnit

getItemVolume

getItemVolumeUnit

getTransactionCurrency

getNetAmount

getMaterialGroup

getBatch

getIncotermsClassification

getIncotermsTransferLocation

getIncotermsLocation1

getIncotermsLocation2

getCustomerPaymentTerms

getItemBillingBlockReason

getSalesDocumentRjcnReason

getSDProcessStatus

getOrderRelatedBillingStatus

getErpConfigContext

setDebitMemoRequest

setDebitMemoRequestItem

setHigherLevelItem