Versions Compared

Version Old Version 13 New Version 14
Changes made by

Lou Dizon

Kiro Franco

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

...

Find the Vendor Lookup Criteria.

Note

You must not edit the Default FlowAP Template.

Any changes made to the default template will be overriden 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.

...

  • Invalid vendor records are not returned by the lookup

    • inactive = T

  • The lookup will perform the serach search for each vendor lookup array element until a vendor is found. The maximum lookup criteria is 7 elements.

  • The search will start from the first element in the array and will stop once a vendor is found.

  • If a vendor is found, the following information will be set on the JSON data:

    • vendorname

    • vendorvat

...

This feature lets FlowAP create a new vendor in the system if one is not found during the conversion’s vendor lookup.

Navigating to the setup

Enable Auto-Created Vendor

  1. Navigate to FlowAP > FlowAP Configuration > Staria FlowAP Subsidiary Setup

  2. View the record related to your subsidiary.

  3. Navigate to the Conversion subtab > Vendor Field Group.

  4. Find the Auto Created Vendor checkbox.

Vendor Mapping Template

  1. Navigate to FlowAP > FlowAP Configuration > Staria FlowAP Subsidiary Setup

  2. View the record related to your subsidiary.

  3. Navigate to the Conversion subtab.

  4. Find the FlowAP Template field and click the hyperlink.

  5. View and Edit the FlowAP Template.

  6. Navigate to the Mapping Templates field group.

  7. Find the vendor mapping field.

Info

Syntax:

  • Each element in the vendor mapping is surrounded by curly braces and is separated by a comma. Each element represents one field being mapped from the XML to a NetSuite field.

    • Example: [{ELEMENT1}, {ELEMENT2}, {ELEMENT3}]

  • Each element of the mapping JSON array contains two (2) parameters.

    • [NetSuite Field ID] - This is the vendor field in NetSuite..

    • xpath - This is the location of the XML element that contains the data to be saved in the target NetSuite field.

...

Enable Cross-Subsidiary Vendor

  1. Navigate to FlowAP > FlowAP Configuration > Staria FlowAP Subsidiary Setup

  2. View the record related to your subsidiary.

  3. Navigate to the Conversion subtab > Vendor Field Group.

  4. Find the Enable Cross-subsidiary vendor multi-select field.

  5. Select one or more subsidiaries that will be included in the lookup.

...

  1. Save the Staria FlowAP Subsidiary Setup.

Understanding the Enabled Cross-Subsidiary Vendor Feature

...

Enable Vendor-Specific Preferences Feature

  1. Navigate to FlowAP > FlowAP Configuration > Staria FlowAP Subsidiary Setup

  2. View the record related to your subsidiary.

  3. Navigate to the Conversion subtab > Vendor Field Group.

  4. Find the vendor-specific preferences field.

  5. Select a vendor type saved search.

  6. Save the Staria FlowAP Subsidiary Setup.

Setting up the vendor-saved search for the Vendor-Specific Preferences Feature

...

Add the criteria to limit the results of the search. Only include vendors that belongs belong to the subsidiary you are setting up.

...

Example use case:

All the vendors for subsidiary XYZ needs need to have departments assigned to them. Default departments will be defined in the vendor record and used during conversion.

Solution:

Setup a vendor saved search with the following:

Criteria: Subsidiary = XYZ

Results Column: [STA] Default Department

...