public static final class PurchaseContractItem.PurchaseContractItemBuilder extends Object
@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder purchaseContract(PurchaseContract value)
value - The PurchaseContract to build this PurchaseContractItem with.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder purchaseContract(String value)
Original property name from the Odata EDM: PurchaseContract
value - The purchaseContract to build this PurchaseContractItem with.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder purContrItemCondition(PurContrItemCondition... value)
value - The PurContrItemConditions to build this PurchaseContractItem with.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder purCtrAccount(PurCtrAccount... value)
value - The PurCtrAccounts to build this PurchaseContractItem with.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder purCtrAddress(PurCtrAddress... value)
value - The PurCtrAddresss to build this PurchaseContractItem with.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder purchaseContractItem(@Nullable String purchaseContractItem)
Original property name from the Odata EDM: PurchaseContractItem
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder purchaseContractItemText(@Nullable String purchaseContractItemText)
Original property name from the Odata EDM: PurchaseContractItemText
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder plant(@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.
code).this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder orderQuantityUnit(@Nullable String orderQuantityUnit)
Original property name from the Odata EDM: OrderQuantityUnit
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder targetQuantity(@Nullable BigDecimal targetQuantity)
Original property name from the Odata EDM: TargetQuantity
agreement (contract or scheduling agreement).this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder orderPriceUnitToOrderUnitNmrtr(@Nullable BigDecimal orderPriceUnitToOrderUnitNmrtr)
Original property name from the Odata EDM: OrderPriceUnitToOrderUnitNmrtr
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder contractNetPriceAmount(@Nullable BigDecimal contractNetPriceAmount)
Original property name from the Odata EDM: ContractNetPriceAmount
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder documentCurrency(@Nullable String documentCurrency)
Original property name from the Odata EDM: DocumentCurrency
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder netPriceQuantity(@Nullable BigDecimal netPriceQuantity)
Original property name from the Odata EDM: NetPriceQuantity
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder taxCountry(@Nullable String taxCountry)
Original property name from the Odata EDM: TaxCountry
When the Registration for Indirect Taxation Abroad (RITA) is enabled,you can designate a tax country/region 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/region rather than the company code country/region.Please note that the tax country/region must be supplied in transactionssubject to tax calculation.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder taxDeterminationDate(@Nullable LocalDateTime taxDeterminationDate)
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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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).this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder isInfoRecordUpdated(@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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder priceIsToBePrinted(@Nullable Boolean priceIsToBePrinted)
Original property name from the Odata EDM: PriceIsToBePrinted
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder unlimitedOverdeliveryIsAllowed(@Nullable Boolean unlimitedOverdeliveryIsAllowed)
Original property name from the Odata EDM: UnlimitedOverdeliveryIsAllowed
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder underdelivTolrtdLmtRatioInPct(@Nullable BigDecimal underdelivTolrtdLmtRatioInPct)
Original property name from the Odata EDM: UnderdelivTolrtdLmtRatioInPct
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder accountAssignmentCategory(@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.
center).this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder multipleAcctAssgmtDistribution(@Nullable String multipleAcctAssgmtDistribution)
Original property name from the Odata EDM: MultipleAcctAssgmtDistribution
You can distribute the purchase order quantity or the net value of a document item, or specify a percentage for each account assignment. The system calculates complementary values. For example, if you choose quantity-based distribution and enter a number of pieces for each account assignment, the system calculates the percentage and net value.If you choose quantity-based or percentage distribution, the quantities that are distributed to an account assignment are rounded to three decimal places, to ensure that the 100% of the item quantity is always distributed.If you choose percentage distribution and change the requested quantity on the item overview screen, the system adjusts the quantities in the associated account assignment items.If you choose amount-based distribution, the system distributes the item quantity to the individual account assignments exactly according to the defined distribution, including very small value amounts. The quantities of individual account assignment items are displayed as rounded, but the system uses the exact quantities.
assignment items.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder invoiceIsGoodsReceiptBased(@Nullable Boolean invoiceIsGoodsReceiptBased)
Original property name from the Odata EDM: InvoiceIsGoodsReceiptBased
purchase order item or invoice item.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder isOrderAcknRqd(@Nullable Boolean isOrderAcknRqd)
Original property name from the Odata EDM: IsOrderAcknRqd
acknowledged by the supplier.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder shippingInstruction(@Nullable String shippingInstruction)
Original property name from the Odata EDM: ShippingInstruction
Enter the key for the relevant shipping instructions.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder manualDeliveryAddressID(@Nullable String manualDeliveryAddressID)
Original property name from the Odata EDM: ManualDeliveryAddressID
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder volumeUnit(@Nullable String volumeUnit)
Original property name from the Odata EDM: VolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder subcontractor(@Nullable String subcontractor)
Original property name from the Odata EDM: Subcontractor
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder evaldRcptSettlmtIsAllowed(@Nullable Boolean evaldRcptSettlmtIsAllowed)
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.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder servicePerformer(@Nullable String servicePerformer)
Original property name from the Odata EDM: ServicePerformer
relation (staffed from external supplier).
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder 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.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.
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder materialType(@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.
trading goods.this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder formattedPurchaseContractItem(@Nullable String formattedPurchaseContractItem)
Original property name from the Odata EDM: FormattedPurchaseContractItem
this.@Nonnull public PurchaseContractItem.PurchaseContractItemBuilder purchasingParentItem(@Nullable String purchasingParentItem)
Original property name from the Odata EDM: PurchasingParentItem
Items can be arranged hierarchically. If a sub-item is assigned to an item, the former becomes a higher-level item.Enter the number of a higher-level item.
this.@Nonnull public PurchaseContractItem build()
Copyright © 2021 SAP SE. All rights reserved.