SchAgrmtItem.SchAgrmtItemBuilder (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.schedulingagreement.SchAgrmtItem.SchAgrmtItemBuilder

Enclosing class:

SchAgrmtItem
```
public static final class SchAgrmtItem.SchAgrmtItemBuilder
extends Object
```
Helper class to allow for fluent creation of SchAgrmtItem instances.

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`SchAgrmtItem.SchAgrmtItemBuilder`	`accountAssignmentCategory(String accountAssignmentCategory)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem`	`build()`
`SchAgrmtItem.SchAgrmtItemBuilder`	`companyCode(String companyCode)` Constraints: Not nullable, Maximum length: 4
`SchAgrmtItem.SchAgrmtItemBuilder`	`cumulativeQuantityIsNotSent(Boolean cumulativeQuantityIsNotSent)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`documentCurrency(String documentCurrency)` Constraints: Not nullable, Maximum length: 5
`SchAgrmtItem.SchAgrmtItemBuilder`	`evaldRcptSettlmtIsAllowed(Boolean evaldRcptSettlmtIsAllowed)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`firmTradeOffZoneBindMRP(String firmTradeOffZoneBindMRP)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`goodsReceiptIsExpected(Boolean goodsReceiptIsExpected)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`goodsReceiptIsNonValuated(Boolean goodsReceiptIsNonValuated)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`incotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3
`SchAgrmtItem.SchAgrmtItemBuilder`	`incotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28
`SchAgrmtItem.SchAgrmtItemBuilder`	`invoiceIsExpected(Boolean invoiceIsExpected)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`invoiceIsGoodsReceiptBased(Boolean invoiceIsGoodsReceiptBased)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`isInfoAtRegistration(String isInfoAtRegistration)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`isInfoRecordUpdated(String isInfoRecordUpdated)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`isOrderAcknRqd(Boolean isOrderAcknRqd)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`isRelevantForJITDelivSchedule(String isRelevantForJITDelivSchedule)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`itemLastTransmissionDate(LocalDateTime itemLastTransmissionDate)` Constraints: Not nullable, Precision: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`manufacturerMaterial(String manufacturerMaterial)` Constraints: Not nullable, Maximum length: 40
`SchAgrmtItem.SchAgrmtItemBuilder`	`material(String material)` Constraints: Not nullable, Maximum length: 40
`SchAgrmtItem.SchAgrmtItemBuilder`	`materialGroup(String materialGroup)` Constraints: Not nullable, Maximum length: 9
`SchAgrmtItem.SchAgrmtItemBuilder`	`materialType(String materialType)` Constraints: Not nullable, Maximum length: 4
`SchAgrmtItem.SchAgrmtItemBuilder`	`minRemainingShelfLife(BigDecimal minRemainingShelfLife)` Constraints: Not nullable, Precision: 4, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`multipleAcctAssgmtDistribution(String multipleAcctAssgmtDistribution)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`netPriceAmount(BigDecimal netPriceAmount)` Constraints: Not nullable, Precision: 12, Scale: 3
`SchAgrmtItem.SchAgrmtItemBuilder`	`netPriceQuantity(BigDecimal netPriceQuantity)` Constraints: Not nullable, Precision: 5, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`nextFcstDelivSchedSendingDate(LocalDateTime nextFcstDelivSchedSendingDate)` Constraints: Not nullable, Precision: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`nextJITDelivSchedSendingDate(LocalDateTime nextJITDelivSchedSendingDate)` Constraints: Not nullable, Precision: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`noDaysReminder1(BigDecimal noDaysReminder1)` Constraints: Not nullable, Precision: 3, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`noDaysReminder2(BigDecimal noDaysReminder2)` Constraints: Not nullable, Precision: 3, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`noDaysReminder3(BigDecimal noDaysReminder3)` Constraints: Not nullable, Precision: 3, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`orderPriceUnit(String orderPriceUnit)` Constraints: Not nullable, Maximum length: 3
`SchAgrmtItem.SchAgrmtItemBuilder`	`orderPriceUnitToOrderUnitNmrtr(BigDecimal orderPriceUnitToOrderUnitNmrtr)` Constraints: Not nullable, Precision: 5, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`orderQuantityUnit(String orderQuantityUnit)` Constraints: Not nullable, Maximum length: 3
`SchAgrmtItem.SchAgrmtItemBuilder`	`ordPriceUnitToOrderUnitDnmntr(BigDecimal ordPriceUnitToOrderUnitDnmntr)` Constraints: Not nullable, Precision: 5, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`overdelivTolrtdLmtRatioInPct(BigDecimal overdelivTolrtdLmtRatioInPct)` Constraints: Not nullable, Precision: 3, Scale: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`partialInvoiceDistribution(String partialInvoiceDistribution)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`plant(String plant)` Constraints: Not nullable, Maximum length: 4
`SchAgrmtItem.SchAgrmtItemBuilder`	`priceIsToBePrinted(Boolean priceIsToBePrinted)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`productType(String productType)` Constraints: Not nullable, Maximum length: 2
`SchAgrmtItem.SchAgrmtItemBuilder`	`purchaseRequisition(String purchaseRequisition)` Constraints: Not nullable, Maximum length: 10
`SchAgrmtItem.SchAgrmtItemBuilder`	`purchaseRequisitionItem(String purchaseRequisitionItem)` Constraints: Not nullable, Maximum length: 5
`SchAgrmtItem.SchAgrmtItemBuilder`	`purchasingDocumentCategory(String purchasingDocumentCategory)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`purchasingDocumentDeletionCode(String purchasingDocumentDeletionCode)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`purchasingDocumentItemCategory(String purchasingDocumentItemCategory)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`purchasingDocumentItemText(String purchasingDocumentItemText)` Constraints: Not nullable, Maximum length: 40
`SchAgrmtItem.SchAgrmtItemBuilder`	`purchasingInfoRecord(String purchasingInfoRecord)` Constraints: Not nullable, Maximum length: 10
`SchAgrmtItem.SchAgrmtItemBuilder`	`purgDocEstimatedPrice(Boolean purgDocEstimatedPrice)` Constraints: none
`SchAgrmtItem.SchAgrmtItemBuilder`	`purgDocOrderAcknNumber(String purgDocOrderAcknNumber)` Constraints: Not nullable, Maximum length: 20
`SchAgrmtItem.SchAgrmtItemBuilder`	`qualityCertificateType(String qualityCertificateType)` Constraints: Not nullable, Maximum length: 4
`SchAgrmtItem.SchAgrmtItemBuilder`	`qualityMgmtCtrlKey(String qualityMgmtCtrlKey)` Constraints: Not nullable, Maximum length: 8
`SchAgrmtItem.SchAgrmtItemBuilder`	`referenceDeliveryAddressID(String referenceDeliveryAddressID)` Constraints: Not nullable, Maximum length: 10
`SchAgrmtItem.SchAgrmtItemBuilder`	`requirementTracking(String requirementTracking)` Constraints: Not nullable, Maximum length: 10
`SchAgrmtItem.SchAgrmtItemBuilder`	`schAgrmtAcCnt(SchAgrmtAcCnt... value)` Navigation property to_SchAgrmtAcCnt for SchAgrmtItem to multiple SchAgrmtAcCnt.
`SchAgrmtItem.SchAgrmtItemBuilder`	`schAgrmtSchLine(SchAgrmtSchLine... value)` Navigation property to_SchAgrmtSchLine for SchAgrmtItem to multiple SchAgrmtSchLine.
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedAgrmtAgreedCumQty(BigDecimal schedAgrmtAgreedCumQty)` Constraints: Not nullable, Precision: 13, Scale: 3
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedAgrmtCumQtyReconcileDate(LocalDateTime schedAgrmtCumQtyReconcileDate)` Constraints: Not nullable, Precision: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedAgrmtCumulativeQtyControl(String schedAgrmtCumulativeQtyControl)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedgAgrmtDeliveryAddress(SchedgAgrmtDeliveryAddress value)` Navigation property to_SchedgAgrmtDeliveryAddress for SchAgrmtItem to single SchedgAgrmtDeliveryAddress.
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedgAgrmtItmNotes(SchedgAgrmtItmNotes... value)` Navigation property to_SchedgAgrmtItmNotes for SchAgrmtItem to multiple SchedgAgrmtItmNotes.
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedgAgrmtRelCreationProfile(String schedgAgrmtRelCreationProfile)` Constraints: Not nullable, Maximum length: 4
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedLineSemiFirmOrderInDays(BigDecimal schedLineSemiFirmOrderInDays)` Constraints: Not nullable, Precision: 3, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`scheduleLineFirmOrderInDays(BigDecimal scheduleLineFirmOrderInDays)` Constraints: Not nullable, Precision: 3, Scale: 0
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedulingAgreement(String schedulingAgreement)` (Key Field) Constraints: Not nullable, Maximum length: 10
`SchAgrmtItem.SchAgrmtItemBuilder`	`schedulingAgreementItem(String schedulingAgreementItem)` (Key Field) Constraints: Not nullable, Maximum length: 5
`SchAgrmtItem.SchAgrmtItemBuilder`	`shippingInstruction(String shippingInstruction)` Constraints: Not nullable, Maximum length: 2
`SchAgrmtItem.SchAgrmtItemBuilder`	`stockType(String stockType)` Constraints: Not nullable, Maximum length: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`storageLocation(String storageLocation)` Constraints: Not nullable, Maximum length: 4
`SchAgrmtItem.SchAgrmtItemBuilder`	`supplierMaterialNumber(String supplierMaterialNumber)` Constraints: Not nullable, Maximum length: 35
`SchAgrmtItem.SchAgrmtItemBuilder`	`targetQuantity(BigDecimal targetQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3
`SchAgrmtItem.SchAgrmtItemBuilder`	`taxCode(String taxCode)` Constraints: Not nullable, Maximum length: 2
`SchAgrmtItem.SchAgrmtItemBuilder`	`taxCountry(String taxCountry)` Constraints: Not nullable, Maximum length: 3
`SchAgrmtItem.SchAgrmtItemBuilder`	`taxDeterminationDate(LocalDateTime taxDeterminationDate)` Constraints: Not nullable, Precision: 0
`String`	`toString()`
`SchAgrmtItem.SchAgrmtItemBuilder`	`underdelivTolrtdLmtRatioInPct(BigDecimal underdelivTolrtdLmtRatioInPct)` Constraints: Not nullable, Precision: 3, Scale: 1
`SchAgrmtItem.SchAgrmtItemBuilder`	`unlimitedOverdeliveryIsAllowed(Boolean unlimitedOverdeliveryIsAllowed)` Constraints: none

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

- Method Detail
  - schAgrmtAcCnt
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schAgrmtAcCnt(SchAgrmtAcCnt... value)
```
    Navigation property to_SchAgrmtAcCnt for SchAgrmtItem to multiple SchAgrmtAcCnt.
    
    Parameters:
    
    value - The SchAgrmtAcCnts to build this SchAgrmtItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - schAgrmtSchLine
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schAgrmtSchLine(SchAgrmtSchLine... value)
```
    Navigation property to_SchAgrmtSchLine for SchAgrmtItem to multiple SchAgrmtSchLine.
    
    Parameters:
    
    value - The SchAgrmtSchLines to build this SchAgrmtItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - schedgAgrmtDeliveryAddress
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedgAgrmtDeliveryAddress(SchedgAgrmtDeliveryAddress value)
```
    Navigation property to_SchedgAgrmtDeliveryAddress for SchAgrmtItem to single SchedgAgrmtDeliveryAddress.
    
    Parameters:
    
    value - The SchedgAgrmtDeliveryAddress to build this SchAgrmtItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - schedgAgrmtItmNotes
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedgAgrmtItmNotes(SchedgAgrmtItmNotes... value)
```
    Navigation property to_SchedgAgrmtItmNotes for SchAgrmtItem to multiple SchedgAgrmtItmNotes.
    
    Parameters:
    
    value - The SchedgAgrmtItmNotess to build this SchAgrmtItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - schedulingAgreement
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedulingAgreement(@Nullable
                                                                     String schedulingAgreement)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SchedulingAgreement
    
    Returns:
    
    this.
  - schedulingAgreementItem
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedulingAgreementItem(@Nullable
                                                                         String schedulingAgreementItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: SchedulingAgreementItem
    
    Returns:
    
    this.
  - companyCode
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder companyCode(@Nullable
                                                             String companyCode)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CompanyCode
    
    Returns:
    
    this.
  - purchasingDocumentCategory
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purchasingDocumentCategory(@Nullable
                                                                            String purchasingDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PurchasingDocumentCategory
    
    Returns:
    
    this.
  - purchasingDocumentItemCategory
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purchasingDocumentItemCategory(@Nullable
                                                                                String purchasingDocumentItemCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PurchasingDocumentItemCategory
    
    The item category controls whether the following entries and procedures are necessary or permitted for the item:material numberadditional account assignmentinventory management in the SAP Systemgoods receiptinvoice receiptIn the standard system an item in the "normal" category requires goods and invoice receipts. On the other hand for items in the "consignment" category, (that is order item for consignment material) invoice receipts are not allowed.
    
    Returns:
    
    this.
  - purchasingDocumentItemText
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purchasingDocumentItemText(@Nullable
                                                                            String purchasingDocumentItemText)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: PurchasingDocumentItemText
    
    Returns:
    
    this.
  - material
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder material(@Nullable
                                                          String material)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
    
    Returns:
    
    this.
  - manufacturerMaterial
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder manufacturerMaterial(@Nullable
                                                                      String manufacturerMaterial)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: ManufacturerMaterial
    
    This field is also used for MPN materials.
    
    Returns:
    
    this.
  - supplierMaterialNumber
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder supplierMaterialNumber(@Nullable
                                                                        String supplierMaterialNumber)
```
    Constraints: Not nullable, Maximum length: 35
    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.
    
    Returns:
    
    this.
  - materialGroup
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder materialGroup(@Nullable
                                                               String materialGroup)
```
    Constraints: Not nullable, Maximum length: 9
    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
    them to a particular material group.
    
    Returns:
    
    this.
  - plant
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder plant(@Nullable
                                                       String plant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Plant
    
    You use the plant key to determine, for instance, which plant is to receive ordered goods.
    code).
    
    Returns:
    
    this.
  - referenceDeliveryAddressID
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder referenceDeliveryAddressID(@Nullable
                                                                            String referenceDeliveryAddressID)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceDeliveryAddressID
    
    Returns:
    
    this.
  - incotermsClassification
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder incotermsClassification(@Nullable
                                                                         String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    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.
    Commerce (ICC).
    
    Returns:
    
    this.
  - incotermsTransferLocation
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder incotermsTransferLocation(@Nullable
                                                                           String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    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").
    
    Returns:
    
    this.
  - orderQuantityUnit
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder orderQuantityUnit(@Nullable
                                                                   String orderQuantityUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: OrderQuantityUnit
    
    Returns:
    
    this.
  - targetQuantity
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder targetQuantity(@Nullable
                                                                BigDecimal targetQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: TargetQuantity
    agreement (contract or scheduling agreement).
    
    Returns:
    
    this.
  - purchaseRequisition
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purchaseRequisition(@Nullable
                                                                     String purchaseRequisition)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: PurchaseRequisition
    
    Returns:
    
    this.
  - purchaseRequisitionItem
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purchaseRequisitionItem(@Nullable
                                                                         String purchaseRequisitionItem)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: PurchaseRequisitionItem
    
    Returns:
    
    this.
  - schedAgrmtAgreedCumQty
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedAgrmtAgreedCumQty(@Nullable
                                                                        BigDecimal schedAgrmtAgreedCumQty)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    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
    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.
    
    Returns:
    
    this.
  - schedAgrmtCumQtyReconcileDate
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedAgrmtCumQtyReconcileDate(@Nullable
                                                                               LocalDateTime schedAgrmtCumQtyReconcileDate)
```
    Constraints: Not nullable, Precision: 0
    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.
    
    Returns:
    
    this.
  - itemLastTransmissionDate
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder itemLastTransmissionDate(@Nullable
                                                                          LocalDateTime itemLastTransmissionDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ItemLastTransmissionDate
    
    Returns:
    
    this.
  - noDaysReminder1
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder noDaysReminder1(@Nullable
                                                                 BigDecimal noDaysReminder1)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    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 ( " " " ).
    termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.
    
    Returns:
    
    this.
  - noDaysReminder2
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder noDaysReminder2(@Nullable
                                                                 BigDecimal noDaysReminder2)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    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 ( " " " ).
    termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.
    
    Returns:
    
    this.
  - noDaysReminder3
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder noDaysReminder3(@Nullable
                                                                 BigDecimal noDaysReminder3)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    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 ( " " " ).
    termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.
    
    Returns:
    
    this.
  - purgDocOrderAcknNumber
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purgDocOrderAcknNumber(@Nullable
                                                                        String purgDocOrderAcknNumber)
```
    Constraints: Not nullable, Maximum length: 20
    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.
    
    Returns:
    
    this.
  - requirementTracking
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder requirementTracking(@Nullable
                                                                     String requirementTracking)
```
    Constraints: Not nullable, Maximum length: 10
    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.
    can relate to a requisition note (or requirement notice/slip) that was not generated in the system.
    
    Returns:
    
    this.
  - isOrderAcknRqd
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder isOrderAcknRqd(@Nullable
                                                                Boolean isOrderAcknRqd)
```
    Constraints: none
    Original property name from the Odata EDM: IsOrderAcknRqd
    acknowledged by the supplier.
    
    Returns:
    
    this.
  - purgDocEstimatedPrice
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purgDocEstimatedPrice(@Nullable
                                                                       Boolean purgDocEstimatedPrice)
```
    Constraints: none
    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.
    
    Returns:
    
    this.
  - priceIsToBePrinted
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder priceIsToBePrinted(@Nullable
                                                                    Boolean priceIsToBePrinted)
```
    Constraints: none
    Original property name from the Odata EDM: PriceIsToBePrinted
    
    Returns:
    
    this.
  - accountAssignmentCategory
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder accountAssignmentCategory(@Nullable
                                                                           String accountAssignmentCategory)
```
    Constraints: Not nullable, Maximum length: 1
    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.
    center).
    
    Returns:
    
    this.
  - multipleAcctAssgmtDistribution
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder multipleAcctAssgmtDistribution(@Nullable
                                                                                String multipleAcctAssgmtDistribution)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: MultipleAcctAssgmtDistribution
    
    Returns:
    
    this.
  - partialInvoiceDistribution
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder partialInvoiceDistribution(@Nullable
                                                                            String partialInvoiceDistribution)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PartialInvoiceDistribution
    
    Returns:
    
    this.
  - netPriceAmount
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder netPriceAmount(@Nullable
                                                                BigDecimal netPriceAmount)
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property name from the Odata EDM: NetPriceAmount
    
    Returns:
    
    this.
  - netPriceQuantity
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder netPriceQuantity(@Nullable
                                                                  BigDecimal netPriceQuantity)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property name from the Odata EDM: NetPriceQuantity
    
    Returns:
    
    this.
  - orderPriceUnit
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder orderPriceUnit(@Nullable
                                                                String orderPriceUnit)
```
    Constraints: Not nullable, Maximum length: 3
    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.
    
    Returns:
    
    this.
  - productType
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder productType(@Nullable
                                                             String productType)
```
    Constraints: Not nullable, Maximum length: 2
    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.You also use the product type group Service to control that a service entry sheet can be created as a follow-on document of a purchase order.The selection field Product Type Group is available for the following item categories:StandardThird-partyLimitIn the product master data, the assigned material type defines the product type group, that is, whether the product is a material or a service. This means that whenever you select, for example, Service as the product type group in your purchasing document item, you can only enter the number of a product with the same product type group in the Material field of the item.And the other way round: if you enter a product number in the Material field, for example, in a purchase order item, the product type group is derived automatically from the material type assigned to the product master. In this case, you cannot manually maintain the product type group in the purchase order item.If you don´t enter a product number, but create a free-text item or a limit item, you have to maintain the product type group manually.
    
    Returns:
    
    this.
  - materialType
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder materialType(@Nullable
                                                              String materialType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: MaterialType
    
    The material type defines certain attributes of the material and has important control functions.
    trading goods.
    
    Returns:
    
    this.
  - storageLocation
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder storageLocation(@Nullable
                                                                 String storageLocation)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: StorageLocation
    
    Returns:
    
    this.
  - documentCurrency
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder documentCurrency(@Nullable
                                                                  String documentCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: DocumentCurrency
    
    Returns:
    
    this.
  - isInfoRecordUpdated
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder isInfoRecordUpdated(@Nullable
                                                                     String isInfoRecordUpdated)
```
    Constraints: Not nullable, Maximum length: 1
    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.
    
    Returns:
    
    this.
  - purchasingInfoRecord
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purchasingInfoRecord(@Nullable
                                                                      String purchasingInfoRecord)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: PurchasingInfoRecord
    
    Returns:
    
    this.
  - ordPriceUnitToOrderUnitDnmntr
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder ordPriceUnitToOrderUnitDnmntr(@Nullable
                                                                               BigDecimal ordPriceUnitToOrderUnitDnmntr)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    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
    
    Returns:
    
    this.
  - orderPriceUnitToOrderUnitNmrtr
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder orderPriceUnitToOrderUnitNmrtr(@Nullable
                                                                                BigDecimal orderPriceUnitToOrderUnitNmrtr)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    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
    
    Returns:
    
    this.
  - purchasingDocumentDeletionCode
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder purchasingDocumentDeletionCode(@Nullable
                                                                                String purchasingDocumentDeletionCode)
```
    Constraints: Not nullable, Maximum length: 1
    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.
    
    Returns:
    
    this.
  - underdelivTolrtdLmtRatioInPct
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder underdelivTolrtdLmtRatioInPct(@Nullable
                                                                               BigDecimal underdelivTolrtdLmtRatioInPct)
```
    Constraints: Not nullable, Precision: 3, Scale: 1
    Original property name from the Odata EDM: UnderdelivTolrtdLmtRatioInPct
    
    Returns:
    
    this.
  - overdelivTolrtdLmtRatioInPct
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder overdelivTolrtdLmtRatioInPct(@Nullable
                                                                              BigDecimal overdelivTolrtdLmtRatioInPct)
```
    Constraints: Not nullable, Precision: 3, Scale: 1
    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.
    
    Returns:
    
    this.
  - unlimitedOverdeliveryIsAllowed
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder unlimitedOverdeliveryIsAllowed(@Nullable
                                                                                Boolean unlimitedOverdeliveryIsAllowed)
```
    Constraints: none
    Original property name from the Odata EDM: UnlimitedOverdeliveryIsAllowed
    
    Returns:
    
    this.
  - stockType
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder stockType(@Nullable
                                                           String stockType)
```
    Constraints: Not nullable, Maximum length: 1
    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.
    goods issue).
    
    Returns:
    
    this.
  - taxCode
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder taxCode(@Nullable
                                                         String taxCode)
```
    Constraints: Not nullable, Maximum length: 2
    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.
    the tax authorities.
    
    Returns:
    
    this.
  - taxCountry
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder taxCountry(@Nullable
                                                            String taxCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: TaxCountry
    
    When the Registration for Indirect Taxation Abroad (RITA) is enabled,you can designate a tax country for the calculation and reporting oftaxes. RITA allows you to do this without having a separate companycode in those countries. When RITA is enabled, tax is calculatedbased on the tax country rather than the company code country.Please note that the tax country must be supplied in transactionssubject to tax calculation.
    
    Returns:
    
    this.
  - taxDeterminationDate
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder taxDeterminationDate(@Nullable
                                                                      LocalDateTime taxDeterminationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: TaxDeterminationDate
    
    The system determines the date for calculating time-dependent tax (depending on the Customizing settings in the company code) either from the posting date or from the document date.If you want to use a date which is neither the posting date nor the document date for calculating tax on sales/purchases, you can enter the alternative date here.Enter the alternative date.
    
    Returns:
    
    this.
  - shippingInstruction
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder shippingInstruction(@Nullable
                                                                     String shippingInstruction)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingInstruction
    
    Enter the key for the relevant shipping instructions.
    
    Returns:
    
    this.
  - isInfoAtRegistration
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder isInfoAtRegistration(@Nullable
                                                                      String isInfoAtRegistration)
```
    Constraints: Not nullable, Maximum length: 1
    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).
    notifies when inbound deliveries for this item are registered in the goods receipt office.
    
    Returns:
    
    this.
  - goodsReceiptIsExpected
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder goodsReceiptIsExpected(@Nullable
                                                                        Boolean goodsReceiptIsExpected)
```
    Constraints: none
    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.
    
    Returns:
    
    this.
  - goodsReceiptIsNonValuated
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder goodsReceiptIsNonValuated(@Nullable
                                                                           Boolean goodsReceiptIsNonValuated)
```
    Constraints: none
    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.
    
    Returns:
    
    this.
  - invoiceIsExpected
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder invoiceIsExpected(@Nullable
                                                                   Boolean invoiceIsExpected)
```
    Constraints: none
    Original property name from the Odata EDM: InvoiceIsExpected
    
    If the indicator is not set, the goods are to be delivered free of charge.
    
    Returns:
    
    this.
  - invoiceIsGoodsReceiptBased
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder invoiceIsGoodsReceiptBased(@Nullable
                                                                            Boolean invoiceIsGoodsReceiptBased)
```
    Constraints: none
    Original property name from the Odata EDM: InvoiceIsGoodsReceiptBased
    purchase order item or invoice item.
    
    Returns:
    
    this.
  - evaldRcptSettlmtIsAllowed
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder evaldRcptSettlmtIsAllowed(@Nullable
                                                                           Boolean evaldRcptSettlmtIsAllowed)
```
    Constraints: none
    Original property name from the Odata EDM: EvaldRcptSettlmtIsAllowed
    
    You set this indicator if you do not expect the supplier to send you an invoice. Instead, the invoice is to be generated by the system based on the data available in the purchase order and the goods receipt document.You can use the indicator Evaluated Receipt Settlement (ERS) for the procurement of materials and services.(In the case of services performed, you create a service entry sheet. Once it has been approved, the system creates a goods receipt in the background.)If you want to use the Evaluated Receipt Settlement (ERS) functionality, you have to set the ERS indicator both in the supplier master data and in the purchase order item. Please note: You have the option to select or deselect the indicator in the purchase order only if it is set in the supplier master data.Where to set the indicator:Supplier master data:Use the Maintain Business Partner app andgo to your supplier´s purchasing data that is specific for the respective purchasing organization.Purchase order item:In the purchase order item, you can use the indicator in all available item categories, except in limit items for materials (product type group 1 - as no goods receipt is expected for these items).Use the Manage Purchase Orders app or the Create Purchase Order - Advanced app andalso set the indicators Goods Receipt and Goods-Receipt-Based Invoice Verification on item level.
    materials or services has been posted.
    
    Returns:
    
    this.
  - minRemainingShelfLife
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder minRemainingShelfLife(@Nullable
                                                                       BigDecimal minRemainingShelfLife)
```
    Constraints: Not nullable, Precision: 4, Scale: 0
    Original property name from the Odata EDM: MinRemainingShelfLife
    
    The period (day, week, month, year) depends on the entry in the Period indicator field.
    accepted by the system.
    
    Returns:
    
    this.
  - qualityMgmtCtrlKey
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder qualityMgmtCtrlKey(@Nullable
                                                                    String qualityMgmtCtrlKey)
```
    Constraints: Not nullable, Maximum length: 8
    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.
    
    Returns:
    
    this.
  - qualityCertificateType
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder qualityCertificateType(@Nullable
                                                                        String qualityCertificateType)
```
    Constraints: Not nullable, Maximum length: 4
    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.For certificate creation, you can use the certificate type to control the statuses in the certificate profile. The certificate type is specified in the certificate profile.The entry of a certificate type in the Quality Management view of the material only takes effect if you also set the indicator for the activation of QM in procurement.
    
    Returns:
    
    this.
  - schedAgrmtCumulativeQtyControl
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedAgrmtCumulativeQtyControl(@Nullable
                                                                                String schedAgrmtCumulativeQtyControl)
```
    Constraints: Not nullable, Maximum length: 1
    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
    
    Returns:
    
    this.
  - cumulativeQuantityIsNotSent
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder cumulativeQuantityIsNotSent(@Nullable
                                                                             Boolean cumulativeQuantityIsNotSent)
```
    Constraints: none
    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.
    used.
    
    Returns:
    
    this.
  - schedgAgrmtRelCreationProfile
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedgAgrmtRelCreationProfile(@Nullable
                                                                               String schedgAgrmtRelCreationProfile)
```
    Constraints: Not nullable, Maximum length: 4
    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.
    
    Returns:
    
    this.
  - isRelevantForJITDelivSchedule
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder isRelevantForJITDelivSchedule(@Nullable
                                                                               String isRelevantForJITDelivSchedule)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsRelevantForJITDelivSchedule
    for a material specified in a purchase scheduling agreement.
    
    Returns:
    
    this.
  - nextFcstDelivSchedSendingDate
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder nextFcstDelivSchedSendingDate(@Nullable
                                                                               LocalDateTime nextFcstDelivSchedSendingDate)
```
    Constraints: Not nullable, Precision: 0
    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.
    
    Returns:
    
    this.
  - nextJITDelivSchedSendingDate
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder nextJITDelivSchedSendingDate(@Nullable
                                                                              LocalDateTime nextJITDelivSchedSendingDate)
```
    Constraints: Not nullable, Precision: 0
    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.
    
    Returns:
    
    this.
  - scheduleLineFirmOrderInDays
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder scheduleLineFirmOrderInDays(@Nullable
                                                                             BigDecimal scheduleLineFirmOrderInDays)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    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).
    release are classified as firm or semi-firm.
    
    Returns:
    
    this.
  - schedLineSemiFirmOrderInDays
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder schedLineSemiFirmOrderInDays(@Nullable
                                                                              BigDecimal schedLineSemiFirmOrderInDays)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    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).
    release are classified as firm or semi-firm.
    
    Returns:
    
    this.
  - firmTradeOffZoneBindMRP
```
@Nonnull
public SchAgrmtItem.SchAgrmtItemBuilder firmTradeOffZoneBindMRP(@Nullable
                                                                         String firmTradeOffZoneBindMRP)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: FirmTradeOffZoneBindMRP
    during the planning run.
    
    Returns:
    
    this.
  - build
```
@Nonnull
public SchAgrmtItem build()
```
  - toString
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class Object

Class SchAgrmtItem.SchAgrmtItemBuilder

Method Summary

Methods inherited from class java.lang.Object

Method Detail

schAgrmtAcCnt

schAgrmtSchLine

schedgAgrmtDeliveryAddress

schedgAgrmtItmNotes

schedulingAgreement

schedulingAgreementItem

companyCode

purchasingDocumentCategory

purchasingDocumentItemCategory

purchasingDocumentItemText

material

manufacturerMaterial

supplierMaterialNumber

materialGroup

plant

referenceDeliveryAddressID

incotermsClassification

incotermsTransferLocation

orderQuantityUnit

targetQuantity

purchaseRequisition

purchaseRequisitionItem

schedAgrmtAgreedCumQty

schedAgrmtCumQtyReconcileDate

itemLastTransmissionDate

noDaysReminder1

noDaysReminder2

noDaysReminder3

purgDocOrderAcknNumber

requirementTracking

isOrderAcknRqd

purgDocEstimatedPrice

priceIsToBePrinted

accountAssignmentCategory

multipleAcctAssgmtDistribution

partialInvoiceDistribution

netPriceAmount

netPriceQuantity

orderPriceUnit

productType

materialType

storageLocation

documentCurrency

isInfoRecordUpdated

purchasingInfoRecord

ordPriceUnitToOrderUnitDnmntr

orderPriceUnitToOrderUnitNmrtr

purchasingDocumentDeletionCode

underdelivTolrtdLmtRatioInPct

overdelivTolrtdLmtRatioInPct

unlimitedOverdeliveryIsAllowed

stockType

taxCode

taxCountry

taxDeterminationDate

shippingInstruction

isInfoAtRegistration

goodsReceiptIsExpected

goodsReceiptIsNonValuated

invoiceIsExpected

invoiceIsGoodsReceiptBased

evaldRcptSettlmtIsAllowed

minRemainingShelfLife

qualityMgmtCtrlKey

qualityCertificateType

schedAgrmtCumulativeQtyControl

cumulativeQuantityIsNotSent

schedgAgrmtRelCreationProfile

isRelevantForJITDelivSchedule

nextFcstDelivSchedSendingDate

nextJITDelivSchedSendingDate

scheduleLineFirmOrderInDays

schedLineSemiFirmOrderInDays

firmTradeOffZoneBindMRP

build

toString