| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
This is the list of available FlowAP templates. 3 default templates come with FlowAP upon installation.
| Note |
|---|
You must not edit the Default FlowAP Templates. Any changes made to the default template will be overridden during new version releases of FlowAP. To use a customized version of the FlowAP template, save a copy of the Default FlowAP Template. Apply your own lookup criteria and XML mapping to the new FlowAP Template; and assign it to the relevant Staria FlowAP Subsidiary Setup. |
Assigning FlowAP Templates to the FlowAP Subsidiary setup
Navigate to FlowAP > FlowAP Configuration > Staria FlowAP Subsidiary Setup.
Select the subsidiary setup and click edit.
Navigate to the Conversion subtab and find the FlowAP template field.
Select the FlowAP Template.
Click Save.
Parts of the FlowAP Template
...
This mapping notation is used for the majority of the transaction fields. This maps one (1) NetSuite field to (1) XML element.
Example:
| Code Block | ||
|---|---|---|
| ||
{
"nsfieldid1": {"xpath": ["/cac:parentxmlelement/cbc:childxmlelement1"]},
"nsfieldid2": {"xpath": ["/cac:parentxmlelement/cbc:childxmlelement2"]}
} |
...
NetSuite field ID - The field ID of the target field of the NetSuite record or transaction
XML element path - The XML element together with its parent element. The parent element is not needed if the element is a direct child of the <Invoice> element.
Multiple Source Mapping Notation
...
Transaction Expense/Item Sublist
NetSuite Electronic Bank Payment Vendor Entity Bank Details
Allowance Charge
Example:
| Code Block | ||
|---|---|---|
| ||
{
"nssublistname": {"listpath": ["/cac:parentxmlelement","fields" : [{
"nsfieldid1": {"xpath": ["/cac:parentxmlelement/cbc:childxmlelement1"]},
"nsfieldid2": {"xpath": ["/cac:parentxmlelement/cbc:childxmlelement2"]},
} |
For all fields in the sublist:
If the xpath starts with a period (.) - this means that the absolute path to get the XML value is
Invoice/<listpath>/<xpath>Otherwise, the absolute path starts directly from the
Invoiceelement similar to the body fields:Invoice/<XPath>
Example:
| Code Block | ||
|---|---|---|
| ||
"item" : {
"listpath" : "/cac:InvoiceLine",
"fields" : [
{
"taxpercent": {
"xpath" : ["./cac:Item/cac:ClassifiedTaxCategory/cbc:Percent",
"/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:Percent"]
}
}
]
} |
Fields with Special Validation
NetSuite expense lines created when conversion is unable to identify a NetSuite item for the invoice line. | The memo field of the expense line will have the value: <taxpercent> | <vendorcode> - <itemname> | |||||||||||
↪️ custom mapping for the expense line memo | The default mapping for the following fields are as follows:
The value of the memo field can be modified by changing the mapping of each of the contatenated values for taxpercent,vendorcode and itemname. For example, they want item name to be either the Name/ID or the Description in the XML. Replace the XPath assigned to itemname.
|
"vendorvat": {"xpath": ["/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID=\"VAT\"]"]},
...
Use Case | Setup Options | Related Articles |
|---|---|---|
Allow transaction creation to proceed even if the conversion was unable to find a matching NetSuite item for the vendor bill lines. The conversion will post unidentified items as expense lines. | FlowAP Subsidiary Setup > CREATE UNIDENTIFIED ITEMS AS EXPENSE | |
Use NetSuite expense items instead of expense lines | FlowAP Subsidiary Setup > USE EXPENSE ITEMS INSTEAD OF ACCOUNTS FOR EXPENSE LINES | |
Ignore XML line level data and allow NetSuite to copy the line level information from the related purchase order in NetSuite. The total payable amount of the bill will always be equal to the XML. The user responsible for the bill is expected to review the line details of the bill and make the necessary data entry to correct it for the total payable amount. | FlowAP Subsidiary Setup > INHERIT PO LINES FlowAP Subsidiary Setup > INHERIT PO LINES: DEFAULT TO 0 QUANTITY AND AMOUNT | |
Ignore the XML line level data and save a single transaction line in NetSuite transaction. | FlowAP Subsidiary Setup > POST SINGLE BILL LINE: USE PAYABLE AMOUNT (NO TAX) | |
Vendor Preference: [STA] No Direct Bill | Will not allow a well formed XML to create a stand-alone bill (Direct bill) if the PO Reference is empty. | |
Vendor Preference: [STA] No Direct Credit | Will not allow a well formed XML to create a stand-alone bill credit (Direct Credit) if the Bill Reference is empty. | |
| ||
| ||
| ||
|
...
Fixed an issue where a duplicate number error is flagged when using the same document number between a vendor bill and a vendor credit.
Fixed an issue where vendor creation fails if the XML does not contain or has an invalid payment term.
The following tax code lookup options now support 0% tax rates:
Vendor-subsidiary sublist tax code field.
Item tax schedule
Fixed an issue where the final tax code lookup hierarchy entry is using a Default tax code for the vendor’s billing country instead of the transaction’s subsidiary country.
Expected errors
If multiple or no vendors are found then an audit trail will be created instead of getting an unexpected error.
TO DO:
Correlate completeness of this document with Krizia’s requests for additional documents in the Jira comments.
Jira Legacy server System Jira serverId 016d54d6-529c-3a48-9649-201c3dee7635 key SAPROD-7454
Limitations
| Warning |
|---|
|