Oracle Financials Cloud: Data templates
When you configure the Oracle Financials Cloud target system service, you can use data templates to specify values for distribution combinations, header fields, line-item fields and payables descriptive flexfields for header and line-item fields.
- Distribution combination template specifies the data from Tungsten AP Essentials that you want to use for the distribution combinations in Oracle Financials Cloud.
- Header field mapping specifies the Tungsten AP Essentials data to use when mapping to payables header fields in Oracle Financials Cloud.
- Line-item field mapping specifies the Tungsten AP Essentials data to use when mapping to item fields in Oracle Financials Cloud.
- Descriptive flexfield template specifies the Tungsten AP Essentials data to use when mapping to payables descriptive flexfields in Oracle Financials Cloud.
- Line-item descriptive flexfield template specifies the Tungsten AP Essentials data to use when mapping to line-item descriptive flexfields in Oracle Financials Cloud.
To utilize flexfield templates, you must add custom fields(DFFContext and/or LIT_DFFContext) to a document type. During verification, the values you specify in these fields provide context to the flexfield template. The flexfield templates are not used unless you specify a field value that matches a context code in the template. Read more about context fields.
You specify the data templates using plain-text constants and variables enclosed in percent marks.
- Constants - fixed values that you specify as text.
- Variables - dynamic values that are determined by invoice data or system data. Variables are enclosed in percent characters (%).
To specify a variable for an invoice field, enclose the Type name of the field in percent characters (%).
A variable can also be preceded by:
- # - to indicate that it is a system variable.
- @ - to indicate that it is a history variable.
- $ - to indicate that it is a meta-data variable.
Example
Customer: $WebEye.CustomerID Document created: %@date0{yyyy-MM-dd}% Buyer: %#buyer.Name%
The default value for the Distribution combination templatesetting is:
%$BuyerExternalId%-%AccountCode%
Field mapping
By default, Tungsten AP Essentials maps many fields to payables fields in Oracle (See defaults here). However, if you want to override a default mapping or map data to a field that is not mapped by default, you can specify a custom mapping. Use the target system settings described at the top of this topic to specify custom field mapping.
You use data templates to specify a custom mapping using this format:
OracleField="DataTemplate"
...where OracleField is the name of a payables field as designated by the Oracle API, and DataTemplate is a data template described in this topic. Separate multiple field mappings using semicolons.
Example
InvoiceNumber="000%InvoiceNumber%"
In the example above, the invoice number field in Oracle (InvoiceNumber) is mapped to the invoice number field in Tungsten AP Essentials (%InvoiceNumber%), which is preceded by three zeros. Therefore, if you process an invoice with invoice number 123456, the value of the invoice number field in Oracle would be set to:
000123456
System variables
You can specify system variables to obtain the values of system variables in Tungsten AP Essentials.
- #Appendices
- #CreditInvoice
- #BatchPrefix
- #buyer.Type
- #buyer.Name
- #buyer.Id
- #buyer.ExternalId
- #buyer.Description
- #buyer.TaxRegistrationNumber
- #buyer.OrganizationNumber
- #buyer.Street
- #buyer.PostalCode
- #buyer.City
- #buyer.CountryName
- #buyer.PaymentTerm
- #buyer.PaymentMethod
- #buyer.CurrencyCode
- #buyer.BankAccounts
- #Currency
- #DateTime
- #Description
- #DocumentTypeSystemName
- #ImageFile2
- #NumberOfPagesFrontAndBack
- #NumberOfInvoicePages
- #NumberOfInvoicePagesFrontAndBack
- #NumberOfAppendixPages
- #NumberOfAppendixPagesFrontAndBack
- #Pages
- #Permalink
- #ProfileName
- #EndorserNumber
- #Supplier
- #Supplier.Description
- #supplier.Type
- #supplier.Name
- #supplier.Id
- #supplier.ExternalId
- #supplier.TaxRegistrationNumber
- #supplier.OrganizationNumber
- #supplier.Street
- #supplier.PostalCode
- #supplier.City
- #supplier.CountryName
- #supplier.PaymentTerm
- #supplier.PaymentMethod
- #supplier.CurrencyCode
- #supplier.BankAccounts
History variables
You can specify history variables to obtain the user or the date and time of a specific process. You construct a history variable using one of these formats:
- @UserX
- @DateX
The default date format returned by the date variable is YYY-MM-ddTHH:mm:ss.FFFFFFFZ. For example: 2021-02-28T14:46:21.1265774Z.
| Process status | Numerical code |
|---|---|
| DocumentCreated | 0 |
| DocumentExtractionInProgress | 30 |
| DocumentExtractionSucceeded | 40 |
| DocumentPendingManualVerification | 45 |
| DocumentPendingCorrection | 46 |
| DocumentCorrectionFlowStarting | 47 |
| DocumentCorrectionFlowInProgress | 48 |
| DocumentCorrectionFlowDone | 49 |
| DocumentRejectedDuringVerification | 50 |
| DocumentRequestForInformationDuringVerification | 55 |
| DocumentManuallyVerified | 60 |
| DocumentPendingRegistration | 61 |
| DocumentRegistrationInProgress | 62 |
| DocumentRegistrationSucceeded | 63 |
| DocumentRegistrationFailed | 64 |
| DocumentPendingApproval | 65 |
| DocumentApprovalStarting | 79 |
| DocumentApprovalInProgress | 66 |
| DocumentApproved | 67 |
| DocumentApprovalSucceeded | 68 |
| DocumentApprovalRejected | 69 |
| DocumentRequestForInformation | 70 |
| DocumentPendingAllocation | 71 |
| DocumentPendingPost | 74 |
| DocumentPostInProgress | 75 |
| DocumentPostSucceeded | 76 |
| DocumentPostFailed | 77 |
| DocumentAssignedToUser | 78 |
| DocumentPendingBatchRegistration | 80 |
| DocumentPendingBatchPost | 81 |
| DocumentValidationFailed | 82 |
| DocumentPendingExport | 90 |
| DocumentExportPostponed | 91 |
| DocumentExportInProgress | 95 |
| DocumentExportFailed | 99 |
| DocumentExportSucceeded | 100 |
| DocumentSentToStorage | 200 |
| DocumentCommentAdded | 201 |
| LineItemExtractionUsed | 202 |
| DocumentFailed | 900 |
| DocumentDeleted | 1000 |
Custom date formats
The default date format returned by the date variable is YYY-MM-ddTHH:mm:ss.FFFFFFFZ. For example: 2021-02-28T14:46:21.1265774Z.
If you use the Oracle Financials Cloud integration or the SAP S/4HANA Cloud ES integration, you can control the format of the date variable using standard date and time formats as well as custom formats. You specify the format of your choice by enclosing it in braces after the date variable, like this:
%@date0{yyyy-MM-dd}%
The date variable above would return for example, 2021-02-28.
Meta-data variables
You can specify these variables to obtain additional meta data from Tungsten AP Essentials that is not available in the variables above:
- $WebEye.CustomerID
- $WebEye.BatchID
- $WebEye.OutputImageFormat
- $WebEye.DocumentID
- $ExternalId
- $UploaderUserName
- $OriginalFileName
- $BatchTrackId
- $ReceiveTime
- $DocumentId
- $VerifierUserName