public class SchAgrmtItem extends VdmEntity<SchAgrmtItem>
Original entity name from the Odata EDM: A_SchAgrmtItemType
Modifier and Type | Class and Description |
---|---|
static class |
SchAgrmtItem.SchAgrmtItemBuilder
Helper class to allow for fluent creation of SchAgrmtItem instances.
|
Modifier and Type | Field and Description |
---|---|
static SchAgrmtItemField<String> |
ACCOUNT_ASSIGNMENT_CATEGORY
Use with available fluent helpers to apply the AccountAssignmentCategory field to query operations.
|
static SchAgrmtItemSelectable |
ALL_FIELDS
Selector for all available fields of SchAgrmtItem.
|
static SchAgrmtItemField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static SchAgrmtItemField<Boolean> |
CUMULATIVE_QUANTITY_IS_NOT_SENT
Use with available fluent helpers to apply the CumulativeQuantityIsNotSent field to query operations.
|
static SchAgrmtItemField<String> |
DOCUMENT_CURRENCY
Use with available fluent helpers to apply the DocumentCurrency field to query operations.
|
static SchAgrmtItemField<Boolean> |
EVALD_RCPT_SETTLMT_IS_ALLOWED
Use with available fluent helpers to apply the EvaldRcptSettlmtIsAllowed field to query operations.
|
static SchAgrmtItemField<String> |
FIRM_TRADE_OFF_ZONE_BIND_MRP
Use with available fluent helpers to apply the FirmTradeOffZoneBindMRP field to query operations.
|
static SchAgrmtItemField<Boolean> |
GOODS_RECEIPT_IS_EXPECTED
Use with available fluent helpers to apply the GoodsReceiptIsExpected field to query operations.
|
static SchAgrmtItemField<Boolean> |
GOODS_RECEIPT_IS_NON_VALUATED
Use with available fluent helpers to apply the GoodsReceiptIsNonValuated field to query operations.
|
static SchAgrmtItemField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static SchAgrmtItemField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static SchAgrmtItemField<Boolean> |
INVOICE_IS_EXPECTED
Use with available fluent helpers to apply the InvoiceIsExpected field to query operations.
|
static SchAgrmtItemField<Boolean> |
INVOICE_IS_GOODS_RECEIPT_BASED
Use with available fluent helpers to apply the InvoiceIsGoodsReceiptBased field to query operations.
|
static SchAgrmtItemField<String> |
IS_INFO_AT_REGISTRATION
Use with available fluent helpers to apply the IsInfoAtRegistration field to query operations.
|
static SchAgrmtItemField<String> |
IS_INFO_RECORD_UPDATED
Use with available fluent helpers to apply the IsInfoRecordUpdated field to query operations.
|
static SchAgrmtItemField<Boolean> |
IS_ORDER_ACKN_RQD
Use with available fluent helpers to apply the IsOrderAcknRqd field to query operations.
|
static SchAgrmtItemField<String> |
IS_RELEVANT_FOR_JIT_DELIV_SCHEDULE
Use with available fluent helpers to apply the IsRelevantForJITDelivSchedule field to query operations.
|
static SchAgrmtItemField<LocalDateTime> |
ITEM_LAST_TRANSMISSION_DATE
Use with available fluent helpers to apply the ItemLastTransmissionDate field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
ITEM_NET_WEIGHT
Use with available fluent helpers to apply the ItemNetWeight field to query operations.
|
static SchAgrmtItemField<String> |
MANUAL_DELIVERY_ADDRESS_ID
Use with available fluent helpers to apply the ManualDeliveryAddressID field to query operations.
|
static SchAgrmtItemField<String> |
MANUFACTURER_MATERIAL
Use with available fluent helpers to apply the ManufacturerMaterial field to query operations.
|
static SchAgrmtItemField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static SchAgrmtItemField<String> |
MATERIAL_GROUP
Use with available fluent helpers to apply the MaterialGroup field to query operations.
|
static SchAgrmtItemField<String> |
MATERIAL_TYPE
Use with available fluent helpers to apply the MaterialType field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
MIN_REMAINING_SHELF_LIFE
Use with available fluent helpers to apply the MinRemainingShelfLife field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
NET_PRICE_AMOUNT
Use with available fluent helpers to apply the NetPriceAmount field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
NET_PRICE_QUANTITY
Use with available fluent helpers to apply the NetPriceQuantity field to query operations.
|
static SchAgrmtItemField<LocalDateTime> |
NEXT_FCST_DELIV_SCHED_SENDING_DATE
Use with available fluent helpers to apply the NextFcstDelivSchedSendingDate field to query operations.
|
static SchAgrmtItemField<LocalDateTime> |
NEXT_JIT_DELIV_SCHED_SENDING_DATE
Use with available fluent helpers to apply the NextJITDelivSchedSendingDate field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
NO_DAYS_REMINDER1
Use with available fluent helpers to apply the NoDaysReminder1 field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
NO_DAYS_REMINDER2
Use with available fluent helpers to apply the NoDaysReminder2 field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
NO_DAYS_REMINDER3
Use with available fluent helpers to apply the NoDaysReminder3 field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
ORD_PRICE_UNIT_TO_ORDER_UNIT_DNMNTR
Use with available fluent helpers to apply the OrdPriceUnitToOrderUnitDnmntr field to query operations.
|
static SchAgrmtItemField<String> |
ORDER_PRICE_UNIT
Use with available fluent helpers to apply the OrderPriceUnit field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
ORDER_PRICE_UNIT_TO_ORDER_UNIT_NMRTR
Use with available fluent helpers to apply the OrderPriceUnitToOrderUnitNmrtr field to query operations.
|
static SchAgrmtItemField<String> |
ORDER_QUANTITY_UNIT
Use with available fluent helpers to apply the OrderQuantityUnit field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
OVERDELIV_TOLRTD_LMT_RATIO_IN_PCT
Use with available fluent helpers to apply the OverdelivTolrtdLmtRatioInPct field to query operations.
|
static SchAgrmtItemField<String> |
PLANT
Use with available fluent helpers to apply the Plant field to query operations.
|
static SchAgrmtItemField<Boolean> |
PRICE_IS_TO_BE_PRINTED
Use with available fluent helpers to apply the PriceIsToBePrinted field to query operations.
|
static SchAgrmtItemField<String> |
PRODUCT_TYPE
Use with available fluent helpers to apply the ProductType field to query operations.
|
static SchAgrmtItemField<String> |
PURCHASE_REQUISITION
Use with available fluent helpers to apply the PurchaseRequisition field to query operations.
|
static SchAgrmtItemField<String> |
PURCHASE_REQUISITION_ITEM
Use with available fluent helpers to apply the PurchaseRequisitionItem field to query operations.
|
static SchAgrmtItemField<String> |
PURCHASING_DOCUMENT_CATEGORY
Use with available fluent helpers to apply the PurchasingDocumentCategory field to query operations.
|
static SchAgrmtItemField<String> |
PURCHASING_DOCUMENT_DELETION_CODE
Use with available fluent helpers to apply the PurchasingDocumentDeletionCode field to query operations.
|
static SchAgrmtItemField<String> |
PURCHASING_DOCUMENT_ITEM_TEXT
Use with available fluent helpers to apply the PurchasingDocumentItemText field to query operations.
|
static SchAgrmtItemField<String> |
PURCHASING_INFO_RECORD
Use with available fluent helpers to apply the PurchasingInfoRecord field to query operations.
|
static SchAgrmtItemField<Boolean> |
PURG_DOC_ESTIMATED_PRICE
Use with available fluent helpers to apply the PurgDocEstimatedPrice field to query operations.
|
static SchAgrmtItemField<String> |
PURG_DOC_ORDER_ACKN_NUMBER
Use with available fluent helpers to apply the PurgDocOrderAcknNumber field to query operations.
|
static SchAgrmtItemField<String> |
QUALITY_CERTIFICATE_TYPE
Use with available fluent helpers to apply the QualityCertificateType field to query operations.
|
static SchAgrmtItemField<String> |
QUALITY_MGMT_CTRL_KEY
Use with available fluent helpers to apply the QualityMgmtCtrlKey field to query operations.
|
static SchAgrmtItemField<String> |
REFERENCE_DELIVERY_ADDRESS_ID
Use with available fluent helpers to apply the ReferenceDeliveryAddressID field to query operations.
|
static SchAgrmtItemField<String> |
REQUIREMENT_TRACKING
Use with available fluent helpers to apply the RequirementTracking field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
SCHED_AGRMT_AGREED_CUM_QTY
Use with available fluent helpers to apply the SchedAgrmtAgreedCumQty field to query operations.
|
static SchAgrmtItemField<LocalDateTime> |
SCHED_AGRMT_CUM_QTY_RECONCILE_DATE
Use with available fluent helpers to apply the SchedAgrmtCumQtyReconcileDate field to query operations.
|
static SchAgrmtItemField<String> |
SCHED_AGRMT_CUMULATIVE_QTY_CONTROL
Use with available fluent helpers to apply the SchedAgrmtCumulativeQtyControl field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
SCHED_LINE_SEMI_FIRM_ORDER_IN_DAYS
Use with available fluent helpers to apply the SchedLineSemiFirmOrderInDays field to query operations.
|
static SchAgrmtItemField<String> |
SCHEDG_AGRMT_REL_CREATION_PROFILE
Use with available fluent helpers to apply the SchedgAgrmtRelCreationProfile field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
SCHEDULE_LINE_FIRM_ORDER_IN_DAYS
Use with available fluent helpers to apply the ScheduleLineFirmOrderInDays field to query operations.
|
static SchAgrmtItemField<String> |
SCHEDULING_AGREEMENT
Use with available fluent helpers to apply the SchedulingAgreement field to query operations.
|
static SchAgrmtItemField<String> |
SCHEDULING_AGREEMENT_ITEM
Use with available fluent helpers to apply the SchedulingAgreementItem field to query operations.
|
static SchAgrmtItemField<String> |
SHIPPING_INSTRUCTION
Use with available fluent helpers to apply the ShippingInstruction field to query operations.
|
static SchAgrmtItemField<String> |
STOCK_TYPE
Use with available fluent helpers to apply the StockType field to query operations.
|
static SchAgrmtItemField<String> |
STORAGE_LOCATION
Use with available fluent helpers to apply the StorageLocation field to query operations.
|
static SchAgrmtItemField<String> |
SUPPLIER_MATERIAL_NUMBER
Use with available fluent helpers to apply the SupplierMaterialNumber field to query operations.
|
static SchAgrmtItemField<BigDecimal> |
TARGET_QUANTITY
Use with available fluent helpers to apply the TargetQuantity field to query operations.
|
static SchAgrmtItemField<String> |
TAX_CODE
Use with available fluent helpers to apply the TaxCode field to query operations.
|
static SchAgrmtItemLink<SchAgrmtAcCnt> |
TO_SCH_AGRMT_AC_CNT
Use with available fluent helpers to apply the to_SchAgrmtAcCnt navigation property to query operations.
|
static SchAgrmtItemLink<SchAgrmtSchLine> |
TO_SCH_AGRMT_SCH_LINE
Use with available fluent helpers to apply the to_SchAgrmtSchLine navigation property to query operations.
|
static SchAgrmtItemField<BigDecimal> |
UNDERDELIV_TOLRTD_LMT_RATIO_IN_PCT
Use with available fluent helpers to apply the UnderdelivTolrtdLmtRatioInPct field to query operations.
|
static SchAgrmtItemField<Boolean> |
UNLIMITED_OVERDELIVERY_IS_ALLOWED
Use with available fluent helpers to apply the UnlimitedOverdeliveryIsAllowed field to query operations.
|
static SchAgrmtItemField<String> |
WEIGHT_UNIT
Use with available fluent helpers to apply the WeightUnit field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SchAgrmtItem() |
SchAgrmtItem(String schedulingAgreement,
String schedulingAgreementItem,
String companyCode,
String purchasingDocumentCategory,
String purchasingDocumentItemText,
String material,
String manufacturerMaterial,
String supplierMaterialNumber,
String materialGroup,
String plant,
String manualDeliveryAddressID,
String referenceDeliveryAddressID,
String incotermsClassification,
String incotermsTransferLocation,
String orderQuantityUnit,
BigDecimal itemNetWeight,
String weightUnit,
BigDecimal targetQuantity,
String purchaseRequisition,
String purchaseRequisitionItem,
BigDecimal schedAgrmtAgreedCumQty,
LocalDateTime schedAgrmtCumQtyReconcileDate,
LocalDateTime itemLastTransmissionDate,
BigDecimal noDaysReminder1,
BigDecimal noDaysReminder2,
BigDecimal noDaysReminder3,
String purgDocOrderAcknNumber,
String requirementTracking,
Boolean isOrderAcknRqd,
Boolean purgDocEstimatedPrice,
Boolean priceIsToBePrinted,
String accountAssignmentCategory,
BigDecimal netPriceAmount,
BigDecimal netPriceQuantity,
String orderPriceUnit,
String productType,
String materialType,
String storageLocation,
String documentCurrency,
String isInfoRecordUpdated,
String purchasingInfoRecord,
BigDecimal ordPriceUnitToOrderUnitDnmntr,
BigDecimal orderPriceUnitToOrderUnitNmrtr,
String purchasingDocumentDeletionCode,
BigDecimal underdelivTolrtdLmtRatioInPct,
BigDecimal overdelivTolrtdLmtRatioInPct,
Boolean unlimitedOverdeliveryIsAllowed,
String stockType,
String taxCode,
String shippingInstruction,
String isInfoAtRegistration,
Boolean goodsReceiptIsExpected,
Boolean goodsReceiptIsNonValuated,
Boolean invoiceIsExpected,
Boolean invoiceIsGoodsReceiptBased,
Boolean evaldRcptSettlmtIsAllowed,
BigDecimal minRemainingShelfLife,
String qualityMgmtCtrlKey,
String qualityCertificateType,
String schedAgrmtCumulativeQtyControl,
Boolean cumulativeQuantityIsNotSent,
String schedgAgrmtRelCreationProfile,
String isRelevantForJITDelivSchedule,
LocalDateTime nextFcstDelivSchedSendingDate,
LocalDateTime nextJITDelivSchedSendingDate,
BigDecimal scheduleLineFirmOrderInDays,
BigDecimal schedLineSemiFirmOrderInDays,
String firmTradeOffZoneBindMRP,
List<SchAgrmtAcCnt> toSchAgrmtAcCnt,
List<SchAgrmtSchLine> toSchAgrmtSchLine) |
Modifier and Type | Method and Description |
---|---|
void |
addSchAgrmtAcCnt(SchAgrmtAcCnt... entity)
Adds elements to the list of associated SchAgrmtAcCnt entities.
|
void |
addSchAgrmtSchLine(SchAgrmtSchLine... entity)
Adds elements to the list of associated SchAgrmtSchLine entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static SchAgrmtItem.SchAgrmtItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<SchAgrmtAcCnt> |
fetchSchAgrmtAcCnt()
Fetches the SchAgrmtAcCnt entities (one to many) associated with this entity.
|
List<SchAgrmtSchLine> |
fetchSchAgrmtSchLine()
Fetches the SchAgrmtSchLine entities (one to many) associated with this entity.
|
static <T> SchAgrmtItemField<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 |
getAccountAssignmentCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getCompanyCode()
Constraints: Not nullable, Maximum length: 4
|
Boolean |
getCumulativeQuantityIsNotSent()
Constraints: none
|
protected String |
getDefaultServicePath() |
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
String |
getDocumentCurrency()
Constraints: Not nullable, Maximum length: 5
|
protected String |
getEntityCollection() |
Boolean |
getEvaldRcptSettlmtIsAllowed()
Constraints: none
|
String |
getFirmTradeOffZoneBindMRP()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getGoodsReceiptIsExpected()
Constraints: none
|
Boolean |
getGoodsReceiptIsNonValuated()
Constraints: none
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28
|
Boolean |
getInvoiceIsExpected()
Constraints: none
|
Boolean |
getInvoiceIsGoodsReceiptBased()
Constraints: none
|
String |
getIsInfoAtRegistration()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsInfoRecordUpdated()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getIsOrderAcknRqd()
Constraints: none
|
String |
getIsRelevantForJITDelivSchedule()
Constraints: Not nullable, Maximum length: 1
|
LocalDateTime |
getItemLastTransmissionDate()
Constraints: Not nullable, Precision: 0
|
BigDecimal |
getItemNetWeight()
Constraints: Not nullable, Precision: 13, Scale: 3
|
protected Map<String,Object> |
getKey() |
String |
getManualDeliveryAddressID()
Constraints: Not nullable, Maximum length: 10
|
String |
getManufacturerMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9
|
String |
getMaterialType()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getMinRemainingShelfLife()
Constraints: Not nullable, Precision: 4, Scale: 0
|
BigDecimal |
getNetPriceAmount()
Constraints: Not nullable, Precision: 12, Scale: 3
|
BigDecimal |
getNetPriceQuantity()
Constraints: Not nullable, Precision: 5, Scale: 0
|
LocalDateTime |
getNextFcstDelivSchedSendingDate()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getNextJITDelivSchedSendingDate()
Constraints: Not nullable, Precision: 0
|
BigDecimal |
getNoDaysReminder1()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getNoDaysReminder2()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getNoDaysReminder3()
Constraints: Not nullable, Precision: 3, Scale: 0
|
String |
getOrderPriceUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getOrderPriceUnitToOrderUnitNmrtr()
Constraints: Not nullable, Precision: 5, Scale: 0
|
String |
getOrderQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getOrdPriceUnitToOrderUnitDnmntr()
Constraints: Not nullable, Precision: 5, Scale: 0
|
BigDecimal |
getOverdelivTolrtdLmtRatioInPct()
Constraints: Not nullable, Precision: 3, Scale: 1
|
String |
getPlant()
Constraints: Not nullable, Maximum length: 4
|
Boolean |
getPriceIsToBePrinted()
Constraints: none
|
String |
getProductType()
Constraints: Not nullable, Maximum length: 2
|
String |
getPurchaseRequisition()
Constraints: Not nullable, Maximum length: 10
|
String |
getPurchaseRequisitionItem()
Constraints: Not nullable, Maximum length: 5
|
String |
getPurchasingDocumentCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getPurchasingDocumentDeletionCode()
Constraints: Not nullable, Maximum length: 1
|
String |
getPurchasingDocumentItemText()
Constraints: Not nullable, Maximum length: 40
|
String |
getPurchasingInfoRecord()
Constraints: Not nullable, Maximum length: 10
|
Boolean |
getPurgDocEstimatedPrice()
Constraints: none
|
String |
getPurgDocOrderAcknNumber()
Constraints: Not nullable, Maximum length: 20
|
String |
getQualityCertificateType()
Constraints: Not nullable, Maximum length: 4
|
String |
getQualityMgmtCtrlKey()
Constraints: Not nullable, Maximum length: 8
|
String |
getReferenceDeliveryAddressID()
Constraints: Not nullable, Maximum length: 10
|
String |
getRequirementTracking()
Constraints: Not nullable, Maximum length: 10
|
io.vavr.control.Option<List<SchAgrmtAcCnt>> |
getSchAgrmtAcCntIfPresent()
Retrieval of associated SchAgrmtAcCnt entities (one to many).
|
List<SchAgrmtAcCnt> |
getSchAgrmtAcCntOrFetch()
Retrieval of associated SchAgrmtAcCnt entities (one to many).
|
io.vavr.control.Option<List<SchAgrmtSchLine>> |
getSchAgrmtSchLineIfPresent()
Retrieval of associated SchAgrmtSchLine entities (one to many).
|
List<SchAgrmtSchLine> |
getSchAgrmtSchLineOrFetch()
Retrieval of associated SchAgrmtSchLine entities (one to many).
|
BigDecimal |
getSchedAgrmtAgreedCumQty()
Constraints: Not nullable, Precision: 13, Scale: 3
|
LocalDateTime |
getSchedAgrmtCumQtyReconcileDate()
Constraints: Not nullable, Precision: 0
|
String |
getSchedAgrmtCumulativeQtyControl()
Constraints: Not nullable, Maximum length: 1
|
String |
getSchedgAgrmtRelCreationProfile()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getSchedLineSemiFirmOrderInDays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getScheduleLineFirmOrderInDays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
String |
getSchedulingAgreement()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSchedulingAgreementItem()
(Key Field) Constraints: Not nullable, Maximum length: 5
|
String |
getShippingInstruction()
Constraints: Not nullable, Maximum length: 2
|
String |
getStockType()
Constraints: Not nullable, Maximum length: 1
|
String |
getStorageLocation()
Constraints: Not nullable, Maximum length: 4
|
String |
getSupplierMaterialNumber()
Constraints: Not nullable, Maximum length: 35
|
BigDecimal |
getTargetQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getTaxCode()
Constraints: Not nullable, Maximum length: 2
|
Class<SchAgrmtItem> |
getType() |
BigDecimal |
getUnderdelivTolrtdLmtRatioInPct()
Constraints: Not nullable, Precision: 3, Scale: 1
|
Boolean |
getUnlimitedOverdeliveryIsAllowed()
Constraints: none
|
String |
getWeightUnit()
Constraints: Not nullable, Maximum length: 3
|
int |
hashCode() |
void |
setAccountAssignmentCategory(String accountAssignmentCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setCompanyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setCumulativeQuantityIsNotSent(Boolean cumulativeQuantityIsNotSent)
Constraints: none
|
void |
setDocumentCurrency(String documentCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setEvaldRcptSettlmtIsAllowed(Boolean evaldRcptSettlmtIsAllowed)
Constraints: none
|
void |
setFirmTradeOffZoneBindMRP(String firmTradeOffZoneBindMRP)
Constraints: Not nullable, Maximum length: 1
|
void |
setGoodsReceiptIsExpected(Boolean goodsReceiptIsExpected)
Constraints: none
|
void |
setGoodsReceiptIsNonValuated(Boolean goodsReceiptIsNonValuated)
Constraints: none
|
void |
setIncotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
void |
setIncotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
void |
setInvoiceIsExpected(Boolean invoiceIsExpected)
Constraints: none
|
void |
setInvoiceIsGoodsReceiptBased(Boolean invoiceIsGoodsReceiptBased)
Constraints: none
|
void |
setIsInfoAtRegistration(String isInfoAtRegistration)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsInfoRecordUpdated(String isInfoRecordUpdated)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsOrderAcknRqd(Boolean isOrderAcknRqd)
Constraints: none
|
void |
setIsRelevantForJITDelivSchedule(String isRelevantForJITDelivSchedule)
Constraints: Not nullable, Maximum length: 1
|
void |
setItemLastTransmissionDate(LocalDateTime itemLastTransmissionDate)
Constraints: Not nullable, Precision: 0
|
void |
setItemNetWeight(BigDecimal itemNetWeight)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setManualDeliveryAddressID(String manualDeliveryAddressID)
Constraints: Not nullable, Maximum length: 10
|
void |
setManufacturerMaterial(String manufacturerMaterial)
Constraints: Not nullable, Maximum length: 40
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40
|
void |
setMaterialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9
|
void |
setMaterialType(String materialType)
Constraints: Not nullable, Maximum length: 4
|
void |
setMinRemainingShelfLife(BigDecimal minRemainingShelfLife)
Constraints: Not nullable, Precision: 4, Scale: 0
|
void |
setNetPriceAmount(BigDecimal netPriceAmount)
Constraints: Not nullable, Precision: 12, Scale: 3
|
void |
setNetPriceQuantity(BigDecimal netPriceQuantity)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setNextFcstDelivSchedSendingDate(LocalDateTime nextFcstDelivSchedSendingDate)
Constraints: Not nullable, Precision: 0
|
void |
setNextJITDelivSchedSendingDate(LocalDateTime nextJITDelivSchedSendingDate)
Constraints: Not nullable, Precision: 0
|
void |
setNoDaysReminder1(BigDecimal noDaysReminder1)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setNoDaysReminder2(BigDecimal noDaysReminder2)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setNoDaysReminder3(BigDecimal noDaysReminder3)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setOrderPriceUnit(String orderPriceUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setOrderPriceUnitToOrderUnitNmrtr(BigDecimal orderPriceUnitToOrderUnitNmrtr)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setOrderQuantityUnit(String orderQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setOrdPriceUnitToOrderUnitDnmntr(BigDecimal ordPriceUnitToOrderUnitDnmntr)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setOverdelivTolrtdLmtRatioInPct(BigDecimal overdelivTolrtdLmtRatioInPct)
Constraints: Not nullable, Precision: 3, Scale: 1
|
void |
setPlant(String plant)
Constraints: Not nullable, Maximum length: 4
|
void |
setPriceIsToBePrinted(Boolean priceIsToBePrinted)
Constraints: none
|
void |
setProductType(String productType)
Constraints: Not nullable, Maximum length: 2
|
void |
setPurchaseRequisition(String purchaseRequisition)
Constraints: Not nullable, Maximum length: 10
|
void |
setPurchaseRequisitionItem(String purchaseRequisitionItem)
Constraints: Not nullable, Maximum length: 5
|
void |
setPurchasingDocumentCategory(String purchasingDocumentCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setPurchasingDocumentDeletionCode(String purchasingDocumentDeletionCode)
Constraints: Not nullable, Maximum length: 1
|
void |
setPurchasingDocumentItemText(String purchasingDocumentItemText)
Constraints: Not nullable, Maximum length: 40
|
void |
setPurchasingInfoRecord(String purchasingInfoRecord)
Constraints: Not nullable, Maximum length: 10
|
void |
setPurgDocEstimatedPrice(Boolean purgDocEstimatedPrice)
Constraints: none
|
void |
setPurgDocOrderAcknNumber(String purgDocOrderAcknNumber)
Constraints: Not nullable, Maximum length: 20
|
void |
setQualityCertificateType(String qualityCertificateType)
Constraints: Not nullable, Maximum length: 4
|
void |
setQualityMgmtCtrlKey(String qualityMgmtCtrlKey)
Constraints: Not nullable, Maximum length: 8
|
void |
setReferenceDeliveryAddressID(String referenceDeliveryAddressID)
Constraints: Not nullable, Maximum length: 10
|
void |
setRequirementTracking(String requirementTracking)
Constraints: Not nullable, Maximum length: 10
|
void |
setSchAgrmtAcCnt(List<SchAgrmtAcCnt> value)
Overwrites the list of associated SchAgrmtAcCnt entities for the loaded navigation property
to_SchAgrmtAcCnt.
|
void |
setSchAgrmtSchLine(List<SchAgrmtSchLine> value)
Overwrites the list of associated SchAgrmtSchLine entities for the loaded navigation property
to_SchAgrmtSchLine.
|
void |
setSchedAgrmtAgreedCumQty(BigDecimal schedAgrmtAgreedCumQty)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setSchedAgrmtCumQtyReconcileDate(LocalDateTime schedAgrmtCumQtyReconcileDate)
Constraints: Not nullable, Precision: 0
|
void |
setSchedAgrmtCumulativeQtyControl(String schedAgrmtCumulativeQtyControl)
Constraints: Not nullable, Maximum length: 1
|
void |
setSchedgAgrmtRelCreationProfile(String schedgAgrmtRelCreationProfile)
Constraints: Not nullable, Maximum length: 4
|
void |
setSchedLineSemiFirmOrderInDays(BigDecimal schedLineSemiFirmOrderInDays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setScheduleLineFirmOrderInDays(BigDecimal scheduleLineFirmOrderInDays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setSchedulingAgreement(String schedulingAgreement)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSchedulingAgreementItem(String schedulingAgreementItem)
(Key Field) Constraints: Not nullable, Maximum length: 5
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setShippingInstruction(String shippingInstruction)
Constraints: Not nullable, Maximum length: 2
|
void |
setStockType(String stockType)
Constraints: Not nullable, Maximum length: 1
|
void |
setStorageLocation(String storageLocation)
Constraints: Not nullable, Maximum length: 4
|
void |
setSupplierMaterialNumber(String supplierMaterialNumber)
Constraints: Not nullable, Maximum length: 35
|
void |
setTargetQuantity(BigDecimal targetQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setTaxCode(String taxCode)
Constraints: Not nullable, Maximum length: 2
|
void |
setUnderdelivTolrtdLmtRatioInPct(BigDecimal underdelivTolrtdLmtRatioInPct)
Constraints: Not nullable, Precision: 3, Scale: 1
|
void |
setUnlimitedOverdeliveryIsAllowed(Boolean unlimitedOverdeliveryIsAllowed)
Constraints: none
|
void |
setWeightUnit(String weightUnit)
Constraints: Not nullable, Maximum length: 3
|
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 SchAgrmtItemSelectable ALL_FIELDS
public static final SchAgrmtItemField<String> SCHEDULING_AGREEMENT
public static final SchAgrmtItemField<String> SCHEDULING_AGREEMENT_ITEM
public static final SchAgrmtItemField<String> COMPANY_CODE
public static final SchAgrmtItemField<String> PURCHASING_DOCUMENT_CATEGORY
public static final SchAgrmtItemField<String> PURCHASING_DOCUMENT_ITEM_TEXT
public static final SchAgrmtItemField<String> MATERIAL
public static final SchAgrmtItemField<String> MANUFACTURER_MATERIAL
public static final SchAgrmtItemField<String> SUPPLIER_MATERIAL_NUMBER
public static final SchAgrmtItemField<String> MATERIAL_GROUP
public static final SchAgrmtItemField<String> PLANT
public static final SchAgrmtItemField<String> MANUAL_DELIVERY_ADDRESS_ID
public static final SchAgrmtItemField<String> REFERENCE_DELIVERY_ADDRESS_ID
public static final SchAgrmtItemField<String> INCOTERMS_CLASSIFICATION
public static final SchAgrmtItemField<String> INCOTERMS_TRANSFER_LOCATION
public static final SchAgrmtItemField<String> ORDER_QUANTITY_UNIT
public static final SchAgrmtItemField<BigDecimal> ITEM_NET_WEIGHT
public static final SchAgrmtItemField<String> WEIGHT_UNIT
public static final SchAgrmtItemField<BigDecimal> TARGET_QUANTITY
public static final SchAgrmtItemField<String> PURCHASE_REQUISITION
public static final SchAgrmtItemField<String> PURCHASE_REQUISITION_ITEM
public static final SchAgrmtItemField<BigDecimal> SCHED_AGRMT_AGREED_CUM_QTY
public static final SchAgrmtItemField<LocalDateTime> SCHED_AGRMT_CUM_QTY_RECONCILE_DATE
public static final SchAgrmtItemField<LocalDateTime> ITEM_LAST_TRANSMISSION_DATE
public static final SchAgrmtItemField<BigDecimal> NO_DAYS_REMINDER1
public static final SchAgrmtItemField<BigDecimal> NO_DAYS_REMINDER2
public static final SchAgrmtItemField<BigDecimal> NO_DAYS_REMINDER3
public static final SchAgrmtItemField<String> PURG_DOC_ORDER_ACKN_NUMBER
public static final SchAgrmtItemField<String> REQUIREMENT_TRACKING
public static final SchAgrmtItemField<Boolean> IS_ORDER_ACKN_RQD
public static final SchAgrmtItemField<Boolean> PURG_DOC_ESTIMATED_PRICE
public static final SchAgrmtItemField<Boolean> PRICE_IS_TO_BE_PRINTED
public static final SchAgrmtItemField<String> ACCOUNT_ASSIGNMENT_CATEGORY
public static final SchAgrmtItemField<BigDecimal> NET_PRICE_AMOUNT
public static final SchAgrmtItemField<BigDecimal> NET_PRICE_QUANTITY
public static final SchAgrmtItemField<String> ORDER_PRICE_UNIT
public static final SchAgrmtItemField<String> PRODUCT_TYPE
public static final SchAgrmtItemField<String> MATERIAL_TYPE
public static final SchAgrmtItemField<String> STORAGE_LOCATION
public static final SchAgrmtItemField<String> DOCUMENT_CURRENCY
public static final SchAgrmtItemField<String> IS_INFO_RECORD_UPDATED
public static final SchAgrmtItemField<String> PURCHASING_INFO_RECORD
public static final SchAgrmtItemField<BigDecimal> ORD_PRICE_UNIT_TO_ORDER_UNIT_DNMNTR
public static final SchAgrmtItemField<BigDecimal> ORDER_PRICE_UNIT_TO_ORDER_UNIT_NMRTR
public static final SchAgrmtItemField<String> PURCHASING_DOCUMENT_DELETION_CODE
public static final SchAgrmtItemField<BigDecimal> UNDERDELIV_TOLRTD_LMT_RATIO_IN_PCT
public static final SchAgrmtItemField<BigDecimal> OVERDELIV_TOLRTD_LMT_RATIO_IN_PCT
public static final SchAgrmtItemField<Boolean> UNLIMITED_OVERDELIVERY_IS_ALLOWED
public static final SchAgrmtItemField<String> STOCK_TYPE
public static final SchAgrmtItemField<String> TAX_CODE
public static final SchAgrmtItemField<String> SHIPPING_INSTRUCTION
public static final SchAgrmtItemField<String> IS_INFO_AT_REGISTRATION
public static final SchAgrmtItemField<Boolean> GOODS_RECEIPT_IS_EXPECTED
public static final SchAgrmtItemField<Boolean> GOODS_RECEIPT_IS_NON_VALUATED
public static final SchAgrmtItemField<Boolean> INVOICE_IS_EXPECTED
public static final SchAgrmtItemField<Boolean> INVOICE_IS_GOODS_RECEIPT_BASED
public static final SchAgrmtItemField<Boolean> EVALD_RCPT_SETTLMT_IS_ALLOWED
public static final SchAgrmtItemField<BigDecimal> MIN_REMAINING_SHELF_LIFE
public static final SchAgrmtItemField<String> QUALITY_MGMT_CTRL_KEY
public static final SchAgrmtItemField<String> QUALITY_CERTIFICATE_TYPE
public static final SchAgrmtItemField<String> SCHED_AGRMT_CUMULATIVE_QTY_CONTROL
public static final SchAgrmtItemField<Boolean> CUMULATIVE_QUANTITY_IS_NOT_SENT
public static final SchAgrmtItemField<String> SCHEDG_AGRMT_REL_CREATION_PROFILE
public static final SchAgrmtItemField<String> IS_RELEVANT_FOR_JIT_DELIV_SCHEDULE
public static final SchAgrmtItemField<LocalDateTime> NEXT_FCST_DELIV_SCHED_SENDING_DATE
public static final SchAgrmtItemField<LocalDateTime> NEXT_JIT_DELIV_SCHED_SENDING_DATE
public static final SchAgrmtItemField<BigDecimal> SCHEDULE_LINE_FIRM_ORDER_IN_DAYS
public static final SchAgrmtItemField<BigDecimal> SCHED_LINE_SEMI_FIRM_ORDER_IN_DAYS
public static final SchAgrmtItemField<String> FIRM_TRADE_OFF_ZONE_BIND_MRP
public static final SchAgrmtItemLink<SchAgrmtAcCnt> TO_SCH_AGRMT_AC_CNT
public static final SchAgrmtItemLink<SchAgrmtSchLine> TO_SCH_AGRMT_SCH_LINE
public SchAgrmtItem()
public SchAgrmtItem(@Nullable String schedulingAgreement, @Nullable String schedulingAgreementItem, @Nullable String companyCode, @Nullable String purchasingDocumentCategory, @Nullable String purchasingDocumentItemText, @Nullable String material, @Nullable String manufacturerMaterial, @Nullable String supplierMaterialNumber, @Nullable String materialGroup, @Nullable String plant, @Nullable String manualDeliveryAddressID, @Nullable String referenceDeliveryAddressID, @Nullable String incotermsClassification, @Nullable String incotermsTransferLocation, @Nullable String orderQuantityUnit, @Nullable BigDecimal itemNetWeight, @Nullable String weightUnit, @Nullable BigDecimal targetQuantity, @Nullable String purchaseRequisition, @Nullable String purchaseRequisitionItem, @Nullable BigDecimal schedAgrmtAgreedCumQty, @Nullable LocalDateTime schedAgrmtCumQtyReconcileDate, @Nullable LocalDateTime itemLastTransmissionDate, @Nullable BigDecimal noDaysReminder1, @Nullable BigDecimal noDaysReminder2, @Nullable BigDecimal noDaysReminder3, @Nullable String purgDocOrderAcknNumber, @Nullable String requirementTracking, @Nullable Boolean isOrderAcknRqd, @Nullable Boolean purgDocEstimatedPrice, @Nullable Boolean priceIsToBePrinted, @Nullable String accountAssignmentCategory, @Nullable BigDecimal netPriceAmount, @Nullable BigDecimal netPriceQuantity, @Nullable String orderPriceUnit, @Nullable String productType, @Nullable String materialType, @Nullable String storageLocation, @Nullable String documentCurrency, @Nullable String isInfoRecordUpdated, @Nullable String purchasingInfoRecord, @Nullable BigDecimal ordPriceUnitToOrderUnitDnmntr, @Nullable BigDecimal orderPriceUnitToOrderUnitNmrtr, @Nullable String purchasingDocumentDeletionCode, @Nullable BigDecimal underdelivTolrtdLmtRatioInPct, @Nullable BigDecimal overdelivTolrtdLmtRatioInPct, @Nullable Boolean unlimitedOverdeliveryIsAllowed, @Nullable String stockType, @Nullable String taxCode, @Nullable String shippingInstruction, @Nullable String isInfoAtRegistration, @Nullable Boolean goodsReceiptIsExpected, @Nullable Boolean goodsReceiptIsNonValuated, @Nullable Boolean invoiceIsExpected, @Nullable Boolean invoiceIsGoodsReceiptBased, @Nullable Boolean evaldRcptSettlmtIsAllowed, @Nullable BigDecimal minRemainingShelfLife, @Nullable String qualityMgmtCtrlKey, @Nullable String qualityCertificateType, @Nullable String schedAgrmtCumulativeQtyControl, @Nullable Boolean cumulativeQuantityIsNotSent, @Nullable String schedgAgrmtRelCreationProfile, @Nullable String isRelevantForJITDelivSchedule, @Nullable LocalDateTime nextFcstDelivSchedSendingDate, @Nullable LocalDateTime nextJITDelivSchedSendingDate, @Nullable BigDecimal scheduleLineFirmOrderInDays, @Nullable BigDecimal schedLineSemiFirmOrderInDays, @Nullable String firmTradeOffZoneBindMRP, List<SchAgrmtAcCnt> toSchAgrmtAcCnt, List<SchAgrmtSchLine> toSchAgrmtSchLine)
@Nonnull public Class<SchAgrmtItem> getType()
getType
in class VdmObject<SchAgrmtItem>
public void setSchedulingAgreement(@Nullable String schedulingAgreement)
Original property name from the Odata EDM: SchedulingAgreement
schedulingAgreement
- Alphanumeric key uniquely identifying the document.public void setSchedulingAgreementItem(@Nullable String schedulingAgreementItem)
Original property name from the Odata EDM: SchedulingAgreementItem
schedulingAgreementItem
- Specifies the number that uniquely identifies an item in .public void setCompanyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
companyCode
- The company code is an organizational unit within financial accounting.public void setPurchasingDocumentCategory(@Nullable String purchasingDocumentCategory)
Original property name from the Odata EDM: PurchasingDocumentCategory
purchasingDocumentCategory
- Allows a distinction to be made between the various purchasing documents.public void setPurchasingDocumentItemText(@Nullable String purchasingDocumentItemText)
Original property name from the Odata EDM: PurchasingDocumentItemText
purchasingDocumentItemText
- Short description of the material.public void setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setManufacturerMaterial(@Nullable String manufacturerMaterial)
Original property name from the Odata EDM: ManufacturerMaterial
This field is also used for MPN materials.
manufacturerMaterial
- Uniquely identifies a material.public void setSupplierMaterialNumber(@Nullable String supplierMaterialNumber)
Original property name from the Odata EDM: SupplierMaterialNumber
In most cases, the supplier uses a different number for the material than the one used in this system. The supplier's material number can therefore also be quoted in a purchase order for identification purposes.
supplierMaterialNumber
- Material number used by the supplier.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 setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
You use the plant key to determine, for instance, which plant is to receive ordered goods.
plant
- Specifies the key for a production facility or branch office within the company (that is, the company
code).public void setManualDeliveryAddressID(@Nullable String manualDeliveryAddressID)
Original property name from the Odata EDM: ManualDeliveryAddressID
manualDeliveryAddressID
- Manual address number in purchasing document itempublic void setReferenceDeliveryAddressID(@Nullable String referenceDeliveryAddressID)
Original property name from the Odata EDM: ReferenceDeliveryAddressID
referenceDeliveryAddressID
- Number of delivery addresspublic 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 setOrderQuantityUnit(@Nullable String orderQuantityUnit)
Original property name from the Odata EDM: OrderQuantityUnit
orderQuantityUnit
- Specifies the unit of measure in which the material is ordered.public void setItemNetWeight(@Nullable BigDecimal itemNetWeight)
Original property name from the Odata EDM: ItemNetWeight
The weight is expressed in terms of the unit of measure you specify in the field "unit of weight".
itemNetWeight
- Net weight of item per unit of weight.public void setWeightUnit(@Nullable String weightUnit)
Original property name from the Odata EDM: WeightUnit
If you specify a gross or net weight, you must enter the relevant unit of weight here.
weightUnit
- Unit in which the gross or net weight of this item is expressed.public void setTargetQuantity(@Nullable BigDecimal targetQuantity)
Original property name from the Odata EDM: TargetQuantity
targetQuantity
- Total quantity, agreed with the supplier, that can be released or scheduled against the relevant
agreement (contract or scheduling agreement).public void setPurchaseRequisition(@Nullable String purchaseRequisition)
Original property name from the Odata EDM: PurchaseRequisition
purchaseRequisition
- Alphanumeric key uniquely identifying the document.public void setPurchaseRequisitionItem(@Nullable String purchaseRequisitionItem)
Original property name from the Odata EDM: PurchaseRequisitionItem
purchaseRequisitionItem
- Specifies the number that uniquely identifies an item in .public void setSchedAgrmtAgreedCumQty(@Nullable BigDecimal schedAgrmtAgreedCumQty)
Original property name from the Odata EDM: SchedAgrmtAgreedCumQty
If, in the case of procurement by means of scheduling agreements, differences should arise between the cumulative quantities recorded by your supplier and those determined by the SAP system, you can reconcile the figures with the supplier.As of the reconciliation date, Purchasing and the supplier then both work on the basis of the same, agreed figures.If no reconciliation date has been entered and an agreed cumulative quantity has been maintained, the latter serves as a starting value. This may be useful, for example, if you are creating a new scheduling agreement and wish to start with the cumulative quantity of a previous scheduling agreement with the supplier.Calculation:Starting value = cumulative received quantity + agreed cumulative quantityIf a reconciliation date has been entered and an agreed cumulative quantity maintained, the latter quantity enables you to represent the situation at the change of the fiscal year.Calculation:Cumulative scheduled quantity = cumulative received quantity - agreed cumulative quantity
schedAgrmtAgreedCumQty
- Cumulative quantity of all delivery schedule lines relating to a scheduling agreement item, which has
been agreed between Purchasing and the supplier and is valid as of a certain date as the basis for the
further ongoing computation of the cumulative quantities.public void setSchedAgrmtCumQtyReconcileDate(@Nullable LocalDateTime schedAgrmtCumQtyReconcileDate)
Original property name from the Odata EDM: SchedAgrmtCumQtyReconcileDate
If no reconciliation date has been entered and an agreed cumulative quantity has been maintained, the latter quantity serves as a starting value.This may be useful, for example, if you are creating a new scheduling agreement and wish to start with the cumulative quantity of a previous scheduling agreement with the supplier.If a reconciliation date has been entered and an agreed cumulative quantity maintained, the latter quantity is a means of representing the situation at the change of the fiscal year. You can thus reset the cumulative scheduled quantity to 0 after the change of the year.
schedAgrmtCumQtyReconcileDate
- Date as of which the cumulative delivered quantity agreed with the supplier is valid.public void setItemLastTransmissionDate(@Nullable LocalDateTime itemLastTransmissionDate)
Original property name from the Odata EDM: ItemLastTransmissionDate
itemLastTransmissionDate
- Date on which the schedule for the item was last transmitted.public void setNoDaysReminder1(@Nullable BigDecimal noDaysReminder1)
Original property name from the Odata EDM: NoDaysReminder1
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
noDaysReminder1
- Number of days representing the time interval at which reminders or urging letters/messages (may also
be termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.public void setNoDaysReminder2(@Nullable BigDecimal noDaysReminder2)
Original property name from the Odata EDM: NoDaysReminder2
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
noDaysReminder2
- Number of days representing the time interval at which reminders or urging letters/messages (may also
be termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.public void setNoDaysReminder3(@Nullable BigDecimal noDaysReminder3)
Original property name from the Odata EDM: NoDaysReminder3
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
noDaysReminder3
- Number of days representing the time interval at which reminders or urging letters/messages (may also
be termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.public void setPurgDocOrderAcknNumber(@Nullable String purgDocOrderAcknNumber)
Original property name from the Odata EDM: PurgDocOrderAcknNumber
If you work exclusively with order acknowledgments and the supplier sends you one, enter an identifier defined within your firm (e.g. number assigned to incoming mail or date of receipt).NoteIf you work with several confirmation categories and a confirmation control key, you enter the confirmation data in the confirmation overview. This field is then for information only.
purgDocOrderAcknNumber
- Number of the supplier's order acknowledgment.public void setRequirementTracking(@Nullable String requirementTracking)
Original property name from the Odata EDM: RequirementTracking
The requirement tracking number from the purchase requisition is copied to the purchasing documents (for example: RFQ or purchase order) created with reference to a purchase requisition.The requirement tracking number thus enables you to group together the purchasing documents that exist for a certain material requirement.
requirementTracking
- Number that facilitates the monitoring of the procurement of required materials or services. This
number can relate to a requisition note (or requirement notice/slip) that was not generated in the
system.public void setIsOrderAcknRqd(@Nullable Boolean isOrderAcknRqd)
Original property name from the Odata EDM: IsOrderAcknRqd
isOrderAcknRqd
- Determines whether the purchasing document (purchase order, outline purchase agreement, etc.) is to be
acknowledged by the supplier.public void setPurgDocEstimatedPrice(@Nullable Boolean purgDocEstimatedPrice)
Original property name from the Odata EDM: PurgDocEstimatedPrice
If you do not know the exact net price of a material, you can indicate that the price is an estimated price. In consequence, a greater price variance is tolerated during invoice verification than would be the case in the event of an exact net price.
purgDocEstimatedPrice
- Indicates that this net price is merely an estimated price.public void setPriceIsToBePrinted(@Nullable Boolean priceIsToBePrinted)
Original property name from the Odata EDM: PriceIsToBePrinted
priceIsToBePrinted
- Determines whether or not the price is to be included in the purchase order printout.public void setAccountAssignmentCategory(@Nullable String accountAssignmentCategory)
Original property name from the Odata EDM: AccountAssignmentCategory
The account assignment category determines which account assignment data (such as cost center, account number and so on) is necessary for the item.
accountAssignmentCategory
- Specifies whether accounting for an item is to be effected via an auxiliary account (such as a cost
center).public void setNetPriceAmount(@Nullable BigDecimal netPriceAmount)
Original property name from the Odata EDM: NetPriceAmount
netPriceAmount
- Net price per price unit.public void setNetPriceQuantity(@Nullable BigDecimal netPriceQuantity)
Original property name from the Odata EDM: NetPriceQuantity
netPriceQuantity
- Price Unitpublic void setOrderPriceUnit(@Nullable String orderPriceUnit)
Original property name from the Odata EDM: OrderPriceUnit
Invoices are created using price units and purchase order price units which constitute the basis for value postings.They can be stored in the purchasing info record.A material or commodity (for example, oil) can be ordered by the liter, but the supplier's invoice shows a price of 2 dollars per kilogram.You enter 10 l as the order quantity and order unit, but specify 2 dollars per kg as purchase order price and purchase order price unit.In addition, you enter the conversion factor "order unit -> purchase order price unit" (for example 2 l per 1 kg) in the "details" data of the purchase order item.
orderPriceUnit
- Indicates the unit of measurement to which the purchase order price relates.public void setProductType(@Nullable String productType)
Original property name from the Odata EDM: ProductType
In the product type group you choose to either procure a material (by entering blank or 1) or a service (by entering 2).The procurement process is different for materials and services. For example, you can only maintain the field Service Performer when you purchase a service.If you enter a material number in a purchase order item, the product type group is derived automatically from the material type. In this case you can no longer maintain the product type group in the purchase order manually. If you do not enter a material number, you can maintain the field manually.This functionality is available for the following item categories:- Standard- Third-Party
productType
- Superordinate term that covers products that can be procured, for example materials and services.public void setMaterialType(@Nullable String materialType)
Original property name from the Odata EDM: MaterialType
The material type defines certain attributes of the material and has important control functions.
materialType
- Key that assigns the material to a group of materials such as raw materials, operating supplies or
trading goods.public void setStorageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
storageLocation
- Storage Locationpublic void setDocumentCurrency(@Nullable String documentCurrency)
Original property name from the Odata EDM: DocumentCurrency
documentCurrency
- Currency key for amounts in the system.public void setIsInfoRecordUpdated(@Nullable String isInfoRecordUpdated)
Original property name from the Odata EDM: IsInfoRecordUpdated
The purchasing info record for this supplier and material is to refer to this PO item, andThe item is to be valid for the entire purchasing organization or just for the plant.The indicator determines which prices and conditions are suggested in future PO items.Prices and conditions can apply to an entire purchasing organization or to a single plant within a purchasing organization.For example, if you create a purchase order for a plant for which an info record has been defined at plant level, the purchase order is based on the conditions in the plant info record and not on the conditions that apply to the purchasing organization.Enter the relevant plant key:AUpdating of the document number is effected at plant level as long as there is a purchasing info record at plant level. Otherwise the document number is updated at purchasing organization level.BUpdating is effected at plant level if plant conditions are allowed for the plant.CUpdating is effected without plant data if plant conditions are not necessary for the plant.The level at which updating of the document number may be effected is defined for each plant.
isInfoRecordUpdated
- Determines whether:public void setPurchasingInfoRecord(@Nullable String purchasingInfoRecord)
Original property name from the Odata EDM: PurchasingInfoRecord
purchasingInfoRecord
- Specifies the number that uniquely identifies a purchasing info record.public void setOrdPriceUnitToOrderUnitDnmntr(@Nullable BigDecimal ordPriceUnitToOrderUnitDnmntr)
Original property name from the Odata EDM: OrdPriceUnitToOrderUnitDnmntr
order unit: purchase order price unit.Enter the quantity in the order unit that applies for the quantity in the purchase order price unit.You want to order 200 l of a liquid. However, the supplier sells the liquid by the kilogram. 1 kg of this liquid corresponds to 4 l.As conversion factor, enter:Order quantity/order unit Order price qty./order price unit4 l --> 1 kg
ordPriceUnitToOrderUnitDnmntr
- Denominator of the quotient representing the ratiopublic void setOrderPriceUnitToOrderUnitNmrtr(@Nullable BigDecimal orderPriceUnitToOrderUnitNmrtr)
Original property name from the Odata EDM: OrderPriceUnitToOrderUnitNmrtr
Enter the quantity in the PO price unit that applies for the quantity in the order unit.You want to order 200 l of a liquid. However, the supplier sells the liquid by the kilogram. 1 kg of this liquid corresponds to 4 l.As conversion factor, enter:Order quantity/order unit Order price qty./order price unit4 l --> 1 kg
orderPriceUnitToOrderUnitNmrtr
- Numerator of the quotient representing the ratio order unit : purchase order price unit.public void setPurchasingDocumentDeletionCode(@Nullable String purchasingDocumentDeletionCode)
Original property name from the Odata EDM: PurchasingDocumentDeletionCode
You can set the deletion indicator by choosing Edit -> Delete if:You want to cancel an itemAn item is closed and can be archivedYou can set the blocking indicator by selecting the item and then choosing Edit -> Block if you do not want to allow subsequent functions for the item. Note that you must manually remove the indicator as soon as subsequent functions are allowed again.You have entered a purchase order item by mistake. You cancel it by setting the deletion indicator.A purchase order item has been delivered, invoiced, and paid for, and can now be archived. You can set the deletion indicator.
purchasingDocumentDeletionCode
- Determines whether the item in the purchasing document is deleted or blocked.public void setUnderdelivTolrtdLmtRatioInPct(@Nullable BigDecimal underdelivTolrtdLmtRatioInPct)
Original property name from the Odata EDM: UnderdelivTolrtdLmtRatioInPct
underdelivTolrtdLmtRatioInPct
- Percentage (based on the order quantity) up to which an underdelivery of this item will be accepted.public void setOverdelivTolrtdLmtRatioInPct(@Nullable BigDecimal overdelivTolrtdLmtRatioInPct)
Original property name from the Odata EDM: OverdelivTolrtdLmtRatioInPct
If you have set the indicator in the Partial delivery/Item field to 'D' (partial delivery allowed), this takes priority. It makes no sense to define a tolerance limit for overdelivery in such case.
overdelivTolrtdLmtRatioInPct
- Percentage (based on the order quantity) up to which an overdelivery of this item will be accepted.public void setUnlimitedOverdeliveryIsAllowed(@Nullable Boolean unlimitedOverdeliveryIsAllowed)
Original property name from the Odata EDM: UnlimitedOverdeliveryIsAllowed
unlimitedOverdeliveryIsAllowed
- Indicator that specifies whether unlimited overdelivery can be accepted for the item.public void setStockType(@Nullable String stockType)
Original property name from the Odata EDM: StockType
If the material is subject to quality inspection, a goods receipt is posted to stock in quality inspection.
stockType
- Specifies the stock to which the material is posted upon goods receipt (or from which it is posted
upon goods issue).public void setTaxCode(@Nullable String taxCode)
Original property name from the Odata EDM: TaxCode
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
taxCode
- The tax code represents a tax category which must be taken into consideration when making a tax return
to the tax authorities.public void setShippingInstruction(@Nullable String shippingInstruction)
Original property name from the Odata EDM: ShippingInstruction
Enter the key for the relevant shipping instructions.
shippingInstruction
- Specifies the packaging and shipping instructions issued to the supplier.public void setIsInfoAtRegistration(@Nullable String isInfoAtRegistration)
Original property name from the Odata EDM: IsInfoAtRegistration
This indicator is transferred to method FUNCTION_AFTER_REGISTRATION of BADI BORGR_REGISTRATION during registration and can be used to trigger actions (for example, Workflow, e-mail to the MRP controller).
isInfoAtRegistration
- This indicator is usually set by MRP controllers. It indicates that the MRP controller would like to
be notifies when inbound deliveries for this item are registered in the goods receipt office.public void setGoodsReceiptIsExpected(@Nullable Boolean goodsReceiptIsExpected)
Original property name from the Odata EDM: GoodsReceiptIsExpected
DependenciesIn the processing of production and process orders, the indicator specifies whether a goods receipt is allowed and expected for the order item.If the indicator is set, the order item is relevant to inventory management. The indicator is set during the creation of the order if the order is settled in respect of a material or a sales order item.
goodsReceiptIsExpected
- Specifies whether the item involves a goods receipt.public void setGoodsReceiptIsNonValuated(@Nullable Boolean goodsReceiptIsNonValuated)
Original property name from the Odata EDM: GoodsReceiptIsNonValuated
Set the indicator if goods receipts involving this material are not to be valuated. The valuation of the purchase order item will then take place at the time of invoice verification.NoteIf the indicator has been set for an item with the material type non- valuated, the quantity recorded in Inventory Management can differ from the value in Financial Accounting during the period between goods receipt and invoice receipt, since the value is not updated until the invoice is posted in Financial Accounting.
goodsReceiptIsNonValuated
- Specifies that the goods receipt for this item is not to be valuated.public void setInvoiceIsExpected(@Nullable Boolean invoiceIsExpected)
Original property name from the Odata EDM: InvoiceIsExpected
If the indicator is not set, the goods are to be delivered free of charge.
invoiceIsExpected
- Specifies whether an invoice receipt is linked to the purchase order item.public void setInvoiceIsGoodsReceiptBased(@Nullable Boolean invoiceIsGoodsReceiptBased)
Original property name from the Odata EDM: InvoiceIsGoodsReceiptBased
invoiceIsGoodsReceiptBased
- Indicator specifying that provision has been made for goods-receipt-based invoice verification for a
purchase order item or invoice item.public void setEvaldRcptSettlmtIsAllowed(@Nullable Boolean evaldRcptSettlmtIsAllowed)
Original property name from the Odata EDM: EvaldRcptSettlmtIsAllowed
If you wish to settle up with regard to PO or scheduling agreement items involving this supplier using Evaluated Receipt Settlement (ERS), this indicator must be set.This indicator must also be set if you wish to work with purchase orders used in conjunction with invoicing plans when procuring external services.
evaldRcptSettlmtIsAllowed
- Specifies that evaluated receipt settlement (ERS) or the automatic generation of invoices according to
an invoicing plan is to be possible in relation to materials supplied or services performed
(respectively) with regard to this supplier or this document item.public void setMinRemainingShelfLife(@Nullable BigDecimal minRemainingShelfLife)
Original property name from the Odata EDM: MinRemainingShelfLife
The period (day, week, month, year) depends on the entry in the Period indicator field.
minRemainingShelfLife
- Minimum amount of time for which the material must keep upon goods receipt for the goods receipt to be
accepted by the system.public void setQualityMgmtCtrlKey(@Nullable String qualityMgmtCtrlKey)
Original property name from the Odata EDM: QualityMgmtCtrlKey
If you activate the indicator for QM in procurement in the material master record at the client level, you must also store a control key at the plant level for quality management in procurement.Depending on the control indicators in the control key, you may have to maintain additional data.
qualityMgmtCtrlKey
- This key determines which conditions are valid for quality management in procurement.public void setQualityCertificateType(@Nullable String qualityCertificateType)
Original property name from the Odata EDM: QualityCertificateType
In procurement, you can use the certificate type to control a number of functions that have been defined for the processing of certificate receipts. The certificate type is specified in the QM data of the material for this purpose.The entry of a certificate type in the Quality Management view of the material only takes effect if you also set the indicator for QM in procurement.
qualityCertificateType
- Defines the content of a quality certificate.public void setSchedAgrmtCumulativeQtyControl(@Nullable String schedAgrmtCumulativeQtyControl)
Original property name from the Odata EDM: SchedAgrmtCumulativeQtyControl
You can use the Control Type to define how cumulative quantities in the scheduling agreement release are determined:Based on inbound deliveriesBased on goods receipts
schedAgrmtCumulativeQtyControl
- Determines how cumulative quantities (CQ) are calculated.public void setCumulativeQuantityIsNotSent(@Nullable Boolean cumulativeQuantityIsNotSent)
Original property name from the Odata EDM: CumulativeQuantityIsNotSent
Setting this flag for a scheduling agreement item has the following consequences:When a scheduling agreement release is created in SAP APO, no cumulative quantities are sent to the vendor for this item on release.No agreed cumulative quantity is calculated in the Set/Reset Agreed Cumulative Quantities and Reconciliation Date function (transaction ME88).No vendor cumulative quantity is expected in an advanced shipping notification item that is related to the scheduling agreement item.On creation of an inbound delivery, no cumulative quantity is calculated for items that are related to the scheduling agreement item.No Cumulative Quantity Imbalance Alert is raised in Inventory Collaboration Hub (ICH) for an inbound delivery item that is related to the scheduling agreement item.You can define whether or not cumulative quantities are sent in the SA release, regardless of the control type that you have chosen.This flag is transferred to SAP APO and is displayed there in the master data.
cumulativeQuantityIsNotSent
- Defines whether cumulative quantities are sent in scheduling agreement (SA) releases when SAP APO is
used.public void setSchedgAgrmtRelCreationProfile(@Nullable String schedgAgrmtRelCreationProfile)
Original property name from the Odata EDM: SchedgAgrmtRelCreationProfile
The creation periodicity of the releases (scheduling agreement delivery schedules), i.e. the period in which releases against a scheduling agreement are created and transmitted to the supplier, andThe way in which the quantities transmitted to the supplier are aggregated (starting from the current creation date of the release)Example:The creation periodicity for a scheduling agreement for which delivery schedule lines have been maintained over two years provides that releases are created weekly from 1.1. to 12.31 of the first year.The release quantities are to be aggregated as follows:For a period of 10 days starting from the current date of release creation, no aggregation; from the tenth to the thirtieth day, on a daily basis; and from the thirtieth day to the sixtieth day, on a monthly basis.
schedgAgrmtRelCreationProfile
- Controls:public void setIsRelevantForJITDelivSchedule(@Nullable String isRelevantForJITDelivSchedule)
Original property name from the Odata EDM: IsRelevantForJITDelivSchedule
isRelevantForJITDelivSchedule
- Determines whether it is possible to generate JIT delivery schedules in addition to forecast schedules
for a material specified in a purchase scheduling agreement.public void setNextFcstDelivSchedSendingDate(@Nullable LocalDateTime nextFcstDelivSchedSendingDate)
Original property name from the Odata EDM: NextFcstDelivSchedSendingDate
This date is taken into account in the process of automatic release (delivery schedule) generation. If the indicator is set to "With next creation date", only those scheduling agreement items with respect to which the creation date is earlier than the current date are chosen for release generation.
nextFcstDelivSchedSendingDate
- Date on which the next forecast delivery schedule is to be transmitted to the supplier.public void setNextJITDelivSchedSendingDate(@Nullable LocalDateTime nextJITDelivSchedSendingDate)
Original property name from the Odata EDM: NextJITDelivSchedSendingDate
This date is taken into account in the process of automatic release (delivery schedule) generation. If the indicator is set to "With next creation date", only those scheduling agreement items with respect to which the creation date is earlier than the current date are chosen for release generation.
nextJITDelivSchedSendingDate
- Date on which the next JIT delivery schedule is to be transmitted to the supplier.public void setScheduleLineFirmOrderInDays(@Nullable BigDecimal scheduleLineFirmOrderInDays)
Original property name from the Odata EDM: ScheduleLineFirmOrderInDays
! Firm zone I Trade-off zone I!------------------!-----I------------------------I--> Days! ! I I! !SA release creation date Schedule line dateFirm zone: (go-ahead for production)If the date of a schedule line lies within the firm zone, the supplier has the go-ahead to produce the relevant quantity with the assurance that the orderer will bear any and all material and production costs associated with the scheduled quantity in the event of subsequent cancellation by the latter.Trade-off zone: (go-ahead for procurement of input materials)If the date of a schedule line lies within the trade-off zone, the supplier has the go-ahead to purchase any input materials necessary to produce the scheduled quantity. The orderer will recompense him in full for such outlay (but not for any other production costs) in the event that he should subsequently cancel the scheduled quantity.Schedule lines that lie beyond the firm and trade-off zones fall within the planning zone (forecast zone) and are for rough guidance only, being without any commitment on the part of the orderer.In the "Firm zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the firm zone ends and the trade-off zone begins.In the "Trade-off zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the trade-off zone ends.If the firm zone ends in one month, enter 30 in the "Firm zone" field.If the trade-off zone ends one month after the firm zone, enter 60 in the "Trade-off zone" field.In the standard system, the end date for production go-ahead is calculated at the time of SA release creation from the firm zone. The end date for material go-ahead is calculated from the trade-off zone. These dates are displayed in the header of the relevant scheduling agreement release.When an SA release is transmitted to the supplier via IDoc, the end dates for production and material go-ahead are determined from the firm and trade-off zones and the SA release creation date. These dates are shown in the sales scheduling agreement in the SA release header in the relevant fields (End of Production Go-Ahead, End of Material Go-Ahead).
scheduleLineFirmOrderInDays
- One of two periods specifying the degree to which the delivery schedule lines of a scheduling
agreement release are classified as firm or semi-firm.public void setSchedLineSemiFirmOrderInDays(@Nullable BigDecimal schedLineSemiFirmOrderInDays)
Original property name from the Odata EDM: SchedLineSemiFirmOrderInDays
! Firm zone I Trade-off zone I!------------------!-----I------------------------I--> Days! ! I I! !SA release creation date Schedule line dateFirm zone: (go-ahead for production)If the date of a schedule line lies within the firm zone, the supplier has the go-ahead to produce the relevant quantity with the assurance that the orderer will bear any and all material and production costs associated with the scheduled quantity in the event of subsequent cancellation by the latter.Trade-off zone: (go-ahead for procurement of input materials)If the date of a schedule line lies within the trade-off zone, the supplier has the go-ahead to purchase any input materials necessary to produce the scheduled quantity. The orderer will recompense him in full for such outlay (but not for any other production costs) in the event that he should subsequently cancel the scheduled quantity.Schedule lines that lie beyond the firm and trade-off zones fall within the planning zone (forecast zone) and are for rough guidance only, being without any commitment on the part of the orderer.In the "Firm zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the firm zone ends and the trade-off zone begins.In the "Trade-off zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the trade-off zone ends.If the firm zone ends in one month, enter 30 in the "Firm zone" field.If the trade-off zone ends one month after the firm zone, enter 60 in the "Trade-off zone" field.In the standard system, the end date for production go-ahead is calculated at the time of SA release creation from the firm zone. The end date for material go-ahead is calculated from the trade-off zone. These dates are displayed in the header of the relevant scheduling agreement release.When an SA release is transmitted to the supplier via IDoc, the end dates for production and material go-ahead are determined from the firm and trade-off zones and the SA release creation date. These dates are shown in the sales scheduling agreement in the SA release header in the relevant fields (End of Production Go-Ahead, End of Material Go-Ahead).
schedLineSemiFirmOrderInDays
- One of two periods specifying the degree to which the delivery schedule lines of a scheduling
agreement release are classified as firm or semi-firm.public void setFirmTradeOffZoneBindMRP(@Nullable String firmTradeOffZoneBindMRP)
Original property name from the Odata EDM: FirmTradeOffZoneBindMRP
firmTradeOffZoneBindMRP
- Specifies whether or not the schedule lines lying within the firm and trade-off zones can be changed
during the planning run.protected String getEntityCollection()
getEntityCollection
in class VdmEntity<SchAgrmtItem>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<SchAgrmtItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SchAgrmtItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SchAgrmtItem>
@Nonnull public static <T> SchAgrmtItemField<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> SchAgrmtItemField<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<SchAgrmtItem>
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<SchAgrmtItem>
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<SchAgrmtItem>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
getDefaultServicePath
in class VdmEntity<SchAgrmtItem>
@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SchAgrmtItem>
@Nonnull public List<SchAgrmtAcCnt> fetchSchAgrmtAcCnt() 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<SchAgrmtAcCnt> getSchAgrmtAcCntOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SchAgrmtAcCnt of a queried SchAgrmtItem 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<SchAgrmtAcCnt>> getSchAgrmtAcCntIfPresent()
If the navigation property for an entity SchAgrmtItem 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 setSchAgrmtAcCnt(@Nonnull List<SchAgrmtAcCnt> value)
If the navigation property to_SchAgrmtAcCnt of a queried SchAgrmtItem 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 SchAgrmtAcCnt entities.public void addSchAgrmtAcCnt(SchAgrmtAcCnt... entity)
If the navigation property to_SchAgrmtAcCnt of a queried SchAgrmtItem 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 SchAgrmtAcCnt entities.@Nonnull public List<SchAgrmtSchLine> fetchSchAgrmtSchLine() 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<SchAgrmtSchLine> getSchAgrmtSchLineOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SchAgrmtSchLine of a queried SchAgrmtItem 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<SchAgrmtSchLine>> getSchAgrmtSchLineIfPresent()
If the navigation property for an entity SchAgrmtItem 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 setSchAgrmtSchLine(@Nonnull List<SchAgrmtSchLine> value)
If the navigation property to_SchAgrmtSchLine of a queried SchAgrmtItem 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 SchAgrmtSchLine entities.public void addSchAgrmtSchLine(SchAgrmtSchLine... entity)
If the navigation property to_SchAgrmtSchLine of a queried SchAgrmtItem 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 SchAgrmtSchLine entities.public static SchAgrmtItem.SchAgrmtItemBuilder builder()
@Nullable public String getSchedulingAgreement()
Original property name from the Odata EDM: SchedulingAgreement
@Nullable public String getSchedulingAgreementItem()
Original property name from the Odata EDM: SchedulingAgreementItem
@Nullable public String getCompanyCode()
Original property name from the Odata EDM: CompanyCode
@Nullable public String getPurchasingDocumentCategory()
Original property name from the Odata EDM: PurchasingDocumentCategory
@Nullable public String getPurchasingDocumentItemText()
Original property name from the Odata EDM: PurchasingDocumentItemText
@Nullable public String getMaterial()
Original property name from the Odata EDM: Material
@Nullable public String getManufacturerMaterial()
Original property name from the Odata EDM: ManufacturerMaterial
This field is also used for MPN materials.
@Nullable public String getSupplierMaterialNumber()
Original property name from the Odata EDM: SupplierMaterialNumber
In most cases, the supplier uses a different number for the material than the one used in this system. The supplier's material number can therefore also be quoted in a purchase order for identification purposes.
@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 getPlant()
Original property name from the Odata EDM: Plant
You use the plant key to determine, for instance, which plant is to receive ordered goods.
@Nullable public String getManualDeliveryAddressID()
Original property name from the Odata EDM: ManualDeliveryAddressID
@Nullable public String getReferenceDeliveryAddressID()
Original property name from the Odata EDM: ReferenceDeliveryAddressID
@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 getOrderQuantityUnit()
Original property name from the Odata EDM: OrderQuantityUnit
@Nullable public BigDecimal getItemNetWeight()
Original property name from the Odata EDM: ItemNetWeight
The weight is expressed in terms of the unit of measure you specify in the field "unit of weight".
@Nullable public String getWeightUnit()
Original property name from the Odata EDM: WeightUnit
If you specify a gross or net weight, you must enter the relevant unit of weight here.
@Nullable public BigDecimal getTargetQuantity()
Original property name from the Odata EDM: TargetQuantity
@Nullable public String getPurchaseRequisition()
Original property name from the Odata EDM: PurchaseRequisition
@Nullable public String getPurchaseRequisitionItem()
Original property name from the Odata EDM: PurchaseRequisitionItem
@Nullable public BigDecimal getSchedAgrmtAgreedCumQty()
Original property name from the Odata EDM: SchedAgrmtAgreedCumQty
If, in the case of procurement by means of scheduling agreements, differences should arise between the cumulative quantities recorded by your supplier and those determined by the SAP system, you can reconcile the figures with the supplier.As of the reconciliation date, Purchasing and the supplier then both work on the basis of the same, agreed figures.If no reconciliation date has been entered and an agreed cumulative quantity has been maintained, the latter serves as a starting value. This may be useful, for example, if you are creating a new scheduling agreement and wish to start with the cumulative quantity of a previous scheduling agreement with the supplier.Calculation:Starting value = cumulative received quantity + agreed cumulative quantityIf a reconciliation date has been entered and an agreed cumulative quantity maintained, the latter quantity enables you to represent the situation at the change of the fiscal year.Calculation:Cumulative scheduled quantity = cumulative received quantity - agreed cumulative quantity
@Nullable public LocalDateTime getSchedAgrmtCumQtyReconcileDate()
Original property name from the Odata EDM: SchedAgrmtCumQtyReconcileDate
If no reconciliation date has been entered and an agreed cumulative quantity has been maintained, the latter quantity serves as a starting value.This may be useful, for example, if you are creating a new scheduling agreement and wish to start with the cumulative quantity of a previous scheduling agreement with the supplier.If a reconciliation date has been entered and an agreed cumulative quantity maintained, the latter quantity is a means of representing the situation at the change of the fiscal year. You can thus reset the cumulative scheduled quantity to 0 after the change of the year.
@Nullable public LocalDateTime getItemLastTransmissionDate()
Original property name from the Odata EDM: ItemLastTransmissionDate
@Nullable public BigDecimal getNoDaysReminder1()
Original property name from the Odata EDM: NoDaysReminder1
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
@Nullable public BigDecimal getNoDaysReminder2()
Original property name from the Odata EDM: NoDaysReminder2
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
@Nullable public BigDecimal getNoDaysReminder3()
Original property name from the Odata EDM: NoDaysReminder3
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
@Nullable public String getPurgDocOrderAcknNumber()
Original property name from the Odata EDM: PurgDocOrderAcknNumber
If you work exclusively with order acknowledgments and the supplier sends you one, enter an identifier defined within your firm (e.g. number assigned to incoming mail or date of receipt).NoteIf you work with several confirmation categories and a confirmation control key, you enter the confirmation data in the confirmation overview. This field is then for information only.
@Nullable public String getRequirementTracking()
Original property name from the Odata EDM: RequirementTracking
The requirement tracking number from the purchase requisition is copied to the purchasing documents (for example: RFQ or purchase order) created with reference to a purchase requisition.The requirement tracking number thus enables you to group together the purchasing documents that exist for a certain material requirement.
@Nullable public Boolean getIsOrderAcknRqd()
Original property name from the Odata EDM: IsOrderAcknRqd
@Nullable public Boolean getPurgDocEstimatedPrice()
Original property name from the Odata EDM: PurgDocEstimatedPrice
If you do not know the exact net price of a material, you can indicate that the price is an estimated price. In consequence, a greater price variance is tolerated during invoice verification than would be the case in the event of an exact net price.
@Nullable public Boolean getPriceIsToBePrinted()
Original property name from the Odata EDM: PriceIsToBePrinted
@Nullable public String getAccountAssignmentCategory()
Original property name from the Odata EDM: AccountAssignmentCategory
The account assignment category determines which account assignment data (such as cost center, account number and so on) is necessary for the item.
@Nullable public BigDecimal getNetPriceAmount()
Original property name from the Odata EDM: NetPriceAmount
@Nullable public BigDecimal getNetPriceQuantity()
Original property name from the Odata EDM: NetPriceQuantity
@Nullable public String getOrderPriceUnit()
Original property name from the Odata EDM: OrderPriceUnit
Invoices are created using price units and purchase order price units which constitute the basis for value postings.They can be stored in the purchasing info record.A material or commodity (for example, oil) can be ordered by the liter, but the supplier's invoice shows a price of 2 dollars per kilogram.You enter 10 l as the order quantity and order unit, but specify 2 dollars per kg as purchase order price and purchase order price unit.In addition, you enter the conversion factor "order unit -> purchase order price unit" (for example 2 l per 1 kg) in the "details" data of the purchase order item.
@Nullable public String getProductType()
Original property name from the Odata EDM: ProductType
In the product type group you choose to either procure a material (by entering blank or 1) or a service (by entering 2).The procurement process is different for materials and services. For example, you can only maintain the field Service Performer when you purchase a service.If you enter a material number in a purchase order item, the product type group is derived automatically from the material type. In this case you can no longer maintain the product type group in the purchase order manually. If you do not enter a material number, you can maintain the field manually.This functionality is available for the following item categories:- Standard- Third-Party
@Nullable public String getMaterialType()
Original property name from the Odata EDM: MaterialType
The material type defines certain attributes of the material and has important control functions.
@Nullable public String getStorageLocation()
Original property name from the Odata EDM: StorageLocation
@Nullable public String getDocumentCurrency()
Original property name from the Odata EDM: DocumentCurrency
@Nullable public String getIsInfoRecordUpdated()
Original property name from the Odata EDM: IsInfoRecordUpdated
The purchasing info record for this supplier and material is to refer to this PO item, andThe item is to be valid for the entire purchasing organization or just for the plant.The indicator determines which prices and conditions are suggested in future PO items.Prices and conditions can apply to an entire purchasing organization or to a single plant within a purchasing organization.For example, if you create a purchase order for a plant for which an info record has been defined at plant level, the purchase order is based on the conditions in the plant info record and not on the conditions that apply to the purchasing organization.Enter the relevant plant key:AUpdating of the document number is effected at plant level as long as there is a purchasing info record at plant level. Otherwise the document number is updated at purchasing organization level.BUpdating is effected at plant level if plant conditions are allowed for the plant.CUpdating is effected without plant data if plant conditions are not necessary for the plant.The level at which updating of the document number may be effected is defined for each plant.
@Nullable public String getPurchasingInfoRecord()
Original property name from the Odata EDM: PurchasingInfoRecord
@Nullable public BigDecimal getOrdPriceUnitToOrderUnitDnmntr()
Original property name from the Odata EDM: OrdPriceUnitToOrderUnitDnmntr
order unit: purchase order price unit.Enter the quantity in the order unit that applies for the quantity in the purchase order price unit.You want to order 200 l of a liquid. However, the supplier sells the liquid by the kilogram. 1 kg of this liquid corresponds to 4 l.As conversion factor, enter:Order quantity/order unit Order price qty./order price unit4 l --> 1 kg
@Nullable public BigDecimal getOrderPriceUnitToOrderUnitNmrtr()
Original property name from the Odata EDM: OrderPriceUnitToOrderUnitNmrtr
Enter the quantity in the PO price unit that applies for the quantity in the order unit.You want to order 200 l of a liquid. However, the supplier sells the liquid by the kilogram. 1 kg of this liquid corresponds to 4 l.As conversion factor, enter:Order quantity/order unit Order price qty./order price unit4 l --> 1 kg
@Nullable public String getPurchasingDocumentDeletionCode()
Original property name from the Odata EDM: PurchasingDocumentDeletionCode
You can set the deletion indicator by choosing Edit -> Delete if:You want to cancel an itemAn item is closed and can be archivedYou can set the blocking indicator by selecting the item and then choosing Edit -> Block if you do not want to allow subsequent functions for the item. Note that you must manually remove the indicator as soon as subsequent functions are allowed again.You have entered a purchase order item by mistake. You cancel it by setting the deletion indicator.A purchase order item has been delivered, invoiced, and paid for, and can now be archived. You can set the deletion indicator.
@Nullable public BigDecimal getUnderdelivTolrtdLmtRatioInPct()
Original property name from the Odata EDM: UnderdelivTolrtdLmtRatioInPct
@Nullable public BigDecimal getOverdelivTolrtdLmtRatioInPct()
Original property name from the Odata EDM: OverdelivTolrtdLmtRatioInPct
If you have set the indicator in the Partial delivery/Item field to 'D' (partial delivery allowed), this takes priority. It makes no sense to define a tolerance limit for overdelivery in such case.
@Nullable public Boolean getUnlimitedOverdeliveryIsAllowed()
Original property name from the Odata EDM: UnlimitedOverdeliveryIsAllowed
@Nullable public String getStockType()
Original property name from the Odata EDM: StockType
If the material is subject to quality inspection, a goods receipt is posted to stock in quality inspection.
@Nullable public String getTaxCode()
Original property name from the Odata EDM: TaxCode
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
@Nullable public String getShippingInstruction()
Original property name from the Odata EDM: ShippingInstruction
Enter the key for the relevant shipping instructions.
@Nullable public String getIsInfoAtRegistration()
Original property name from the Odata EDM: IsInfoAtRegistration
This indicator is transferred to method FUNCTION_AFTER_REGISTRATION of BADI BORGR_REGISTRATION during registration and can be used to trigger actions (for example, Workflow, e-mail to the MRP controller).
@Nullable public Boolean getGoodsReceiptIsExpected()
Original property name from the Odata EDM: GoodsReceiptIsExpected
DependenciesIn the processing of production and process orders, the indicator specifies whether a goods receipt is allowed and expected for the order item.If the indicator is set, the order item is relevant to inventory management. The indicator is set during the creation of the order if the order is settled in respect of a material or a sales order item.
@Nullable public Boolean getGoodsReceiptIsNonValuated()
Original property name from the Odata EDM: GoodsReceiptIsNonValuated
Set the indicator if goods receipts involving this material are not to be valuated. The valuation of the purchase order item will then take place at the time of invoice verification.NoteIf the indicator has been set for an item with the material type non- valuated, the quantity recorded in Inventory Management can differ from the value in Financial Accounting during the period between goods receipt and invoice receipt, since the value is not updated until the invoice is posted in Financial Accounting.
@Nullable public Boolean getInvoiceIsExpected()
Original property name from the Odata EDM: InvoiceIsExpected
If the indicator is not set, the goods are to be delivered free of charge.
@Nullable public Boolean getInvoiceIsGoodsReceiptBased()
Original property name from the Odata EDM: InvoiceIsGoodsReceiptBased
@Nullable public Boolean getEvaldRcptSettlmtIsAllowed()
Original property name from the Odata EDM: EvaldRcptSettlmtIsAllowed
If you wish to settle up with regard to PO or scheduling agreement items involving this supplier using Evaluated Receipt Settlement (ERS), this indicator must be set.This indicator must also be set if you wish to work with purchase orders used in conjunction with invoicing plans when procuring external services.
@Nullable public BigDecimal getMinRemainingShelfLife()
Original property name from the Odata EDM: MinRemainingShelfLife
The period (day, week, month, year) depends on the entry in the Period indicator field.
@Nullable public String getQualityMgmtCtrlKey()
Original property name from the Odata EDM: QualityMgmtCtrlKey
If you activate the indicator for QM in procurement in the material master record at the client level, you must also store a control key at the plant level for quality management in procurement.Depending on the control indicators in the control key, you may have to maintain additional data.
@Nullable public String getQualityCertificateType()
Original property name from the Odata EDM: QualityCertificateType
In procurement, you can use the certificate type to control a number of functions that have been defined for the processing of certificate receipts. The certificate type is specified in the QM data of the material for this purpose.The entry of a certificate type in the Quality Management view of the material only takes effect if you also set the indicator for QM in procurement.
@Nullable public String getSchedAgrmtCumulativeQtyControl()
Original property name from the Odata EDM: SchedAgrmtCumulativeQtyControl
You can use the Control Type to define how cumulative quantities in the scheduling agreement release are determined:Based on inbound deliveriesBased on goods receipts
@Nullable public Boolean getCumulativeQuantityIsNotSent()
Original property name from the Odata EDM: CumulativeQuantityIsNotSent
Setting this flag for a scheduling agreement item has the following consequences:When a scheduling agreement release is created in SAP APO, no cumulative quantities are sent to the vendor for this item on release.No agreed cumulative quantity is calculated in the Set/Reset Agreed Cumulative Quantities and Reconciliation Date function (transaction ME88).No vendor cumulative quantity is expected in an advanced shipping notification item that is related to the scheduling agreement item.On creation of an inbound delivery, no cumulative quantity is calculated for items that are related to the scheduling agreement item.No Cumulative Quantity Imbalance Alert is raised in Inventory Collaboration Hub (ICH) for an inbound delivery item that is related to the scheduling agreement item.You can define whether or not cumulative quantities are sent in the SA release, regardless of the control type that you have chosen.This flag is transferred to SAP APO and is displayed there in the master data.
@Nullable public String getSchedgAgrmtRelCreationProfile()
Original property name from the Odata EDM: SchedgAgrmtRelCreationProfile
The creation periodicity of the releases (scheduling agreement delivery schedules), i.e. the period in which releases against a scheduling agreement are created and transmitted to the supplier, andThe way in which the quantities transmitted to the supplier are aggregated (starting from the current creation date of the release)Example:The creation periodicity for a scheduling agreement for which delivery schedule lines have been maintained over two years provides that releases are created weekly from 1.1. to 12.31 of the first year.The release quantities are to be aggregated as follows:For a period of 10 days starting from the current date of release creation, no aggregation; from the tenth to the thirtieth day, on a daily basis; and from the thirtieth day to the sixtieth day, on a monthly basis.
@Nullable public String getIsRelevantForJITDelivSchedule()
Original property name from the Odata EDM: IsRelevantForJITDelivSchedule
@Nullable public LocalDateTime getNextFcstDelivSchedSendingDate()
Original property name from the Odata EDM: NextFcstDelivSchedSendingDate
This date is taken into account in the process of automatic release (delivery schedule) generation. If the indicator is set to "With next creation date", only those scheduling agreement items with respect to which the creation date is earlier than the current date are chosen for release generation.
@Nullable public LocalDateTime getNextJITDelivSchedSendingDate()
Original property name from the Odata EDM: NextJITDelivSchedSendingDate
This date is taken into account in the process of automatic release (delivery schedule) generation. If the indicator is set to "With next creation date", only those scheduling agreement items with respect to which the creation date is earlier than the current date are chosen for release generation.
@Nullable public BigDecimal getScheduleLineFirmOrderInDays()
Original property name from the Odata EDM: ScheduleLineFirmOrderInDays
! Firm zone I Trade-off zone I!------------------!-----I------------------------I--> Days! ! I I! !SA release creation date Schedule line dateFirm zone: (go-ahead for production)If the date of a schedule line lies within the firm zone, the supplier has the go-ahead to produce the relevant quantity with the assurance that the orderer will bear any and all material and production costs associated with the scheduled quantity in the event of subsequent cancellation by the latter.Trade-off zone: (go-ahead for procurement of input materials)If the date of a schedule line lies within the trade-off zone, the supplier has the go-ahead to purchase any input materials necessary to produce the scheduled quantity. The orderer will recompense him in full for such outlay (but not for any other production costs) in the event that he should subsequently cancel the scheduled quantity.Schedule lines that lie beyond the firm and trade-off zones fall within the planning zone (forecast zone) and are for rough guidance only, being without any commitment on the part of the orderer.In the "Firm zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the firm zone ends and the trade-off zone begins.In the "Trade-off zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the trade-off zone ends.If the firm zone ends in one month, enter 30 in the "Firm zone" field.If the trade-off zone ends one month after the firm zone, enter 60 in the "Trade-off zone" field.In the standard system, the end date for production go-ahead is calculated at the time of SA release creation from the firm zone. The end date for material go-ahead is calculated from the trade-off zone. These dates are displayed in the header of the relevant scheduling agreement release.When an SA release is transmitted to the supplier via IDoc, the end dates for production and material go-ahead are determined from the firm and trade-off zones and the SA release creation date. These dates are shown in the sales scheduling agreement in the SA release header in the relevant fields (End of Production Go-Ahead, End of Material Go-Ahead).
@Nullable public BigDecimal getSchedLineSemiFirmOrderInDays()
Original property name from the Odata EDM: SchedLineSemiFirmOrderInDays
! Firm zone I Trade-off zone I!------------------!-----I------------------------I--> Days! ! I I! !SA release creation date Schedule line dateFirm zone: (go-ahead for production)If the date of a schedule line lies within the firm zone, the supplier has the go-ahead to produce the relevant quantity with the assurance that the orderer will bear any and all material and production costs associated with the scheduled quantity in the event of subsequent cancellation by the latter.Trade-off zone: (go-ahead for procurement of input materials)If the date of a schedule line lies within the trade-off zone, the supplier has the go-ahead to purchase any input materials necessary to produce the scheduled quantity. The orderer will recompense him in full for such outlay (but not for any other production costs) in the event that he should subsequently cancel the scheduled quantity.Schedule lines that lie beyond the firm and trade-off zones fall within the planning zone (forecast zone) and are for rough guidance only, being without any commitment on the part of the orderer.In the "Firm zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the firm zone ends and the trade-off zone begins.In the "Trade-off zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the trade-off zone ends.If the firm zone ends in one month, enter 30 in the "Firm zone" field.If the trade-off zone ends one month after the firm zone, enter 60 in the "Trade-off zone" field.In the standard system, the end date for production go-ahead is calculated at the time of SA release creation from the firm zone. The end date for material go-ahead is calculated from the trade-off zone. These dates are displayed in the header of the relevant scheduling agreement release.When an SA release is transmitted to the supplier via IDoc, the end dates for production and material go-ahead are determined from the firm and trade-off zones and the SA release creation date. These dates are shown in the sales scheduling agreement in the SA release header in the relevant fields (End of Production Go-Ahead, End of Material Go-Ahead).
@Nullable public String getFirmTradeOffZoneBindMRP()
Original property name from the Odata EDM: FirmTradeOffZoneBindMRP
public String toString()
toString
in class VdmObject<SchAgrmtItem>
public boolean equals(Object o)
equals
in class VdmObject<SchAgrmtItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<SchAgrmtItem>
public int hashCode()
hashCode
in class VdmObject<SchAgrmtItem>
Copyright © 2019 SAP SE. All rights reserved.