Article Type: Concept
Audience: Solution Architects, Enterprise Administrators, Integration Specialists, Partners
Module: NetSuite ERP Integration
Applies to Versions: 2025.4.0+

1. Overview

The MES-NetSuite 2025.4.0 integration package provides comprehensive bidirectional connectivity between Fuuz Manufacturing Execution System and Oracle NetSuite ERP. This production-ready integration enables real-time synchronization of master data and transactional information, creating a unified digital manufacturing environment where shop floor operations seamlessly connect to enterprise resource planning systems.

The package delivers 64 pre-configured components including 22 integration data models, 18 automated data flows, and 15 event-driven integration topics that handle everything from initial master data synchronization to real-time transactional updates for receipts, work order completions, inventory adjustments, and fulfillment.

Package Contents Summary:

• 22 Integration Models defining NetSuite object structures
• 18 Data Flows for query, inbound sync, and outbound updates
• 15 Event Topics for real-time integration triggers
• 3 User Interface Screens for RMA and vendor return workflows
• 1 NetSuite Connection configuration with RESTlet endpoints
• 1 Integration Definition for NetSuite ERP
• Configuration Extensions including inventory statuses and shipment types for returns management

2. Architecture & Data Flow

Definitions

• Integration Model: JSON schema definitions that map NetSuite ERP objects to Fuuz data structures. These models define the payload structure for data exchange between systems without requiring custom API coding.
• NetSuite RESTlet: Server-side JavaScript function deployed in NetSuite that exposes REST API endpoints for external system integration. The MES-NetSuite package includes RESTlet definitions that Fuuz Data Flows invoke to query and update NetSuite data.
• Bidirectional Integration: Two-way data synchronization where master data flows from NetSuite to Fuuz (inbound) and transactional updates flow from Fuuz to NetSuite (outbound), maintaining data consistency across both systems.
• Integration Topic: Pub/sub event channel that triggers data flows based on business events. Topics enable real-time integration by publishing messages when specific actions occur (e.g., work order completion, receipt confirmation).
• Pagination Flow: Data Flow design pattern for retrieving large datasets from NetSuite in batches, preventing timeout errors and managing API governance limits by iteratively querying data in pages.
• Connection: Configured endpoint containing NetSuite account credentials, RESTlet URLs, authentication tokens, and API settings required for Fuuz to communicate with the NetSuite environment.

Components

The MES-NetSuite integration architecture consists of three primary integration patterns:

1. Inbound Synchronization (NetSuite → Fuuz):

• Master Data Query Flows: Scheduled Data Flows that query NetSuite for customers, vendors, items, locations, and workcenters. These flows use pagination to handle large datasets and create/update corresponding records in Fuuz.
• Transactional Data Query Flows: Event-triggered flows that retrieve work orders, purchase orders, sales orders, transfer orders, and customer/vendor return authorizations from NetSuite when production planning or procurement events occur.
• BOM and Routing Synchronization: Specialized flows that query NetSuite assembly items, bills of material, and work order routings to ensure Fuuz manufacturing instructions match ERP product definitions.

2. Outbound Transaction Updates (Fuuz → NetSuite):

• Receipt Confirmations: When materials are received in Fuuz, the integration creates receipt records in NetSuite, updating purchase order statuses and triggering accounts payable processes.
• Work Order Completions: Production completions captured in Fuuz update NetSuite work order statuses and post inventory transactions for finished goods and component consumption.
• Inventory Adjustments: Cycle count adjustments, scrap reporting, and manual inventory corrections in Fuuz synchronize to NetSuite inventory adjustment journals.
• Fulfillment Confirmations: When customer shipments are loaded and shipped in Fuuz, the integration creates fulfillment records in NetSuite, updating sales order statuses and triggering invoicing.
• Assembly Builds: Discrete manufacturing assembly transactions post to NetSuite with component backflush and finished goods receipt details.

3. Returns Management (Bidirectional):

• Customer Return Authorizations (RMA): Query customer RMAs from NetSuite, process receipts in Fuuz mobile interface, and update NetSuite with returned material disposition.
• Vendor Return Authorizations (VRA): Query vendor RMAs from NetSuite, process shipments in Fuuz, and update NetSuite with return tracking information.

3. Use Cases

• ERP-Driven Manufacturing: Organizations running Oracle NetSuite as their financial and operational system of record can deploy Fuuz MES for shop floor execution while maintaining NetSuite as the master source for customers, vendors, items, and production planning. Work orders created in NetSuite automatically appear in Fuuz for execution, and production completions flow back to update inventory and costing.
• Real-Time Inventory Visibility: Finance and operations teams gain real-time visibility into shop floor inventory transactions without manual data entry. When operators complete production, issue materials, or perform cycle counts in Fuuz, these transactions immediately update NetSuite inventory balances, enabling accurate financial reporting and inventory valuation.
• Procurement Automation: Purchase orders created in NetSuite synchronize to Fuuz receiving applications. Warehouse personnel use Fuuz mobile screens to confirm receipts with barcode scanning and lot tracking. Receipt confirmations automatically post to NetSuite, triggering three-way match processes and vendor payment workflows without duplicate data entry.
• Order-to-Cash Integration: Sales orders flow from NetSuite to Fuuz for production planning and fulfillment. As production completes and materials stage for shipment, Fuuz warehouse applications manage picking, packing, and loading. When shipments confirm, the integration creates NetSuite fulfillment records that trigger automatic invoicing and accounts receivable posting.
• Returns Management: Customer and vendor return authorizations created in NetSuite flow to Fuuz mobile applications. Warehouse personnel process RMA receipts and vendor return shipments using specialized Fuuz screens with disposition codes and defect tracking. Return transactions update NetSuite for credit memo processing and vendor debit memos.
• Multi-Location Operations: Companies with multiple manufacturing or distribution facilities can synchronize location hierarchies from NetSuite to Fuuz. Transfer orders created in NetSuite to move inventory between facilities trigger pick/pack/ship workflows in Fuuz at the origin location and receiving workflows at the destination, with automatic posting of in-transit inventory movements.
• Contract Manufacturing: Discrete manufacturers performing work for multiple customers can maintain customer-specific pricing, terms, and contracts in NetSuite while managing actual production execution in Fuuz. Work orders for different customers maintain proper cost accounting segregation and inventory ownership tracking across both systems.

4. Screen Details

The MES-NetSuite package includes 3 specialized user interface screens for managing integration workflows and returns processing:

Integration Management Screen

/app/[application]/integration

• Purpose: Administrative interface for monitoring and managing NetSuite integration status, execution logs, and error handling
• Features: View integration request history, retry failed transactions, monitor data flow execution status, access detailed error logs with NetSuite API responses
• Filters: Date range, integration type (inbound/outbound), status (success/pending/failed), entity type (customer/item/work order/etc.)
• Actions: Retry failed requests, view JSON payloads, export integration logs for troubleshooting, manually trigger synchronization flows
• Audience: Enterprise Administrators, Integration Specialists

Customer Return Authorization Receipt Confirmation

/app/[application]/customer-return-authorization-receipt

• Purpose: Mobile-optimized interface for warehouse personnel to receive and process customer returns (RMAs) synchronized from NetSuite
• Features: Barcode scanning for RMA lookup, line item selection, quantity entry, disposition code assignment (restock/scrap/repair/etc.), location put-away, photo attachments for damage documentation
• Forms: RMA header information (customer, reason, authorization number), line item receipt form with lot/serial capture, disposition decision form with notes
• Actions: Confirm receipt (triggers outbound data flow to update NetSuite RMA status), print return labels, capture defect photos, assign restocking locations
• Integration: Executes RMA Receipt Confirmation From Screen data flow to post receipt transaction to NetSuite
• Audience: Warehouse personnel with Web Access roles

Vendor Return Authorization Shipping

/app/[application]/vendor-return-authorization-shipping

• Purpose: Mobile-optimized interface for warehouse personnel to process vendor returns (defective material returns to suppliers) synchronized from NetSuite
• Features: Vendor RMA lookup, material staging, quantity confirmation, carrier/tracking number entry, shipping documentation generation
• Forms: Vendor RMA header (vendor name, reason code, authorization), line item selection for shipping, packing list generation, bill of lading details
• Actions: Confirm shipment (triggers outbound data flow to update NetSuite vendor RMA status), print shipping labels, generate packing slips, record carrier tracking information
• Integration: Executes vendor return authorization shipping mobile web flow data flow to post shipment to NetSuite
• Audience: Warehouse personnel, shipping coordinators with Web Access roles

All screens utilize Fuuz's mobile-responsive design with large touch targets, barcode scanning integration, and offline capability for warehouse environments with intermittent connectivity.

5. Technical Details

Integration Models (22 Total)

Integration models define the JSON payload structure for data exchange with NetSuite:

• Master Data Models: Customer, Vendor, Item, Inventory Item, Non Inventory Item, Other Charge Item, Assembly Item, Location, Workcenter, System Data
• Transaction Models: Work Order, Work Order Completion, Work Order Routing, Purchase Order, Sales Order, Transfer Order, Return Authorization (customer), Vendor Return Authorization
• Fulfillment Models: Receipt, Fulfillment, Inventory Adjustment, Inventory Transfer

Each integration model maps NetSuite fields to Fuuz data model attributes, handling data type conversions, null value processing, and custom field extensions.

Data Flows (18 Total)

The package includes three categories of data flows:

Inbound Query Flows (13 flows):

• MES-NS-NetSuite: Query Customer - Paginated customer master data synchronization
• MES-NS-NetSuite: Query Vendor - Paginated vendor master data synchronization
• MES-NS-NetSuite: Query Item - Item master synchronization with inventory attributes
• MES-NS-NetSuite: Query Assembly Item - Manufactured assembly item definitions
• MES-NS-NetSuite: Query BOM - Bill of materials with component relationships
• MES-NS-NetSuite: Query Location - Warehouse and facility location hierarchy
• MES-NS-NetSuite: Query Workcenter - Manufacturing workcenter resources
• MES-NS-NetSuite: Query Work Order - Production work orders for execution
• MES-NS-NetSuite: Query Purchase Order - Purchase orders for receiving
• MES-NS-NetSuite: Query Sales Order - Sales orders for fulfillment
• MES-NS-NetSuite: Query Transfer Order - Intercompany transfer orders
• MES-NS-NetSuite: Query Customer Return Authorization - Customer RMAs
• MES-NS-NetSuite: Query Vendor Return Authorization - Vendor RMAs

Inbound Processing Flow (1 flow):

• MES-NS-NetSuite Inbound - Central orchestration flow that processes inbound integration messages, routes them to appropriate Fuuz data models, handles error logging, and manages retry logic

Outbound Update Flows (4 flows):

• MES-NS-Netsuite: Outbound - Central orchestration for outbound transactions to NetSuite
• RMA Receipt Confirmation From Screen - Customer return receipt posting
• vendor return authorization shipping mobile web flow - Vendor return shipment posting
• MES-NS-NetSuite: Query System Data - NetSuite configuration and system metadata retrieval

Integration Topics (15 Total)

Event-driven integration triggers using Fuuz's pub/sub messaging system:

• Pagination Topics (9 topics): Control iterative data retrieval for large datasets - netSuite.pagination.customer, netSuite.pagination.vendor, netSuite.pagination.item, netSuite.pagination.purchaseOrder, netSuite.pagination.workOrder, netSuite.pagination.salesOrder, netSuite.pagination.transferOrder, netSuite.pagination.bom, netSuite.pagination.phantom
• Integration Topic (1 topic): General NetSuite integration message routing - netSuite.integration
• Outbound Transaction Topics (5 topics): Trigger updates to NetSuite when Fuuz transactions complete - netSuite.outbound.receipt, netSuite.outbound.inventoryAdjustment, netSuite.outbound.workOrderCompletion, netSuite.outbound.fulfillment, netSuite.outbound.assemblyBuild

NetSuite Connection Configuration

The package includes a pre-configured NetSuite connection template requiring the following parameters:

• NetSuite Account ID: NetSuite account identifier (e.g., 1234567)
• RESTlet URL Base: Base URL for deployed RESTlet scripts
• Consumer Key: OAuth 1.0 token-based authentication consumer key from NetSuite integration record
• Consumer Secret: OAuth 1.0 consumer secret
• Token ID: Access token ID for API authentication
• Token Secret: Access token secret

The connection uses OAuth 1.0 token-based authentication (TBA) which provides secure, passwordless API access without exposing NetSuite user credentials.

Configuration Extensions

The package extends Fuuz MES configuration with returns management capabilities:

• Inventory Statuses: "Pending Return" and "Returned" statuses for RMA material tracking
• Inventory Type: "RMA" classification for customer return inventory segregation
• Shipment Type: "Vendor Return Authorization" for outbound vendor return shipments

6. Resources

• Fuuz Industrial Operations Platform (fuuz.com)
• Fuuz Data Flow Designer Documentation (Integration node reference, connector configuration)
• Oracle NetSuite SuiteCloud Development Framework (RESTlet deployment guide, OAuth 1.0 token-based authentication setup)
• NetSuite SuiteScript 2.1 API Documentation (N/record module, search API, transaction processing)
• Fuuz Integration Best Practices Guide (Error handling, retry logic, pagination patterns)
• MES-NetSuite RESTlet Bundle (NetSuite SuiteScript files for deployment in NetSuite account)
• Fuuz Professional Services (Integration implementation, NetSuite RESTlet deployment assistance)

7. Troubleshooting

• OAuth Authentication Failures: Integration requests return 401 Unauthorized or "Invalid Login" errors. Cause: Incorrect OAuth credentials, expired tokens, or insufficient NetSuite role permissions. Fix: Verify Consumer Key, Consumer Secret, Token ID, and Token Secret match NetSuite integration record values exactly (no extra spaces). Confirm the NetSuite role assigned to the integration user has "Web Services" permission and access to required record types (work orders, purchase orders, sales orders, etc.). Regenerate access tokens if expired.
• RESTlet Deployment Not Found: Data flows fail with "Script not found" or 404 errors when calling NetSuite. Cause: RESTlet scripts not deployed in NetSuite or incorrect RESTlet URLs in Fuuz connection configuration. Fix: Deploy all MES-NetSuite RESTlet scripts to NetSuite using SuiteCloud IDE or file cabinet upload. Create RESTlet deployments for each script and record the deployment URLs. Update Fuuz NetSuite connection with correct RESTlet deployment URLs. Verify deployments are set to "Released" status in NetSuite.
• Data Not Synchronizing from NetSuite: Query flows execute successfully but no records appear in Fuuz. Cause: NetSuite saved search filters excluding records, incorrect date range parameters, or missing custom field mappings. Fix: Review NetSuite saved searches used by RESTlets to ensure filters return expected records. Check data flow execution logs for JSON response payloads to verify data is being returned from NetSuite. Validate integration model field mappings match NetSuite custom field internal IDs. Test RESTlet directly in NetSuite using RESTlet testing tools to isolate issues.
• Pagination Timeout Errors: Large dataset queries timeout or fail to complete. Cause: Page size too large for NetSuite governance limits or network timeout configuration. Fix: Reduce page size parameter in query data flows (recommended: 100-200 records per page). Increase Fuuz data flow timeout settings in Data Flow Designer. Implement incremental synchronization using last modified date filters rather than full refreshes. Schedule large dataset synchronizations during off-peak hours to reduce NetSuite API contention.
• Outbound Transaction Posting Failures: Fuuz transactions (receipts, completions, fulfillments) fail to post to NetSuite with validation errors. Cause: Required NetSuite field missing in Fuuz payload, invalid NetSuite internal IDs, or business logic validation failures in NetSuite. Fix: Review integration request logs in Fuuz Integration Management screen for detailed NetSuite error messages. Common issues include missing location IDs (ensure locations are synchronized), invalid item IDs (verify item synchronization completed), or required custom fields. Update integration model mappings to include all NetSuite required fields. Test transactions manually in NetSuite first to understand validation requirements.
• Duplicate Records Created: Multiple Fuuz records created for single NetSuite record or vice versa. Cause: Integration running multiple times due to retry logic or missing uniqueness checks. Fix: Ensure integration models include NetSuite internal ID field for deduplication. Configure data flows to check for existing records before creating new ones. Review integration topic subscriptions to prevent duplicate event triggers. Implement idempotency keys in outbound transaction flows to prevent duplicate NetSuite postings on retry.
• Custom Field Mapping Issues: NetSuite custom fields not synchronizing to Fuuz or vice versa. Cause: Custom field internal IDs not included in integration models or RESTlet searches. Fix: Identify NetSuite custom field internal IDs (format: custbody_fieldname, custitem_fieldname). Add custom field mappings to integration models in Fuuz. Update NetSuite RESTlet saved searches and scripts to include custom fields in returned columns. Test mappings with sample data before full deployment.

8. Revision History