public class SalesContractItem extends VdmEntity<SalesContractItem>
| Modifier and Type | Class and Description |
|---|---|
static class |
SalesContractItem.SalesContractItemBuilder |
| Modifier and Type | Field and Description |
|---|---|
static EntityFieldAll<SalesContractItem> |
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<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<Calendar> |
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> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer 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<Calendar> |
SALES_CONTRACT_SIGNED_DATE
Use with available fluent helpers to apply the SalesContractSignedDate field to query operations.
|
static SalesContractItemField<Calendar> |
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<Calendar> |
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<Calendar> |
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 SalesContractItemLink<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.
|
| Constructor and Description |
|---|
SalesContractItem() |
SalesContractItem(String salesContract,
String salesContractItem,
String higherLevelItem,
String salesContractItemCategory,
String salesContractItemText,
String purchaseOrderByCustomer,
String material,
String materialByCustomer,
Calendar pricingDate,
BigDecimal requestedQuantity,
String requestedQuantityUnit,
BigDecimal itemGrossWeight,
BigDecimal itemNetWeight,
String itemWeightUnit,
BigDecimal itemVolume,
String itemVolumeUnit,
String transactionCurrency,
BigDecimal netAmount,
String materialGroup,
String batch,
String productionPlant,
String storageLocation,
String shippingPoint,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String customerPaymentTerms,
String salesDocumentRjcnReason,
String itemBillingBlockReason,
String sDProcessStatus,
BigDecimal outlineAgreementTargetAmount,
Calendar salesContractValidityStartDate,
Calendar salesContractValidityEndDate,
String nmbrOfSalesContractValdtyPerd,
String salesContractValidityPerdUnit,
String salesContractValidityPerdCat,
Calendar salesContractSignedDate,
String salesContractFollowUpAction,
Calendar slsContractFollowUpActionDate,
ErpConfigContext erpConfigContext,
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.
|
static SalesContractItem.SalesContractItemBuilder |
builder() |
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.
|
String |
getBatch()
Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getHigherLevelItem()
Constraints: Not nullable, Maximum length: 6
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsLocation1()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsLocation2()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28
|
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
|
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterialByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9
|
BigDecimal |
getNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getNmbrOfSalesContractValdtyPerd()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getOutlineAgreementTargetAmount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
List<SalesContractItemPartner> |
getPartnerOrFetch()
Retrieval of associated SalesContractItemPartner entities (one to many).
|
com.google.common.base.Optional<List<SalesContractItemPartner>> |
getPartnerOrNull()
Retrieval of associated SalesContractItemPartner entities (one to many).
|
Calendar |
getPricingDate()
Constraints: Not nullable, Precision: 0
|
List<SalesContractItemPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated SalesContractItemPrcgElmnt entities (one to many).
|
com.google.common.base.Optional<List<SalesContractItemPrcgElmnt>> |
getPricingElementOrNull()
Retrieval of associated SalesContractItemPrcgElmnt entities (one to many).
|
String |
getProductionPlant()
Constraints: Not nullable, Maximum length: 4
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
BigDecimal |
getRequestedQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getRequestedQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesContract()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSalesContractFollowUpAction()
Constraints: Not nullable, Maximum length: 4
|
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).
|
com.google.common.base.Optional<SalesContract> |
getSalesContractOrNull()
Retrieval of associated SalesContract entity (one to one).
|
Calendar |
getSalesContractSignedDate()
Constraints: Not nullable, Precision: 0
|
Calendar |
getSalesContractValidityEndDate()
Constraints: Not nullable, Precision: 0
|
String |
getSalesContractValidityPerdCat()
Constraints: Not nullable, Maximum length: 2
|
String |
getSalesContractValidityPerdUnit()
Constraints: Not nullable, Maximum length: 1
|
Calendar |
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
|
Calendar |
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() |
int |
hashCode() |
void |
setBatch(String batch)
Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setHigherLevelItem(String higherLevelItem)
Constraints: Not nullable, Maximum length: 6
|
void |
setIncotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
void |
setIncotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
void |
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 |
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(Calendar 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 |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setRequestedQuantity(BigDecimal requestedQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setRequestedQuantityUnit(String requestedQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesContract(SalesContract value)
Overwrites the associated SalesContract entity for the loaded navigation property to_SalesContract.
|
void |
setSalesContract(String value)
(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(Calendar salesContractSignedDate)
Constraints: Not nullable, Precision: 0
|
void |
setSalesContractValidityEndDate(Calendar 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(Calendar 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
|
void |
setShippingPoint(String shippingPoint)
Constraints: Not nullable, Maximum length: 4
|
void |
setSlsContractFollowUpActionDate(Calendar 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
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final EntityFieldAll<SalesContractItem> 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<Calendar> 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<String> TRANSACTION_CURRENCY
public static final SalesContractItemField<BigDecimal> NET_AMOUNT
public static final SalesContractItemField<String> MATERIAL_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> SD_PROCESS_STATUS
public static final SalesContractItemField<BigDecimal> OUTLINE_AGREEMENT_TARGET_AMOUNT
public static final SalesContractItemField<Calendar> SALES_CONTRACT_VALIDITY_START_DATE
public static final SalesContractItemField<Calendar> 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<Calendar> SALES_CONTRACT_SIGNED_DATE
public static final SalesContractItemField<String> SALES_CONTRACT_FOLLOW_UP_ACTION
public static final SalesContractItemField<Calendar> SLS_CONTRACT_FOLLOW_UP_ACTION_DATE
public static final SalesContractItemLink<SalesContractItemPartner> TO_PARTNER
public static final SalesContractItemLink<SalesContractItemPrcgElmnt> TO_PRICING_ELEMENT
public static final SalesContractItemLink<SalesContract> TO_SALES_CONTRACT
@Generated(value="lombok") public SalesContractItem()
@ConstructorProperties(value={"salesContract","salesContractItem","higherLevelItem","salesContractItemCategory","salesContractItemText","purchaseOrderByCustomer","material","materialByCustomer","pricingDate","requestedQuantity","requestedQuantityUnit","itemGrossWeight","itemNetWeight","itemWeightUnit","itemVolume","itemVolumeUnit","transactionCurrency","netAmount","materialGroup","batch","productionPlant","storageLocation","shippingPoint","incotermsClassification","incotermsTransferLocation","incotermsLocation1","incotermsLocation2","customerPaymentTerms","salesDocumentRjcnReason","itemBillingBlockReason","sDProcessStatus","outlineAgreementTargetAmount","salesContractValidityStartDate","salesContractValidityEndDate","nmbrOfSalesContractValdtyPerd","salesContractValidityPerdUnit","salesContractValidityPerdCat","salesContractSignedDate","salesContractFollowUpAction","slsContractFollowUpActionDate","erpConfigContext","toPartner","toPricingElement","toSalesContract"}) @Generated(value="lombok") 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 Calendar pricingDate, @Nullable BigDecimal requestedQuantity, @Nullable String requestedQuantityUnit, @Nullable BigDecimal itemGrossWeight, @Nullable BigDecimal itemNetWeight, @Nullable String itemWeightUnit, @Nullable BigDecimal itemVolume, @Nullable String itemVolumeUnit, @Nullable String transactionCurrency, @Nullable BigDecimal netAmount, @Nullable String materialGroup, @Nullable String batch, @Nullable String 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 sDProcessStatus, @Nullable BigDecimal outlineAgreementTargetAmount, @Nullable Calendar salesContractValidityStartDate, @Nullable Calendar salesContractValidityEndDate, @Nullable String nmbrOfSalesContractValdtyPerd, @Nullable String salesContractValidityPerdUnit, @Nullable String salesContractValidityPerdCat, @Nullable Calendar salesContractSignedDate, @Nullable String salesContractFollowUpAction, @Nullable Calendar slsContractFollowUpActionDate, @Nullable ErpConfigContext erpConfigContext, List<SalesContractItemPartner> toPartner, List<SalesContractItemPrcgElmnt> toPricingElement, @Nullable SalesContract toSalesContract)
public Class<SalesContractItem> getType()
getType in class VdmObject<SalesContractItem>public static <T> SalesContractItemField<T> field(String fieldName, Class<T> fieldType)
fieldName - The name of the extension field as returned by the OData service.fieldType - The Java type to use for the extension field when performing value comparisons.public List<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.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.public com.google.common.base.Optional<List<SalesContractItemPartner>> getPartnerOrNull()
If the navigation property to_Partner for an entity SalesContractItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setPartner(@NonNull
List<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.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.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.public com.google.common.base.Optional<List<SalesContractItemPrcgElmnt>> getPricingElementOrNull()
If the navigation property to_PricingElement for an entity SalesContractItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setPricingElement(@NonNull
List<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.public SalesContract fetchSalesContract() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public 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.public com.google.common.base.Optional<SalesContract> getSalesContractOrNull()
If the navigation property to_SalesContract for an entity SalesContractItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setSalesContract(SalesContract value)
value - New SalesContract entity.public void setSalesContract(String value)
value - salesContract@Generated(value="lombok") public static SalesContractItem.SalesContractItemBuilder builder()
@Nullable @Generated(value="lombok") public String getSalesContract()
@Nullable @Generated(value="lombok") public String getSalesContractItem()
@Nullable @Generated(value="lombok") public String getHigherLevelItem()
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item. Enter the number of a higher-level item.
@Nullable @Generated(value="lombok") public String getSalesContractItemCategory()
The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document. If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.
@Nullable @Generated(value="lombok") public String getSalesContractItemText()
Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations. The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
@Nullable @Generated(value="lombok") public String getPurchaseOrderByCustomer()
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
@Nullable @Generated(value="lombok") public String getMaterial()
@Nullable @Generated(value="lombok") public String getMaterialByCustomer()
If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such as Minimum delivery quantity Partial delivery conditions Enter a value from an existing customer-material info record.
@Nullable @Generated(value="lombok") public Calendar getPricingDate()
You can use the pricing date as a selection criterion when you process billing documents collectively. The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue. Determining the Proposal In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date. In the billing document: The billing date is proposed as the pricing date.
@Nullable @Generated(value="lombok") public BigDecimal getRequestedQuantity()
@Nullable @Generated(value="lombok") public String getRequestedQuantityUnit()
@Nullable @Generated(value="lombok") public BigDecimal getItemGrossWeight()
The system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the gross weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the gross weight using the target quantity. You can change the value manually at the item level.
@Nullable @Generated(value="lombok") public BigDecimal getItemNetWeight()
The system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the net weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the net weight using the target quantity. You can change the value manually at the item level. The gross weight of a refrigerator and its packaging (a cardboard box including protective padding) is 350 pounds. The packaging weighs 25 pounds. In this case, the net weight is 325 pounds.
@Nullable @Generated(value="lombok") public String getItemWeightUnit()
If you specify a weight, you must enter the corresponding unit of weight here.
@Nullable @Generated(value="lombok") public BigDecimal getItemVolume()
The system calculates the volume based on the order quantity for the item and the volume proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the volume. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the volume using the target quantity. You can change the value manually at the item level.
@Nullable @Generated(value="lombok") public String getItemVolumeUnit()
If you specify a volume, you have to enter the corresponding volume unit here.
@Nullable @Generated(value="lombok") public String getTransactionCurrency()
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable @Generated(value="lombok") public BigDecimal getNetAmount()
@Nullable @Generated(value="lombok") public String getMaterialGroup()
You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
@Nullable @Generated(value="lombok") public String getBatch()
@Nullable @Generated(value="lombok") public String getProductionPlant()
@Nullable @Generated(value="lombok") public String getStorageLocation()
@Nullable @Generated(value="lombok") public String getShippingPoint()
You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries. A delivery can be shipped from one shipping point only or received at one receiving point only. 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. You can define a user-specific default value for the shipping point in the user parameter VST.
@Nullable @Generated(value="lombok") public String getIncotermsClassification()
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully. If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
@Nullable @Generated(value="lombok") public String getIncotermsTransferLocation()
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
@Nullable @Generated(value="lombok") public String getIncotermsLocation1()
1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 1 EXW Ex Works Place of Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
@Nullable @Generated(value="lombok") public String getIncotermsLocation2()
No Version: This field is disabled Incoterm Version 2000 This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions. Incoterm Version 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
@Nullable @Generated(value="lombok") public String getCustomerPaymentTerms()
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data can be entered in the field for the terms of payment key in various ways as you enter a business transaction: In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question. In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field. Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at: item level in sales orders header level in purchase orders and invoices Master records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
@Nullable @Generated(value="lombok") public String getSalesDocumentRjcnReason()
The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection: Inquiries and quotations: no further references by other documents Sales orders: no further delivery of items Contracts: no further creation of release orders Credit and debit memo requests: no further processing of credit or debit memos Enter one of the values predefined for your system. If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
@Nullable @Generated(value="lombok") public String getItemBillingBlockReason()
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 @Generated(value="lombok") public String getSDProcessStatus()
The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
@Nullable @Generated(value="lombok") public BigDecimal getOutlineAgreementTargetAmount()
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 @Generated(value="lombok") public Calendar getSalesContractValidityStartDate()
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 @Generated(value="lombok") public Calendar getSalesContractValidityEndDate()
@Nullable @Generated(value="lombok") public String getNmbrOfSalesContractValdtyPerd()
@Nullable @Generated(value="lombok") public String getSalesContractValidityPerdUnit()
@Nullable @Generated(value="lombok") public String getSalesContractValidityPerdCat()
@Nullable @Generated(value="lombok") public Calendar getSalesContractSignedDate()
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 @Generated(value="lombok") public String getSalesContractFollowUpAction()
Creating a contract Creating a quotation Creating a sales activity such as a telephone call Sending an internal electronic mail
@Nullable @Generated(value="lombok") public Calendar getSlsContractFollowUpActionDate()
The contract will be included in the worklist for contracts with follow-up actions when The date you enter in this field lies within the selection period you define for the worklist The 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.
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setSalesContractItem(@Nullable String salesContractItem)
salesContractItem - @Generated(value="lombok") public void setHigherLevelItem(@Nullable String higherLevelItem)
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item. Enter the number of a higher-level item.
higherLevelItem - @Generated(value="lombok") public void setSalesContractItemCategory(@Nullable String 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 - @Generated(value="lombok") public void setSalesContractItemText(@Nullable String 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 - @Generated(value="lombok") public void setPurchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
purchaseOrderByCustomer - @Generated(value="lombok") public void setMaterial(@Nullable String material)
material - @Generated(value="lombok") public void setMaterialByCustomer(@Nullable String materialByCustomer)
If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such as Minimum delivery quantity Partial delivery conditions Enter a value from an existing customer-material info record.
materialByCustomer - @Generated(value="lombok") public void setPricingDate(@Nullable Calendar pricingDate)
You can use the pricing date as a selection criterion when you process billing documents collectively. The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue. Determining the Proposal In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date. In the billing document: The billing date is proposed as the pricing date.
pricingDate - @Generated(value="lombok") public void setRequestedQuantity(@Nullable BigDecimal requestedQuantity)
requestedQuantity - @Generated(value="lombok") public void setRequestedQuantityUnit(@Nullable String requestedQuantityUnit)
requestedQuantityUnit - @Generated(value="lombok") public void setItemGrossWeight(@Nullable BigDecimal itemGrossWeight)
The system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the gross weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the gross weight using the target quantity. You can change the value manually at the item level.
itemGrossWeight - @Generated(value="lombok") public void setItemNetWeight(@Nullable BigDecimal itemNetWeight)
The system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the net weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the net weight using the target quantity. You can change the value manually at the item level. The gross weight of a refrigerator and its packaging (a cardboard box including protective padding) is 350 pounds. The packaging weighs 25 pounds. In this case, the net weight is 325 pounds.
itemNetWeight - @Generated(value="lombok") public void setItemWeightUnit(@Nullable String itemWeightUnit)
If you specify a weight, you must enter the corresponding unit of weight here.
itemWeightUnit - @Generated(value="lombok") public void setItemVolume(@Nullable BigDecimal itemVolume)
The system calculates the volume based on the order quantity for the item and the volume proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the volume. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the volume using the target quantity. You can change the value manually at the item level.
itemVolume - @Generated(value="lombok") public void setItemVolumeUnit(@Nullable String itemVolumeUnit)
If you specify a volume, you have to enter the corresponding volume unit here.
itemVolumeUnit - @Generated(value="lombok") public void setTransactionCurrency(@Nullable String transactionCurrency)
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
transactionCurrency - @Generated(value="lombok") public void setNetAmount(@Nullable BigDecimal netAmount)
netAmount - @Generated(value="lombok") public void setMaterialGroup(@Nullable String materialGroup)
You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
materialGroup - @Generated(value="lombok") public void setBatch(@Nullable String batch)
batch - @Generated(value="lombok") public void setProductionPlant(@Nullable String productionPlant)
productionPlant - @Generated(value="lombok") public void setStorageLocation(@Nullable String storageLocation)
storageLocation - @Generated(value="lombok") public void setShippingPoint(@Nullable String shippingPoint)
You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries. A delivery can be shipped from one shipping point only or received at one receiving point only. 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. You can define a user-specific default value for the shipping point in the user parameter VST.
shippingPoint - @Generated(value="lombok") public void setIncotermsClassification(@Nullable String incotermsClassification)
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully. If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
incotermsClassification - @Generated(value="lombok") public void setIncotermsTransferLocation(@Nullable String incotermsTransferLocation)
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
incotermsTransferLocation - @Generated(value="lombok") public void setIncotermsLocation1(@Nullable String incotermsLocation1)
1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 1 EXW Ex Works Place of Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
incotermsLocation1 - @Generated(value="lombok") public void setIncotermsLocation2(@Nullable String incotermsLocation2)
No Version: This field is disabled Incoterm Version 2000 This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions. Incoterm Version 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
incotermsLocation2 - @Generated(value="lombok") public void setCustomerPaymentTerms(@Nullable String customerPaymentTerms)
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data can be entered in the field for the terms of payment key in various ways as you enter a business transaction: In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question. In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field. Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at: item level in sales orders header level in purchase orders and invoices Master records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
customerPaymentTerms - @Generated(value="lombok") public void setSalesDocumentRjcnReason(@Nullable String salesDocumentRjcnReason)
The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection: Inquiries and quotations: no further references by other documents Sales orders: no further delivery of items Contracts: no further creation of release orders Credit and debit memo requests: no further processing of credit or debit memos Enter one of the values predefined for your system. If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
salesDocumentRjcnReason - @Generated(value="lombok") public void setItemBillingBlockReason(@Nullable String 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 - @Generated(value="lombok") public void setSDProcessStatus(@Nullable String sDProcessStatus)
The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
sDProcessStatus - @Generated(value="lombok") public void setOutlineAgreementTargetAmount(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setSalesContractValidityStartDate(@Nullable Calendar 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 - @Generated(value="lombok") public void setSalesContractValidityEndDate(@Nullable Calendar salesContractValidityEndDate)
salesContractValidityEndDate - @Generated(value="lombok") public void setNmbrOfSalesContractValdtyPerd(@Nullable String nmbrOfSalesContractValdtyPerd)
nmbrOfSalesContractValdtyPerd - @Generated(value="lombok") public void setSalesContractValidityPerdUnit(@Nullable String salesContractValidityPerdUnit)
salesContractValidityPerdUnit - @Generated(value="lombok") public void setSalesContractValidityPerdCat(@Nullable String salesContractValidityPerdCat)
salesContractValidityPerdCat - @Generated(value="lombok") public void setSalesContractSignedDate(@Nullable Calendar 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 - @Generated(value="lombok") public void setSalesContractFollowUpAction(@Nullable String salesContractFollowUpAction)
Creating a contract Creating a quotation Creating a sales activity such as a telephone call Sending an internal electronic mail
salesContractFollowUpAction - @Generated(value="lombok") public void setSlsContractFollowUpActionDate(@Nullable Calendar slsContractFollowUpActionDate)
The contract will be included in the worklist for contracts with follow-up actions when The date you enter in this field lies within the selection period you define for the worklist The 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 - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class VdmObject<SalesContractItem>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<SalesContractItem>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<SalesContractItem>Copyright © 2017 SAP SE. All rights reserved.