public class SupplierInvoice extends VdmEntity<SupplierInvoice>
Original entity name from the Odata EDM: A_SupplierInvoiceType
Modifier and Type | Class and Description |
---|---|
static class |
SupplierInvoice.SupplierInvoiceBuilder
Helper class to allow for fluent creation of SupplierInvoice instances.
|
Modifier and Type | Field and Description |
---|---|
static SupplierInvoiceField<String> |
ACCOUNTING_DOCUMENT_TYPE
Use with available fluent helpers to apply the AccountingDocumentType field to query operations.
|
static SupplierInvoiceSelectable |
ALL_FIELDS
Selector for all available fields of SupplierInvoice.
|
static SupplierInvoiceField<String> |
ASSIGNMENT_REFERENCE
Use with available fluent helpers to apply the AssignmentReference field to query operations.
|
static SupplierInvoiceField<String> |
BP_BANK_ACCOUNT_INTERNAL_ID
Use with available fluent helpers to apply the BPBankAccountInternalID field to query operations.
|
static SupplierInvoiceField<String> |
BUSINESS_AREA
Use with available fluent helpers to apply the BusinessArea field to query operations.
|
static SupplierInvoiceField<String> |
BUSINESS_PLACE
Use with available fluent helpers to apply the BusinessPlace field to query operations.
|
static SupplierInvoiceField<String> |
BUSINESS_SECTION_CODE
Use with available fluent helpers to apply the BusinessSectionCode field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
CASH_DISCOUNT1_DAYS
Use with available fluent helpers to apply the CashDiscount1Days field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
CASH_DISCOUNT1_PERCENT
Use with available fluent helpers to apply the CashDiscount1Percent field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
CASH_DISCOUNT2_DAYS
Use with available fluent helpers to apply the CashDiscount2Days field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
CASH_DISCOUNT2_PERCENT
Use with available fluent helpers to apply the CashDiscount2Percent field to query operations.
|
static SupplierInvoiceField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static SupplierInvoiceField<String> |
DELIVERY_OF_GOODS_REPORTING_CNTRY
Use with available fluent helpers to apply the DeliveryOfGoodsReportingCntry field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
DIRECT_QUOTED_EXCHANGE_RATE
Use with available fluent helpers to apply the DirectQuotedExchangeRate field to query operations.
|
static SupplierInvoiceField<String> |
DOCUMENT_CURRENCY
Use with available fluent helpers to apply the DocumentCurrency field to query operations.
|
static SupplierInvoiceField<LocalDateTime> |
DOCUMENT_DATE
Use with available fluent helpers to apply the DocumentDate field to query operations.
|
static SupplierInvoiceField<String> |
DOCUMENT_HEADER_TEXT
Use with available fluent helpers to apply the DocumentHeaderText field to query operations.
|
static SupplierInvoiceField<LocalDateTime> |
DUE_CALCULATION_BASE_DATE
Use with available fluent helpers to apply the DueCalculationBaseDate field to query operations.
|
static SupplierInvoiceField<String> |
FISCAL_YEAR
Use with available fluent helpers to apply the FiscalYear field to query operations.
|
static SupplierInvoiceField<String> |
FIXED_CASH_DISCOUNT
Use with available fluent helpers to apply the FixedCashDiscount field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
INDIRECT_QUOTED_EXCHANGE_RATE
Use with available fluent helpers to apply the IndirectQuotedExchangeRate field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
INVOICE_GROSS_AMOUNT
Use with available fluent helpers to apply the InvoiceGrossAmount field to query operations.
|
static SupplierInvoiceField<LocalDateTime> |
INVOICE_RECEIPT_DATE
Use with available fluent helpers to apply the InvoiceReceiptDate field to query operations.
|
static SupplierInvoiceField<String> |
INVOICE_REFERENCE
Use with available fluent helpers to apply the InvoiceReference field to query operations.
|
static SupplierInvoiceField<String> |
INVOICE_REFERENCE_FISCAL_YEAR
Use with available fluent helpers to apply the InvoiceReferenceFiscalYear field to query operations.
|
static SupplierInvoiceField<String> |
INVOICING_PARTY
Use with available fluent helpers to apply the InvoicingParty field to query operations.
|
static SupplierInvoiceField<Boolean> |
IS_EU_TRIANGULAR_DEAL
Use with available fluent helpers to apply the IsEUTriangularDeal field to query operations.
|
static SupplierInvoiceField<Boolean> |
IS_REVERSAL
Use with available fluent helpers to apply the IsReversal field to query operations.
|
static SupplierInvoiceField<Boolean> |
IS_REVERSED
Use with available fluent helpers to apply the IsReversed field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
MANUAL_CASH_DISCOUNT
Use with available fluent helpers to apply the ManualCashDiscount field to query operations.
|
static SupplierInvoiceField<BigDecimal> |
NET_PAYMENT_DAYS
Use with available fluent helpers to apply the NetPaymentDays field to query operations.
|
static SupplierInvoiceField<String> |
PAYMENT_BLOCKING_REASON
Use with available fluent helpers to apply the PaymentBlockingReason field to query operations.
|
static SupplierInvoiceField<String> |
PAYMENT_METHOD
Use with available fluent helpers to apply the PaymentMethod field to query operations.
|
static SupplierInvoiceField<String> |
PAYMENT_METHOD_SUPPLEMENT
Use with available fluent helpers to apply the PaymentMethodSupplement field to query operations.
|
static SupplierInvoiceField<String> |
PAYMENT_REFERENCE
Use with available fluent helpers to apply the PaymentReference field to query operations.
|
static SupplierInvoiceField<String> |
PAYMENT_TERMS
Use with available fluent helpers to apply the PaymentTerms field to query operations.
|
static SupplierInvoiceField<String> |
PAYT_SLIP_WTH_REF_CHECK_DIGIT
Use with available fluent helpers to apply the PaytSlipWthRefCheckDigit field to query operations.
|
static SupplierInvoiceField<String> |
PAYT_SLIP_WTH_REF_REFERENCE
Use with available fluent helpers to apply the PaytSlipWthRefReference field to query operations.
|
static SupplierInvoiceField<String> |
PAYT_SLIP_WTH_REF_SUBSCRIBER
Use with available fluent helpers to apply the PaytSlipWthRefSubscriber field to query operations.
|
static SupplierInvoiceField<LocalDateTime> |
POSTING_DATE
Use with available fluent helpers to apply the PostingDate field to query operations.
|
static SupplierInvoiceField<String> |
REVERSE_DOCUMENT
Use with available fluent helpers to apply the ReverseDocument field to query operations.
|
static SupplierInvoiceField<String> |
REVERSE_DOCUMENT_FISCAL_YEAR
Use with available fluent helpers to apply the ReverseDocumentFiscalYear field to query operations.
|
static SupplierInvoiceField<String> |
STATE_CENTRAL_BANK_PAYMENT_REASON
Use with available fluent helpers to apply the StateCentralBankPaymentReason field to query operations.
|
static SupplierInvoiceField<String> |
SUPLR_INVC_DEBIT_CRDT_CODE_DELIVERY
Use with available fluent helpers to apply the SuplrInvcDebitCrdtCodeDelivery field to query operations.
|
static SupplierInvoiceField<String> |
SUPLR_INVC_DEBIT_CRDT_CODE_RETURNS
Use with available fluent helpers to apply the SuplrInvcDebitCrdtCodeReturns field to query operations.
|
static SupplierInvoiceField<String> |
SUPPLIER_INVOICE
Use with available fluent helpers to apply the SupplierInvoice field to query operations.
|
static SupplierInvoiceField<String> |
SUPPLIER_INVOICE_ID_BY_INVCG_PARTY
Use with available fluent helpers to apply the SupplierInvoiceIDByInvcgParty field to query operations.
|
static SupplierInvoiceField<String> |
SUPPLIER_INVOICE_IS_CREDIT_MEMO
Use with available fluent helpers to apply the SupplierInvoiceIsCreditMemo field to query operations.
|
static SupplierInvoiceField<String> |
SUPPLIER_INVOICE_ORIGIN
Use with available fluent helpers to apply the SupplierInvoiceOrigin field to query operations.
|
static SupplierInvoiceField<String> |
SUPPLIER_INVOICE_STATUS
Use with available fluent helpers to apply the SupplierInvoiceStatus field to query operations.
|
static SupplierInvoiceField<String> |
SUPPLIER_POSTING_LINE_ITEM_TEXT
Use with available fluent helpers to apply the SupplierPostingLineItemText field to query operations.
|
static SupplierInvoiceField<String> |
SUPPLIER_VAT_REGISTRATION
Use with available fluent helpers to apply the SupplierVATRegistration field to query operations.
|
static SupplierInvoiceField<String> |
SUPPLYING_COUNTRY
Use with available fluent helpers to apply the SupplyingCountry field to query operations.
|
static SupplierInvoiceField<LocalDateTime> |
TAX_DETERMINATION_DATE
Use with available fluent helpers to apply the TaxDeterminationDate field to query operations.
|
static SupplierInvoiceField<Boolean> |
TAX_IS_CALCULATED_AUTOMATICALLY
Use with available fluent helpers to apply the TaxIsCalculatedAutomatically field to query operations.
|
static SupplierInvoiceField<LocalDateTime> |
TAX_REPORTING_DATE
Use with available fluent helpers to apply the TaxReportingDate field to query operations.
|
static SupplierInvoiceLink<SuplrInvcItemPurOrdRef> |
TO_SUPLR_INVC_ITEM_PUR_ORD_REF
Use with available fluent helpers to apply the to_SuplrInvcItemPurOrdRef navigation property to query
operations.
|
static SupplierInvoiceLink<SupplierInvoiceItemGLAcct> |
TO_SUPPLIER_INVOICE_ITEM_GL_ACCT
Use with available fluent helpers to apply the to_SupplierInvoiceItemGLAcct navigation property to query
operations.
|
static SupplierInvoiceLink<SupplierInvoiceTax> |
TO_SUPPLIER_INVOICE_TAX
Use with available fluent helpers to apply the to_SupplierInvoiceTax navigation property to query
operations.
|
static SupplierInvoiceLink<SuplrInvcHeaderWhldgTax> |
TO_SUPPLIER_INVOICE_WHLDG_TAX
Use with available fluent helpers to apply the to_SupplierInvoiceWhldgTax navigation property to query
operations.
|
static SupplierInvoiceField<BigDecimal> |
UNPLANNED_DELIVERY_COST
Use with available fluent helpers to apply the UnplannedDeliveryCost field to query operations.
|
static SupplierInvoiceField<String> |
UNPLANNED_DELIVERY_COST_TAX_CODE
Use with available fluent helpers to apply the UnplannedDeliveryCostTaxCode field to query operations.
|
static SupplierInvoiceField<String> |
UNPLND_DELIV_COST_TAX_JURISDICTION
Use with available fluent helpers to apply the UnplndDelivCostTaxJurisdiction field to query operations.
|
static SupplierInvoiceField<String> |
UNPLND_DELIVERY_COST_TAX_COUNTRY
Use with available fluent helpers to apply the UnplndDeliveryCostTaxCountry field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SupplierInvoice() |
SupplierInvoice(String supplierInvoice,
String fiscalYear,
String companyCode,
LocalDateTime documentDate,
LocalDateTime postingDate,
String supplierInvoiceIDByInvcgParty,
String invoicingParty,
String documentCurrency,
BigDecimal invoiceGrossAmount,
BigDecimal unplannedDeliveryCost,
String documentHeaderText,
BigDecimal manualCashDiscount,
String paymentTerms,
LocalDateTime dueCalculationBaseDate,
BigDecimal cashDiscount1Percent,
BigDecimal cashDiscount1Days,
BigDecimal cashDiscount2Percent,
BigDecimal cashDiscount2Days,
BigDecimal netPaymentDays,
String paymentBlockingReason,
String accountingDocumentType,
String bPBankAccountInternalID,
String supplierInvoiceStatus,
BigDecimal indirectQuotedExchangeRate,
BigDecimal directQuotedExchangeRate,
String stateCentralBankPaymentReason,
String supplyingCountry,
String paymentMethod,
String paymentMethodSupplement,
String paymentReference,
String invoiceReference,
String invoiceReferenceFiscalYear,
String fixedCashDiscount,
String unplannedDeliveryCostTaxCode,
String unplndDelivCostTaxJurisdiction,
String unplndDeliveryCostTaxCountry,
String assignmentReference,
String supplierPostingLineItemText,
Boolean taxIsCalculatedAutomatically,
String businessPlace,
String businessSectionCode,
String businessArea,
String supplierInvoiceIsCreditMemo,
String paytSlipWthRefSubscriber,
String paytSlipWthRefCheckDigit,
String paytSlipWthRefReference,
LocalDateTime taxDeterminationDate,
LocalDateTime taxReportingDate,
LocalDateTime invoiceReceiptDate,
String deliveryOfGoodsReportingCntry,
String supplierVATRegistration,
Boolean isEUTriangularDeal,
String suplrInvcDebitCrdtCodeDelivery,
String suplrInvcDebitCrdtCodeReturns,
String supplierInvoiceOrigin,
String reverseDocument,
String reverseDocumentFiscalYear,
Boolean isReversal,
Boolean isReversed,
List<SuplrInvcItemPurOrdRef> toSuplrInvcItemPurOrdRef,
List<SupplierInvoiceItemGLAcct> toSupplierInvoiceItemGLAcct,
List<SupplierInvoiceTax> toSupplierInvoiceTax,
List<SuplrInvcHeaderWhldgTax> toSupplierInvoiceWhldgTax) |
Modifier and Type | Method and Description |
---|---|
void |
addSuplrInvcItemPurOrdRef(SuplrInvcItemPurOrdRef... entity)
Adds elements to the list of associated SuplrInvcItemPurOrdRef entities.
|
void |
addSupplierInvoiceItemGLAcct(SupplierInvoiceItemGLAcct... entity)
Adds elements to the list of associated SupplierInvoiceItemGLAcct entities.
|
void |
addSupplierInvoiceTax(SupplierInvoiceTax... entity)
Adds elements to the list of associated SupplierInvoiceTax entities.
|
void |
addSupplierInvoiceWhldgTax(SuplrInvcHeaderWhldgTax... entity)
Adds elements to the list of associated SuplrInvcHeaderWhldgTax entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static SupplierInvoice.SupplierInvoiceBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<SuplrInvcItemPurOrdRef> |
fetchSuplrInvcItemPurOrdRef()
Fetches the SuplrInvcItemPurOrdRef entities (one to many) associated with this entity.
|
List<SupplierInvoiceItemGLAcct> |
fetchSupplierInvoiceItemGLAcct()
Fetches the SupplierInvoiceItemGLAcct entities (one to many) associated with this entity.
|
List<SupplierInvoiceTax> |
fetchSupplierInvoiceTax()
Fetches the SupplierInvoiceTax entities (one to many) associated with this entity.
|
List<SuplrInvcHeaderWhldgTax> |
fetchSupplierInvoiceWhldgTax()
Fetches the SuplrInvcHeaderWhldgTax entities (one to many) associated with this entity.
|
static <T> SupplierInvoiceField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getAccountingDocumentType()
Constraints: Not nullable, Maximum length: 2
|
String |
getAssignmentReference()
Constraints: Not nullable, Maximum length: 18
|
String |
getBPBankAccountInternalID()
Constraints: Not nullable, Maximum length: 4
|
String |
getBusinessArea()
Constraints: Not nullable, Maximum length: 4
|
String |
getBusinessPlace()
Constraints: Not nullable, Maximum length: 4
|
String |
getBusinessSectionCode()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getCashDiscount1Days()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getCashDiscount1Percent()
Constraints: Not nullable, Precision: 5, Scale: 3
|
BigDecimal |
getCashDiscount2Days()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getCashDiscount2Percent()
Constraints: Not nullable, Precision: 5, Scale: 3
|
String |
getCompanyCode()
Constraints: Not nullable, Maximum length: 4
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getDeliveryOfGoodsReportingCntry()
Constraints: Not nullable, Maximum length: 3
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
BigDecimal |
getDirectQuotedExchangeRate()
Constraints: Not nullable, Precision: 9, Scale: 5
|
String |
getDocumentCurrency()
Constraints: Not nullable, Maximum length: 5
|
LocalDateTime |
getDocumentDate()
Constraints: Not nullable, Precision: 0
|
String |
getDocumentHeaderText()
Constraints: Not nullable, Maximum length: 25
|
LocalDateTime |
getDueCalculationBaseDate()
Constraints: Not nullable, Precision: 0
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getFiscalYear()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getFixedCashDiscount()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getIndirectQuotedExchangeRate()
Constraints: Not nullable, Precision: 9, Scale: 5
|
BigDecimal |
getInvoiceGrossAmount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
LocalDateTime |
getInvoiceReceiptDate()
Constraints: Not nullable, Precision: 0
|
String |
getInvoiceReference()
Constraints: Not nullable, Maximum length: 10
|
String |
getInvoiceReferenceFiscalYear()
Constraints: Not nullable, Maximum length: 4
|
String |
getInvoicingParty()
Constraints: Not nullable, Maximum length: 10
|
Boolean |
getIsEUTriangularDeal()
Constraints: none
|
Boolean |
getIsReversal()
Constraints: none
|
Boolean |
getIsReversed()
Constraints: none
|
protected Map<String,Object> |
getKey() |
BigDecimal |
getManualCashDiscount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
BigDecimal |
getNetPaymentDays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
String |
getPaymentBlockingReason()
Constraints: Not nullable, Maximum length: 1
|
String |
getPaymentMethod()
Constraints: Not nullable, Maximum length: 1
|
String |
getPaymentMethodSupplement()
Constraints: Not nullable, Maximum length: 2
|
String |
getPaymentReference()
Constraints: Not nullable, Maximum length: 30
|
String |
getPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
String |
getPaytSlipWthRefCheckDigit()
Constraints: Not nullable, Maximum length: 2
|
String |
getPaytSlipWthRefReference()
Constraints: Not nullable, Maximum length: 27
|
String |
getPaytSlipWthRefSubscriber()
Constraints: Not nullable, Maximum length: 11
|
LocalDateTime |
getPostingDate()
Constraints: Not nullable, Precision: 0
|
String |
getReverseDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getReverseDocumentFiscalYear()
Constraints: Not nullable, Maximum length: 4
|
String |
getStateCentralBankPaymentReason()
Constraints: Not nullable, Maximum length: 3
|
String |
getSuplrInvcDebitCrdtCodeDelivery()
Constraints: Not nullable, Maximum length: 1
|
String |
getSuplrInvcDebitCrdtCodeReturns()
Constraints: Not nullable, Maximum length: 1
|
io.vavr.control.Option<List<SuplrInvcItemPurOrdRef>> |
getSuplrInvcItemPurOrdRefIfPresent()
Retrieval of associated SuplrInvcItemPurOrdRef entities (one to many).
|
List<SuplrInvcItemPurOrdRef> |
getSuplrInvcItemPurOrdRefOrFetch()
Retrieval of associated SuplrInvcItemPurOrdRef entities (one to many).
|
String |
getSupplierInvoice()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSupplierInvoiceIDByInvcgParty()
Constraints: Not nullable, Maximum length: 16
|
String |
getSupplierInvoiceIsCreditMemo()
Constraints: Not nullable, Maximum length: 1
|
io.vavr.control.Option<List<SupplierInvoiceItemGLAcct>> |
getSupplierInvoiceItemGLAcctIfPresent()
Retrieval of associated SupplierInvoiceItemGLAcct entities (one to many).
|
List<SupplierInvoiceItemGLAcct> |
getSupplierInvoiceItemGLAcctOrFetch()
Retrieval of associated SupplierInvoiceItemGLAcct entities (one to many).
|
String |
getSupplierInvoiceOrigin()
Constraints: Not nullable, Maximum length: 1
|
String |
getSupplierInvoiceStatus()
Constraints: Not nullable, Maximum length: 1
|
io.vavr.control.Option<List<SupplierInvoiceTax>> |
getSupplierInvoiceTaxIfPresent()
Retrieval of associated SupplierInvoiceTax entities (one to many).
|
List<SupplierInvoiceTax> |
getSupplierInvoiceTaxOrFetch()
Retrieval of associated SupplierInvoiceTax entities (one to many).
|
io.vavr.control.Option<List<SuplrInvcHeaderWhldgTax>> |
getSupplierInvoiceWhldgTaxIfPresent()
Retrieval of associated SuplrInvcHeaderWhldgTax entities (one to many).
|
List<SuplrInvcHeaderWhldgTax> |
getSupplierInvoiceWhldgTaxOrFetch()
Retrieval of associated SuplrInvcHeaderWhldgTax entities (one to many).
|
String |
getSupplierPostingLineItemText()
Constraints: Not nullable, Maximum length: 50
|
String |
getSupplierVATRegistration()
Constraints: Not nullable, Maximum length: 20
|
String |
getSupplyingCountry()
Constraints: Not nullable, Maximum length: 3
|
LocalDateTime |
getTaxDeterminationDate()
Constraints: Not nullable, Precision: 0
|
Boolean |
getTaxIsCalculatedAutomatically()
Constraints: none
|
LocalDateTime |
getTaxReportingDate()
Constraints: Not nullable, Precision: 0
|
Class<SupplierInvoice> |
getType() |
BigDecimal |
getUnplannedDeliveryCost()
Constraints: Not nullable, Precision: 14, Scale: 3
|
String |
getUnplannedDeliveryCostTaxCode()
Constraints: Not nullable, Maximum length: 2
|
String |
getUnplndDelivCostTaxJurisdiction()
Constraints: Not nullable, Maximum length: 15
|
String |
getUnplndDeliveryCostTaxCountry()
Constraints: Not nullable, Maximum length: 3
|
int |
hashCode() |
void |
setAccountingDocumentType(String accountingDocumentType)
Constraints: Not nullable, Maximum length: 2
|
void |
setAssignmentReference(String assignmentReference)
Constraints: Not nullable, Maximum length: 18
|
void |
setBPBankAccountInternalID(String bPBankAccountInternalID)
Constraints: Not nullable, Maximum length: 4
|
void |
setBusinessArea(String businessArea)
Constraints: Not nullable, Maximum length: 4
|
void |
setBusinessPlace(String businessPlace)
Constraints: Not nullable, Maximum length: 4
|
void |
setBusinessSectionCode(String businessSectionCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setCashDiscount1Days(BigDecimal cashDiscount1Days)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setCashDiscount1Percent(BigDecimal cashDiscount1Percent)
Constraints: Not nullable, Precision: 5, Scale: 3
|
void |
setCashDiscount2Days(BigDecimal cashDiscount2Days)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setCashDiscount2Percent(BigDecimal cashDiscount2Percent)
Constraints: Not nullable, Precision: 5, Scale: 3
|
void |
setCompanyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setDeliveryOfGoodsReportingCntry(String deliveryOfGoodsReportingCntry)
Constraints: Not nullable, Maximum length: 3
|
void |
setDirectQuotedExchangeRate(BigDecimal directQuotedExchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5
|
void |
setDocumentCurrency(String documentCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setDocumentDate(LocalDateTime documentDate)
Constraints: Not nullable, Precision: 0
|
void |
setDocumentHeaderText(String documentHeaderText)
Constraints: Not nullable, Maximum length: 25
|
void |
setDueCalculationBaseDate(LocalDateTime dueCalculationBaseDate)
Constraints: Not nullable, Precision: 0
|
void |
setFiscalYear(String fiscalYear)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setFixedCashDiscount(String fixedCashDiscount)
Constraints: Not nullable, Maximum length: 1
|
void |
setIndirectQuotedExchangeRate(BigDecimal indirectQuotedExchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5
|
void |
setInvoiceGrossAmount(BigDecimal invoiceGrossAmount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setInvoiceReceiptDate(LocalDateTime invoiceReceiptDate)
Constraints: Not nullable, Precision: 0
|
void |
setInvoiceReference(String invoiceReference)
Constraints: Not nullable, Maximum length: 10
|
void |
setInvoiceReferenceFiscalYear(String invoiceReferenceFiscalYear)
Constraints: Not nullable, Maximum length: 4
|
void |
setInvoicingParty(String invoicingParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setIsEUTriangularDeal(Boolean isEUTriangularDeal)
Constraints: none
|
void |
setIsReversal(Boolean isReversal)
Constraints: none
|
void |
setIsReversed(Boolean isReversed)
Constraints: none
|
void |
setManualCashDiscount(BigDecimal manualCashDiscount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setNetPaymentDays(BigDecimal netPaymentDays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setPaymentBlockingReason(String paymentBlockingReason)
Constraints: Not nullable, Maximum length: 1
|
void |
setPaymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1
|
void |
setPaymentMethodSupplement(String paymentMethodSupplement)
Constraints: Not nullable, Maximum length: 2
|
void |
setPaymentReference(String paymentReference)
Constraints: Not nullable, Maximum length: 30
|
void |
setPaymentTerms(String paymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setPaytSlipWthRefCheckDigit(String paytSlipWthRefCheckDigit)
Constraints: Not nullable, Maximum length: 2
|
void |
setPaytSlipWthRefReference(String paytSlipWthRefReference)
Constraints: Not nullable, Maximum length: 27
|
void |
setPaytSlipWthRefSubscriber(String paytSlipWthRefSubscriber)
Constraints: Not nullable, Maximum length: 11
|
void |
setPostingDate(LocalDateTime postingDate)
Constraints: Not nullable, Precision: 0
|
void |
setReverseDocument(String reverseDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setReverseDocumentFiscalYear(String reverseDocumentFiscalYear)
Constraints: Not nullable, Maximum length: 4
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setStateCentralBankPaymentReason(String stateCentralBankPaymentReason)
Constraints: Not nullable, Maximum length: 3
|
void |
setSuplrInvcDebitCrdtCodeDelivery(String suplrInvcDebitCrdtCodeDelivery)
Constraints: Not nullable, Maximum length: 1
|
void |
setSuplrInvcDebitCrdtCodeReturns(String suplrInvcDebitCrdtCodeReturns)
Constraints: Not nullable, Maximum length: 1
|
void |
setSuplrInvcItemPurOrdRef(List<SuplrInvcItemPurOrdRef> value)
Overwrites the list of associated SuplrInvcItemPurOrdRef entities for the loaded navigation property
to_SuplrInvcItemPurOrdRef.
|
void |
setSupplierInvoice(String supplierInvoice)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSupplierInvoiceIDByInvcgParty(String supplierInvoiceIDByInvcgParty)
Constraints: Not nullable, Maximum length: 16
|
void |
setSupplierInvoiceIsCreditMemo(String supplierInvoiceIsCreditMemo)
Constraints: Not nullable, Maximum length: 1
|
void |
setSupplierInvoiceItemGLAcct(List<SupplierInvoiceItemGLAcct> value)
Overwrites the list of associated SupplierInvoiceItemGLAcct entities for the loaded navigation property
to_SupplierInvoiceItemGLAcct.
|
void |
setSupplierInvoiceOrigin(String supplierInvoiceOrigin)
Constraints: Not nullable, Maximum length: 1
|
void |
setSupplierInvoiceStatus(String supplierInvoiceStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setSupplierInvoiceTax(List<SupplierInvoiceTax> value)
Overwrites the list of associated SupplierInvoiceTax entities for the loaded navigation property
to_SupplierInvoiceTax.
|
void |
setSupplierInvoiceWhldgTax(List<SuplrInvcHeaderWhldgTax> value)
Overwrites the list of associated SuplrInvcHeaderWhldgTax entities for the loaded navigation property
to_SupplierInvoiceWhldgTax.
|
void |
setSupplierPostingLineItemText(String supplierPostingLineItemText)
Constraints: Not nullable, Maximum length: 50
|
void |
setSupplierVATRegistration(String supplierVATRegistration)
Constraints: Not nullable, Maximum length: 20
|
void |
setSupplyingCountry(String supplyingCountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setTaxDeterminationDate(LocalDateTime taxDeterminationDate)
Constraints: Not nullable, Precision: 0
|
void |
setTaxIsCalculatedAutomatically(Boolean taxIsCalculatedAutomatically)
Constraints: none
|
void |
setTaxReportingDate(LocalDateTime taxReportingDate)
Constraints: Not nullable, Precision: 0
|
void |
setUnplannedDeliveryCost(BigDecimal unplannedDeliveryCost)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setUnplannedDeliveryCostTaxCode(String unplannedDeliveryCostTaxCode)
Constraints: Not nullable, Maximum length: 2
|
void |
setUnplndDelivCostTaxJurisdiction(String unplndDelivCostTaxJurisdiction)
Constraints: Not nullable, Maximum length: 15
|
void |
setUnplndDeliveryCostTaxCountry(String unplndDeliveryCostTaxCountry)
Constraints: Not nullable, Maximum length: 3
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final SupplierInvoiceSelectable ALL_FIELDS
public static final SupplierInvoiceField<String> SUPPLIER_INVOICE
public static final SupplierInvoiceField<String> FISCAL_YEAR
public static final SupplierInvoiceField<String> COMPANY_CODE
public static final SupplierInvoiceField<LocalDateTime> DOCUMENT_DATE
public static final SupplierInvoiceField<LocalDateTime> POSTING_DATE
public static final SupplierInvoiceField<String> SUPPLIER_INVOICE_ID_BY_INVCG_PARTY
public static final SupplierInvoiceField<String> INVOICING_PARTY
public static final SupplierInvoiceField<String> DOCUMENT_CURRENCY
public static final SupplierInvoiceField<BigDecimal> INVOICE_GROSS_AMOUNT
public static final SupplierInvoiceField<BigDecimal> UNPLANNED_DELIVERY_COST
public static final SupplierInvoiceField<String> DOCUMENT_HEADER_TEXT
public static final SupplierInvoiceField<BigDecimal> MANUAL_CASH_DISCOUNT
public static final SupplierInvoiceField<String> PAYMENT_TERMS
public static final SupplierInvoiceField<LocalDateTime> DUE_CALCULATION_BASE_DATE
public static final SupplierInvoiceField<BigDecimal> CASH_DISCOUNT1_PERCENT
public static final SupplierInvoiceField<BigDecimal> CASH_DISCOUNT1_DAYS
public static final SupplierInvoiceField<BigDecimal> CASH_DISCOUNT2_PERCENT
public static final SupplierInvoiceField<BigDecimal> CASH_DISCOUNT2_DAYS
public static final SupplierInvoiceField<BigDecimal> NET_PAYMENT_DAYS
public static final SupplierInvoiceField<String> PAYMENT_BLOCKING_REASON
public static final SupplierInvoiceField<String> ACCOUNTING_DOCUMENT_TYPE
public static final SupplierInvoiceField<String> BP_BANK_ACCOUNT_INTERNAL_ID
public static final SupplierInvoiceField<String> SUPPLIER_INVOICE_STATUS
public static final SupplierInvoiceField<BigDecimal> INDIRECT_QUOTED_EXCHANGE_RATE
public static final SupplierInvoiceField<BigDecimal> DIRECT_QUOTED_EXCHANGE_RATE
public static final SupplierInvoiceField<String> STATE_CENTRAL_BANK_PAYMENT_REASON
public static final SupplierInvoiceField<String> SUPPLYING_COUNTRY
public static final SupplierInvoiceField<String> PAYMENT_METHOD
public static final SupplierInvoiceField<String> PAYMENT_METHOD_SUPPLEMENT
public static final SupplierInvoiceField<String> PAYMENT_REFERENCE
public static final SupplierInvoiceField<String> INVOICE_REFERENCE
public static final SupplierInvoiceField<String> INVOICE_REFERENCE_FISCAL_YEAR
public static final SupplierInvoiceField<String> FIXED_CASH_DISCOUNT
public static final SupplierInvoiceField<String> UNPLANNED_DELIVERY_COST_TAX_CODE
public static final SupplierInvoiceField<String> UNPLND_DELIV_COST_TAX_JURISDICTION
public static final SupplierInvoiceField<String> UNPLND_DELIVERY_COST_TAX_COUNTRY
public static final SupplierInvoiceField<String> ASSIGNMENT_REFERENCE
public static final SupplierInvoiceField<String> SUPPLIER_POSTING_LINE_ITEM_TEXT
public static final SupplierInvoiceField<Boolean> TAX_IS_CALCULATED_AUTOMATICALLY
public static final SupplierInvoiceField<String> BUSINESS_PLACE
public static final SupplierInvoiceField<String> BUSINESS_SECTION_CODE
public static final SupplierInvoiceField<String> BUSINESS_AREA
public static final SupplierInvoiceField<String> SUPPLIER_INVOICE_IS_CREDIT_MEMO
public static final SupplierInvoiceField<String> PAYT_SLIP_WTH_REF_SUBSCRIBER
public static final SupplierInvoiceField<String> PAYT_SLIP_WTH_REF_CHECK_DIGIT
public static final SupplierInvoiceField<String> PAYT_SLIP_WTH_REF_REFERENCE
public static final SupplierInvoiceField<LocalDateTime> TAX_DETERMINATION_DATE
public static final SupplierInvoiceField<LocalDateTime> TAX_REPORTING_DATE
public static final SupplierInvoiceField<LocalDateTime> INVOICE_RECEIPT_DATE
public static final SupplierInvoiceField<String> DELIVERY_OF_GOODS_REPORTING_CNTRY
public static final SupplierInvoiceField<String> SUPPLIER_VAT_REGISTRATION
public static final SupplierInvoiceField<Boolean> IS_EU_TRIANGULAR_DEAL
public static final SupplierInvoiceField<String> SUPLR_INVC_DEBIT_CRDT_CODE_DELIVERY
public static final SupplierInvoiceField<String> SUPLR_INVC_DEBIT_CRDT_CODE_RETURNS
public static final SupplierInvoiceField<String> SUPPLIER_INVOICE_ORIGIN
public static final SupplierInvoiceField<String> REVERSE_DOCUMENT
public static final SupplierInvoiceField<String> REVERSE_DOCUMENT_FISCAL_YEAR
public static final SupplierInvoiceField<Boolean> IS_REVERSAL
public static final SupplierInvoiceField<Boolean> IS_REVERSED
public static final SupplierInvoiceLink<SuplrInvcItemPurOrdRef> TO_SUPLR_INVC_ITEM_PUR_ORD_REF
public static final SupplierInvoiceLink<SupplierInvoiceItemGLAcct> TO_SUPPLIER_INVOICE_ITEM_GL_ACCT
public static final SupplierInvoiceLink<SupplierInvoiceTax> TO_SUPPLIER_INVOICE_TAX
public static final SupplierInvoiceLink<SuplrInvcHeaderWhldgTax> TO_SUPPLIER_INVOICE_WHLDG_TAX
public SupplierInvoice()
public SupplierInvoice(@Nullable String supplierInvoice, @Nullable String fiscalYear, @Nullable String companyCode, @Nullable LocalDateTime documentDate, @Nullable LocalDateTime postingDate, @Nullable String supplierInvoiceIDByInvcgParty, @Nullable String invoicingParty, @Nullable String documentCurrency, @Nullable BigDecimal invoiceGrossAmount, @Nullable BigDecimal unplannedDeliveryCost, @Nullable String documentHeaderText, @Nullable BigDecimal manualCashDiscount, @Nullable String paymentTerms, @Nullable LocalDateTime dueCalculationBaseDate, @Nullable BigDecimal cashDiscount1Percent, @Nullable BigDecimal cashDiscount1Days, @Nullable BigDecimal cashDiscount2Percent, @Nullable BigDecimal cashDiscount2Days, @Nullable BigDecimal netPaymentDays, @Nullable String paymentBlockingReason, @Nullable String accountingDocumentType, @Nullable String bPBankAccountInternalID, @Nullable String supplierInvoiceStatus, @Nullable BigDecimal indirectQuotedExchangeRate, @Nullable BigDecimal directQuotedExchangeRate, @Nullable String stateCentralBankPaymentReason, @Nullable String supplyingCountry, @Nullable String paymentMethod, @Nullable String paymentMethodSupplement, @Nullable String paymentReference, @Nullable String invoiceReference, @Nullable String invoiceReferenceFiscalYear, @Nullable String fixedCashDiscount, @Nullable String unplannedDeliveryCostTaxCode, @Nullable String unplndDelivCostTaxJurisdiction, @Nullable String unplndDeliveryCostTaxCountry, @Nullable String assignmentReference, @Nullable String supplierPostingLineItemText, @Nullable Boolean taxIsCalculatedAutomatically, @Nullable String businessPlace, @Nullable String businessSectionCode, @Nullable String businessArea, @Nullable String supplierInvoiceIsCreditMemo, @Nullable String paytSlipWthRefSubscriber, @Nullable String paytSlipWthRefCheckDigit, @Nullable String paytSlipWthRefReference, @Nullable LocalDateTime taxDeterminationDate, @Nullable LocalDateTime taxReportingDate, @Nullable LocalDateTime invoiceReceiptDate, @Nullable String deliveryOfGoodsReportingCntry, @Nullable String supplierVATRegistration, @Nullable Boolean isEUTriangularDeal, @Nullable String suplrInvcDebitCrdtCodeDelivery, @Nullable String suplrInvcDebitCrdtCodeReturns, @Nullable String supplierInvoiceOrigin, @Nullable String reverseDocument, @Nullable String reverseDocumentFiscalYear, @Nullable Boolean isReversal, @Nullable Boolean isReversed, List<SuplrInvcItemPurOrdRef> toSuplrInvcItemPurOrdRef, List<SupplierInvoiceItemGLAcct> toSupplierInvoiceItemGLAcct, List<SupplierInvoiceTax> toSupplierInvoiceTax, List<SuplrInvcHeaderWhldgTax> toSupplierInvoiceWhldgTax)
@Nonnull public Class<SupplierInvoice> getType()
getType
in class VdmObject<SupplierInvoice>
public void setSupplierInvoice(@Nullable String supplierInvoice)
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.
supplierInvoice
- Number which uniquely identifies an invoice document.public void setFiscalYear(@Nullable String fiscalYear)
Original property name from the Odata EDM: FiscalYear
fiscalYear
- Period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The
fiscal year can be the same as the calendar year, but does not have to be.public void setCompanyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
companyCode
- The company code is an organizational unit within financial accounting.public void setDocumentDate(@Nullable LocalDateTime documentDate)
Original property name from the Odata EDM: DocumentDate
documentDate
- Specifies the issue date of the original document.public void setPostingDate(@Nullable LocalDateTime postingDate)
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).
postingDate
- Date which is used when entering the document in Financial Accounting or Controlling.public void setSupplierInvoiceIDByInvcgParty(@Nullable String supplierInvoiceIDByInvcgParty)
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 "*".
supplierInvoiceIDByInvcgParty
- The reference document number can contain the document number of the customer/vendor. However it may
contain a different value.public void setInvoicingParty(@Nullable String invoicingParty)
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.
invoicingParty
- Alphanumeric key uniquely identifying the document.public void setDocumentCurrency(@Nullable String documentCurrency)
Original property name from the Odata EDM: DocumentCurrency
documentCurrency
- Currency key for amounts in the system.public void setInvoiceGrossAmount(@Nullable BigDecimal invoiceGrossAmount)
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
invoiceGrossAmount
- The gross invoice amount is the sum of the net item amounts together with the tax amounts.public void setUnplannedDeliveryCost(@Nullable BigDecimal unplannedDeliveryCost)
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.
unplannedDeliveryCost
- This field is for entering unplanned delivery costs.public void setDocumentHeaderText(@Nullable String documentHeaderText)
Original property name from the Odata EDM: DocumentHeaderText
documentHeaderText
- The document header text contains explanations or notes which apply to the document as a whole, that
is, not only for certain line items.public void setManualCashDiscount(@Nullable BigDecimal manualCashDiscount)
Original property name from the Odata EDM: ManualCashDiscount
manualCashDiscount
- Cash Discount Amount in Document Currencypublic void setPaymentTerms(@Nullable String paymentTerms)
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.
paymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setDueCalculationBaseDate(@Nullable LocalDateTime dueCalculationBaseDate)
Original property name from the Odata EDM: DueCalculationBaseDate
dueCalculationBaseDate
- Baseline date for due date calculationpublic void setCashDiscount1Percent(@Nullable BigDecimal cashDiscount1Percent)
Original property name from the Odata EDM: CashDiscount1Percent
cashDiscount1Percent
- Cash discount percentage rate applied to the shortest payment period.public void setCashDiscount1Days(@Nullable BigDecimal cashDiscount1Days)
Original property name from the Odata EDM: CashDiscount1Days
cashDiscount1Days
- Period within which a payment must be made in order to take advantage of the first cash discount
terms.public void setCashDiscount2Percent(@Nullable BigDecimal cashDiscount2Percent)
Original property name from the Odata EDM: CashDiscount2Percent
cashDiscount2Percent
- Cash discount percentage rate applied to the second payment period.public void setCashDiscount2Days(@Nullable BigDecimal cashDiscount2Days)
Original property name from the Odata EDM: CashDiscount2Days
cashDiscount2Days
- Period within which a payment must be made in order to take advantage of the second cash discount
terms.public void setNetPaymentDays(@Nullable BigDecimal netPaymentDays)
Original property name from the Odata EDM: NetPaymentDays
netPaymentDays
- Standard settlement period (in days).public void setPaymentBlockingReason(@Nullable String paymentBlockingReason)
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.
paymentBlockingReason
- Specifies why a document is blocked for payment.public void setAccountingDocumentType(@Nullable String accountingDocumentType)
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.
accountingDocumentType
- The document type classifies the accounting documents. It is stored in the document header.public void setBPBankAccountInternalID(@Nullable String bPBankAccountInternalID)
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.
bPBankAccountInternalID
- Key you enter in the line item to specify which business partner's bank the system should use.public void setSupplierInvoiceStatus(@Nullable String supplierInvoiceStatus)
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)
supplierInvoiceStatus
- Invoice documents can have the following different statuses:public void setIndirectQuotedExchangeRate(@Nullable BigDecimal indirectQuotedExchangeRate)
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.
indirectQuotedExchangeRate
- This field contains an exchange rate according to the direct quotation method. The exchange rate gives
the price in the "to" currency that you have to pay for a unit (10, 100,...) of "from" currency.public void setDirectQuotedExchangeRate(@Nullable BigDecimal directQuotedExchangeRate)
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.
directQuotedExchangeRate
- This field contains an exchange rate according to the indirect quotation method. The exchange rate
gives the amount of the "from" currency that you get for a unit (10, 100,...) of the "to" currency.public void setStateCentralBankPaymentReason(@Nullable String stateCentralBankPaymentReason)
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.
stateCentralBankPaymentReason
- Germanypublic void setSupplyingCountry(@Nullable String supplyingCountry)
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.
supplyingCountry
- Germanypublic void setPaymentMethod(@Nullable String paymentMethod)
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.
paymentMethod
- The payment method determines how payments are to be made, e.g. by check, bank transfer or bill of
exchange.public void setPaymentMethodSupplement(@Nullable String paymentMethodSupplement)
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.
paymentMethodSupplement
- Characteristic in an open item for the grouping of payments.public void setPaymentReference(@Nullable String paymentReference)
Original property name from the Odata EDM: PaymentReference
For supplier line items, the key that the supplier 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 Denmark:The FIK OCR line is entered using the format
+nn
paymentReference
- The payment reference contains a key for customer line items that is passed on to the customer in the
invoice. The customer should refer to the payment reference when making the payment.public void setInvoiceReference(@Nullable String invoiceReference)
Original property name from the Odata EDM: InvoiceReference
invoiceReference
- Invoice reference: Document number for invoice referencepublic void setInvoiceReferenceFiscalYear(@Nullable String invoiceReferenceFiscalYear)
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.
invoiceReferenceFiscalYear
- For line items which are related to another line item, this field contains the fiscal year of the
related document.public void setFixedCashDiscount(@Nullable String fixedCashDiscount)
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.
fixedCashDiscount
- Indicator that the first or second cash discount term can be taken advantage of irrespective of
whether the corresponding period has elapsed or not.public void setUnplannedDeliveryCostTaxCode(@Nullable String unplannedDeliveryCostTaxCode)
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.
unplannedDeliveryCostTaxCode
- The tax code stands for a tax category which must be taken into consideration when making a tax return
to the tax authorities.public void setUnplndDelivCostTaxJurisdiction(@Nullable String unplndDelivCostTaxJurisdiction)
Original property name from the Odata EDM: UnplndDelivCostTaxJurisdiction
unplndDelivCostTaxJurisdiction
- The tax jurisdiction is used for determining the tax rates in the USA. It defines to which tax
authorities you must pay your taxes. It is always the city to which the goods are supplied.public void setUnplndDeliveryCostTaxCountry(@Nullable String unplndDeliveryCostTaxCountry)
Original property name from the Odata EDM: UnplndDeliveryCostTaxCountry
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.
unplndDeliveryCostTaxCountry
- Country where taxes are calculated and reported.public void setAssignmentReference(@Nullable String assignmentReference)
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.
assignmentReference
- The assignment number is an additional information reference field in the line item.public void setSupplierPostingLineItemText(@Nullable String supplierPostingLineItemText)
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.
supplierPostingLineItemText
- Contains an explanatory text on the line item.public void setTaxIsCalculatedAutomatically(@Nullable Boolean taxIsCalculatedAutomatically)
Original property name from the Odata EDM: TaxIsCalculatedAutomatically
taxIsCalculatedAutomatically
- If you select this field, the system calculates the taxes automatically during simulation or posting.public void setBusinessPlace(@Nullable String businessPlace)
Original property name from the Odata EDM: BusinessPlace
businessPlace
- Specifies the business place.public void setBusinessSectionCode(@Nullable String businessSectionCode)
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.
businessSectionCode
- Specifies the section code.public void setBusinessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
businessArea
- Key that uniquely identifies a business area.public void setSupplierInvoiceIsCreditMemo(@Nullable String supplierInvoiceIsCreditMemo)
Original property name from the Odata EDM: SupplierInvoiceIsCreditMemo
supplierInvoiceIsCreditMemo
- Single-Character Flagpublic void setPaytSlipWthRefSubscriber(@Nullable String paytSlipWthRefSubscriber)
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.
paytSlipWthRefSubscriber
- ISR stands for inpayment slip with reference number, a special payment procedure of the Swiss Postal
Service. The field is therefore only relevant in Switzerland.public void setPaytSlipWthRefCheckDigit(@Nullable String paytSlipWthRefCheckDigit)
Original property name from the Odata EDM: PaytSlipWthRefCheckDigit
The rules for forming a check digit are set by the Swiss PTT.
paytSlipWthRefCheckDigit
- For long POR numbers (9 characters), this field contains the check digit for the amount and for short
POR numbers (5 characters), it contains the check digit for the amount, subscriber number and
reference number.public void setPaytSlipWthRefReference(@Nullable String paytSlipWthRefReference)
Original property name from the Odata EDM: PaytSlipWthRefReference
paytSlipWthRefReference
- This field is used as a reference to the vendor invoice in payment transactions. The field is only
used 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.public void setTaxDeterminationDate(@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.
taxDeterminationDate
- This field is significant when determining tax rates.public void setTaxReportingDate(@Nullable LocalDateTime taxReportingDate)
Original property name from the Odata EDM: TaxReportingDate
The tax reporting date can be identical to the posting date or the document date; you also can define your own rules to determine the date.Tax ReportingThe tax reporting date is used in tax reporting primarily as a selection criterion, in addition to the posting date or document date.The tax reporting date is contained as a selection criterion in the logical database BRF.The field is available by default in the selection screens of several programs (for example, RFUMSV00, RFUMSV10, RDASLM00 , RFASLD02, RFASLD20). In the other report programs based on logical database BRF, the selection screens do not contain the field by default, but you can choose it from the custom selections.Exchange Rate Determination in Currency Translation of the Tax AmountYou also can use the tax reporting date to determine the exchange rate when performing currency translation of the tax amount. To do this, in Customizing for Tax on Sales/Purchases under Change Foreign Currency Translation choose the option Determine exchange rate based on tax reporting date. Even if you have selected this option, you can change the reporting date in the document for reporting purposes at a later date. The tax amount is not recalculated again if you do this.More InformationFor more information, see SAP Note 1232484 and the related notes.The tax reporting date is a field in the document header (table BKPF) and therefore applies to the entire document.To be able to use the field in documents, you need to activate the function Inventory-managing Customizing of Global Parameters for the company code. To do this, go to Enter Global Parameters and set Tax Reporting Date Active.If you have not selected Tax Reporting Date Active or the document is not tax relevant (does not contain a tax code), the system stores the tax reporting date with an initialized value.When entering documents, you can enter the tax reporting date in the dialog box for taxes. The BAdI Define and Check Tax Reporting Date (VATDATE_VALUES) proposes a value for this date. In the standard implementation, this is the posting date or, alternatively, the document date. You can change this date in the transaction for changing documents (FB02). But first you need to allow for the date to be changed in Customizing for Document Change Rules under Document Change Rules, Document Header. You can use the BAdI VATDATE_VALUES to verify the changes to the tax reporting date in the document.You can use the BAdI Determine Exchange Rate for Tax Items (BADI_TAX_EXCHANGE_RATE) to determine which exchange rate is relevant for tax line items in documents.
taxReportingDate
- Date on which the tax on sales and purchases is due, or the date on which that tax must be reported to
the tax authority.public void setInvoiceReceiptDate(@Nullable LocalDateTime invoiceReceiptDate)
Original property name from the Odata EDM: InvoiceReceiptDate
invoiceReceiptDate
- Specifies the date on which the invoice was received.public void setDeliveryOfGoodsReportingCntry(@Nullable String deliveryOfGoodsReportingCntry)
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.
deliveryOfGoodsReportingCntry
- Country in which the customer acquired a VAT registration number (VAT reg.no.). Every VAT reg.no. of
the customer must be stored under the corresponding reporting country in the master record.public void setSupplierVATRegistration(@Nullable String supplierVATRegistration)
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.
supplierVATRegistration
- VAT registration number (VAT reg.no.) of the customer, vendor or your company code.public void setIsEUTriangularDeal(@Nullable Boolean isEUTriangularDeal)
Original property name from the Odata EDM: IsEUTriangularDeal
isEUTriangularDeal
- If you select this field, the system includes this transaction in the EC sales list under the
triangular deal section.public void setSuplrInvcDebitCrdtCodeDelivery(@Nullable String suplrInvcDebitCrdtCodeDelivery)
Original property name from the Odata EDM: SuplrInvcDebitCrdtCodeDelivery
suplrInvcDebitCrdtCodeDelivery
- Posting logic for delivery items (invoice/credit memo)public void setSuplrInvcDebitCrdtCodeReturns(@Nullable String suplrInvcDebitCrdtCodeReturns)
Original property name from the Odata EDM: SuplrInvcDebitCrdtCodeReturns
suplrInvcDebitCrdtCodeReturns
- Posting logic for returns items (invoice/credit memo)public void setSupplierInvoiceOrigin(@Nullable String supplierInvoiceOrigin)
Original property name from the Odata EDM: SupplierInvoiceOrigin
supplierInvoiceOrigin
- Specifies the way that an invoice was created in Logistics Invoice Verification.public void setReverseDocument(@Nullable String reverseDocument)
Original property name from the Odata EDM: ReverseDocument
reverseDocument
- Number of the invoice document that reverses the invoice document displayed.public void setReverseDocumentFiscalYear(@Nullable String reverseDocumentFiscalYear)
Original property name from the Odata EDM: ReverseDocumentFiscalYear
reverseDocumentFiscalYear
- Fiscal year in which the document in the Reversed by field was posted.public void setIsReversal(@Nullable Boolean isReversal)
Original property name from the Odata EDM: IsReversal
isReversal
- Is Reversalpublic void setIsReversed(@Nullable Boolean isReversed)
Original property name from the Odata EDM: IsReversed
isReversed
- Is Reversedprotected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<SupplierInvoice>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<SupplierInvoice>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SupplierInvoice>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SupplierInvoice>
@Nonnull public static <T> SupplierInvoiceField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> SupplierInvoiceField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<SupplierInvoice>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<SupplierInvoice>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<SupplierInvoice>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
VdmEntity
getDefaultServicePath
in class VdmEntity<SupplierInvoice>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SupplierInvoice>
@Nonnull public List<SuplrInvcItemPurOrdRef> fetchSuplrInvcItemPurOrdRef() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<SuplrInvcItemPurOrdRef> getSuplrInvcItemPurOrdRefOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SuplrInvcItemPurOrdRef of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SuplrInvcItemPurOrdRef>> getSuplrInvcItemPurOrdRefIfPresent()
If the navigation property for an entity SupplierInvoice has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setSuplrInvcItemPurOrdRef(@Nonnull List<SuplrInvcItemPurOrdRef> value)
If the navigation property to_SuplrInvcItemPurOrdRef of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of SuplrInvcItemPurOrdRef entities.public void addSuplrInvcItemPurOrdRef(SuplrInvcItemPurOrdRef... entity)
If the navigation property to_SuplrInvcItemPurOrdRef of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of SuplrInvcItemPurOrdRef entities.@Nonnull public List<SupplierInvoiceItemGLAcct> fetchSupplierInvoiceItemGLAcct() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<SupplierInvoiceItemGLAcct> getSupplierInvoiceItemGLAcctOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SupplierInvoiceItemGLAcct of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SupplierInvoiceItemGLAcct>> getSupplierInvoiceItemGLAcctIfPresent()
If the navigation property for an entity SupplierInvoice has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with
result state empty
is returned.public void setSupplierInvoiceItemGLAcct(@Nonnull List<SupplierInvoiceItemGLAcct> value)
If the navigation property to_SupplierInvoiceItemGLAcct of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of SupplierInvoiceItemGLAcct entities.public void addSupplierInvoiceItemGLAcct(SupplierInvoiceItemGLAcct... entity)
If the navigation property to_SupplierInvoiceItemGLAcct of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of SupplierInvoiceItemGLAcct entities.@Nonnull public List<SupplierInvoiceTax> fetchSupplierInvoiceTax() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<SupplierInvoiceTax> getSupplierInvoiceTaxOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SupplierInvoiceTax of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SupplierInvoiceTax>> getSupplierInvoiceTaxIfPresent()
If the navigation property for an entity SupplierInvoice has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setSupplierInvoiceTax(@Nonnull List<SupplierInvoiceTax> value)
If the navigation property to_SupplierInvoiceTax of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of SupplierInvoiceTax entities.public void addSupplierInvoiceTax(SupplierInvoiceTax... entity)
If the navigation property to_SupplierInvoiceTax of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of SupplierInvoiceTax entities.@Nonnull public List<SuplrInvcHeaderWhldgTax> fetchSupplierInvoiceWhldgTax() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<SuplrInvcHeaderWhldgTax> getSupplierInvoiceWhldgTaxOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SupplierInvoiceWhldgTax of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<SuplrInvcHeaderWhldgTax>> getSupplierInvoiceWhldgTaxIfPresent()
If the navigation property for an entity SupplierInvoice has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with
result state empty
is returned.public void setSupplierInvoiceWhldgTax(@Nonnull List<SuplrInvcHeaderWhldgTax> value)
If the navigation property to_SupplierInvoiceWhldgTax of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of SuplrInvcHeaderWhldgTax entities.public void addSupplierInvoiceWhldgTax(SuplrInvcHeaderWhldgTax... entity)
If the navigation property to_SupplierInvoiceWhldgTax of a queried SupplierInvoice is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of SuplrInvcHeaderWhldgTax entities.@Nonnull public static SupplierInvoice.SupplierInvoiceBuilder builder()
@Nullable public String getSupplierInvoice()
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.
@Nullable public String getFiscalYear()
Original property name from the Odata EDM: FiscalYear
@Nullable public String getCompanyCode()
Original property name from the Odata EDM: CompanyCode
@Nullable public LocalDateTime getDocumentDate()
Original property name from the Odata EDM: DocumentDate
@Nullable public LocalDateTime getPostingDate()
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).
@Nullable public String getSupplierInvoiceIDByInvcgParty()
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 "*".
@Nullable public String getInvoicingParty()
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.
@Nullable public String getDocumentCurrency()
Original property name from the Odata EDM: DocumentCurrency
@Nullable public BigDecimal getInvoiceGrossAmount()
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
@Nullable public BigDecimal getUnplannedDeliveryCost()
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.
@Nullable public String getDocumentHeaderText()
Original property name from the Odata EDM: DocumentHeaderText
@Nullable public BigDecimal getManualCashDiscount()
Original property name from the Odata EDM: ManualCashDiscount
@Nullable public String getPaymentTerms()
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.
@Nullable public LocalDateTime getDueCalculationBaseDate()
Original property name from the Odata EDM: DueCalculationBaseDate
@Nullable public BigDecimal getCashDiscount1Percent()
Original property name from the Odata EDM: CashDiscount1Percent
@Nullable public BigDecimal getCashDiscount1Days()
Original property name from the Odata EDM: CashDiscount1Days
@Nullable public BigDecimal getCashDiscount2Percent()
Original property name from the Odata EDM: CashDiscount2Percent
@Nullable public BigDecimal getCashDiscount2Days()
Original property name from the Odata EDM: CashDiscount2Days
@Nullable public BigDecimal getNetPaymentDays()
Original property name from the Odata EDM: NetPaymentDays
@Nullable public String getPaymentBlockingReason()
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.
@Nullable public String getAccountingDocumentType()
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.
@Nullable public String getBPBankAccountInternalID()
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.
@Nullable public String getSupplierInvoiceStatus()
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)
@Nullable public BigDecimal getIndirectQuotedExchangeRate()
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.
@Nullable public BigDecimal getDirectQuotedExchangeRate()
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.
@Nullable public String getStateCentralBankPaymentReason()
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.
@Nullable public String getSupplyingCountry()
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.
@Nullable public String getPaymentMethod()
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.
@Nullable public String getPaymentMethodSupplement()
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.
@Nullable public String getPaymentReference()
Original property name from the Odata EDM: PaymentReference
For supplier line items, the key that the supplier 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 Denmark:The FIK OCR line is entered using the format
+nn
@Nullable public String getInvoiceReference()
Original property name from the Odata EDM: InvoiceReference
@Nullable public String getInvoiceReferenceFiscalYear()
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.
@Nullable public String getFixedCashDiscount()
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.
@Nullable public String getUnplannedDeliveryCostTaxCode()
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.
@Nullable public String getUnplndDelivCostTaxJurisdiction()
Original property name from the Odata EDM: UnplndDelivCostTaxJurisdiction
@Nullable public String getUnplndDeliveryCostTaxCountry()
Original property name from the Odata EDM: UnplndDeliveryCostTaxCountry
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.
@Nullable public String getAssignmentReference()
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.
@Nullable public String getSupplierPostingLineItemText()
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.
@Nullable public Boolean getTaxIsCalculatedAutomatically()
Original property name from the Odata EDM: TaxIsCalculatedAutomatically
@Nullable public String getBusinessPlace()
Original property name from the Odata EDM: BusinessPlace
@Nullable public String getBusinessSectionCode()
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.
@Nullable public String getBusinessArea()
Original property name from the Odata EDM: BusinessArea
@Nullable public String getSupplierInvoiceIsCreditMemo()
Original property name from the Odata EDM: SupplierInvoiceIsCreditMemo
@Nullable public String getPaytSlipWthRefSubscriber()
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.
@Nullable public String getPaytSlipWthRefCheckDigit()
Original property name from the Odata EDM: PaytSlipWthRefCheckDigit
The rules for forming a check digit are set by the Swiss PTT.
@Nullable public String getPaytSlipWthRefReference()
Original property name from the Odata EDM: PaytSlipWthRefReference
@Nullable public LocalDateTime getTaxDeterminationDate()
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.
@Nullable public LocalDateTime getTaxReportingDate()
Original property name from the Odata EDM: TaxReportingDate
The tax reporting date can be identical to the posting date or the document date; you also can define your own rules to determine the date.Tax ReportingThe tax reporting date is used in tax reporting primarily as a selection criterion, in addition to the posting date or document date.The tax reporting date is contained as a selection criterion in the logical database BRF.The field is available by default in the selection screens of several programs (for example, RFUMSV00, RFUMSV10, RDASLM00 , RFASLD02, RFASLD20). In the other report programs based on logical database BRF, the selection screens do not contain the field by default, but you can choose it from the custom selections.Exchange Rate Determination in Currency Translation of the Tax AmountYou also can use the tax reporting date to determine the exchange rate when performing currency translation of the tax amount. To do this, in Customizing for Tax on Sales/Purchases under Change Foreign Currency Translation choose the option Determine exchange rate based on tax reporting date. Even if you have selected this option, you can change the reporting date in the document for reporting purposes at a later date. The tax amount is not recalculated again if you do this.More InformationFor more information, see SAP Note 1232484 and the related notes.The tax reporting date is a field in the document header (table BKPF) and therefore applies to the entire document.To be able to use the field in documents, you need to activate the function Inventory-managing Customizing of Global Parameters for the company code. To do this, go to Enter Global Parameters and set Tax Reporting Date Active.If you have not selected Tax Reporting Date Active or the document is not tax relevant (does not contain a tax code), the system stores the tax reporting date with an initialized value.When entering documents, you can enter the tax reporting date in the dialog box for taxes. The BAdI Define and Check Tax Reporting Date (VATDATE_VALUES) proposes a value for this date. In the standard implementation, this is the posting date or, alternatively, the document date. You can change this date in the transaction for changing documents (FB02). But first you need to allow for the date to be changed in Customizing for Document Change Rules under Document Change Rules, Document Header. You can use the BAdI VATDATE_VALUES to verify the changes to the tax reporting date in the document.You can use the BAdI Determine Exchange Rate for Tax Items (BADI_TAX_EXCHANGE_RATE) to determine which exchange rate is relevant for tax line items in documents.
@Nullable public LocalDateTime getInvoiceReceiptDate()
Original property name from the Odata EDM: InvoiceReceiptDate
@Nullable public String getDeliveryOfGoodsReportingCntry()
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.
@Nullable public String getSupplierVATRegistration()
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.
@Nullable public Boolean getIsEUTriangularDeal()
Original property name from the Odata EDM: IsEUTriangularDeal
@Nullable public String getSuplrInvcDebitCrdtCodeDelivery()
Original property name from the Odata EDM: SuplrInvcDebitCrdtCodeDelivery
@Nullable public String getSuplrInvcDebitCrdtCodeReturns()
Original property name from the Odata EDM: SuplrInvcDebitCrdtCodeReturns
@Nullable public String getSupplierInvoiceOrigin()
Original property name from the Odata EDM: SupplierInvoiceOrigin
@Nullable public String getReverseDocument()
Original property name from the Odata EDM: ReverseDocument
@Nullable public String getReverseDocumentFiscalYear()
Original property name from the Odata EDM: ReverseDocumentFiscalYear
@Nullable public Boolean getIsReversal()
Original property name from the Odata EDM: IsReversal
@Nullable public Boolean getIsReversed()
Original property name from the Odata EDM: IsReversed
@Nonnull public String toString()
toString
in class VdmObject<SupplierInvoice>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<SupplierInvoice>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<SupplierInvoice>
public int hashCode()
hashCode
in class VdmObject<SupplierInvoice>
Copyright © 2021 SAP SE. All rights reserved.