public class SalesContractItem extends VdmEntity<SalesContractItem>
Original entity name from the Odata EDM: A_SalesContractItemType
Modifier and Type | Class and Description |
---|---|
static class |
SalesContractItem.SalesContractItemBuilder
Helper class to allow for fluent creation of SalesContractItem instances.
|
Modifier and Type | Field and Description |
---|---|
static SalesContractItemSelectable |
ALL_FIELDS
Selector for all available fields of SalesContractItem.
|
static SalesContractItemField<String> |
BATCH
Use with available fluent helpers to apply the Batch field to query operations.
|
static SalesContractItemField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static SalesContractItemField<String> |
HIGHER_LEVEL_ITEM
Use with available fluent helpers to apply the HigherLevelItem field to query operations.
|
static SalesContractItemField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static SalesContractItemField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static SalesContractItemField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static SalesContractItemField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static SalesContractItemField<String> |
ITEM_BILLING_BLOCK_REASON
Use with available fluent helpers to apply the ItemBillingBlockReason field to query operations.
|
static SalesContractItemField<BigDecimal> |
ITEM_GROSS_WEIGHT
Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
|
static SalesContractItemField<BigDecimal> |
ITEM_NET_WEIGHT
Use with available fluent helpers to apply the ItemNetWeight field to query operations.
|
static SalesContractItemField<BigDecimal> |
ITEM_VOLUME
Use with available fluent helpers to apply the ItemVolume field to query operations.
|
static SalesContractItemField<String> |
ITEM_VOLUME_UNIT
Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
|
static SalesContractItemField<String> |
ITEM_WEIGHT_UNIT
Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
|
static SalesContractItemField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static SalesContractItemField<String> |
MATERIAL_BY_CUSTOMER
Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
|
static SalesContractItemField<String> |
MATERIAL_GROUP
Use with available fluent helpers to apply the MaterialGroup field to query operations.
|
static SalesContractItemField<String> |
MATERIAL_PRICING_GROUP
Use with available fluent helpers to apply the MaterialPricingGroup field to query operations.
|
static SalesContractItemField<BigDecimal> |
NET_AMOUNT
Use with available fluent helpers to apply the NetAmount field to query operations.
|
static SalesContractItemField<String> |
NMBR_OF_SALES_CONTRACT_VALDTY_PERD
Use with available fluent helpers to apply the NmbrOfSalesContractValdtyPerd field to query operations.
|
static SalesContractItemField<BigDecimal> |
OUTLINE_AGREEMENT_TARGET_AMOUNT
Use with available fluent helpers to apply the OutlineAgreementTargetAmount field to query operations.
|
static SalesContractItemField<LocalDateTime> |
PRICING_DATE
Use with available fluent helpers to apply the PricingDate field to query operations.
|
static SalesContractItemField<String> |
PRODUCTION_PLANT
Use with available fluent helpers to apply the ProductionPlant field to query operations.
|
static SalesContractItemField<String> |
PROFIT_CENTER
Use with available fluent helpers to apply the ProfitCenter field to query operations.
|
static SalesContractItemField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static SalesContractItemField<String> |
REFERENCE_SD_DOCUMENT
Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
|
static SalesContractItemField<String> |
REFERENCE_SD_DOCUMENT_ITEM
Use with available fluent helpers to apply the ReferenceSDDocumentItem field to query operations.
|
static SalesContractItemField<BigDecimal> |
REQUESTED_QUANTITY
Use with available fluent helpers to apply the RequestedQuantity field to query operations.
|
static SalesContractItemField<String> |
REQUESTED_QUANTITY_UNIT
Use with available fluent helpers to apply the RequestedQuantityUnit field to query operations.
|
static SalesContractItemField<String> |
SALES_CONTRACT
Use with available fluent helpers to apply the SalesContract field to query operations.
|
static SalesContractItemField<String> |
SALES_CONTRACT_FOLLOW_UP_ACTION
Use with available fluent helpers to apply the SalesContractFollowUpAction field to query operations.
|
static SalesContractItemField<String> |
SALES_CONTRACT_ITEM
Use with available fluent helpers to apply the SalesContractItem field to query operations.
|
static SalesContractItemField<String> |
SALES_CONTRACT_ITEM_CATEGORY
Use with available fluent helpers to apply the SalesContractItemCategory field to query operations.
|
static SalesContractItemField<String> |
SALES_CONTRACT_ITEM_TEXT
Use with available fluent helpers to apply the SalesContractItemText field to query operations.
|
static SalesContractItemField<LocalDateTime> |
SALES_CONTRACT_SIGNED_DATE
Use with available fluent helpers to apply the SalesContractSignedDate field to query operations.
|
static SalesContractItemField<LocalDateTime> |
SALES_CONTRACT_VALIDITY_END_DATE
Use with available fluent helpers to apply the SalesContractValidityEndDate field to query operations.
|
static SalesContractItemField<String> |
SALES_CONTRACT_VALIDITY_PERD_CAT
Use with available fluent helpers to apply the SalesContractValidityPerdCat field to query operations.
|
static SalesContractItemField<String> |
SALES_CONTRACT_VALIDITY_PERD_UNIT
Use with available fluent helpers to apply the SalesContractValidityPerdUnit field to query operations.
|
static SalesContractItemField<LocalDateTime> |
SALES_CONTRACT_VALIDITY_START_DATE
Use with available fluent helpers to apply the SalesContractValidityStartDate field to query operations.
|
static SalesContractItemField<String> |
SALES_DOCUMENT_RJCN_REASON
Use with available fluent helpers to apply the SalesDocumentRjcnReason field to query operations.
|
static SalesContractItemField<String> |
SD_PROCESS_STATUS
Use with available fluent helpers to apply the SDProcessStatus field to query operations.
|
static SalesContractItemField<String> |
SHIPPING_POINT
Use with available fluent helpers to apply the ShippingPoint field to query operations.
|
static SalesContractItemField<LocalDateTime> |
SLS_CONTRACT_FOLLOW_UP_ACTION_DATE
Use with available fluent helpers to apply the SlsContractFollowUpActionDate field to query operations.
|
static SalesContractItemField<String> |
STORAGE_LOCATION
Use with available fluent helpers to apply the StorageLocation field to query operations.
|
static SalesContractItemLink<SalesContractItemPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static SalesContractItemLink<SalesContractItemPrcgElmnt> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static SalesContractItemOneToOneLink<SalesContract> |
TO_SALES_CONTRACT
Use with available fluent helpers to apply the to_SalesContract navigation property to query operations.
|
static SalesContractItemField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
static SalesContractItemField<String> |
WBS_ELEMENT
Use with available fluent helpers to apply the WBSElement field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SalesContractItem() |
SalesContractItem(String salesContract,
String salesContractItem,
String higherLevelItem,
String salesContractItemCategory,
String salesContractItemText,
String purchaseOrderByCustomer,
String material,
String materialByCustomer,
LocalDateTime pricingDate,
BigDecimal requestedQuantity,
String requestedQuantityUnit,
BigDecimal itemGrossWeight,
BigDecimal itemNetWeight,
String itemWeightUnit,
BigDecimal itemVolume,
String itemVolumeUnit,
BigDecimal outlineAgreementTargetAmount,
String transactionCurrency,
BigDecimal netAmount,
String materialGroup,
String materialPricingGroup,
String batch,
String productionPlant,
String storageLocation,
String shippingPoint,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String customerPaymentTerms,
String salesDocumentRjcnReason,
String itemBillingBlockReason,
String wBSElement,
String profitCenter,
String referenceSDDocument,
String referenceSDDocumentItem,
String sDProcessStatus,
LocalDateTime salesContractValidityStartDate,
LocalDateTime salesContractValidityEndDate,
String nmbrOfSalesContractValdtyPerd,
String salesContractValidityPerdUnit,
String salesContractValidityPerdCat,
LocalDateTime salesContractSignedDate,
String salesContractFollowUpAction,
LocalDateTime slsContractFollowUpActionDate,
List<SalesContractItemPartner> toPartner,
List<SalesContractItemPrcgElmnt> toPricingElement,
SalesContract toSalesContract) |
Modifier and Type | Method and Description |
---|---|
void |
addPartner(SalesContractItemPartner... entity)
Adds elements to the list of associated SalesContractItemPartner entities.
|
void |
addPricingElement(SalesContractItemPrcgElmnt... entity)
Adds elements to the list of associated SalesContractItemPrcgElmnt entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static SalesContractItem.SalesContractItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<SalesContractItemPartner> |
fetchPartner()
Fetches the SalesContractItemPartner entities (one to many) associated with this entity.
|
List<SalesContractItemPrcgElmnt> |
fetchPricingElement()
Fetches the SalesContractItemPrcgElmnt entities (one to many) associated with this entity.
|
SalesContract |
fetchSalesContract()
Fetches the SalesContract entity (one to one) associated with this entity.
|
static <T> SalesContractItemField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getBatch()
Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getHigherLevelItem()
Constraints: Not nullable, Maximum length: 6
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsLocation1()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsLocation2()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28
|
String |
getItemBillingBlockReason()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getItemGrossWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
BigDecimal |
getItemNetWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
BigDecimal |
getItemVolume()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getItemVolumeUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getItemWeightUnit()
Constraints: Not nullable, Maximum length: 3
|
protected Map<String,Object> |
getKey() |
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterialByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9
|
String |
getMaterialPricingGroup()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getNmbrOfSalesContractValdtyPerd()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getOutlineAgreementTargetAmount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
io.vavr.control.Option<List<SalesContractItemPartner>> |
getPartnerIfPresent()
Retrieval of associated SalesContractItemPartner entities (one to many).
|
List<SalesContractItemPartner> |
getPartnerOrFetch()
Retrieval of associated SalesContractItemPartner entities (one to many).
|
LocalDateTime |
getPricingDate()
Constraints: Not nullable, Precision: 0
|
io.vavr.control.Option<List<SalesContractItemPrcgElmnt>> |
getPricingElementIfPresent()
Retrieval of associated SalesContractItemPrcgElmnt entities (one to many).
|
List<SalesContractItemPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated SalesContractItemPrcgElmnt entities (one to many).
|
String |
getProductionPlant()
Constraints: Not nullable, Maximum length: 4
|
String |
getProfitCenter()
Constraints: Not nullable, Maximum length: 10
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getReferenceSDDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getReferenceSDDocumentItem()
Constraints: Not nullable, Maximum length: 6
|
BigDecimal |
getRequestedQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getRequestedQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesContract()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSalesContractFollowUpAction()
Constraints: Not nullable, Maximum length: 4
|
io.vavr.control.Option<SalesContract> |
getSalesContractIfPresent()
Retrieval of associated SalesContract entity (one to one).
|
String |
getSalesContractItem()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getSalesContractItemCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesContractItemText()
Constraints: Not nullable, Maximum length: 40
|
SalesContract |
getSalesContractOrFetch()
Retrieval of associated SalesContract entity (one to one).
|
LocalDateTime |
getSalesContractSignedDate()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getSalesContractValidityEndDate()
Constraints: Not nullable, Precision: 0
|
String |
getSalesContractValidityPerdCat()
Constraints: Not nullable, Maximum length: 2
|
String |
getSalesContractValidityPerdUnit()
Constraints: Not nullable, Maximum length: 1
|
LocalDateTime |
getSalesContractValidityStartDate()
Constraints: Not nullable, Precision: 0
|
String |
getSalesDocumentRjcnReason()
Constraints: Not nullable, Maximum length: 2
|
String |
getSDProcessStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getShippingPoint()
Constraints: Not nullable, Maximum length: 4
|
LocalDateTime |
getSlsContractFollowUpActionDate()
Constraints: Not nullable, Precision: 0
|
String |
getStorageLocation()
Constraints: Not nullable, Maximum length: 4
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<SalesContractItem> |
getType() |
String |
getWBSElement()
Constraints: Not nullable, Maximum length: 24
|
int |
hashCode() |
void |
setBatch(String batch)
Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setHigherLevelItem(String higherLevelItem)
Constraints: Not nullable, Maximum length: 6
|
void |
setIncotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
void |
setIncotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
void |
setItemBillingBlockReason(String itemBillingBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setItemGrossWeight(BigDecimal itemGrossWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemNetWeight(BigDecimal itemNetWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemVolume(BigDecimal itemVolume)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemVolumeUnit(String itemVolumeUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setItemWeightUnit(String itemWeightUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40
|
void |
setMaterialByCustomer(String materialByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setMaterialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9
|
void |
setMaterialPricingGroup(String materialPricingGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setNetAmount(BigDecimal netAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setNmbrOfSalesContractValdtyPerd(String nmbrOfSalesContractValdtyPerd)
Constraints: Not nullable, Maximum length: 3
|
void |
setOutlineAgreementTargetAmount(BigDecimal outlineAgreementTargetAmount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setPartner(List<SalesContractItemPartner> value)
Overwrites the list of associated SalesContractItemPartner entities for the loaded navigation property
to_Partner.
|
void |
setPricingDate(LocalDateTime pricingDate)
Constraints: Not nullable, Precision: 0
|
void |
setPricingElement(List<SalesContractItemPrcgElmnt> value)
Overwrites the list of associated SalesContractItemPrcgElmnt entities for the loaded navigation property
to_PricingElement.
|
void |
setProductionPlant(String productionPlant)
Constraints: Not nullable, Maximum length: 4
|
void |
setProfitCenter(String profitCenter)
Constraints: Not nullable, Maximum length: 10
|
void |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setReferenceSDDocument(String referenceSDDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setReferenceSDDocumentItem(String referenceSDDocumentItem)
Constraints: Not nullable, Maximum length: 6
|
void |
setRequestedQuantity(BigDecimal requestedQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setRequestedQuantityUnit(String requestedQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesContract(SalesContract value)
Overwrites the associated SalesContract entity for the loaded navigation property to_SalesContract.
|
void |
setSalesContract(String salesContract)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSalesContractFollowUpAction(String salesContractFollowUpAction)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesContractItem(String salesContractItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setSalesContractItemCategory(String salesContractItemCategory)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesContractItemText(String salesContractItemText)
Constraints: Not nullable, Maximum length: 40
|
void |
setSalesContractSignedDate(LocalDateTime salesContractSignedDate)
Constraints: Not nullable, Precision: 0
|
void |
setSalesContractValidityEndDate(LocalDateTime salesContractValidityEndDate)
Constraints: Not nullable, Precision: 0
|
void |
setSalesContractValidityPerdCat(String salesContractValidityPerdCat)
Constraints: Not nullable, Maximum length: 2
|
void |
setSalesContractValidityPerdUnit(String salesContractValidityPerdUnit)
Constraints: Not nullable, Maximum length: 1
|
void |
setSalesContractValidityStartDate(LocalDateTime salesContractValidityStartDate)
Constraints: Not nullable, Precision: 0
|
void |
setSalesDocumentRjcnReason(String salesDocumentRjcnReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setSDProcessStatus(String sDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setShippingPoint(String shippingPoint)
Constraints: Not nullable, Maximum length: 4
|
void |
setSlsContractFollowUpActionDate(LocalDateTime slsContractFollowUpActionDate)
Constraints: Not nullable, Precision: 0
|
void |
setStorageLocation(String storageLocation)
Constraints: Not nullable, Maximum length: 4
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setWBSElement(String wBSElement)
Constraints: Not nullable, Maximum length: 24
|
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 SalesContractItemSelectable ALL_FIELDS
public static final SalesContractItemField<String> SALES_CONTRACT
public static final SalesContractItemField<String> SALES_CONTRACT_ITEM
public static final SalesContractItemField<String> HIGHER_LEVEL_ITEM
public static final SalesContractItemField<String> SALES_CONTRACT_ITEM_CATEGORY
public static final SalesContractItemField<String> SALES_CONTRACT_ITEM_TEXT
public static final SalesContractItemField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final SalesContractItemField<String> MATERIAL
public static final SalesContractItemField<String> MATERIAL_BY_CUSTOMER
public static final SalesContractItemField<LocalDateTime> PRICING_DATE
public static final SalesContractItemField<BigDecimal> REQUESTED_QUANTITY
public static final SalesContractItemField<String> REQUESTED_QUANTITY_UNIT
public static final SalesContractItemField<BigDecimal> ITEM_GROSS_WEIGHT
public static final SalesContractItemField<BigDecimal> ITEM_NET_WEIGHT
public static final SalesContractItemField<String> ITEM_WEIGHT_UNIT
public static final SalesContractItemField<BigDecimal> ITEM_VOLUME
public static final SalesContractItemField<String> ITEM_VOLUME_UNIT
public static final SalesContractItemField<BigDecimal> OUTLINE_AGREEMENT_TARGET_AMOUNT
public static final SalesContractItemField<String> TRANSACTION_CURRENCY
public static final SalesContractItemField<BigDecimal> NET_AMOUNT
public static final SalesContractItemField<String> MATERIAL_GROUP
public static final SalesContractItemField<String> MATERIAL_PRICING_GROUP
public static final SalesContractItemField<String> BATCH
public static final SalesContractItemField<String> PRODUCTION_PLANT
public static final SalesContractItemField<String> STORAGE_LOCATION
public static final SalesContractItemField<String> SHIPPING_POINT
public static final SalesContractItemField<String> INCOTERMS_CLASSIFICATION
public static final SalesContractItemField<String> INCOTERMS_TRANSFER_LOCATION
public static final SalesContractItemField<String> INCOTERMS_LOCATION1
public static final SalesContractItemField<String> INCOTERMS_LOCATION2
public static final SalesContractItemField<String> CUSTOMER_PAYMENT_TERMS
public static final SalesContractItemField<String> SALES_DOCUMENT_RJCN_REASON
public static final SalesContractItemField<String> ITEM_BILLING_BLOCK_REASON
public static final SalesContractItemField<String> WBS_ELEMENT
public static final SalesContractItemField<String> PROFIT_CENTER
public static final SalesContractItemField<String> REFERENCE_SD_DOCUMENT
public static final SalesContractItemField<String> REFERENCE_SD_DOCUMENT_ITEM
public static final SalesContractItemField<String> SD_PROCESS_STATUS
public static final SalesContractItemField<LocalDateTime> SALES_CONTRACT_VALIDITY_START_DATE
public static final SalesContractItemField<LocalDateTime> SALES_CONTRACT_VALIDITY_END_DATE
public static final SalesContractItemField<String> NMBR_OF_SALES_CONTRACT_VALDTY_PERD
public static final SalesContractItemField<String> SALES_CONTRACT_VALIDITY_PERD_UNIT
public static final SalesContractItemField<String> SALES_CONTRACT_VALIDITY_PERD_CAT
public static final SalesContractItemField<LocalDateTime> SALES_CONTRACT_SIGNED_DATE
public static final SalesContractItemField<String> SALES_CONTRACT_FOLLOW_UP_ACTION
public static final SalesContractItemField<LocalDateTime> SLS_CONTRACT_FOLLOW_UP_ACTION_DATE
public static final SalesContractItemLink<SalesContractItemPartner> TO_PARTNER
public static final SalesContractItemLink<SalesContractItemPrcgElmnt> TO_PRICING_ELEMENT
public static final SalesContractItemOneToOneLink<SalesContract> TO_SALES_CONTRACT
public SalesContractItem()
public SalesContractItem(@Nullable String salesContract, @Nullable String salesContractItem, @Nullable String higherLevelItem, @Nullable String salesContractItemCategory, @Nullable String salesContractItemText, @Nullable String purchaseOrderByCustomer, @Nullable String material, @Nullable String materialByCustomer, @Nullable LocalDateTime pricingDate, @Nullable BigDecimal requestedQuantity, @Nullable String requestedQuantityUnit, @Nullable BigDecimal itemGrossWeight, @Nullable BigDecimal itemNetWeight, @Nullable String itemWeightUnit, @Nullable BigDecimal itemVolume, @Nullable String itemVolumeUnit, @Nullable BigDecimal outlineAgreementTargetAmount, @Nullable String transactionCurrency, @Nullable BigDecimal netAmount, @Nullable String materialGroup, @Nullable String materialPricingGroup, @Nullable String batch, @Nullable String productionPlant, @Nullable String storageLocation, @Nullable String shippingPoint, @Nullable String incotermsClassification, @Nullable String incotermsTransferLocation, @Nullable String incotermsLocation1, @Nullable String incotermsLocation2, @Nullable String customerPaymentTerms, @Nullable String salesDocumentRjcnReason, @Nullable String itemBillingBlockReason, @Nullable String wBSElement, @Nullable String profitCenter, @Nullable String referenceSDDocument, @Nullable String referenceSDDocumentItem, @Nullable String sDProcessStatus, @Nullable LocalDateTime salesContractValidityStartDate, @Nullable LocalDateTime salesContractValidityEndDate, @Nullable String nmbrOfSalesContractValdtyPerd, @Nullable String salesContractValidityPerdUnit, @Nullable String salesContractValidityPerdCat, @Nullable LocalDateTime salesContractSignedDate, @Nullable String salesContractFollowUpAction, @Nullable LocalDateTime slsContractFollowUpActionDate, List<SalesContractItemPartner> toPartner, List<SalesContractItemPrcgElmnt> toPricingElement, @Nullable SalesContract toSalesContract)
@Nonnull public Class<SalesContractItem> getType()
getType
in class VdmObject<SalesContractItem>
public void setSalesContract(@Nullable String salesContract)
Original property name from the Odata EDM: SalesContract
salesContract
- Sales Contractpublic void setSalesContractItem(@Nullable String salesContractItem)
Original property name from the Odata EDM: SalesContractItem
salesContractItem
- Sales Contract Itempublic void setHigherLevelItem(@Nullable String higherLevelItem)
Original property name from the Odata EDM: HigherLevelItem
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item.Enter the number of a higher-level item.
higherLevelItem
- The number of the higher-level item to which this item belongs in a hierarchy.public void setSalesContractItemCategory(@Nullable String salesContractItemCategory)
Original property name from the Odata EDM: SalesContractItemCategory
The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document.If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.
salesContractItemCategory
- A classification that distinguishes between different types of item (for example, free of charge items
and text items) and determines how the system processes the item.public void setSalesContractItemText(@Nullable String salesContractItemText)
Original property name from the Odata EDM: SalesContractItemText
Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations.The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
salesContractItemText
- A short description of the item.public void setPurchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
purchaseOrderByCustomer
- Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a
purchase order).public void setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setMaterialByCustomer(@Nullable String materialByCustomer)
Original property name from the Odata EDM: MaterialByCustomer
If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such asMinimum delivery quantityPartial delivery conditionsEnter a value from an existing customer-material info record.
materialByCustomer
- Uniquely identifies the material from the customer's point of view.public void 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 setRequestedQuantity(@Nullable BigDecimal requestedQuantity)
Original property name from the Odata EDM: RequestedQuantity
requestedQuantity
- Requested Quantitypublic void setRequestedQuantityUnit(@Nullable String requestedQuantityUnit)
Original property name from the Odata EDM: RequestedQuantityUnit
requestedQuantityUnit
- Requested Quantity Unitpublic void setItemGrossWeight(@Nullable BigDecimal itemGrossWeight)
Original property name from the Odata EDM: ItemGrossWeight
The system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record.If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the gross weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the gross weight using the target quantity.You can change the value manually at the item level.
itemGrossWeight
- The total gross weight of the item. The gross weight represents the net weight plus the weight of
packaging.public void setItemNetWeight(@Nullable BigDecimal itemNetWeight)
Original property name from the Odata EDM: ItemNetWeight
The system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the net weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the net weight using the target quantity.You can change the value manually at the item level.The gross weight of a refrigerator and its packaging (a cardboard box including protective padding) is 350 pounds. The packaging weighs 25 pounds. In this case, the net weight is 325 pounds.
itemNetWeight
- The total net weight for the item. The net weight represents the gross weight less the weight of
packaging.public void setItemWeightUnit(@Nullable String itemWeightUnit)
Original property name from the Odata EDM: ItemWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
itemWeightUnit
- Unit referring to the gross weight or net weight of the material.public void setItemVolume(@Nullable BigDecimal itemVolume)
Original property name from the Odata EDM: ItemVolume
The system calculates the volume based on the order quantity for the item and the volume proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the volume. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the volume using the target quantity.You can change the value manually at the item level.
itemVolume
- The total volume for the item.public void setItemVolumeUnit(@Nullable String itemVolumeUnit)
Original property name from the Odata EDM: ItemVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
itemVolumeUnit
- Unit referring to the volume of the material.public void setOutlineAgreementTargetAmount(@Nullable BigDecimal outlineAgreementTargetAmount)
Original property name from the Odata EDM: OutlineAgreementTargetAmount
The target value represents the value of products or services that a customer has agreed to purchase or that a supplier has agreed to supply during the validity period of the outline agreement.
outlineAgreementTargetAmount
- The target value of an outline agreement (for example, a value contract). 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 setNetAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
netAmount
- The net value of the item, after any discounts and surcharges are taken into account. Sales taxes are
not included. The value is expressed in the document currency.public void setMaterialGroup(@Nullable String materialGroup)
Original property name from the Odata EDM: MaterialGroup
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
materialGroup
- Key that you use to group together several materials or services with the same attributes, and to
assign them to a particular material group.public void setMaterialPricingGroup(@Nullable String materialPricingGroup)
Original property name from the Odata EDM: MaterialPricingGroup
You can create condition records for a material price group using the following condition types:Material price group (for example, all non-food products)A combination of customer and material price groupA combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
materialPricingGroup
- A way of grouping materials to which you want to apply the same condition.public void setBatch(@Nullable String batch)
Original property name from the Odata EDM: Batch
batch
- Assigns a material that is manufactured in batches or production lots to a specific batch.public void setProductionPlant(@Nullable String productionPlant)
Original property name from the Odata EDM: ProductionPlant
productionPlant
- Key that uniquely identifies a plant.public void setStorageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
storageLocation
- Number of the storage location in which the material is stored. A plant may contain one or more
storage locations.public void setShippingPoint(@Nullable String shippingPoint)
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.
shippingPoint
- The physical location (for example, a warehouse or collection of loading ramps) from which you ship
the item.public void setIncotermsClassification(@Nullable String incotermsClassification)
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
incotermsClassification
- Commonly used trading terms that comply with the standards established by the International Chamber of
Commerce (ICC).public void setIncotermsTransferLocation(@Nullable String incotermsTransferLocation)
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
incotermsTransferLocation
- Additional information for the primary Incoterm.public void setIncotermsLocation1(@Nullable String incotermsLocation1)
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
incotermsLocation1
- Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:public void setIncotermsLocation2(@Nullable String incotermsLocation2)
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
incotermsLocation2
- Provides additional information for the Incoterms. This field is only available for C-Clauses (if
customized appropriately). Note the following for the incoterms versions below:public void setCustomerPaymentTerms(@Nullable String customerPaymentTerms)
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
customerPaymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setSalesDocumentRjcnReason(@Nullable String salesDocumentRjcnReason)
Original property name from the Odata EDM: SalesDocumentRjcnReason
The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection:Inquiries and quotations: no further references by other documentsSales orders: no further delivery of itemsContracts: no further creation of release ordersCredit and debit memo requests: no further processing of credit or debit memosEnter one of the values predefined for your system.If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
salesDocumentRjcnReason
- The reason for rejecting a sales document (for example, a sales quotation or a sales order).public void setItemBillingBlockReason(@Nullable String itemBillingBlockReason)
Original property name from the Odata EDM: ItemBillingBlockReason
To block an item for billing, enter one of the values predefined for your system.You can block an item for billing so that, for example, terms of payment or prices can be checked before further processing takes place.
itemBillingBlockReason
- Indicates if the item is blocked for billing.public void setWBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
wBSElement
- Key that identifies a WBS element.public void setProfitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
profitCenter
- Key which together with the controlling area uniquely identifies a profit center.public void setReferenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
referenceSDDocument
- Identifies the sales order to which the delivery refers.public void setReferenceSDDocumentItem(@Nullable String referenceSDDocumentItem)
Original property name from the Odata EDM: ReferenceSDDocumentItem
referenceSDDocumentItem
- The number of the sales order item to which the delivery item refers.public void setSDProcessStatus(@Nullable String sDProcessStatus)
Original property name from the Odata EDM: SDProcessStatus
The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
sDProcessStatus
- Displays the overall processing status of the item.public void setSalesContractValidityStartDate(@Nullable LocalDateTime salesContractValidityStartDate)
Original property name from the Odata EDM: SalesContractValidityStartDate
The contract start date can be entered both at header and at item level. If the contract start date is only entered at header level, then it is valid for all items.The contract start date can be proposed automatically as a default from another data field on the basis of a date rule.
salesContractValidityStartDate
- Enter the contract start date.public void setSalesContractValidityEndDate(@Nullable LocalDateTime salesContractValidityEndDate)
Original property name from the Odata EDM: SalesContractValidityEndDate
salesContractValidityEndDate
- Contract End Datepublic void setNmbrOfSalesContractValdtyPerd(@Nullable String nmbrOfSalesContractValdtyPerd)
Original property name from the Odata EDM: NmbrOfSalesContractValdtyPerd
nmbrOfSalesContractValdtyPerd
- Validity Period of Contractpublic void setSalesContractValidityPerdUnit(@Nullable String salesContractValidityPerdUnit)
Original property name from the Odata EDM: SalesContractValidityPerdUnit
salesContractValidityPerdUnit
- Unit of Validity Period of Contractpublic void setSalesContractValidityPerdCat(@Nullable String salesContractValidityPerdCat)
Original property name from the Odata EDM: SalesContractValidityPerdCat
salesContractValidityPerdCat
- Enter a value here to indicate what kind of validity period the contract has (6 months, one year, and
so on).public void setSalesContractSignedDate(@Nullable LocalDateTime salesContractSignedDate)
Original property name from the Odata EDM: SalesContractSignedDate
The date you enter can be used as a baseline date for determining other dates in the contract.You want the contract to become valid on the day it is signed by the customer. You enter a date rule for the contract start date which has the date on which the contract is signed as its baseline date. When you enter the date on which the contract was signed in the contract, the system automatically makes the appropriate entry in the contract start date field.
salesContractSignedDate
- Enter the date on which the customer signs the contract.public void setSalesContractFollowUpAction(@Nullable String salesContractFollowUpAction)
Original property name from the Odata EDM: SalesContractFollowUpAction
Creating a contractCreating a quotationCreating a sales activity such as a telephone callSending an internal electronic mail
salesContractFollowUpAction
- Enter the follow-up action which is to be taken when the contract ends. Follow-up actions arepublic void setSlsContractFollowUpActionDate(@Nullable LocalDateTime slsContractFollowUpActionDate)
Original property name from the Odata EDM: SlsContractFollowUpActionDate
The contract will be included in the worklist for contracts with follow-up actions whenThe date you enter in this field lies within the selection period you define for the worklistThe contract fulfills the other selection criteria you define for the worklist.You reach the selection screen for the worklist for contracts with follow-up actions by choosing Outline agreements -> Contracts -> Subsequent functions -> Follow-up actions.
slsContractFollowUpActionDate
- Enter the date on which you want the follow-up action for the contract to be performed.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<SalesContractItem>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<SalesContractItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SalesContractItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SalesContractItem>
@Nonnull public static <T> SalesContractItemField<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> SalesContractItemField<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<SalesContractItem>
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<SalesContractItem>
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<SalesContractItem>
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()
VdmEntity
getDefaultServicePath
in class VdmEntity<SalesContractItem>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SalesContractItem>
@Nonnull public List<SalesContractItemPartner> 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<SalesContractItemPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried SalesContractItem 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<SalesContractItemPartner>> getPartnerIfPresent()
If the navigation property for an entity SalesContractItem 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<SalesContractItemPartner> value)
If the navigation property to_Partner of a queried SalesContractItem 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 SalesContractItemPartner entities.public void addPartner(SalesContractItemPartner... entity)
If the navigation property to_Partner of a queried SalesContractItem 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 SalesContractItemPartner entities.@Nonnull public List<SalesContractItemPrcgElmnt> 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<SalesContractItemPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried SalesContractItem 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<SalesContractItemPrcgElmnt>> getPricingElementIfPresent()
If the navigation property for an entity SalesContractItem 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<SalesContractItemPrcgElmnt> value)
If the navigation property to_PricingElement of a queried SalesContractItem 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 SalesContractItemPrcgElmnt entities.public void addPricingElement(SalesContractItemPrcgElmnt... entity)
If the navigation property to_PricingElement of a queried SalesContractItem 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 SalesContractItemPrcgElmnt entities.@Nullable public SalesContract fetchSalesContract() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
null
if an entity is not associated.com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nullable public SalesContract getSalesContractOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SalesContract of a queried SalesContractItem 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<SalesContract> getSalesContractIfPresent()
If the navigation property for an entity SalesContractItem 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 setSalesContract(SalesContract value)
value
- New SalesContract entity.public static SalesContractItem.SalesContractItemBuilder builder()
@Nullable public String getSalesContract()
Original property name from the Odata EDM: SalesContract
@Nullable public String getSalesContractItem()
Original property name from the Odata EDM: SalesContractItem
@Nullable public String getHigherLevelItem()
Original property name from the Odata EDM: HigherLevelItem
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item.Enter the number of a higher-level item.
@Nullable public String getSalesContractItemCategory()
Original property name from the Odata EDM: SalesContractItemCategory
The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document.If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.
@Nullable public String getSalesContractItemText()
Original property name from the Odata EDM: SalesContractItemText
Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations.The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
@Nullable public String getPurchaseOrderByCustomer()
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
@Nullable public String getMaterial()
Original property name from the Odata EDM: Material
@Nullable public String getMaterialByCustomer()
Original property name from the Odata EDM: MaterialByCustomer
If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such asMinimum delivery quantityPartial delivery conditionsEnter a value from an existing customer-material info record.
@Nullable public 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 BigDecimal getRequestedQuantity()
Original property name from the Odata EDM: RequestedQuantity
@Nullable public String getRequestedQuantityUnit()
Original property name from the Odata EDM: RequestedQuantityUnit
@Nullable public BigDecimal getItemGrossWeight()
Original property name from the Odata EDM: ItemGrossWeight
The system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record.If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the gross weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the gross weight using the target quantity.You can change the value manually at the item level.
@Nullable public BigDecimal getItemNetWeight()
Original property name from the Odata EDM: ItemNetWeight
The system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the net weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the net weight using the target quantity.You can change the value manually at the item level.The gross weight of a refrigerator and its packaging (a cardboard box including protective padding) is 350 pounds. The packaging weighs 25 pounds. In this case, the net weight is 325 pounds.
@Nullable public String getItemWeightUnit()
Original property name from the Odata EDM: ItemWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
@Nullable public BigDecimal getItemVolume()
Original property name from the Odata EDM: ItemVolume
The system calculates the volume based on the order quantity for the item and the volume proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the volume. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the volume using the target quantity.You can change the value manually at the item level.
@Nullable public String getItemVolumeUnit()
Original property name from the Odata EDM: ItemVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
@Nullable public BigDecimal getOutlineAgreementTargetAmount()
Original property name from the Odata EDM: OutlineAgreementTargetAmount
The target value represents the value of products or services that a customer has agreed to purchase or that a supplier has agreed to supply during the validity period of the outline agreement.
@Nullable public String getTransactionCurrency()
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable public BigDecimal getNetAmount()
Original property name from the Odata EDM: NetAmount
@Nullable public String getMaterialGroup()
Original property name from the Odata EDM: MaterialGroup
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
@Nullable public String getMaterialPricingGroup()
Original property name from the Odata EDM: MaterialPricingGroup
You can create condition records for a material price group using the following condition types:Material price group (for example, all non-food products)A combination of customer and material price groupA combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
@Nullable public String getBatch()
Original property name from the Odata EDM: Batch
@Nullable public String getProductionPlant()
Original property name from the Odata EDM: ProductionPlant
@Nullable public String getStorageLocation()
Original property name from the Odata EDM: StorageLocation
@Nullable public String getShippingPoint()
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.
@Nullable public String getIncotermsClassification()
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
@Nullable public String getIncotermsTransferLocation()
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
@Nullable public String getIncotermsLocation1()
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
@Nullable public String getIncotermsLocation2()
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
@Nullable public String getCustomerPaymentTerms()
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
@Nullable public String getSalesDocumentRjcnReason()
Original property name from the Odata EDM: SalesDocumentRjcnReason
The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection:Inquiries and quotations: no further references by other documentsSales orders: no further delivery of itemsContracts: no further creation of release ordersCredit and debit memo requests: no further processing of credit or debit memosEnter one of the values predefined for your system.If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
@Nullable public String getItemBillingBlockReason()
Original property name from the Odata EDM: ItemBillingBlockReason
To block an item for billing, enter one of the values predefined for your system.You can block an item for billing so that, for example, terms of payment or prices can be checked before further processing takes place.
@Nullable public String getWBSElement()
Original property name from the Odata EDM: WBSElement
@Nullable public String getProfitCenter()
Original property name from the Odata EDM: ProfitCenter
@Nullable public String getReferenceSDDocument()
Original property name from the Odata EDM: ReferenceSDDocument
@Nullable public String getReferenceSDDocumentItem()
Original property name from the Odata EDM: ReferenceSDDocumentItem
@Nullable public String getSDProcessStatus()
Original property name from the Odata EDM: SDProcessStatus
The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
@Nullable public LocalDateTime getSalesContractValidityStartDate()
Original property name from the Odata EDM: SalesContractValidityStartDate
The contract start date can be entered both at header and at item level. If the contract start date is only entered at header level, then it is valid for all items.The contract start date can be proposed automatically as a default from another data field on the basis of a date rule.
@Nullable public LocalDateTime getSalesContractValidityEndDate()
Original property name from the Odata EDM: SalesContractValidityEndDate
@Nullable public String getNmbrOfSalesContractValdtyPerd()
Original property name from the Odata EDM: NmbrOfSalesContractValdtyPerd
@Nullable public String getSalesContractValidityPerdUnit()
Original property name from the Odata EDM: SalesContractValidityPerdUnit
@Nullable public String getSalesContractValidityPerdCat()
Original property name from the Odata EDM: SalesContractValidityPerdCat
@Nullable public LocalDateTime getSalesContractSignedDate()
Original property name from the Odata EDM: SalesContractSignedDate
The date you enter can be used as a baseline date for determining other dates in the contract.You want the contract to become valid on the day it is signed by the customer. You enter a date rule for the contract start date which has the date on which the contract is signed as its baseline date. When you enter the date on which the contract was signed in the contract, the system automatically makes the appropriate entry in the contract start date field.
@Nullable public String getSalesContractFollowUpAction()
Original property name from the Odata EDM: SalesContractFollowUpAction
Creating a contractCreating a quotationCreating a sales activity such as a telephone callSending an internal electronic mail
@Nullable public LocalDateTime getSlsContractFollowUpActionDate()
Original property name from the Odata EDM: SlsContractFollowUpActionDate
The contract will be included in the worklist for contracts with follow-up actions whenThe date you enter in this field lies within the selection period you define for the worklistThe contract fulfills the other selection criteria you define for the worklist.You reach the selection screen for the worklist for contracts with follow-up actions by choosing Outline agreements -> Contracts -> Subsequent functions -> Follow-up actions.
public String toString()
toString
in class VdmObject<SalesContractItem>
public boolean equals(Object o)
equals
in class VdmObject<SalesContractItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<SalesContractItem>
public int hashCode()
hashCode
in class VdmObject<SalesContractItem>
Copyright © 2020 SAP SE. All rights reserved.