public static final class SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder extends Object
@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder supplierInvoiceItmAcctAssgmt(SuplrInvcItemAcctAssgmt... value)
value
- The SuplrInvcItemAcctAssgmts to build this SuplrInvcItemPurOrdRef with.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder supplierInvoice(@Nullable String supplierInvoice)
Original property name from the Odata EDM: SupplierInvoice
The document number is unique per company code and fiscal year. When entering an accounting document, you can specify the number manually or it can be determined by the system from a pre-defined area (number range).The relevant area of the document numbers (number range) is determined in each company code per document type.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder fiscalYear(@Nullable String fiscalYear)
Original property name from the Odata EDM: FiscalYear
fiscal year can be the same as the calendar year, but does not have to be.this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder supplierInvoiceItem(@Nullable String supplierInvoiceItem)
Original property name from the Odata EDM: SupplierInvoiceItem
The system places the line selected at the top of the invoice item display.
to process.this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder purchaseOrder(@Nullable String purchaseOrder)
Original property name from the Odata EDM: PurchaseOrder
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder purchaseOrderItem(@Nullable String purchaseOrderItem)
Original property name from the Odata EDM: PurchaseOrderItem
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder referenceDocument(@Nullable String referenceDocument)
Original property name from the Odata EDM: ReferenceDocument
The document number is unique per company code and fiscal year. When you enter an accounting_document, the number can be assigned either manually by the user or by the system (from a predefined number range).The permitted document number ranges are specified in tables for various document types.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder referenceDocumentFiscalYear(@Nullable String referenceDocumentFiscalYear)
Original property name from the Odata EDM: ReferenceDocumentFiscalYear
In the simplest case, the fiscal year and the calendar year will match. Otherwise, the calendar days on which individual posting periods end must be defined. This can be done at the same time for several company codes or individually for each company code.Different variants of fiscal years can be defined in table T009. One of the variants from table 009 must be defined in table T001 for every company code that does not work with the calendar year.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder referenceDocumentItem(@Nullable String referenceDocumentItem)
Original property name from the Odata EDM: ReferenceDocumentItem
All items in an accounting document are assigned a number that allows them to be uniquely identified.The numbers are assigned consecutively when the document is created.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder isSubsequentDebitCredit(@Nullable String isSubsequentDebitCredit)
Original property name from the Odata EDM: IsSubsequentDebitCredit
Subsequent debits or credits occur if further invoices or credit memos are received in respect of goods which have already been invoiced. It is only the invoiced value that changes as a result: the invoiced quantity is not affected.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder 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 SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder taxJurisdiction(@Nullable String taxJurisdiction)
Original property name from the Odata EDM: TaxJurisdiction
authorities you must pay your taxes. It is always the city to which the goods are supplied.this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder documentCurrency(@Nullable String documentCurrency)
Original property name from the Odata EDM: DocumentCurrency
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder supplierInvoiceItemAmount(@Nullable BigDecimal supplierInvoiceItemAmount)
Original property name from the Odata EDM: SupplierInvoiceItemAmount
During document entry, enter the amount manually. In the last line item, you can specify a '*'. The system will then enter the balance of the line items entered prior to the last item as the amount for the last item.Amounts you enter may be changed automatically by the system if the following postings are made:Tax adjustmentsCash discount adjustments during net postings
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder purchaseOrderQuantityUnit(@Nullable String purchaseOrderQuantityUnit)
Original property name from the Odata EDM: PurchaseOrderQuantityUnit
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder quantityInPurchaseOrderUnit(@Nullable BigDecimal quantityInPurchaseOrderUnit)
Original property name from the Odata EDM: QuantityInPurchaseOrderUnit
The quantity entered determines which portion of the costs you wish to distribute to this account assignment item.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder purchaseOrderPriceUnit(@Nullable String purchaseOrderPriceUnit)
Original property name from the Odata EDM: PurchaseOrderPriceUnit
100 pc are ordered at a price of 10 $/kg. The order unit is "pc" (piece), and the purchase order price unit is "kg" (kilogram).
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder qtyInPurchaseOrderPriceUnit(@Nullable BigDecimal qtyInPurchaseOrderPriceUnit)
Original property name from the Odata EDM: QtyInPurchaseOrderPriceUnit
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder suplrInvcDeliveryCostCndnType(@Nullable String suplrInvcDeliveryCostCndnType)
Original property name from the Odata EDM: SuplrInvcDeliveryCostCndnType
differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder suplrInvcDeliveryCostCndnStep(@Nullable String suplrInvcDeliveryCostCndnStep)
Original property name from the Odata EDM: SuplrInvcDeliveryCostCndnStep
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder suplrInvcDeliveryCostCndnCount(@Nullable String suplrInvcDeliveryCostCndnCount)
Original property name from the Odata EDM: SuplrInvcDeliveryCostCndnCount
During automatic pricing, the system takes into account the sequence specified by the counter.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder supplierInvoiceItemText(@Nullable String supplierInvoiceItemText)
Original property name from the Odata EDM: SupplierInvoiceItemText
Line item texts can be used internally and externally. To be able to distinguish between these, you must begin texts for external use with "*". These texts can then be printed on all correspondence, dunning notices, payment advice notes, etc. The asterisk is removed when the text is printed.This function is only available in the FI component. It cannot be used in Materials Management.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder freightSupplier(@Nullable String freightSupplier)
Original property name from the Odata EDM: FreightSupplier
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder isNotCashDiscountLiable(@Nullable Boolean isNotCashDiscountLiable)
Original property name from the Odata EDM: IsNotCashDiscountLiable
If a cash discount is not granted for the entire invoiced amount, the system can determine the amount qualifying for cash discount automatically by means of the offsetting entries. To enable the system to do this, you must mark all offsetting entries as being either liable or not liable to cash discount.
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder 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 SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder 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 SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder serviceEntrySheet(@Nullable String serviceEntrySheet)
Original property name from the Odata EDM: ServiceEntrySheet
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder serviceEntrySheetItem(@Nullable String serviceEntrySheetItem)
Original property name from the Odata EDM: ServiceEntrySheetItem
this
.@Nonnull public SuplrInvcItemPurOrdRef.SuplrInvcItemPurOrdRefBuilder 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 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.
this
.@Nonnull public SuplrInvcItemPurOrdRef build()
Copyright © 2020 SAP SE. All rights reserved.