public static final class SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder extends Object
@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder salesOrder(SalesOrderSimulation value)
value
- The SalesOrderSimulation to build this SalesOrderScheduleLineSimln with.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder salesOrder(String value)
Original property name from the Odata EDM: SalesOrder
value
- The salesOrder to build this SalesOrderScheduleLineSimln with.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder salesOrderItem(SalesOrderItemSimulation value)
value
- The SalesOrderItemSimulation to build this SalesOrderScheduleLineSimln with.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder salesOrderItem(String value)
Original property name from the Odata EDM: SalesOrderItem
value
- The salesOrderItem to build this SalesOrderScheduleLineSimln with.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder scheduleLine(@Nullable String scheduleLine)
Original property name from the Odata EDM: ScheduleLine
When an item has more than one schedule line, the system automatically assigns a unique number to each line. The number is displayed in the details screens for schedule lines.The schedule line number serves internal purposes and does not, for example, determine the sequence of schedule lines in the overview screen. The schedule lines on the overview screen are sorted by date.
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder requestedDeliveryDate(@Nullable LocalDateTime requestedDeliveryDate)
Original property name from the Odata EDM: RequestedDeliveryDate
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder confirmedDeliveryDate(@Nullable LocalDateTime confirmedDeliveryDate)
Original property name from the Odata EDM: ConfirmedDeliveryDate
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder orderQuantityUnit(@Nullable String orderQuantityUnit)
Original property name from the Odata EDM: OrderQuantityUnit
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder orderQuantitySAPUnit(@Nullable String orderQuantitySAPUnit)
Original property name from the Odata EDM: OrderQuantitySAPUnit
For the order quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder orderQuantityISOUnit(@Nullable String orderQuantityISOUnit)
Original property name from the Odata EDM: OrderQuantityISOUnit
For the order quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder scheduleLineOrderQuantity(@Nullable BigDecimal scheduleLineOrderQuantity)
Original property name from the Odata EDM: ScheduleLineOrderQuantity
If you change the required order quantity in the schedule line, the system re-rounds the quantities, determines the rounded quantity, and re-runs the availability check based on the rounded quantity. The required order quantity remains as the orginal quantity (before rounding) in the schedule line.If the system does not round up the quantity, this means that the required order quantity matches the rounded quantity.
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder confdOrderQtyByMatlAvailCheck(@Nullable BigDecimal confdOrderQtyByMatlAvailCheck)
Original property name from the Odata EDM: ConfdOrderQtyByMatlAvailCheck
The confirmed quantity can differ from the order quantity (for example, insufficient stock is available to meet the customer's request). If the availability of inventory changes during delivery processing, the confirmed quantity can also differ from the delivered quantity that the customer actually receives.If you change the order quantity (for example, if you create new schedule lines for the item), the system updates the confirmed quantity (depending on availability).
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder openConfdDelivQtyInOrdQtyUnit(@Nullable BigDecimal openConfdDelivQtyInOrdQtyUnit)
Original property name from the Odata EDM: OpenConfdDelivQtyInOrdQtyUnit
this
.@Nonnull public SalesOrderScheduleLineSimln.SalesOrderScheduleLineSimlnBuilder correctedQtyInOrderQtyUnit(@Nullable BigDecimal correctedQtyInOrderQtyUnit)
Original property name from the Odata EDM: CorrectedQtyInOrderQtyUnit
The system rounds the quantity using the rounding profiles from the customer-material info record or the material master record. The profile can be switched on for each customer.If you change the rounded quantity, the system automatically performs an availability check and/or delivery scheduling and updates the confirmed quantity. The rounded quantity is cumulated in the total order quantity of the item. The required order quantity remains as the original quantity (before rounding) in the schedule line.If the system does not round the quantity, the rounded quantity of the required order quantity in the schedule line is valid.
this
.@Nonnull public SalesOrderScheduleLineSimln build()
Copyright © 2021 SAP SE. All rights reserved.