public static final class CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder extends Object
@Nonnull public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder cntrlPurConItmDistribution(CntrlPurContrItmDistribution... value)
value - The CntrlPurContrItmDistributions to build this CntrlPurchaseContractItem with.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder centralPurchaseContract(@Nullable String centralPurchaseContract)
Original property name from the Odata EDM: CentralPurchaseContract
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder centralPurchaseContractItem(@Nullable String centralPurchaseContractItem)
Original property name from the Odata EDM: CentralPurchaseContractItem
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder purchasingDocumentItemCategory(@Nullable String purchasingDocumentItemCategory)
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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder formattedPurchaseContractItem(@Nullable String formattedPurchaseContractItem)
Original property name from the Odata EDM: FormattedPurchaseContractItem
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder materialGroup(@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
them to a particular material group.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder purchasingCentralMaterial(@Nullable String purchasingCentralMaterial)
Original property name from the Odata EDM: PurchasingCentralMaterial
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder cntrlPurContractItemText(@Nullable String cntrlPurContractItemText)
Original property name from the Odata EDM: CntrlPurContractItemText
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder productType(@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
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder netPriceQuantity(@Nullable BigDecimal netPriceQuantity)
Original property name from the Odata EDM: NetPriceQuantity
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder orderPriceUnit(@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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder targetQuantity(@Nullable BigDecimal targetQuantity)
Original property name from the Odata EDM: TargetQuantity
agreement (contract or scheduling agreement).public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder cntrlPurContrItmTargetAmount(@Nullable BigDecimal cntrlPurContrItmTargetAmount)
Original property name from the Odata EDM: CntrlPurContrItmTargetAmount
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder contractNetPriceAmount(@Nullable BigDecimal contractNetPriceAmount)
Original property name from the Odata EDM: ContractNetPriceAmount
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder orderQuantityUnit(@Nullable String orderQuantityUnit)
Original property name from the Odata EDM: OrderQuantityUnit
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder purgDocReleaseOrderQuantity(@Nullable BigDecimal purgDocReleaseOrderQuantity)
Original property name from the Odata EDM: PurgDocReleaseOrderQuantity
This is the quantity that is taken as a basis in the process of price determination.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder ordPriceUnitToOrderUnitDnmntr(@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
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder orderPriceUnitToOrderUnitNmrtr(@Nullable BigDecimal orderPriceUnitToOrderUnitNmrtr)
Original property name from the Odata EDM: OrderPriceUnitToOrderUnitNmrtr
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder documentCurrency(@Nullable String documentCurrency)
Original property name from the Odata EDM: DocumentCurrency
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder noDaysReminder1(@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 ( " " " ).
termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder noDaysReminder2(@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 ( " " " ).
termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder noDaysReminder3(@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 ( " " " ).
termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder purgDocOrderAcknNumber(@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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder requirementTracking(@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.
can relate to a requisition note (or requirement notice/slip) that was not generated in the system.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder supplierMaterialNumber(@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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder isOrderAcknRqd(@Nullable Boolean isOrderAcknRqd)
Original property name from the Odata EDM: IsOrderAcknRqd
acknowledged by the supplier.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder purgDocEstimatedPrice(@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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder priceIsToBePrinted(@Nullable Boolean priceIsToBePrinted)
Original property name from the Odata EDM: PriceIsToBePrinted
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder underdelivTolrtdLmtRatioInPct(@Nullable BigDecimal underdelivTolrtdLmtRatioInPct)
Original property name from the Odata EDM: UnderdelivTolrtdLmtRatioInPct
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder overdelivTolrtdLmtRatioInPct(@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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder unlimitedOverdeliveryIsAllowed(@Nullable Boolean unlimitedOverdeliveryIsAllowed)
Original property name from the Odata EDM: UnlimitedOverdeliveryIsAllowed
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder stockType(@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.
goods issue).public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder taxCode(@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.
the tax authorities.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder shippingInstruction(@Nullable String shippingInstruction)
Original property name from the Odata EDM: ShippingInstruction
Enter the key for the relevant shipping instructions.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder goodsReceiptIsExpected(@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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder goodsReceiptIsNonValuated(@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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder invoiceIsExpected(@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.
public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder invoiceIsGoodsReceiptBased(@Nullable Boolean invoiceIsGoodsReceiptBased)
Original property name from the Odata EDM: InvoiceIsGoodsReceiptBased
purchase order item or invoice item.public CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder evaldRcptSettlmtIsAllowed(@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.
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 CntrlPurchaseContractItem.CntrlPurchaseContractItemBuilder purchasingContractDeletionCode(@Nullable String purchasingContractDeletionCode)
Original property name from the Odata EDM: PurchasingContractDeletionCode
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.
public CntrlPurchaseContractItem build()
Copyright © 2019 SAP SE. All rights reserved.