SalesContractItem (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<SalesContractItem>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.salescontract.SalesContractItem

```
public class SalesContractItem
extends VdmEntity<SalesContractItem>
```
Sales Contract Item (API)
Original entity name from the Odata EDM: A_SalesContractItemType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class SalesContractItem.SalesContractItemBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`SalesContractItem.SalesContractItemBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static SalesContractItemSelectable`	`ALL_FIELDS` Selector for all available fields of SalesContractItem.
`static SalesContractItemField<String>`	`BATCH` Use with available fluent helpers to apply the Batch field to query operations.
`static SalesContractItemField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static SalesContractItemField<String>`	`HIGHER_LEVEL_ITEM` Use with available fluent helpers to apply the HigherLevelItem field to query operations.
`static SalesContractItemField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static SalesContractItemField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static SalesContractItemField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static SalesContractItemField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static SalesContractItemField<String>`	`ITEM_BILLING_BLOCK_REASON` Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
`static SalesContractItemField<BigDecimal>`	`ITEM_GROSS_WEIGHT` Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
`static SalesContractItemField<BigDecimal>`	`ITEM_NET_WEIGHT` Use with available fluent helpers to apply the ItemNetWeight field to query operations.
`static SalesContractItemField<BigDecimal>`	`ITEM_VOLUME` Use with available fluent helpers to apply the ItemVolume field to query operations.
`static SalesContractItemField<String>`	`ITEM_VOLUME_UNIT` Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
`static SalesContractItemField<String>`	`ITEM_WEIGHT_UNIT` Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
`static SalesContractItemField<String>`	`MATERIAL` Use with available fluent helpers to apply the Material field to query operations.
`static SalesContractItemField<String>`	`MATERIAL_BY_CUSTOMER` Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
`static SalesContractItemField<String>`	`MATERIAL_GROUP` Use with available fluent helpers to apply the MaterialGroup field to query operations.
`static SalesContractItemField<BigDecimal>`	`NET_AMOUNT` Use with available fluent helpers to apply the NetAmount field to query operations.
`static SalesContractItemField<String>`	`NMBR_OF_SALES_CONTRACT_VALDTY_PERD` Use with available fluent helpers to apply the NmbrOfSalesContractValdtyPerd field to query operations.
`static SalesContractItemField<BigDecimal>`	`OUTLINE_AGREEMENT_TARGET_AMOUNT` Use with available fluent helpers to apply the OutlineAgreementTargetAmount field to query operations.
`static SalesContractItemField<Calendar>`	`PRICING_DATE` Use with available fluent helpers to apply the PricingDate field to query operations.
`static SalesContractItemField<String>`	`PRODUCTION_PLANT` Use with available fluent helpers to apply the ProductionPlant field to query operations.
`static SalesContractItemField<String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static SalesContractItemField<BigDecimal>`	`REQUESTED_QUANTITY` Use with available fluent helpers to apply the RequestedQuantity field to query operations.
`static SalesContractItemField<String>`	`REQUESTED_QUANTITY_UNIT` Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
`static SalesContractItemField<String>`	`SALES_CONTRACT` Use with available fluent helpers to apply the SalesContract field to query operations.
`static SalesContractItemField<String>`	`SALES_CONTRACT_FOLLOW_UP_ACTION` Use with available fluent helpers to apply the SalesContractFollowUpAction field to query operations.
`static SalesContractItemField<String>`	`SALES_CONTRACT_ITEM` Use with available fluent helpers to apply the SalesContractItem field to query operations.
`static SalesContractItemField<String>`	`SALES_CONTRACT_ITEM_CATEGORY` Use with available fluent helpers to apply the SalesContractItemCategory field to query operations.
`static SalesContractItemField<String>`	`SALES_CONTRACT_ITEM_TEXT` Use with available fluent helpers to apply the SalesContractItemText field to query operations.
`static SalesContractItemField<Calendar>`	`SALES_CONTRACT_SIGNED_DATE` Use with available fluent helpers to apply the SalesContractSignedDate field to query operations.
`static SalesContractItemField<Calendar>`	`SALES_CONTRACT_VALIDITY_END_DATE` Use with available fluent helpers to apply the SalesContractValidityEndDate field to query operations.
`static SalesContractItemField<String>`	`SALES_CONTRACT_VALIDITY_PERD_CAT` Use with available fluent helpers to apply the SalesContractValidityPerdCat field to query operations.
`static SalesContractItemField<String>`	`SALES_CONTRACT_VALIDITY_PERD_UNIT` Use with available fluent helpers to apply the SalesContractValidityPerdUnit field to query operations.
`static SalesContractItemField<Calendar>`	`SALES_CONTRACT_VALIDITY_START_DATE` Use with available fluent helpers to apply the SalesContractValidityStartDate field to query operations.
`static SalesContractItemField<String>`	`SALES_DOCUMENT_RJCN_REASON` Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
`static SalesContractItemField<String>`	`SD_PROCESS_STATUS` Use with available fluent helpers to apply the SDProcessStatus field to query operations.
`static SalesContractItemField<String>`	`SHIPPING_POINT` Use with available fluent helpers to apply the ShippingPoint field to query operations.
`static SalesContractItemField<Calendar>`	`SLS_CONTRACT_FOLLOW_UP_ACTION_DATE` Use with available fluent helpers to apply the SlsContractFollowUpActionDate field to query operations.
`static SalesContractItemField<String>`	`STORAGE_LOCATION` Use with available fluent helpers to apply the StorageLocation field to query operations.
`static SalesContractItemLink<SalesContractItemPartner>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static SalesContractItemLink<SalesContractItemPrcgElmnt>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static SalesContractItemLink<SalesContract>`	`TO_SALES_CONTRACT` Use with available fluent helpers to apply the to_SalesContract navigation property to query operations.
`static SalesContractItemField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.

Constructor Summary

Constructors
Constructor and Description
`SalesContractItem()`
SalesContractItem(String salesContract, String salesContractItem, String higherLevelItem, String salesContractItemCategory, String salesContractItemText, String purchaseOrderByCustomer, String material, String materialByCustomer, Calendar pricingDate, BigDecimal requestedQuantity, String requestedQuantityUnit, BigDecimal itemGrossWeight, BigDecimal itemNetWeight, String itemWeightUnit, BigDecimal itemVolume, String itemVolumeUnit, String transactionCurrency, BigDecimal netAmount, String materialGroup, String batch, String productionPlant, String storageLocation, String shippingPoint, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String customerPaymentTerms, String salesDocumentRjcnReason, String itemBillingBlockReason, String sDProcessStatus, BigDecimal outlineAgreementTargetAmount, Calendar salesContractValidityStartDate, Calendar salesContractValidityEndDate, String nmbrOfSalesContractValdtyPerd, String salesContractValidityPerdUnit, String salesContractValidityPerdCat, Calendar salesContractSignedDate, String salesContractFollowUpAction, Calendar slsContractFollowUpActionDate, ErpConfigContext erpConfigContext, List<SalesContractItemPartner> toPartner, List<SalesContractItemPrcgElmnt> toPricingElement, SalesContract toSalesContract)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addPartner(SalesContractItemPartner... entity)` Adds elements to the list of associated SalesContractItemPartner entities.
`void`	`addPricingElement(SalesContractItemPrcgElmnt... entity)` Adds elements to the list of associated SalesContractItemPrcgElmnt entities.
`static SalesContractItem.SalesContractItemBuilder`	`builder()`
`boolean`	`equals(Object o)`
`List<SalesContractItemPartner>`	`fetchPartner()` Fetches the SalesContractItemPartner entities (one to many) associated with this entity.
`List<SalesContractItemPrcgElmnt>`	`fetchPricingElement()` Fetches the SalesContractItemPrcgElmnt entities (one to many) associated with this entity.
`SalesContract`	`fetchSalesContract()` Fetches the SalesContract entity (one to one) associated with this entity.
`static <T> SalesContractItemField<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 Original property name from the Odata EDM: Batch
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CustomerPaymentTermsIt is used in sales orders, purchase orders, and invoices.
`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 Original property name from the Odata EDM: HigherLevelItemItems can be organized hierarchically.
`String`	`getIncotermsClassification()` Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: IncotermsClassificationIncoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.
`String`	`getIncotermsLocation1()` Constraints: Not nullable, Maximum length: 70 Original property name from the Odata EDM: IncotermsLocation11.
`String`	`getIncotermsLocation2()` Constraints: Not nullable, Maximum length: 70 Original property name from the Odata EDM: IncotermsLocation2No Version: This field is disabled Incoterm Version 2000 This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.
`String`	`getIncotermsTransferLocation()` Constraints: Not nullable, Maximum length: 28 Original property name from the Odata EDM: IncotermsTransferLocationIf 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 Original property name from the Odata EDM: ItemBillingBlockReasonTo block an item for billing, enter one of the values predefined for your system.
`BigDecimal`	`getItemGrossWeight()` Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemGrossWeightThe system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record.
`BigDecimal`	`getItemNetWeight()` Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemNetWeightThe 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 Original property name from the Odata EDM: ItemVolumeThe 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 Original property name from the Odata EDM: ItemVolumeUnitIf you specify a volume, you have to enter the corresponding volume unit here.
`String`	`getItemWeightUnit()` Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ItemWeightUnitIf you specify a weight, you must enter the corresponding unit of weight here.
`String`	`getMaterial()` Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: Material
`String`	`getMaterialByCustomer()` Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: MaterialByCustomerIf 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 Original property name from the Odata EDM: MaterialGroupYou can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
`BigDecimal`	`getNetAmount()` Constraints: Not nullable, Precision: 16, Scale: 3 Original property name from the Odata EDM: NetAmount
`String`	`getNmbrOfSalesContractValdtyPerd()` Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: NmbrOfSalesContractValdtyPerd
`BigDecimal`	`getOutlineAgreementTargetAmount()` Constraints: Not nullable, Precision: 14, Scale: 3 Original property name from the Odata EDM: OutlineAgreementTargetAmountThe target value represents the value of products or services that a customer has agreed to purchase or that a supplier has agreed to supply during the validity period of the outline agreement.
`List<SalesContractItemPartner>`	`getPartnerOrFetch()` Retrieval of associated SalesContractItemPartner entities (one to many).
`com.google.common.base.Optional<List<SalesContractItemPartner>>`	`getPartnerOrNull()` Retrieval of associated SalesContractItemPartner entities (one to many).
`Calendar`	`getPricingDate()` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: PricingDateYou can use the pricing date as a selection criterion when you process billing documents collectively.
`List<SalesContractItemPrcgElmnt>`	`getPricingElementOrFetch()` Retrieval of associated SalesContractItemPrcgElmnt entities (one to many).
`com.google.common.base.Optional<List<SalesContractItemPrcgElmnt>>`	`getPricingElementOrNull()` Retrieval of associated SalesContractItemPrcgElmnt entities (one to many).
`String`	`getProductionPlant()` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ProductionPlant
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: PurchaseOrderByCustomerThe number creates the link between the customer purchase order and the sales document that you create.
`BigDecimal`	`getRequestedQuantity()` Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: RequestedQuantity
`String`	`getRequestedQuantityUnit()` Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: RequestedQuantityUnit
`String`	`getSalesContract()` (Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: SalesContract
`String`	`getSalesContractFollowUpAction()` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SalesContractFollowUpActionCreating a contract Creating a quotation Creating a sales activity such as a telephone call Sending an internal electronic mail
`String`	`getSalesContractItem()` (Key Field) Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SalesContractItem
`String`	`getSalesContractItemCategory()` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SalesContractItemCategoryThe system proposes an item category.
`String`	`getSalesContractItemText()` Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: SalesContractItemTextShort texts are used throughout sales order processing, shipping, and billing.
`SalesContract`	`getSalesContractOrFetch()` Retrieval of associated SalesContract entity (one to one).
`com.google.common.base.Optional<SalesContract>`	`getSalesContractOrNull()` Retrieval of associated SalesContract entity (one to one).
`Calendar`	`getSalesContractSignedDate()` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SalesContractSignedDateThe date you enter can be used as a baseline date for determining other dates in the contract.
`Calendar`	`getSalesContractValidityEndDate()` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SalesContractValidityEndDate
`String`	`getSalesContractValidityPerdCat()` Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: SalesContractValidityPerdCat
`String`	`getSalesContractValidityPerdUnit()` Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SalesContractValidityPerdUnit
`Calendar`	`getSalesContractValidityStartDate()` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SalesContractValidityStartDateThe contract start date can be entered both at header and at item level.
`String`	`getSalesDocumentRjcnReason()` Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: SalesDocumentRjcnReasonThe 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).
`String`	`getSDProcessStatus()` Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SDProcessStatusThe system determines the overall status from all statuses (for example, delivery and billing) for this item.
`String`	`getShippingPoint()` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ShippingPointYou can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.
`Calendar`	`getSlsContractFollowUpActionDate()` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SlsContractFollowUpActionDateThe contract will be included in the worklist for contracts with follow-up actions when The date you enter in this field lies within the selection period you define for the worklist The contract fulfills the other selection criteria you define for the worklist.
`String`	`getStorageLocation()` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: StorageLocation
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: TransactionCurrencyThe system proposes the document currency from the customer master record of the sold-to party.
`Class<SalesContractItem>`	`getType()`
`int`	`hashCode()`
`void`	`setBatch(String batch)` Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Batch
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CustomerPaymentTermsIt is used in sales orders, purchase orders, and invoices.
`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 Original property name from the Odata EDM: HigherLevelItemItems can be organized hierarchically.
`void`	`setIncotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: IncotermsClassificationIncoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.
`void`	`setIncotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70 Original property name from the Odata EDM: IncotermsLocation11.
`void`	`setIncotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70 Original property name from the Odata EDM: IncotermsLocation2No Version: This field is disabled Incoterm Version 2000 This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.
`void`	`setIncotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28 Original property name from the Odata EDM: IncotermsTransferLocationIf 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 Original property name from the Odata EDM: ItemBillingBlockReasonTo block an item for billing, enter one of the values predefined for your system.
`void`	`setItemGrossWeight(BigDecimal itemGrossWeight)` Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemGrossWeightThe system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record.
`void`	`setItemNetWeight(BigDecimal itemNetWeight)` Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemNetWeightThe 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 Original property name from the Odata EDM: ItemVolumeThe 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 Original property name from the Odata EDM: ItemVolumeUnitIf you specify a volume, you have to enter the corresponding volume unit here.
`void`	`setItemWeightUnit(String itemWeightUnit)` Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ItemWeightUnitIf you specify a weight, you must enter the corresponding unit of weight here.
`void`	`setMaterial(String material)` Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: Material
`void`	`setMaterialByCustomer(String materialByCustomer)` Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: MaterialByCustomerIf 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 Original property name from the Odata EDM: MaterialGroupYou can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
`void`	`setNetAmount(BigDecimal netAmount)` Constraints: Not nullable, Precision: 16, Scale: 3 Original property name from the Odata EDM: NetAmount
`void`	`setNmbrOfSalesContractValdtyPerd(String nmbrOfSalesContractValdtyPerd)` Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: NmbrOfSalesContractValdtyPerd
`void`	`setOutlineAgreementTargetAmount(BigDecimal outlineAgreementTargetAmount)` Constraints: Not nullable, Precision: 14, Scale: 3 Original property name from the Odata EDM: OutlineAgreementTargetAmountThe target value represents the value of products or services that a customer has agreed to purchase or that a supplier has agreed to supply during the validity period of the outline agreement.
`void`	`setPartner(List<SalesContractItemPartner> value)` Overwrites the list of associated SalesContractItemPartner entities for the loaded navigation property to_Partner.
`void`	`setPricingDate(Calendar pricingDate)` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: PricingDateYou can use the pricing date as a selection criterion when you process billing documents collectively.
`void`	`setPricingElement(List<SalesContractItemPrcgElmnt> value)` Overwrites the list of associated SalesContractItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
`void`	`setProductionPlant(String productionPlant)` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ProductionPlant
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: PurchaseOrderByCustomerThe number creates the link between the customer purchase order and the sales document that you create.
`void`	`setRequestedQuantity(BigDecimal requestedQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: RequestedQuantity
`void`	`setRequestedQuantityUnit(String requestedQuantityUnit)` Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: RequestedQuantityUnit
`void`	`setSalesContract(SalesContract value)` Overwrites the associated SalesContract entity for the loaded navigation property to_SalesContract.
`void`	`setSalesContract(String salesContract)` (Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: SalesContract
`void`	`setSalesContractFollowUpAction(String salesContractFollowUpAction)` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SalesContractFollowUpActionCreating a contract Creating a quotation Creating a sales activity such as a telephone call Sending an internal electronic mail
`void`	`setSalesContractItem(String salesContractItem)` (Key Field) Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SalesContractItem
`void`	`setSalesContractItemCategory(String salesContractItemCategory)` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SalesContractItemCategoryThe system proposes an item category.
`void`	`setSalesContractItemText(String salesContractItemText)` Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: SalesContractItemTextShort texts are used throughout sales order processing, shipping, and billing.
`void`	`setSalesContractSignedDate(Calendar salesContractSignedDate)` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SalesContractSignedDateThe date you enter can be used as a baseline date for determining other dates in the contract.
`void`	`setSalesContractValidityEndDate(Calendar salesContractValidityEndDate)` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SalesContractValidityEndDate
`void`	`setSalesContractValidityPerdCat(String salesContractValidityPerdCat)` Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: SalesContractValidityPerdCat
`void`	`setSalesContractValidityPerdUnit(String salesContractValidityPerdUnit)` Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SalesContractValidityPerdUnit
`void`	`setSalesContractValidityStartDate(Calendar salesContractValidityStartDate)` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SalesContractValidityStartDateThe contract start date can be entered both at header and at item level.
`void`	`setSalesDocumentRjcnReason(String salesDocumentRjcnReason)` Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: SalesDocumentRjcnReasonThe 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`	`setSDProcessStatus(String sDProcessStatus)` Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SDProcessStatusThe 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 Original property name from the Odata EDM: ShippingPointYou can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.
`void`	`setSlsContractFollowUpActionDate(Calendar slsContractFollowUpActionDate)` Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SlsContractFollowUpActionDateThe contract will be included in the worklist for contracts with follow-up actions when The date you enter in this field lies within the selection period you define for the worklist The contract fulfills the other selection criteria you define for the worklist.
`void`	`setStorageLocation(String storageLocation)` Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: StorageLocation
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: TransactionCurrencyThe 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.VdmEntity
getVersionIdentifier, setVersionIdentifier

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getChangedFields, 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 SalesContractItemSelectable ALL_FIELDS
```
    Selector for all available fields of SalesContractItem.
  - SALES_CONTRACT
```
public static final SalesContractItemField<String> SALES_CONTRACT
```
    Use with available fluent helpers to apply the SalesContract field to query operations.
  - SALES_CONTRACT_ITEM
```
public static final SalesContractItemField<String> SALES_CONTRACT_ITEM
```
    Use with available fluent helpers to apply the SalesContractItem field to query operations.
  - HIGHER_LEVEL_ITEM
```
public static final SalesContractItemField<String> HIGHER_LEVEL_ITEM
```
    Use with available fluent helpers to apply the HigherLevelItem field to query operations.
  - SALES_CONTRACT_ITEM_CATEGORY
```
public static final SalesContractItemField<String> SALES_CONTRACT_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the SalesContractItemCategory field to query operations.
  - SALES_CONTRACT_ITEM_TEXT
```
public static final SalesContractItemField<String> SALES_CONTRACT_ITEM_TEXT
```
    Use with available fluent helpers to apply the SalesContractItemText field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final SalesContractItemField<String> PURCHASE_ORDER_BY_CUSTOMER
```
    Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
  - MATERIAL
```
public static final SalesContractItemField<String> MATERIAL
```
    Use with available fluent helpers to apply the Material field to query operations.
  - MATERIAL_BY_CUSTOMER
```
public static final SalesContractItemField<String> MATERIAL_BY_CUSTOMER
```
    Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
  - PRICING_DATE
```
public static final SalesContractItemField<Calendar> PRICING_DATE
```
    Use with available fluent helpers to apply the PricingDate field to query operations.
  - REQUESTED_QUANTITY
```
public static final SalesContractItemField<BigDecimal> REQUESTED_QUANTITY
```
    Use with available fluent helpers to apply the RequestedQuantity field to query operations.
  - REQUESTED_QUANTITY_UNIT
```
public static final SalesContractItemField<String> REQUESTED_QUANTITY_UNIT
```
    Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
  - ITEM_GROSS_WEIGHT
```
public static final SalesContractItemField<BigDecimal> ITEM_GROSS_WEIGHT
```
    Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
  - ITEM_NET_WEIGHT
```
public static final SalesContractItemField<BigDecimal> ITEM_NET_WEIGHT
```
    Use with available fluent helpers to apply the ItemNetWeight field to query operations.
  - ITEM_WEIGHT_UNIT
```
public static final SalesContractItemField<String> ITEM_WEIGHT_UNIT
```
    Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
  - ITEM_VOLUME
```
public static final SalesContractItemField<BigDecimal> ITEM_VOLUME
```
    Use with available fluent helpers to apply the ItemVolume field to query operations.
  - ITEM_VOLUME_UNIT
```
public static final SalesContractItemField<String> ITEM_VOLUME_UNIT
```
    Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
  - TRANSACTION_CURRENCY
```
public static final SalesContractItemField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - NET_AMOUNT
```
public static final SalesContractItemField<BigDecimal> NET_AMOUNT
```
    Use with available fluent helpers to apply the NetAmount field to query operations.
  - MATERIAL_GROUP
```
public static final SalesContractItemField<String> MATERIAL_GROUP
```
    Use with available fluent helpers to apply the MaterialGroup field to query operations.
  - BATCH
```
public static final SalesContractItemField<String> BATCH
```
    Use with available fluent helpers to apply the Batch field to query operations.
  - PRODUCTION_PLANT
```
public static final SalesContractItemField<String> PRODUCTION_PLANT
```
    Use with available fluent helpers to apply the ProductionPlant field to query operations.
  - STORAGE_LOCATION
```
public static final SalesContractItemField<String> STORAGE_LOCATION
```
    Use with available fluent helpers to apply the StorageLocation field to query operations.
  - SHIPPING_POINT
```
public static final SalesContractItemField<String> SHIPPING_POINT
```
    Use with available fluent helpers to apply the ShippingPoint field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final SalesContractItemField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final SalesContractItemField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final SalesContractItemField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final SalesContractItemField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final SalesContractItemField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - SALES_DOCUMENT_RJCN_REASON
```
public static final SalesContractItemField<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 SalesContractItemField<String> ITEM_BILLING_BLOCK_REASON
```
    Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
  - SD_PROCESS_STATUS
```
public static final SalesContractItemField<String> SD_PROCESS_STATUS
```
    Use with available fluent helpers to apply the SDProcessStatus field to query operations.
  - OUTLINE_AGREEMENT_TARGET_AMOUNT
```
public static final SalesContractItemField<BigDecimal> OUTLINE_AGREEMENT_TARGET_AMOUNT
```
    Use with available fluent helpers to apply the OutlineAgreementTargetAmount field to query operations.
  - SALES_CONTRACT_VALIDITY_START_DATE
```
public static final SalesContractItemField<Calendar> SALES_CONTRACT_VALIDITY_START_DATE
```
    Use with available fluent helpers to apply the SalesContractValidityStartDate field to query operations.
  - SALES_CONTRACT_VALIDITY_END_DATE
```
public static final SalesContractItemField<Calendar> SALES_CONTRACT_VALIDITY_END_DATE
```
    Use with available fluent helpers to apply the SalesContractValidityEndDate field to query operations.
  - NMBR_OF_SALES_CONTRACT_VALDTY_PERD
```
public static final SalesContractItemField<String> NMBR_OF_SALES_CONTRACT_VALDTY_PERD
```
    Use with available fluent helpers to apply the NmbrOfSalesContractValdtyPerd field to query operations.
  - SALES_CONTRACT_VALIDITY_PERD_UNIT
```
public static final SalesContractItemField<String> SALES_CONTRACT_VALIDITY_PERD_UNIT
```
    Use with available fluent helpers to apply the SalesContractValidityPerdUnit field to query operations.
  - SALES_CONTRACT_VALIDITY_PERD_CAT
```
public static final SalesContractItemField<String> SALES_CONTRACT_VALIDITY_PERD_CAT
```
    Use with available fluent helpers to apply the SalesContractValidityPerdCat field to query operations.
  - SALES_CONTRACT_SIGNED_DATE
```
public static final SalesContractItemField<Calendar> SALES_CONTRACT_SIGNED_DATE
```
    Use with available fluent helpers to apply the SalesContractSignedDate field to query operations.
  - SALES_CONTRACT_FOLLOW_UP_ACTION
```
public static final SalesContractItemField<String> SALES_CONTRACT_FOLLOW_UP_ACTION
```
    Use with available fluent helpers to apply the SalesContractFollowUpAction field to query operations.
  - SLS_CONTRACT_FOLLOW_UP_ACTION_DATE
```
public static final SalesContractItemField<Calendar> SLS_CONTRACT_FOLLOW_UP_ACTION_DATE
```
    Use with available fluent helpers to apply the SlsContractFollowUpActionDate field to query operations.
  - TO_PARTNER
```
public static final SalesContractItemLink<SalesContractItemPartner> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final SalesContractItemLink<SalesContractItemPrcgElmnt> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
  - TO_SALES_CONTRACT
```
public static final SalesContractItemLink<SalesContract> TO_SALES_CONTRACT
```
    Use with available fluent helpers to apply the to_SalesContract navigation property to query operations.
- Constructor Detail
  - SalesContractItem
```
public SalesContractItem()
```
  - SalesContractItem
```
public SalesContractItem(@Nullable
                         String salesContract,
                         @Nullable
                         String salesContractItem,
                         @Nullable
                         String higherLevelItem,
                         @Nullable
                         String salesContractItemCategory,
                         @Nullable
                         String salesContractItemText,
                         @Nullable
                         String purchaseOrderByCustomer,
                         @Nullable
                         String material,
                         @Nullable
                         String materialByCustomer,
                         @Nullable
                         Calendar pricingDate,
                         @Nullable
                         BigDecimal requestedQuantity,
                         @Nullable
                         String requestedQuantityUnit,
                         @Nullable
                         BigDecimal itemGrossWeight,
                         @Nullable
                         BigDecimal itemNetWeight,
                         @Nullable
                         String itemWeightUnit,
                         @Nullable
                         BigDecimal itemVolume,
                         @Nullable
                         String itemVolumeUnit,
                         @Nullable
                         String transactionCurrency,
                         @Nullable
                         BigDecimal netAmount,
                         @Nullable
                         String materialGroup,
                         @Nullable
                         String batch,
                         @Nullable
                         String productionPlant,
                         @Nullable
                         String storageLocation,
                         @Nullable
                         String shippingPoint,
                         @Nullable
                         String incotermsClassification,
                         @Nullable
                         String incotermsTransferLocation,
                         @Nullable
                         String incotermsLocation1,
                         @Nullable
                         String incotermsLocation2,
                         @Nullable
                         String customerPaymentTerms,
                         @Nullable
                         String salesDocumentRjcnReason,
                         @Nullable
                         String itemBillingBlockReason,
                         @Nullable
                         String sDProcessStatus,
                         @Nullable
                         BigDecimal outlineAgreementTargetAmount,
                         @Nullable
                         Calendar salesContractValidityStartDate,
                         @Nullable
                         Calendar salesContractValidityEndDate,
                         @Nullable
                         String nmbrOfSalesContractValdtyPerd,
                         @Nullable
                         String salesContractValidityPerdUnit,
                         @Nullable
                         String salesContractValidityPerdCat,
                         @Nullable
                         Calendar salesContractSignedDate,
                         @Nullable
                         String salesContractFollowUpAction,
                         @Nullable
                         Calendar slsContractFollowUpActionDate,
                         @Nullable
                         ErpConfigContext erpConfigContext,
                         List<SalesContractItemPartner> toPartner,
                         List<SalesContractItemPrcgElmnt> toPricingElement,
                         @Nullable
                         SalesContract toSalesContract)
```
- Method Detail
  - getType
```
public Class<SalesContractItem> getType()
```
    Specified by:
    
    getType in class VdmObject<SalesContractItem>
    
    Returns:
    
    The class of this object.
  - setSalesContract
```
public void setSalesContract(@Nullable
                             String salesContract)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesContract
    
    Parameters:
    
    salesContract - Sales Contract
  - setSalesContractItem
```
public void setSalesContractItem(@Nullable
                                 String salesContractItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesContractItem
    
    Parameters:
    
    salesContractItem - Sales Contract Item
  - setHigherLevelItem
```
public void setHigherLevelItem(@Nullable
                               String higherLevelItem)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: HigherLevelItem
    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 - The number of the higher-level item to which this item belongs in a hierarchy.
  - setSalesContractItemCategory
```
public void setSalesContractItemCategory(@Nullable
                                         String salesContractItemCategory)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesContractItemCategory
    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:
    
    salesContractItemCategory - 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.
  - setSalesContractItemText
```
public void setSalesContractItemText(@Nullable
                                     String salesContractItemText)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: SalesContractItemText
    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:
    
    salesContractItemText - A short description of the item.
  - setPurchaseOrderByCustomer
```
public void setPurchaseOrderByCustomer(@Nullable
                                       String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    
    Parameters:
    
    purchaseOrderByCustomer - Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).
  - setMaterial
```
public void setMaterial(@Nullable
                        String material)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
    
    Parameters:
    
    material - Alphanumeric key uniquely identifying the material.
  - setMaterialByCustomer
```
public void setMaterialByCustomer(@Nullable
                                  String materialByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: MaterialByCustomer
    If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such as Minimum delivery quantity Partial delivery conditions Enter a value from an existing customer-material info record.
    
    Parameters:
    
    materialByCustomer - Uniquely identifies the material from the customer's point of view.
  - setPricingDate
```
public void setPricingDate(@Nullable
                           Calendar pricingDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PricingDate
    You can use the pricing date as a selection criterion when you process billing documents collectively. The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue. Determining the Proposal In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date. In the billing document: The billing date is proposed as the pricing date.
    
    Parameters:
    
    pricingDate - The date that determines date-related pricing elements, such as conditions and foreign exchange rate.
  - setRequestedQuantity
```
public void setRequestedQuantity(@Nullable
                                 BigDecimal requestedQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property name from the Odata EDM: RequestedQuantity
    
    Parameters:
    
    requestedQuantity - Requested Quantity
  - setRequestedQuantityUnit
```
public void setRequestedQuantityUnit(@Nullable
                                     String requestedQuantityUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: RequestedQuantityUnit
    
    Parameters:
    
    requestedQuantityUnit - Requested Quantity Unit
  - setItemGrossWeight
```
public void setItemGrossWeight(@Nullable
                               BigDecimal itemGrossWeight)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property name from the Odata EDM: ItemGrossWeight
    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 - The total gross weight of the item. The gross weight represents the net weight plus the weight of packaging.
  - setItemNetWeight
```
public void setItemNetWeight(@Nullable
                             BigDecimal itemNetWeight)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property name from the Odata EDM: ItemNetWeight
    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 - The total net weight for the item. The net weight represents the gross weight less the weight of packaging.
  - setItemWeightUnit
```
public void setItemWeightUnit(@Nullable
                              String itemWeightUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: ItemWeightUnit
    If you specify a weight, you must enter the corresponding unit of weight here.
    
    Parameters:
    
    itemWeightUnit - Unit referring to the gross weight or net weight of the material.
  - setItemVolume
```
public void setItemVolume(@Nullable
                          BigDecimal itemVolume)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property name from the Odata EDM: ItemVolume
    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 - The total volume for the item.
  - setItemVolumeUnit
```
public void setItemVolumeUnit(@Nullable
                              String itemVolumeUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: ItemVolumeUnit
    If you specify a volume, you have to enter the corresponding volume unit here.
    
    Parameters:
    
    itemVolumeUnit - Unit referring to the volume of the material.
  - setTransactionCurrency
```
public void setTransactionCurrency(@Nullable
                                   String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: TransactionCurrency
    The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
    
    Parameters:
    
    transactionCurrency - The currency that applies to the document (for example, to a sales order or an invoice).
  - setNetAmount
```
public void setNetAmount(@Nullable
                         BigDecimal netAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: NetAmount
    
    Parameters:
    
    netAmount - 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.
  - setMaterialGroup
```
public void setMaterialGroup(@Nullable
                             String materialGroup)
```
    Constraints: Not nullable, Maximum length: 9
    Original property name from the Odata EDM: MaterialGroup
    You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
    
    Parameters:
    
    materialGroup - Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.
  - setBatch
```
public void setBatch(@Nullable
                     String batch)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Batch
    
    Parameters:
    
    batch - Assigns a material that is manufactured in batches or production lots to a specific batch.
  - setProductionPlant
```
public void setProductionPlant(@Nullable
                               String productionPlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ProductionPlant
    
    Parameters:
    
    productionPlant - Key that uniquely identifies a plant.
  - setStorageLocation
```
public void setStorageLocation(@Nullable
                               String storageLocation)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: StorageLocation
    
    Parameters:
    
    storageLocation - Number of the storage location in which the material is stored. A plant may contain one or more storage locations.
  - setShippingPoint
```
public void setShippingPoint(@Nullable
                             String shippingPoint)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ShippingPoint
    You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During 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 - The physical location (for example, a warehouse or collection of loading ramps) from which you ship the item.
  - setIncotermsClassification
```
public void setIncotermsClassification(@Nullable
                                       String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully. If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Parameters:
    
    incotermsClassification - Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - setIncotermsTransferLocation
```
public void setIncotermsTransferLocation(@Nullable
                                         String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Parameters:
    
    incotermsTransferLocation - Additional information for the primary Incoterm.
  - setIncotermsLocation1
```
public void setIncotermsLocation1(@Nullable
                                  String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 1 EXW Ex Works Place of Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Parameters:
    
    incotermsLocation1 - Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - setIncotermsLocation2
```
public void setIncotermsLocation2(@Nullable
                                  String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    No Version: This field is disabled Incoterm Version 2000 This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions. Incoterm Version 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
    
    Parameters:
    
    incotermsLocation2 - 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:
  - setCustomerPaymentTerms
```
public void setCustomerPaymentTerms(@Nullable
                                    String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data can be entered in the field for the terms of payment key in various ways as you enter a business transaction: In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question. In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field. Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at: item level in sales orders header level in purchase orders and invoices Master records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Parameters:
    
    customerPaymentTerms - Key for defining payment terms composed of cash discount percentages and payment periods.
  - setSalesDocumentRjcnReason
```
public void setSalesDocumentRjcnReason(@Nullable
                                       String salesDocumentRjcnReason)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: SalesDocumentRjcnReason
    The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection: Inquiries and quotations: no further references by other documents Sales orders: no further delivery of items Contracts: no further creation of release orders Credit and debit memo requests: no further processing of credit or debit memos Enter one of the values predefined for your system. If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
    
    Parameters:
    
    salesDocumentRjcnReason - The reason for rejecting a quotation or a sales order.
  - setItemBillingBlockReason
```
public void setItemBillingBlockReason(@Nullable
                                      String itemBillingBlockReason)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ItemBillingBlockReason
    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 - Indicates if the item is blocked for billing.
  - setSDProcessStatus
```
public void setSDProcessStatus(@Nullable
                               String sDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SDProcessStatus
    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 - Displays the overall processing status of the item.
  - setOutlineAgreementTargetAmount
```
public void setOutlineAgreementTargetAmount(@Nullable
                                            BigDecimal outlineAgreementTargetAmount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: OutlineAgreementTargetAmount
    The target value represents the value of products or services that a customer has agreed to purchase or that a supplier has agreed to supply during the validity period of the outline agreement.
    
    Parameters:
    
    outlineAgreementTargetAmount - The target value of an outline agreement (for example, a value contract). The value is expressed in the document currency.
  - setSalesContractValidityStartDate
```
public void setSalesContractValidityStartDate(@Nullable
                                              Calendar salesContractValidityStartDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesContractValidityStartDate
    The contract start date can be entered both at header and at item level. If the contract start date is only entered at header level, then it is valid for all items. The contract start date can be proposed automatically as a default from another data field on the basis of a date rule.
    
    Parameters:
    
    salesContractValidityStartDate - Enter the contract start date.
  - setSalesContractValidityEndDate
```
public void setSalesContractValidityEndDate(@Nullable
                                            Calendar salesContractValidityEndDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesContractValidityEndDate
    
    Parameters:
    
    salesContractValidityEndDate - Contract End Date
  - setNmbrOfSalesContractValdtyPerd
```
public void setNmbrOfSalesContractValdtyPerd(@Nullable
                                             String nmbrOfSalesContractValdtyPerd)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NmbrOfSalesContractValdtyPerd
    
    Parameters:
    
    nmbrOfSalesContractValdtyPerd - Validity Period of Contract
  - setSalesContractValidityPerdUnit
```
public void setSalesContractValidityPerdUnit(@Nullable
                                             String salesContractValidityPerdUnit)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SalesContractValidityPerdUnit
    
    Parameters:
    
    salesContractValidityPerdUnit - Unit of Validity Period of Contract
  - setSalesContractValidityPerdCat
```
public void setSalesContractValidityPerdCat(@Nullable
                                            String salesContractValidityPerdCat)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: SalesContractValidityPerdCat
    
    Parameters:
    
    salesContractValidityPerdCat - Enter a value here to indicate what kind of validity period the contract has (6 months, one year, and so on).
  - setSalesContractSignedDate
```
public void setSalesContractSignedDate(@Nullable
                                       Calendar salesContractSignedDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesContractSignedDate
    The date you enter can be used as a baseline date for determining other dates in the contract. You want the contract to become valid on the day it is signed by the customer. You enter a date rule for the contract start date which has the date on which the contract is signed as its baseline date. When you enter the date on which the contract was signed in the contract, the system automatically makes the appropriate entry in the contract start date field.
    
    Parameters:
    
    salesContractSignedDate - Enter the date on which the customer signs the contract.
  - setSalesContractFollowUpAction
```
public void setSalesContractFollowUpAction(@Nullable
                                           String salesContractFollowUpAction)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesContractFollowUpAction
    Creating a contract Creating a quotation Creating a sales activity such as a telephone call Sending an internal electronic mail
    
    Parameters:
    
    salesContractFollowUpAction - Enter the follow-up action which is to be taken when the contract ends. Follow-up actions are
  - setSlsContractFollowUpActionDate
```
public void setSlsContractFollowUpActionDate(@Nullable
                                             Calendar slsContractFollowUpActionDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SlsContractFollowUpActionDate
    The contract will be included in the worklist for contracts with follow-up actions when The date you enter in this field lies within the selection period you define for the worklist The contract fulfills the other selection criteria you define for the worklist. You reach the selection screen for the worklist for contracts with follow-up actions by choosing Outline agreements -> Contracts -> Subsequent functions -> Follow-up actions.
    
    Parameters:
    
    slsContractFollowUpActionDate - Enter the date on which you want the follow-up action for the contract to be performed.
  - field
```
public static <T> SalesContractItemField<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.
  - fetchPartner
```
public List<SalesContractItemPartner> fetchPartner()
                                            throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesContractItemPartner 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 SalesContractItemPartner 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<SalesContractItemPartner> getPartnerOrFetch()
                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesContractItemPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesContractItem 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 SalesContractItemPartner 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<SalesContractItemPartner>> getPartnerOrNull()
```
    Retrieval of associated SalesContractItemPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property for an entity SalesContractItem 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 SalesContractItemPartner entities. If not, a null value state is returned.
  - setPartner
```
public void setPartner(@NonNull
                       List<SalesContractItemPartner> value)
```
    Overwrites the list of associated SalesContractItemPartner entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesContractItem 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 SalesContractItemPartner entities.
  - addPartner
```
public void addPartner(SalesContractItemPartner... entity)
```
    Adds elements to the list of associated SalesContractItemPartner entities. This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried SalesContractItem 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 SalesContractItemPartner entities.
  - fetchPricingElement
```
public List<SalesContractItemPrcgElmnt> fetchPricingElement()
                                                     throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesContractItemPrcgElmnt 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 SalesContractItemPrcgElmnt 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<SalesContractItemPrcgElmnt> getPricingElementOrFetch()
                                                          throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesContractItemPrcgElmnt entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesContractItem 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 SalesContractItemPrcgElmnt 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<SalesContractItemPrcgElmnt>> getPricingElementOrNull()
```
    Retrieval of associated SalesContractItemPrcgElmnt entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property for an entity SalesContractItem 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 SalesContractItemPrcgElmnt entities. If not, a null value state is returned.
  - setPricingElement
```
public void setPricingElement(@NonNull
                              List<SalesContractItemPrcgElmnt> value)
```
    Overwrites the list of associated SalesContractItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesContractItem 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 SalesContractItemPrcgElmnt entities.
  - addPricingElement
```
public void addPricingElement(SalesContractItemPrcgElmnt... entity)
```
    Adds elements to the list of associated SalesContractItemPrcgElmnt entities. This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried SalesContractItem 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 SalesContractItemPrcgElmnt entities.
  - fetchSalesContract
```
public SalesContract fetchSalesContract()
                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesContract entity (one to one) associated with this entity. This corresponds to the OData navigation property to_SalesContract.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated SalesContract 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.
  - getSalesContractOrFetch
```
public SalesContract getSalesContractOrFetch()
                                      throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesContract entity (one to one). This corresponds to the OData navigation property to_SalesContract.
    If the navigation property to_SalesContract of a queried SalesContractItem 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 SalesContract 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.
  - getSalesContractOrNull
```
public com.google.common.base.Optional<SalesContract> getSalesContractOrNull()
```
    Retrieval of associated SalesContract entity (one to one). This corresponds to the OData navigation property to_SalesContract.
    If the navigation property for an entity SalesContractItem 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_SalesContract is already loaded, the result will contain the SalesContract entity. If not, a null value state is returned.
  - setSalesContract
```
public void setSalesContract(SalesContract value)
```
    Overwrites the associated SalesContract entity for the loaded navigation property to_SalesContract.
    
    Parameters:
    
    value - New SalesContract entity.
  - builder
```
public static SalesContractItem.SalesContractItemBuilder builder()
```
  - getSalesContract
```
@Nullable
public String getSalesContract()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesContract
    
    Returns:
    
    Sales Contract
  - getSalesContractItem
```
@Nullable
public String getSalesContractItem()
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesContractItem
    
    Returns:
    
    Sales Contract Item
  - getHigherLevelItem
```
@Nullable
public String getHigherLevelItem()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: HigherLevelItem
    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.
  - getSalesContractItemCategory
```
@Nullable
public String getSalesContractItemCategory()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesContractItemCategory
    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.
  - getSalesContractItemText
```
@Nullable
public String getSalesContractItemText()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: SalesContractItemText
    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
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    
    Returns:
    
    Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).
  - getMaterial
```
@Nullable
public String getMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getMaterialByCustomer
```
@Nullable
public String getMaterialByCustomer()
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: MaterialByCustomer
    If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such as Minimum delivery quantity Partial delivery conditions Enter a value from an existing customer-material info record.
    
    Returns:
    
    Uniquely identifies the material from the customer's point of view.
  - getPricingDate
```
@Nullable
public Calendar getPricingDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PricingDate
    You can use the pricing date as a selection criterion when you process billing documents collectively. The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue. Determining the Proposal In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date. In the billing document: The billing date is proposed as the pricing date.
    
    Returns:
    
    The date that determines date-related pricing elements, such as conditions and foreign exchange rate.
  - getRequestedQuantity
```
@Nullable
public BigDecimal getRequestedQuantity()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property name from the Odata EDM: RequestedQuantity
    
    Returns:
    
    Requested Quantity
  - getRequestedQuantityUnit
```
@Nullable
public String getRequestedQuantityUnit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: RequestedQuantityUnit
    
    Returns:
    
    Requested Quantity Unit
  - getItemGrossWeight
```
@Nullable
public BigDecimal getItemGrossWeight()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property name from the Odata EDM: ItemGrossWeight
    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
    Original property name from the Odata EDM: ItemNetWeight
    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
    Original property name from the Odata EDM: ItemWeightUnit
    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
    Original property name from the Odata EDM: ItemVolume
    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
    Original property name from the Odata EDM: ItemVolumeUnit
    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
    Original property name from the Odata EDM: TransactionCurrency
    The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
    
    Returns:
    
    The currency that applies to the document (for example, to a sales order or an invoice).
  - getNetAmount
```
@Nullable
public BigDecimal getNetAmount()
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: NetAmount
    
    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
    Original property name from the Odata EDM: MaterialGroup
    You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
    
    Returns:
    
    Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.
  - getBatch
```
@Nullable
public String getBatch()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Batch
    
    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
    Original property name from the Odata EDM: ProductionPlant
    
    Returns:
    
    Key that uniquely identifies a plant.
  - getStorageLocation
```
@Nullable
public String getStorageLocation()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: StorageLocation
    
    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
    Original property name from the Odata EDM: ShippingPoint
    You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During 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.
  - getIncotermsClassification
```
@Nullable
public String getIncotermsClassification()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully. If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Returns:
    
    Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - getIncotermsTransferLocation
```
@Nullable
public String getIncotermsTransferLocation()
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Returns:
    
    Additional information for the primary Incoterm.
  - getIncotermsLocation1
```
@Nullable
public String getIncotermsLocation1()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 1 EXW Ex Works Place of Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Returns:
    
    Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - getIncotermsLocation2
```
@Nullable
public String getIncotermsLocation2()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    No Version: This field is disabled Incoterm Version 2000 This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions. Incoterm Version 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
    
    Returns:
    
    Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:
  - getCustomerPaymentTerms
```
@Nullable
public String getCustomerPaymentTerms()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data can be entered in the field for the terms of payment key in various ways as you enter a business transaction: In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question. In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field. Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at: item level in sales orders header level in purchase orders and invoices Master records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Returns:
    
    Key for defining payment terms composed of cash discount percentages and payment periods.
  - getSalesDocumentRjcnReason
```
@Nullable
public String getSalesDocumentRjcnReason()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: SalesDocumentRjcnReason
    The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection: Inquiries and quotations: no further references by other documents Sales orders: no further delivery of items Contracts: no further creation of release orders Credit and debit memo requests: no further processing of credit or debit memos Enter one of the values predefined for your system. If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
    
    Returns:
    
    The reason for rejecting a quotation or a sales order.
  - getItemBillingBlockReason
```
@Nullable
public String getItemBillingBlockReason()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ItemBillingBlockReason
    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.
  - getSDProcessStatus
```
@Nullable
public String getSDProcessStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SDProcessStatus
    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.
  - getOutlineAgreementTargetAmount
```
@Nullable
public BigDecimal getOutlineAgreementTargetAmount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: OutlineAgreementTargetAmount
    The target value represents the value of products or services that a customer has agreed to purchase or that a supplier has agreed to supply during the validity period of the outline agreement.
    
    Returns:
    
    The target value of an outline agreement (for example, a value contract). The value is expressed in the document currency.
  - getSalesContractValidityStartDate
```
@Nullable
public Calendar getSalesContractValidityStartDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesContractValidityStartDate
    The contract start date can be entered both at header and at item level. If the contract start date is only entered at header level, then it is valid for all items. The contract start date can be proposed automatically as a default from another data field on the basis of a date rule.
    
    Returns:
    
    Enter the contract start date.
  - getSalesContractValidityEndDate
```
@Nullable
public Calendar getSalesContractValidityEndDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesContractValidityEndDate
    
    Returns:
    
    Contract End Date
  - getNmbrOfSalesContractValdtyPerd
```
@Nullable
public String getNmbrOfSalesContractValdtyPerd()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: NmbrOfSalesContractValdtyPerd
    
    Returns:
    
    Validity Period of Contract
  - getSalesContractValidityPerdUnit
```
@Nullable
public String getSalesContractValidityPerdUnit()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SalesContractValidityPerdUnit
    
    Returns:
    
    Unit of Validity Period of Contract
  - getSalesContractValidityPerdCat
```
@Nullable
public String getSalesContractValidityPerdCat()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: SalesContractValidityPerdCat
    
    Returns:
    
    Enter a value here to indicate what kind of validity period the contract has (6 months, one year, and so on).
  - getSalesContractSignedDate
```
@Nullable
public Calendar getSalesContractSignedDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SalesContractSignedDate
    The date you enter can be used as a baseline date for determining other dates in the contract. You want the contract to become valid on the day it is signed by the customer. You enter a date rule for the contract start date which has the date on which the contract is signed as its baseline date. When you enter the date on which the contract was signed in the contract, the system automatically makes the appropriate entry in the contract start date field.
    
    Returns:
    
    Enter the date on which the customer signs the contract.
  - getSalesContractFollowUpAction
```
@Nullable
public String getSalesContractFollowUpAction()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesContractFollowUpAction
    Creating a contract Creating a quotation Creating a sales activity such as a telephone call Sending an internal electronic mail
    
    Returns:
    
    Enter the follow-up action which is to be taken when the contract ends. Follow-up actions are
  - getSlsContractFollowUpActionDate
```
@Nullable
public Calendar getSlsContractFollowUpActionDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: SlsContractFollowUpActionDate
    The contract will be included in the worklist for contracts with follow-up actions when The date you enter in this field lies within the selection period you define for the worklist The contract fulfills the other selection criteria you define for the worklist. You reach the selection screen for the worklist for contracts with follow-up actions by choosing Outline agreements -> Contracts -> Subsequent functions -> Follow-up actions.
    
    Returns:
    
    Enter the date on which you want the follow-up action for the contract to be performed.
  - 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.
  - 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<SalesContractItem>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<SalesContractItem>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<SalesContractItem>

Class SalesContractItem

Nested Class Summary

Field Summary

Constructor Summary

Method Summary

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

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

SALES_CONTRACT

SALES_CONTRACT_ITEM

HIGHER_LEVEL_ITEM

SALES_CONTRACT_ITEM_CATEGORY

SALES_CONTRACT_ITEM_TEXT

PURCHASE_ORDER_BY_CUSTOMER

MATERIAL

MATERIAL_BY_CUSTOMER

PRICING_DATE

REQUESTED_QUANTITY

REQUESTED_QUANTITY_UNIT

ITEM_GROSS_WEIGHT

ITEM_NET_WEIGHT

ITEM_WEIGHT_UNIT

ITEM_VOLUME

ITEM_VOLUME_UNIT

TRANSACTION_CURRENCY

NET_AMOUNT

MATERIAL_GROUP

BATCH

PRODUCTION_PLANT

STORAGE_LOCATION

SHIPPING_POINT

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

CUSTOMER_PAYMENT_TERMS

SALES_DOCUMENT_RJCN_REASON

ITEM_BILLING_BLOCK_REASON

SD_PROCESS_STATUS

OUTLINE_AGREEMENT_TARGET_AMOUNT

SALES_CONTRACT_VALIDITY_START_DATE

SALES_CONTRACT_VALIDITY_END_DATE

NMBR_OF_SALES_CONTRACT_VALDTY_PERD

SALES_CONTRACT_VALIDITY_PERD_UNIT

SALES_CONTRACT_VALIDITY_PERD_CAT

SALES_CONTRACT_SIGNED_DATE

SALES_CONTRACT_FOLLOW_UP_ACTION

SLS_CONTRACT_FOLLOW_UP_ACTION_DATE

TO_PARTNER

TO_PRICING_ELEMENT

TO_SALES_CONTRACT

Constructor Detail

SalesContractItem

SalesContractItem

Method Detail

getType

setSalesContract

setSalesContractItem

setHigherLevelItem

setSalesContractItemCategory

setSalesContractItemText

setPurchaseOrderByCustomer

setMaterial

setMaterialByCustomer

setPricingDate

setRequestedQuantity

setRequestedQuantityUnit

setItemGrossWeight

setItemNetWeight

setItemWeightUnit

setItemVolume

setItemVolumeUnit

setTransactionCurrency

setNetAmount

setMaterialGroup

setBatch

setProductionPlant

setStorageLocation