public class SalesInquiry extends VdmEntity<SalesInquiry>
| Modifier and Type | Class and Description |
|---|---|
static class |
SalesInquiry.SalesInquiryBuilder |
| Modifier and Type | Field and Description |
|---|---|
static EntityFieldAll<SalesInquiry> |
ALL_FIELDS
Selector for all available fields of SalesInquiry.
|
static SalesInquiryField<Calendar> |
BINDING_PERIOD_VALIDITY_END_DATE
Use with available fluent helpers to apply the BindingPeriodValidityEndDate field to query operations.
|
static SalesInquiryField<Calendar> |
BINDING_PERIOD_VALIDITY_START_DATE
Use with available fluent helpers to apply the BindingPeriodValidityStartDate field to query operations.
|
static SalesInquiryField<String> |
CREATED_BY_USER
Use with available fluent helpers to apply the CreatedByUser field to query operations.
|
static SalesInquiryField<Calendar> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static SalesInquiryField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static SalesInquiryField<Calendar> |
CUSTOMER_PURCHASE_ORDER_DATE
Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
|
static SalesInquiryField<String> |
CUSTOMER_PURCHASE_ORDER_TYPE
Use with available fluent helpers to apply the CustomerPurchaseOrderType field to query operations.
|
static SalesInquiryField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static SalesInquiryField<BigDecimal> |
EXPECTED_ORDER_NET_AMOUNT
Use with available fluent helpers to apply the ExpectedOrderNetAmount field to query operations.
|
static SalesInquiryField<String> |
HDR_ORDER_PROBABILITY_IN_PERCENT
Use with available fluent helpers to apply the HdrOrderProbabilityInPercent field to query operations.
|
static SalesInquiryField<String> |
HEADER_BILLING_BLOCK_REASON
Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
|
static SalesInquiryField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static SalesInquiryField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static SalesInquiryField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static SalesInquiryField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static SalesInquiryField<String> |
INCOTERMS_VERSION
Use with available fluent helpers to apply the IncotermsVersion field to query operations.
|
static SalesInquiryField<Calendar> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static SalesInquiryField<Calendar> |
LAST_CHANGE_DATE_TIME
Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
|
static SalesInquiryField<String> |
ORGANIZATION_DIVISION
Use with available fluent helpers to apply the OrganizationDivision field to query operations.
|
static SalesInquiryField<String> |
OVERALL_SD_DOCUMENT_REJECTION_STS
Use with available fluent helpers to apply the OverallSDDocumentRejectionSts field to query operations.
|
static SalesInquiryField<String> |
OVERALL_SD_PROCESS_STATUS
Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
|
static SalesInquiryField<String> |
PAYMENT_METHOD
Use with available fluent helpers to apply the PaymentMethod field to query operations.
|
static SalesInquiryField<Calendar> |
PRICING_DATE
Use with available fluent helpers to apply the PricingDate field to query operations.
|
static SalesInquiryField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static SalesInquiryField<String> |
SALES_DISTRICT
Use with available fluent helpers to apply the SalesDistrict field to query operations.
|
static SalesInquiryField<String> |
SALES_GROUP
Use with available fluent helpers to apply the SalesGroup field to query operations.
|
static SalesInquiryField<String> |
SALES_INQUIRY
Use with available fluent helpers to apply the SalesInquiry field to query operations.
|
static SalesInquiryField<Calendar> |
SALES_INQUIRY_DATE
Use with available fluent helpers to apply the SalesInquiryDate field to query operations.
|
static SalesInquiryField<String> |
SALES_INQUIRY_TYPE
Use with available fluent helpers to apply the SalesInquiryType field to query operations.
|
static SalesInquiryField<String> |
SALES_OFFICE
Use with available fluent helpers to apply the SalesOffice field to query operations.
|
static SalesInquiryField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static SalesInquiryField<String> |
SD_DOCUMENT_REASON
Use with available fluent helpers to apply the SDDocumentReason field to query operations.
|
static SalesInquiryField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
static SalesInquiryLink<SalesInquiryItem> |
TO_ITEM
Use with available fluent helpers to apply the to_Item navigation property to query operations.
|
static SalesInquiryLink<SalesInquiryPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static SalesInquiryLink<SalesInquiryPrcgElmnt> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static SalesInquiryField<String> |
TOTAL_CREDIT_CHECK_STATUS
Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
|
static SalesInquiryField<BigDecimal> |
TOTAL_NET_AMOUNT
Use with available fluent helpers to apply the TotalNetAmount field to query operations.
|
static SalesInquiryField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
| Constructor and Description |
|---|
SalesInquiry() |
SalesInquiry(String salesInquiry,
String salesInquiryType,
String salesOrganization,
String distributionChannel,
String organizationDivision,
String salesGroup,
String salesOffice,
String salesDistrict,
String soldToParty,
Calendar creationDate,
String createdByUser,
Calendar lastChangeDate,
Calendar lastChangeDateTime,
String purchaseOrderByCustomer,
String customerPurchaseOrderType,
Calendar customerPurchaseOrderDate,
Calendar salesInquiryDate,
BigDecimal totalNetAmount,
String transactionCurrency,
String sDDocumentReason,
Calendar pricingDate,
String headerBillingBlockReason,
Calendar bindingPeriodValidityStartDate,
Calendar bindingPeriodValidityEndDate,
String hdrOrderProbabilityInPercent,
BigDecimal expectedOrderNetAmount,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String incotermsVersion,
String customerPaymentTerms,
String paymentMethod,
String overallSDProcessStatus,
String totalCreditCheckStatus,
String overallSDDocumentRejectionSts,
ErpConfigContext erpConfigContext,
List<SalesInquiryItem> toItem,
List<SalesInquiryPartner> toPartner,
List<SalesInquiryPrcgElmnt> toPricingElement) |
| Modifier and Type | Method and Description |
|---|---|
void |
addItem(SalesInquiryItem... entity)
Adds elements to the list of associated SalesInquiryItem entities.
|
void |
addPartner(SalesInquiryPartner... entity)
Adds elements to the list of associated SalesInquiryPartner entities.
|
void |
addPricingElement(SalesInquiryPrcgElmnt... entity)
Adds elements to the list of associated SalesInquiryPrcgElmnt entities.
|
static SalesInquiry.SalesInquiryBuilder |
builder() |
boolean |
equals(Object o) |
List<SalesInquiryItem> |
fetchItem()
Fetches the SalesInquiryItem entities (one to many) associated with this entity.
|
List<SalesInquiryPartner> |
fetchPartner()
Fetches the SalesInquiryPartner entities (one to many) associated with this entity.
|
List<SalesInquiryPrcgElmnt> |
fetchPricingElement()
Fetches the SalesInquiryPrcgElmnt entities (one to many) associated with this entity.
|
static <T> SalesInquiryField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
Calendar |
getBindingPeriodValidityEndDate()
Constraints: Not nullable, Precision: 0
|
Calendar |
getBindingPeriodValidityStartDate()
Constraints: Not nullable, Precision: 0
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
Calendar |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
Calendar |
getCustomerPurchaseOrderDate()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerPurchaseOrderType()
Constraints: Not nullable, Maximum length: 4
|
String |
getDistributionChannel()
Constraints: Not nullable, Maximum length: 2
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
BigDecimal |
getExpectedOrderNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getHdrOrderProbabilityInPercent()
Constraints: Not nullable, Maximum length: 3
|
String |
getHeaderBillingBlockReason()
Constraints: Not nullable, Maximum length: 2
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsLocation1()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsLocation2()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28
|
String |
getIncotermsVersion()
Constraints: Not nullable, Maximum length: 4
|
List<SalesInquiryItem> |
getItemOrFetch()
Retrieval of associated SalesInquiryItem entities (one to many).
|
com.google.common.base.Optional<List<SalesInquiryItem>> |
getItemOrNull()
Retrieval of associated SalesInquiryItem entities (one to many).
|
Calendar |
getLastChangeDate()
Constraints: Not nullable, Precision: 0
|
Calendar |
getLastChangeDateTime()
Constraints: Not nullable, Precision: 7
|
String |
getOrganizationDivision()
Constraints: Not nullable, Maximum length: 2
|
String |
getOverallSDDocumentRejectionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallSDProcessStatus()
Constraints: Not nullable, Maximum length: 1
|
List<SalesInquiryPartner> |
getPartnerOrFetch()
Retrieval of associated SalesInquiryPartner entities (one to many).
|
com.google.common.base.Optional<List<SalesInquiryPartner>> |
getPartnerOrNull()
Retrieval of associated SalesInquiryPartner entities (one to many).
|
String |
getPaymentMethod()
Constraints: Not nullable, Maximum length: 1
|
Calendar |
getPricingDate()
Constraints: Not nullable, Precision: 0
|
List<SalesInquiryPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated SalesInquiryPrcgElmnt entities (one to many).
|
com.google.common.base.Optional<List<SalesInquiryPrcgElmnt>> |
getPricingElementOrNull()
Retrieval of associated SalesInquiryPrcgElmnt entities (one to many).
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getSalesDistrict()
Constraints: Not nullable, Maximum length: 6
|
String |
getSalesGroup()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesInquiry()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
Calendar |
getSalesInquiryDate()
Constraints: Not nullable, Precision: 0
|
String |
getSalesInquiryType()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesOffice()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesOrganization()
Constraints: Not nullable, Maximum length: 4
|
String |
getSDDocumentReason()
Constraints: Not nullable, Maximum length: 3
|
String |
getSoldToParty()
Constraints: Not nullable, Maximum length: 10
|
String |
getTotalCreditCheckStatus()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getTotalNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<SalesInquiry> |
getType() |
int |
hashCode() |
void |
setBindingPeriodValidityEndDate(Calendar bindingPeriodValidityEndDate)
Constraints: Not nullable, Precision: 0
|
void |
setBindingPeriodValidityStartDate(Calendar bindingPeriodValidityStartDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDate(Calendar creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setCustomerPurchaseOrderDate(Calendar customerPurchaseOrderDate)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerPurchaseOrderType(String customerPurchaseOrderType)
Constraints: Not nullable, Maximum length: 4
|
void |
setDistributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setExpectedOrderNetAmount(BigDecimal expectedOrderNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setHdrOrderProbabilityInPercent(String hdrOrderProbabilityInPercent)
Constraints: Not nullable, Maximum length: 3
|
void |
setHeaderBillingBlockReason(String headerBillingBlockReason)
Constraints: Not nullable, Maximum length: 2
|
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 |
setIncotermsVersion(String incotermsVersion)
Constraints: Not nullable, Maximum length: 4
|
void |
setItem(List<SalesInquiryItem> value)
Overwrites the list of associated SalesInquiryItem entities for the loaded navigation property to_Item.
|
void |
setLastChangeDate(Calendar lastChangeDate)
Constraints: Not nullable, Precision: 0
|
void |
setLastChangeDateTime(Calendar lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
void |
setOrganizationDivision(String organizationDivision)
Constraints: Not nullable, Maximum length: 2
|
void |
setOverallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallSDProcessStatus(String overallSDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setPartner(List<SalesInquiryPartner> value)
Overwrites the list of associated SalesInquiryPartner entities for the loaded navigation property to_Partner.
|
void |
setPaymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1
|
void |
setPricingDate(Calendar pricingDate)
Constraints: Not nullable, Precision: 0
|
void |
setPricingElement(List<SalesInquiryPrcgElmnt> value)
Overwrites the list of associated SalesInquiryPrcgElmnt entities for the loaded navigation property to_PricingElement.
|
void |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setSalesDistrict(String salesDistrict)
Constraints: Not nullable, Maximum length: 6
|
void |
setSalesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesInquiry(String salesInquiry)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSalesInquiryDate(Calendar salesInquiryDate)
Constraints: Not nullable, Precision: 0
|
void |
setSalesInquiryType(String salesInquiryType)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
void |
setSDDocumentReason(String sDDocumentReason)
Constraints: Not nullable, Maximum length: 3
|
void |
setSoldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setTotalCreditCheckStatus(String totalCreditCheckStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setTotalNetAmount(BigDecimal totalNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final EntityFieldAll<SalesInquiry> ALL_FIELDS
public static final SalesInquiryField<String> SALES_INQUIRY
public static final SalesInquiryField<String> SALES_INQUIRY_TYPE
public static final SalesInquiryField<String> SALES_ORGANIZATION
public static final SalesInquiryField<String> DISTRIBUTION_CHANNEL
public static final SalesInquiryField<String> ORGANIZATION_DIVISION
public static final SalesInquiryField<String> SALES_GROUP
public static final SalesInquiryField<String> SALES_OFFICE
public static final SalesInquiryField<String> SALES_DISTRICT
public static final SalesInquiryField<String> SOLD_TO_PARTY
public static final SalesInquiryField<Calendar> CREATION_DATE
public static final SalesInquiryField<String> CREATED_BY_USER
public static final SalesInquiryField<Calendar> LAST_CHANGE_DATE
public static final SalesInquiryField<Calendar> LAST_CHANGE_DATE_TIME
public static final SalesInquiryField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final SalesInquiryField<String> CUSTOMER_PURCHASE_ORDER_TYPE
public static final SalesInquiryField<Calendar> CUSTOMER_PURCHASE_ORDER_DATE
public static final SalesInquiryField<Calendar> SALES_INQUIRY_DATE
public static final SalesInquiryField<BigDecimal> TOTAL_NET_AMOUNT
public static final SalesInquiryField<String> TRANSACTION_CURRENCY
public static final SalesInquiryField<String> SD_DOCUMENT_REASON
public static final SalesInquiryField<Calendar> PRICING_DATE
public static final SalesInquiryField<String> HEADER_BILLING_BLOCK_REASON
public static final SalesInquiryField<Calendar> BINDING_PERIOD_VALIDITY_START_DATE
public static final SalesInquiryField<Calendar> BINDING_PERIOD_VALIDITY_END_DATE
public static final SalesInquiryField<String> HDR_ORDER_PROBABILITY_IN_PERCENT
public static final SalesInquiryField<BigDecimal> EXPECTED_ORDER_NET_AMOUNT
public static final SalesInquiryField<String> INCOTERMS_CLASSIFICATION
public static final SalesInquiryField<String> INCOTERMS_TRANSFER_LOCATION
public static final SalesInquiryField<String> INCOTERMS_LOCATION1
public static final SalesInquiryField<String> INCOTERMS_LOCATION2
public static final SalesInquiryField<String> INCOTERMS_VERSION
public static final SalesInquiryField<String> CUSTOMER_PAYMENT_TERMS
public static final SalesInquiryField<String> PAYMENT_METHOD
public static final SalesInquiryField<String> OVERALL_SD_PROCESS_STATUS
public static final SalesInquiryField<String> TOTAL_CREDIT_CHECK_STATUS
public static final SalesInquiryField<String> OVERALL_SD_DOCUMENT_REJECTION_STS
public static final SalesInquiryLink<SalesInquiryItem> TO_ITEM
public static final SalesInquiryLink<SalesInquiryPartner> TO_PARTNER
public static final SalesInquiryLink<SalesInquiryPrcgElmnt> TO_PRICING_ELEMENT
@Generated(value="lombok") public SalesInquiry()
@ConstructorProperties(value={"salesInquiry","salesInquiryType","salesOrganization","distributionChannel","organizationDivision","salesGroup","salesOffice","salesDistrict","soldToParty","creationDate","createdByUser","lastChangeDate","lastChangeDateTime","purchaseOrderByCustomer","customerPurchaseOrderType","customerPurchaseOrderDate","salesInquiryDate","totalNetAmount","transactionCurrency","sDDocumentReason","pricingDate","headerBillingBlockReason","bindingPeriodValidityStartDate","bindingPeriodValidityEndDate","hdrOrderProbabilityInPercent","expectedOrderNetAmount","incotermsClassification","incotermsTransferLocation","incotermsLocation1","incotermsLocation2","incotermsVersion","customerPaymentTerms","paymentMethod","overallSDProcessStatus","totalCreditCheckStatus","overallSDDocumentRejectionSts","erpConfigContext","toItem","toPartner","toPricingElement"}) @Generated(value="lombok") public SalesInquiry(@Nullable String salesInquiry, @Nullable String salesInquiryType, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String organizationDivision, @Nullable String salesGroup, @Nullable String salesOffice, @Nullable String salesDistrict, @Nullable String soldToParty, @Nullable Calendar creationDate, @Nullable String createdByUser, @Nullable Calendar lastChangeDate, @Nullable Calendar lastChangeDateTime, @Nullable String purchaseOrderByCustomer, @Nullable String customerPurchaseOrderType, @Nullable Calendar customerPurchaseOrderDate, @Nullable Calendar salesInquiryDate, @Nullable BigDecimal totalNetAmount, @Nullable String transactionCurrency, @Nullable String sDDocumentReason, @Nullable Calendar pricingDate, @Nullable String headerBillingBlockReason, @Nullable Calendar bindingPeriodValidityStartDate, @Nullable Calendar bindingPeriodValidityEndDate, @Nullable String hdrOrderProbabilityInPercent, @Nullable BigDecimal expectedOrderNetAmount, @Nullable String incotermsClassification, @Nullable String incotermsTransferLocation, @Nullable String incotermsLocation1, @Nullable String incotermsLocation2, @Nullable String incotermsVersion, @Nullable String customerPaymentTerms, @Nullable String paymentMethod, @Nullable String overallSDProcessStatus, @Nullable String totalCreditCheckStatus, @Nullable String overallSDDocumentRejectionSts, @Nullable ErpConfigContext erpConfigContext, List<SalesInquiryItem> toItem, List<SalesInquiryPartner> toPartner, List<SalesInquiryPrcgElmnt> toPricingElement)
public Class<SalesInquiry> getType()
getType in class VdmObject<SalesInquiry>public static <T> SalesInquiryField<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<SalesInquiryItem> fetchItem() 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<SalesInquiryItem> getItemOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Item of a queried SalesInquiry 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<SalesInquiryItem>> getItemOrNull()
If the navigation property to_Item for an entity SalesInquiry has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setItem(@NonNull
List<SalesInquiryItem> value)
If the navigation property to_Item of a queried SalesInquiry 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 SalesInquiryItem entities.public void addItem(SalesInquiryItem... entity)
If the navigation property to_Item of a queried SalesInquiry 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 SalesInquiryItem entities.public List<SalesInquiryPartner> 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<SalesInquiryPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried SalesInquiry 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<SalesInquiryPartner>> getPartnerOrNull()
If the navigation property to_Partner for an entity SalesInquiry 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<SalesInquiryPartner> value)
If the navigation property to_Partner of a queried SalesInquiry 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 SalesInquiryPartner entities.public void addPartner(SalesInquiryPartner... entity)
If the navigation property to_Partner of a queried SalesInquiry 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 SalesInquiryPartner entities.public List<SalesInquiryPrcgElmnt> 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<SalesInquiryPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried SalesInquiry 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<SalesInquiryPrcgElmnt>> getPricingElementOrNull()
If the navigation property to_PricingElement for an entity SalesInquiry 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<SalesInquiryPrcgElmnt> value)
If the navigation property to_PricingElement of a queried SalesInquiry 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 SalesInquiryPrcgElmnt entities.public void addPricingElement(SalesInquiryPrcgElmnt... entity)
If the navigation property to_PricingElement of a queried SalesInquiry 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 SalesInquiryPrcgElmnt entities.@Generated(value="lombok") public static SalesInquiry.SalesInquiryBuilder builder()
@Nullable @Generated(value="lombok") public String getSalesInquiry()
@Nullable @Generated(value="lombok") public String getSalesInquiryType()
The sales document type determines how the system processes the sales document. For example, depending on the sales document type, the system determines which screens to present and which data to ask you for.
@Nullable @Generated(value="lombok") public String getSalesOrganization()
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
@Nullable @Generated(value="lombok") public String getDistributionChannel()
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel. You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel. For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
@Nullable @Generated(value="lombok") public String getOrganizationDivision()
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise. If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
@Nullable @Generated(value="lombok") public String getSalesGroup()
By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria. If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market. You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
@Nullable @Generated(value="lombok") public String getSalesOffice()
When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office. You can assign each customer to a sales office in the customer master record. Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
@Nullable @Generated(value="lombok") public String getSalesDistrict()
Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria. The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
@Nullable @Generated(value="lombok") public String getSoldToParty()
@Nullable @Generated(value="lombok") public Calendar getCreationDate()
@Nullable @Generated(value="lombok") public String getCreatedByUser()
@Nullable @Generated(value="lombok") public Calendar getLastChangeDate()
@Nullable @Generated(value="lombok") public Calendar getLastChangeDateTime()
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose. Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone. The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure. See also GET TIME STAMP A UTC time stamp in short form is also available.
@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 getCustomerPurchaseOrderType()
You can record here whether the sales document arrived, for example, by telephone, mail, or fax. Enter one of the values predefined for your system.
@Nullable @Generated(value="lombok") public Calendar getCustomerPurchaseOrderDate()
@Nullable @Generated(value="lombok") public Calendar getSalesInquiryDate()
When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected. You can define the document date to meet the needs of your organization. For sales orders, for example, you can define the document date as the date when the order actually arrives at your offices. Alternatively, you could define it as the date when the order was written up by a field sales representative. The system proposes the current date. You can change it manually in the sales document.
@Nullable @Generated(value="lombok") public BigDecimal getTotalNetAmount()
@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 String getSDDocumentReason()
You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria. Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason. If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
@Nullable @Generated(value="lombok") public Calendar getPricingDate()
You can use the pricing date as a selection criterion when you process billing documents collectively. The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue. Determining the Proposal In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date. In the billing document: The billing date is proposed as the pricing date.
@Nullable @Generated(value="lombok") public String getHeaderBillingBlockReason()
The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level. You may want to apply a billing block to certain documents so that prices can be checked before further processing.
@Nullable @Generated(value="lombok") public Calendar getBindingPeriodValidityStartDate()
The beginning date and the end date together define the validity period of the inquiry or quotation.
@Nullable @Generated(value="lombok") public Calendar getBindingPeriodValidityEndDate()
@Nullable @Generated(value="lombok") public String getHdrOrderProbabilityInPercent()
The system uses the probability and net value of each item to calculate a total expected order value for the sales document. The expected order value appears in the double-line entry screen. The system proposes the probability for each item. You can change the value manually depending on the sales document category. A quotation contains two items: Item 1 has a value of $100 and a probability of 100% Item 2 has a value of $200 and a probability of 25% The system calculates the total probability as follows: ($100 x 100% + $200 x 25% ) divided by $300 = 50% In this case, the probability of this quotation resulting in a sales order is 50%. You can generate requirements from quotations. The probability of the quotation items affects how the system passes on requirements. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.
@Nullable @Generated(value="lombok") public BigDecimal getExpectedOrderNetAmount()
@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 getIncotermsVersion()
@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 getPaymentMethod()
If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules. For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
@Nullable @Generated(value="lombok") public String getOverallSDProcessStatus()
The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
@Nullable @Generated(value="lombok") public String getTotalCreditCheckStatus()
@Nullable @Generated(value="lombok") public String getOverallSDDocumentRejectionSts()
The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setSalesInquiry(@Nullable String salesInquiry)
salesInquiry - @Generated(value="lombok") public void setSalesInquiryType(@Nullable String salesInquiryType)
The sales document type determines how the system processes the sales document. For example, depending on the sales document type, the system determines which screens to present and which data to ask you for.
salesInquiryType - @Generated(value="lombok") public void setSalesOrganization(@Nullable String salesOrganization)
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
salesOrganization - @Generated(value="lombok") public void setDistributionChannel(@Nullable String distributionChannel)
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel. You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel. For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
distributionChannel - @Generated(value="lombok") public void setOrganizationDivision(@Nullable String organizationDivision)
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise. If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
organizationDivision - @Generated(value="lombok") public void setSalesGroup(@Nullable String salesGroup)
By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria. If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market. You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
salesGroup - @Generated(value="lombok") public void setSalesOffice(@Nullable String salesOffice)
When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office. You can assign each customer to a sales office in the customer master record. Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
salesOffice - @Generated(value="lombok") public void setSalesDistrict(@Nullable String salesDistrict)
Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria. The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
salesDistrict - @Generated(value="lombok") public void setSoldToParty(@Nullable String soldToParty)
soldToParty - @Generated(value="lombok") public void setCreationDate(@Nullable Calendar creationDate)
creationDate - @Generated(value="lombok") public void setCreatedByUser(@Nullable String createdByUser)
createdByUser - @Generated(value="lombok") public void setLastChangeDate(@Nullable Calendar lastChangeDate)
lastChangeDate - @Generated(value="lombok") public void setLastChangeDateTime(@Nullable Calendar lastChangeDateTime)
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose. Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone. The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure. See also GET TIME STAMP A UTC time stamp in short form is also available.
lastChangeDateTime - @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 setCustomerPurchaseOrderType(@Nullable String customerPurchaseOrderType)
You can record here whether the sales document arrived, for example, by telephone, mail, or fax. Enter one of the values predefined for your system.
customerPurchaseOrderType - @Generated(value="lombok") public void setCustomerPurchaseOrderDate(@Nullable Calendar customerPurchaseOrderDate)
customerPurchaseOrderDate - @Generated(value="lombok") public void setSalesInquiryDate(@Nullable Calendar salesInquiryDate)
When you want to generate a list of sales documents or sales statistics, the document date you enter determines which sales documents are selected. You can define the document date to meet the needs of your organization. For sales orders, for example, you can define the document date as the date when the order actually arrives at your offices. Alternatively, you could define it as the date when the order was written up by a field sales representative. The system proposes the current date. You can change it manually in the sales document.
salesInquiryDate - @Generated(value="lombok") public void setTotalNetAmount(@Nullable BigDecimal totalNetAmount)
totalNetAmount - @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 setSDDocumentReason(@Nullable String sDDocumentReason)
You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria. Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason. If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
sDDocumentReason - @Generated(value="lombok") public void setPricingDate(@Nullable Calendar pricingDate)
You can use the pricing date as a selection criterion when you process billing documents collectively. The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue. Determining the Proposal In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date. In the billing document: The billing date is proposed as the pricing date.
pricingDate - @Generated(value="lombok") public void setHeaderBillingBlockReason(@Nullable String headerBillingBlockReason)
The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level. You may want to apply a billing block to certain documents so that prices can be checked before further processing.
headerBillingBlockReason - @Generated(value="lombok") public void setBindingPeriodValidityStartDate(@Nullable Calendar bindingPeriodValidityStartDate)
The beginning date and the end date together define the validity period of the inquiry or quotation.
bindingPeriodValidityStartDate - @Generated(value="lombok") public void setBindingPeriodValidityEndDate(@Nullable Calendar bindingPeriodValidityEndDate)
bindingPeriodValidityEndDate - @Generated(value="lombok") public void setHdrOrderProbabilityInPercent(@Nullable String hdrOrderProbabilityInPercent)
The system uses the probability and net value of each item to calculate a total expected order value for the sales document. The expected order value appears in the double-line entry screen. The system proposes the probability for each item. You can change the value manually depending on the sales document category. A quotation contains two items: Item 1 has a value of $100 and a probability of 100% Item 2 has a value of $200 and a probability of 25% The system calculates the total probability as follows: ($100 x 100% + $200 x 25% ) divided by $300 = 50% In this case, the probability of this quotation resulting in a sales order is 50%. You can generate requirements from quotations. The probability of the quotation items affects how the system passes on requirements. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.
hdrOrderProbabilityInPercent - @Generated(value="lombok") public void setExpectedOrderNetAmount(@Nullable BigDecimal expectedOrderNetAmount)
expectedOrderNetAmount - @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 setIncotermsVersion(@Nullable String incotermsVersion)
incotermsVersion - @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 setPaymentMethod(@Nullable String paymentMethod)
If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules. For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
paymentMethod - @Generated(value="lombok") public void setOverallSDProcessStatus(@Nullable String overallSDProcessStatus)
The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
overallSDProcessStatus - @Generated(value="lombok") public void setTotalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
totalCreditCheckStatus - @Generated(value="lombok") public void setOverallSDDocumentRejectionSts(@Nullable String overallSDDocumentRejectionSts)
The system determines the total status from the status of all individual items in the sales document. The status message tells you whether the sales document has been partially or completely rejected or whether nothing has been rejected.
overallSDDocumentRejectionSts - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class VdmObject<SalesInquiry>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<SalesInquiry>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<SalesInquiry>Copyright © 2017 SAP SE. All rights reserved.