public class SalesSchedgAgrmtItem extends VdmEntity<SalesSchedgAgrmtItem>
Original entity name from the Odata EDM: A_SalesSchedgAgrmtItemType
Modifier and Type | Class and Description |
---|---|
static class |
SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder
Helper class to allow for fluent creation of SalesSchedgAgrmtItem instances.
|
Modifier and Type | Field and Description |
---|---|
static SalesSchedgAgrmtItemSelectable |
ALL_FIELDS
Selector for all available fields of SalesSchedgAgrmtItem.
|
static SalesSchedgAgrmtItemField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
DELIVERY_PRIORITY
Use with available fluent helpers to apply the DeliveryPriority field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
DELIVERY_STATUS
Use with available fluent helpers to apply the DeliveryStatus field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
ITEM_BILLING_BLOCK_REASON
Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
ITEM_BILLING_INCOMPLETION_STATUS
Use with available fluent helpers to apply the ItemBillingIncompletionStatus field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
ITEM_DELIVERY_INCOMPLETION_STATUS
Use with available fluent helpers to apply the ItemDeliveryIncompletionStatus field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
ITEM_GENERAL_INCOMPLETION_STATUS
Use with available fluent helpers to apply the ItemGeneralIncompletionStatus field to query operations.
|
static SalesSchedgAgrmtItemField<LocalDateTime> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
MATERIAL_BY_CUSTOMER
Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
MATERIAL_GROUP
Use with available fluent helpers to apply the MaterialGroup field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
MATERIAL_PRICING_GROUP
Use with available fluent helpers to apply the MaterialPricingGroup field to query operations.
|
static SalesSchedgAgrmtItemField<BigDecimal> |
NET_AMOUNT
Use with available fluent helpers to apply the NetAmount field to query operations.
|
static SalesSchedgAgrmtItemField<BigDecimal> |
NET_PRICE_AMOUNT
Use with available fluent helpers to apply the NetPriceAmount field to query operations.
|
static SalesSchedgAgrmtItemField<BigDecimal> |
NET_PRICE_QUANTITY
Use with available fluent helpers to apply the NetPriceQuantity field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
NET_PRICE_QUANTITY_UNIT
Use with available fluent helpers to apply the NetPriceQuantityUnit field to query operations.
|
static SalesSchedgAgrmtItemField<BigDecimal> |
ORDER_QUANTITY
Use with available fluent helpers to apply the OrderQuantity field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
ORDER_QUANTITY_UNIT
Use with available fluent helpers to apply the OrderQuantityUnit field to query operations.
|
static SalesSchedgAgrmtItemField<BigDecimal> |
ORDER_TO_BASE_QUANTITY_DNMNTR
Use with available fluent helpers to apply the OrderToBaseQuantityDnmntr field to query operations.
|
static SalesSchedgAgrmtItemField<BigDecimal> |
ORDER_TO_BASE_QUANTITY_NMRTR
Use with available fluent helpers to apply the OrderToBaseQuantityNmrtr field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
ORIGINALLY_REQUESTED_MATERIAL
Use with available fluent helpers to apply the OriginallyRequestedMaterial field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
PLNG_DELIV_SCHED_INSTRN
Use with available fluent helpers to apply the PlngDelivSchedInstrn field to query operations.
|
static SalesSchedgAgrmtItemField<LocalDateTime> |
PRICING_DATE
Use with available fluent helpers to apply the PricingDate field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
PRODUCTION_PLANT
Use with available fluent helpers to apply the ProductionPlant field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
SALES_DOCUMENT_RJCN_REASON
Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
SALES_SCHEDG_AGRMT_ITEM_CATEGORY
Use with available fluent helpers to apply the SalesSchedgAgrmtItemCategory field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
SALES_SCHEDG_AGRMT_ITEM_TEXT
Use with available fluent helpers to apply the SalesSchedgAgrmtItemText field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
SALES_SCHEDULING_AGREEMENT
Use with available fluent helpers to apply the SalesSchedulingAgreement field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
SALES_SCHEDULING_AGREEMENT_ITEM
Use with available fluent helpers to apply the SalesSchedulingAgreementItem field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
SD_PROCESS_STATUS
Use with available fluent helpers to apply the SDProcessStatus field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
SHIPPING_POINT
Use with available fluent helpers to apply the ShippingPoint field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
SHIPPING_TYPE
Use with available fluent helpers to apply the ShippingType field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
STORAGE_LOCATION
Use with available fluent helpers to apply the StorageLocation field to query operations.
|
static SalesSchedgAgrmtItemField<BigDecimal> |
TARGET_QUANTITY
Use with available fluent helpers to apply the TargetQuantity field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
TARGET_QUANTITY_UNIT
Use with available fluent helpers to apply the TargetQuantityUnit field to query operations.
|
static SalesSchedgAgrmtItemLink<SalesSchedgAgrmtItemPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static SalesSchedgAgrmtItemLink<SalesSchedgAgrmtItmPrcgElmnt> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static SalesSchedgAgrmtItemOneToOneLink<SalesSchedgAgrmt> |
TO_SALES_SCHEDG_AGRMT
Use with available fluent helpers to apply the to_SalesSchedgAgrmt navigation property to query
operations.
|
static SalesSchedgAgrmtItemLink<SalesSchedgAgrmtDelivSched> |
TO_SALES_SCHEDG_AGRMT_DELIV_SCHED
Use with available fluent helpers to apply the to_SalesSchedgAgrmtDelivSched navigation property to query
operations.
|
static SalesSchedgAgrmtItemLink<SalesSchedgAgrmtItemText> |
TO_TEXT
Use with available fluent helpers to apply the to_Text navigation property to query operations.
|
static SalesSchedgAgrmtItemField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
static SalesSchedgAgrmtItemField<String> |
UNDERLYING_PURCHASE_ORDER_ITEM
Use with available fluent helpers to apply the UnderlyingPurchaseOrderItem field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SalesSchedgAgrmtItem() |
SalesSchedgAgrmtItem(String salesSchedulingAgreement,
String salesSchedulingAgreementItem,
String salesSchedgAgrmtItemCategory,
LocalDateTime lastChangeDate,
String material,
String originallyRequestedMaterial,
String materialByCustomer,
String materialGroup,
String materialPricingGroup,
String productionPlant,
String storageLocation,
String plngDelivSchedInstrn,
String salesSchedgAgrmtItemText,
String purchaseOrderByCustomer,
String underlyingPurchaseOrderItem,
BigDecimal orderQuantity,
BigDecimal orderToBaseQuantityDnmntr,
BigDecimal orderToBaseQuantityNmrtr,
String orderQuantityUnit,
BigDecimal targetQuantity,
String targetQuantityUnit,
String salesDocumentRjcnReason,
BigDecimal netAmount,
BigDecimal netPriceAmount,
BigDecimal netPriceQuantity,
String netPriceQuantityUnit,
String transactionCurrency,
LocalDateTime pricingDate,
String shippingPoint,
String shippingType,
String deliveryPriority,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String customerPaymentTerms,
String itemBillingBlockReason,
String sDProcessStatus,
String deliveryStatus,
String itemGeneralIncompletionStatus,
String itemBillingIncompletionStatus,
String itemDeliveryIncompletionStatus,
List<SalesSchedgAgrmtItemPartner> toPartner,
List<SalesSchedgAgrmtItmPrcgElmnt> toPricingElement,
SalesSchedgAgrmt toSalesSchedgAgrmt,
List<SalesSchedgAgrmtDelivSched> toSalesSchedgAgrmtDelivSched,
List<SalesSchedgAgrmtItemText> toText) |
Modifier and Type | Method and Description |
---|---|
void |
addPartner(SalesSchedgAgrmtItemPartner... entity)
Adds elements to the list of associated SalesSchedgAgrmtItemPartner entities.
|
void |
addPricingElement(SalesSchedgAgrmtItmPrcgElmnt... entity)
Adds elements to the list of associated SalesSchedgAgrmtItmPrcgElmnt entities.
|
void |
addSalesSchedgAgrmtDelivSched(SalesSchedgAgrmtDelivSched... entity)
Adds elements to the list of associated SalesSchedgAgrmtDelivSched entities.
|
void |
addText(SalesSchedgAgrmtItemText... entity)
Adds elements to the list of associated SalesSchedgAgrmtItemText entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<SalesSchedgAgrmtItemPartner> |
fetchPartner()
Fetches the SalesSchedgAgrmtItemPartner entities (one to many) associated with this entity.
|
List<SalesSchedgAgrmtItmPrcgElmnt> |
fetchPricingElement()
Fetches the SalesSchedgAgrmtItmPrcgElmnt entities (one to many) associated with this entity.
|
SalesSchedgAgrmt |
fetchSalesSchedgAgrmt()
Fetches the SalesSchedgAgrmt entity (one to one) associated with this entity.
|
List<SalesSchedgAgrmtDelivSched> |
fetchSalesSchedgAgrmtDelivSched()
Fetches the SalesSchedgAgrmtDelivSched entities (one to many) associated with this entity.
|
List<SalesSchedgAgrmtItemText> |
fetchText()
Fetches the SalesSchedgAgrmtItemText entities (one to many) associated with this entity.
|
static <T> SalesSchedgAgrmtItemField<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 |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
protected String |
getDefaultServicePath() |
String |
getDeliveryPriority()
Constraints: Not nullable, Maximum length: 2
|
String |
getDeliveryStatus()
Constraints: Not nullable, Maximum length: 1
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
protected String |
getEntityCollection() |
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
|
String |
getItemBillingIncompletionStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getItemDeliveryIncompletionStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getItemGeneralIncompletionStatus()
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
getKey() |
LocalDateTime |
getLastChangeDate()
Constraints: Not nullable, Precision: 0
|
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterialByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9
|
String |
getMaterialPricingGroup()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
BigDecimal |
getNetPriceAmount()
Constraints: Not nullable, Precision: 12, Scale: 3
|
BigDecimal |
getNetPriceQuantity()
Constraints: Not nullable, Precision: 5, Scale: 0
|
String |
getNetPriceQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getOrderQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getOrderQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getOrderToBaseQuantityDnmntr()
Constraints: Not nullable, Precision: 5, Scale: 0
|
BigDecimal |
getOrderToBaseQuantityNmrtr()
Constraints: Not nullable, Precision: 5, Scale: 0
|
String |
getOriginallyRequestedMaterial()
Constraints: Not nullable, Maximum length: 40
|
io.vavr.control.Option<List<SalesSchedgAgrmtItemPartner>> |
getPartnerIfPresent()
Retrieval of associated SalesSchedgAgrmtItemPartner entities (one to many).
|
List<SalesSchedgAgrmtItemPartner> |
getPartnerOrFetch()
Retrieval of associated SalesSchedgAgrmtItemPartner entities (one to many).
|
String |
getPlngDelivSchedInstrn()
Constraints: Not nullable, Maximum length: 4
|
LocalDateTime |
getPricingDate()
Constraints: Not nullable, Precision: 0
|
io.vavr.control.Option<List<SalesSchedgAgrmtItmPrcgElmnt>> |
getPricingElementIfPresent()
Retrieval of associated SalesSchedgAgrmtItmPrcgElmnt entities (one to many).
|
List<SalesSchedgAgrmtItmPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated SalesSchedgAgrmtItmPrcgElmnt entities (one to many).
|
String |
getProductionPlant()
Constraints: Not nullable, Maximum length: 4
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getSalesDocumentRjcnReason()
Constraints: Not nullable, Maximum length: 2
|
io.vavr.control.Option<List<SalesSchedgAgrmtDelivSched>> |
getSalesSchedgAgrmtDelivSchedIfPresent()
Retrieval of associated SalesSchedgAgrmtDelivSched entities (one to many).
|
List<SalesSchedgAgrmtDelivSched> |
getSalesSchedgAgrmtDelivSchedOrFetch()
Retrieval of associated SalesSchedgAgrmtDelivSched entities (one to many).
|
io.vavr.control.Option<SalesSchedgAgrmt> |
getSalesSchedgAgrmtIfPresent()
Retrieval of associated SalesSchedgAgrmt entity (one to one).
|
String |
getSalesSchedgAgrmtItemCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesSchedgAgrmtItemText()
Constraints: Not nullable, Maximum length: 40
|
SalesSchedgAgrmt |
getSalesSchedgAgrmtOrFetch()
Retrieval of associated SalesSchedgAgrmt entity (one to one).
|
String |
getSalesSchedulingAgreement()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSalesSchedulingAgreementItem()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
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
|
BigDecimal |
getTargetQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getTargetQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
io.vavr.control.Option<List<SalesSchedgAgrmtItemText>> |
getTextIfPresent()
Retrieval of associated SalesSchedgAgrmtItemText entities (one to many).
|
List<SalesSchedgAgrmtItemText> |
getTextOrFetch()
Retrieval of associated SalesSchedgAgrmtItemText entities (one to many).
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<SalesSchedgAgrmtItem> |
getType() |
String |
getUnderlyingPurchaseOrderItem()
Constraints: Not nullable, Maximum length: 6
|
int |
hashCode() |
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setDeliveryPriority(String deliveryPriority)
Constraints: Not nullable, Maximum length: 2
|
void |
setDeliveryStatus(String deliveryStatus)
Constraints: Not nullable, Maximum length: 1
|
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 |
setItemBillingIncompletionStatus(String itemBillingIncompletionStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setItemDeliveryIncompletionStatus(String itemDeliveryIncompletionStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setItemGeneralIncompletionStatus(String itemGeneralIncompletionStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setLastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0
|
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 |
setMaterialPricingGroup(String materialPricingGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setNetAmount(BigDecimal netAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setNetPriceAmount(BigDecimal netPriceAmount)
Constraints: Not nullable, Precision: 12, Scale: 3
|
void |
setNetPriceQuantity(BigDecimal netPriceQuantity)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setNetPriceQuantityUnit(String netPriceQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setOrderQuantity(BigDecimal orderQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setOrderQuantityUnit(String orderQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setOrderToBaseQuantityDnmntr(BigDecimal orderToBaseQuantityDnmntr)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setOrderToBaseQuantityNmrtr(BigDecimal orderToBaseQuantityNmrtr)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setOriginallyRequestedMaterial(String originallyRequestedMaterial)
Constraints: Not nullable, Maximum length: 40
|
void |
setPartner(List<SalesSchedgAgrmtItemPartner> value)
Overwrites the list of associated SalesSchedgAgrmtItemPartner entities for the loaded navigation property
to_Partner.
|
void |
setPlngDelivSchedInstrn(String plngDelivSchedInstrn)
Constraints: Not nullable, Maximum length: 4
|
void |
setPricingDate(LocalDateTime pricingDate)
Constraints: Not nullable, Precision: 0
|
void |
setPricingElement(List<SalesSchedgAgrmtItmPrcgElmnt> value)
Overwrites the list of associated SalesSchedgAgrmtItmPrcgElmnt 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 |
setSalesDocumentRjcnReason(String salesDocumentRjcnReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setSalesSchedgAgrmt(SalesSchedgAgrmt value)
Overwrites the associated SalesSchedgAgrmt entity for the loaded navigation property
to_SalesSchedgAgrmt.
|
void |
setSalesSchedgAgrmtDelivSched(List<SalesSchedgAgrmtDelivSched> value)
Overwrites the list of associated SalesSchedgAgrmtDelivSched entities for the loaded navigation property
to_SalesSchedgAgrmtDelivSched.
|
void |
setSalesSchedgAgrmtItemCategory(String salesSchedgAgrmtItemCategory)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesSchedgAgrmtItemText(String salesSchedgAgrmtItemText)
Constraints: Not nullable, Maximum length: 40
|
void |
setSalesSchedulingAgreement(String salesSchedulingAgreement)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSalesSchedulingAgreementItem(String salesSchedulingAgreementItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setSDProcessStatus(String sDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
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 |
setTargetQuantity(BigDecimal targetQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setTargetQuantityUnit(String targetQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setText(List<SalesSchedgAgrmtItemText> value)
Overwrites the list of associated SalesSchedgAgrmtItemText entities for the loaded navigation property
to_Text.
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setUnderlyingPurchaseOrderItem(String underlyingPurchaseOrderItem)
Constraints: Not nullable, Maximum length: 6
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final SalesSchedgAgrmtItemSelectable ALL_FIELDS
public static final SalesSchedgAgrmtItemField<String> SALES_SCHEDULING_AGREEMENT
public static final SalesSchedgAgrmtItemField<String> SALES_SCHEDULING_AGREEMENT_ITEM
public static final SalesSchedgAgrmtItemField<String> SALES_SCHEDG_AGRMT_ITEM_CATEGORY
public static final SalesSchedgAgrmtItemField<LocalDateTime> LAST_CHANGE_DATE
public static final SalesSchedgAgrmtItemField<String> MATERIAL
public static final SalesSchedgAgrmtItemField<String> ORIGINALLY_REQUESTED_MATERIAL
public static final SalesSchedgAgrmtItemField<String> MATERIAL_BY_CUSTOMER
public static final SalesSchedgAgrmtItemField<String> MATERIAL_GROUP
public static final SalesSchedgAgrmtItemField<String> MATERIAL_PRICING_GROUP
public static final SalesSchedgAgrmtItemField<String> PRODUCTION_PLANT
public static final SalesSchedgAgrmtItemField<String> STORAGE_LOCATION
public static final SalesSchedgAgrmtItemField<String> PLNG_DELIV_SCHED_INSTRN
public static final SalesSchedgAgrmtItemField<String> SALES_SCHEDG_AGRMT_ITEM_TEXT
public static final SalesSchedgAgrmtItemField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final SalesSchedgAgrmtItemField<String> UNDERLYING_PURCHASE_ORDER_ITEM
public static final SalesSchedgAgrmtItemField<BigDecimal> ORDER_QUANTITY
public static final SalesSchedgAgrmtItemField<BigDecimal> ORDER_TO_BASE_QUANTITY_DNMNTR
public static final SalesSchedgAgrmtItemField<BigDecimal> ORDER_TO_BASE_QUANTITY_NMRTR
public static final SalesSchedgAgrmtItemField<String> ORDER_QUANTITY_UNIT
public static final SalesSchedgAgrmtItemField<BigDecimal> TARGET_QUANTITY
public static final SalesSchedgAgrmtItemField<String> TARGET_QUANTITY_UNIT
public static final SalesSchedgAgrmtItemField<String> SALES_DOCUMENT_RJCN_REASON
public static final SalesSchedgAgrmtItemField<BigDecimal> NET_AMOUNT
public static final SalesSchedgAgrmtItemField<BigDecimal> NET_PRICE_AMOUNT
public static final SalesSchedgAgrmtItemField<BigDecimal> NET_PRICE_QUANTITY
public static final SalesSchedgAgrmtItemField<String> NET_PRICE_QUANTITY_UNIT
public static final SalesSchedgAgrmtItemField<String> TRANSACTION_CURRENCY
public static final SalesSchedgAgrmtItemField<LocalDateTime> PRICING_DATE
public static final SalesSchedgAgrmtItemField<String> SHIPPING_POINT
public static final SalesSchedgAgrmtItemField<String> SHIPPING_TYPE
public static final SalesSchedgAgrmtItemField<String> DELIVERY_PRIORITY
public static final SalesSchedgAgrmtItemField<String> INCOTERMS_CLASSIFICATION
public static final SalesSchedgAgrmtItemField<String> INCOTERMS_TRANSFER_LOCATION
public static final SalesSchedgAgrmtItemField<String> INCOTERMS_LOCATION1
public static final SalesSchedgAgrmtItemField<String> INCOTERMS_LOCATION2
public static final SalesSchedgAgrmtItemField<String> CUSTOMER_PAYMENT_TERMS
public static final SalesSchedgAgrmtItemField<String> ITEM_BILLING_BLOCK_REASON
public static final SalesSchedgAgrmtItemField<String> SD_PROCESS_STATUS
public static final SalesSchedgAgrmtItemField<String> DELIVERY_STATUS
public static final SalesSchedgAgrmtItemField<String> ITEM_GENERAL_INCOMPLETION_STATUS
public static final SalesSchedgAgrmtItemField<String> ITEM_BILLING_INCOMPLETION_STATUS
public static final SalesSchedgAgrmtItemField<String> ITEM_DELIVERY_INCOMPLETION_STATUS
public static final SalesSchedgAgrmtItemLink<SalesSchedgAgrmtItemPartner> TO_PARTNER
public static final SalesSchedgAgrmtItemLink<SalesSchedgAgrmtItmPrcgElmnt> TO_PRICING_ELEMENT
public static final SalesSchedgAgrmtItemOneToOneLink<SalesSchedgAgrmt> TO_SALES_SCHEDG_AGRMT
public static final SalesSchedgAgrmtItemLink<SalesSchedgAgrmtDelivSched> TO_SALES_SCHEDG_AGRMT_DELIV_SCHED
public static final SalesSchedgAgrmtItemLink<SalesSchedgAgrmtItemText> TO_TEXT
public SalesSchedgAgrmtItem()
public SalesSchedgAgrmtItem(@Nullable String salesSchedulingAgreement, @Nullable String salesSchedulingAgreementItem, @Nullable String salesSchedgAgrmtItemCategory, @Nullable LocalDateTime lastChangeDate, @Nullable String material, @Nullable String originallyRequestedMaterial, @Nullable String materialByCustomer, @Nullable String materialGroup, @Nullable String materialPricingGroup, @Nullable String productionPlant, @Nullable String storageLocation, @Nullable String plngDelivSchedInstrn, @Nullable String salesSchedgAgrmtItemText, @Nullable String purchaseOrderByCustomer, @Nullable String underlyingPurchaseOrderItem, @Nullable BigDecimal orderQuantity, @Nullable BigDecimal orderToBaseQuantityDnmntr, @Nullable BigDecimal orderToBaseQuantityNmrtr, @Nullable String orderQuantityUnit, @Nullable BigDecimal targetQuantity, @Nullable String targetQuantityUnit, @Nullable String salesDocumentRjcnReason, @Nullable BigDecimal netAmount, @Nullable BigDecimal netPriceAmount, @Nullable BigDecimal netPriceQuantity, @Nullable String netPriceQuantityUnit, @Nullable String transactionCurrency, @Nullable LocalDateTime pricingDate, @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 itemBillingBlockReason, @Nullable String sDProcessStatus, @Nullable String deliveryStatus, @Nullable String itemGeneralIncompletionStatus, @Nullable String itemBillingIncompletionStatus, @Nullable String itemDeliveryIncompletionStatus, List<SalesSchedgAgrmtItemPartner> toPartner, List<SalesSchedgAgrmtItmPrcgElmnt> toPricingElement, @Nullable SalesSchedgAgrmt toSalesSchedgAgrmt, List<SalesSchedgAgrmtDelivSched> toSalesSchedgAgrmtDelivSched, List<SalesSchedgAgrmtItemText> toText)
@Nonnull public Class<SalesSchedgAgrmtItem> getType()
getType
in class VdmObject<SalesSchedgAgrmtItem>
public void setSalesSchedulingAgreement(@Nullable String salesSchedulingAgreement)
Original property name from the Odata EDM: SalesSchedulingAgreement
salesSchedulingAgreement
- The number that uniquely identifies the sales scheduling agreement.public void setSalesSchedulingAgreementItem(@Nullable String salesSchedulingAgreementItem)
Original property name from the Odata EDM: SalesSchedulingAgreementItem
salesSchedulingAgreementItem
- The number that uniquely identifies the item in the sales scheduling agreement.public void setSalesSchedgAgrmtItemCategory(@Nullable String salesSchedgAgrmtItemCategory)
Original property name from the Odata EDM: SalesSchedgAgrmtItemCategory
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.
salesSchedgAgrmtItemCategory
- 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 setLastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
lastChangeDate
- Date of Last Changepublic void setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setOriginallyRequestedMaterial(@Nullable String originallyRequestedMaterial)
Original property name from the Odata EDM: OriginallyRequestedMaterial
If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
originallyRequestedMaterial
- Material originally requested by the customer.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 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 setMaterialPricingGroup(@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)
materialPricingGroup
- A way of grouping materials to which you want to apply the same condition.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 setPlngDelivSchedInstrn(@Nullable String plngDelivSchedInstrn)
Original property name from the Odata EDM: PlngDelivSchedInstrn
To create or change a planning delivery schedule, you must first enter a valid instruction in the relevant sales scheduling agreement item. Then you can process planning delivery schedules just as you process forecast and just-in-time (JIT) delivery schedules.Schedule lines in the planning delivery schedule replace those schedule lines in the forecast delivery schedule regarding planning relevance, and if any, delivery relevance.
plngDelivSchedInstrn
- Determines how planning delivery schedules are generated.public void setSalesSchedgAgrmtItemText(@Nullable String salesSchedgAgrmtItemText)
Original property name from the Odata EDM: SalesSchedgAgrmtItemText
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.
salesSchedgAgrmtItemText
- 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 setUnderlyingPurchaseOrderItem(@Nullable String underlyingPurchaseOrderItem)
Original property name from the Odata EDM: UnderlyingPurchaseOrderItem
Enter the item number from the customer's document. The item number may vary from the item number that appears in your own sales document.
underlyingPurchaseOrderItem
- The item number (from a purchase order, for example) that the customer uses to uniquely identify the
item.public void setOrderQuantity(@Nullable BigDecimal orderQuantity)
Original property name from the Odata EDM: OrderQuantity
If there is more than one schedule line for the item, the total order quantity is taken from the rounded quantity of the total of all the schedule lines.If no rounding is carried out, then the order required quantity corresponds to a schedule line of the rounded quantity.
orderQuantity
- The total (rounded) order quantity for this item.public void setOrderToBaseQuantityDnmntr(@Nullable BigDecimal orderToBaseQuantityDnmntr)
Original property name from the Odata EDM: OrderToBaseQuantityDnmntr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
orderToBaseQuantityDnmntr
- Denominator of the conversion factor that the system uses to convert sales units base units of
measure.public void setOrderToBaseQuantityNmrtr(@Nullable BigDecimal orderToBaseQuantityNmrtr)
Original property name from the Odata EDM: OrderToBaseQuantityNmrtr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
orderToBaseQuantityNmrtr
- Numerator of the conversion factor that the system uses to convert sales units base units of measure.public void setOrderQuantityUnit(@Nullable String orderQuantityUnit)
Original property name from the Odata EDM: OrderQuantityUnit
orderQuantityUnit
- Unit of measure in which the material is sold.public void setTargetQuantity(@Nullable BigDecimal targetQuantity)
Original property name from the Odata EDM: TargetQuantity
The following list shows the use of target quantities in different types of sales document.Scheduling agreements: A target quantity represents the total quantity of an item that the customer has agreed to buy during the validity period of the agreement.Credit and debit memo requests: A target quantity represents the total quantity of an item for which you want to issue a credit or debit memo request.Product proposals: A target quantity represents the total quantity of an item that is suggested as part of a product proposal. After you have copied the product proposal into a new sales document, you can create schedule lines.
targetQuantity
- The target quantity for an item in a sales document. The quantity is expressed in sales units (for
example, bottles).public void setTargetQuantityUnit(@Nullable String targetQuantityUnit)
Original property name from the Odata EDM: TargetQuantityUnit
You may use a different unit of measure when you actually process the item.You can create a contract, for example, in which you enter a target quantity in pallets. Later, when you create release orders against the contract, you can specify any other units of measure defined in the material master (for example, cartons).
targetQuantityUnit
- The unit of measure of the target quantity of a material.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 sales document (for example, a sales quotation or a sales order).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 setNetPriceAmount(@Nullable BigDecimal netPriceAmount)
Original property name from the Odata EDM: NetPriceAmount
The net price always refers to the condition unit and the condition pricing unit in the relevant pricing condition.
netPriceAmount
- The net price that results from the net value divided by the order quantity.public void setNetPriceQuantity(@Nullable BigDecimal netPriceQuantity)
Original property name from the Odata EDM: NetPriceQuantity
You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.
netPriceQuantity
- The quantity on which the amount or percentage is based. The quantity is expressed in sales units (for
example, bottles).public void setNetPriceQuantityUnit(@Nullable String netPriceQuantityUnit)
Original property name from the Odata EDM: NetPriceQuantityUnit
netPriceQuantityUnit
- Quantity unit to which the condition amount refers.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 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 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 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 setItemGeneralIncompletionStatus(@Nullable String itemGeneralIncompletionStatus)
Original property name from the Odata EDM: ItemGeneralIncompletionStatus
The status line tells you if all item information, necessary for further processing this item, is complete.
itemGeneralIncompletionStatus
- Displays the status of all information that applies to this item.public void setItemBillingIncompletionStatus(@Nullable String itemBillingIncompletionStatus)
Original property name from the Odata EDM: ItemBillingIncompletionStatus
The status line tells you to what extent the information necessary for billing the item is complete.A sales order item, for example, is incomplete for billing if prices are missing. You cannot bill the item until you provide the missing information.
itemBillingIncompletionStatus
- Displays the incompletion status of billing-related information that applies to this item.public void setItemDeliveryIncompletionStatus(@Nullable String itemDeliveryIncompletionStatus)
Original property name from the Odata EDM: ItemDeliveryIncompletionStatus
The status line tells you if delivery-related item information is complete. You must enter this information, if you want to process the item further.A sales order item is incomplete for delivery processing if, for example, you do not enter a shipping point. You cannot deliver the item until you provide this information.
itemDeliveryIncompletionStatus
- Displays the status of delivery-related information that applies to this item.protected String getEntityCollection()
getEntityCollection
in class VdmEntity<SalesSchedgAgrmtItem>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<SalesSchedgAgrmtItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SalesSchedgAgrmtItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SalesSchedgAgrmtItem>
@Nonnull public static <T> SalesSchedgAgrmtItemField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.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> SalesSchedgAgrmtItemField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<SalesSchedgAgrmtItem>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<SalesSchedgAgrmtItem>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<SalesSchedgAgrmtItem>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
getDefaultServicePath
in class VdmEntity<SalesSchedgAgrmtItem>
@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SalesSchedgAgrmtItem>
@Nonnull public List<SalesSchedgAgrmtItemPartner> 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.@Nonnull public List<SalesSchedgAgrmtItemPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried SalesSchedgAgrmtItem 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.@Nonnull public io.vavr.control.Option<List<SalesSchedgAgrmtItemPartner>> getPartnerIfPresent()
If the navigation property for an entity SalesSchedgAgrmtItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setPartner(@Nonnull List<SalesSchedgAgrmtItemPartner> value)
If the navigation property to_Partner of a queried SalesSchedgAgrmtItem 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 SalesSchedgAgrmtItemPartner entities.public void addPartner(SalesSchedgAgrmtItemPartner... entity)
If the navigation property to_Partner of a queried SalesSchedgAgrmtItem 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 SalesSchedgAgrmtItemPartner entities.@Nonnull public List<SalesSchedgAgrmtItmPrcgElmnt> 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.@Nonnull public List<SalesSchedgAgrmtItmPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried SalesSchedgAgrmtItem 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.@Nonnull public io.vavr.control.Option<List<SalesSchedgAgrmtItmPrcgElmnt>> getPricingElementIfPresent()
If the navigation property for an entity SalesSchedgAgrmtItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result
state empty
is returned.public void setPricingElement(@Nonnull List<SalesSchedgAgrmtItmPrcgElmnt> value)
If the navigation property to_PricingElement of a queried SalesSchedgAgrmtItem 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 SalesSchedgAgrmtItmPrcgElmnt entities.public void addPricingElement(SalesSchedgAgrmtItmPrcgElmnt... entity)
If the navigation property to_PricingElement of a queried SalesSchedgAgrmtItem 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 SalesSchedgAgrmtItmPrcgElmnt entities.@Nullable public SalesSchedgAgrmt fetchSalesSchedgAgrmt() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
null
if an entity is not associated.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.@Nullable public SalesSchedgAgrmt getSalesSchedgAgrmtOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SalesSchedgAgrmt of a queried SalesSchedgAgrmtItem 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.@Nonnull public io.vavr.control.Option<SalesSchedgAgrmt> getSalesSchedgAgrmtIfPresent()
If the navigation property for an entity SalesSchedgAgrmtItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setSalesSchedgAgrmt(SalesSchedgAgrmt value)
value
- New SalesSchedgAgrmt entity.@Nonnull public List<SalesSchedgAgrmtDelivSched> fetchSalesSchedgAgrmtDelivSched() 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.@Nonnull public List<SalesSchedgAgrmtDelivSched> getSalesSchedgAgrmtDelivSchedOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SalesSchedgAgrmtDelivSched of a queried SalesSchedgAgrmtItem 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.@Nonnull public io.vavr.control.Option<List<SalesSchedgAgrmtDelivSched>> getSalesSchedgAgrmtDelivSchedIfPresent()
If the navigation property for an entity SalesSchedgAgrmtItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with
result state empty
is returned.public void setSalesSchedgAgrmtDelivSched(@Nonnull List<SalesSchedgAgrmtDelivSched> value)
If the navigation property to_SalesSchedgAgrmtDelivSched of a queried SalesSchedgAgrmtItem 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 SalesSchedgAgrmtDelivSched entities.public void addSalesSchedgAgrmtDelivSched(SalesSchedgAgrmtDelivSched... entity)
If the navigation property to_SalesSchedgAgrmtDelivSched of a queried SalesSchedgAgrmtItem 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 SalesSchedgAgrmtDelivSched entities.@Nonnull public List<SalesSchedgAgrmtItemText> fetchText() 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.@Nonnull public List<SalesSchedgAgrmtItemText> getTextOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Text of a queried SalesSchedgAgrmtItem 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.@Nonnull public io.vavr.control.Option<List<SalesSchedgAgrmtItemText>> getTextIfPresent()
If the navigation property for an entity SalesSchedgAgrmtItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setText(@Nonnull List<SalesSchedgAgrmtItemText> value)
If the navigation property to_Text of a queried SalesSchedgAgrmtItem 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 SalesSchedgAgrmtItemText entities.public void addText(SalesSchedgAgrmtItemText... entity)
If the navigation property to_Text of a queried SalesSchedgAgrmtItem 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 SalesSchedgAgrmtItemText entities.public static SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder builder()
@Nullable public String getSalesSchedulingAgreement()
Original property name from the Odata EDM: SalesSchedulingAgreement
@Nullable public String getSalesSchedulingAgreementItem()
Original property name from the Odata EDM: SalesSchedulingAgreementItem
@Nullable public String getSalesSchedgAgrmtItemCategory()
Original property name from the Odata EDM: SalesSchedgAgrmtItemCategory
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 LocalDateTime getLastChangeDate()
Original property name from the Odata EDM: LastChangeDate
@Nullable public String getMaterial()
Original property name from the Odata EDM: Material
@Nullable public String getOriginallyRequestedMaterial()
Original property name from the Odata EDM: OriginallyRequestedMaterial
If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
@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 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 getMaterialPricingGroup()
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)
@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 getPlngDelivSchedInstrn()
Original property name from the Odata EDM: PlngDelivSchedInstrn
To create or change a planning delivery schedule, you must first enter a valid instruction in the relevant sales scheduling agreement item. Then you can process planning delivery schedules just as you process forecast and just-in-time (JIT) delivery schedules.Schedule lines in the planning delivery schedule replace those schedule lines in the forecast delivery schedule regarding planning relevance, and if any, delivery relevance.
@Nullable public String getSalesSchedgAgrmtItemText()
Original property name from the Odata EDM: SalesSchedgAgrmtItemText
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 getUnderlyingPurchaseOrderItem()
Original property name from the Odata EDM: UnderlyingPurchaseOrderItem
Enter the item number from the customer's document. The item number may vary from the item number that appears in your own sales document.
@Nullable public BigDecimal getOrderQuantity()
Original property name from the Odata EDM: OrderQuantity
If there is more than one schedule line for the item, the total order quantity is taken from the rounded quantity of the total of all the schedule lines.If no rounding is carried out, then the order required quantity corresponds to a schedule line of the rounded quantity.
@Nullable public BigDecimal getOrderToBaseQuantityDnmntr()
Original property name from the Odata EDM: OrderToBaseQuantityDnmntr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
@Nullable public BigDecimal getOrderToBaseQuantityNmrtr()
Original property name from the Odata EDM: OrderToBaseQuantityNmrtr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
@Nullable public String getOrderQuantityUnit()
Original property name from the Odata EDM: OrderQuantityUnit
@Nullable public BigDecimal getTargetQuantity()
Original property name from the Odata EDM: TargetQuantity
The following list shows the use of target quantities in different types of sales document.Scheduling agreements: A target quantity represents the total quantity of an item that the customer has agreed to buy during the validity period of the agreement.Credit and debit memo requests: A target quantity represents the total quantity of an item for which you want to issue a credit or debit memo request.Product proposals: A target quantity represents the total quantity of an item that is suggested as part of a product proposal. After you have copied the product proposal into a new sales document, you can create schedule lines.
@Nullable public String getTargetQuantityUnit()
Original property name from the Odata EDM: TargetQuantityUnit
You may use a different unit of measure when you actually process the item.You can create a contract, for example, in which you enter a target quantity in pallets. Later, when you create release orders against the contract, you can specify any other units of measure defined in the material master (for example, cartons).
@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 BigDecimal getNetAmount()
Original property name from the Odata EDM: NetAmount
@Nullable public BigDecimal getNetPriceAmount()
Original property name from the Odata EDM: NetPriceAmount
The net price always refers to the condition unit and the condition pricing unit in the relevant pricing condition.
@Nullable public BigDecimal getNetPriceQuantity()
Original property name from the Odata EDM: NetPriceQuantity
You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.
@Nullable public String getNetPriceQuantityUnit()
Original property name from the Odata EDM: NetPriceQuantityUnit
@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 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 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 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 getItemGeneralIncompletionStatus()
Original property name from the Odata EDM: ItemGeneralIncompletionStatus
The status line tells you if all item information, necessary for further processing this item, is complete.
@Nullable public String getItemBillingIncompletionStatus()
Original property name from the Odata EDM: ItemBillingIncompletionStatus
The status line tells you to what extent the information necessary for billing the item is complete.A sales order item, for example, is incomplete for billing if prices are missing. You cannot bill the item until you provide the missing information.
@Nullable public String getItemDeliveryIncompletionStatus()
Original property name from the Odata EDM: ItemDeliveryIncompletionStatus
The status line tells you if delivery-related item information is complete. You must enter this information, if you want to process the item further.A sales order item is incomplete for delivery processing if, for example, you do not enter a shipping point. You cannot deliver the item until you provide this information.
public String toString()
toString
in class VdmObject<SalesSchedgAgrmtItem>
public boolean equals(Object o)
equals
in class VdmObject<SalesSchedgAgrmtItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<SalesSchedgAgrmtItem>
public int hashCode()
hashCode
in class VdmObject<SalesSchedgAgrmtItem>
Copyright © 2019 SAP SE. All rights reserved.