Admin Guide

1. Who Is This Section For?

This section is intended for:

• NetSuite administrators

• Implementation specialists

• Sales or operations leads responsible for system setup

It is relevant for anyone configuring:

• integration behavior per subsidiary

• transaction creation logic

• field mappings and automation settings

The purpose of this section is to guide you through the initial configuration and ongoing maintenance of Alta Via Order Agent, ensuring that the integration processes documents correctly and according to your business requirements.

Note: Without proper configuration, the integration will not process any documents.

2. Setup

Prerequisites

Before you begin, ensure that:

• You have sufficient permissions to create and manage custom records

• The Alta Via Order Agent SuiteApp is installed

• If your NetSuite account uses subsidiaries, create a configuration record for each subsidiary you want to process documents for.

Note: If your NetSuite account uses subsidiaries, documents are only processed for subsidiaries with a configuration record. 

Accessing the Configuration

Navigate to: AVA Order Agent > AV Order Agent > Configuration

This opens the configuration record used to control how the integration behaves per subsidiary.

Creating a Configuration Record

For each subsidiary, create one configuration record.

The configuration acts as the central control point for:

• which transactions can be created

• how data is mapped

• how documents are stored

• how errors are handled

Configuration Fields

Maintain the following fields:

Activation Logic

The configuration determines whether and how the integration runs:

• The integration only processes documents if a configuration exists for the subsidiary

• Only transactions defined in Activated transactions will be created

• Automation behavior depends on the Automated Sales Orders setting

Global vs. Subsidiary Configuration

All settings are defined per subsidiary.

This allows you to:

• apply different transaction logic per legal entity

• adapt field mappings to local requirements

• control automation levels independently

Finalizing Setup

After completing the configuration:

1. Save the record

2. Ensure all required fields are populated

3. Verify that the correct subsidiary is assigned

Once saved, the integration is ready to process documents for that subsidiary. Incoming documents are automatically stored in the configured folder when processing begins.

Summary: The configuration record controls all integration behavior per subsidiary. Without it, no documents are processed. Proper setup ensures accurate, automated, and controlled order creation.