| 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. |
...
Example:
| Code Block | ||
|---|---|---|
| ||
{
"nsfieldid1": {
"xpath": ["/cac:parentxmlelement/cbc:childxmlelement1"]
},
"nsfieldid2": {
"xpath": ["/cac:parentxmlelement/cbc:childxmlelement2"]
}
} |
Each field mapping contains the name/value pairs. The name/value pairs consist of:
...
| Code Block | ||
|---|---|---|
| ||
"taxpercent": {
"xpath" : [
"./cac:Item/cac:ClassifiedTaxCategory/cbc:Percent",
"/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:Percent"]
}}]}, |
In this example, the taxpercent field is mapped to the line-level tax percent and the transaction header-level tax percent.
...
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:
...
Example:
| Code Block | ||
|---|---|---|
| ||
{ "item" : { "listpath" : "/cac:InvoiceLine", "fields" : [ { "taxpercent": { "xpath" : ["./cac:Item/cac:ClassifiedTaxCategory/cbc:Percent", "/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:Percent"] } } ] } } |
For taxpercent, there are 2 xpaths which means that there’s a hierarchy in retrieving the value for taxpercent
...
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) | Understanding the [STA] POST SINGLE BILL LINE preference guide
| ||
Do not allow a well-formed XML to create a stand-alone bill (Direct bill) if the PO Reference is empty. | Staria FlowAP Subsidiary Setup > WHEN BILL NOT FOUND | |||
Do not allow a well-formed XML to create a stand-alone bill credit (Direct Credit) if the Bill Reference is empty. | Staria FlowAP Subsidiary Setup > WHEN PO# NOT FOUND | |||
Do not allow stand alone transactions for a specific vendor. | Configure vendor preferences in the vendor record.
Configure the Vendor-specific preferences saved search in the FlowAP Subsidiary Setup > VENDOR-SPECIFIC PREFERENCES | |||
Define tax codes for each tax rate/percent parsed from the XML during conversion. | FlowAP Subsidiary Setup > TAX CODE TABLE |
...