SalesOrderItem.SalesOrderItemBuilder (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.salesorder.SalesOrderItem.SalesOrderItemBuilder

Enclosing class:

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

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`SalesOrderItem.SalesOrderItemBuilder`	`batch(String batch)` Constraints: Not nullable, Maximum length: 10
`SalesOrderItem`	`build()`
`SalesOrderItem.SalesOrderItemBuilder`	`customerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`SalesOrderItem.SalesOrderItemBuilder`	`deliveryDateTypeRule(String deliveryDateTypeRule)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`deliveryGroup(String deliveryGroup)` Constraints: Not nullable, Maximum length: 3
`SalesOrderItem.SalesOrderItemBuilder`	`deliveryPriority(String deliveryPriority)` Constraints: Not nullable, Maximum length: 2
`SalesOrderItem.SalesOrderItemBuilder`	`deliveryStatus(String deliveryStatus)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`higherLevelItem(String higherLevelItem)` Constraints: Not nullable, Maximum length: 6
`SalesOrderItem.SalesOrderItemBuilder`	`incotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3
`SalesOrderItem.SalesOrderItemBuilder`	`incotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70
`SalesOrderItem.SalesOrderItemBuilder`	`incotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70
`SalesOrderItem.SalesOrderItemBuilder`	`incotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28
`SalesOrderItem.SalesOrderItemBuilder`	`itemBillingBlockReason(String itemBillingBlockReason)` Constraints: Not nullable, Maximum length: 2
`SalesOrderItem.SalesOrderItemBuilder`	`itemGrossWeight(BigDecimal itemGrossWeight)` Constraints: Not nullable, Precision: 15, Scale: 3
`SalesOrderItem.SalesOrderItemBuilder`	`itemNetWeight(BigDecimal itemNetWeight)` Constraints: Not nullable, Precision: 15, Scale: 3
`SalesOrderItem.SalesOrderItemBuilder`	`itemVolume(BigDecimal itemVolume)` Constraints: Not nullable, Precision: 15, Scale: 3
`SalesOrderItem.SalesOrderItemBuilder`	`itemVolumeUnit(String itemVolumeUnit)` Constraints: Not nullable, Maximum length: 3
`SalesOrderItem.SalesOrderItemBuilder`	`itemWeightUnit(String itemWeightUnit)` Constraints: Not nullable, Maximum length: 3
`SalesOrderItem.SalesOrderItemBuilder`	`material(String material)` Constraints: Not nullable, Maximum length: 40
`SalesOrderItem.SalesOrderItemBuilder`	`materialByCustomer(String materialByCustomer)` Constraints: Not nullable, Maximum length: 35
`SalesOrderItem.SalesOrderItemBuilder`	`materialGroup(String materialGroup)` Constraints: Not nullable, Maximum length: 9
`SalesOrderItem.SalesOrderItemBuilder`	`materialPricingGroup(String materialPricingGroup)` Constraints: Not nullable, Maximum length: 2
`SalesOrderItem.SalesOrderItemBuilder`	`matlAccountAssignmentGroup(String matlAccountAssignmentGroup)` Constraints: Not nullable, Maximum length: 2
`SalesOrderItem.SalesOrderItemBuilder`	`netAmount(BigDecimal netAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`SalesOrderItem.SalesOrderItemBuilder`	`orderRelatedBillingStatus(String orderRelatedBillingStatus)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`partner(SalesOrderItemPartner... value)` Navigation property to_Partner for SalesOrderItem to multiple SalesOrderItemPartner.
`SalesOrderItem.SalesOrderItemBuilder`	`pricingDate(LocalDateTime pricingDate)` Constraints: Not nullable, Precision: 0
`SalesOrderItem.SalesOrderItemBuilder`	`pricingElement(SalesOrderItemPrElement... value)` Navigation property to_PricingElement for SalesOrderItem to multiple SalesOrderItemPrElement.
`SalesOrderItem.SalesOrderItemBuilder`	`productionPlant(String productionPlant)` Constraints: Not nullable, Maximum length: 4
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification1(String productTaxClassification1)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification2(String productTaxClassification2)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification3(String productTaxClassification3)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification4(String productTaxClassification4)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification5(String productTaxClassification5)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification6(String productTaxClassification6)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification7(String productTaxClassification7)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification8(String productTaxClassification8)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`productTaxClassification9(String productTaxClassification9)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`profitCenter(String profitCenter)` Constraints: Not nullable, Maximum length: 10
`SalesOrderItem.SalesOrderItemBuilder`	`purchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`SalesOrderItem.SalesOrderItemBuilder`	`referenceSDDocument(String referenceSDDocument)` Constraints: Not nullable, Maximum length: 10
`SalesOrderItem.SalesOrderItemBuilder`	`referenceSDDocumentItem(String referenceSDDocumentItem)` Constraints: Not nullable, Maximum length: 6
`SalesOrderItem.SalesOrderItemBuilder`	`requestedQuantity(BigDecimal requestedQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3
`SalesOrderItem.SalesOrderItemBuilder`	`requestedQuantityUnit(String requestedQuantityUnit)` Constraints: Not nullable, Maximum length: 3
`SalesOrderItem.SalesOrderItemBuilder`	`salesDocumentRjcnReason(String salesDocumentRjcnReason)` Constraints: Not nullable, Maximum length: 2
`SalesOrderItem.SalesOrderItemBuilder`	`salesOrder(SalesOrder value)` Navigation property to_SalesOrder for SalesOrderItem to single SalesOrder.
`SalesOrderItem.SalesOrderItemBuilder`	`salesOrder(String value)` (Key Field) Constraints: Not nullable, Maximum length: 10
`SalesOrderItem.SalesOrderItemBuilder`	`salesOrderItem(String salesOrderItem)` (Key Field) Constraints: Not nullable, Maximum length: 6
`SalesOrderItem.SalesOrderItemBuilder`	`salesOrderItemCategory(String salesOrderItemCategory)` Constraints: Not nullable, Maximum length: 4
`SalesOrderItem.SalesOrderItemBuilder`	`salesOrderItemText(String salesOrderItemText)` Constraints: Not nullable, Maximum length: 40
`SalesOrderItem.SalesOrderItemBuilder`	`scheduleLine(SalesOrderScheduleLine... value)` Navigation property to_ScheduleLine for SalesOrderItem to multiple SalesOrderScheduleLine.
`SalesOrderItem.SalesOrderItemBuilder`	`sDProcessStatus(String sDProcessStatus)` Constraints: Not nullable, Maximum length: 1
`SalesOrderItem.SalesOrderItemBuilder`	`shippingPoint(String shippingPoint)` Constraints: Not nullable, Maximum length: 4
`SalesOrderItem.SalesOrderItemBuilder`	`shippingType(String shippingType)` Constraints: Not nullable, Maximum length: 2
`SalesOrderItem.SalesOrderItemBuilder`	`storageLocation(String storageLocation)` Constraints: Not nullable, Maximum length: 4
`SalesOrderItem.SalesOrderItemBuilder`	`text(SalesOrderItemText... value)` Navigation property to_Text for SalesOrderItem to multiple SalesOrderItemText.
`String`	`toString()`
`SalesOrderItem.SalesOrderItemBuilder`	`transactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5
`SalesOrderItem.SalesOrderItemBuilder`	`wBSElement(String wBSElement)` Constraints: Not nullable, Maximum length: 24

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

- Method Detail
  - partner
```
@Nonnull
public SalesOrderItem.SalesOrderItemBuilder partner(SalesOrderItemPartner... value)
```
    Navigation property to_Partner for SalesOrderItem to multiple SalesOrderItemPartner.
    
    Parameters:
    
    value - The SalesOrderItemPartners to build this SalesOrderItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - pricingElement
```
@Nonnull
public SalesOrderItem.SalesOrderItemBuilder pricingElement(SalesOrderItemPrElement... value)
```
    Navigation property to_PricingElement for SalesOrderItem to multiple SalesOrderItemPrElement.
    
    Parameters:
    
    value - The SalesOrderItemPrElements to build this SalesOrderItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - salesOrder
```
@Nonnull
public SalesOrderItem.SalesOrderItemBuilder salesOrder(SalesOrder value)
```
    Navigation property to_SalesOrder for SalesOrderItem to single SalesOrder.
    
    Parameters:
    
    value - The SalesOrder to build this SalesOrderItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - salesOrder
```
@Nonnull
public SalesOrderItem.SalesOrderItemBuilder salesOrder(String value)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesOrder
    
    Parameters:
    
    value - The salesOrder to build this SalesOrderItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - scheduleLine
```
@Nonnull
public SalesOrderItem.SalesOrderItemBuilder scheduleLine(SalesOrderScheduleLine... value)
```
    Navigation property to_ScheduleLine for SalesOrderItem to multiple SalesOrderScheduleLine.
    
    Parameters:
    
    value - The SalesOrderScheduleLines to build this SalesOrderItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - text
```
@Nonnull
public SalesOrderItem.SalesOrderItemBuilder text(SalesOrderItemText... value)
```
    Navigation property to_Text for SalesOrderItem to multiple SalesOrderItemText.
    
    Parameters:
    
    value - The SalesOrderItemTexts to build this SalesOrderItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - salesOrderItem
```
public SalesOrderItem.SalesOrderItemBuilder salesOrderItem(@Nullable
                                                           String salesOrderItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesOrderItem
    
    Returns:
    
    this.
  - higherLevelItem
```
public SalesOrderItem.SalesOrderItemBuilder higherLevelItem(@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.
    
    Returns:
    
    this.
  - salesOrderItemCategory
```
public SalesOrderItem.SalesOrderItemBuilder salesOrderItemCategory(@Nullable
                                                                   String salesOrderItemCategory)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SalesOrderItemCategory
    
    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.
    and text items) and determines how the system processes the item.
    
    Returns:
    
    this.
  - salesOrderItemText
```
public SalesOrderItem.SalesOrderItemBuilder salesOrderItemText(@Nullable
                                                               String salesOrderItemText)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: SalesOrderItemText
    
    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:
    
    this.
  - purchaseOrderByCustomer
```
public SalesOrderItem.SalesOrderItemBuilder purchaseOrderByCustomer(@Nullable
                                                                    String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    order).
    
    Returns:
    
    this.
  - material
```
public SalesOrderItem.SalesOrderItemBuilder material(@Nullable
                                                     String material)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
    
    Returns:
    
    this.
  - materialByCustomer
```
public SalesOrderItem.SalesOrderItemBuilder materialByCustomer(@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 asMinimum delivery quantityPartial delivery conditionsEnter a value from an existing customer-material info record.
    
    Returns:
    
    this.
  - pricingDate
```
public SalesOrderItem.SalesOrderItemBuilder pricingDate(@Nullable
                                                        LocalDateTime pricingDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PricingDate
    
    You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
    
    Returns:
    
    this.
  - requestedQuantity
```
public SalesOrderItem.SalesOrderItemBuilder requestedQuantity(@Nullable
                                                              BigDecimal requestedQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property name from the Odata EDM: RequestedQuantity
    
    Returns:
    
    this.
  - requestedQuantityUnit
```
public SalesOrderItem.SalesOrderItemBuilder requestedQuantityUnit(@Nullable
                                                                  String requestedQuantityUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: RequestedQuantityUnit
    
    Returns:
    
    this.
  - itemGrossWeight
```
public SalesOrderItem.SalesOrderItemBuilder itemGrossWeight(@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.
    packaging.
    
    Returns:
    
    this.
  - itemNetWeight
```
public SalesOrderItem.SalesOrderItemBuilder itemNetWeight(@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.
    packaging.
    
    Returns:
    
    this.
  - itemWeightUnit
```
public SalesOrderItem.SalesOrderItemBuilder itemWeightUnit(@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.
    
    Returns:
    
    this.
  - itemVolume
```
public SalesOrderItem.SalesOrderItemBuilder itemVolume(@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.
    
    Returns:
    
    this.
  - itemVolumeUnit
```
public SalesOrderItem.SalesOrderItemBuilder itemVolumeUnit(@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.
    
    Returns:
    
    this.
  - transactionCurrency
```
public SalesOrderItem.SalesOrderItemBuilder transactionCurrency(@Nullable
                                                                String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: TransactionCurrency
    
    The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
    
    Returns:
    
    this.
  - netAmount
```
public SalesOrderItem.SalesOrderItemBuilder netAmount(@Nullable
                                                      BigDecimal netAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: NetAmount
    included. The value is expressed in the document currency.
    
    Returns:
    
    this.
  - materialGroup
```
public SalesOrderItem.SalesOrderItemBuilder materialGroup(@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 analysesSearch specifically for material master records via search helps
    them to a particular material group.
    
    Returns:
    
    this.
  - materialPricingGroup
```
public SalesOrderItem.SalesOrderItemBuilder materialPricingGroup(@Nullable
                                                                 String materialPricingGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: MaterialPricingGroup
    
    You can create condition records for a material price group using the following condition types:Material price group (for example, all non-food products)A combination of customer and material price groupA combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
    
    Returns:
    
    this.
  - batch
```
public SalesOrderItem.SalesOrderItemBuilder batch(@Nullable
                                                  String batch)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Batch
    
    Returns:
    
    this.
  - productionPlant
```
public SalesOrderItem.SalesOrderItemBuilder productionPlant(@Nullable
                                                            String productionPlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ProductionPlant
    
    Returns:
    
    this.
  - storageLocation
```
public SalesOrderItem.SalesOrderItemBuilder storageLocation(@Nullable
                                                            String storageLocation)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: StorageLocation
    locations.
    
    Returns:
    
    this.
  - deliveryGroup
```
public SalesOrderItem.SalesOrderItemBuilder deliveryGroup(@Nullable
                                                          String deliveryGroup)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: DeliveryGroup
    
    The system uses delivery groups to check the availability of items that should be delivered together. The delivery date of the latest schedule line in the delivery group is taken as the general date for the whole group.During sales order processing, you can enter a number (up to three digits) that identifies a delivery group. The number is freely definable.If necessary, the system adjusts requirements that have already been created and changes the material availability dates for individual items to the delivery date that it has determined for the group.If a typewriter is usually delivered with a case, you can define the two items as a delivery group.If an item has more than one schedule line with a confirmed quantity, then the system deletes all undelivered schedule lines up to the last one. The system automatically carries over the quantities from the deleted schedule lines into the last one. If necessary, the system changes the delivery date of the last schedule line to that of the delivery group.
    
    Returns:
    
    this.
  - shippingPoint
```
public SalesOrderItem.SalesOrderItemBuilder shippingPoint(@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 ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.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.
    item.
    
    Returns:
    
    this.
  - shippingType
```
public SalesOrderItem.SalesOrderItemBuilder shippingType(@Nullable
                                                         String shippingType)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingType
    
    During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
    for the shipment legs.
    
    Returns:
    
    this.
  - deliveryPriority
```
public SalesOrderItem.SalesOrderItemBuilder deliveryPriority(@Nullable
                                                             String deliveryPriority)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DeliveryPriority
    
    You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
    
    Returns:
    
    this.
  - deliveryDateTypeRule
```
public SalesOrderItem.SalesOrderItemBuilder deliveryDateTypeRule(@Nullable
                                                                 String deliveryDateTypeRule)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DeliveryDateTypeRule
    
    You can choose one of the following options:The goods should be delivered on the requested delivery date or later. Note that there is no guarantee that the goods will not be delivered earlier.The goods must be delivered exactly on the confirmed delivery date.The goods must be delivered by the confirmed delivery date (that is, on the date or earlier).You can set the delivery date rule on header level to set a default for any items that you create afterwards.In Transportation Management (TM), this field has the following implications:If you want the goods to be delivered on the requested delivery date or later, the delivery date/time is used as the requested pick-up date/time of the freight unit which contains the sales order item.If you want the goods to be delivered on the confirmed delivery date, the start of the delivery date is used as the earliest acceptable delivery date/time and the end of the delivery date as the latest acceptable delivery date/time of the freight unit which contains the sales order item.If you want the goods to be delivered by the confirmed delivery date, the end of the delivery date is used as the latest acceptable delivery date/time of the freight unit which contains the sales order item.Note: If you want to the goods to be delivered on or by the confirmed delivery date, the system ignores the rule for pick-up and delivery window and the condition for pick-up and delivery window determination which you have defined in the freight unit type for the delivery stop.
    
    Returns:
    
    this.
  - incotermsClassification
```
public SalesOrderItem.SalesOrderItemBuilder incotermsClassification(@Nullable
                                                                    String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    Commerce (ICC).
    
    Returns:
    
    this.
  - incotermsTransferLocation
```
public SalesOrderItem.SalesOrderItemBuilder incotermsTransferLocation(@Nullable
                                                                      String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Returns:
    
    this.
  - incotermsLocation1
```
public SalesOrderItem.SalesOrderItemBuilder incotermsLocation1(@Nullable
                                                               String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    
    1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Returns:
    
    this.
  - incotermsLocation2
```
public SalesOrderItem.SalesOrderItemBuilder incotermsLocation2(@Nullable
                                                               String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    customized appropriately). Note the following for the incoterms versions below:
    
    Returns:
    
    this.
  - productTaxClassification1
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification1(@Nullable
                                                                      String productTaxClassification1)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification1
    
    Returns:
    
    this.
  - productTaxClassification2
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification2(@Nullable
                                                                      String productTaxClassification2)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification2
    
    Returns:
    
    this.
  - productTaxClassification3
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification3(@Nullable
                                                                      String productTaxClassification3)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification3
    
    Returns:
    
    this.
  - productTaxClassification4
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification4(@Nullable
                                                                      String productTaxClassification4)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification4
    
    Returns:
    
    this.
  - productTaxClassification5
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification5(@Nullable
                                                                      String productTaxClassification5)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification5
    
    Returns:
    
    this.
  - productTaxClassification6
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification6(@Nullable
                                                                      String productTaxClassification6)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification6
    
    Returns:
    
    this.
  - productTaxClassification7
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification7(@Nullable
                                                                      String productTaxClassification7)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification7
    
    Returns:
    
    this.
  - productTaxClassification8
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification8(@Nullable
                                                                      String productTaxClassification8)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification8
    
    Returns:
    
    this.
  - productTaxClassification9
```
public SalesOrderItem.SalesOrderItemBuilder productTaxClassification9(@Nullable
                                                                      String productTaxClassification9)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ProductTaxClassification9
    
    Returns:
    
    this.
  - matlAccountAssignmentGroup
```
public SalesOrderItem.SalesOrderItemBuilder matlAccountAssignmentGroup(@Nullable
                                                                       String matlAccountAssignmentGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: MatlAccountAssignmentGroup
    
    Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
    
    Returns:
    
    this.
  - customerPaymentTerms
```
public SalesOrderItem.SalesOrderItemBuilder customerPaymentTerms(@Nullable
                                                                 String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Returns:
    
    this.
  - salesDocumentRjcnReason
```
public SalesOrderItem.SalesOrderItemBuilder salesDocumentRjcnReason(@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 documentsSales orders: no further delivery of itemsContracts: no further creation of release ordersCredit and debit memo requests: no further processing of credit or debit memosEnter one of the values predefined for your system.If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
    
    Returns:
    
    this.
  - itemBillingBlockReason
```
public SalesOrderItem.SalesOrderItemBuilder itemBillingBlockReason(@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.
    
    Returns:
    
    this.
  - wBSElement
```
public SalesOrderItem.SalesOrderItemBuilder wBSElement(@Nullable
                                                       String wBSElement)
```
    Constraints: Not nullable, Maximum length: 24
    Original property name from the Odata EDM: WBSElement
    
    Returns:
    
    this.
  - profitCenter
```
public SalesOrderItem.SalesOrderItemBuilder profitCenter(@Nullable
                                                         String profitCenter)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ProfitCenter
    
    Returns:
    
    this.
  - referenceSDDocument
```
public SalesOrderItem.SalesOrderItemBuilder referenceSDDocument(@Nullable
                                                                String referenceSDDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceSDDocument
    
    Returns:
    
    this.
  - referenceSDDocumentItem
```
public SalesOrderItem.SalesOrderItemBuilder referenceSDDocumentItem(@Nullable
                                                                    String referenceSDDocumentItem)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: ReferenceSDDocumentItem
    
    Returns:
    
    this.
  - sDProcessStatus
```
public SalesOrderItem.SalesOrderItemBuilder sDProcessStatus(@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.
    
    Returns:
    
    this.
  - deliveryStatus
```
public SalesOrderItem.SalesOrderItemBuilder deliveryStatus(@Nullable
                                                           String deliveryStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DeliveryStatus
    
    The status line tells you if the item is not yet delivered, is partly delivered, is completely delivered, or is not relevant for delivery.
    
    Returns:
    
    this.
  - orderRelatedBillingStatus
```
public SalesOrderItem.SalesOrderItemBuilder orderRelatedBillingStatus(@Nullable
                                                                      String orderRelatedBillingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OrderRelatedBillingStatus
    
    You determine whether an item is billed as an order-related or delivery-related item when you define item category defaults through the Customizing menus.Credit and debit memo items, for example, are billed as order-related items.
    
    Returns:
    
    this.
  - build
```
public SalesOrderItem build()
```
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class Object

Class SalesOrderItem.SalesOrderItemBuilder

Method Summary

Methods inherited from class java.lang.Object

Method Detail

partner

pricingElement

salesOrder

salesOrder

scheduleLine

text

salesOrderItem

higherLevelItem

salesOrderItemCategory

salesOrderItemText

purchaseOrderByCustomer

material

materialByCustomer

pricingDate

requestedQuantity

requestedQuantityUnit

itemGrossWeight

itemNetWeight

itemWeightUnit

itemVolume

itemVolumeUnit

transactionCurrency

netAmount

materialGroup

materialPricingGroup

batch

productionPlant

storageLocation

deliveryGroup

shippingPoint

shippingType

deliveryPriority

deliveryDateTypeRule

incotermsClassification

incotermsTransferLocation

incotermsLocation1

incotermsLocation2

productTaxClassification1

productTaxClassification2

productTaxClassification3

productTaxClassification4

productTaxClassification5

productTaxClassification6

productTaxClassification7

productTaxClassification8

productTaxClassification9

matlAccountAssignmentGroup

customerPaymentTerms

salesDocumentRjcnReason

itemBillingBlockReason

wBSElement

profitCenter

referenceSDDocument

referenceSDDocumentItem

sDProcessStatus

deliveryStatus

orderRelatedBillingStatus

build

toString