public class SalesSchedgAgrmt extends VdmEntity<SalesSchedgAgrmt>
Original entity name from the Odata EDM: A_SalesSchedgAgrmtType
Modifier and Type | Class and Description |
---|---|
static class |
SalesSchedgAgrmt.SalesSchedgAgrmtBuilder
Helper class to allow for fluent creation of SalesSchedgAgrmt instances.
|
Modifier and Type | Field and Description |
---|---|
static SalesSchedgAgrmtField<LocalDateTime> |
AGRMT_VALDTY_END_DATE
Use with available fluent helpers to apply the AgrmtValdtyEndDate field to query operations.
|
static SalesSchedgAgrmtField<LocalDateTime> |
AGRMT_VALDTY_START_DATE
Use with available fluent helpers to apply the AgrmtValdtyStartDate field to query operations.
|
static SalesSchedgAgrmtSelectable |
ALL_FIELDS
Selector for all available fields of SalesSchedgAgrmt.
|
static SalesSchedgAgrmtField<String> |
CREATED_BY_USER
Use with available fluent helpers to apply the CreatedByUser field to query operations.
|
static SalesSchedgAgrmtField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static SalesSchedgAgrmtField<LocalTime> |
CREATION_TIME
Use with available fluent helpers to apply the CreationTime field to query operations.
|
static SalesSchedgAgrmtField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static SalesSchedgAgrmtField<LocalDateTime> |
CUSTOMER_PURCHASE_ORDER_DATE
Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
|
static SalesSchedgAgrmtField<String> |
CUSTOMER_PURCHASE_ORDER_TYPE
Use with available fluent helpers to apply the CustomerPurchaseOrderType field to query operations.
|
static SalesSchedgAgrmtField<String> |
DELIV_SCHED_TYPE_MRP_RLVNCE_CODE
Use with available fluent helpers to apply the DelivSchedTypeMRPRlvnceCode field to query operations.
|
static SalesSchedgAgrmtField<String> |
DELIVERY_BLOCK_REASON
Use with available fluent helpers to apply the DeliveryBlockReason field to query operations.
|
static SalesSchedgAgrmtField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static SalesSchedgAgrmtField<String> |
FISCAL_PERIOD
Use with available fluent helpers to apply the FiscalPeriod field to query operations.
|
static SalesSchedgAgrmtField<String> |
FISCAL_YEAR
Use with available fluent helpers to apply the FiscalYear field to query operations.
|
static SalesSchedgAgrmtField<String> |
HEADER_BILLING_BLOCK_REASON
Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
|
static SalesSchedgAgrmtField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static SalesSchedgAgrmtField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static SalesSchedgAgrmtField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static SalesSchedgAgrmtField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static SalesSchedgAgrmtField<String> |
INCOTERMS_VERSION
Use with available fluent helpers to apply the IncotermsVersion field to query operations.
|
static SalesSchedgAgrmtField<LocalDateTime> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static SalesSchedgAgrmtField<ZonedDateTime> |
LAST_CHANGE_DATE_TIME
Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
|
static SalesSchedgAgrmtField<String> |
LAST_CHANGED_BY_USER
Use with available fluent helpers to apply the LastChangedByUser field to query operations.
|
static SalesSchedgAgrmtField<String> |
MATL_USAGE_INDICATOR
Use with available fluent helpers to apply the MatlUsageIndicator field to query operations.
|
static SalesSchedgAgrmtField<String> |
ORGANIZATION_DIVISION
Use with available fluent helpers to apply the OrganizationDivision field to query operations.
|
static SalesSchedgAgrmtField<String> |
OVERALL_BILLING_BLOCK_STATUS
Use with available fluent helpers to apply the OverallBillingBlockStatus field to query operations.
|
static SalesSchedgAgrmtField<String> |
OVERALL_DELIVERY_BLOCK_STATUS
Use with available fluent helpers to apply the OverallDeliveryBlockStatus field to query operations.
|
static SalesSchedgAgrmtField<String> |
OVERALL_DELIVERY_STATUS
Use with available fluent helpers to apply the OverallDeliveryStatus field to query operations.
|
static SalesSchedgAgrmtField<String> |
OVERALL_SD_DOCUMENT_REJECTION_STS
Use with available fluent helpers to apply the OverallSDDocumentRejectionSts field to query operations.
|
static SalesSchedgAgrmtField<String> |
OVERALL_SD_PROCESS_STATUS
Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
|
static SalesSchedgAgrmtField<String> |
PAYMENT_METHOD
Use with available fluent helpers to apply the PaymentMethod field to query operations.
|
static SalesSchedgAgrmtField<LocalDateTime> |
PRICING_DATE
Use with available fluent helpers to apply the PricingDate field to query operations.
|
static SalesSchedgAgrmtField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static SalesSchedgAgrmtField<String> |
SALES_DISTRICT
Use with available fluent helpers to apply the SalesDistrict field to query operations.
|
static SalesSchedgAgrmtField<String> |
SALES_GROUP
Use with available fluent helpers to apply the SalesGroup field to query operations.
|
static SalesSchedgAgrmtField<String> |
SALES_OFFICE
Use with available fluent helpers to apply the SalesOffice field to query operations.
|
static SalesSchedgAgrmtField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static SalesSchedgAgrmtField<LocalDateTime> |
SALES_SCHEDG_AGRMT_DATE
Use with available fluent helpers to apply the SalesSchedgAgrmtDate field to query operations.
|
static SalesSchedgAgrmtField<String> |
SALES_SCHEDG_AGRMT_TYPE
Use with available fluent helpers to apply the SalesSchedgAgrmtType field to query operations.
|
static SalesSchedgAgrmtField<String> |
SALES_SCHEDULING_AGREEMENT
Use with available fluent helpers to apply the SalesSchedulingAgreement field to query operations.
|
static SalesSchedgAgrmtField<String> |
SD_DOCUMENT_REASON
Use with available fluent helpers to apply the SDDocumentReason field to query operations.
|
static SalesSchedgAgrmtField<String> |
SHIPPING_CONDITION
Use with available fluent helpers to apply the ShippingCondition field to query operations.
|
static SalesSchedgAgrmtField<String> |
SHIPPING_TYPE
Use with available fluent helpers to apply the ShippingType field to query operations.
|
static SalesSchedgAgrmtField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
static SalesSchedgAgrmtLink<SalesSchedgAgrmtItem> |
TO_ITEM
Use with available fluent helpers to apply the to_Item navigation property to query operations.
|
static SalesSchedgAgrmtLink<SalesSchedgAgrmtPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static SalesSchedgAgrmtLink<SalesSchedgAgrmtPrcgElement> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static SalesSchedgAgrmtLink<SalesSchedgAgrmtText> |
TO_TEXT
Use with available fluent helpers to apply the to_Text navigation property to query operations.
|
static SalesSchedgAgrmtField<String> |
TOTAL_BLOCK_STATUS
Use with available fluent helpers to apply the TotalBlockStatus field to query operations.
|
static SalesSchedgAgrmtField<String> |
TOTAL_CREDIT_CHECK_STATUS
Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
|
static SalesSchedgAgrmtField<BigDecimal> |
TOTAL_NET_AMOUNT
Use with available fluent helpers to apply the TotalNetAmount field to query operations.
|
static SalesSchedgAgrmtField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SalesSchedgAgrmt() |
SalesSchedgAgrmt(String salesSchedulingAgreement,
String salesSchedgAgrmtType,
String createdByUser,
String lastChangedByUser,
LocalDateTime creationDate,
LocalTime creationTime,
LocalDateTime lastChangeDate,
ZonedDateTime lastChangeDateTime,
String salesOrganization,
String distributionChannel,
String organizationDivision,
String salesGroup,
String salesOffice,
String soldToParty,
LocalDateTime salesSchedgAgrmtDate,
String sDDocumentReason,
String purchaseOrderByCustomer,
String customerPurchaseOrderType,
LocalDateTime customerPurchaseOrderDate,
String salesDistrict,
BigDecimal totalNetAmount,
String transactionCurrency,
LocalDateTime pricingDate,
String shippingType,
String shippingCondition,
String incotermsVersion,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String deliveryBlockReason,
String delivSchedTypeMRPRlvnceCode,
LocalDateTime agrmtValdtyStartDate,
LocalDateTime agrmtValdtyEndDate,
String matlUsageIndicator,
String headerBillingBlockReason,
String customerPaymentTerms,
String paymentMethod,
String fiscalYear,
String fiscalPeriod,
String overallSDProcessStatus,
String overallSDDocumentRejectionSts,
String totalBlockStatus,
String overallDeliveryStatus,
String overallDeliveryBlockStatus,
String overallBillingBlockStatus,
String totalCreditCheckStatus,
List<SalesSchedgAgrmtItem> toItem,
List<SalesSchedgAgrmtPartner> toPartner,
List<SalesSchedgAgrmtPrcgElement> toPricingElement,
List<SalesSchedgAgrmtText> toText) |
Modifier and Type | Method and Description |
---|---|
void |
addItem(SalesSchedgAgrmtItem... entity)
Adds elements to the list of associated SalesSchedgAgrmtItem entities.
|
void |
addPartner(SalesSchedgAgrmtPartner... entity)
Adds elements to the list of associated SalesSchedgAgrmtPartner entities.
|
void |
addPricingElement(SalesSchedgAgrmtPrcgElement... entity)
Adds elements to the list of associated SalesSchedgAgrmtPrcgElement entities.
|
void |
addText(SalesSchedgAgrmtText... entity)
Adds elements to the list of associated SalesSchedgAgrmtText entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static SalesSchedgAgrmt.SalesSchedgAgrmtBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<SalesSchedgAgrmtItem> |
fetchItem()
Fetches the SalesSchedgAgrmtItem entities (one to many) associated with this entity.
|
List<SalesSchedgAgrmtPartner> |
fetchPartner()
Fetches the SalesSchedgAgrmtPartner entities (one to many) associated with this entity.
|
List<SalesSchedgAgrmtPrcgElement> |
fetchPricingElement()
Fetches the SalesSchedgAgrmtPrcgElement entities (one to many) associated with this entity.
|
List<SalesSchedgAgrmtText> |
fetchText()
Fetches the SalesSchedgAgrmtText entities (one to many) associated with this entity.
|
static <T> SalesSchedgAgrmtField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
LocalDateTime |
getAgrmtValdtyEndDate()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getAgrmtValdtyStartDate()
Constraints: Not nullable, Precision: 0
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
LocalTime |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
LocalDateTime |
getCustomerPurchaseOrderDate()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerPurchaseOrderType()
Constraints: Not nullable, Maximum length: 4
|
protected String |
getDefaultServicePath() |
String |
getDeliveryBlockReason()
Constraints: Not nullable, Maximum length: 2
|
String |
getDelivSchedTypeMRPRlvnceCode()
Constraints: Not nullable, Maximum length: 1
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
String |
getDistributionChannel()
Constraints: Not nullable, Maximum length: 2
|
protected String |
getEntityCollection() |
String |
getFiscalPeriod()
Constraints: Not nullable, Maximum length: 3
|
String |
getFiscalYear()
Constraints: Not nullable, Maximum length: 4
|
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
|
io.vavr.control.Option<List<SalesSchedgAgrmtItem>> |
getItemIfPresent()
Retrieval of associated SalesSchedgAgrmtItem entities (one to many).
|
List<SalesSchedgAgrmtItem> |
getItemOrFetch()
Retrieval of associated SalesSchedgAgrmtItem entities (one to many).
|
protected Map<String,Object> |
getKey() |
LocalDateTime |
getLastChangeDate()
Constraints: Not nullable, Precision: 0
|
ZonedDateTime |
getLastChangeDateTime()
Constraints: Not nullable, Precision: 7
|
String |
getLastChangedByUser()
Constraints: Not nullable, Maximum length: 12
|
String |
getMatlUsageIndicator()
Constraints: Not nullable, Maximum length: 3
|
String |
getOrganizationDivision()
Constraints: Not nullable, Maximum length: 2
|
String |
getOverallBillingBlockStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallDeliveryBlockStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallDeliveryStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallSDDocumentRejectionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallSDProcessStatus()
Constraints: Not nullable, Maximum length: 1
|
io.vavr.control.Option<List<SalesSchedgAgrmtPartner>> |
getPartnerIfPresent()
Retrieval of associated SalesSchedgAgrmtPartner entities (one to many).
|
List<SalesSchedgAgrmtPartner> |
getPartnerOrFetch()
Retrieval of associated SalesSchedgAgrmtPartner entities (one to many).
|
String |
getPaymentMethod()
Constraints: Not nullable, Maximum length: 1
|
LocalDateTime |
getPricingDate()
Constraints: Not nullable, Precision: 0
|
io.vavr.control.Option<List<SalesSchedgAgrmtPrcgElement>> |
getPricingElementIfPresent()
Retrieval of associated SalesSchedgAgrmtPrcgElement entities (one to many).
|
List<SalesSchedgAgrmtPrcgElement> |
getPricingElementOrFetch()
Retrieval of associated SalesSchedgAgrmtPrcgElement 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 |
getSalesOffice()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesOrganization()
Constraints: Not nullable, Maximum length: 4
|
LocalDateTime |
getSalesSchedgAgrmtDate()
Constraints: Not nullable, Precision: 0
|
String |
getSalesSchedgAgrmtType()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesSchedulingAgreement()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSDDocumentReason()
Constraints: Not nullable, Maximum length: 3
|
String |
getShippingCondition()
Constraints: Not nullable, Maximum length: 2
|
String |
getShippingType()
Constraints: Not nullable, Maximum length: 2
|
String |
getSoldToParty()
Constraints: Not nullable, Maximum length: 10
|
io.vavr.control.Option<List<SalesSchedgAgrmtText>> |
getTextIfPresent()
Retrieval of associated SalesSchedgAgrmtText entities (one to many).
|
List<SalesSchedgAgrmtText> |
getTextOrFetch()
Retrieval of associated SalesSchedgAgrmtText entities (one to many).
|
String |
getTotalBlockStatus()
Constraints: Not nullable, Maximum length: 1
|
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<SalesSchedgAgrmt> |
getType() |
int |
hashCode() |
void |
setAgrmtValdtyEndDate(LocalDateTime agrmtValdtyEndDate)
Constraints: Not nullable, Precision: 0
|
void |
setAgrmtValdtyStartDate(LocalDateTime agrmtValdtyStartDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setCustomerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerPurchaseOrderType(String customerPurchaseOrderType)
Constraints: Not nullable, Maximum length: 4
|
void |
setDeliveryBlockReason(String deliveryBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setDelivSchedTypeMRPRlvnceCode(String delivSchedTypeMRPRlvnceCode)
Constraints: Not nullable, Maximum length: 1
|
void |
setDistributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
void |
setFiscalPeriod(String fiscalPeriod)
Constraints: Not nullable, Maximum length: 3
|
void |
setFiscalYear(String fiscalYear)
Constraints: Not nullable, Maximum length: 4
|
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<SalesSchedgAgrmtItem> value)
Overwrites the list of associated SalesSchedgAgrmtItem entities for the loaded navigation property
to_Item.
|
void |
setLastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0
|
void |
setLastChangeDateTime(ZonedDateTime lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
void |
setLastChangedByUser(String lastChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setMatlUsageIndicator(String matlUsageIndicator)
Constraints: Not nullable, Maximum length: 3
|
void |
setOrganizationDivision(String organizationDivision)
Constraints: Not nullable, Maximum length: 2
|
void |
setOverallBillingBlockStatus(String overallBillingBlockStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallDeliveryBlockStatus(String overallDeliveryBlockStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallDeliveryStatus(String overallDeliveryStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallSDDocumentRejectionSts(String overallSDDocumentRejectionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallSDProcessStatus(String overallSDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setPartner(List<SalesSchedgAgrmtPartner> value)
Overwrites the list of associated SalesSchedgAgrmtPartner entities for the loaded navigation property
to_Partner.
|
void |
setPaymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1
|
void |
setPricingDate(LocalDateTime pricingDate)
Constraints: Not nullable, Precision: 0
|
void |
setPricingElement(List<SalesSchedgAgrmtPrcgElement> value)
Overwrites the list of associated SalesSchedgAgrmtPrcgElement 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 |
setSalesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesSchedgAgrmtDate(LocalDateTime salesSchedgAgrmtDate)
Constraints: Not nullable, Precision: 0
|
void |
setSalesSchedgAgrmtType(String salesSchedgAgrmtType)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesSchedulingAgreement(String salesSchedulingAgreement)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSDDocumentReason(String sDDocumentReason)
Constraints: Not nullable, Maximum length: 3
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setShippingCondition(String shippingCondition)
Constraints: Not nullable, Maximum length: 2
|
void |
setShippingType(String shippingType)
Constraints: Not nullable, Maximum length: 2
|
void |
setSoldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setText(List<SalesSchedgAgrmtText> value)
Overwrites the list of associated SalesSchedgAgrmtText entities for the loaded navigation property
to_Text.
|
void |
setTotalBlockStatus(String totalBlockStatus)
Constraints: Not nullable, Maximum length: 1
|
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
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final SalesSchedgAgrmtSelectable ALL_FIELDS
public static final SalesSchedgAgrmtField<String> SALES_SCHEDULING_AGREEMENT
public static final SalesSchedgAgrmtField<String> SALES_SCHEDG_AGRMT_TYPE
public static final SalesSchedgAgrmtField<String> CREATED_BY_USER
public static final SalesSchedgAgrmtField<String> LAST_CHANGED_BY_USER
public static final SalesSchedgAgrmtField<LocalDateTime> CREATION_DATE
public static final SalesSchedgAgrmtField<LocalTime> CREATION_TIME
public static final SalesSchedgAgrmtField<LocalDateTime> LAST_CHANGE_DATE
public static final SalesSchedgAgrmtField<ZonedDateTime> LAST_CHANGE_DATE_TIME
public static final SalesSchedgAgrmtField<String> SALES_ORGANIZATION
public static final SalesSchedgAgrmtField<String> DISTRIBUTION_CHANNEL
public static final SalesSchedgAgrmtField<String> ORGANIZATION_DIVISION
public static final SalesSchedgAgrmtField<String> SALES_GROUP
public static final SalesSchedgAgrmtField<String> SALES_OFFICE
public static final SalesSchedgAgrmtField<String> SOLD_TO_PARTY
public static final SalesSchedgAgrmtField<LocalDateTime> SALES_SCHEDG_AGRMT_DATE
public static final SalesSchedgAgrmtField<String> SD_DOCUMENT_REASON
public static final SalesSchedgAgrmtField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final SalesSchedgAgrmtField<String> CUSTOMER_PURCHASE_ORDER_TYPE
public static final SalesSchedgAgrmtField<LocalDateTime> CUSTOMER_PURCHASE_ORDER_DATE
public static final SalesSchedgAgrmtField<String> SALES_DISTRICT
public static final SalesSchedgAgrmtField<BigDecimal> TOTAL_NET_AMOUNT
public static final SalesSchedgAgrmtField<String> TRANSACTION_CURRENCY
public static final SalesSchedgAgrmtField<LocalDateTime> PRICING_DATE
public static final SalesSchedgAgrmtField<String> SHIPPING_TYPE
public static final SalesSchedgAgrmtField<String> SHIPPING_CONDITION
public static final SalesSchedgAgrmtField<String> INCOTERMS_VERSION
public static final SalesSchedgAgrmtField<String> INCOTERMS_CLASSIFICATION
public static final SalesSchedgAgrmtField<String> INCOTERMS_TRANSFER_LOCATION
public static final SalesSchedgAgrmtField<String> INCOTERMS_LOCATION1
public static final SalesSchedgAgrmtField<String> INCOTERMS_LOCATION2
public static final SalesSchedgAgrmtField<String> DELIVERY_BLOCK_REASON
public static final SalesSchedgAgrmtField<String> DELIV_SCHED_TYPE_MRP_RLVNCE_CODE
public static final SalesSchedgAgrmtField<LocalDateTime> AGRMT_VALDTY_START_DATE
public static final SalesSchedgAgrmtField<LocalDateTime> AGRMT_VALDTY_END_DATE
public static final SalesSchedgAgrmtField<String> MATL_USAGE_INDICATOR
public static final SalesSchedgAgrmtField<String> HEADER_BILLING_BLOCK_REASON
public static final SalesSchedgAgrmtField<String> CUSTOMER_PAYMENT_TERMS
public static final SalesSchedgAgrmtField<String> PAYMENT_METHOD
public static final SalesSchedgAgrmtField<String> FISCAL_YEAR
public static final SalesSchedgAgrmtField<String> FISCAL_PERIOD
public static final SalesSchedgAgrmtField<String> OVERALL_SD_PROCESS_STATUS
public static final SalesSchedgAgrmtField<String> OVERALL_SD_DOCUMENT_REJECTION_STS
public static final SalesSchedgAgrmtField<String> TOTAL_BLOCK_STATUS
public static final SalesSchedgAgrmtField<String> OVERALL_DELIVERY_STATUS
public static final SalesSchedgAgrmtField<String> OVERALL_DELIVERY_BLOCK_STATUS
public static final SalesSchedgAgrmtField<String> OVERALL_BILLING_BLOCK_STATUS
public static final SalesSchedgAgrmtField<String> TOTAL_CREDIT_CHECK_STATUS
public static final SalesSchedgAgrmtLink<SalesSchedgAgrmtItem> TO_ITEM
public static final SalesSchedgAgrmtLink<SalesSchedgAgrmtPartner> TO_PARTNER
public static final SalesSchedgAgrmtLink<SalesSchedgAgrmtPrcgElement> TO_PRICING_ELEMENT
public static final SalesSchedgAgrmtLink<SalesSchedgAgrmtText> TO_TEXT
public SalesSchedgAgrmt()
public SalesSchedgAgrmt(@Nullable String salesSchedulingAgreement, @Nullable String salesSchedgAgrmtType, @Nullable String createdByUser, @Nullable String lastChangedByUser, @Nullable LocalDateTime creationDate, @Nullable LocalTime creationTime, @Nullable LocalDateTime lastChangeDate, @Nullable ZonedDateTime lastChangeDateTime, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String organizationDivision, @Nullable String salesGroup, @Nullable String salesOffice, @Nullable String soldToParty, @Nullable LocalDateTime salesSchedgAgrmtDate, @Nullable String sDDocumentReason, @Nullable String purchaseOrderByCustomer, @Nullable String customerPurchaseOrderType, @Nullable LocalDateTime customerPurchaseOrderDate, @Nullable String salesDistrict, @Nullable BigDecimal totalNetAmount, @Nullable String transactionCurrency, @Nullable LocalDateTime pricingDate, @Nullable String shippingType, @Nullable String shippingCondition, @Nullable String incotermsVersion, @Nullable String incotermsClassification, @Nullable String incotermsTransferLocation, @Nullable String incotermsLocation1, @Nullable String incotermsLocation2, @Nullable String deliveryBlockReason, @Nullable String delivSchedTypeMRPRlvnceCode, @Nullable LocalDateTime agrmtValdtyStartDate, @Nullable LocalDateTime agrmtValdtyEndDate, @Nullable String matlUsageIndicator, @Nullable String headerBillingBlockReason, @Nullable String customerPaymentTerms, @Nullable String paymentMethod, @Nullable String fiscalYear, @Nullable String fiscalPeriod, @Nullable String overallSDProcessStatus, @Nullable String overallSDDocumentRejectionSts, @Nullable String totalBlockStatus, @Nullable String overallDeliveryStatus, @Nullable String overallDeliveryBlockStatus, @Nullable String overallBillingBlockStatus, @Nullable String totalCreditCheckStatus, List<SalesSchedgAgrmtItem> toItem, List<SalesSchedgAgrmtPartner> toPartner, List<SalesSchedgAgrmtPrcgElement> toPricingElement, List<SalesSchedgAgrmtText> toText)
@Nonnull public Class<SalesSchedgAgrmt> getType()
getType
in class VdmObject<SalesSchedgAgrmt>
public void setSalesSchedulingAgreement(@Nullable String salesSchedulingAgreement)
Original property name from the Odata EDM: SalesSchedulingAgreement
salesSchedulingAgreement
- The number that uniquely identifies the sales scheduling agreement.public void setSalesSchedgAgrmtType(@Nullable String salesSchedgAgrmtType)
Original property name from the Odata EDM: SalesSchedgAgrmtType
salesSchedgAgrmtType
- A classification that distinguishes between different kinds of sales scheduling agreements.public void setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser
- Name of Person Who Created Objectpublic void setLastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
lastChangedByUser
- User Who Last Changed the Business Documentpublic void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate
- Date on Which Record Was Createdpublic void setCreationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
creationTime
- Time at Which Record Was Createdpublic void setLastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
lastChangeDate
- Date of Last Changepublic void setLastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: 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 STAMPA UTC time stamp in short form is also available.
lastChangeDateTime
- The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).public void setSalesOrganization(@Nullable String salesOrganization)
Original property name from the Odata EDM: 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
- An organizational unit responsible for the sale of certain products or services. The responsibility of
a sales organization may include legal liability for products and customer claims.public void setDistributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: 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
- The way in which products or services reach the customer. Typical examples of distribution channels
are wholesale, retail, or direct sales.public void setOrganizationDivision(@Nullable String organizationDivision)
Original property name from the Odata EDM: 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
- A way of grouping materials, products, or services. The system uses divisions to determine the sales
areas and the business areas for a material, product, or service.public void setSalesGroup(@Nullable String salesGroup)
Original property name from the Odata EDM: 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
- A group of sales people who are responsible for processing sales of certain products or services.public void setSalesOffice(@Nullable String salesOffice)
Original property name from the Odata EDM: 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
- A physical location (for example, a branch office) that has responsibility for the sale of certain
products or services within a given geographical area.public void setSoldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
soldToParty
- Sold-to Partypublic void setSalesSchedgAgrmtDate(@Nullable LocalDateTime salesSchedgAgrmtDate)
Original property name from the Odata EDM: SalesSchedgAgrmtDate
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.
salesSchedgAgrmtDate
- The date on which you want the sales document (the sales order, for example) to become effective for
sales management purposes.public void setSDDocumentReason(@Nullable String sDDocumentReason)
Original property name from the Odata EDM: 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
- Indicates the reason for creating the sales document.public void setPurchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
purchaseOrderByCustomer
- Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a
purchase order).public void setCustomerPurchaseOrderType(@Nullable String customerPurchaseOrderType)
Original property name from the Odata EDM: 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
- The way in which the sales document (the inquiry or sales order, for example) arrives from the
customer.public void setCustomerPurchaseOrderDate(@Nullable LocalDateTime customerPurchaseOrderDate)
Original property name from the Odata EDM: CustomerPurchaseOrderDate
customerPurchaseOrderDate
- The date that appears on the customer's purchase order. This date can be, for example, the date on
which the customer created the purchase order.public void setSalesDistrict(@Nullable String salesDistrict)
Original property name from the Odata EDM: 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
- A geographical sales district or region.public void setTotalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
totalNetAmount
- The total value of all items in the sales document, after any discounts and surcharges are taken into
account. The value is expressed in the document currency.public void setTransactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
transactionCurrency
- The currency that applies to the document (for example, to a sales order or an invoice).public void setPricingDate(@Nullable LocalDateTime pricingDate)
Original property name from the Odata EDM: PricingDate
You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
pricingDate
- The date that determines date-related pricing elements, such as conditions and foreign exchange rate.public void setShippingType(@Nullable String shippingType)
Original property name from the Odata EDM: ShippingType
During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
shippingType
- Shipping type (for example, by road or rail) that has been selected for the transportation of the
goods for the shipment legs.public void setShippingCondition(@Nullable String shippingCondition)
Original property name from the Odata EDM: ShippingCondition
You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
shippingCondition
- General shipping strategy for the delivery of goods from the vendor to the customer.public void setIncotermsVersion(@Nullable String incotermsVersion)
Original property name from the Odata EDM: IncotermsVersion
incotermsVersion
- An incoterms version is an edition containing a list of international terms for transportation that is
defined by the International Chamber of Commerce (ICC).public void setIncotermsClassification(@Nullable String incotermsClassification)
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
incotermsClassification
- Commonly used trading terms that comply with the standards established by the International Chamber of
Commerce (ICC).public void setIncotermsTransferLocation(@Nullable String incotermsTransferLocation)
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
incotermsTransferLocation
- Additional information for the primary Incoterm.public void setIncotermsLocation1(@Nullable String incotermsLocation1)
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
incotermsLocation1
- Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:public void setIncotermsLocation2(@Nullable String incotermsLocation2)
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
incotermsLocation2
- Provides additional information for the Incoterms. This field is only available for C-Clauses (if
customized appropriately). Note the following for the incoterms versions below:public void setDeliveryBlockReason(@Nullable String deliveryBlockReason)
Original property name from the Odata EDM: DeliveryBlockReason
The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
deliveryBlockReason
- Indicates if an entire sales document (a sales order, for example) is blocked for delivery.public void setDelivSchedTypeMRPRlvnceCode(@Nullable String delivSchedTypeMRPRlvnceCode)
Original property name from the Odata EDM: DelivSchedTypeMRPRlvnceCode
The SAP System contains the following requirements planning settings:No delivery schedules are used.This indicator is default for all sales documents without delivery schedules.Only forecast delivery schedules are relevant for requirements planning. Forecast delivery schedules and JIT (just-in-time) delivery schedules are relevant for delivery, depending on their validity.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning and delivery, depending on their validity.Only forecast delivery schedules are relevant for requirements planning. Only JIT delivery schedules are relevant for delivery.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning, depending on their validity. Only JIT delivery schedules are relevant for delivery.JIT delivery schedules are not used.You have set material requirements planning indicator B (Forecast and JIT delivery schedules are relevant for requirements planning and delivery) in the scheduling agreement header. The forecast delivery schedule contains schedule lines from January 1 up to March 31. The JIT delivery schedule horizon covers the period up to January 31. The JIT delivery schedule is relevant for requirements planning and delivery within this horizon. As of February 1, the forecast delivery schedule is relevant for requirements planning and delivery.
delivSchedTypeMRPRlvnceCode
- Specifies whether forecast delivery schedules or JIT delivery schedules are relevant for planning
and/or delivery.public void setAgrmtValdtyStartDate(@Nullable LocalDateTime agrmtValdtyStartDate)
Original property name from the Odata EDM: AgrmtValdtyStartDate
agrmtValdtyStartDate
- Valid-from Datepublic void setAgrmtValdtyEndDate(@Nullable LocalDateTime agrmtValdtyEndDate)
Original property name from the Odata EDM: AgrmtValdtyEndDate
agrmtValdtyEndDate
- Valid-to Datepublic void setMatlUsageIndicator(@Nullable String matlUsageIndicator)
Original property name from the Odata EDM: MatlUsageIndicator
The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.The same material, but with different uses, can be sold to the same customer in separate items or orders.Enter whether the material is:A spare, or replacement partA samplePart of a series, used in repetitive manufacturing
matlUsageIndicator
- Defines how the material is used.public void setHeaderBillingBlockReason(@Nullable String headerBillingBlockReason)
Original property name from the Odata EDM: 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
- Indicates if the entire sales document is blocked for billing.public void setCustomerPaymentTerms(@Nullable String customerPaymentTerms)
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
customerPaymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setPaymentMethod(@Nullable String paymentMethod)
Original property name from the Odata EDM: 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
- Payment method with which this item is to be paid.public void setFiscalYear(@Nullable String fiscalYear)
Original property name from the Odata EDM: FiscalYear
fiscalYear
- Period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The
fiscal year can be the same as the calendar year, but does not have to be.public void setFiscalPeriod(@Nullable String fiscalPeriod)
Original property name from the Odata EDM: FiscalPeriod
Every business transaction is allocated to a posting period. The monthly debits and credits of the different business transactions are accumulated per posting period.Examples of period classifications:Per calendar month -> 12 posting periodsEvery 4 weeks -> 13 posting periodsWeekly -> 52 or 53 posting periods
fiscalPeriod
- A posting period is a self-contained part of a fiscal year.public void setOverallSDProcessStatus(@Nullable String overallSDProcessStatus)
Original property name from the Odata EDM: 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
- The processing status of the entire sales document.public void setOverallSDDocumentRejectionSts(@Nullable String overallSDDocumentRejectionSts)
Original property name from the Odata EDM: 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
- Displays the rejection status of the entire sales document.public void setTotalBlockStatus(@Nullable String totalBlockStatus)
Original property name from the Odata EDM: TotalBlockStatus
The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
totalBlockStatus
- Overall blocked status.public void setOverallDeliveryStatus(@Nullable String overallDeliveryStatus)
Original property name from the Odata EDM: OverallDeliveryStatus
overallDeliveryStatus
- The delivery status of the sales document.public void setOverallDeliveryBlockStatus(@Nullable String overallDeliveryBlockStatus)
Original property name from the Odata EDM: OverallDeliveryBlockStatus
Item delivery block status + Document header delivery block + user status for header
overallDeliveryBlockStatus
- The value of this field is calculated using the following values:public void setOverallBillingBlockStatus(@Nullable String overallBillingBlockStatus)
Original property name from the Odata EDM: OverallBillingBlockStatus
Billing block status of item + sales document billing block + user status header
overallBillingBlockStatus
- The value of the overall billing block field is calculated using the:public void setTotalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
Original property name from the Odata EDM: TotalCreditCheckStatus
totalCreditCheckStatus
- Overall Status of Credit Checksprotected String getEntityCollection()
getEntityCollection
in class VdmEntity<SalesSchedgAgrmt>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<SalesSchedgAgrmt>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SalesSchedgAgrmt>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SalesSchedgAgrmt>
@Nonnull public static <T> SalesSchedgAgrmtField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> SalesSchedgAgrmtField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<SalesSchedgAgrmt>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<SalesSchedgAgrmt>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<SalesSchedgAgrmt>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
getDefaultServicePath
in class VdmEntity<SalesSchedgAgrmt>
@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SalesSchedgAgrmt>
@Nonnull public List<SalesSchedgAgrmtItem> 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.@Nonnull public List<SalesSchedgAgrmtItem> getItemOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Item of a queried SalesSchedgAgrmt is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SalesSchedgAgrmtItem>> getItemIfPresent()
If the navigation property for an entity SalesSchedgAgrmt has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state empty
is returned.public void setItem(@Nonnull List<SalesSchedgAgrmtItem> value)
If the navigation property to_Item of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtItem entities.public void addItem(SalesSchedgAgrmtItem... entity)
If the navigation property to_Item of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtItem entities.@Nonnull public List<SalesSchedgAgrmtPartner> fetchPartner() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<SalesSchedgAgrmtPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried SalesSchedgAgrmt is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SalesSchedgAgrmtPartner>> getPartnerIfPresent()
If the navigation property for an entity SalesSchedgAgrmt has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setPartner(@Nonnull List<SalesSchedgAgrmtPartner> value)
If the navigation property to_Partner of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPartner entities.public void addPartner(SalesSchedgAgrmtPartner... entity)
If the navigation property to_Partner of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPartner entities.@Nonnull public List<SalesSchedgAgrmtPrcgElement> fetchPricingElement() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<SalesSchedgAgrmtPrcgElement> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried SalesSchedgAgrmt is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SalesSchedgAgrmtPrcgElement>> getPricingElementIfPresent()
If the navigation property for an entity SalesSchedgAgrmt has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setPricingElement(@Nonnull List<SalesSchedgAgrmtPrcgElement> value)
If the navigation property to_PricingElement of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPrcgElement entities.public void addPricingElement(SalesSchedgAgrmtPrcgElement... entity)
If the navigation property to_PricingElement of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtPrcgElement entities.@Nonnull public List<SalesSchedgAgrmtText> fetchText() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<SalesSchedgAgrmtText> getTextOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Text of a queried SalesSchedgAgrmt is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SalesSchedgAgrmtText>> getTextIfPresent()
If the navigation property for an entity SalesSchedgAgrmt has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state empty
is returned.public void setText(@Nonnull List<SalesSchedgAgrmtText> value)
If the navigation property to_Text of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtText entities.public void addText(SalesSchedgAgrmtText... entity)
If the navigation property to_Text of a queried SalesSchedgAgrmt 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 SalesSchedgAgrmtText entities.public static SalesSchedgAgrmt.SalesSchedgAgrmtBuilder builder()
@Nullable public String getSalesSchedulingAgreement()
Original property name from the Odata EDM: SalesSchedulingAgreement
@Nullable public String getSalesSchedgAgrmtType()
Original property name from the Odata EDM: SalesSchedgAgrmtType
@Nullable public String getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public String getLastChangedByUser()
Original property name from the Odata EDM: LastChangedByUser
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public LocalTime getCreationTime()
Original property name from the Odata EDM: CreationTime
@Nullable public LocalDateTime getLastChangeDate()
Original property name from the Odata EDM: LastChangeDate
@Nullable public ZonedDateTime getLastChangeDateTime()
Original property name from the Odata EDM: 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 STAMPA UTC time stamp in short form is also available.
@Nullable public String getSalesOrganization()
Original property name from the Odata EDM: 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.
@Nullable public String getDistributionChannel()
Original property name from the Odata EDM: 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.
@Nullable public String getOrganizationDivision()
Original property name from the Odata EDM: 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.
@Nullable public String getSalesGroup()
Original property name from the Odata EDM: 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.
@Nullable public String getSalesOffice()
Original property name from the Odata EDM: 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.
@Nullable public String getSoldToParty()
Original property name from the Odata EDM: SoldToParty
@Nullable public LocalDateTime getSalesSchedgAgrmtDate()
Original property name from the Odata EDM: SalesSchedgAgrmtDate
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 public String getSDDocumentReason()
Original property name from the Odata EDM: 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.
@Nullable public String getPurchaseOrderByCustomer()
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
@Nullable public String getCustomerPurchaseOrderType()
Original property name from the Odata EDM: 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.
@Nullable public LocalDateTime getCustomerPurchaseOrderDate()
Original property name from the Odata EDM: CustomerPurchaseOrderDate
@Nullable public String getSalesDistrict()
Original property name from the Odata EDM: 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.
@Nullable public BigDecimal getTotalNetAmount()
Original property name from the Odata EDM: TotalNetAmount
@Nullable public String getTransactionCurrency()
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable public LocalDateTime getPricingDate()
Original property name from the Odata EDM: PricingDate
You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
@Nullable public String getShippingType()
Original property name from the Odata EDM: ShippingType
During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
@Nullable public String getShippingCondition()
Original property name from the Odata EDM: ShippingCondition
You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
@Nullable public String getIncotermsVersion()
Original property name from the Odata EDM: IncotermsVersion
@Nullable public String getIncotermsClassification()
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
@Nullable public String getIncotermsTransferLocation()
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
@Nullable public String getIncotermsLocation1()
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
@Nullable public String getIncotermsLocation2()
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
@Nullable public String getDeliveryBlockReason()
Original property name from the Odata EDM: DeliveryBlockReason
The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place.
@Nullable public String getDelivSchedTypeMRPRlvnceCode()
Original property name from the Odata EDM: DelivSchedTypeMRPRlvnceCode
The SAP System contains the following requirements planning settings:No delivery schedules are used.This indicator is default for all sales documents without delivery schedules.Only forecast delivery schedules are relevant for requirements planning. Forecast delivery schedules and JIT (just-in-time) delivery schedules are relevant for delivery, depending on their validity.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning and delivery, depending on their validity.Only forecast delivery schedules are relevant for requirements planning. Only JIT delivery schedules are relevant for delivery.Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning, depending on their validity. Only JIT delivery schedules are relevant for delivery.JIT delivery schedules are not used.You have set material requirements planning indicator B (Forecast and JIT delivery schedules are relevant for requirements planning and delivery) in the scheduling agreement header. The forecast delivery schedule contains schedule lines from January 1 up to March 31. The JIT delivery schedule horizon covers the period up to January 31. The JIT delivery schedule is relevant for requirements planning and delivery within this horizon. As of February 1, the forecast delivery schedule is relevant for requirements planning and delivery.
@Nullable public LocalDateTime getAgrmtValdtyStartDate()
Original property name from the Odata EDM: AgrmtValdtyStartDate
@Nullable public LocalDateTime getAgrmtValdtyEndDate()
Original property name from the Odata EDM: AgrmtValdtyEndDate
@Nullable public String getMatlUsageIndicator()
Original property name from the Odata EDM: MatlUsageIndicator
The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.The same material, but with different uses, can be sold to the same customer in separate items or orders.Enter whether the material is:A spare, or replacement partA samplePart of a series, used in repetitive manufacturing
@Nullable public String getHeaderBillingBlockReason()
Original property name from the Odata EDM: 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.
@Nullable public String getCustomerPaymentTerms()
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
@Nullable public String getPaymentMethod()
Original property name from the Odata EDM: 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.
@Nullable public String getFiscalYear()
Original property name from the Odata EDM: FiscalYear
@Nullable public String getFiscalPeriod()
Original property name from the Odata EDM: FiscalPeriod
Every business transaction is allocated to a posting period. The monthly debits and credits of the different business transactions are accumulated per posting period.Examples of period classifications:Per calendar month -> 12 posting periodsEvery 4 weeks -> 13 posting periodsWeekly -> 52 or 53 posting periods
@Nullable public String getOverallSDProcessStatus()
Original property name from the Odata EDM: 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.
@Nullable public String getOverallSDDocumentRejectionSts()
Original property name from the Odata EDM: 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.
@Nullable public String getTotalBlockStatus()
Original property name from the Odata EDM: TotalBlockStatus
The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status
@Nullable public String getOverallDeliveryStatus()
Original property name from the Odata EDM: OverallDeliveryStatus
@Nullable public String getOverallDeliveryBlockStatus()
Original property name from the Odata EDM: OverallDeliveryBlockStatus
Item delivery block status + Document header delivery block + user status for header
@Nullable public String getOverallBillingBlockStatus()
Original property name from the Odata EDM: OverallBillingBlockStatus
Billing block status of item + sales document billing block + user status header
@Nullable public String getTotalCreditCheckStatus()
Original property name from the Odata EDM: TotalCreditCheckStatus
public String toString()
toString
in class VdmObject<SalesSchedgAgrmt>
public boolean equals(Object o)
equals
in class VdmObject<SalesSchedgAgrmt>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<SalesSchedgAgrmt>
public int hashCode()
hashCode
in class VdmObject<SalesSchedgAgrmt>
Copyright © 2019 SAP SE. All rights reserved.