public class SalesOrderItem extends VdmEntity<SalesOrderItem>
Original entity name from the Odata EDM: A_SalesOrderItemType
Modifier and Type | Class and Description |
---|---|
static class |
SalesOrderItem.SalesOrderItemBuilder |
Modifier and Type | Field and Description |
---|---|
static SalesOrderItemSelectable |
ALL_FIELDS
Selector for all available fields of SalesOrderItem.
|
static SalesOrderItemField<String> |
BATCH
Use with available fluent helpers to apply the Batch field to query operations.
|
static SalesOrderItemField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static SalesOrderItemField<String> |
DELIVERY_GROUP
Use with available fluent helpers to apply the DeliveryGroup field to query operations.
|
static SalesOrderItemField<String> |
DELIVERY_PRIORITY
Use with available fluent helpers to apply the DeliveryPriority field to query operations.
|
static SalesOrderItemField<String> |
DELIVERY_STATUS
Use with available fluent helpers to apply the DeliveryStatus field to query operations.
|
static SalesOrderItemField<String> |
HIGHER_LEVEL_ITEM
Use with available fluent helpers to apply the HigherLevelItem field to query operations.
|
static SalesOrderItemField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static SalesOrderItemField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static SalesOrderItemField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static SalesOrderItemField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static SalesOrderItemField<String> |
ITEM_BILLING_BLOCK_REASON
Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
|
static SalesOrderItemField<BigDecimal> |
ITEM_GROSS_WEIGHT
Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
|
static SalesOrderItemField<BigDecimal> |
ITEM_NET_WEIGHT
Use with available fluent helpers to apply the ItemNetWeight field to query operations.
|
static SalesOrderItemField<BigDecimal> |
ITEM_VOLUME
Use with available fluent helpers to apply the ItemVolume field to query operations.
|
static SalesOrderItemField<String> |
ITEM_VOLUME_UNIT
Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
|
static SalesOrderItemField<String> |
ITEM_WEIGHT_UNIT
Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
|
static SalesOrderItemField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static SalesOrderItemField<String> |
MATERIAL_BY_CUSTOMER
Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
|
static SalesOrderItemField<String> |
MATERIAL_GROUP
Use with available fluent helpers to apply the MaterialGroup field to query operations.
|
static SalesOrderItemField<BigDecimal> |
NET_AMOUNT
Use with available fluent helpers to apply the NetAmount field to query operations.
|
static SalesOrderItemField<String> |
ORDER_RELATED_BILLING_STATUS
Use with available fluent helpers to apply the OrderRelatedBillingStatus field to query operations.
|
static SalesOrderItemField<LocalDateTime> |
PRICING_DATE
Use with available fluent helpers to apply the PricingDate field to query operations.
|
static SalesOrderItemField<String> |
PRODUCTION_PLANT
Use with available fluent helpers to apply the ProductionPlant field to query operations.
|
static SalesOrderItemField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static SalesOrderItemField<BigDecimal> |
REQUESTED_QUANTITY
Use with available fluent helpers to apply the RequestedQuantity field to query operations.
|
static SalesOrderItemField<String> |
REQUESTED_QUANTITY_UNIT
Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
|
static SalesOrderItemField<String> |
SALES_DOCUMENT_RJCN_REASON
Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
|
static SalesOrderItemField<String> |
SALES_ORDER
Use with available fluent helpers to apply the SalesOrder field to query operations.
|
static SalesOrderItemField<String> |
SALES_ORDER_ITEM
Use with available fluent helpers to apply the SalesOrderItem field to query operations.
|
static SalesOrderItemField<String> |
SALES_ORDER_ITEM_CATEGORY
Use with available fluent helpers to apply the SalesOrderItemCategory field to query operations.
|
static SalesOrderItemField<String> |
SALES_ORDER_ITEM_TEXT
Use with available fluent helpers to apply the SalesOrderItemText field to query operations.
|
static SalesOrderItemField<String> |
SD_PROCESS_STATUS
Use with available fluent helpers to apply the SDProcessStatus field to query operations.
|
static SalesOrderItemField<String> |
SHIPPING_POINT
Use with available fluent helpers to apply the ShippingPoint field to query operations.
|
static SalesOrderItemField<String> |
SHIPPING_TYPE
Use with available fluent helpers to apply the ShippingType field to query operations.
|
static SalesOrderItemField<String> |
STORAGE_LOCATION
Use with available fluent helpers to apply the StorageLocation field to query operations.
|
static SalesOrderItemLink<SalesOrderItemPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static SalesOrderItemLink<SalesOrderItemPrElement> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static SalesOrderItemLink<SalesOrder> |
TO_SALES_ORDER
Use with available fluent helpers to apply the to_SalesOrder navigation property to query operations.
|
static SalesOrderItemLink<SalesOrderScheduleLine> |
TO_SCHEDULE_LINE
Use with available fluent helpers to apply the to_ScheduleLine navigation property to query operations.
|
static SalesOrderItemField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SalesOrderItem() |
SalesOrderItem(String salesOrder,
String salesOrderItem,
String higherLevelItem,
String salesOrderItemCategory,
String salesOrderItemText,
String purchaseOrderByCustomer,
String material,
String materialByCustomer,
LocalDateTime 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 deliveryGroup,
String shippingPoint,
String shippingType,
String deliveryPriority,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String customerPaymentTerms,
String salesDocumentRjcnReason,
String itemBillingBlockReason,
String sDProcessStatus,
String deliveryStatus,
String orderRelatedBillingStatus,
ErpConfigContext erpConfigContext,
List<SalesOrderItemPartner> toPartner,
List<SalesOrderItemPrElement> toPricingElement,
SalesOrder toSalesOrder,
List<SalesOrderScheduleLine> toScheduleLine) |
Modifier and Type | Method and Description |
---|---|
void |
addPartner(SalesOrderItemPartner... entity)
Adds elements to the list of associated SalesOrderItemPartner entities.
|
void |
addPricingElement(SalesOrderItemPrElement... entity)
Adds elements to the list of associated SalesOrderItemPrElement entities.
|
void |
addScheduleLine(SalesOrderScheduleLine... entity)
Adds elements to the list of associated SalesOrderScheduleLine entities.
|
static SalesOrderItem.SalesOrderItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<SalesOrderItemPartner> |
fetchPartner()
Fetches the SalesOrderItemPartner entities (one to many) associated with this entity.
|
List<SalesOrderItemPrElement> |
fetchPricingElement()
Fetches the SalesOrderItemPrElement entities (one to many) associated with this entity.
|
SalesOrder |
fetchSalesOrder()
Fetches the SalesOrder entity (one to one) associated with this entity.
|
List<SalesOrderScheduleLine> |
fetchScheduleLine()
Fetches the SalesOrderScheduleLine entities (one to many) associated with this entity.
|
static <T> SalesOrderItemField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getBatch()
Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
String |
getDeliveryGroup()
Constraints: Not nullable, Maximum length: 3
|
String |
getDeliveryPriority()
Constraints: Not nullable, Maximum length: 2
|
String |
getDeliveryStatus()
Constraints: Not nullable, Maximum length: 1
|
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getHigherLevelItem()
Constraints: Not nullable, Maximum length: 6
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsLocation1()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsLocation2()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28
|
String |
getItemBillingBlockReason()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getItemGrossWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
BigDecimal |
getItemNetWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
BigDecimal |
getItemVolume()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getItemVolumeUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getItemWeightUnit()
Constraints: Not nullable, Maximum length: 3
|
protected Map<String,Object> |
getKey() |
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterialByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9
|
BigDecimal |
getNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getOrderRelatedBillingStatus()
Constraints: Not nullable, Maximum length: 1
|
Optional<List<SalesOrderItemPartner>> |
getPartnerIfPresent()
Retrieval of associated SalesOrderItemPartner entities (one to many).
|
List<SalesOrderItemPartner> |
getPartnerOrFetch()
Retrieval of associated SalesOrderItemPartner entities (one to many).
|
LocalDateTime |
getPricingDate()
Constraints: Not nullable, Precision: 0
|
Optional<List<SalesOrderItemPrElement>> |
getPricingElementIfPresent()
Retrieval of associated SalesOrderItemPrElement entities (one to many).
|
List<SalesOrderItemPrElement> |
getPricingElementOrFetch()
Retrieval of associated SalesOrderItemPrElement entities (one to many).
|
String |
getProductionPlant()
Constraints: Not nullable, Maximum length: 4
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
BigDecimal |
getRequestedQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getRequestedQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesDocumentRjcnReason()
Constraints: Not nullable, Maximum length: 2
|
String |
getSalesOrder()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
Optional<SalesOrder> |
getSalesOrderIfPresent()
Retrieval of associated SalesOrder entity (one to one).
|
String |
getSalesOrderItem()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getSalesOrderItemCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesOrderItemText()
Constraints: Not nullable, Maximum length: 40
|
SalesOrder |
getSalesOrderOrFetch()
Retrieval of associated SalesOrder entity (one to one).
|
Optional<List<SalesOrderScheduleLine>> |
getScheduleLineIfPresent()
Retrieval of associated SalesOrderScheduleLine entities (one to many).
|
List<SalesOrderScheduleLine> |
getScheduleLineOrFetch()
Retrieval of associated SalesOrderScheduleLine entities (one to many).
|
String |
getSDProcessStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getShippingPoint()
Constraints: Not nullable, Maximum length: 4
|
String |
getShippingType()
Constraints: Not nullable, Maximum length: 2
|
String |
getStorageLocation()
Constraints: Not nullable, Maximum length: 4
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<SalesOrderItem> |
getType() |
int |
hashCode() |
void |
setBatch(String batch)
Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setDeliveryGroup(String deliveryGroup)
Constraints: Not nullable, Maximum length: 3
|
void |
setDeliveryPriority(String deliveryPriority)
Constraints: Not nullable, Maximum length: 2
|
void |
setDeliveryStatus(String deliveryStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setHigherLevelItem(String higherLevelItem)
Constraints: Not nullable, Maximum length: 6
|
void |
setIncotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
void |
setIncotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
void |
setItemBillingBlockReason(String itemBillingBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setItemGrossWeight(BigDecimal itemGrossWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemNetWeight(BigDecimal itemNetWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemVolume(BigDecimal itemVolume)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemVolumeUnit(String itemVolumeUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setItemWeightUnit(String itemWeightUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40
|
void |
setMaterialByCustomer(String materialByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setMaterialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9
|
void |
setNetAmount(BigDecimal netAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setOrderRelatedBillingStatus(String orderRelatedBillingStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setPartner(List<SalesOrderItemPartner> value)
Overwrites the list of associated SalesOrderItemPartner entities for the loaded navigation property to_Partner.
|
void |
setPricingDate(LocalDateTime pricingDate)
Constraints: Not nullable, Precision: 0
|
void |
setPricingElement(List<SalesOrderItemPrElement> value)
Overwrites the list of associated SalesOrderItemPrElement entities for the loaded navigation property to_PricingElement.
|
void |
setProductionPlant(String productionPlant)
Constraints: Not nullable, Maximum length: 4
|
void |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setRequestedQuantity(BigDecimal requestedQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setRequestedQuantityUnit(String requestedQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesDocumentRjcnReason(String salesDocumentRjcnReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setSalesOrder(SalesOrder value)
Overwrites the associated SalesOrder entity for the loaded navigation property to_SalesOrder.
|
void |
setSalesOrder(String salesOrder)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSalesOrderItem(String salesOrderItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setSalesOrderItemCategory(String salesOrderItemCategory)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesOrderItemText(String salesOrderItemText)
Constraints: Not nullable, Maximum length: 40
|
void |
setScheduleLine(List<SalesOrderScheduleLine> value)
Overwrites the list of associated SalesOrderScheduleLine entities for the loaded navigation property to_ScheduleLine.
|
void |
setSDProcessStatus(String sDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setShippingPoint(String shippingPoint)
Constraints: Not nullable, Maximum length: 4
|
void |
setShippingType(String shippingType)
Constraints: Not nullable, Maximum length: 2
|
void |
setStorageLocation(String storageLocation)
Constraints: Not nullable, Maximum length: 4
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setServicePathForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final SalesOrderItemSelectable ALL_FIELDS
public static final SalesOrderItemField<String> SALES_ORDER
public static final SalesOrderItemField<String> SALES_ORDER_ITEM
public static final SalesOrderItemField<String> HIGHER_LEVEL_ITEM
public static final SalesOrderItemField<String> SALES_ORDER_ITEM_CATEGORY
public static final SalesOrderItemField<String> SALES_ORDER_ITEM_TEXT
public static final SalesOrderItemField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final SalesOrderItemField<String> MATERIAL
public static final SalesOrderItemField<String> MATERIAL_BY_CUSTOMER
public static final SalesOrderItemField<LocalDateTime> PRICING_DATE
public static final SalesOrderItemField<BigDecimal> REQUESTED_QUANTITY
public static final SalesOrderItemField<String> REQUESTED_QUANTITY_UNIT
public static final SalesOrderItemField<BigDecimal> ITEM_GROSS_WEIGHT
public static final SalesOrderItemField<BigDecimal> ITEM_NET_WEIGHT
public static final SalesOrderItemField<String> ITEM_WEIGHT_UNIT
public static final SalesOrderItemField<BigDecimal> ITEM_VOLUME
public static final SalesOrderItemField<String> ITEM_VOLUME_UNIT
public static final SalesOrderItemField<String> TRANSACTION_CURRENCY
public static final SalesOrderItemField<BigDecimal> NET_AMOUNT
public static final SalesOrderItemField<String> MATERIAL_GROUP
public static final SalesOrderItemField<String> BATCH
public static final SalesOrderItemField<String> PRODUCTION_PLANT
public static final SalesOrderItemField<String> STORAGE_LOCATION
public static final SalesOrderItemField<String> DELIVERY_GROUP
public static final SalesOrderItemField<String> SHIPPING_POINT
public static final SalesOrderItemField<String> SHIPPING_TYPE
public static final SalesOrderItemField<String> DELIVERY_PRIORITY
public static final SalesOrderItemField<String> INCOTERMS_CLASSIFICATION
public static final SalesOrderItemField<String> INCOTERMS_TRANSFER_LOCATION
public static final SalesOrderItemField<String> INCOTERMS_LOCATION1
public static final SalesOrderItemField<String> INCOTERMS_LOCATION2
public static final SalesOrderItemField<String> CUSTOMER_PAYMENT_TERMS
public static final SalesOrderItemField<String> SALES_DOCUMENT_RJCN_REASON
public static final SalesOrderItemField<String> ITEM_BILLING_BLOCK_REASON
public static final SalesOrderItemField<String> SD_PROCESS_STATUS
public static final SalesOrderItemField<String> DELIVERY_STATUS
public static final SalesOrderItemField<String> ORDER_RELATED_BILLING_STATUS
public static final SalesOrderItemLink<SalesOrderItemPartner> TO_PARTNER
public static final SalesOrderItemLink<SalesOrderItemPrElement> TO_PRICING_ELEMENT
public static final SalesOrderItemLink<SalesOrder> TO_SALES_ORDER
public static final SalesOrderItemLink<SalesOrderScheduleLine> TO_SCHEDULE_LINE
public SalesOrderItem()
public SalesOrderItem(@Nullable String salesOrder, @Nullable String salesOrderItem, @Nullable String higherLevelItem, @Nullable String salesOrderItemCategory, @Nullable String salesOrderItemText, @Nullable String purchaseOrderByCustomer, @Nullable String material, @Nullable String materialByCustomer, @Nullable LocalDateTime 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 deliveryGroup, @Nullable String shippingPoint, @Nullable String shippingType, @Nullable String deliveryPriority, @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 String deliveryStatus, @Nullable String orderRelatedBillingStatus, @Nullable ErpConfigContext erpConfigContext, List<SalesOrderItemPartner> toPartner, List<SalesOrderItemPrElement> toPricingElement, @Nullable SalesOrder toSalesOrder, List<SalesOrderScheduleLine> toScheduleLine)
public Class<SalesOrderItem> getType()
getType
in class VdmObject<SalesOrderItem>
public void setSalesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
salesOrder
- Sales Orderpublic void setSalesOrderItem(@Nullable String salesOrderItem)
Original property name from the Odata EDM: SalesOrderItem
salesOrderItem
- Sales Order Itempublic void setHigherLevelItem(@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.
higherLevelItem
- The number of the higher-level item to which this item belongs in a hierarchy.public void setSalesOrderItemCategory(@Nullable String salesOrderItemCategory)
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.
salesOrderItemCategory
- 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.public void setSalesOrderItemText(@Nullable String salesOrderItemText)
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.
salesOrderItemText
- A short description of the item.public void setPurchaseOrderByCustomer(@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).
purchaseOrderByCustomer
- Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).public void setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setMaterialByCustomer(@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.
materialByCustomer
- Uniquely identifies the material from the customer's point of view.public void setPricingDate(@Nullable LocalDateTime pricingDate)
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.
pricingDate
- The date that determines date-related pricing elements, such as conditions and foreign exchange rate.public void setRequestedQuantity(@Nullable BigDecimal requestedQuantity)
Original property name from the Odata EDM: RequestedQuantity
requestedQuantity
- Requested Quantitypublic void setRequestedQuantityUnit(@Nullable String requestedQuantityUnit)
Original property name from the Odata EDM: RequestedQuantityUnit
requestedQuantityUnit
- Requested Quantity Unitpublic void setItemGrossWeight(@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.
itemGrossWeight
- The total gross weight of the item. The gross weight represents the net weight plus the weight of packaging.public void setItemNetWeight(@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.
itemNetWeight
- The total net weight for the item. The net weight represents the gross weight less the weight of packaging.public void setItemWeightUnit(@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.
itemWeightUnit
- Unit referring to the gross weight or net weight of the material.public void setItemVolume(@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.
itemVolume
- The total volume for the item.public void setItemVolumeUnit(@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.
itemVolumeUnit
- Unit referring to the volume of the material.public void setTransactionCurrency(@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.
transactionCurrency
- The currency that applies to the document (for example, to a sales order or an invoice).public void setNetAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
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.public void setMaterialGroup(@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
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.public void setBatch(@Nullable String batch)
Original property name from the Odata EDM: Batch
batch
- Assigns a material that is manufactured in batches or production lots to a specific batch.public void setProductionPlant(@Nullable String productionPlant)
Original property name from the Odata EDM: ProductionPlant
productionPlant
- Key that uniquely identifies a plant.public void setStorageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
storageLocation
- Number of the storage location in which the material is stored. A plant may contain one or more storage locations.public void setDeliveryGroup(@Nullable String deliveryGroup)
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.
deliveryGroup
- A combination of items that should be delivered together.public void setShippingPoint(@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.
shippingPoint
- The physical location (for example, a warehouse or collection of loading ramps) from which you ship the item.public void setShippingType(@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
shippingType
- Shipping type (for example, by road or rail) that has been selected for the transportation of the goods for the shipment legs.public void setDeliveryPriority(@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.
deliveryPriority
- The delivery priority assigned to an item.public void setIncotermsClassification(@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.
incotermsClassification
- Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).public void setIncotermsTransferLocation(@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").
incotermsTransferLocation
- Additional information for the primary Incoterm.public void setIncotermsLocation1(@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.
incotermsLocation1
- Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:public void setIncotermsLocation2(@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
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:public void setCustomerPaymentTerms(@Nullable String customerPaymentTerms)
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.
customerPaymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setSalesDocumentRjcnReason(@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.
salesDocumentRjcnReason
- The reason for rejecting a quotation or a sales order.public void setItemBillingBlockReason(@Nullable String itemBillingBlockReason)
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.
itemBillingBlockReason
- Indicates if the item is blocked for billing.public void setSDProcessStatus(@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.
sDProcessStatus
- Displays the overall processing status of the item.public void setDeliveryStatus(@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.
deliveryStatus
- Displays the delivery status of the item.public void setOrderRelatedBillingStatus(@Nullable String orderRelatedBillingStatus)
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.
orderRelatedBillingStatus
- The order-related billing status shows to what extent an item has been processed for billing.protected String getEntityCollection()
getEntityCollection
in class VdmEntity<SalesOrderItem>
protected Map<String,Object> getKey()
getKey
in class VdmObject<SalesOrderItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SalesOrderItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SalesOrderItem>
@Nonnull public static <T> SalesOrderItemField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
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.@Nonnull public static <T,DomainT> SalesOrderItemField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SalesOrderItem>
public List<SalesOrderItemPartner> fetchPartner() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
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.public List<SalesOrderItemPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried SalesOrderItem 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.
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.public Optional<List<SalesOrderItemPartner>> getPartnerIfPresent()
If the navigation property for an entity SalesOrderItem has not been resolved yet, this method will not query further information. Instead its Optional
result state will be empty
.
Optional
with result state empty
is returned.public void setPartner(@Nonnull List<SalesOrderItemPartner> value)
If the navigation property to_Partner of a queried SalesOrderItem 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.
value
- List of SalesOrderItemPartner entities.public void addPartner(SalesOrderItemPartner... entity)
If the navigation property to_Partner of a queried SalesOrderItem 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.
entity
- Array of SalesOrderItemPartner entities.public List<SalesOrderItemPrElement> fetchPricingElement() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
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.public List<SalesOrderItemPrElement> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried SalesOrderItem 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.
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.public Optional<List<SalesOrderItemPrElement>> getPricingElementIfPresent()
If the navigation property for an entity SalesOrderItem has not been resolved yet, this method will not query further information. Instead its Optional
result state will be empty
.
Optional
with result state empty
is returned.public void setPricingElement(@Nonnull List<SalesOrderItemPrElement> value)
If the navigation property to_PricingElement of a queried SalesOrderItem 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.
value
- List of SalesOrderItemPrElement entities.public void addPricingElement(SalesOrderItemPrElement... entity)
If the navigation property to_PricingElement of a queried SalesOrderItem 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.
entity
- Array of SalesOrderItemPrElement entities.public SalesOrder fetchSalesOrder() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
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.public SalesOrder getSalesOrderOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SalesOrder of a queried SalesOrderItem 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.
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.public Optional<SalesOrder> getSalesOrderIfPresent()
If the navigation property for an entity SalesOrderItem has not been resolved yet, this method will not query further information. Instead its Optional
result state will be empty
.
Optional
with result state empty
is returned.public void setSalesOrder(SalesOrder value)
value
- New SalesOrder entity.public List<SalesOrderScheduleLine> fetchScheduleLine() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
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.public List<SalesOrderScheduleLine> getScheduleLineOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_ScheduleLine of a queried SalesOrderItem 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.
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.public Optional<List<SalesOrderScheduleLine>> getScheduleLineIfPresent()
If the navigation property for an entity SalesOrderItem has not been resolved yet, this method will not query further information. Instead its Optional
result state will be empty
.
Optional
with result state empty
is returned.public void setScheduleLine(@Nonnull List<SalesOrderScheduleLine> value)
If the navigation property to_ScheduleLine of a queried SalesOrderItem 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.
value
- List of SalesOrderScheduleLine entities.public void addScheduleLine(SalesOrderScheduleLine... entity)
If the navigation property to_ScheduleLine of a queried SalesOrderItem 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.
entity
- Array of SalesOrderScheduleLine entities.public static SalesOrderItem.SalesOrderItemBuilder builder()
@Nullable public String getSalesOrder()
Original property name from the Odata EDM: SalesOrder
@Nullable public String getSalesOrderItem()
Original property name from the Odata EDM: SalesOrderItem
@Nullable public String getHigherLevelItem()
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.
@Nullable public String getSalesOrderItemCategory()
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.
@Nullable public String getSalesOrderItemText()
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.
@Nullable public String getPurchaseOrderByCustomer()
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).
@Nullable public String getMaterial()
Original property name from the Odata EDM: Material
@Nullable public String getMaterialByCustomer()
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.
@Nullable public LocalDateTime getPricingDate()
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.
@Nullable public BigDecimal getRequestedQuantity()
Original property name from the Odata EDM: RequestedQuantity
@Nullable public String getRequestedQuantityUnit()
Original property name from the Odata EDM: RequestedQuantityUnit
@Nullable public BigDecimal getItemGrossWeight()
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.
@Nullable public BigDecimal getItemNetWeight()
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.
@Nullable public String getItemWeightUnit()
Original property name from the Odata EDM: ItemWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
@Nullable public BigDecimal getItemVolume()
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.
@Nullable public String getItemVolumeUnit()
Original property name from the Odata EDM: ItemVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
@Nullable public String getTransactionCurrency()
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.
@Nullable public BigDecimal getNetAmount()
Original property name from the Odata EDM: NetAmount
@Nullable public String getMaterialGroup()
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
@Nullable public String getBatch()
Original property name from the Odata EDM: Batch
@Nullable public String getProductionPlant()
Original property name from the Odata EDM: ProductionPlant
@Nullable public String getStorageLocation()
Original property name from the Odata EDM: StorageLocation
@Nullable public String getDeliveryGroup()
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.
@Nullable public String getShippingPoint()
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.
@Nullable public String getShippingType()
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
@Nullable public String getDeliveryPriority()
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.
@Nullable public String getIncotermsClassification()
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.
@Nullable public String getIncotermsTransferLocation()
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").
@Nullable public String getIncotermsLocation1()
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.
@Nullable public String getIncotermsLocation2()
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
@Nullable public String getCustomerPaymentTerms()
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.
@Nullable public String getSalesDocumentRjcnReason()
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.
@Nullable public String getItemBillingBlockReason()
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.
@Nullable public String getSDProcessStatus()
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.
@Nullable public String getDeliveryStatus()
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.
@Nullable public String getOrderRelatedBillingStatus()
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.
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<SalesOrderItem>
erpConfigContext
- public String toString()
toString
in class VdmObject<SalesOrderItem>
public boolean equals(Object o)
equals
in class VdmObject<SalesOrderItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<SalesOrderItem>
public int hashCode()
hashCode
in class VdmObject<SalesOrderItem>
Copyright © 2018 SAP SE. All rights reserved.