The following data fields are exported by
Kofax AP Agility
and passed to the
S/4HANA Cloud ES
ERP via the connector. They are exported by OData Post Request in JSON format.
Header level
SupplierInvoice (Invoice ID)
CompanyCode (Business Unit ID)
FiscalYear
PostingDate
DocumentDate (Invoice date)
SupplierInvoiceIDByInvcgParty
InvoicingParty (Vendor ID)
DocumentHeaderText (Invalid Reason)
InvoiceGrossAmount (invoice amount)
ManualCashDiscount (discount amount)
PaymentTerms
UnplannedDeliveryCost (Freight)
DocumentCurrency (Currency)
DueCalculationBaseDate
CashDiscount1Percent
CashDiscount1Day
CashDiscount2Percent
CashDiscount2Days
NetPaymentDays
PaymentBlockingReason
AccountingDocumentType (Document Type: Credit or not)
BPBankAccountInternalID
SupplierInvoiceStatus
Planned for background verification (background invoice verification)
Deleted (background and online invoice verification)
Contains errors (background invoice verification)
SupplierInvoiceStatus (continued)
Correct (posted, not complete) (background invoice verification)
Posted (background and online invoice verification)
Parked (online invoice verification)
Parked complete (online invoice verification)
Held parked (online invoice verification)
Held entered (online invoice verification)
Parked released (online invoice verification
IndirectQuotedExchangeRate
DirectQuotedExchangeRate
StateCentralBankPaymentReason
SupplyingCountry
PaymentMethod
PaymentMethodSupplement
PaymentReference
InvoiceReference
InvoiceReferenceFiscalYear
FixedCashDiscount
UnplannedDeliveryCostTaxCode
UnplndDelivCostTaxJurisdiction
UnplndDeliveryCostTaxCountry
AssignementReference
SupplierPostingLineItemText
TaxIsCalculatedAutomatically
BusinessPlace
BusinessSectionCode
BusinessArea
SupplierInvoiceIsCreditMemo
PaytSlipWthRefSubscriber
PaytSlipWthRefCheckDigit
PaytSlipWthRefReference
TaxDeterminationDate
TaxReportingDate
InvoiceReceiptDate (Scan date)
DeliveryOfGoodsReportingCntry
SupplierVATRegistration (Vendor VATRegNo)
IsEUTriangularDeal
SuplrInvcDebitCrdtCodeDelivery
SuplrInvcDebitCrdtCodeReturns
SupplierInvoiceOrigin
ReverseDocument
ReverseDocumentFiscalYear
IsReversal
IsReversed
to_SuplrInvcItemPurOrdRef (PO lines)
to_SupplierInvoiceItemGLAcct (GL accounts)
to_SupplierInvoiceTax (Tax set)
to_SupplierInvoiceWhldgTax (Withholding Tax set)
Line-item level, PO lines
SupplierInvoice
Fiscalyear
SupplierInvoiceItem
PurchaseOrder
PurchaseOrderItem
Plant
ReferenceDocument
ReferenceDocumentItem
IsSubsequentDebitCredit
TaxCode
TaxJurisdiction
DocumentCurrenct
SupplierInvoiceItemAmount
PurchaseOrderQuantityUnit
QuantityInPurchaseOrderUnit
PurchaseOrderPriceUnit
QtyInPurchaseOrderPriceUnit
SuplrInvcDeliveryCostCndnType
SuplrInvcDeliveryCostCndnStep
SuplrInvcDeliveryCostCndnCount
SupplierInvoiceItemText
FreightSupplier
IsNotCashDiscountLiable
PurchasingDocumentItemCategory
ProductType
ServiceEntrySheet
ServiceEntrySheetItem
TaxCountry
to_SupplierInvoiceItmAcctAssgmt
Line-item level, GL lines
WorkItem
DebitCreditCode
TaxJurisdiction
SupplierInvoiceItemText
AssignmentReference
IsNotCashDiscountLiable
InternalOrder
PersonnelNumber
ProjectNetwork
CommitmentItem
FundsCenter
TaxBaseAmountInTransCrcy
Fund
GrantID
QuantityUnit
Quantity
NetworkActivity
PartnerBusinessArea
TaxCode
DocumentCurrency
SupplierInvoice
FiscalYear
SupplierInvoiceItem
CompanyCode
CostCenter
ControllingArea
BusinessArea
SupplierInvoiceItemAmount
ProfitCenter
GLAccount
SalesOrder
SalesOrderItem
CostObject
CostCtrActivityType
BusinessProcess
WBSElement
FunctionalArea
TaxCountry
Search results
Search tips
The search returns topics that contain terms you enter. If you type more than one term, an OR is assumed, which returns topics where any of the terms are found. Enclose your search terms in quotes for exact-phrase matching.
The search also uses fuzzy matching to account for partial words (such as install and installs). The results appear in order of relevance, based on how many search terms occur per topic. Exact matches are highlighted.
To refine the search, you can use the following operators:
Type + in front of words that must be included in the search or - in front of words to exclude. (Example: user +shortcut –group finds shortcut and user shortcut, but not group or user group.)
Use * as a wildcard for missing characters. The wildcard can be used anywhere in a search term. (Example: inst* finds installation and instructions.)
Type title: at the beginning of the search phrase to look only for topic titles. (Example: title:configuration finds the topic titled “Changing the software configuration.”)
For multi-term searches, you can specify a priority for terms in your search. Follow the term with ^ and a positive number that indicates the weight given that term. A higher number indicates more weight. (Example: shortcut^10 group gives shortcut 10 times the weight as group.)
To use fuzzy searching to account for misspellings, follow the term with ~ and a positive number for the number of corrections to be made. (Example: port~1 matches fort, post, or potr, and other instances where one correction leads to a match.)
Note that operators cannot be used as search terms: + - * : ~ ^ ' "
