public class SalesQuotationItem extends VdmEntity<SalesQuotationItem>
Original entity name from the Odata EDM: A_SalesQuotationItemType
Modifier and Type | Class and Description |
---|---|
static class |
SalesQuotationItem.SalesQuotationItemBuilder |
Modifier and Type | Field and Description |
---|---|
static SalesQuotationItemSelectable |
ALL_FIELDS
Selector for all available fields of SalesQuotationItem.
|
static SalesQuotationItemField<String> |
ALTERNATIVE_TO_ITEM
Use with available fluent helpers to apply the AlternativeToItem field to query operations.
|
static SalesQuotationItemField<String> |
BATCH
Use with available fluent helpers to apply the Batch field to query operations.
|
static SalesQuotationItemField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static SalesQuotationItemField<String> |
HIGHER_LEVEL_ITEM
Use with available fluent helpers to apply the HigherLevelItem field to query operations.
|
static SalesQuotationItemField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static SalesQuotationItemField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static SalesQuotationItemField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static SalesQuotationItemField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static SalesQuotationItemField<BigDecimal> |
ITEM_GROSS_WEIGHT
Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
|
static SalesQuotationItemField<BigDecimal> |
ITEM_NET_WEIGHT
Use with available fluent helpers to apply the ItemNetWeight field to query operations.
|
static SalesQuotationItemField<String> |
ITEM_ORDER_PROBABILITY_IN_PERCENT
Use with available fluent helpers to apply the ItemOrderProbabilityInPercent field to query operations.
|
static SalesQuotationItemField<BigDecimal> |
ITEM_VOLUME
Use with available fluent helpers to apply the ItemVolume field to query operations.
|
static SalesQuotationItemField<String> |
ITEM_VOLUME_UNIT
Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
|
static SalesQuotationItemField<String> |
ITEM_WEIGHT_UNIT
Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
|
static SalesQuotationItemField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static SalesQuotationItemField<String> |
MATERIAL_BY_CUSTOMER
Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
|
static SalesQuotationItemField<String> |
MATERIAL_GROUP
Use with available fluent helpers to apply the MaterialGroup field to query operations.
|
static SalesQuotationItemField<BigDecimal> |
NET_AMOUNT
Use with available fluent helpers to apply the NetAmount field to query operations.
|
static SalesQuotationItemField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static SalesQuotationItemField<BigDecimal> |
REQUESTED_QUANTITY
Use with available fluent helpers to apply the RequestedQuantity field to query operations.
|
static SalesQuotationItemField<String> |
REQUESTED_QUANTITY_UNIT
Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
|
static SalesQuotationItemField<String> |
SALES_DOCUMENT_RJCN_REASON
Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
|
static SalesQuotationItemField<String> |
SALES_QUOTATION
Use with available fluent helpers to apply the SalesQuotation field to query operations.
|
static SalesQuotationItemField<String> |
SALES_QUOTATION_ITEM
Use with available fluent helpers to apply the SalesQuotationItem field to query operations.
|
static SalesQuotationItemField<String> |
SALES_QUOTATION_ITEM_CATEGORY
Use with available fluent helpers to apply the SalesQuotationItemCategory field to query operations.
|
static SalesQuotationItemField<String> |
SALES_QUOTATION_ITEM_TEXT
Use with available fluent helpers to apply the SalesQuotationItemText field to query operations.
|
static SalesQuotationItemField<String> |
SD_PROCESS_STATUS
Use with available fluent helpers to apply the SDProcessStatus field to query operations.
|
static SalesQuotationItemLink<SalesQuotationItemPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static SalesQuotationItemLink<SalesQuotationItemPrcgElmnt> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static SalesQuotationItemLink<SalesQuotation> |
TO_SALES_QUOTATION
Use with available fluent helpers to apply the to_SalesQuotation navigation property to query operations.
|
static SalesQuotationItemField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SalesQuotationItem() |
SalesQuotationItem(String salesQuotation,
String salesQuotationItem,
String higherLevelItem,
String salesQuotationItemCategory,
String salesQuotationItemText,
String purchaseOrderByCustomer,
String material,
String materialByCustomer,
BigDecimal requestedQuantity,
String requestedQuantityUnit,
String itemOrderProbabilityInPercent,
String alternativeToItem,
BigDecimal itemGrossWeight,
BigDecimal itemNetWeight,
String itemWeightUnit,
BigDecimal itemVolume,
String itemVolumeUnit,
String transactionCurrency,
BigDecimal netAmount,
String materialGroup,
String batch,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String customerPaymentTerms,
String salesDocumentRjcnReason,
String sDProcessStatus,
ErpConfigContext erpConfigContext,
List<SalesQuotationItemPartner> toPartner,
List<SalesQuotationItemPrcgElmnt> toPricingElement,
SalesQuotation toSalesQuotation) |
Modifier and Type | Method and Description |
---|---|
void |
addPartner(SalesQuotationItemPartner... entity)
Adds elements to the list of associated SalesQuotationItemPartner entities.
|
void |
addPricingElement(SalesQuotationItemPrcgElmnt... entity)
Adds elements to the list of associated SalesQuotationItemPrcgElmnt entities.
|
static SalesQuotationItem.SalesQuotationItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<SalesQuotationItemPartner> |
fetchPartner()
Fetches the SalesQuotationItemPartner entities (one to many) associated with this entity.
|
List<SalesQuotationItemPrcgElmnt> |
fetchPricingElement()
Fetches the SalesQuotationItemPrcgElmnt entities (one to many) associated with this entity.
|
SalesQuotation |
fetchSalesQuotation()
Fetches the SalesQuotation entity (one to one) associated with this entity.
|
static <T> SalesQuotationItemField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getAlternativeToItem()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: AlternativeToItemYou can use alternative items in inquiries and quotations.Enter the item number of the alternative item.A customer wants a quotation for 100 units of product A.
|
String |
getBatch()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Batch
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CustomerPaymentTermsIt is used in sales orders, purchase orders, and invoices.
|
protected String |
getEndpointUrl() |
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
String |
getHigherLevelItem()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: HigherLevelItemItems can be organized hierarchically.
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: IncotermsClassificationIncoterms 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").
|
String |
getIncotermsLocation1()
Constraints: Not nullable, Maximum length: 70 Original property name from the Odata EDM: IncotermsLocation11.
|
String |
getIncotermsLocation2()
Constraints: Not nullable, Maximum length: 70 Original property name from the Odata EDM: IncotermsLocation2No 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
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28 Original property name from the Odata EDM: IncotermsTransferLocationIf 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").
|
BigDecimal |
getItemGrossWeight()
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemGrossWeightThe 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.
|
BigDecimal |
getItemNetWeight()
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemNetWeightThe system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record.
|
String |
getItemOrderProbabilityInPercent()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ItemOrderProbabilityInPercentThe system combines the probability factors from the sales document type and from the customer master record of the sold-to party.If probability is 80% for the sales document type and 50% in the customer master record, the system combines the two values.
|
BigDecimal |
getItemVolume()
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemVolumeThe system calculates the volume based on the order quantity for the item and the volume proposed from the material master record.
|
String |
getItemVolumeUnit()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ItemVolumeUnitIf you specify a volume, you have to enter the corresponding volume unit here.
|
String |
getItemWeightUnit()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ItemWeightUnitIf you specify a weight, you must enter the corresponding unit of weight here.
|
protected Map<String,Object> |
getKey() |
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: Material
|
String |
getMaterialByCustomer()
Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: MaterialByCustomerIf 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.
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9 Original property name from the Odata EDM: MaterialGroupYou can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
|
BigDecimal |
getNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3 Original property name from the Odata EDM: NetAmount
|
Optional<List<SalesQuotationItemPartner>> |
getPartnerIfPresent()
Retrieval of associated SalesQuotationItemPartner entities (one to many).
|
List<SalesQuotationItemPartner> |
getPartnerOrFetch()
Retrieval of associated SalesQuotationItemPartner entities (one to many).
|
Optional<List<SalesQuotationItemPrcgElmnt>> |
getPricingElementIfPresent()
Retrieval of associated SalesQuotationItemPrcgElmnt entities (one to many).
|
List<SalesQuotationItemPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated SalesQuotationItemPrcgElmnt entities (one to many).
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: PurchaseOrderByCustomerThe number creates the link between the customer purchase order and the sales document that you create.
|
BigDecimal |
getRequestedQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: RequestedQuantity
|
String |
getRequestedQuantityUnit()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: RequestedQuantityUnit
|
String |
getSalesDocumentRjcnReason()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: SalesDocumentRjcnReasonThe 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).
|
String |
getSalesQuotation()
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: SalesQuotation
|
Optional<SalesQuotation> |
getSalesQuotationIfPresent()
Retrieval of associated SalesQuotation entity (one to one).
|
String |
getSalesQuotationItem()
(Key Field) Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SalesQuotationItem
|
String |
getSalesQuotationItemCategory()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SalesQuotationItemCategoryThe system proposes an item category.
|
String |
getSalesQuotationItemText()
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: SalesQuotationItemTextShort texts are used throughout sales order processing, shipping, and billing.
|
SalesQuotation |
getSalesQuotationOrFetch()
Retrieval of associated SalesQuotation entity (one to one).
|
String |
getSDProcessStatus()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SDProcessStatusThe system determines the overall status from all statuses (for example, delivery and billing) for this item.
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: TransactionCurrencyThe system proposes the document currency from the customer master record of the sold-to party.
|
Class<SalesQuotationItem> |
getType() |
int |
hashCode() |
void |
setAlternativeToItem(String alternativeToItem)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: AlternativeToItemYou can use alternative items in inquiries and quotations.Enter the item number of the alternative item.A customer wants a quotation for 100 units of product A.
|
void |
setBatch(String batch)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Batch
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CustomerPaymentTermsIt is used in sales orders, purchase orders, and invoices.
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setHigherLevelItem(String higherLevelItem)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: HigherLevelItemItems can be organized hierarchically.
|
void |
setIncotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: IncotermsClassificationIncoterms 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").
|
void |
setIncotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70 Original property name from the Odata EDM: IncotermsLocation11.
|
void |
setIncotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70 Original property name from the Odata EDM: IncotermsLocation2No 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
|
void |
setIncotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28 Original property name from the Odata EDM: IncotermsTransferLocationIf 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").
|
void |
setItemGrossWeight(BigDecimal itemGrossWeight)
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemGrossWeightThe 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.
|
void |
setItemNetWeight(BigDecimal itemNetWeight)
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemNetWeightThe system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record.
|
void |
setItemOrderProbabilityInPercent(String itemOrderProbabilityInPercent)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ItemOrderProbabilityInPercentThe system combines the probability factors from the sales document type and from the customer master record of the sold-to party.If probability is 80% for the sales document type and 50% in the customer master record, the system combines the two values.
|
void |
setItemVolume(BigDecimal itemVolume)
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: ItemVolumeThe system calculates the volume based on the order quantity for the item and the volume proposed from the material master record.
|
void |
setItemVolumeUnit(String itemVolumeUnit)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ItemVolumeUnitIf you specify a volume, you have to enter the corresponding volume unit here.
|
void |
setItemWeightUnit(String itemWeightUnit)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ItemWeightUnitIf you specify a weight, you must enter the corresponding unit of weight here.
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: Material
|
void |
setMaterialByCustomer(String materialByCustomer)
Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: MaterialByCustomerIf 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.
|
void |
setMaterialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9 Original property name from the Odata EDM: MaterialGroupYou can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
|
void |
setNetAmount(BigDecimal netAmount)
Constraints: Not nullable, Precision: 16, Scale: 3 Original property name from the Odata EDM: NetAmount
|
void |
setPartner(List<SalesQuotationItemPartner> value)
Overwrites the list of associated SalesQuotationItemPartner entities for the loaded navigation property to_Partner.
|
void |
setPricingElement(List<SalesQuotationItemPrcgElmnt> value)
Overwrites the list of associated SalesQuotationItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
|
void |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: PurchaseOrderByCustomerThe number creates the link between the customer purchase order and the sales document that you create.
|
void |
setRequestedQuantity(BigDecimal requestedQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: RequestedQuantity
|
void |
setRequestedQuantityUnit(String requestedQuantityUnit)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: RequestedQuantityUnit
|
void |
setSalesDocumentRjcnReason(String salesDocumentRjcnReason)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: SalesDocumentRjcnReasonThe 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).
|
void |
setSalesQuotation(SalesQuotation value)
Overwrites the associated SalesQuotation entity for the loaded navigation property to_SalesQuotation.
|
void |
setSalesQuotation(String salesQuotation)
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: SalesQuotation
|
void |
setSalesQuotationItem(String salesQuotationItem)
(Key Field) Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SalesQuotationItem
|
void |
setSalesQuotationItemCategory(String salesQuotationItemCategory)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SalesQuotationItemCategoryThe system proposes an item category.
|
void |
setSalesQuotationItemText(String salesQuotationItemText)
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: SalesQuotationItemTextShort texts are used throughout sales order processing, shipping, and billing.
|
void |
setSDProcessStatus(String sDProcessStatus)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SDProcessStatusThe system determines the overall status from all statuses (for example, delivery and billing) for this item.
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: TransactionCurrencyThe system proposes the document currency from the customer master record of the sold-to party.
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final SalesQuotationItemSelectable ALL_FIELDS
public static final SalesQuotationItemField<String> SALES_QUOTATION
public static final SalesQuotationItemField<String> SALES_QUOTATION_ITEM
public static final SalesQuotationItemField<String> HIGHER_LEVEL_ITEM
public static final SalesQuotationItemField<String> SALES_QUOTATION_ITEM_CATEGORY
public static final SalesQuotationItemField<String> SALES_QUOTATION_ITEM_TEXT
public static final SalesQuotationItemField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final SalesQuotationItemField<String> MATERIAL
public static final SalesQuotationItemField<String> MATERIAL_BY_CUSTOMER
public static final SalesQuotationItemField<BigDecimal> REQUESTED_QUANTITY
public static final SalesQuotationItemField<String> REQUESTED_QUANTITY_UNIT
public static final SalesQuotationItemField<String> ITEM_ORDER_PROBABILITY_IN_PERCENT
public static final SalesQuotationItemField<String> ALTERNATIVE_TO_ITEM
public static final SalesQuotationItemField<BigDecimal> ITEM_GROSS_WEIGHT
public static final SalesQuotationItemField<BigDecimal> ITEM_NET_WEIGHT
public static final SalesQuotationItemField<String> ITEM_WEIGHT_UNIT
public static final SalesQuotationItemField<BigDecimal> ITEM_VOLUME
public static final SalesQuotationItemField<String> ITEM_VOLUME_UNIT
public static final SalesQuotationItemField<String> TRANSACTION_CURRENCY
public static final SalesQuotationItemField<BigDecimal> NET_AMOUNT
public static final SalesQuotationItemField<String> MATERIAL_GROUP
public static final SalesQuotationItemField<String> BATCH
public static final SalesQuotationItemField<String> INCOTERMS_CLASSIFICATION
public static final SalesQuotationItemField<String> INCOTERMS_TRANSFER_LOCATION
public static final SalesQuotationItemField<String> INCOTERMS_LOCATION1
public static final SalesQuotationItemField<String> INCOTERMS_LOCATION2
public static final SalesQuotationItemField<String> CUSTOMER_PAYMENT_TERMS
public static final SalesQuotationItemField<String> SALES_DOCUMENT_RJCN_REASON
public static final SalesQuotationItemField<String> SD_PROCESS_STATUS
public static final SalesQuotationItemLink<SalesQuotationItemPartner> TO_PARTNER
public static final SalesQuotationItemLink<SalesQuotationItemPrcgElmnt> TO_PRICING_ELEMENT
public static final SalesQuotationItemLink<SalesQuotation> TO_SALES_QUOTATION
public SalesQuotationItem()
public SalesQuotationItem(@Nullable String salesQuotation, @Nullable String salesQuotationItem, @Nullable String higherLevelItem, @Nullable String salesQuotationItemCategory, @Nullable String salesQuotationItemText, @Nullable String purchaseOrderByCustomer, @Nullable String material, @Nullable String materialByCustomer, @Nullable BigDecimal requestedQuantity, @Nullable String requestedQuantityUnit, @Nullable String itemOrderProbabilityInPercent, @Nullable String alternativeToItem, @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 incotermsClassification, @Nullable String incotermsTransferLocation, @Nullable String incotermsLocation1, @Nullable String incotermsLocation2, @Nullable String customerPaymentTerms, @Nullable String salesDocumentRjcnReason, @Nullable String sDProcessStatus, @Nullable ErpConfigContext erpConfigContext, List<SalesQuotationItemPartner> toPartner, List<SalesQuotationItemPrcgElmnt> toPricingElement, @Nullable SalesQuotation toSalesQuotation)
public Class<SalesQuotationItem> getType()
getType
in class VdmObject<SalesQuotationItem>
public void setSalesQuotation(@Nullable String salesQuotation)
Original property name from the Odata EDM: SalesQuotation
salesQuotation
- Sales Quotationpublic void setSalesQuotationItem(@Nullable String salesQuotationItem)
Original property name from the Odata EDM: SalesQuotationItem
salesQuotationItem
- Sales Quotation 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 setSalesQuotationItemCategory(@Nullable String salesQuotationItemCategory)
Original property name from the Odata EDM: SalesQuotationItemCategory
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.
salesQuotationItemCategory
- 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 setSalesQuotationItemText(@Nullable String salesQuotationItemText)
Original property name from the Odata EDM: SalesQuotationItemText
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.
salesQuotationItemText
- 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 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 setItemOrderProbabilityInPercent(@Nullable String itemOrderProbabilityInPercent)
Original property name from the Odata EDM: ItemOrderProbabilityInPercent
The system combines the probability factors from the sales document type and from the customer master record of the sold-to party.If probability is 80% for the sales document type and 50% in the customer master record, the system combines the two values. In this case, the system takes 50% of 80% and proposes 40% for the item.The system proposes the probability. You can change the value manually for the item.You can generate requirements from quotations. Accordingly, the probability of quotation items affects how requirements are passed on. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.
itemOrderProbabilityInPercent
- The probability (expressed as a percentage) of the customer confirming the inquiry or quotation item as part of a sales order.public void setAlternativeToItem(@Nullable String alternativeToItem)
Original property name from the Odata EDM: AlternativeToItem
You can use alternative items in inquiries and quotations.Enter the item number of the alternative item.A customer wants a quotation for 100 units of product A. You enter a line in the quotation and the system assigns the item number 10. The customer has also stated that, if product A is not available, you can deliver product B as an alternative. You create a second line in the quotation for 100 items of product B and, in the alternative item field, enter the item number for product A (in this case, 10).If you copy a quotation into a sales order, the system only copies alternative items that you mark for copying in the selection list.
alternativeToItem
- The number of the item for which you can offer this item as an alternative.public 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 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 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.protected String getEndpointUrl()
getEndpointUrl
in class VdmEntity<SalesQuotationItem>
protected String getEntityCollection()
getEntityCollection
in class VdmEntity<SalesQuotationItem>
protected Map<String,Object> getKey()
getKey
in class VdmObject<SalesQuotationItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SalesQuotationItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SalesQuotationItem>
public static <T> SalesQuotationItemField<T> field(String fieldName, 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.protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SalesQuotationItem>
public List<SalesQuotationItemPartner> 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<SalesQuotationItemPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried SalesQuotationItem 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<SalesQuotationItemPartner>> getPartnerIfPresent()
If the navigation property for an entity SalesQuotationItem 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<SalesQuotationItemPartner> value)
If the navigation property to_Partner of a queried SalesQuotationItem 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 SalesQuotationItemPartner entities.public void addPartner(SalesQuotationItemPartner... entity)
If the navigation property to_Partner of a queried SalesQuotationItem 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 SalesQuotationItemPartner entities.public List<SalesQuotationItemPrcgElmnt> 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<SalesQuotationItemPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried SalesQuotationItem 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<SalesQuotationItemPrcgElmnt>> getPricingElementIfPresent()
If the navigation property for an entity SalesQuotationItem 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<SalesQuotationItemPrcgElmnt> value)
If the navigation property to_PricingElement of a queried SalesQuotationItem 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 SalesQuotationItemPrcgElmnt entities.public void addPricingElement(SalesQuotationItemPrcgElmnt... entity)
If the navigation property to_PricingElement of a queried SalesQuotationItem 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 SalesQuotationItemPrcgElmnt entities.public SalesQuotation fetchSalesQuotation() 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 SalesQuotation getSalesQuotationOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SalesQuotation of a queried SalesQuotationItem 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<SalesQuotation> getSalesQuotationIfPresent()
If the navigation property for an entity SalesQuotationItem 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 setSalesQuotation(SalesQuotation value)
value
- New SalesQuotation entity.public static SalesQuotationItem.SalesQuotationItemBuilder builder()
@Nullable public String getSalesQuotation()
Original property name from the Odata EDM: SalesQuotation
@Nullable public String getSalesQuotationItem()
Original property name from the Odata EDM: SalesQuotationItem
@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 getSalesQuotationItemCategory()
Original property name from the Odata EDM: SalesQuotationItemCategory
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 getSalesQuotationItemText()
Original property name from the Odata EDM: SalesQuotationItemText
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 BigDecimal getRequestedQuantity()
Original property name from the Odata EDM: RequestedQuantity
@Nullable public String getRequestedQuantityUnit()
Original property name from the Odata EDM: RequestedQuantityUnit
@Nullable public String getItemOrderProbabilityInPercent()
Original property name from the Odata EDM: ItemOrderProbabilityInPercent
The system combines the probability factors from the sales document type and from the customer master record of the sold-to party.If probability is 80% for the sales document type and 50% in the customer master record, the system combines the two values. In this case, the system takes 50% of 80% and proposes 40% for the item.The system proposes the probability. You can change the value manually for the item.You can generate requirements from quotations. Accordingly, the probability of quotation items affects how requirements are passed on. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.
@Nullable public String getAlternativeToItem()
Original property name from the Odata EDM: AlternativeToItem
You can use alternative items in inquiries and quotations.Enter the item number of the alternative item.A customer wants a quotation for 100 units of product A. You enter a line in the quotation and the system assigns the item number 10. The customer has also stated that, if product A is not available, you can deliver product B as an alternative. You create a second line in the quotation for 100 items of product B and, in the alternative item field, enter the item number for product A (in this case, 10).If you copy a quotation into a sales order, the system only copies alternative items that you mark for copying in the selection list.
@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 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 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 ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<SalesQuotationItem>
erpConfigContext
- public String toString()
toString
in class VdmObject<SalesQuotationItem>
public boolean equals(Object o)
equals
in class VdmObject<SalesQuotationItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<SalesQuotationItem>
public int hashCode()
hashCode
in class VdmObject<SalesQuotationItem>
Copyright © 2018 SAP SE. All rights reserved.