SupplierInvoice.SupplierInvoiceBuilder (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.supplierinvoiceintegration.SupplierInvoice.SupplierInvoiceBuilder

Enclosing class:

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

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`SupplierInvoice.SupplierInvoiceBuilder`	`accountingDocumentType(String accountingDocumentType)` Constraints: Not nullable, Maximum length: 2
`SupplierInvoice.SupplierInvoiceBuilder`	`assignmentReference(String assignmentReference)` Constraints: Not nullable, Maximum length: 18
`SupplierInvoice.SupplierInvoiceBuilder`	`bPBankAccountInternalID(String bPBankAccountInternalID)` Constraints: Not nullable, Maximum length: 4
`SupplierInvoice`	`build()`
`SupplierInvoice.SupplierInvoiceBuilder`	`businessArea(String businessArea)` Constraints: Not nullable, Maximum length: 4
`SupplierInvoice.SupplierInvoiceBuilder`	`businessPlace(String businessPlace)` Constraints: Not nullable, Maximum length: 4
`SupplierInvoice.SupplierInvoiceBuilder`	`businessSectionCode(String businessSectionCode)` Constraints: Not nullable, Maximum length: 4
`SupplierInvoice.SupplierInvoiceBuilder`	`cashDiscount1Days(BigDecimal cashDiscount1Days)` Constraints: Not nullable, Precision: 3, Scale: 0
`SupplierInvoice.SupplierInvoiceBuilder`	`cashDiscount1Percent(BigDecimal cashDiscount1Percent)` Constraints: Not nullable, Precision: 5, Scale: 3
`SupplierInvoice.SupplierInvoiceBuilder`	`cashDiscount2Days(BigDecimal cashDiscount2Days)` Constraints: Not nullable, Precision: 3, Scale: 0
`SupplierInvoice.SupplierInvoiceBuilder`	`cashDiscount2Percent(BigDecimal cashDiscount2Percent)` Constraints: Not nullable, Precision: 5, Scale: 3
`SupplierInvoice.SupplierInvoiceBuilder`	`companyCode(String companyCode)` Constraints: Not nullable, Maximum length: 4
`SupplierInvoice.SupplierInvoiceBuilder`	`deliveryOfGoodsReportingCntry(String deliveryOfGoodsReportingCntry)` Constraints: Not nullable, Maximum length: 3
`SupplierInvoice.SupplierInvoiceBuilder`	`directQuotedExchangeRate(BigDecimal directQuotedExchangeRate)` Constraints: Not nullable, Precision: 9, Scale: 5
`SupplierInvoice.SupplierInvoiceBuilder`	`documentCurrency(String documentCurrency)` Constraints: Not nullable, Maximum length: 5
`SupplierInvoice.SupplierInvoiceBuilder`	`documentDate(LocalDateTime documentDate)` Constraints: Not nullable, Precision: 0
`SupplierInvoice.SupplierInvoiceBuilder`	`documentHeaderText(String documentHeaderText)` Constraints: Not nullable, Maximum length: 25
`SupplierInvoice.SupplierInvoiceBuilder`	`dueCalculationBaseDate(LocalDateTime dueCalculationBaseDate)` Constraints: Not nullable, Precision: 0
`SupplierInvoice.SupplierInvoiceBuilder`	`fiscalYear(String fiscalYear)` (Key Field) Constraints: Not nullable, Maximum length: 4
`SupplierInvoice.SupplierInvoiceBuilder`	`fixedCashDiscount(String fixedCashDiscount)` Constraints: Not nullable, Maximum length: 1
`SupplierInvoice.SupplierInvoiceBuilder`	`indirectQuotedExchangeRate(BigDecimal indirectQuotedExchangeRate)` Constraints: Not nullable, Precision: 9, Scale: 5
`SupplierInvoice.SupplierInvoiceBuilder`	`invoiceGrossAmount(BigDecimal invoiceGrossAmount)` Constraints: Not nullable, Precision: 14, Scale: 3
`SupplierInvoice.SupplierInvoiceBuilder`	`invoiceReceiptDate(LocalDateTime invoiceReceiptDate)` Constraints: Not nullable, Precision: 0
`SupplierInvoice.SupplierInvoiceBuilder`	`invoiceReference(String invoiceReference)` Constraints: Not nullable, Maximum length: 10
`SupplierInvoice.SupplierInvoiceBuilder`	`invoiceReferenceFiscalYear(String invoiceReferenceFiscalYear)` Constraints: Not nullable, Maximum length: 4
`SupplierInvoice.SupplierInvoiceBuilder`	`invoicingParty(String invoicingParty)` Constraints: Not nullable, Maximum length: 10
`SupplierInvoice.SupplierInvoiceBuilder`	`isEUTriangularDeal(Boolean isEUTriangularDeal)` Constraints: none
`SupplierInvoice.SupplierInvoiceBuilder`	`manualCashDiscount(BigDecimal manualCashDiscount)` Constraints: Not nullable, Precision: 14, Scale: 3
`SupplierInvoice.SupplierInvoiceBuilder`	`netPaymentDays(BigDecimal netPaymentDays)` Constraints: Not nullable, Precision: 3, Scale: 0
`SupplierInvoice.SupplierInvoiceBuilder`	`paymentBlockingReason(String paymentBlockingReason)` Constraints: Not nullable, Maximum length: 1
`SupplierInvoice.SupplierInvoiceBuilder`	`paymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1
`SupplierInvoice.SupplierInvoiceBuilder`	`paymentMethodSupplement(String paymentMethodSupplement)` Constraints: Not nullable, Maximum length: 2
`SupplierInvoice.SupplierInvoiceBuilder`	`paymentReference(String paymentReference)` Constraints: Not nullable, Maximum length: 30
`SupplierInvoice.SupplierInvoiceBuilder`	`paymentTerms(String paymentTerms)` Constraints: Not nullable, Maximum length: 4
`SupplierInvoice.SupplierInvoiceBuilder`	`paytSlipWthRefCheckDigit(String paytSlipWthRefCheckDigit)` Constraints: Not nullable, Maximum length: 2
`SupplierInvoice.SupplierInvoiceBuilder`	`paytSlipWthRefReference(String paytSlipWthRefReference)` Constraints: Not nullable, Maximum length: 27
`SupplierInvoice.SupplierInvoiceBuilder`	`paytSlipWthRefSubscriber(String paytSlipWthRefSubscriber)` Constraints: Not nullable, Maximum length: 11
`SupplierInvoice.SupplierInvoiceBuilder`	`postingDate(LocalDateTime postingDate)` Constraints: Not nullable, Precision: 0
`SupplierInvoice.SupplierInvoiceBuilder`	`stateCentralBankPaymentReason(String stateCentralBankPaymentReason)` Constraints: Not nullable, Maximum length: 3
`SupplierInvoice.SupplierInvoiceBuilder`	`suplrInvcDebitCrdtCodeDelivery(String suplrInvcDebitCrdtCodeDelivery)` Constraints: Not nullable, Maximum length: 1
`SupplierInvoice.SupplierInvoiceBuilder`	`suplrInvcDebitCrdtCodeReturns(String suplrInvcDebitCrdtCodeReturns)` Constraints: Not nullable, Maximum length: 1
`SupplierInvoice.SupplierInvoiceBuilder`	`suplrInvcItemPurOrdRef(SuplrInvcItemPurOrdRef... value)` Navigation property to_SuplrInvcItemPurOrdRef for SupplierInvoice to multiple SuplrInvcItemPurOrdRef.
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierInvoice(String supplierInvoice)` (Key Field) Constraints: Not nullable, Maximum length: 10
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierInvoiceIDByInvcgParty(String supplierInvoiceIDByInvcgParty)` Constraints: Not nullable, Maximum length: 16
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierInvoiceIsCreditMemo(String supplierInvoiceIsCreditMemo)` Constraints: Not nullable, Maximum length: 1
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierInvoiceItemGLAcct(SupplierInvoiceItemGLAcct... value)` Navigation property to_SupplierInvoiceItemGLAcct for SupplierInvoice to multiple SupplierInvoiceItemGLAcct.
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierInvoiceStatus(String supplierInvoiceStatus)` Constraints: Not nullable, Maximum length: 1
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierInvoiceTax(SupplierInvoiceTax... value)` Navigation property to_SupplierInvoiceTax for SupplierInvoice to multiple SupplierInvoiceTax.
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierInvoiceWhldgTax(SuplrInvcHeaderWhldgTax... value)` Navigation property to_SupplierInvoiceWhldgTax for SupplierInvoice to multiple SuplrInvcHeaderWhldgTax.
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierPostingLineItemText(String supplierPostingLineItemText)` Constraints: Not nullable, Maximum length: 50
`SupplierInvoice.SupplierInvoiceBuilder`	`supplierVATRegistration(String supplierVATRegistration)` Constraints: Not nullable, Maximum length: 20
`SupplierInvoice.SupplierInvoiceBuilder`	`supplyingCountry(String supplyingCountry)` Constraints: Not nullable, Maximum length: 3
`SupplierInvoice.SupplierInvoiceBuilder`	`taxDeterminationDate(LocalDateTime taxDeterminationDate)` Constraints: Not nullable, Precision: 0
`SupplierInvoice.SupplierInvoiceBuilder`	`taxIsCalculatedAutomatically(Boolean taxIsCalculatedAutomatically)` Constraints: none
`String`	`toString()`
`SupplierInvoice.SupplierInvoiceBuilder`	`unplannedDeliveryCost(BigDecimal unplannedDeliveryCost)` Constraints: Not nullable, Precision: 14, Scale: 3
`SupplierInvoice.SupplierInvoiceBuilder`	`unplannedDeliveryCostTaxCode(String unplannedDeliveryCostTaxCode)` Constraints: Not nullable, Maximum length: 2
`SupplierInvoice.SupplierInvoiceBuilder`	`unplndDelivCostTaxJurisdiction(String unplndDelivCostTaxJurisdiction)` Constraints: Not nullable, Maximum length: 15

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

- Method Detail
  - suplrInvcItemPurOrdRef
```
@Nonnull
public SupplierInvoice.SupplierInvoiceBuilder suplrInvcItemPurOrdRef(SuplrInvcItemPurOrdRef... value)
```
    Navigation property to_SuplrInvcItemPurOrdRef for SupplierInvoice to multiple SuplrInvcItemPurOrdRef.
    
    Parameters:
    
    value - The SuplrInvcItemPurOrdRefs to build this SupplierInvoice with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - supplierInvoiceItemGLAcct
```
@Nonnull
public SupplierInvoice.SupplierInvoiceBuilder supplierInvoiceItemGLAcct(SupplierInvoiceItemGLAcct... value)
```
    Navigation property to_SupplierInvoiceItemGLAcct for SupplierInvoice to multiple SupplierInvoiceItemGLAcct.
    
    Parameters:
    
    value - The SupplierInvoiceItemGLAccts to build this SupplierInvoice with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - supplierInvoiceTax
```
@Nonnull
public SupplierInvoice.SupplierInvoiceBuilder supplierInvoiceTax(SupplierInvoiceTax... value)
```
    Navigation property to_SupplierInvoiceTax for SupplierInvoice to multiple SupplierInvoiceTax.
    
    Parameters:
    
    value - The SupplierInvoiceTaxs to build this SupplierInvoice with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - supplierInvoiceWhldgTax
```
@Nonnull
public SupplierInvoice.SupplierInvoiceBuilder supplierInvoiceWhldgTax(SuplrInvcHeaderWhldgTax... value)
```
    Navigation property to_SupplierInvoiceWhldgTax for SupplierInvoice to multiple SuplrInvcHeaderWhldgTax.
    
    Parameters:
    
    value - The SuplrInvcHeaderWhldgTaxs to build this SupplierInvoice with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - supplierInvoice
```
public SupplierInvoice.SupplierInvoiceBuilder supplierInvoice(@Nullable
                                                              String supplierInvoice)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SupplierInvoice
    
    The invoice document number is unique in every company code and fiscal year. Depending on the system configuration, the invoice document number can either be entered manually or be assigned internally by the system from a predefined number range.
  - fiscalYear
```
public SupplierInvoice.SupplierInvoiceBuilder fiscalYear(@Nullable
                                                         String fiscalYear)
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: FiscalYear
    fiscal year can be the same as the calendar year, but does not have to be.
  - companyCode
```
public SupplierInvoice.SupplierInvoiceBuilder companyCode(@Nullable
                                                          String companyCode)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CompanyCode
  - documentDate
```
public SupplierInvoice.SupplierInvoiceBuilder documentDate(@Nullable
                                                           LocalDateTime documentDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: DocumentDate
  - postingDate
```
public SupplierInvoice.SupplierInvoiceBuilder postingDate(@Nullable
                                                          LocalDateTime postingDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: PostingDate
    
    The fiscal year and the period for which an update of the accounts specified in the document or cost elements is made, are derived from the posting date.When entering documents, the system checks whether the posting date entered is allowed by means of the posting period permitted.The posting date can differ from both the entry date (day of entry into the system) and the document date (day of creation of the original document).
  - supplierInvoiceIDByInvcgParty
```
public SupplierInvoice.SupplierInvoiceBuilder supplierInvoiceIDByInvcgParty(@Nullable
                                                                            String supplierInvoiceIDByInvcgParty)
```
    Constraints: Not nullable, Maximum length: 16
    Original property name from the Odata EDM: SupplierInvoiceIDByInvcgParty
    
    The reference document number is used as a search criterion when displaying or changing documents. In correspondence, the reference document number is sometimes printed in place of the document number.Enter the number specified by the business partner. If the document was created in-house and you do not know the business partner document number, you can copy the document number into the reference number field by entering "*".
    contain a different value.
  - invoicingParty
```
public SupplierInvoice.SupplierInvoiceBuilder invoicingParty(@Nullable
                                                             String invoicingParty)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InvoicingParty
    
    This number denotes the supplier (creditor) invoicing the ordered material or services performed, to whom the amount due is payable.When the invoice is received, the number of the invoicing party is inserted in the invoice in place of the actual supplier.
  - documentCurrency
```
public SupplierInvoice.SupplierInvoiceBuilder documentCurrency(@Nullable
                                                               String documentCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: DocumentCurrency
  - invoiceGrossAmount
```
public SupplierInvoice.SupplierInvoiceBuilder invoiceGrossAmount(@Nullable
                                                                 BigDecimal invoiceGrossAmount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: InvoiceGrossAmount
    
    Enter the gross amount of the invoice.The following is an invoice with the names of the individual amounts:Quantity Material Price Amount Description10 pieces A 10 DM/piece 100.00 DM net item amount20 pieces B 6 DM/piece + 120.00 DM net item amount= 220.00 DM net sumplus 7 % tax + 7.00 DM tax amountplus 15 % tax + 18.00 DM tax amount= 245.00 DM gross invoice amntminus 3 % cash discount - 7.35 DM cash disc. amount= 237.65 DM
  - unplannedDeliveryCost
```
public SupplierInvoice.SupplierInvoiceBuilder unplannedDeliveryCost(@Nullable
                                                                    BigDecimal unplannedDeliveryCost)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: UnplannedDeliveryCost
    
    Enter the amount of the unplanned delivery costs without taxes.If you are using the conventional Invoice Verification component, the system splits up the delivery costs entered among the individual items, based on the amounts invoiced so far plus those in the invoice being entered (see example).If you are using Logistics Invoice Verification, how the unplanned delivery costs are posted depends on the Customizing settings. There are two possibilities:Unplanned delivery costs are split up as in conventional Invoice Verification (see above).Unplanned delivery costs are posted in a separate posting line to a G/L account set up for this.Purchase order100 pieces material A200 pieces material B1st invoice for the purchase order50 pieces material A at $ 10.00/piece = $ 50050 pieces material B at $ 12.00/piece = $ 6002nd invoice for the purchase order20 pieces material A at $ 10.00/piece = $ 20080 pieces material B at $ 10.00/piece = $ 800Delivery costs = $ 90The system divides up the delivery costs in the following ratio:(500 + 200) : (600 + 800) = 700 : 1400 = 1 : 2.Material A is debited for $ 30, material B for $ 60.
  - documentHeaderText
```
public SupplierInvoice.SupplierInvoiceBuilder documentHeaderText(@Nullable
                                                                 String documentHeaderText)
```
    Constraints: Not nullable, Maximum length: 25
    Original property name from the Odata EDM: DocumentHeaderText
    not only for certain line items.
  - manualCashDiscount
```
public SupplierInvoice.SupplierInvoiceBuilder manualCashDiscount(@Nullable
                                                                 BigDecimal manualCashDiscount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: ManualCashDiscount
  - paymentTerms
```
public SupplierInvoice.SupplierInvoiceBuilder paymentTerms(@Nullable
                                                           String paymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: PaymentTerms
    
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
  - dueCalculationBaseDate
```
public SupplierInvoice.SupplierInvoiceBuilder dueCalculationBaseDate(@Nullable
                                                                     LocalDateTime dueCalculationBaseDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: DueCalculationBaseDate
    
    For line items in G/L accounts, the item is due immediately on this date because there are no cash discount specifications.During document entry for open item accounts, the date may be defaulted. For this, a terms of payment key must have been specified in the customer's/vendor's master record for which a default value is requested in the document.The proposed date can be overwritten.If the cash discount rates (and days) have not been entered, the baseline date for payment is the same as the due date.
    the case for line items in open item accounts.
  - cashDiscount1Percent
```
public SupplierInvoice.SupplierInvoiceBuilder cashDiscount1Percent(@Nullable
                                                                   BigDecimal cashDiscount1Percent)
```
    Constraints: Not nullable, Precision: 5, Scale: 3
    Original property name from the Odata EDM: CashDiscount1Percent
  - cashDiscount1Days
```
public SupplierInvoice.SupplierInvoiceBuilder cashDiscount1Days(@Nullable
                                                                BigDecimal cashDiscount1Days)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: CashDiscount1Days
  - cashDiscount2Percent
```
public SupplierInvoice.SupplierInvoiceBuilder cashDiscount2Percent(@Nullable
                                                                   BigDecimal cashDiscount2Percent)
```
    Constraints: Not nullable, Precision: 5, Scale: 3
    Original property name from the Odata EDM: CashDiscount2Percent
  - cashDiscount2Days
```
public SupplierInvoice.SupplierInvoiceBuilder cashDiscount2Days(@Nullable
                                                                BigDecimal cashDiscount2Days)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: CashDiscount2Days
  - netPaymentDays
```
public SupplierInvoice.SupplierInvoiceBuilder netPaymentDays(@Nullable
                                                             BigDecimal netPaymentDays)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: NetPaymentDays
  - paymentBlockingReason
```
public SupplierInvoice.SupplierInvoiceBuilder paymentBlockingReason(@Nullable
                                                                    String paymentBlockingReason)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentBlockingReason
    
    The following payment blocks exist:Manual payment blockIf you manually select a payment block from the list field to block an invoice for payment, the payment block field in the header of the invoice document is marked with the appropriate indicator.Blocked due to differencesIf invoices are to be blocked automatically due to differences in the invoice items, the system enters the payment block R in the vendor line of the Accounting document. The field in the header of the invoice document remains empty.Random payment blockInvoices that do not show any other blocking reason, can be blocked in accordance with the random principle. In Customizing for the Logistics invoice verification, you can set the probability for the block. The indicator for the logistical payment block is entered in the header of the invoice document.If you have set a manual payment block, and an invoice is blocked automatically due to differences in the invoice items, the system enters the manual payment block in the vendor line of the Accounting document.
  - accountingDocumentType
```
public SupplierInvoice.SupplierInvoiceBuilder accountingDocumentType(@Nullable
                                                                     String accountingDocumentType)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: AccountingDocumentType
    
    Attributes that control the entry of the document, or which are themselves noted in the document, are defined for each document type. In particular, the number range assigned to the associated documents is defined on the basis of the document type.
  - bPBankAccountInternalID
```
public SupplierInvoice.SupplierInvoiceBuilder bPBankAccountInternalID(@Nullable
                                                                      String bPBankAccountInternalID)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BPBankAccountInternalID
    
    In the business partner's master record:If several bank accounts exist in a customer or vendor master record, you can assign different keys for these accounts.In the item:To use a particular bank of the business partner for the payment of an item, enter the appropriate key in the item. The payment program then pays the item via the business partner's predefined bank.
  - supplierInvoiceStatus
```
public SupplierInvoice.SupplierInvoiceBuilder supplierInvoiceStatus(@Nullable
                                                                    String supplierInvoiceStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SupplierInvoiceStatus
    
    ' ': Posted (Online invoice verification)1: Planned for background verification (Bacground invoice verification)2: Deleted (Background and online invoice verification)3: Contains errors (Background invoice verification)4: Correct (Posted, not complete) (Background invoice verification)5: Posted (Background and online invoice verification)A: Parked (Online invoice verification)B: Parked complete (Online invoice verification)C: Held parked (Online invoice verification)D: Held entered (Online invoice verification)E: Parked released (Online invoice verification)
  - indirectQuotedExchangeRate
```
public SupplierInvoice.SupplierInvoiceBuilder indirectQuotedExchangeRate(@Nullable
                                                                         BigDecimal indirectQuotedExchangeRate)
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: IndirectQuotedExchangeRate
    
    If the field content is highlighted (usually in red), then you have set the indirect quotation method of exchange rate entry for that currency pair in Customizing.
    the price in the "to" currency that you have to pay for a unit (10, 100,...) of "from" currency.
  - directQuotedExchangeRate
```
public SupplierInvoice.SupplierInvoiceBuilder directQuotedExchangeRate(@Nullable
                                                                       BigDecimal directQuotedExchangeRate)
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: DirectQuotedExchangeRate
    
    If the field content is highlighted (usually in red), then you have set the direct quotation method of exchange rate entry for that currency pair in Customizing.
    the amount of the "from" currency that you get for a unit (10, 100,...) of the "to" currency.
  - stateCentralBankPaymentReason
```
public SupplierInvoice.SupplierInvoiceBuilder stateCentralBankPaymentReason(@Nullable
                                                                            String stateCentralBankPaymentReason)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: StateCentralBankPaymentReason
    
    In foreign payment transactions, information concerning the reason for payment is needed for the report according to German foreign trade regulations (AWV).The possible reasons for payment are defined within configuration for SCB indicators. This includes certain indicators which are the key to the reasons for payment, and an explanatory text.The reasons for payment appear on the reporting form and/or in the corresponding data medium exchange.AustriaFor foreign bank transfers, the explanatory text for the OeNB is determined using this indicator on the bank transfer form or in the data medium exchange.BelgiumThe content of the first text field for this indicator is used in the data medium exchange.NetherlandsThe usage of the state central bank indicator, the document type and the texts for this indicator is explained in the detailed documentation for the individual fields.JapanFor foreign bank transfers, the reason for payment is determined by this indicator when reporting to the Japanese ministry of finance.We recommend entering a "J" as the first letter so that you can better distinguish this report from other non-Japanese reports.
  - supplyingCountry
```
public SupplierInvoice.SupplierInvoiceBuilder supplyingCountry(@Nullable
                                                               String supplyingCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: SupplyingCountry
    
    This field contains the country key of the purchasing country in the case of imports or transits (field U4 or field V5 on the data medium) or that of the country of investment in the case of capital transactions (field W7).Together with the German State Central Bank indicator, this specification is needed for creating reports in line with German foreign trade regulations.
  - paymentMethod
```
public SupplierInvoice.SupplierInvoiceBuilder paymentMethod(@Nullable
                                                            String paymentMethod)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentMethod
    
    Payment methods are entered in the master records of customers and vendors in order to specify how payments are made. If an open item is to be paid using a specific payment method, enter it in the open item. The terms which have been defined for the payment method must be satisfied for the payment.Payment methods are to be defined in the Financial Accounting configuration menu, where the following steps are to be carried out:First of all, make all specifications that are required for a country-specific payment method.Then define per company code the terms under which a payment method can be used.All payment methods are displayed in the customer or vendor master record in the screen for selecting the payment method. Here you select the required payment method by marking it; the system transfers the payment methods to the customer/vendor master record.
    exchange.
  - paymentMethodSupplement
```
public SupplierInvoice.SupplierInvoiceBuilder paymentMethodSupplement(@Nullable
                                                                      String paymentMethodSupplement)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: PaymentMethodSupplement
    
    Items with different payment method supplements are settled individually. When printing a form, it is possible to print separately according to payment method supplement. Checks can thus be divided into several groups that are then subject to a number of different checking procedures in the company before being mailed, for example.When entering invoices, the payment method supplement is defaulted from the master record of the customer/vendor. You can overwrite this supplement.
  - paymentReference
```
public SupplierInvoice.SupplierInvoiceBuilder paymentReference(@Nullable
                                                               String paymentReference)
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: PaymentReference
    
    For vendor line items, the key that the vendor passes on in the invoice is entered in the payment reference. In automatic payment transactions, the payment reference can be passed on again to the payee.When an outgoing payment is made, the payment reference you specify is passed on to the relevant financial institute and from there to the payee.When you are processing your account statement, you can use the payment reference to determine which items you have paid and then clear them.Payment reference numbers are often used in Finland, Norway, and Sweden. These countries also have rules for the structure of the payment reference. Check digit procedures are used to check that these rules are followed.DME Finland: The number '4477' has a check digit of '8' and should be defined as the character string '44778'.DME Norway: The number '12345678' has the check digit '2' when using the Modulo-10 method, and check digit '5' when using the Modulo-11 method. Therefore, 123456782 or 123456785 are permitted as payment references.DME Sweden: The number '1234567890' has the check digit '3' and should be defined as the character string '12345678903'. The Modulo procedure used is a form of Modulo-10 with the key '1212121'.
    invoice. The customer should refer to the payment reference when making the payment.
  - invoiceReference
```
public SupplierInvoice.SupplierInvoiceBuilder invoiceReference(@Nullable
                                                               String invoiceReference)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InvoiceReference
  - invoiceReferenceFiscalYear
```
public SupplierInvoice.SupplierInvoiceBuilder invoiceReferenceFiscalYear(@Nullable
                                                                         String invoiceReferenceFiscalYear)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InvoiceReferenceFiscalYear
    
    The fiscal year is not required if the related document number is unique and has not been used in other fiscal years.
    document.
  - fixedCashDiscount
```
public SupplierInvoice.SupplierInvoiceBuilder fixedCashDiscount(@Nullable
                                                                String fixedCashDiscount)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: FixedCashDiscount
    
    You can prevent lost cash discounts with this indicator.You should set the indicator if the transaction is overdue, due to an incomplete transaction or is the fault of the customer/vendor.Generally, if a vendor account has a debit balance then no payment will be made. This may possibly cause unpaid invoices to exceed the entitled period.
    the corresponding period has elapsed or not.
  - unplannedDeliveryCostTaxCode
```
public SupplierInvoice.SupplierInvoiceBuilder unplannedDeliveryCostTaxCode(@Nullable
                                                                           String unplannedDeliveryCostTaxCode)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: UnplannedDeliveryCostTaxCode
    
    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 with these tax code exist.
    the tax authorities.
  - unplndDelivCostTaxJurisdiction
```
public SupplierInvoice.SupplierInvoiceBuilder unplndDelivCostTaxJurisdiction(@Nullable
                                                                             String unplndDelivCostTaxJurisdiction)
```
    Constraints: Not nullable, Maximum length: 15
    Original property name from the Odata EDM: UnplndDelivCostTaxJurisdiction
    authorities you must pay your taxes. It is always the city to which the goods are supplied.
  - assignmentReference
```
public SupplierInvoice.SupplierInvoiceBuilder assignmentReference(@Nullable
                                                                  String assignmentReference)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: AssignmentReference
    
    The program can display the account line items sorted according to the content of this field.You can either enter the field contents manually, or have the system define them automatically in the master record via the sort key field.You define the rules for the layout of the assignment number field in the Implementation Guide (IMG) under Determine Standard Sorting for Line Items.
  - supplierPostingLineItemText
```
public SupplierInvoice.SupplierInvoiceBuilder supplierPostingLineItemText(@Nullable
                                                                          String supplierPostingLineItemText)
```
    Constraints: Not nullable, Maximum length: 50
    Original property name from the Odata EDM: SupplierPostingLineItemText
    
    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.
  - taxIsCalculatedAutomatically
```
public SupplierInvoice.SupplierInvoiceBuilder taxIsCalculatedAutomatically(@Nullable
                                                                           Boolean taxIsCalculatedAutomatically)
```
    Constraints: none
    Original property name from the Odata EDM: TaxIsCalculatedAutomatically
  - businessPlace
```
public SupplierInvoice.SupplierInvoiceBuilder businessPlace(@Nullable
                                                            String businessPlace)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BusinessPlace
  - businessSectionCode
```
public SupplierInvoice.SupplierInvoiceBuilder businessSectionCode(@Nullable
                                                                  String businessSectionCode)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BusinessSectionCode
    
    You can customize section codes in Customizing for Financial Accounting (FI), by choosing Financial Accounting Global Settings -> Withholding Tax -> Extended Withholding Tax ->Basic Settings -> India or South Korea -> Define Section Codes.
  - businessArea
```
public SupplierInvoice.SupplierInvoiceBuilder businessArea(@Nullable
                                                           String businessArea)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BusinessArea
  - supplierInvoiceIsCreditMemo
```
public SupplierInvoice.SupplierInvoiceBuilder supplierInvoiceIsCreditMemo(@Nullable
                                                                          String supplierInvoiceIsCreditMemo)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SupplierInvoiceIsCreditMemo
  - paytSlipWthRefSubscriber
```
public SupplierInvoice.SupplierInvoiceBuilder paytSlipWthRefSubscriber(@Nullable
                                                                       String paytSlipWthRefSubscriber)
```
    Constraints: Not nullable, Maximum length: 11
    Original property name from the Odata EDM: PaytSlipWthRefSubscriber
    
    Every vendor who participates in this procedure receives a subscriber number. Providing the ISR procedure is to be used in automatic payment transactions, this subscriber number is to be entered in the master record.When entering invoices for vendor accounts, the subscriber number is copied into the document. The payment program pays all invoices with an ISR number individually.For data medium exchange, the transactions 'TA826' for data medium exchange and 'TA08' for SAD are created. When printing out a form, only a note is printed so that the appropriate blue inpayment slips can be attached to the authorized payment order.
    Service. The field is therefore only relevant in Switzerland.
  - paytSlipWthRefCheckDigit
```
public SupplierInvoice.SupplierInvoiceBuilder paytSlipWthRefCheckDigit(@Nullable
                                                                       String paytSlipWthRefCheckDigit)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: PaytSlipWthRefCheckDigit
    
    The rules for forming a check digit are set by the Swiss PTT.
    numbers (5 characters), it contains the check digit for the amount, subscriber number and reference number.
  - paytSlipWthRefReference
```
public SupplierInvoice.SupplierInvoiceBuilder paytSlipWthRefReference(@Nullable
                                                                      String paytSlipWthRefReference)
```
    Constraints: Not nullable, Maximum length: 27
    Original property name from the Odata EDM: PaytSlipWthRefReference
    for the ISR procedure (inpayment slip with reference number) in the Swiss Postal Service and for the QR bill, the successor to the ISR procedure in Switzerland and Liechtenstein. The modulus 10 check digit routine is used recursively for checking the field.
  - taxDeterminationDate
```
public SupplierInvoice.SupplierInvoiceBuilder 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.
  - invoiceReceiptDate
```
public SupplierInvoice.SupplierInvoiceBuilder invoiceReceiptDate(@Nullable
                                                                 LocalDateTime invoiceReceiptDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: InvoiceReceiptDate
  - deliveryOfGoodsReportingCntry
```
public SupplierInvoice.SupplierInvoiceBuilder deliveryOfGoodsReportingCntry(@Nullable
                                                                            String deliveryOfGoodsReportingCntry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: DeliveryOfGoodsReportingCntry
    
    By specifying the reporting country, call up the VAT reg.no. stored in the master record. The reporting country is not stored in the line item. For evaluations, the reporting country can be derived from the first two positions of the VAT reg.no.Enter the country key of the reporting country for which you want to call up the VAT reg.no.
    customer must be stored under the corresponding reporting country in the master record.
  - supplierVATRegistration
```
public SupplierInvoice.SupplierInvoiceBuilder supplierVATRegistration(@Nullable
                                                                      String supplierVATRegistration)
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: SupplierVATRegistration
    
    The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.
  - isEUTriangularDeal
```
public SupplierInvoice.SupplierInvoiceBuilder isEUTriangularDeal(@Nullable
                                                                 Boolean isEUTriangularDeal)
```
    Constraints: none
    Original property name from the Odata EDM: IsEUTriangularDeal
    deal section.
  - suplrInvcDebitCrdtCodeDelivery
```
public SupplierInvoice.SupplierInvoiceBuilder suplrInvcDebitCrdtCodeDelivery(@Nullable
                                                                             String suplrInvcDebitCrdtCodeDelivery)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SuplrInvcDebitCrdtCodeDelivery
  - suplrInvcDebitCrdtCodeReturns
```
public SupplierInvoice.SupplierInvoiceBuilder suplrInvcDebitCrdtCodeReturns(@Nullable
                                                                            String suplrInvcDebitCrdtCodeReturns)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: SuplrInvcDebitCrdtCodeReturns
  - build
```
public SupplierInvoice build()
```
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class Object

Class SupplierInvoice.SupplierInvoiceBuilder

Method Summary

Methods inherited from class java.lang.Object

Method Detail

suplrInvcItemPurOrdRef

supplierInvoiceItemGLAcct

supplierInvoiceTax

supplierInvoiceWhldgTax

supplierInvoice

fiscalYear

companyCode

documentDate

postingDate

supplierInvoiceIDByInvcgParty

invoicingParty

documentCurrency

invoiceGrossAmount

unplannedDeliveryCost

documentHeaderText

manualCashDiscount

paymentTerms

dueCalculationBaseDate

cashDiscount1Percent

cashDiscount1Days

cashDiscount2Percent

cashDiscount2Days

netPaymentDays

paymentBlockingReason

accountingDocumentType

bPBankAccountInternalID

supplierInvoiceStatus

indirectQuotedExchangeRate

directQuotedExchangeRate

stateCentralBankPaymentReason

supplyingCountry

paymentMethod

paymentMethodSupplement

paymentReference

invoiceReference

invoiceReferenceFiscalYear

fixedCashDiscount

unplannedDeliveryCostTaxCode

unplndDelivCostTaxJurisdiction

assignmentReference

supplierPostingLineItemText

taxIsCalculatedAutomatically

businessPlace

businessSectionCode

businessArea

supplierInvoiceIsCreditMemo

paytSlipWthRefSubscriber

paytSlipWthRefCheckDigit

paytSlipWthRefReference

taxDeterminationDate

invoiceReceiptDate

deliveryOfGoodsReportingCntry

supplierVATRegistration

isEUTriangularDeal

suplrInvcDebitCrdtCodeDelivery

suplrInvcDebitCrdtCodeReturns

build

toString