public static class ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder extends Object
public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder deliveryVersion(@Nullable String deliveryVersion)
Original property name from the Odata EDM: DeliveryVersion
public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder precedingDocument(@Nullable String precedingDocument)
Original property name from the Odata EDM: PrecedingDocument
quotation from which you created a sales order).public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder precedingDocumentCategory(@Nullable String precedingDocumentCategory)
Original property name from the Odata EDM: PrecedingDocumentCategory
public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder precedingDocumentItem(@Nullable String precedingDocumentItem)
Original property name from the Odata EDM: PrecedingDocumentItem
public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder subsequentdocument(@Nullable String subsequentdocument)
Original property name from the Odata EDM: Subsequentdocument
sales order that you create from a previous quotation).public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder quantityInBaseUnit(@Nullable BigDecimal quantityInBaseUnit)
Original property name from the Odata EDM: QuantityInBaseUnit
A sales order item has an order quantity of 100 pieces. You create two delivery notes against the order: the first for 20 pieces, the second for 80 pieces. In the first case, the referenced quantity is 20 pieces; in the second case, 80 pieces.
referenced quantity is expressed in basic stock units.public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder subsequentDocumentItem(@Nullable String subsequentDocumentItem)
Original property name from the Odata EDM: SubsequentDocumentItem
you created from a quotation).public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder sDFulfillmentCalculationRule(@Nullable String sDFulfillmentCalculationRule)
Original property name from the Odata EDM: SDFulfillmentCalculationRule
The system uses this indicator to determine how the quantity in the source document is affected. For example, if youCreate a quotation item for 100 pieces,Copy the quotation into a sales order, andCreate a sales order item for 80 pieces,the copying has a positive effect on the quotation. In effect, you have added 80 pieces to the quotation quantity that is now considered complete. 20 pieces in the quotation remain to be completed.If you do not make an entry in this field, or set indicator 0, the source document is not blocked, which allows you to create several target documents at once (for example, when using EDI and frequent contract releases).While the source document (such as quotation or quantity contract) is being processed, it is blocked. For instance, if you are working on a quantity contract, no one can create a release order for that contract.In sales documents, for example, you can expect the following results:Quotation -> Sales order: positiveContract -> Return: negativeSales order -> Sales order: no effectIn billing documents, for example, you can expect the following results:Delivery -> Invoice: positiveDelivery -> Cancellation: negativeDelivery -> Pro-forma invoice: no effect
positive effect, or no effect at all on the quantity still to be completed in the source document.public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder subsequentDocumentCategory(@Nullable String subsequentDocumentCategory)
Original property name from the Odata EDM: SubsequentDocumentCategory
a delivery note that has been created from a sales order).public ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder transferOrderInWrhsMgmtIsConfd(@Nullable Boolean transferOrderInWrhsMgmtIsConfd)
Original property name from the Odata EDM: TransferOrderInWrhsMgmtIsConfd
public ReturnsDeliveryDocFlow build()
Copyright © 2019 SAP SE. All rights reserved.