public class SalesInquiryItem extends VdmEntity<SalesInquiryItem>
| Modifier and Type | Class and Description |
|---|---|
static class |
SalesInquiryItem.SalesInquiryItemBuilder |
| Modifier and Type | Field and Description |
|---|---|
static EntityFieldAll<SalesInquiryItem> |
ALL_FIELDS
Selector for all available fields of SalesInquiryItem.
|
static SalesInquiryItemField<String> |
ALTERNATIVE_TO_ITEM
Use with available fluent helpers to apply the AlternativeToItem field to query operations.
|
static SalesInquiryItemField<String> |
BATCH
Use with available fluent helpers to apply the Batch field to query operations.
|
static SalesInquiryItemField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static SalesInquiryItemField<String> |
HIGHER_LEVEL_ITEM
Use with available fluent helpers to apply the HigherLevelItem field to query operations.
|
static SalesInquiryItemField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static SalesInquiryItemField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static SalesInquiryItemField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static SalesInquiryItemField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static SalesInquiryItemField<BigDecimal> |
ITEM_GROSS_WEIGHT
Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
|
static SalesInquiryItemField<BigDecimal> |
ITEM_NET_WEIGHT
Use with available fluent helpers to apply the ItemNetWeight field to query operations.
|
static SalesInquiryItemField<String> |
ITEM_ORDER_PROBABILITY_IN_PERCENT
Use with available fluent helpers to apply the ItemOrderProbabilityInPercent field to query operations.
|
static SalesInquiryItemField<BigDecimal> |
ITEM_VOLUME
Use with available fluent helpers to apply the ItemVolume field to query operations.
|
static SalesInquiryItemField<String> |
ITEM_VOLUME_UNIT
Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
|
static SalesInquiryItemField<String> |
ITEM_WEIGHT_UNIT
Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
|
static SalesInquiryItemField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static SalesInquiryItemField<String> |
MATERIAL_BY_CUSTOMER
Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
|
static SalesInquiryItemField<String> |
MATERIAL_GROUP
Use with available fluent helpers to apply the MaterialGroup field to query operations.
|
static SalesInquiryItemField<BigDecimal> |
NET_AMOUNT
Use with available fluent helpers to apply the NetAmount field to query operations.
|
static SalesInquiryItemField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static SalesInquiryItemField<BigDecimal> |
REQUESTED_QUANTITY
Use with available fluent helpers to apply the RequestedQuantity field to query operations.
|
static SalesInquiryItemField<String> |
REQUESTED_QUANTITY_UNIT
Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
|
static SalesInquiryItemField<String> |
SALES_DOCUMENT_RJCN_REASON
Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
|
static SalesInquiryItemField<String> |
SALES_INQUIRY
Use with available fluent helpers to apply the SalesInquiry field to query operations.
|
static SalesInquiryItemField<String> |
SALES_INQUIRY_ITEM
Use with available fluent helpers to apply the SalesInquiryItem field to query operations.
|
static SalesInquiryItemField<String> |
SALES_INQUIRY_ITEM_CATEGORY
Use with available fluent helpers to apply the SalesInquiryItemCategory field to query operations.
|
static SalesInquiryItemField<String> |
SALES_INQUIRY_ITEM_TEXT
Use with available fluent helpers to apply the SalesInquiryItemText field to query operations.
|
static SalesInquiryItemField<String> |
SD_PROCESS_STATUS
Use with available fluent helpers to apply the SDProcessStatus field to query operations.
|
static SalesInquiryItemLink<SalesInquiryItemPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static SalesInquiryItemLink<SalesInquiryItemPrcgElmnt> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static SalesInquiryItemLink<SalesInquiry> |
TO_SALES_INQUIRY
Use with available fluent helpers to apply the to_SalesInquiry navigation property to query operations.
|
static SalesInquiryItemField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
| Constructor and Description |
|---|
SalesInquiryItem() |
SalesInquiryItem(String salesInquiry,
String salesInquiryItem,
String higherLevelItem,
String salesInquiryItemCategory,
String salesInquiryItemText,
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<SalesInquiryItemPartner> toPartner,
List<SalesInquiryItemPrcgElmnt> toPricingElement,
SalesInquiry toSalesInquiry) |
| Modifier and Type | Method and Description |
|---|---|
void |
addPartner(SalesInquiryItemPartner... entity)
Adds elements to the list of associated SalesInquiryItemPartner entities.
|
void |
addPricingElement(SalesInquiryItemPrcgElmnt... entity)
Adds elements to the list of associated SalesInquiryItemPrcgElmnt entities.
|
static SalesInquiryItem.SalesInquiryItemBuilder |
builder() |
boolean |
equals(Object o) |
List<SalesInquiryItemPartner> |
fetchPartner()
Fetches the SalesInquiryItemPartner entities (one to many) associated with this entity.
|
List<SalesInquiryItemPrcgElmnt> |
fetchPricingElement()
Fetches the SalesInquiryItemPrcgElmnt entities (one to many) associated with this entity.
|
SalesInquiry |
fetchSalesInquiry()
Fetches the SalesInquiry entity (one to one) associated with this entity.
|
static <T> SalesInquiryItemField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getAlternativeToItem()
Constraints: Not nullable, Maximum length: 6
|
String |
getBatch()
Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getHigherLevelItem()
Constraints: Not nullable, Maximum length: 6
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsLocation1()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsLocation2()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28
|
BigDecimal |
getItemGrossWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
BigDecimal |
getItemNetWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getItemOrderProbabilityInPercent()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getItemVolume()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getItemVolumeUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getItemWeightUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterialByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9
|
BigDecimal |
getNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
List<SalesInquiryItemPartner> |
getPartnerOrFetch()
Retrieval of associated SalesInquiryItemPartner entities (one to many).
|
com.google.common.base.Optional<List<SalesInquiryItemPartner>> |
getPartnerOrNull()
Retrieval of associated SalesInquiryItemPartner entities (one to many).
|
List<SalesInquiryItemPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated SalesInquiryItemPrcgElmnt entities (one to many).
|
com.google.common.base.Optional<List<SalesInquiryItemPrcgElmnt>> |
getPricingElementOrNull()
Retrieval of associated SalesInquiryItemPrcgElmnt entities (one to many).
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
BigDecimal |
getRequestedQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getRequestedQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesDocumentRjcnReason()
Constraints: Not nullable, Maximum length: 2
|
String |
getSalesInquiry()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSalesInquiryItem()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getSalesInquiryItemCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesInquiryItemText()
Constraints: Not nullable, Maximum length: 40
|
SalesInquiry |
getSalesInquiryOrFetch()
Retrieval of associated SalesInquiry entity (one to one).
|
com.google.common.base.Optional<SalesInquiry> |
getSalesInquiryOrNull()
Retrieval of associated SalesInquiry entity (one to one).
|
String |
getSDProcessStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<SalesInquiryItem> |
getType() |
int |
hashCode() |
void |
setAlternativeToItem(String alternativeToItem)
Constraints: Not nullable, Maximum length: 6
|
void |
setBatch(String batch)
Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setHigherLevelItem(String higherLevelItem)
Constraints: Not nullable, Maximum length: 6
|
void |
setIncotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
void |
setIncotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
void |
setItemGrossWeight(BigDecimal itemGrossWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemNetWeight(BigDecimal itemNetWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemOrderProbabilityInPercent(String itemOrderProbabilityInPercent)
Constraints: Not nullable, Maximum length: 3
|
void |
setItemVolume(BigDecimal itemVolume)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemVolumeUnit(String itemVolumeUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setItemWeightUnit(String itemWeightUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40
|
void |
setMaterialByCustomer(String materialByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setMaterialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9
|
void |
setNetAmount(BigDecimal netAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setPartner(List<SalesInquiryItemPartner> value)
Overwrites the list of associated SalesInquiryItemPartner entities for the loaded navigation property to_Partner.
|
void |
setPricingElement(List<SalesInquiryItemPrcgElmnt> value)
Overwrites the list of associated SalesInquiryItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
|
void |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setRequestedQuantity(BigDecimal requestedQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setRequestedQuantityUnit(String requestedQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesDocumentRjcnReason(String salesDocumentRjcnReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setSalesInquiry(SalesInquiry value)
Overwrites the associated SalesInquiry entity for the loaded navigation property to_SalesInquiry.
|
void |
setSalesInquiry(String value)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSalesInquiryItem(String salesInquiryItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setSalesInquiryItemCategory(String salesInquiryItemCategory)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesInquiryItemText(String salesInquiryItemText)
Constraints: Not nullable, Maximum length: 40
|
void |
setSDProcessStatus(String sDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final EntityFieldAll<SalesInquiryItem> ALL_FIELDS
public static final SalesInquiryItemField<String> SALES_INQUIRY
public static final SalesInquiryItemField<String> SALES_INQUIRY_ITEM
public static final SalesInquiryItemField<String> HIGHER_LEVEL_ITEM
public static final SalesInquiryItemField<String> SALES_INQUIRY_ITEM_CATEGORY
public static final SalesInquiryItemField<String> SALES_INQUIRY_ITEM_TEXT
public static final SalesInquiryItemField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final SalesInquiryItemField<String> MATERIAL
public static final SalesInquiryItemField<String> MATERIAL_BY_CUSTOMER
public static final SalesInquiryItemField<BigDecimal> REQUESTED_QUANTITY
public static final SalesInquiryItemField<String> REQUESTED_QUANTITY_UNIT
public static final SalesInquiryItemField<String> ITEM_ORDER_PROBABILITY_IN_PERCENT
public static final SalesInquiryItemField<String> ALTERNATIVE_TO_ITEM
public static final SalesInquiryItemField<BigDecimal> ITEM_GROSS_WEIGHT
public static final SalesInquiryItemField<BigDecimal> ITEM_NET_WEIGHT
public static final SalesInquiryItemField<String> ITEM_WEIGHT_UNIT
public static final SalesInquiryItemField<BigDecimal> ITEM_VOLUME
public static final SalesInquiryItemField<String> ITEM_VOLUME_UNIT
public static final SalesInquiryItemField<String> TRANSACTION_CURRENCY
public static final SalesInquiryItemField<BigDecimal> NET_AMOUNT
public static final SalesInquiryItemField<String> MATERIAL_GROUP
public static final SalesInquiryItemField<String> BATCH
public static final SalesInquiryItemField<String> INCOTERMS_CLASSIFICATION
public static final SalesInquiryItemField<String> INCOTERMS_TRANSFER_LOCATION
public static final SalesInquiryItemField<String> INCOTERMS_LOCATION1
public static final SalesInquiryItemField<String> INCOTERMS_LOCATION2
public static final SalesInquiryItemField<String> CUSTOMER_PAYMENT_TERMS
public static final SalesInquiryItemField<String> SALES_DOCUMENT_RJCN_REASON
public static final SalesInquiryItemField<String> SD_PROCESS_STATUS
public static final SalesInquiryItemLink<SalesInquiryItemPartner> TO_PARTNER
public static final SalesInquiryItemLink<SalesInquiryItemPrcgElmnt> TO_PRICING_ELEMENT
public static final SalesInquiryItemLink<SalesInquiry> TO_SALES_INQUIRY
@Generated(value="lombok") public SalesInquiryItem()
@ConstructorProperties(value={"salesInquiry","salesInquiryItem","higherLevelItem","salesInquiryItemCategory","salesInquiryItemText","purchaseOrderByCustomer","material","materialByCustomer","requestedQuantity","requestedQuantityUnit","itemOrderProbabilityInPercent","alternativeToItem","itemGrossWeight","itemNetWeight","itemWeightUnit","itemVolume","itemVolumeUnit","transactionCurrency","netAmount","materialGroup","batch","incotermsClassification","incotermsTransferLocation","incotermsLocation1","incotermsLocation2","customerPaymentTerms","salesDocumentRjcnReason","sDProcessStatus","erpConfigContext","toPartner","toPricingElement","toSalesInquiry"}) @Generated(value="lombok") public SalesInquiryItem(@Nullable String salesInquiry, @Nullable String salesInquiryItem, @Nullable String higherLevelItem, @Nullable String salesInquiryItemCategory, @Nullable String salesInquiryItemText, @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<SalesInquiryItemPartner> toPartner, List<SalesInquiryItemPrcgElmnt> toPricingElement, @Nullable SalesInquiry toSalesInquiry)
public Class<SalesInquiryItem> getType()
getType in class VdmObject<SalesInquiryItem>public static <T> SalesInquiryItemField<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.public List<SalesInquiryItemPartner> 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<SalesInquiryItemPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried SalesInquiryItem 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 com.google.common.base.Optional<List<SalesInquiryItemPartner>> getPartnerOrNull()
If the navigation property to_Partner for an entity SalesInquiryItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setPartner(@NonNull
List<SalesInquiryItemPartner> value)
If the navigation property to_Partner of a queried SalesInquiryItem 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 SalesInquiryItemPartner entities.public void addPartner(SalesInquiryItemPartner... entity)
If the navigation property to_Partner of a queried SalesInquiryItem 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 SalesInquiryItemPartner entities.public List<SalesInquiryItemPrcgElmnt> 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<SalesInquiryItemPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried SalesInquiryItem 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 com.google.common.base.Optional<List<SalesInquiryItemPrcgElmnt>> getPricingElementOrNull()
If the navigation property to_PricingElement for an entity SalesInquiryItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setPricingElement(@NonNull
List<SalesInquiryItemPrcgElmnt> value)
If the navigation property to_PricingElement of a queried SalesInquiryItem 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 SalesInquiryItemPrcgElmnt entities.public void addPricingElement(SalesInquiryItemPrcgElmnt... entity)
If the navigation property to_PricingElement of a queried SalesInquiryItem 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 SalesInquiryItemPrcgElmnt entities.public SalesInquiry fetchSalesInquiry() 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 SalesInquiry getSalesInquiryOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SalesInquiry of a queried SalesInquiryItem 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 com.google.common.base.Optional<SalesInquiry> getSalesInquiryOrNull()
If the navigation property to_SalesInquiry for an entity SalesInquiryItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setSalesInquiry(SalesInquiry value)
value - New SalesInquiry entity.public void setSalesInquiry(String value)
value - salesInquiry@Generated(value="lombok") public static SalesInquiryItem.SalesInquiryItemBuilder builder()
@Nullable @Generated(value="lombok") public String getSalesInquiry()
@Nullable @Generated(value="lombok") public String getSalesInquiryItem()
@Nullable @Generated(value="lombok") public String getHigherLevelItem()
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 @Generated(value="lombok") public String getSalesInquiryItemCategory()
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 @Generated(value="lombok") public String getSalesInquiryItemText()
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 @Generated(value="lombok") public String getPurchaseOrderByCustomer()
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 @Generated(value="lombok") public String getMaterial()
@Nullable @Generated(value="lombok") public String getMaterialByCustomer()
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 as Minimum delivery quantity Partial delivery conditions Enter a value from an existing customer-material info record.
@Nullable @Generated(value="lombok") public BigDecimal getRequestedQuantity()
@Nullable @Generated(value="lombok") public String getRequestedQuantityUnit()
@Nullable @Generated(value="lombok") public String getItemOrderProbabilityInPercent()
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 @Generated(value="lombok") public String getAlternativeToItem()
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 @Generated(value="lombok") public BigDecimal getItemGrossWeight()
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 @Generated(value="lombok") public BigDecimal getItemNetWeight()
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 @Generated(value="lombok") public String getItemWeightUnit()
If you specify a weight, you must enter the corresponding unit of weight here.
@Nullable @Generated(value="lombok") public BigDecimal getItemVolume()
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 @Generated(value="lombok") public String getItemVolumeUnit()
If you specify a volume, you have to enter the corresponding volume unit here.
@Nullable @Generated(value="lombok") public String getTransactionCurrency()
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 @Generated(value="lombok") public BigDecimal getNetAmount()
@Nullable @Generated(value="lombok") public String getMaterialGroup()
You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
@Nullable @Generated(value="lombok") public String getBatch()
@Nullable @Generated(value="lombok") public String getIncotermsClassification()
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 @Generated(value="lombok") public String getIncotermsTransferLocation()
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 @Generated(value="lombok") public String getIncotermsLocation1()
1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms 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 Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If 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 @Generated(value="lombok") public String getIncotermsLocation2()
No Version: This field is disabled Incoterm Version 2000 This 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 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
@Nullable @Generated(value="lombok") public String getCustomerPaymentTerms()
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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 @Generated(value="lombok") public String getSalesDocumentRjcnReason()
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 documents Sales orders: no further delivery of items Contracts: no further creation of release orders Credit and debit memo requests: no further processing of credit or debit memos Enter 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 @Generated(value="lombok") public String getSDProcessStatus()
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 @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setSalesInquiryItem(@Nullable String salesInquiryItem)
salesInquiryItem - @Generated(value="lombok") public void setHigherLevelItem(@Nullable String 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 - @Generated(value="lombok") public void setSalesInquiryItemCategory(@Nullable String salesInquiryItemCategory)
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.
salesInquiryItemCategory - @Generated(value="lombok") public void setSalesInquiryItemText(@Nullable String salesInquiryItemText)
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.
salesInquiryItemText - @Generated(value="lombok") public void setPurchaseOrderByCustomer(@Nullable String 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 - @Generated(value="lombok") public void setMaterial(@Nullable String material)
material - @Generated(value="lombok") public void setMaterialByCustomer(@Nullable String 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 as Minimum delivery quantity Partial delivery conditions Enter a value from an existing customer-material info record.
materialByCustomer - @Generated(value="lombok") public void setRequestedQuantity(@Nullable BigDecimal requestedQuantity)
requestedQuantity - @Generated(value="lombok") public void setRequestedQuantityUnit(@Nullable String requestedQuantityUnit)
requestedQuantityUnit - @Generated(value="lombok") public void setItemOrderProbabilityInPercent(@Nullable String 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 - @Generated(value="lombok") public void setAlternativeToItem(@Nullable String 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 - @Generated(value="lombok") public void setItemGrossWeight(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setItemNetWeight(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setItemWeightUnit(@Nullable String itemWeightUnit)
If you specify a weight, you must enter the corresponding unit of weight here.
itemWeightUnit - @Generated(value="lombok") public void setItemVolume(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setItemVolumeUnit(@Nullable String itemVolumeUnit)
If you specify a volume, you have to enter the corresponding volume unit here.
itemVolumeUnit - @Generated(value="lombok") public void setTransactionCurrency(@Nullable String 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 - @Generated(value="lombok") public void setNetAmount(@Nullable BigDecimal netAmount)
netAmount - @Generated(value="lombok") public void setMaterialGroup(@Nullable String materialGroup)
You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
materialGroup - @Generated(value="lombok") public void setBatch(@Nullable String batch)
batch - @Generated(value="lombok") public void setIncotermsClassification(@Nullable String 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 - @Generated(value="lombok") public void setIncotermsTransferLocation(@Nullable String 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 - @Generated(value="lombok") public void setIncotermsLocation1(@Nullable String incotermsLocation1)
1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms 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 Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If 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 - @Generated(value="lombok") public void setIncotermsLocation2(@Nullable String incotermsLocation2)
No Version: This field is disabled Incoterm Version 2000 This 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 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
incotermsLocation2 - @Generated(value="lombok") public void setCustomerPaymentTerms(@Nullable String customerPaymentTerms)
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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 - @Generated(value="lombok") public void setSalesDocumentRjcnReason(@Nullable String 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 documents Sales orders: no further delivery of items Contracts: no further creation of release orders Credit and debit memo requests: no further processing of credit or debit memos Enter 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 - @Generated(value="lombok") public void setSDProcessStatus(@Nullable String 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 - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class VdmObject<SalesInquiryItem>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<SalesInquiryItem>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<SalesInquiryItem>Copyright © 2017 SAP SE. All rights reserved.