| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Field name | Description |
Primary Information | |
Name | Enter a name for your FlowAP Template. |
Lookup Criteria | |
Vendor Lookup Criteria | JSON objects that would be used as criteria for searching the Vendor for the FlowAP Document. You can enter a maximum of 15 criteria and a minimum of 1. |
Item Lookup Criteria | JSON objects that would be used as criteria for searching the Item for the FlowAP Document. You can enter a maximum of 5 criteria and a minimum of 1. |
Mapping Templates | |
Transaction Mapping | JSON object which defines the mapping for the Transaction Header and Lines. |
Vendor Mapping | JSON object which defines the mapping for the new vendor creation. |
...
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. |
...
Select the FlowAP Template.
Click Save.
Parts of the FlowAP Template
Lookup Criteria
Transaction Mapping
FlowAP template notation
The FlowAP template is based on JSON syntax. The mapping templates are written inside curly braces.
...
The following setup options influence or override the behavior of the mapped elements during conversion.
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) | |
| ||
| ||
| ||
|
...