NZ Disk To NetSuite Update

#

Overview

This process "NZ Disk To NetSuite Update" is designed to update Item Fulfillment and Consolidated Fulfillment records in the NetSuite ERP system based on data retrieved from a disk-based source. It starts by retrieving files from the disk, performs various data processing and mapping steps, and then updates the corresponding records in NetSuite. The process also includes error handling mechanisms, decision points, and the ability to store backup files on the disk. Additionally, it leverages a subprocess to query and retrieve data from NetSuite's Saved Search functionality. This integration solution enables organizations to efficiently synchronize and update critical fulfillment data between their disk-based systems and the NetSuite ERP, ensuring data accuracy and streamlining order management processes.

#

Process Diagram

#

Business Context

Source Application: Disk
Target Application: NetSuite
Application Info:

1. Disk: The disk connector in Boomi AtomSphere enables the retrieval, storage, and management of files and documents from local or network-attached storage systems. This process leverages the disk connector to fetch files containing fulfillment data that needs to be synchronized with the NetSuite ERP.
2. NetSuite: NetSuite is a comprehensive and highly scalable cloud ERP system tailored for mid-market and enterprise businesses. It unifies core functions spanning accounting, finance, revenue management, fixed assets, order-to-cash, purchasing, inventory, manufacturing, supply chain management and employee management on a single platform. This process updates Item Fulfillment and Consolidated Fulfillment records in the NetSuite system to ensure data consistency and accuracy across the organization.

#

Process Steps and Functions

Start\[stepname= "Start"]: Initiates the process flow.
Document Properties\[stepname= "Document Properties"]: Manages and sets properties or metadata associated with the processed documents, potentially preparing the data for further processing or storage.
Branch\[stepname= "Branch", numBranches= "2", 1= "Process Call", 2= "Connector"]: Splits the process flow into two parallel paths - one to call a subprocess, and the other to retrieve files from the disk.
Process Call\[stepname= "Process Call", sub\process\name= "SubProcess: NS\CF\SavedSearch"]: Invokes a subprocess responsible for querying and retrieving data from NetSuite's Saved Search functionality. This allows the process to leverage pre-defined and optimized data retrieval mechanisms within NetSuite.
Save File to Disk\[stepname= "Connector", connectorname= "Disk", actionType= "Get"]: Utilizes the disk connector to retrieve files from the disk-based storage system. These files likely contain the fulfillment data that needs to be synchronized with NetSuite.
Business Rules\[stepname= "Business Rules", Accepted= "Document Properties2", Rejected= "Stop"]: Applies business rules to determine whether the retrieved files should be processed further (Accepted) or the process should be stopped (Rejected).
Document Properties2\[stepname= "Document Properties"]: Performs additional document property management tasks based on the outcome of the business rules evaluation.
Stop\[stepname= "Stop"]: Marks the successful completion of the process when the business rules reject the file processing.
Try/Catch\[stepname= "Try/Catch", default= "Map", error= "Business Rules2"]: Establishes an error handling mechanism, directing the flow to a mapping step or a separate set of business rules in case of errors.
NZ\Split\[stepname= "Map", mapname= "NZ\Split",

of mappings= 5]: This mapping step splits or transforms the data retrieved from the disk-based source into a format suitable for further processing. It utilizes custom functions like Date, Date Format, and CF\Name to handle the data transformations.
Data Process\[stepname= "Data Process"]: Performs additional data processing tasks on the transformed data.
Decision\[stepname= "Decision", true= "Flow Control", false= "Stop2"]: Evaluates a condition and routes the process flow accordingly, either continuing to the flow control step or stopping the process.
Flow Control\[stepname= "Flow Control"]: Manages the flow of the process based on specific conditions or logic.
Branch2\[stepname= "Branch", numBranches= "2", 1= "Update\IF", 2= "Update\CF"]: Splits the process flow into two parallel branches to handle the update of Item Fulfillment and Consolidated Fulfillment records in NetSuite.
Update\IF\[stepname= "Map", mapname= "Update\IF",

of mappings= 3]: This mapping step transforms the data to update the Item Fulfillment records in NetSuite. It utilizes the Document Cache Lookup function to retrieve relevant data.
Update\CF\[stepname= "Map", mapname= "Update\CF",

of mappings= 5]: This mapping step transforms the data to update the Consolidated Fulfillment records in NetSuite. It also leverages the Document Cache Lookup function.
\[CHECK]IF\Internal\ID\[stepname= "Decision", true= "Try/Catch2", false= "Stop3"]: Checks the existence of the Item Fulfillment Internal ID and routes the process accordingly.
Try/Catch2\[stepname= "Try/Catch", default= "Connector2", error= "Stop4"]: Establishes an additional error handling mechanism for the Item Fulfillment update process.
Connector2\[stepname= "Connector", connectorname= "NetSuite", actionType= "UPDATE"]: Leverages the NetSuite connector to update the Item Fulfillment records in the NetSuite system.
\[CHECK]CF\Internal\ID\[stepname= "Decision", true= "Connector3", false= "Stop6"]: Checks the existence of the Consolidated Fulfillment Internal ID and routes the process accordingly.
Connector3\[stepname= "Connector", connectorname= "NetSuite", actionType= "UPDATE"]: Utilizes the NetSuite connector to update the Consolidated Fulfillment records in the NetSuite system.
\[CHECK]CF\Success\[stepname= "Decision", true= "Connector4", false= "Stop7"]: Evaluates the success of the Consolidated Fulfillment update and routes the process accordingly.
Connector4\[stepname= "Connector", connectorname= "Disk", actionType= "Get"]: Leverages the disk connector to delete the processed file from the disk-based storage.
Document Properties3\[stepname= "Document Properties"]: Performs additional document property management tasks.
Set Disk File Name and Backup Directory\[stepname= "Document Properties"]: Sets the file name and backup directory for the disk-based storage.
Store File to Disk\[stepname= "Connector", connectorname= "Disk", actionType= "Send"]: Utilizes the disk connector to store a backup of the processed file on the disk-based storage.
Delete File from Disk\[stepname= "Connector", connectorname= "Disk", actionType= "Get"]: Leverages the disk connector to delete the processed file from the disk-based storage.
Message\[stepname= "Message"]: Generates a message, potentially for notification or logging purposes, when the business rules reject the file processing.
Set Disk File Name and Backup Directory\[stepname= "Document Properties"]: Sets the file name and backup directory for the disk-based storage in the case of a rejected file.
Store File to Disk\[stepname= "Connector", connectorname= "Disk", actionType= "Send"]: Utilizes the disk connector to store a backup of the rejected file on the disk-based storage.
Slack\[stepname= "Connector", connectorname= "Slack", actionType= "CREATE"]: Leverages the Slack connector to create a new chat message, potentially for notification or monitoring purposes.