public static final class SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder extends Object
@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder partner(SlsOrdWthoutChrgItmPartner... value)
value - The SlsOrdWthoutChrgItmPartners to build this SalesOrderWithoutChargeItem with.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder salesOrderWithoutCharge(SalesOrderWithoutCharge value)
value - The SalesOrderWithoutCharge to build this SalesOrderWithoutChargeItem with.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder salesOrderWithoutCharge(String value)
Original property name from the Odata EDM: SalesOrderWithoutCharge
value - The salesOrderWithoutCharge to build this SalesOrderWithoutChargeItem with.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder scheduleLine(SlsOrdWthoutChrgSchedLine... value)
value - The SlsOrdWthoutChrgSchedLines to build this SalesOrderWithoutChargeItem with.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder salesOrderWithoutChargeItem(@Nullable String salesOrderWithoutChargeItem)
Original property name from the Odata EDM: SalesOrderWithoutChargeItem
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder higherLevelItem(@Nullable String higherLevelItem)
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder slsOrdWthoutChrgItemCategory(@Nullable String slsOrdWthoutChrgItemCategory)
Original property name from the Odata EDM: SlsOrdWthoutChrgItemCategory
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.this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder salesOrderWthoutChrgItemText(@Nullable String salesOrderWthoutChrgItemText)
Original property name from the Odata EDM: SalesOrderWthoutChrgItemText
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder purchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
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).this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder materialByCustomer(@Nullable String materialByCustomer)
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder requestedQuantity(@Nullable BigDecimal requestedQuantity)
Original property name from the Odata EDM: RequestedQuantity
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder requestedQuantityUnit(@Nullable String requestedQuantityUnit)
Original property name from the Odata EDM: RequestedQuantityUnit
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder itemGrossWeight(@Nullable BigDecimal itemGrossWeight)
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.this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder itemNetWeight(@Nullable BigDecimal itemNetWeight)
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.this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder itemWeightUnit(@Nullable String itemWeightUnit)
Original property name from the Odata EDM: ItemWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder itemVolume(@Nullable BigDecimal itemVolume)
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder itemVolumeUnit(@Nullable String itemVolumeUnit)
Original property name from the Odata EDM: ItemVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder transactionCurrency(@Nullable String transactionCurrency)
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder netAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
included. The value is expressed in the document currency.this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder materialGroup(@Nullable String materialGroup)
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.this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder materialPricingGroup(@Nullable String materialPricingGroup)
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)
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder batch(@Nullable String batch)
Original property name from the Odata EDM: Batch
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
locations.this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder shippingPoint(@Nullable String shippingPoint)
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.this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder shippingType(@Nullable String shippingType)
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.this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder deliveryPriority(@Nullable String deliveryPriority)
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder deliveryDateTypeRule(@Nullable String deliveryDateTypeRule)
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 earliest requested delivery 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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder incotermsClassification(@Nullable String incotermsClassification)
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).this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder incotermsTransferLocation(@Nullable String incotermsTransferLocation)
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").
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder incotermsLocation1(@Nullable String incotermsLocation1)
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder incotermsLocation2(@Nullable String incotermsLocation2)
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:this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder salesDocumentRjcnReason(@Nullable String salesDocumentRjcnReason)
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder referenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder referenceSDDocumentItem(@Nullable String referenceSDDocumentItem)
Original property name from the Odata EDM: ReferenceSDDocumentItem
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder sDProcessStatus(@Nullable String sDProcessStatus)
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.
this.@Nonnull public SalesOrderWithoutChargeItem.SalesOrderWithoutChargeItemBuilder deliveryStatus(@Nullable String deliveryStatus)
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.
this.@Nonnull public SalesOrderWithoutChargeItem build()
Copyright © 2020 SAP SE. All rights reserved.