CustomerReturnItem (SAP S/4HANA Cloud SDK

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

public class CustomerReturnItem
extends VdmEntity<CustomerReturnItem>

Customer Return Item (API)

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class CustomerReturnItem.CustomerReturnItemBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`CustomerReturnItem.CustomerReturnItemBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static CustomerReturnItemSelectable`	`ALL_FIELDS` Selector for all available fields of CustomerReturnItem.
`static CustomerReturnItemField<String>`	`BATCH` Use with available fluent helpers to apply the Batch field to query operations.
`static CustomerReturnItemField<String>`	`CRM_LOGICAL_SYSTEM` Use with available fluent helpers to apply the CRMLogicalSystem field to query operations.
`static CustomerReturnItemField<String>`	`CRM_OBJECT_ID` Use with available fluent helpers to apply the CRMObjectID field to query operations.
`static CustomerReturnItemField<String>`	`CRM_OBJECT_TYPE` Use with available fluent helpers to apply the CRMObjectType field to query operations.
`static CustomerReturnItemField<String>`	`CRM_OBJECT_UUID` Use with available fluent helpers to apply the CRMObjectUUID field to query operations.
`static CustomerReturnItemField<String>`	`CUST_RET_ITM_FOLLOW_UP_ACTIVITY` Use with available fluent helpers to apply the CustRetItmFollowUpActivity field to query operations.
`static CustomerReturnItemField<String>`	`CUST_RET_MATL_AUTHZN` Use with available fluent helpers to apply the CustRetMatlAuthzn field to query operations.
`static CustomerReturnItemField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static CustomerReturnItemField<String>`	`CUSTOMER_RET_MATL_INSP_RESULT_CODE` Use with available fluent helpers to apply the CustomerRetMatlInspResultCode field to query operations.
`static CustomerReturnItemField<String>`	`CUSTOMER_RETURN` Use with available fluent helpers to apply the CustomerReturn field to query operations.
`static CustomerReturnItemField<String>`	`CUSTOMER_RETURN_ITEM` Use with available fluent helpers to apply the CustomerReturnItem field to query operations.
`static CustomerReturnItemField<String>`	`CUSTOMER_RETURN_ITEM_CATEGORY` Use with available fluent helpers to apply the CustomerReturnItemCategory field to query operations.
`static CustomerReturnItemField<String>`	`CUSTOMER_RETURN_ITEM_TEXT` Use with available fluent helpers to apply the CustomerReturnItemText field to query operations.
`static CustomerReturnItemField<String>`	`DELIVERY_PRIORITY` Use with available fluent helpers to apply the DeliveryPriority field to query operations.
`static CustomerReturnItemField<String>`	`HIGHER_LEVEL_ITEM` Use with available fluent helpers to apply the HigherLevelItem field to query operations.
`static CustomerReturnItemField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static CustomerReturnItemField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static CustomerReturnItemField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static CustomerReturnItemField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static CustomerReturnItemField<String>`	`ITEM_BILLING_BLOCK_REASON` Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
`static CustomerReturnItemField<BigDecimal>`	`ITEM_GROSS_WEIGHT` Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
`static CustomerReturnItemField<BigDecimal>`	`ITEM_NET_WEIGHT` Use with available fluent helpers to apply the ItemNetWeight field to query operations.
`static CustomerReturnItemField<BigDecimal>`	`ITEM_VOLUME` Use with available fluent helpers to apply the ItemVolume field to query operations.
`static CustomerReturnItemField<String>`	`ITEM_VOLUME_UNIT` Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
`static CustomerReturnItemField<String>`	`ITEM_WEIGHT_UNIT` Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
`static CustomerReturnItemField<String>`	`MATERIAL` Use with available fluent helpers to apply the Material field to query operations.
`static CustomerReturnItemField<String>`	`MATERIAL_BY_CUSTOMER` Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
`static CustomerReturnItemField<String>`	`MATERIAL_GROUP` Use with available fluent helpers to apply the MaterialGroup field to query operations.
`static CustomerReturnItemField<BigDecimal>`	`NET_AMOUNT` Use with available fluent helpers to apply the NetAmount field to query operations.
`static CustomerReturnItemField<String>`	`NEXT_FLLW_UP_ACTIVITY_FOR_MATL_INSP` Use with available fluent helpers to apply the NextFllwUpActivityForMatlInsp field to query operations.
`static CustomerReturnItemField<String>`	`NEXT_PLANT_FOR_FOLLOW_UP_ACTIVITY` Use with available fluent helpers to apply the NextPlantForFollowUpActivity field to query operations.
`static CustomerReturnItemField<String>`	`PRELIM_REFUND_IS_DETERMINED` Use with available fluent helpers to apply the PrelimRefundIsDetermined field to query operations.
`static CustomerReturnItemField<String>`	`PRODUCT_IS_INSPECTED_AT_CUST_SITE` Use with available fluent helpers to apply the ProductIsInspectedAtCustSite field to query operations.
`static CustomerReturnItemField<String>`	`PRODUCTION_PLANT` Use with available fluent helpers to apply the ProductionPlant field to query operations.
`static CustomerReturnItemField<String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static CustomerReturnItemField<String>`	`REFERENCE_SD_DOCUMENT` Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
`static CustomerReturnItemField<String>`	`REFERENCE_SD_DOCUMENT_CATEGORY` Use with available fluent helpers to apply the ReferenceSDDocumentCategory field to query operations.
`static CustomerReturnItemField<String>`	`REFERENCE_SD_DOCUMENT_ITEM` Use with available fluent helpers to apply the ReferenceSDDocumentItem field to query operations.
`static CustomerReturnItemField<String>`	`REPLACEMENT_MATERIAL` Use with available fluent helpers to apply the ReplacementMaterial field to query operations.
`static CustomerReturnItemField<String>`	`REPLACEMENT_MATERIAL_IS_REQUESTED` Use with available fluent helpers to apply the ReplacementMaterialIsRequested field to query operations.
`static CustomerReturnItemField<String>`	`REPLACEMENT_MATERIAL_QTY_UNIT` Use with available fluent helpers to apply the ReplacementMaterialQtyUnit field to query operations.
`static CustomerReturnItemField<BigDecimal>`	`REPLACEMENT_MATERIAL_QUANTITY` Use with available fluent helpers to apply the ReplacementMaterialQuantity field to query operations.
`static CustomerReturnItemField<String>`	`REPLACEMENT_MATL_SUPPLYING_PLANT` Use with available fluent helpers to apply the ReplacementMatlSupplyingPlant field to query operations.
`static CustomerReturnItemField<BigDecimal>`	`REQUESTED_QUANTITY` Use with available fluent helpers to apply the RequestedQuantity field to query operations.
`static CustomerReturnItemField<String>`	`REQUESTED_QUANTITY_UNIT` Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
`static CustomerReturnItemField<String>`	`RET_MATL_INSP_RESULT_CODE` Use with available fluent helpers to apply the RetMatlInspResultCode field to query operations.
`static CustomerReturnItemField<String>`	`RETS_MGMT_ITM_COMPN_PROCG_STATUS` Use with available fluent helpers to apply the RetsMgmtItmCompnProcgStatus field to query operations.
`static CustomerReturnItemField<String>`	`RETS_MGMT_ITM_LOG_PROCG_STATUS` Use with available fluent helpers to apply the RetsMgmtItmLogProcgStatus field to query operations.
`static CustomerReturnItemField<String>`	`RETS_MGMT_ITM_PROCG_STATUS` Use with available fluent helpers to apply the RetsMgmtItmProcgStatus field to query operations.
`static CustomerReturnItemField<String>`	`RETS_MGMT_PROCESS` Use with available fluent helpers to apply the RetsMgmtProcess field to query operations.
`static CustomerReturnItemField<String>`	`RETS_MGMT_PROCESS_ITEM` Use with available fluent helpers to apply the RetsMgmtProcessItem field to query operations.
`static CustomerReturnItemField<String>`	`RETS_MGMT_PROCESSING_BLOCK` Use with available fluent helpers to apply the RetsMgmtProcessingBlock field to query operations.
`static CustomerReturnItemField<String>`	`RETURN_REASON` Use with available fluent helpers to apply the ReturnReason field to query operations.
`static CustomerReturnItemField<String>`	`RETURNS_DOCUMENT_APPROVAL_STATUS` Use with available fluent helpers to apply the ReturnsDocumentApprovalStatus field to query operations.
`static CustomerReturnItemField<String>`	`RETURNS_DOCUMENT_STATUS` Use with available fluent helpers to apply the ReturnsDocumentStatus field to query operations.
`static CustomerReturnItemField<String>`	`RETURNS_MATERIAL_HAS_BEEN_RECEIVED` Use with available fluent helpers to apply the ReturnsMaterialHasBeenReceived field to query operations.
`static CustomerReturnItemField<String>`	`RETURNS_REFUND_EXTENT` Use with available fluent helpers to apply the ReturnsRefundExtent field to query operations.
`static CustomerReturnItemField<String>`	`RETURNS_REFUND_PROCG_MODE` Use with available fluent helpers to apply the ReturnsRefundProcgMode field to query operations.
`static CustomerReturnItemField<String>`	`RETURNS_REFUND_RJCN_REASON` Use with available fluent helpers to apply the ReturnsRefundRjcnReason field to query operations.
`static CustomerReturnItemField<String>`	`RETURNS_REFUND_TYPE` Use with available fluent helpers to apply the ReturnsRefundType field to query operations.
`static CustomerReturnItemField<String>`	`RETURNS_TRANSSHIPMENT_PLANT` Use with available fluent helpers to apply the ReturnsTransshipmentPlant field to query operations.
`static CustomerReturnItemField<String>`	`SALES_DOCUMENT_RJCN_REASON` Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
`static CustomerReturnItemField<String>`	`SD_DOCUMENT_REJECTION_STATUS` Use with available fluent helpers to apply the SDDocumentRejectionStatus field to query operations.
`static CustomerReturnItemField<String>`	`SD_PROCESS_STATUS` Use with available fluent helpers to apply the SDProcessStatus field to query operations.
`static CustomerReturnItemField<String>`	`SHIPPING_POINT` Use with available fluent helpers to apply the ShippingPoint field to query operations.
`static CustomerReturnItemField<String>`	`STORAGE_LOCATION` Use with available fluent helpers to apply the StorageLocation field to query operations.
`static CustomerReturnItemField<String>`	`SUPLR_RET_MATL_AUTHZN_IS_REQUIRED` Use with available fluent helpers to apply the SuplrRetMatlAuthznIsRequired field to query operations.
`static CustomerReturnItemField<String>`	`SUPPLIER` Use with available fluent helpers to apply the Supplier field to query operations.
`static CustomerReturnItemField<String>`	`SUPPLIER_RET_MATL_AUTHZN` Use with available fluent helpers to apply the SupplierRetMatlAuthzn field to query operations.
`static CustomerReturnItemLink<CustomerReturn>`	`TO_CUSTOMER_RETURN` Use with available fluent helpers to apply the to_CustomerReturn navigation property to query operations.
`static CustomerReturnItemLink<CustomerReturnItemPartner>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static CustomerReturnItemLink<CustomerReturnItemPrcgElmnt>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static CustomerReturnItemLink<CustomerReturnProcessStep>`	`TO_PROCESS_STEP` Use with available fluent helpers to apply the to_ProcessStep navigation property to query operations.
`static CustomerReturnItemLink<CustomerReturnScheduleLine>`	`TO_SCHEDULE_LINE` Use with available fluent helpers to apply the to_ScheduleLine navigation property to query operations.
`static CustomerReturnItemField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.

Constructor Summary

Constructors
Constructor and Description
`CustomerReturnItem()`
CustomerReturnItem(String customerReturn, String customerReturnItem, String higherLevelItem, String customerReturnItemCategory, String customerReturnItemText, String purchaseOrderByCustomer, String material, String materialByCustomer, BigDecimal requestedQuantity, String requestedQuantityUnit, BigDecimal itemGrossWeight, BigDecimal itemNetWeight, String itemWeightUnit, BigDecimal itemVolume, String itemVolumeUnit, String transactionCurrency, BigDecimal netAmount, String materialGroup, String batch, String productionPlant, String storageLocation, String shippingPoint, String deliveryPriority, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String customerPaymentTerms, String salesDocumentRjcnReason, String itemBillingBlockReason, String retsMgmtProcess, String retsMgmtProcessItem, String returnReason, String retsMgmtProcessingBlock, String custRetItmFollowUpActivity, String returnsMaterialHasBeenReceived, String returnsRefundType, String returnsRefundProcgMode, String returnsRefundExtent, String prelimRefundIsDetermined, String returnsRefundRjcnReason, String replacementMaterial, BigDecimal replacementMaterialQuantity, String replacementMaterialQtyUnit, String replacementMaterialIsRequested, String replacementMatlSupplyingPlant, String nextPlantForFollowUpActivity, String returnsTransshipmentPlant, String supplier, String supplierRetMatlAuthzn, String suplrRetMatlAuthznIsRequired, String customerRetMatlInspResultCode, String nextFllwUpActivityForMatlInsp, String retMatlInspResultCode, String productIsInspectedAtCustSite, String custRetMatlAuthzn, String cRMLogicalSystem, String cRMObjectUUID, String cRMObjectID, String cRMObjectType, String retsMgmtItmLogProcgStatus, String retsMgmtItmCompnProcgStatus, String retsMgmtItmProcgStatus, String returnsDocumentStatus, String returnsDocumentApprovalStatus, String sDProcessStatus, String referenceSDDocument, String referenceSDDocumentItem, String referenceSDDocumentCategory, String sDDocumentRejectionStatus, ErpConfigContext erpConfigContext, CustomerReturn toCustomerReturn, List<CustomerReturnItemPartner> toPartner, List<CustomerReturnItemPrcgElmnt> toPricingElement, List<CustomerReturnProcessStep> toProcessStep, List<CustomerReturnScheduleLine> toScheduleLine)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addPartner(CustomerReturnItemPartner... entity)` Adds elements to the list of associated CustomerReturnItemPartner entities.
`void`	`addPricingElement(CustomerReturnItemPrcgElmnt... entity)` Adds elements to the list of associated CustomerReturnItemPrcgElmnt entities.
`void`	`addProcessStep(CustomerReturnProcessStep... entity)` Adds elements to the list of associated CustomerReturnProcessStep entities.
`void`	`addScheduleLine(CustomerReturnScheduleLine... entity)` Adds elements to the list of associated CustomerReturnScheduleLine entities.
`static CustomerReturnItem.CustomerReturnItemBuilder`	`builder()`
`boolean`	`equals(Object o)`
`CustomerReturn`	`fetchCustomerReturn()` Fetches the CustomerReturn entity (one to one) associated with this entity.
`List<CustomerReturnItemPartner>`	`fetchPartner()` Fetches the CustomerReturnItemPartner entities (one to many) associated with this entity.
`List<CustomerReturnItemPrcgElmnt>`	`fetchPricingElement()` Fetches the CustomerReturnItemPrcgElmnt entities (one to many) associated with this entity.
`List<CustomerReturnProcessStep>`	`fetchProcessStep()` Fetches the CustomerReturnProcessStep entities (one to many) associated with this entity.
`List<CustomerReturnScheduleLine>`	`fetchScheduleLine()` Fetches the CustomerReturnScheduleLine entities (one to many) associated with this entity.
`static <T> CustomerReturnItemField<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`	`getCRMLogicalSystem()` Constraints: Not nullable, Maximum length: 10
`String`	`getCRMObjectID()` Constraints: Not nullable, Maximum length: 10
`String`	`getCRMObjectType()` Constraints: Not nullable, Maximum length: 10
`String`	`getCRMObjectUUID()` Constraints: Not nullable, Maximum length: 32
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4 It is used in sales orders, purchase orders, and invoices.
`String`	`getCustomerRetMatlInspResultCode()` Constraints: Not nullable, Maximum length: 4 When you create a return order for the relevant material, the customer inspection code and the corresponding inspection comment provide you with useful information for making the appropriate decisions regarding logistical follow-up activities and refunding.
`String`	`getCustomerReturn()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getCustomerReturnItem()` (Key Field) Constraints: Not nullable, Maximum length: 6
`String`	`getCustomerReturnItemCategory()` Constraints: Not nullable, Maximum length: 4 The system proposes an item category.
`String`	`getCustomerReturnItemText()` Constraints: Not nullable, Maximum length: 40 Short texts are used throughout sales order processing, shipping, and billing.
`CustomerReturn`	`getCustomerReturnOrFetch()` Retrieval of associated CustomerReturn entity (one to one).
`com.google.common.base.Optional<CustomerReturn>`	`getCustomerReturnOrNull()` Retrieval of associated CustomerReturn entity (one to one).
`String`	`getCustRetItmFollowUpActivity()` Constraints: Not nullable, Maximum length: 4 You use logistical follow-up activities to move returned materials to their final destination.
`String`	`getCustRetMatlAuthzn()` Constraints: Not nullable, Maximum length: 20
`String`	`getDeliveryPriority()` Constraints: Not nullable, Maximum length: 2 You can assign delivery priority to either a particular material or to a combination of customer and material.
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`String`	`getHigherLevelItem()` Constraints: Not nullable, Maximum length: 6 Items can be organized hierarchically.
`String`	`getIncotermsClassification()` Constraints: Not nullable, Maximum length: 3 Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board").
`String`	`getIncotermsLocation1()` Constraints: Not nullable, Maximum length: 70 1.
`String`	`getIncotermsLocation2()` Constraints: Not nullable, Maximum length: 70 No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
`String`	`getIncotermsTransferLocation()` Constraints: Not nullable, Maximum length: 28 If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
`String`	`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.
`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.
`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.
`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.
`String`	`getItemVolumeUnit()` Constraints: Not nullable, Maximum length: 3 If you specify a volume, you have to enter the corresponding volume unit here.
`String`	`getItemWeightUnit()` Constraints: Not nullable, Maximum length: 3 If you specify a weight, you must enter the corresponding unit of weight here.
`String`	`getMaterial()` Constraints: Not nullable, Maximum length: 40
`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.
`String`	`getMaterialGroup()` Constraints: Not nullable, Maximum length: 9 You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
`BigDecimal`	`getNetAmount()` Constraints: Not nullable, Precision: 16, Scale: 3
`String`	`getNextFllwUpActivityForMatlInsp()` Constraints: Not nullable, Maximum length: 4 In the Next Follow-Up Activity field, you define a default value in the returns order for the next logistical processing step for the material inspection in the warehouse.
`String`	`getNextPlantForFollowUpActivity()` Constraints: Not nullable, Maximum length: 4
`List<CustomerReturnItemPartner>`	`getPartnerOrFetch()` Retrieval of associated CustomerReturnItemPartner entities (one to many).
`com.google.common.base.Optional<List<CustomerReturnItemPartner>>`	`getPartnerOrNull()` Retrieval of associated CustomerReturnItemPartner entities (one to many).
`String`	`getPrelimRefundIsDetermined()` Constraints: Not nullable, Maximum length: 1
`List<CustomerReturnItemPrcgElmnt>`	`getPricingElementOrFetch()` Retrieval of associated CustomerReturnItemPrcgElmnt entities (one to many).
`com.google.common.base.Optional<List<CustomerReturnItemPrcgElmnt>>`	`getPricingElementOrNull()` Retrieval of associated CustomerReturnItemPrcgElmnt entities (one to many).
`List<CustomerReturnProcessStep>`	`getProcessStepOrFetch()` Retrieval of associated CustomerReturnProcessStep entities (one to many).
`com.google.common.base.Optional<List<CustomerReturnProcessStep>>`	`getProcessStepOrNull()` Retrieval of associated CustomerReturnProcessStep entities (one to many).
`String`	`getProductionPlant()` Constraints: Not nullable, Maximum length: 4
`String`	`getProductIsInspectedAtCustSite()` Constraints: Not nullable, Maximum length: 1
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35 The number creates the link between the customer purchase order and the sales document that you create.
`String`	`getReferenceSDDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getReferenceSDDocumentCategory()` Constraints: Not nullable, Maximum length: 4
`String`	`getReferenceSDDocumentItem()` Constraints: Not nullable, Maximum length: 6
`String`	`getReplacementMaterial()` Constraints: Not nullable, Maximum length: 40 The replacement material is usually identical to the returned material.
`String`	`getReplacementMaterialIsRequested()` Constraints: Not nullable, Maximum length: 1
`String`	`getReplacementMaterialQtyUnit()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getReplacementMaterialQuantity()` Constraints: Not nullable, Precision: 15, Scale: 3 Normally, when you decide to compensate a customer for a returned material with a replacement material, you would replace the entire returned quantity.
`String`	`getReplacementMatlSupplyingPlant()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getRequestedQuantity()` Constraints: Not nullable, Precision: 15, Scale: 3
`String`	`getRequestedQuantityUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getRetMatlInspResultCode()` Constraints: Not nullable, Maximum length: 4
`String`	`getRetsMgmtItmCompnProcgStatus()` Constraints: Not nullable, Maximum length: 1 When selecting the refunding status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is not fully credited.Select Error if you want to select items that have at least one partial process that contains an error in a financial document.Select Completed if you want to select items for which all partial processes are fully credited.The selection criteria Process Status and Logistical Status also apply.A process item is only selected if it fulfills ALL status criteria.
`String`	`getRetsMgmtItmLogProcgStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getRetsMgmtItmProcgStatus()` Constraints: Not nullable, Maximum length: 1 The process can be completed, open, or can contain errors.When selecting the process status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is open.Select Error if you want to select items that have at least one partial process that contains an error.Select Completed if you want to select items for which all partial processes are completed.
`String`	`getRetsMgmtProcess()` Constraints: Not nullable, Maximum length: 10
`String`	`getRetsMgmtProcessingBlock()` Constraints: Not nullable, Maximum length: 1 The further processing of a returns order is blocked if the user who is creating or modifying the returns order is not authorized to do so for the receiving plant.
`String`	`getRetsMgmtProcessItem()` Constraints: Not nullable, Maximum length: 6
`String`	`getReturnReason()` Constraints: Not nullable, Maximum length: 3 You enter the return reason in the returns order.
`String`	`getReturnsDocumentApprovalStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getReturnsDocumentStatus()` Constraints: Not nullable, Maximum length: 1 A document item can have the following statuses:ActiveThe document item has been created without errors.Deletion Flag SetThe document item has been deleted.Document Was CancelledThe document item has been cancelled and a corresponding reversal or cancellation document exists.Reversal (Cancellation) DocumentThis is a cancellation or reversal document and a corresponding cancelled document exists.
`String`	`getReturnsMaterialHasBeenReceived()` Constraints: Not nullable, Maximum length: 1
`String`	`getReturnsRefundExtent()` Constraints: Not nullable, Maximum length: 3 The system can determine the returns refund code automatically from the combination of inspection code and return reason, but the user can also select it manually.You define a returns refund code R01 with description 10% reduction = 90% refund.If the item value of the original order item were 100 euros, then the customer would receive a credit memo for 90 euros.
`String`	`getReturnsRefundProcgMode()` Constraints: Not nullable, Maximum length: 1
`String`	`getReturnsRefundRjcnReason()` Constraints: Not nullable, Maximum length: 2
`String`	`getReturnsRefundType()` Constraints: Not nullable, Maximum length: 1 You can specify Credit Memo to give the customer monetary compensation or Replacement Material to replace the returned material by the same or another material.
`String`	`getReturnsTransshipmentPlant()` Constraints: Not nullable, Maximum length: 1 Transshipment plants can thus be listed in delivery documents, but they are not considered for follow-up documents, such as returns stock transport orders or returns purchase orders.
`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).
`List<CustomerReturnScheduleLine>`	`getScheduleLineOrFetch()` Retrieval of associated CustomerReturnScheduleLine entities (one to many).
`com.google.common.base.Optional<List<CustomerReturnScheduleLine>>`	`getScheduleLineOrNull()` Retrieval of associated CustomerReturnScheduleLine entities (one to many).
`String`	`getSDDocumentRejectionStatus()` Constraints: Not nullable, Maximum length: 1 The system uses the rejection status of items to determine the rejection status at the header level.
`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.
`String`	`getShippingPoint()` Constraints: Not nullable, Maximum length: 4 You can predefine shipping/receiving points in the system, based on different combinations ofplantsshipping conditionsloading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from one shipping point only or received at one receiving point only.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point.
`String`	`getStorageLocation()` Constraints: Not nullable, Maximum length: 4
`String`	`getSuplrRetMatlAuthznIsRequired()` Constraints: Not nullable, Maximum length: 1
`String`	`getSupplier()` Constraints: Not nullable, Maximum length: 10
`String`	`getSupplierRetMatlAuthzn()` Constraints: Not nullable, Maximum length: 20 You can enter the RMA in the following documents:Initial returns documentLogistical follow-upReturns purchase orderYou must enter an RMA at the latest in the returns purchase order before the goods can be issued and a delivery can be created.You only have to enter an RMA if the supplier master or purchasing info record indicates so.
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5 The system proposes the document currency from the customer master record of the sold-to party.
`Class<CustomerReturnItem>`	`getType()`
`int`	`hashCode()`
`void`	`setBatch(String batch)` Constraints: Not nullable, Maximum length: 10
`void`	`setCRMLogicalSystem(String cRMLogicalSystem)` Constraints: Not nullable, Maximum length: 10
`void`	`setCRMObjectID(String cRMObjectID)` Constraints: Not nullable, Maximum length: 10
`void`	`setCRMObjectType(String cRMObjectType)` Constraints: Not nullable, Maximum length: 10
`void`	`setCRMObjectUUID(String cRMObjectUUID)` Constraints: Not nullable, Maximum length: 32
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4 It is used in sales orders, purchase orders, and invoices.
`void`	`setCustomerRetMatlInspResultCode(String customerRetMatlInspResultCode)` Constraints: Not nullable, Maximum length: 4 When you create a return order for the relevant material, the customer inspection code and the corresponding inspection comment provide you with useful information for making the appropriate decisions regarding logistical follow-up activities and refunding.
`void`	`setCustomerReturn(CustomerReturn value)` Overwrites the associated CustomerReturn entity for the loaded navigation property to_CustomerReturn.
`void`	`setCustomerReturn(String value)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setCustomerReturnItem(String customerReturnItem)` (Key Field) Constraints: Not nullable, Maximum length: 6
`void`	`setCustomerReturnItemCategory(String customerReturnItemCategory)` Constraints: Not nullable, Maximum length: 4 The system proposes an item category.
`void`	`setCustomerReturnItemText(String customerReturnItemText)` Constraints: Not nullable, Maximum length: 40 Short texts are used throughout sales order processing, shipping, and billing.
`void`	`setCustRetItmFollowUpActivity(String custRetItmFollowUpActivity)` Constraints: Not nullable, Maximum length: 4 You use logistical follow-up activities to move returned materials to their final destination.
`void`	`setCustRetMatlAuthzn(String custRetMatlAuthzn)` Constraints: Not nullable, Maximum length: 20
`void`	`setDeliveryPriority(String deliveryPriority)` Constraints: Not nullable, Maximum length: 2 You can assign delivery priority to either a particular material or to a combination of customer and material.
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`void`	`setHigherLevelItem(String higherLevelItem)` Constraints: Not nullable, Maximum length: 6 Items can be organized hierarchically.
`void`	`setIncotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3 Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board").
`void`	`setIncotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70 1.
`void`	`setIncotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70 No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
`void`	`setIncotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28 If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
`void`	`setItemBillingBlockReason(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.
`void`	`setItemGrossWeight(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.
`void`	`setItemNetWeight(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.
`void`	`setItemVolume(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.
`void`	`setItemVolumeUnit(String itemVolumeUnit)` Constraints: Not nullable, Maximum length: 3 If you specify a volume, you have to enter the corresponding volume unit here.
`void`	`setItemWeightUnit(String itemWeightUnit)` Constraints: Not nullable, Maximum length: 3 If you specify a weight, you must enter the corresponding unit of weight here.
`void`	`setMaterial(String material)` Constraints: Not nullable, Maximum length: 40
`void`	`setMaterialByCustomer(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.
`void`	`setMaterialGroup(String materialGroup)` Constraints: Not nullable, Maximum length: 9 You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
`void`	`setNetAmount(BigDecimal netAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`void`	`setNextFllwUpActivityForMatlInsp(String nextFllwUpActivityForMatlInsp)` Constraints: Not nullable, Maximum length: 4 In the Next Follow-Up Activity field, you define a default value in the returns order for the next logistical processing step for the material inspection in the warehouse.
`void`	`setNextPlantForFollowUpActivity(String nextPlantForFollowUpActivity)` Constraints: Not nullable, Maximum length: 4
`void`	`setPartner(List<CustomerReturnItemPartner> value)` Overwrites the list of associated CustomerReturnItemPartner entities for the loaded navigation property to_Partner.
`void`	`setPrelimRefundIsDetermined(String prelimRefundIsDetermined)` Constraints: Not nullable, Maximum length: 1
`void`	`setPricingElement(List<CustomerReturnItemPrcgElmnt> value)` Overwrites the list of associated CustomerReturnItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
`void`	`setProcessStep(List<CustomerReturnProcessStep> value)` Overwrites the list of associated CustomerReturnProcessStep entities for the loaded navigation property to_ProcessStep.
`void`	`setProductionPlant(String productionPlant)` Constraints: Not nullable, Maximum length: 4
`void`	`setProductIsInspectedAtCustSite(String productIsInspectedAtCustSite)` Constraints: Not nullable, Maximum length: 1
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35 The number creates the link between the customer purchase order and the sales document that you create.
`void`	`setReferenceSDDocument(String referenceSDDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setReferenceSDDocumentCategory(String referenceSDDocumentCategory)` Constraints: Not nullable, Maximum length: 4
`void`	`setReferenceSDDocumentItem(String referenceSDDocumentItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setReplacementMaterial(String replacementMaterial)` Constraints: Not nullable, Maximum length: 40 The replacement material is usually identical to the returned material.
`void`	`setReplacementMaterialIsRequested(String replacementMaterialIsRequested)` Constraints: Not nullable, Maximum length: 1
`void`	`setReplacementMaterialQtyUnit(String replacementMaterialQtyUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setReplacementMaterialQuantity(BigDecimal replacementMaterialQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3 Normally, when you decide to compensate a customer for a returned material with a replacement material, you would replace the entire returned quantity.
`void`	`setReplacementMatlSupplyingPlant(String replacementMatlSupplyingPlant)` Constraints: Not nullable, Maximum length: 4
`void`	`setRequestedQuantity(BigDecimal requestedQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3
`void`	`setRequestedQuantityUnit(String requestedQuantityUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setRetMatlInspResultCode(String retMatlInspResultCode)` Constraints: Not nullable, Maximum length: 4
`void`	`setRetsMgmtItmCompnProcgStatus(String retsMgmtItmCompnProcgStatus)` Constraints: Not nullable, Maximum length: 1 When selecting the refunding status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is not fully credited.Select Error if you want to select items that have at least one partial process that contains an error in a financial document.Select Completed if you want to select items for which all partial processes are fully credited.The selection criteria Process Status and Logistical Status also apply.A process item is only selected if it fulfills ALL status criteria.
`void`	`setRetsMgmtItmLogProcgStatus(String retsMgmtItmLogProcgStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setRetsMgmtItmProcgStatus(String retsMgmtItmProcgStatus)` Constraints: Not nullable, Maximum length: 1 The process can be completed, open, or can contain errors.When selecting the process status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is open.Select Error if you want to select items that have at least one partial process that contains an error.Select Completed if you want to select items for which all partial processes are completed.
`void`	`setRetsMgmtProcess(String retsMgmtProcess)` Constraints: Not nullable, Maximum length: 10
`void`	`setRetsMgmtProcessingBlock(String retsMgmtProcessingBlock)` Constraints: Not nullable, Maximum length: 1 The further processing of a returns order is blocked if the user who is creating or modifying the returns order is not authorized to do so for the receiving plant.
`void`	`setRetsMgmtProcessItem(String retsMgmtProcessItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setReturnReason(String returnReason)` Constraints: Not nullable, Maximum length: 3 You enter the return reason in the returns order.
`void`	`setReturnsDocumentApprovalStatus(String returnsDocumentApprovalStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setReturnsDocumentStatus(String returnsDocumentStatus)` Constraints: Not nullable, Maximum length: 1 A document item can have the following statuses:ActiveThe document item has been created without errors.Deletion Flag SetThe document item has been deleted.Document Was CancelledThe document item has been cancelled and a corresponding reversal or cancellation document exists.Reversal (Cancellation) DocumentThis is a cancellation or reversal document and a corresponding cancelled document exists.
`void`	`setReturnsMaterialHasBeenReceived(String returnsMaterialHasBeenReceived)` Constraints: Not nullable, Maximum length: 1
`void`	`setReturnsRefundExtent(String returnsRefundExtent)` Constraints: Not nullable, Maximum length: 3 The system can determine the returns refund code automatically from the combination of inspection code and return reason, but the user can also select it manually.You define a returns refund code R01 with description 10% reduction = 90% refund.If the item value of the original order item were 100 euros, then the customer would receive a credit memo for 90 euros.
`void`	`setReturnsRefundProcgMode(String returnsRefundProcgMode)` Constraints: Not nullable, Maximum length: 1
`void`	`setReturnsRefundRjcnReason(String returnsRefundRjcnReason)` Constraints: Not nullable, Maximum length: 2
`void`	`setReturnsRefundType(String returnsRefundType)` Constraints: Not nullable, Maximum length: 1 You can specify Credit Memo to give the customer monetary compensation or Replacement Material to replace the returned material by the same or another material.
`void`	`setReturnsTransshipmentPlant(String returnsTransshipmentPlant)` Constraints: Not nullable, Maximum length: 1 Transshipment plants can thus be listed in delivery documents, but they are not considered for follow-up documents, such as returns stock transport orders or returns purchase orders.
`void`	`setSalesDocumentRjcnReason(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).
`void`	`setScheduleLine(List<CustomerReturnScheduleLine> value)` Overwrites the list of associated CustomerReturnScheduleLine entities for the loaded navigation property to_ScheduleLine.
`void`	`setSDDocumentRejectionStatus(String sDDocumentRejectionStatus)` Constraints: Not nullable, Maximum length: 1 The system uses the rejection status of items to determine the rejection status at the header level.
`void`	`setSDProcessStatus(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.
`void`	`setShippingPoint(String shippingPoint)` Constraints: Not nullable, Maximum length: 4 You can predefine shipping/receiving points in the system, based on different combinations ofplantsshipping conditionsloading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from one shipping point only or received at one receiving point only.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point.
`void`	`setStorageLocation(String storageLocation)` Constraints: Not nullable, Maximum length: 4
`void`	`setSuplrRetMatlAuthznIsRequired(String suplrRetMatlAuthznIsRequired)` Constraints: Not nullable, Maximum length: 1
`void`	`setSupplier(String supplier)` Constraints: Not nullable, Maximum length: 10
`void`	`setSupplierRetMatlAuthzn(String supplierRetMatlAuthzn)` Constraints: Not nullable, Maximum length: 20 You can enter the RMA in the following documents:Initial returns documentLogistical follow-upReturns purchase orderYou must enter an RMA at the latest in the returns purchase order before the goods can be issued and a delivery can be created.You only have to enter an RMA if the supplier master or purchasing info record indicates so.
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5 The system proposes the document currency from the customer master record of the sold-to party.
`String`	`toString()`

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

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

- Field Detail
  - ALL_FIELDS
```
public static final CustomerReturnItemSelectable ALL_FIELDS
```
    Selector for all available fields of CustomerReturnItem.
  - CUSTOMER_RETURN
```
public static final CustomerReturnItemField<String> CUSTOMER_RETURN
```
    Use with available fluent helpers to apply the CustomerReturn field to query operations.
  - CUSTOMER_RETURN_ITEM
```
public static final CustomerReturnItemField<String> CUSTOMER_RETURN_ITEM
```
    Use with available fluent helpers to apply the CustomerReturnItem field to query operations.
  - HIGHER_LEVEL_ITEM
```
public static final CustomerReturnItemField<String> HIGHER_LEVEL_ITEM
```
    Use with available fluent helpers to apply the HigherLevelItem field to query operations.
  - CUSTOMER_RETURN_ITEM_CATEGORY
```
public static final CustomerReturnItemField<String> CUSTOMER_RETURN_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the CustomerReturnItemCategory field to query operations.
  - CUSTOMER_RETURN_ITEM_TEXT
```
public static final CustomerReturnItemField<String> CUSTOMER_RETURN_ITEM_TEXT
```
    Use with available fluent helpers to apply the CustomerReturnItemText field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final CustomerReturnItemField<String> PURCHASE_ORDER_BY_CUSTOMER
```
    Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
  - MATERIAL
```
public static final CustomerReturnItemField<String> MATERIAL
```
    Use with available fluent helpers to apply the Material field to query operations.
  - MATERIAL_BY_CUSTOMER
```
public static final CustomerReturnItemField<String> MATERIAL_BY_CUSTOMER
```
    Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
  - REQUESTED_QUANTITY
```
public static final CustomerReturnItemField<BigDecimal> REQUESTED_QUANTITY
```
    Use with available fluent helpers to apply the RequestedQuantity field to query operations.
  - REQUESTED_QUANTITY_UNIT
```
public static final CustomerReturnItemField<String> REQUESTED_QUANTITY_UNIT
```
    Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
  - ITEM_GROSS_WEIGHT
```
public static final CustomerReturnItemField<BigDecimal> ITEM_GROSS_WEIGHT
```
    Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
  - ITEM_NET_WEIGHT
```
public static final CustomerReturnItemField<BigDecimal> ITEM_NET_WEIGHT
```
    Use with available fluent helpers to apply the ItemNetWeight field to query operations.
  - ITEM_WEIGHT_UNIT
```
public static final CustomerReturnItemField<String> ITEM_WEIGHT_UNIT
```
    Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
  - ITEM_VOLUME
```
public static final CustomerReturnItemField<BigDecimal> ITEM_VOLUME
```
    Use with available fluent helpers to apply the ItemVolume field to query operations.
  - ITEM_VOLUME_UNIT
```
public static final CustomerReturnItemField<String> ITEM_VOLUME_UNIT
```
    Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
  - TRANSACTION_CURRENCY
```
public static final CustomerReturnItemField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - NET_AMOUNT
```
public static final CustomerReturnItemField<BigDecimal> NET_AMOUNT
```
    Use with available fluent helpers to apply the NetAmount field to query operations.
  - MATERIAL_GROUP
```
public static final CustomerReturnItemField<String> MATERIAL_GROUP
```
    Use with available fluent helpers to apply the MaterialGroup field to query operations.
  - BATCH
```
public static final CustomerReturnItemField<String> BATCH
```
    Use with available fluent helpers to apply the Batch field to query operations.
  - PRODUCTION_PLANT
```
public static final CustomerReturnItemField<String> PRODUCTION_PLANT
```
    Use with available fluent helpers to apply the ProductionPlant field to query operations.
  - STORAGE_LOCATION
```
public static final CustomerReturnItemField<String> STORAGE_LOCATION
```
    Use with available fluent helpers to apply the StorageLocation field to query operations.
  - SHIPPING_POINT
```
public static final CustomerReturnItemField<String> SHIPPING_POINT
```
    Use with available fluent helpers to apply the ShippingPoint field to query operations.
  - DELIVERY_PRIORITY
```
public static final CustomerReturnItemField<String> DELIVERY_PRIORITY
```
    Use with available fluent helpers to apply the DeliveryPriority field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final CustomerReturnItemField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final CustomerReturnItemField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final CustomerReturnItemField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final CustomerReturnItemField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final CustomerReturnItemField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - SALES_DOCUMENT_RJCN_REASON
```
public static final CustomerReturnItemField<String> SALES_DOCUMENT_RJCN_REASON
```
    Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
  - ITEM_BILLING_BLOCK_REASON
```
public static final CustomerReturnItemField<String> ITEM_BILLING_BLOCK_REASON
```
    Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
  - RETS_MGMT_PROCESS
```
public static final CustomerReturnItemField<String> RETS_MGMT_PROCESS
```
    Use with available fluent helpers to apply the RetsMgmtProcess field to query operations.
  - RETS_MGMT_PROCESS_ITEM
```
public static final CustomerReturnItemField<String> RETS_MGMT_PROCESS_ITEM
```
    Use with available fluent helpers to apply the RetsMgmtProcessItem field to query operations.
  - RETURN_REASON
```
public static final CustomerReturnItemField<String> RETURN_REASON
```
    Use with available fluent helpers to apply the ReturnReason field to query operations.
  - RETS_MGMT_PROCESSING_BLOCK
```
public static final CustomerReturnItemField<String> RETS_MGMT_PROCESSING_BLOCK
```
    Use with available fluent helpers to apply the RetsMgmtProcessingBlock field to query operations.
  - CUST_RET_ITM_FOLLOW_UP_ACTIVITY
```
public static final CustomerReturnItemField<String> CUST_RET_ITM_FOLLOW_UP_ACTIVITY
```
    Use with available fluent helpers to apply the CustRetItmFollowUpActivity field to query operations.
  - RETURNS_MATERIAL_HAS_BEEN_RECEIVED
```
public static final CustomerReturnItemField<String> RETURNS_MATERIAL_HAS_BEEN_RECEIVED
```
    Use with available fluent helpers to apply the ReturnsMaterialHasBeenReceived field to query operations.
  - RETURNS_REFUND_TYPE
```
public static final CustomerReturnItemField<String> RETURNS_REFUND_TYPE
```
    Use with available fluent helpers to apply the ReturnsRefundType field to query operations.
  - RETURNS_REFUND_PROCG_MODE
```
public static final CustomerReturnItemField<String> RETURNS_REFUND_PROCG_MODE
```
    Use with available fluent helpers to apply the ReturnsRefundProcgMode field to query operations.
  - RETURNS_REFUND_EXTENT
```
public static final CustomerReturnItemField<String> RETURNS_REFUND_EXTENT
```
    Use with available fluent helpers to apply the ReturnsRefundExtent field to query operations.
  - PRELIM_REFUND_IS_DETERMINED
```
public static final CustomerReturnItemField<String> PRELIM_REFUND_IS_DETERMINED
```
    Use with available fluent helpers to apply the PrelimRefundIsDetermined field to query operations.
  - RETURNS_REFUND_RJCN_REASON
```
public static final CustomerReturnItemField<String> RETURNS_REFUND_RJCN_REASON
```
    Use with available fluent helpers to apply the ReturnsRefundRjcnReason field to query operations.
  - REPLACEMENT_MATERIAL
```
public static final CustomerReturnItemField<String> REPLACEMENT_MATERIAL
```
    Use with available fluent helpers to apply the ReplacementMaterial field to query operations.
  - REPLACEMENT_MATERIAL_QUANTITY
```
public static final CustomerReturnItemField<BigDecimal> REPLACEMENT_MATERIAL_QUANTITY
```
    Use with available fluent helpers to apply the ReplacementMaterialQuantity field to query operations.
  - REPLACEMENT_MATERIAL_QTY_UNIT
```
public static final CustomerReturnItemField<String> REPLACEMENT_MATERIAL_QTY_UNIT
```
    Use with available fluent helpers to apply the ReplacementMaterialQtyUnit field to query operations.
  - REPLACEMENT_MATERIAL_IS_REQUESTED
```
public static final CustomerReturnItemField<String> REPLACEMENT_MATERIAL_IS_REQUESTED
```
    Use with available fluent helpers to apply the ReplacementMaterialIsRequested field to query operations.
  - REPLACEMENT_MATL_SUPPLYING_PLANT
```
public static final CustomerReturnItemField<String> REPLACEMENT_MATL_SUPPLYING_PLANT
```
    Use with available fluent helpers to apply the ReplacementMatlSupplyingPlant field to query operations.
  - NEXT_PLANT_FOR_FOLLOW_UP_ACTIVITY
```
public static final CustomerReturnItemField<String> NEXT_PLANT_FOR_FOLLOW_UP_ACTIVITY
```
    Use with available fluent helpers to apply the NextPlantForFollowUpActivity field to query operations.
  - RETURNS_TRANSSHIPMENT_PLANT
```
public static final CustomerReturnItemField<String> RETURNS_TRANSSHIPMENT_PLANT
```
    Use with available fluent helpers to apply the ReturnsTransshipmentPlant field to query operations.
  - SUPPLIER
```
public static final CustomerReturnItemField<String> SUPPLIER
```
    Use with available fluent helpers to apply the Supplier field to query operations.
  - SUPPLIER_RET_MATL_AUTHZN
```
public static final CustomerReturnItemField<String> SUPPLIER_RET_MATL_AUTHZN
```
    Use with available fluent helpers to apply the SupplierRetMatlAuthzn field to query operations.
  - SUPLR_RET_MATL_AUTHZN_IS_REQUIRED
```
public static final CustomerReturnItemField<String> SUPLR_RET_MATL_AUTHZN_IS_REQUIRED
```
    Use with available fluent helpers to apply the SuplrRetMatlAuthznIsRequired field to query operations.
  - CUSTOMER_RET_MATL_INSP_RESULT_CODE
```
public static final CustomerReturnItemField<String> CUSTOMER_RET_MATL_INSP_RESULT_CODE
```
    Use with available fluent helpers to apply the CustomerRetMatlInspResultCode field to query operations.
  - NEXT_FLLW_UP_ACTIVITY_FOR_MATL_INSP
```
public static final CustomerReturnItemField<String> NEXT_FLLW_UP_ACTIVITY_FOR_MATL_INSP
```
    Use with available fluent helpers to apply the NextFllwUpActivityForMatlInsp field to query operations.
  - RET_MATL_INSP_RESULT_CODE
```
public static final CustomerReturnItemField<String> RET_MATL_INSP_RESULT_CODE
```
    Use with available fluent helpers to apply the RetMatlInspResultCode field to query operations.
  - PRODUCT_IS_INSPECTED_AT_CUST_SITE
```
public static final CustomerReturnItemField<String> PRODUCT_IS_INSPECTED_AT_CUST_SITE
```
    Use with available fluent helpers to apply the ProductIsInspectedAtCustSite field to query operations.
  - CUST_RET_MATL_AUTHZN
```
public static final CustomerReturnItemField<String> CUST_RET_MATL_AUTHZN
```
    Use with available fluent helpers to apply the CustRetMatlAuthzn field to query operations.
  - CRM_LOGICAL_SYSTEM
```
public static final CustomerReturnItemField<String> CRM_LOGICAL_SYSTEM
```
    Use with available fluent helpers to apply the CRMLogicalSystem field to query operations.
  - CRM_OBJECT_UUID
```
public static final CustomerReturnItemField<String> CRM_OBJECT_UUID
```
    Use with available fluent helpers to apply the CRMObjectUUID field to query operations.
  - CRM_OBJECT_ID
```
public static final CustomerReturnItemField<String> CRM_OBJECT_ID
```
    Use with available fluent helpers to apply the CRMObjectID field to query operations.
  - CRM_OBJECT_TYPE
```
public static final CustomerReturnItemField<String> CRM_OBJECT_TYPE
```
    Use with available fluent helpers to apply the CRMObjectType field to query operations.
  - RETS_MGMT_ITM_LOG_PROCG_STATUS
```
public static final CustomerReturnItemField<String> RETS_MGMT_ITM_LOG_PROCG_STATUS
```
    Use with available fluent helpers to apply the RetsMgmtItmLogProcgStatus field to query operations.
  - RETS_MGMT_ITM_COMPN_PROCG_STATUS
```
public static final CustomerReturnItemField<String> RETS_MGMT_ITM_COMPN_PROCG_STATUS
```
    Use with available fluent helpers to apply the RetsMgmtItmCompnProcgStatus field to query operations.
  - RETS_MGMT_ITM_PROCG_STATUS
```
public static final CustomerReturnItemField<String> RETS_MGMT_ITM_PROCG_STATUS
```
    Use with available fluent helpers to apply the RetsMgmtItmProcgStatus field to query operations.
  - RETURNS_DOCUMENT_STATUS
```
public static final CustomerReturnItemField<String> RETURNS_DOCUMENT_STATUS
```
    Use with available fluent helpers to apply the ReturnsDocumentStatus field to query operations.
  - RETURNS_DOCUMENT_APPROVAL_STATUS
```
public static final CustomerReturnItemField<String> RETURNS_DOCUMENT_APPROVAL_STATUS
```
    Use with available fluent helpers to apply the ReturnsDocumentApprovalStatus field to query operations.
  - SD_PROCESS_STATUS
```
public static final CustomerReturnItemField<String> SD_PROCESS_STATUS
```
    Use with available fluent helpers to apply the SDProcessStatus field to query operations.
  - REFERENCE_SD_DOCUMENT
```
public static final CustomerReturnItemField<String> REFERENCE_SD_DOCUMENT
```
    Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
  - REFERENCE_SD_DOCUMENT_ITEM
```
public static final CustomerReturnItemField<String> REFERENCE_SD_DOCUMENT_ITEM
```
    Use with available fluent helpers to apply the ReferenceSDDocumentItem field to query operations.
  - REFERENCE_SD_DOCUMENT_CATEGORY
```
public static final CustomerReturnItemField<String> REFERENCE_SD_DOCUMENT_CATEGORY
```
    Use with available fluent helpers to apply the ReferenceSDDocumentCategory field to query operations.
  - SD_DOCUMENT_REJECTION_STATUS
```
public static final CustomerReturnItemField<String> SD_DOCUMENT_REJECTION_STATUS
```
    Use with available fluent helpers to apply the SDDocumentRejectionStatus field to query operations.
  - TO_CUSTOMER_RETURN
```
public static final CustomerReturnItemLink<CustomerReturn> TO_CUSTOMER_RETURN
```
    Use with available fluent helpers to apply the to_CustomerReturn navigation property to query operations.
  - TO_PARTNER
```
public static final CustomerReturnItemLink<CustomerReturnItemPartner> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final CustomerReturnItemLink<CustomerReturnItemPrcgElmnt> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
  - TO_PROCESS_STEP
```
public static final CustomerReturnItemLink<CustomerReturnProcessStep> TO_PROCESS_STEP
```
    Use with available fluent helpers to apply the to_ProcessStep navigation property to query operations.
  - TO_SCHEDULE_LINE
```
public static final CustomerReturnItemLink<CustomerReturnScheduleLine> TO_SCHEDULE_LINE
```
    Use with available fluent helpers to apply the to_ScheduleLine navigation property to query operations.
- Constructor Detail
  - CustomerReturnItem
```
public CustomerReturnItem()
```
  - CustomerReturnItem
```
public CustomerReturnItem(@Nullable
                          String customerReturn,
                          @Nullable
                          String customerReturnItem,
                          @Nullable
                          String higherLevelItem,
                          @Nullable
                          String customerReturnItemCategory,
                          @Nullable
                          String customerReturnItemText,
                          @Nullable
                          String purchaseOrderByCustomer,
                          @Nullable
                          String material,
                          @Nullable
                          String materialByCustomer,
                          @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 productionPlant,
                          @Nullable
                          String storageLocation,
                          @Nullable
                          String shippingPoint,
                          @Nullable
                          String deliveryPriority,
                          @Nullable
                          String incotermsClassification,
                          @Nullable
                          String incotermsTransferLocation,
                          @Nullable
                          String incotermsLocation1,
                          @Nullable
                          String incotermsLocation2,
                          @Nullable
                          String customerPaymentTerms,
                          @Nullable
                          String salesDocumentRjcnReason,
                          @Nullable
                          String itemBillingBlockReason,
                          @Nullable
                          String retsMgmtProcess,
                          @Nullable
                          String retsMgmtProcessItem,
                          @Nullable
                          String returnReason,
                          @Nullable
                          String retsMgmtProcessingBlock,
                          @Nullable
                          String custRetItmFollowUpActivity,
                          @Nullable
                          String returnsMaterialHasBeenReceived,
                          @Nullable
                          String returnsRefundType,
                          @Nullable
                          String returnsRefundProcgMode,
                          @Nullable
                          String returnsRefundExtent,
                          @Nullable
                          String prelimRefundIsDetermined,
                          @Nullable
                          String returnsRefundRjcnReason,
                          @Nullable
                          String replacementMaterial,
                          @Nullable
                          BigDecimal replacementMaterialQuantity,
                          @Nullable
                          String replacementMaterialQtyUnit,
                          @Nullable
                          String replacementMaterialIsRequested,
                          @Nullable
                          String replacementMatlSupplyingPlant,
                          @Nullable
                          String nextPlantForFollowUpActivity,
                          @Nullable
                          String returnsTransshipmentPlant,
                          @Nullable
                          String supplier,
                          @Nullable
                          String supplierRetMatlAuthzn,
                          @Nullable
                          String suplrRetMatlAuthznIsRequired,
                          @Nullable
                          String customerRetMatlInspResultCode,
                          @Nullable
                          String nextFllwUpActivityForMatlInsp,
                          @Nullable
                          String retMatlInspResultCode,
                          @Nullable
                          String productIsInspectedAtCustSite,
                          @Nullable
                          String custRetMatlAuthzn,
                          @Nullable
                          String cRMLogicalSystem,
                          @Nullable
                          String cRMObjectUUID,
                          @Nullable
                          String cRMObjectID,
                          @Nullable
                          String cRMObjectType,
                          @Nullable
                          String retsMgmtItmLogProcgStatus,
                          @Nullable
                          String retsMgmtItmCompnProcgStatus,
                          @Nullable
                          String retsMgmtItmProcgStatus,
                          @Nullable
                          String returnsDocumentStatus,
                          @Nullable
                          String returnsDocumentApprovalStatus,
                          @Nullable
                          String sDProcessStatus,
                          @Nullable
                          String referenceSDDocument,
                          @Nullable
                          String referenceSDDocumentItem,
                          @Nullable
                          String referenceSDDocumentCategory,
                          @Nullable
                          String sDDocumentRejectionStatus,
                          @Nullable
                          ErpConfigContext erpConfigContext,
                          @Nullable
                          CustomerReturn toCustomerReturn,
                          List<CustomerReturnItemPartner> toPartner,
                          List<CustomerReturnItemPrcgElmnt> toPricingElement,
                          List<CustomerReturnProcessStep> toProcessStep,
                          List<CustomerReturnScheduleLine> toScheduleLine)
```
- Method Detail
  - getType
```
public Class<CustomerReturnItem> getType()
```
    Specified by:
    
    getType in class VdmObject<CustomerReturnItem>
    
    Returns:
    
    The class of this object.
  - field
```
public static <T> CustomerReturnItemField<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.
  - fetchCustomerReturn
```
public CustomerReturn fetchCustomerReturn()
                                   throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustomerReturn entity (one to one) associated with this entity. This corresponds to the OData navigation property to_CustomerReturn.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated CustomerReturn entity, or null if an entity is not associated.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getCustomerReturnOrFetch
```
public CustomerReturn getCustomerReturnOrFetch()
                                        throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustomerReturn entity (one to one).
    If the navigation property to_CustomerReturn of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated CustomerReturn entity.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getCustomerReturnOrNull
```
public com.google.common.base.Optional<CustomerReturn> getCustomerReturnOrNull()
```
    Retrieval of associated CustomerReturn entity (one to one).
    If the navigation property to_CustomerReturn for an entity CustomerReturnItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_CustomerReturn is already loaded, the result will contain the CustomerReturn entity. If not, a null value state is returned.
  - setCustomerReturn
```
public void setCustomerReturn(CustomerReturn value)
```
    Overwrites the associated CustomerReturn entity for the loaded navigation property to_CustomerReturn.
    
    Parameters:
    
    value - New CustomerReturn entity.
  - setCustomerReturn
```
public void setCustomerReturn(String value)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    value - customerReturn
  - fetchPartner
```
public List<CustomerReturnItemPartner> fetchPartner()
                                             throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustomerReturnItemPartner entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Partner.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated CustomerReturnItemPartner entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPartnerOrFetch
```
public List<CustomerReturnItemPartner> getPartnerOrFetch()
                                                  throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustomerReturnItemPartner entities (one to many).
    If the navigation property to_Partner of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated CustomerReturnItemPartner entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPartnerOrNull
```
public com.google.common.base.Optional<List<CustomerReturnItemPartner>> getPartnerOrNull()
```
    Retrieval of associated CustomerReturnItemPartner entities (one to many).
    If the navigation property to_Partner for an entity CustomerReturnItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_Partner is already loaded, the result will contain the CustomerReturnItemPartner entities. If not, a null value state is returned.
  - setPartner
```
public void setPartner(@NonNull
                       List<CustomerReturnItemPartner> value)
```
    Overwrites the list of associated CustomerReturnItemPartner entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of CustomerReturnItemPartner entities.
  - addPartner
```
public void addPartner(CustomerReturnItemPartner... entity)
```
    Adds elements to the list of associated CustomerReturnItemPartner entities.
    If the navigation property to_Partner of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of CustomerReturnItemPartner entities.
  - fetchPricingElement
```
public List<CustomerReturnItemPrcgElmnt> fetchPricingElement()
                                                      throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustomerReturnItemPrcgElmnt entities (one to many) associated with this entity. This corresponds to the OData navigation property to_PricingElement.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated CustomerReturnItemPrcgElmnt entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPricingElementOrFetch
```
public List<CustomerReturnItemPrcgElmnt> getPricingElementOrFetch()
                                                           throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustomerReturnItemPrcgElmnt entities (one to many).
    If the navigation property to_PricingElement of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated CustomerReturnItemPrcgElmnt entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getPricingElementOrNull
```
public com.google.common.base.Optional<List<CustomerReturnItemPrcgElmnt>> getPricingElementOrNull()
```
    Retrieval of associated CustomerReturnItemPrcgElmnt entities (one to many).
    If the navigation property to_PricingElement for an entity CustomerReturnItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_PricingElement is already loaded, the result will contain the CustomerReturnItemPrcgElmnt entities. If not, a null value state is returned.
  - setPricingElement
```
public void setPricingElement(@NonNull
                              List<CustomerReturnItemPrcgElmnt> value)
```
    Overwrites the list of associated CustomerReturnItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of CustomerReturnItemPrcgElmnt entities.
  - addPricingElement
```
public void addPricingElement(CustomerReturnItemPrcgElmnt... entity)
```
    Adds elements to the list of associated CustomerReturnItemPrcgElmnt entities.
    If the navigation property to_PricingElement of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of CustomerReturnItemPrcgElmnt entities.
  - fetchProcessStep
```
public List<CustomerReturnProcessStep> fetchProcessStep()
                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustomerReturnProcessStep entities (one to many) associated with this entity. This corresponds to the OData navigation property to_ProcessStep.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated CustomerReturnProcessStep entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getProcessStepOrFetch
```
public List<CustomerReturnProcessStep> getProcessStepOrFetch()
                                                      throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustomerReturnProcessStep entities (one to many).
    If the navigation property to_ProcessStep of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated CustomerReturnProcessStep entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getProcessStepOrNull
```
public com.google.common.base.Optional<List<CustomerReturnProcessStep>> getProcessStepOrNull()
```
    Retrieval of associated CustomerReturnProcessStep entities (one to many).
    If the navigation property to_ProcessStep for an entity CustomerReturnItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_ProcessStep is already loaded, the result will contain the CustomerReturnProcessStep entities. If not, a null value state is returned.
  - setProcessStep
```
public void setProcessStep(@NonNull
                           List<CustomerReturnProcessStep> value)
```
    Overwrites the list of associated CustomerReturnProcessStep entities for the loaded navigation property to_ProcessStep.
    If the navigation property to_ProcessStep of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of CustomerReturnProcessStep entities.
  - addProcessStep
```
public void addProcessStep(CustomerReturnProcessStep... entity)
```
    Adds elements to the list of associated CustomerReturnProcessStep entities.
    If the navigation property to_ProcessStep of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of CustomerReturnProcessStep entities.
  - fetchScheduleLine
```
public List<CustomerReturnScheduleLine> fetchScheduleLine()
                                                   throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the CustomerReturnScheduleLine entities (one to many) associated with this entity. This corresponds to the OData navigation property to_ScheduleLine.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated CustomerReturnScheduleLine entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getScheduleLineOrFetch
```
public List<CustomerReturnScheduleLine> getScheduleLineOrFetch()
                                                        throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated CustomerReturnScheduleLine entities (one to many).
    If the navigation property to_ScheduleLine of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated CustomerReturnScheduleLine entities.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getScheduleLineOrNull
```
public com.google.common.base.Optional<List<CustomerReturnScheduleLine>> getScheduleLineOrNull()
```
    Retrieval of associated CustomerReturnScheduleLine entities (one to many).
    If the navigation property to_ScheduleLine for an entity CustomerReturnItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_ScheduleLine is already loaded, the result will contain the CustomerReturnScheduleLine entities. If not, a null value state is returned.
  - setScheduleLine
```
public void setScheduleLine(@NonNull
                            List<CustomerReturnScheduleLine> value)
```
    Overwrites the list of associated CustomerReturnScheduleLine entities for the loaded navigation property to_ScheduleLine.
    If the navigation property to_ScheduleLine of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    value - List of CustomerReturnScheduleLine entities.
  - addScheduleLine
```
public void addScheduleLine(CustomerReturnScheduleLine... entity)
```
    Adds elements to the list of associated CustomerReturnScheduleLine entities.
    If the navigation property to_ScheduleLine of a queried CustomerReturnItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Parameters:
    
    entity - Array of CustomerReturnScheduleLine entities.
  - builder
```
public static CustomerReturnItem.CustomerReturnItemBuilder builder()
```
  - getCustomerReturn
```
@Nullable
public String getCustomerReturn()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Customer Return
  - getCustomerReturnItem
```
@Nullable
public String getCustomerReturnItem()
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    Customer Return Item
  - getHigherLevelItem
```
@Nullable
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.
  - getCustomerReturnItemCategory
```
@Nullable
public String getCustomerReturnItemCategory()
```
    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.
  - getCustomerReturnItemText
```
@Nullable
public String getCustomerReturnItemText()
```
    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
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
public String getMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getMaterialByCustomer
```
@Nullable
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 asMinimum delivery quantityPartial delivery conditionsEnter a value from an existing customer-material info record.
    
    Returns:
    
    Uniquely identifies the material from the customer's point of view.
  - getRequestedQuantity
```
@Nullable
public BigDecimal getRequestedQuantity()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    
    Returns:
    
    Requested Quantity
  - getRequestedQuantityUnit
```
@Nullable
public String getRequestedQuantityUnit()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Requested Quantity Unit
  - getItemGrossWeight
```
@Nullable
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
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
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
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
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
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
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
public String getMaterialGroup()
```
    Constraints: Not nullable, Maximum length: 9
    You can use material groups to:Restrict the scope of analysesSearch 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
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.
  - getProductionPlant
```
@Nullable
public String getProductionPlant()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Key that uniquely identifies a plant.
  - getStorageLocation
```
@Nullable
public String getStorageLocation()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Number of the storage location in which the material is stored. A plant may contain one or more storage locations.
  - getShippingPoint
```
@Nullable
public String getShippingPoint()
```
    Constraints: Not nullable, Maximum length: 4
    You can predefine shipping/receiving points in the system, based on different combinations ofplantsshipping conditionsloading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from one shipping point only or received at one receiving point only.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.You can define a user-specific default value for the shipping point in the user parameter VST.
    
    Returns:
    
    The physical location (for example, a warehouse or collection of loading ramps) from which you ship the item.
  - getDeliveryPriority
```
@Nullable
public String getDeliveryPriority()
```
    Constraints: Not nullable, Maximum length: 2
    You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
    
    Returns:
    
    The delivery priority assigned to an item.
  - getIncotermsClassification
```
@Nullable
public String getIncotermsClassification()
```
    Constraints: Not nullable, Maximum length: 3
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Returns:
    
    Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - getIncotermsTransferLocation
```
@Nullable
public String getIncotermsTransferLocation()
```
    Constraints: Not nullable, Maximum length: 28
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Returns:
    
    Additional information for the primary Incoterm.
  - getIncotermsLocation1
```
@Nullable
public String getIncotermsLocation1()
```
    Constraints: Not nullable, Maximum length: 70
    1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Returns:
    
    Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - getIncotermsLocation2
```
@Nullable
public String getIncotermsLocation2()
```
    Constraints: Not nullable, Maximum length: 70
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Returns:
    
    Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:
  - getCustomerPaymentTerms
```
@Nullable
public String getCustomerPaymentTerms()
```
    Constraints: Not nullable, Maximum length: 4
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Returns:
    
    Key for defining payment terms composed of cash discount percentages and payment periods.
  - getSalesDocumentRjcnReason
```
@Nullable
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 documentsSales orders: no further delivery of itemsContracts: no further creation of release ordersCredit and debit memo requests: no further processing of credit or debit memosEnter 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.
  - getItemBillingBlockReason
```
@Nullable
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.
  - getRetsMgmtProcess
```
@Nullable
public String getRetsMgmtProcess()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Specifies the unique identifier of the advanced returns process.
  - getRetsMgmtProcessItem
```
@Nullable
public String getRetsMgmtProcessItem()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    Specifies an item in the start document of a returns process. This can be a returns order, a returns purchase order, or a returns stock transport order.
  - getReturnReason
```
@Nullable
public String getReturnReason()
```
    Constraints: Not nullable, Maximum length: 3
    You enter the return reason in the returns order.
    
    Returns:
    
    Specifies the return reason code for a customer return in Advanced Returns Management.
  - getRetsMgmtProcessingBlock
```
@Nullable
public String getRetsMgmtProcessingBlock()
```
    Constraints: Not nullable, Maximum length: 1
    The further processing of a returns order is blocked if the user who is creating or modifying the returns order is not authorized to do so for the receiving plant. The system sets the block to Blocked for Release.If the authorized user at the next receiving plant does not approve the order, he or she can set the blodk to Item to Be Revised.
    
    Returns:
    
    Specifies whether a customer returns order is to be blocked pending approval.
  - getCustRetItmFollowUpActivity
```
@Nullable
public String getCustRetItmFollowUpActivity()
```
    Constraints: Not nullable, Maximum length: 4
    You use logistical follow-up activities to move returned materials to their final destination.
    
    Returns:
    
    Specifies the code of the logistical follow-up activity for a returned material in Advanced Returns Management.
  - getReturnsMaterialHasBeenReceived
```
@Nullable
public String getReturnsMaterialHasBeenReceived()
```
    Constraints: Not nullable, Maximum length: 1
  - getReturnsRefundType
```
@Nullable
public String getReturnsRefundType()
```
    Constraints: Not nullable, Maximum length: 1
    You can specify Credit Memo to give the customer monetary compensation or Replacement Material to replace the returned material by the same or another material.
    
    Returns:
    
    Specifies the type of refund a customer will get for a returned material.
  - getReturnsRefundProcgMode
```
@Nullable
public String getReturnsRefundProcgMode()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Refund Processing Mode for a Return
  - getReturnsRefundExtent
```
@Nullable
public String getReturnsRefundExtent()
```
    Constraints: Not nullable, Maximum length: 3
    The system can determine the returns refund code automatically from the combination of inspection code and return reason, but the user can also select it manually.You define a returns refund code R01 with description 10% reduction = 90% refund.If the item value of the original order item were 100 euros, then the customer would receive a credit memo for 90 euros.
    
    Returns:
    
    Can be used in pricing to calculate the refund amount.
  - getPrelimRefundIsDetermined
```
@Nullable
public String getPrelimRefundIsDetermined()
```
    Constraints: Not nullable, Maximum length: 1
  - getReturnsRefundRjcnReason
```
@Nullable
public String getReturnsRefundRjcnReason()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Specifies the reason for rejection for the credit memo request as a follow-up document.
  - getReplacementMaterial
```
@Nullable
public String getReplacementMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    The replacement material is usually identical to the returned material. You can, however, specify a different material as the replacement.
    
    Returns:
    
    Specifies the material that is given to a customer as a replacement for a returned material.
  - getReplacementMaterialQuantity
```
@Nullable
public BigDecimal getReplacementMaterialQuantity()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Normally, when you decide to compensate a customer for a returned material with a replacement material, you would replace the entire returned quantity. However, you can also just replace part of the returned quantity if, for example, you do not have the full quantity on stock. You could then refund the customer for the remaining quantity with a credit memo.The customer returns 7 pieces of Material A. However, you only have 5 pieces of this material on stock. You decide to compensate the customer with these 5 pieces and create a credit memo request for the remaining 2 pieces. In this case, the value in both the Replaced Quantity field and the Replacement Quantity field is 5. You would then enter 2 in the CMR Quantity (Credit Memo Request Quantity) field so that the customer is compensated for the remaining 2 pieces.
    
    Returns:
    
    Indicates the quantity of the replacement material that you give as compensation in a customer returns process created in Advanced Returns Management.
  - getReplacementMaterialQtyUnit
```
@Nullable
public String getReplacementMaterialQtyUnit()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Indicates the unit of measure for the quantity of the replacement material.
  - getReplacementMaterialIsRequested
```
@Nullable
public String getReplacementMaterialIsRequested()
```
    Constraints: Not nullable, Maximum length: 1
  - getReplacementMatlSupplyingPlant
```
@Nullable
public String getReplacementMatlSupplyingPlant()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Specifies the plant from which the replacement material should be delivered to the customer.
  - getNextPlantForFollowUpActivity
```
@Nullable
public String getNextPlantForFollowUpActivity()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Key uniquely identifying a plant.
  - getReturnsTransshipmentPlant
```
@Nullable
public String getReturnsTransshipmentPlant()
```
    Constraints: Not nullable, Maximum length: 1
    Transshipment plants can thus be listed in delivery documents, but they are not considered for follow-up documents, such as returns stock transport orders or returns purchase orders.
    
    Returns:
    
    Transshipment plants can be included for information purposes when forwarding returned material to other plants or to a supplier.
  - getSupplier
```
@Nullable
public String getSupplier()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.
  - getSupplierRetMatlAuthzn
```
@Nullable
public String getSupplierRetMatlAuthzn()
```
    Constraints: Not nullable, Maximum length: 20
    You can enter the RMA in the following documents:Initial returns documentLogistical follow-upReturns purchase orderYou must enter an RMA at the latest in the returns purchase order before the goods can be issued and a delivery can be created.You only have to enter an RMA if the supplier master or purchasing info record indicates so.
    
    Returns:
    
    Specifies the return material authorization (RMA) number from the supplier.
  - getSuplrRetMatlAuthznIsRequired
```
@Nullable
public String getSuplrRetMatlAuthznIsRequired()
```
    Constraints: Not nullable, Maximum length: 1
  - getCustomerRetMatlInspResultCode
```
@Nullable
public String getCustomerRetMatlInspResultCode()
```
    Constraints: Not nullable, Maximum length: 4
    When you create a return order for the relevant material, the customer inspection code and the corresponding inspection comment provide you with useful information for making the appropriate decisions regarding logistical follow-up activities and refunding.
    
    Returns:
    
    Specifies the quality of a material that a customer wants to return. The customer informs the company to which he or she wants to return the material about the quality of the material.
  - getNextFllwUpActivityForMatlInsp
```
@Nullable
public String getNextFllwUpActivityForMatlInsp()
```
    Constraints: Not nullable, Maximum length: 4
    In the Next Follow-Up Activity field, you define a default value in the returns order for the next logistical processing step for the material inspection in the warehouse. When you call the Material Inspection in Warehouse transaction, the system proposes the value you entered here in the Follow-Up Activity field for the relevant item of the returns delivery. However, the inspector can overwrite this value if necessary.You would typically define a next follow-up activity if you have chosen the follow-up activity 0001 Receive into Plant in the returns order.You cannot enter any relevant parameters for the next follow-up activity entered in this field, such as the supplier for the next follow-up activity 0005 Ship to Supplier. You enter the relevant parameters in the material inspection.Note the following special cases for setting the default value in material inspection:Even if you have not selected the Material Received checkbox (because the customer contacted your company by phone, for example), you can still choose 0004 Ship to Other Plant, 0005 Ship to Supplier, or 0006 Ship to Supplier via Other Plant as the Follow-Up Activity.In this case, the system copies the value entered for the logistical follow-up activity to the material inspection as the default value. This enables you to enter the relevant parameters for the follow-up activity in the returns order, such as the supplier or the next plant, which are then copied to the appropriate fields in the material inspection.For a store return, if you choose 0004 Ship to Other Plant as the Follow-Up Activity in the returns order and also select the Material Received checkbox, the system uses this as the default value for the material inspection in the warehouse of the receiving plant.The system ignores the value in the Next Follow-Up Activity field if the entry does not make sense for the process flow defined by the logistical follow-up activity. This applies to immediate goods receipts, for example, that is if you choose 0002 Immediately Move to Free Available Stock or 0003 Immediately Move to Scrap, since the logistical process is then already completed. If you choose 0004 Ship to Other Plant, 0005 Ship to Supplier, or 0006 Ship to Supplier via Other Plant as the Follow-Up Activity, the system ignores any entry you make in the Next Follow-Up Activity field.In the Customizing activity Activate and Rename Follow-Up Activities, you can replace the standard descriptions with your own.According to the customer on the phone, the material is still originally packaged. When you create the returns order for the relevant material, you specify Transfer to Free Available Stock as the next logistical follow-up activity for the returns order item. After the material has arrived at your company and the inspector performs the Material Inspection transaction, the system uses Transfer to Free Available Stock as the default in the logistical follow-up field.
    
    Returns:
    
    Specifies the code of the next logistical follow-up activity for a returned material that is used as the default in the Material Inspection in Warehouse transaction as part of Advanced Returns Management.
  - getRetMatlInspResultCode
```
@Nullable
public String getRetMatlInspResultCode()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Specifies the quality of the returned material as determined during inspection.
  - getProductIsInspectedAtCustSite
```
@Nullable
public String getProductIsInspectedAtCustSite()
```
    Constraints: Not nullable, Maximum length: 1
  - getCustRetMatlAuthzn
```
@Nullable
public String getCustRetMatlAuthzn()
```
    Constraints: Not nullable, Maximum length: 20
    
    Returns:
    
    Specifies the customer return material authorization (RMA) number.
  - getCRMLogicalSystem
```
@Nullable
public String getCRMLogicalSystem()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    CRM Logical System
  - getCRMObjectUUID
```
@Nullable
public String getCRMObjectUUID()
```
    Constraints: Not nullable, Maximum length: 32
    
    Returns:
    
    CRM Object GUID
  - getCRMObjectID
```
@Nullable
public String getCRMObjectID()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    CRM Object ID
  - getCRMObjectType
```
@Nullable
public String getCRMObjectType()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    CRM Object Type
  - getRetsMgmtItmLogProcgStatus
```
@Nullable
public String getRetsMgmtItmLogProcgStatus()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Logistical Processing Status of a Return
  - getRetsMgmtItmCompnProcgStatus
```
@Nullable
public String getRetsMgmtItmCompnProcgStatus()
```
    Constraints: Not nullable, Maximum length: 1
    When selecting the refunding status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is not fully credited.Select Error if you want to select items that have at least one partial process that contains an error in a financial document.Select Completed if you want to select items for which all partial processes are fully credited.The selection criteria Process Status and Logistical Status also apply.A process item is only selected if it fulfills ALL status criteria.
    
    Returns:
    
    Specifies the refunding status of a returns process or a returns item. Refunding is complete when all quantities of a returns item are fully credited; otherwise refunding is open.
  - getRetsMgmtItmProcgStatus
```
@Nullable
public String getRetsMgmtItmProcgStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The process can be completed, open, or can contain errors.When selecting the process status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is open.Select Error if you want to select items that have at least one partial process that contains an error.Select Completed if you want to select items for which all partial processes are completed.
    
    Returns:
    
    Specifies the processing status of a returns process or process item.
  - getReturnsDocumentStatus
```
@Nullable
public String getReturnsDocumentStatus()
```
    Constraints: Not nullable, Maximum length: 1
    A document item can have the following statuses:ActiveThe document item has been created without errors.Deletion Flag SetThe document item has been deleted.Document Was CancelledThe document item has been cancelled and a corresponding reversal or cancellation document exists.Reversal (Cancellation) DocumentThis is a cancellation or reversal document and a corresponding cancelled document exists.
    
    Returns:
    
    Specifies the status of the document item.
  - getReturnsDocumentApprovalStatus
```
@Nullable
public String getReturnsDocumentApprovalStatus()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Approval Status of Returns Process
  - getSDProcessStatus
```
@Nullable
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.
  - getReferenceSDDocument
```
@Nullable
public String getReferenceSDDocument()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Identifies the sales order to which the delivery refers.
  - getReferenceSDDocumentItem
```
@Nullable
public String getReferenceSDDocumentItem()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    The number of the sales order item to which the delivery item refers.
  - getReferenceSDDocumentCategory
```
@Nullable
public String getReferenceSDDocumentCategory()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Specifies the sales document category of the preceding sales, delivery, or billing document.
  - getSDDocumentRejectionStatus
```
@Nullable
public String getSDDocumentRejectionStatus()
```
    Constraints: Not nullable, Maximum length: 1
    The system uses the rejection status of items to determine the rejection status at the header level. For example, if a customer rejects only one of several items in a quotation, the status of the header shows that the quotation is partly rejected.
    
    Returns:
    
    Indicates whether the sales document item (for example, an item in a quotation) is rejected.
  - getErpConfigContext
```
@Nullable
public ErpConfigContext getErpConfigContext()
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Returns:
    
    The stored ERP system context for executing queries, or null if no such context has been set.
  - setCustomerReturnItem
```
public void setCustomerReturnItem(@Nullable
                                  String customerReturnItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    customerReturnItem -
  - setHigherLevelItem
```
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 -
  - setCustomerReturnItemCategory
```
public void setCustomerReturnItemCategory(@Nullable
                                          String customerReturnItemCategory)
```
    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:
    
    customerReturnItemCategory -
  - setCustomerReturnItemText
```
public void setCustomerReturnItemText(@Nullable
                                      String customerReturnItemText)
```
    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:
    
    customerReturnItemText -
  - setPurchaseOrderByCustomer
```
public void setPurchaseOrderByCustomer(@Nullable
                                       String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    
    Parameters:
    
    purchaseOrderByCustomer -
  - setMaterial
```
public void setMaterial(@Nullable
                        String material)
```
    Constraints: Not nullable, Maximum length: 40
    
    Parameters:
    
    material -
  - setMaterialByCustomer
```
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 asMinimum delivery quantityPartial delivery conditionsEnter a value from an existing customer-material info record.
    
    Parameters:
    
    materialByCustomer -
  - setRequestedQuantity
```
public void setRequestedQuantity(@Nullable
                                 BigDecimal requestedQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    
    Parameters:
    
    requestedQuantity -
  - setRequestedQuantityUnit
```
public void setRequestedQuantityUnit(@Nullable
                                     String requestedQuantityUnit)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    requestedQuantityUnit -
  - setItemGrossWeight
```
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
```
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
```
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
```
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
```
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
```
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
```
public void setNetAmount(@Nullable
                         BigDecimal netAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    Parameters:
    
    netAmount -
  - setMaterialGroup
```
public void setMaterialGroup(@Nullable
                             String materialGroup)
```
    Constraints: Not nullable, Maximum length: 9
    You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
    
    Parameters:
    
    materialGroup -
  - setBatch
```
public void setBatch(@Nullable
                     String batch)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    batch -
  - setProductionPlant
```
public void setProductionPlant(@Nullable
                               String productionPlant)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    productionPlant -
  - setStorageLocation
```
public void setStorageLocation(@Nullable
                               String storageLocation)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    storageLocation -
  - setShippingPoint
```
public void setShippingPoint(@Nullable
                             String shippingPoint)
```
    Constraints: Not nullable, Maximum length: 4
    You can predefine shipping/receiving points in the system, based on different combinations ofplantsshipping conditionsloading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from one shipping point only or received at one receiving point only.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.You can define a user-specific default value for the shipping point in the user parameter VST.
    
    Parameters:
    
    shippingPoint -
  - setDeliveryPriority
```
public void setDeliveryPriority(@Nullable
                                String deliveryPriority)
```
    Constraints: Not nullable, Maximum length: 2
    You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
    
    Parameters:
    
    deliveryPriority -
  - setIncotermsClassification
```
public void setIncotermsClassification(@Nullable
                                       String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Parameters:
    
    incotermsClassification -
  - setIncotermsTransferLocation
```
public void setIncotermsTransferLocation(@Nullable
                                         String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Parameters:
    
    incotermsTransferLocation -
  - setIncotermsLocation1
```
public void setIncotermsLocation1(@Nullable
                                  String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Parameters:
    
    incotermsLocation1 -
  - setIncotermsLocation2
```
public void setIncotermsLocation2(@Nullable
                                  String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Parameters:
    
    incotermsLocation2 -
  - setCustomerPaymentTerms
```
public void setCustomerPaymentTerms(@Nullable
                                    String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Parameters:
    
    customerPaymentTerms -
  - setSalesDocumentRjcnReason
```
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 documentsSales orders: no further delivery of itemsContracts: no further creation of release ordersCredit and debit memo requests: no further processing of credit or debit memosEnter 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 -
  - setItemBillingBlockReason
```
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 -
  - setRetsMgmtProcess
```
public void setRetsMgmtProcess(@Nullable
                               String retsMgmtProcess)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    retsMgmtProcess -
  - setRetsMgmtProcessItem
```
public void setRetsMgmtProcessItem(@Nullable
                                   String retsMgmtProcessItem)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    retsMgmtProcessItem -
  - setReturnReason
```
public void setReturnReason(@Nullable
                            String returnReason)
```
    Constraints: Not nullable, Maximum length: 3
    You enter the return reason in the returns order.
    
    Parameters:
    
    returnReason -
  - setRetsMgmtProcessingBlock
```
public void setRetsMgmtProcessingBlock(@Nullable
                                       String retsMgmtProcessingBlock)
```
    Constraints: Not nullable, Maximum length: 1
    The further processing of a returns order is blocked if the user who is creating or modifying the returns order is not authorized to do so for the receiving plant. The system sets the block to Blocked for Release.If the authorized user at the next receiving plant does not approve the order, he or she can set the blodk to Item to Be Revised.
    
    Parameters:
    
    retsMgmtProcessingBlock -
  - setCustRetItmFollowUpActivity
```
public void setCustRetItmFollowUpActivity(@Nullable
                                          String custRetItmFollowUpActivity)
```
    Constraints: Not nullable, Maximum length: 4
    You use logistical follow-up activities to move returned materials to their final destination.
    
    Parameters:
    
    custRetItmFollowUpActivity -
  - setReturnsMaterialHasBeenReceived
```
public void setReturnsMaterialHasBeenReceived(@Nullable
                                              String returnsMaterialHasBeenReceived)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    returnsMaterialHasBeenReceived -
  - setReturnsRefundType
```
public void setReturnsRefundType(@Nullable
                                 String returnsRefundType)
```
    Constraints: Not nullable, Maximum length: 1
    You can specify Credit Memo to give the customer monetary compensation or Replacement Material to replace the returned material by the same or another material.
    
    Parameters:
    
    returnsRefundType -
  - setReturnsRefundProcgMode
```
public void setReturnsRefundProcgMode(@Nullable
                                      String returnsRefundProcgMode)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    returnsRefundProcgMode -
  - setReturnsRefundExtent
```
public void setReturnsRefundExtent(@Nullable
                                   String returnsRefundExtent)
```
    Constraints: Not nullable, Maximum length: 3
    The system can determine the returns refund code automatically from the combination of inspection code and return reason, but the user can also select it manually.You define a returns refund code R01 with description 10% reduction = 90% refund.If the item value of the original order item were 100 euros, then the customer would receive a credit memo for 90 euros.
    
    Parameters:
    
    returnsRefundExtent -
  - setPrelimRefundIsDetermined
```
public void setPrelimRefundIsDetermined(@Nullable
                                        String prelimRefundIsDetermined)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    prelimRefundIsDetermined -
  - setReturnsRefundRjcnReason
```
public void setReturnsRefundRjcnReason(@Nullable
                                       String returnsRefundRjcnReason)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    returnsRefundRjcnReason -
  - setReplacementMaterial
```
public void setReplacementMaterial(@Nullable
                                   String replacementMaterial)
```
    Constraints: Not nullable, Maximum length: 40
    The replacement material is usually identical to the returned material. You can, however, specify a different material as the replacement.
    
    Parameters:
    
    replacementMaterial -
  - setReplacementMaterialQuantity
```
public void setReplacementMaterialQuantity(@Nullable
                                           BigDecimal replacementMaterialQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Normally, when you decide to compensate a customer for a returned material with a replacement material, you would replace the entire returned quantity. However, you can also just replace part of the returned quantity if, for example, you do not have the full quantity on stock. You could then refund the customer for the remaining quantity with a credit memo.The customer returns 7 pieces of Material A. However, you only have 5 pieces of this material on stock. You decide to compensate the customer with these 5 pieces and create a credit memo request for the remaining 2 pieces. In this case, the value in both the Replaced Quantity field and the Replacement Quantity field is 5. You would then enter 2 in the CMR Quantity (Credit Memo Request Quantity) field so that the customer is compensated for the remaining 2 pieces.
    
    Parameters:
    
    replacementMaterialQuantity -
  - setReplacementMaterialQtyUnit
```
public void setReplacementMaterialQtyUnit(@Nullable
                                          String replacementMaterialQtyUnit)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    replacementMaterialQtyUnit -
  - setReplacementMaterialIsRequested
```
public void setReplacementMaterialIsRequested(@Nullable
                                              String replacementMaterialIsRequested)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    replacementMaterialIsRequested -
  - setReplacementMatlSupplyingPlant
```
public void setReplacementMatlSupplyingPlant(@Nullable
                                             String replacementMatlSupplyingPlant)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    replacementMatlSupplyingPlant -
  - setNextPlantForFollowUpActivity
```
public void setNextPlantForFollowUpActivity(@Nullable
                                            String nextPlantForFollowUpActivity)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    nextPlantForFollowUpActivity -
  - setReturnsTransshipmentPlant
```
public void setReturnsTransshipmentPlant(@Nullable
                                         String returnsTransshipmentPlant)
```
    Constraints: Not nullable, Maximum length: 1
    Transshipment plants can thus be listed in delivery documents, but they are not considered for follow-up documents, such as returns stock transport orders or returns purchase orders.
    
    Parameters:
    
    returnsTransshipmentPlant -
  - setSupplier
```
public void setSupplier(@Nullable
                        String supplier)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    supplier -
  - setSupplierRetMatlAuthzn
```
public void setSupplierRetMatlAuthzn(@Nullable
                                     String supplierRetMatlAuthzn)
```
    Constraints: Not nullable, Maximum length: 20
    You can enter the RMA in the following documents:Initial returns documentLogistical follow-upReturns purchase orderYou must enter an RMA at the latest in the returns purchase order before the goods can be issued and a delivery can be created.You only have to enter an RMA if the supplier master or purchasing info record indicates so.
    
    Parameters:
    
    supplierRetMatlAuthzn -
  - setSuplrRetMatlAuthznIsRequired
```
public void setSuplrRetMatlAuthznIsRequired(@Nullable
                                            String suplrRetMatlAuthznIsRequired)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    suplrRetMatlAuthznIsRequired -
  - setCustomerRetMatlInspResultCode
```
public void setCustomerRetMatlInspResultCode(@Nullable
                                             String customerRetMatlInspResultCode)
```
    Constraints: Not nullable, Maximum length: 4
    When you create a return order for the relevant material, the customer inspection code and the corresponding inspection comment provide you with useful information for making the appropriate decisions regarding logistical follow-up activities and refunding.
    
    Parameters:
    
    customerRetMatlInspResultCode -
  - setNextFllwUpActivityForMatlInsp
```
public void setNextFllwUpActivityForMatlInsp(@Nullable
                                             String nextFllwUpActivityForMatlInsp)
```
    Constraints: Not nullable, Maximum length: 4
    In the Next Follow-Up Activity field, you define a default value in the returns order for the next logistical processing step for the material inspection in the warehouse. When you call the Material Inspection in Warehouse transaction, the system proposes the value you entered here in the Follow-Up Activity field for the relevant item of the returns delivery. However, the inspector can overwrite this value if necessary.You would typically define a next follow-up activity if you have chosen the follow-up activity 0001 Receive into Plant in the returns order.You cannot enter any relevant parameters for the next follow-up activity entered in this field, such as the supplier for the next follow-up activity 0005 Ship to Supplier. You enter the relevant parameters in the material inspection.Note the following special cases for setting the default value in material inspection:Even if you have not selected the Material Received checkbox (because the customer contacted your company by phone, for example), you can still choose 0004 Ship to Other Plant, 0005 Ship to Supplier, or 0006 Ship to Supplier via Other Plant as the Follow-Up Activity.In this case, the system copies the value entered for the logistical follow-up activity to the material inspection as the default value. This enables you to enter the relevant parameters for the follow-up activity in the returns order, such as the supplier or the next plant, which are then copied to the appropriate fields in the material inspection.For a store return, if you choose 0004 Ship to Other Plant as the Follow-Up Activity in the returns order and also select the Material Received checkbox, the system uses this as the default value for the material inspection in the warehouse of the receiving plant.The system ignores the value in the Next Follow-Up Activity field if the entry does not make sense for the process flow defined by the logistical follow-up activity. This applies to immediate goods receipts, for example, that is if you choose 0002 Immediately Move to Free Available Stock or 0003 Immediately Move to Scrap, since the logistical process is then already completed. If you choose 0004 Ship to Other Plant, 0005 Ship to Supplier, or 0006 Ship to Supplier via Other Plant as the Follow-Up Activity, the system ignores any entry you make in the Next Follow-Up Activity field.In the Customizing activity Activate and Rename Follow-Up Activities, you can replace the standard descriptions with your own.According to the customer on the phone, the material is still originally packaged. When you create the returns order for the relevant material, you specify Transfer to Free Available Stock as the next logistical follow-up activity for the returns order item. After the material has arrived at your company and the inspector performs the Material Inspection transaction, the system uses Transfer to Free Available Stock as the default in the logistical follow-up field.
    
    Parameters:
    
    nextFllwUpActivityForMatlInsp -
  - setRetMatlInspResultCode
```
public void setRetMatlInspResultCode(@Nullable
                                     String retMatlInspResultCode)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    retMatlInspResultCode -
  - setProductIsInspectedAtCustSite
```
public void setProductIsInspectedAtCustSite(@Nullable
                                            String productIsInspectedAtCustSite)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    productIsInspectedAtCustSite -
  - setCustRetMatlAuthzn
```
public void setCustRetMatlAuthzn(@Nullable
                                 String custRetMatlAuthzn)
```
    Constraints: Not nullable, Maximum length: 20
    
    Parameters:
    
    custRetMatlAuthzn -
  - setCRMLogicalSystem
```
public void setCRMLogicalSystem(@Nullable
                                String cRMLogicalSystem)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    cRMLogicalSystem -
  - setCRMObjectUUID
```
public void setCRMObjectUUID(@Nullable
                             String cRMObjectUUID)
```
    Constraints: Not nullable, Maximum length: 32
    
    Parameters:
    
    cRMObjectUUID -
  - setCRMObjectID
```
public void setCRMObjectID(@Nullable
                           String cRMObjectID)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    cRMObjectID -
  - setCRMObjectType
```
public void setCRMObjectType(@Nullable
                             String cRMObjectType)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    cRMObjectType -
  - setRetsMgmtItmLogProcgStatus
```
public void setRetsMgmtItmLogProcgStatus(@Nullable
                                         String retsMgmtItmLogProcgStatus)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    retsMgmtItmLogProcgStatus -
  - setRetsMgmtItmCompnProcgStatus
```
public void setRetsMgmtItmCompnProcgStatus(@Nullable
                                           String retsMgmtItmCompnProcgStatus)
```
    Constraints: Not nullable, Maximum length: 1
    When selecting the refunding status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is not fully credited.Select Error if you want to select items that have at least one partial process that contains an error in a financial document.Select Completed if you want to select items for which all partial processes are fully credited.The selection criteria Process Status and Logistical Status also apply.A process item is only selected if it fulfills ALL status criteria.
    
    Parameters:
    
    retsMgmtItmCompnProcgStatus -
  - setRetsMgmtItmProcgStatus
```
public void setRetsMgmtItmProcgStatus(@Nullable
                                      String retsMgmtItmProcgStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The process can be completed, open, or can contain errors.When selecting the process status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is open.Select Error if you want to select items that have at least one partial process that contains an error.Select Completed if you want to select items for which all partial processes are completed.
    
    Parameters:
    
    retsMgmtItmProcgStatus -
  - setReturnsDocumentStatus
```
public void setReturnsDocumentStatus(@Nullable
                                     String returnsDocumentStatus)
```
    Constraints: Not nullable, Maximum length: 1
    A document item can have the following statuses:ActiveThe document item has been created without errors.Deletion Flag SetThe document item has been deleted.Document Was CancelledThe document item has been cancelled and a corresponding reversal or cancellation document exists.Reversal (Cancellation) DocumentThis is a cancellation or reversal document and a corresponding cancelled document exists.
    
    Parameters:
    
    returnsDocumentStatus -
  - setReturnsDocumentApprovalStatus
```
public void setReturnsDocumentApprovalStatus(@Nullable
                                             String returnsDocumentApprovalStatus)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    returnsDocumentApprovalStatus -
  - setSDProcessStatus
```
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 -
  - setReferenceSDDocument
```
public void setReferenceSDDocument(@Nullable
                                   String referenceSDDocument)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    referenceSDDocument -
  - setReferenceSDDocumentItem
```
public void setReferenceSDDocumentItem(@Nullable
                                       String referenceSDDocumentItem)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    referenceSDDocumentItem -
  - setReferenceSDDocumentCategory
```
public void setReferenceSDDocumentCategory(@Nullable
                                           String referenceSDDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    referenceSDDocumentCategory -
  - setSDDocumentRejectionStatus
```
public void setSDDocumentRejectionStatus(@Nullable
                                         String sDDocumentRejectionStatus)
```
    Constraints: Not nullable, Maximum length: 1
    The system uses the rejection status of items to determine the rejection status at the header level. For example, if a customer rejects only one of several items in a quotation, the status of the header shows that the quotation is partly rejected.
    
    Parameters:
    
    sDDocumentRejectionStatus -
  - setErpConfigContext
```
public void setErpConfigContext(@Nullable
                                ErpConfigContext erpConfigContext)
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Parameters:
    
    erpConfigContext -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<CustomerReturnItem>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<CustomerReturnItem>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<CustomerReturnItem>

Class CustomerReturnItem

Nested Class Summary

Field Summary

Constructor Summary

Method Summary

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

CUSTOMER_RETURN

CUSTOMER_RETURN_ITEM

HIGHER_LEVEL_ITEM

CUSTOMER_RETURN_ITEM_CATEGORY

CUSTOMER_RETURN_ITEM_TEXT

PURCHASE_ORDER_BY_CUSTOMER

MATERIAL

MATERIAL_BY_CUSTOMER

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

PRODUCTION_PLANT

STORAGE_LOCATION

SHIPPING_POINT

DELIVERY_PRIORITY

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

CUSTOMER_PAYMENT_TERMS

SALES_DOCUMENT_RJCN_REASON

ITEM_BILLING_BLOCK_REASON

RETS_MGMT_PROCESS

RETS_MGMT_PROCESS_ITEM

RETURN_REASON

RETS_MGMT_PROCESSING_BLOCK

CUST_RET_ITM_FOLLOW_UP_ACTIVITY

RETURNS_MATERIAL_HAS_BEEN_RECEIVED

RETURNS_REFUND_TYPE

RETURNS_REFUND_PROCG_MODE

RETURNS_REFUND_EXTENT

PRELIM_REFUND_IS_DETERMINED

RETURNS_REFUND_RJCN_REASON

REPLACEMENT_MATERIAL

REPLACEMENT_MATERIAL_QUANTITY

REPLACEMENT_MATERIAL_QTY_UNIT

REPLACEMENT_MATERIAL_IS_REQUESTED

REPLACEMENT_MATL_SUPPLYING_PLANT

NEXT_PLANT_FOR_FOLLOW_UP_ACTIVITY

RETURNS_TRANSSHIPMENT_PLANT

SUPPLIER

SUPPLIER_RET_MATL_AUTHZN

SUPLR_RET_MATL_AUTHZN_IS_REQUIRED

CUSTOMER_RET_MATL_INSP_RESULT_CODE

NEXT_FLLW_UP_ACTIVITY_FOR_MATL_INSP

RET_MATL_INSP_RESULT_CODE

PRODUCT_IS_INSPECTED_AT_CUST_SITE

CUST_RET_MATL_AUTHZN

CRM_LOGICAL_SYSTEM

CRM_OBJECT_UUID

CRM_OBJECT_ID

CRM_OBJECT_TYPE

RETS_MGMT_ITM_LOG_PROCG_STATUS

RETS_MGMT_ITM_COMPN_PROCG_STATUS

RETS_MGMT_ITM_PROCG_STATUS

RETURNS_DOCUMENT_STATUS

RETURNS_DOCUMENT_APPROVAL_STATUS

SD_PROCESS_STATUS

REFERENCE_SD_DOCUMENT

REFERENCE_SD_DOCUMENT_ITEM

REFERENCE_SD_DOCUMENT_CATEGORY

SD_DOCUMENT_REJECTION_STATUS

TO_CUSTOMER_RETURN