send feedback

❮ Previous Next ❯

Boomi Integrations for NetSuite

About Boomi

Boomi is one of the tools Cloud Inventory® uses to integrate the Cloud Inventory® applications to enterprise resource planning systems.

Prerequisites

Before you implement Boomi integration, the following must be in place or completed.

Boomi Certification Training.
- Boomi Essentials.
- Associate Integration Developer.
- Professional Integration Developer is strongly recommended for customization development efforts.
Cloud Inventory 2022.1 or above with React desktop capabilities.
Customer's Boomi account provisioned. This includes Atom Cloud availability set up and maintained by Cloud Inventory Cloud Operations.
Integration knowledge of NetSuite.
NetSuite specific requirements:
- NetSuite bundles installed.
- NetSuite tokens created.
- NetSuite user for integrations need to have their time zone set to GMT Greenwich Mean Time under the user preferences. This needs to be set as GMT for data replication purposes.

Installation

These instructions outline installing the pre-built Boomi processes to a customer's specific Boomi account.

Note: Before performing the installation, the Boomi processes must be provisioned for each customer account. If you are unable to see the expected Boomi processes in the Process Library or Integration Pack section of the Boomi platform, please contact Cloud Operations.

Two versions of the code are available for installation:

Integration Packs – Packaged integrated solutions that consist of one or more package processes that are ready for installation by users of managed accounts. Think of these like Cloud Inventory® Platform pristine objects. They are not editable processes and are meant for quick installation and setup. No customizations can be made to objects in integration packs. Furthermore, the process's code is not available to view. Any code updates or fixes are handled and released by the solution developer.
Process Library – Packaged processes that can be installed and configured like integration packs, but are also modifiable and customizable. The initial installation of processes from the Process Library contains the current code snapshot at the time the process was published to the Process Library. Any new or updated versions made available by the solution developers are considered a new snapshot version of the process, thus when installing on a system with existing processes installed (not the Integration Packs), a complete, new version of the solution gets installed and will create duplicate files, including the licensed connector components.

Install Integration Pack

From the Boomi platform home page, select Services > Integration.
Select the Deploy > Integration Packs from the menu.
Select the Browse Integration Packs button. This will show you any integration packs that have been made available for the Boomi account that you are logged into.
Expected Result
- You will receive an error if no integration packs are available for install.
- If any integration packs are available for the account, you'll see a list.
  Note:There will be three integration packs available. One for development, stage and production. Each will need to be installed.
Click view for the integration pack you wish to install. As previously stated, there will be one available for development, stage and production. Since the CI developers will control development of these Boomi interfaces, it was determined to create three separate integration packs for segregation of app code for testing and validation as well as production.
Select the Install button.

Example
You will see an Installed message when finished, which typically doesn't take much time.

Expected Result

Install Process Library

Remember, Process Library components are used to customize Boomi processes. They should be installed only when you plan to create custom Boomi processes. If have no reason to customize or modify Boomi code, you can simply use the Integration Packs.

From the Boomi platform home page, select Services > Integration.
Select Browse Process Library.

Expected Result
This is typically at the bottom left of the Integration page.
Select Cloud Inventory from the Filter by Publisher list on the right.

Example
This step filters all available processes published by Cloud Inventory for the current account. Typically, one (main) NW – Release Processes result is displayed. This process contains all the individual released processes available for the ERP.

Example
Select the Install button next to each process name available.

Expected Result
This action will installs the main Boomi processes and related components needed to run the process.
Select the install location.

Example
You can install into either the root/parent folder or create a new folder.

Example
Select Install to complete the installation of the Boomi components.

Example
A confirmation message displays upon successful installation.

Example

Create Package Components

The first step of deployment is to create a packaged component of your downloaded or custom built processes. Deployable components must be packaged before they can be deployed and installed to a Boomi Atom.

Note:Processes installed from Integration Packs do not need to go through this step.

When you create a packaged component or process, you essentially take a "snapshot" of its development on the Build tab, typically when you are done building the process or component and are ready to deploy it to your test or production environment.

The first step of this process has two options:

Option 1 - From the Boomi Build page, open the main process you want to build the package for.
1. Click Create Packaged Component at the top right.
Example
Option 2 - From the Boomi home page, go to the Integration page and select Deploy > Packaged Components.
1. Select Create Packaged Component.
2. Select the main process to create a packaged component.
Step Information

Note:Select only the main process. When the package component is created, it includes all of the referenced components.
Select Next > Add Details.
Enter a unique version for this component.

Step Information

Note:Best practice: use a versioning system that can easily roll back to the previous build if necessary.
Include any additional package notes. This should include notes about the changes made.
On the Sharing option, select Not Allowed.

Step Information

Note:Sharing is used by the core Cloud Inventory® development team to package components that can be distributed to multiple customer accounts.

Once the package has been created, you can deploy the components.

More information about Boomi packaged components can be found at https://help.boomi.com/bundle/integration/page/int-Packaged_components.html

Deploy Packaged Components

Deployment is how you prepare your processes and deployable components to run and operate in a test or production environment. You will deploy a packaged component to a particular environment, which may be one or more Atoms attached.

Option 1 – During the package components process above, you can deploy to the environment directly once the package has been built.

Step Information
Option 2 – From the Boomi Integration page, select Deploy > Packaged Components. This will show you a list of all packaged components and their version and environment where they are deployed to.
1. Find the component you wish to deploy and select the gear icon under Actions then select Deploy.
  
  Example
Option 3 - From the Boomi Integration page, select Deploy > Deployments. This will show you a list of all packaged components and their version and environment where they are deployed to.
1. Select Deploy Packaged Components.
  
  Expected Result
  The list of packaged components opens.
2. Select one or more packaged components then select Next: Review.
After selecting the packaged component to deploy from the options above, select the environment to deploy the packaged component.

Step Information

Note:Deploying components consumes Boomi licenses. Make sure you have enough licenses available for the deployment to succeed.

Expected Result
You will see a list of the packaged components you are about to deploy. This shows you the version that you are about to deploy and the version that is already deployed to the selected environment.
Select Next: Review.
Review the information to ensure everything is correct, then select Deploy.

The component deploys to all Atoms on the selected environment.

For more information about Boomi deployments, visit this help page: https://help.boomi.com/bundle/integration/page/int-Deploy_packaged_components.html

Configuration

Environment Extensions

Environment extensions are similar to Cloud Inventory® Platform Configuration Elements. You can create configurable extensions of your processes that then allow the processes to behave differently. Environment extensions also store connector specifics such as endpoints for APIs and credentials.

Environment extensions are set up for a specific environment. If multiple Atoms are deployed to an environment, the extensions apply to each Atom attached to the environment.

Note:If both the Integration Pack and Process Library processes were installed, duplicate values display in the Environment Extensions. Both values need to be set up.

From the Boomi home page, navigate to the Integrations section.
Select the Manage menu, the select Atom Management.

Expected Result
This opens a page that shows all environments and Atoms configured for the customer's account.
Note:Three environments should be available: Dev (or Develop), Stage, and Production. Each environment should have an Atom attached to it. If not, please contact Cloud Operations to get this set up.
Select the name of the environment where extensions will be configured.
Under Administration, select Environment Extensions.

Expected Result
The Extensions modal page opens.

Example

NetSuite Extensions

Connection Settings (Cloud Inventory, Cloud Inventory PATCH)

URL	This is the URL to the Cloud Inventory® system. This should just be the server and the port. All other information about the specific endpoint will be set up in the Boomi processes. Do not put the trailing / at the end of the URL. For example: https://server.cloudinventory.com:44444

Connection Strings (NetSuite HTTP Client)

URL	This is the URL to the NetSuite system. Do not put the trailing / at the end of the URL. For example: https://<account>.restlets.api.netsuite.com
OAuth Consumer Key	NetSuite generated OAuth consumer key.
OAuth Access Token	NetSuite generated OAuth access token for the NetSuite integration user.
OAuth Token Secret	NetSuite token secret created for the access token.
OAuth Consumer Secret	NetSuite consumer secret for the consumer key.
OAuth Realm	NetSuite Realm, which typically is the account/instance.

Process Properties (CI API_Values)

CI_UserName	Cloud Inventory® login ID. This must be a valid platform login ID. * NOTE * In order to get the user to authenticate correctly, run any CI transaction (example: Item Balance Inquiry) for each CI environment where Boomi processes will run against. This is needed to populate the CI Users table with information needed for processing API requests and is the same as if running FAST applications or CI desktop applications.
CI_Program	Cloud Inventory® program. This is used in the API calls and can be any value. It will show up in the audit fields of the particular transaction.
CI_Device	Cloud Inventory® device ID. This can be any value up to 10 characters.
CI_authKey	This is the Cloud Inventory® API authorization key. This can be obtained from Cloud Operations and is required for all API calls to CI.
CI_API_Version	This is the API version for the Cloud Inventory® APIs and is used when building the complete URL string for the APIs. Typical example is something like v2.2.
CI_PrivateKey	Cloud Inventory® authentication key use to generate an authorization token. This can be obtained from Cloud Operations and is required for all API calls to CI.
CI_UserUUID	This is the Cloud Inventory® Platform User ID based on the value in the CI_UserName above. This is generally a 32 digit GUID value. You can get this by logging in to the CI Platform, looking at the user from the CI_UserName, and finding the User ID.

Process Properties (CI_Transaction_Properties)

ERP_Inv_Sync_ReasonCode

This a Cloud Inventory® code that is setup to use in any Boomi processes that will pull in inventory availability from NetSuite to CI, which will create a CI adjustment transaction. This reason code will tell the Boomi processes that uploads CI transactions back to the NetSuite to ignore any transactions where the Reason Code matches this value.

This requires that the reason code be setup in CI under SETUP > Codes. The code type is REASONCODE and the value in the code will be setup in this process property.

Process Properties (Logging)

Enable Logging	Value that determines whether any additional process logging will be captured. Logging is viewed in Process Reporting, which is explained in detail below.
Log Level	Setting to determine the level of logging. Values include: Info – Everything additional is logged Warning – Only log statements in processes marked as Warning and Error will be logged. Error – Only errors are logged, which are always logged anyway.

Process Properties (NS Post Transactions Configurations)

Adjustment Process Option	Option for posting Adjustments to NetSuite either by single line or consolidate by item.
Posting Date Format	Date format for how the Lot Expiration Date is sent to NetSuite. Valid values: MM/dd/yyyy Dd/MM/yyyy M/d/yyyy d/M/yyyy
Lot/Serial Posting Option	Use this option to determine how Lots and Serials get posted to NetSuite. Valid values: Post one value Post lot if both present Post serial if both present Post neither
Receipts Process Option	Use this option for posting receipts to NetSuite either by single line or consolidate by order.
Sales Order Process Option	Use this option for posting fulfillments to NetSuite either by single line or consolidate by order.
Transfer Order Process Option	Use this option for posting transfers to NetSuite either by single line or consolidate by item.
Bins Used	Use this flag to indicate whether BINs are in use for NetSuite. If BINs are in use, then the BINXREF codes table must be configured for Location to Bin XREF. At this time we support only one BIN per location in the standard App.
Cycle Count Account ID	Internal ID of the Account in NetSuite that Cycle Count Adjustments should post against.
Record NetSuite Transaction ID	If applicable, post the transaction/record ID back to the CI TransactionUpToErp table after successful completion from the NetSuite API call. This will be recorded in the ErrorMessage field but with a status of Complete in the TransactionUpToErp table.

Process Properties (NS Item Configurations)

Item Parse	If true, this parses the item number according to setup in the process. If false, it will send back the passed-in value.
Item First Run	If true, Boomi will replicate items as if it was the first time extracting data from NetSuite to Cloud Inventory®. You need to include the Item ID Start, Stop, and Max Records process properties.
Item ID Start	NetSuite item internal ID value for starting point of item replications. No items with an internal ID prior to this value will be replicated.
Item ID Stop	NetSuite item internal ID value for stopping point of item replications. No items with an internal ID after this value will be replicated.
Item Max Records	The number of item records to query for each call to NetSuite.
Item Exclude Inactive	True/false flag to determine if NetSuite inactive items are replicated to Cloud Inventory®.
Item Lots Used	True/false flag to determine whether items in NetSuite can be lot controlled.
Item Serials Use	True/false flag to determine whether items in NetSuite can be serial controlled.
Item Specific UOM Group	True means each item will have a specific UOM group in Cloud Inventory® based on the NetSuite units type. False means items can share NetSuite units types as the Cloud Inventory® UOM Group.

Process Properties (NS Purchase Order Configurations)

PO First Run	If true, Boomi replicates purchase orders as if it was the first time extracting data from NetSuite to Cloud Inventory®. You need to include the PO ID Start, Stop, and Max Records process properties.
PO ID Start	NetSuite purchase order internal ID value for starting point of PO replications. No POs with an internal ID prior to this value will be replicated.
PO ID Stop	NetSuite purchase order internal ID value for stopping point of PO replications. No POs with an internal ID after this value will be replicated.
PO Max Records	The number of purchase order records to query for each call to NetSuite.
PO Location Filter	Include the location JSON filter to replicate POs from certain locations into the Cloud Inventory® system. This must be in a valid NetSuite JSON format and can contain multiple values. Examples: 'location','anyof','1' 'location','anyof','1','2'
Inbound Shipments	Determines whether inbound shipments are used.

Process Properties (NS Work Order Configurations)

WO First Run	If true, Boomi replicates work orders as if it was the first time extracting data from NetSuite to Cloud Inventory®. You need to include the WO ID Start, Stop, and Max Records process properties.
WO ID Start	NetSuite work order internal ID value for starting point of WO replications. No WOs with an internal ID prior to this value will be replicated.
WO ID Stop	NetSuite work order internal ID value for stopping point of WO replications. No WOs with an internal ID after this value will be replicated.
WO Max Records	The number of work order records to query for each call to NetSuite.
WO Location Filter	Include the location JSON filter to replicate WOs from certain locations into the Cloud Inventory® system. This must be in a valid NetSuite JSON format and can contain multiple values. Examples: 'location','anyof','1' 'location','anyof','1','2'
WO Type	Work order type used when inserting data into Cloud Inventory®.

Process Properties (NS Sales Order Configurations)

SO First Run	If true, Boomi replicates work orders as if it was the first time extracting data from NetSuite to Cloud Inventory. You will need to include the SO ID Start, Stop, and Max Records process properties.
SO ID Start	NetSuite work order internal ID value for starting point of SO replications. No SOs with an internal ID prior to this value will be replicated.
SO ID Stop	NetSuite work order internal ID value for stopping point of SO replications. No SOs with an internal ID after this value will be replicated.
SO Max Records	The number of work order records to query for each call to NetSuite.
SO Location Filter	Include the location JSON filter to replicate SOs from certain locations into the Cloud Inventory® system. This must be in a valid NetSuite JSON format and can contain multiple values. Examples: 'location','anyof','1' 'location','anyof','1','2'
SO Future Days	The number of days in the future to check for valid sales orders for replication into Cloud Inventory®. The number here will be added to the current date and used in the shipdate field of the NS ad hoc search JSON request.

Process Properties (CI Serial Numbers Configurations) – Used when replicating items to Cloud Inventory®

Allow Serial Selection	Controls the display and behavior of the Select Serials button in the serial capture modal on desktop. Valid Values: Never View Only Allow Selection (default)
Default Serial Capture Method	Defines the default serial capture method when setting up a new item or warehouse item. Valid Values: Outbound (default) Inbound-Outbound Bin Tracking
Serial Default IN Rule	Defines the default inbound receiving rule. Valid Values: Capture (default) Validate with Warning Validate with Error
Serial Default OUT Rule	Defines the default outbound shipping rule. Valid Values: Capture (default) Validate with Warning Validate with Error
Serial Default OUT Mismatch Rule	Defines the default outbound inventory known serial rule. Valid Values: Error (default) Allow and Warn
Serial Default OUTSHIP Option	Defines the default outbound processing capture point for serial numbers. Valid Values: Pick (default) Pack Ship Pick,Pack Pack,Ship Pick,Pack,Ship Pick,Ship

Process Properties (NS Transfer Order Configurations)

TO First Run	If true, Boomi replicates transfer orders as if it was the first time extracting data from NetSuite to Cloud Inventory®. You need to include the TO ID Start, Stop, and Max Records process properties.
TO ID Start	NetSuite transfer order internal ID value for starting point of TO replications. No TOs with an internal ID prior to this value will be replicated.
TO ID Stop	NetSuite transfer order internal ID value for stopping point of TO replications. No TOs with an internal ID after this value will be replicated.
TO Max Records	The number of transfer order records to query for each call to NetSuite.
TO Location Filter	Include the location JSON filter to replicate TOs from certain locations into the Cloud Inventory® system. This must in a valid NetSuite JSON format and can contain multiple values. Examples: 'location','anyof','1' 'location','anyof','1','2'

Process Properties (NS Transfer Order Purchase Order Configurations) – CI Generate Inbound POs from NS Transfer Orders

TO PO First Run	If true, Boomi will replicate transfer orders as if it was the first time extracting data from NetSuite to Cloud Inventory®. You will need to include the TO PO ID Start, Stop, and Max Records process properties.
TO PO ID Start	NetSuite transfer order internal ID value for starting point of TO replications. No TOs with an internal ID prior to this value will be replicated.
TO PO ID Stop	NetSuite transfer order internal ID value for stopping point of TO replications. No TOs with an internal ID after this value will be replicated.
TO PO Max Records	The number of transfer order records to query for each call to NetSuite.
TO PO Location Filter	Include the location JSON filter to replicate TOs from certain locations into the Cloud Inventory® system. This must in a valid NetSuite JSON format and can contain multiple values. Examples: 'location','anyof','1' 'location','anyof','1','2'

Process Properties (NS Vendor Returns Configurations) – CI Generate Outbound SOs from NS Vendor Return Authorizations

VRMA First Run	If true, Boomi replicates vendor return authorization orders as if it was the first time extracting data from NetSuite to Cloud Inventory. You need to include the VRMA ID Start, Stop, and Max Records process properties.
VRMA ID Start	NetSuite VRMA internal ID value for starting point of VRMA replications. No VRMAs with an internal ID prior to this value will be replicated.
VRMA ID Stop	NetSuite VRMA internal ID value for stopping point of VRMA replications. No VRMAs with an internal ID after this value will be replicated.
VRMA Max Records	The number of VRMA records to query for each call to NetSuite.
VRMA Location Filter	Include the location JSON filter to replicate VRMAs from certain locations into the Cloud Inventory® system. This must in a valid NetSuite JSON format and can contain multiple values. Examples: 'location','anyof','1' 'location','anyof','1','2'

Process Properties (NS Customer Returns Configurations) – CI Generate Inbound POs from NS Return Authorizations

CR First Run	If true, Boomi replicate customer return orders as if it was the first time extracting data from NetSuite to Cloud Inventory. You will need to include the CR ID Start, Stop, and Max Records process properties.
CR ID Start	NetSuite customer return internal ID value for starting point of customer return replications. No customer returns with an internal ID prior to this value will be replicated.
CR ID Stop	NetSuite customer return internal ID value for stopping point of customer return replications. No customer return's with an internal ID after this value will be replicated.
CR Max Records	The number of customer return records to query for each call to NetSuite.
CR Location Filter	Include the location JSON filter to replicate customer return's from certain locations into the Cloud Inventory® system. This must in a valid NetSuite JSON format and can contain multiple values. Examples: 'location','anyof','1' 'location','anyof','1','2'
CR Prefix Val	Prefix value used when creating the PO in Cloud Inventory®. If value is 'Default Text' then no prefix will be applied.

[CC] Standard Notification Configuration - Used for advanced notifications for error handling if the process is configured using these process properties

ENV_Notification_Method	The notification method employed. eMail Incident Disk
ENV_Notification_Emails_Technical_To	Add email addresses that should be notified upon a Technical Error. Separate emails with the ; symbol.
ENV_Notification_Emails_Data_To	Add email addresses that should be notified upon a Data Error. Separate emails with the ; symbol.
ENV_Notification_Email_Technical_Enabled	If set to true, technical emails are generated and sent. True False
ENV_Notification_Email_Data_Enabled	If set to true, data emails are generated and sent. True False
ENV_Notification_Email_Technical_From	Email address Technical errors sent from.
ENV_Notification_Data_From	Email address Data errors sent from.
ENV_Notification_Content_Type	Email format: text/plain text/html
ENV_Use_Standard_Notification_Config	If set true, the system uses standard notification configuration. If false, the system uses custom process property notification configuration: True False
ENV_Notification_Type	Used to route DATA (Document) errors or TECHNICAL (Connection) errors differently. DATA TECHNICAL
ENV_Notification_Notification_Debug	If set to ON, document and process properties are written via Notify shape to process log. and dumped into notification messages for troubleshooting. OFF ON

Process Scheduling

Similar to the Cloud Inventory® Platform AIM sessions, you can setup Boomi to run processes on scheduled intervals. You scan schedule individual processes as well as stop the schedule for the individual process or all processes. This is all setup by Atom on the Boomi Atom Management page.

From the Boomi home page, navigate to Integrations.
Click on the Manage menu and select Atom Management. This will take you to the page showing all environments and Atoms configured for the customer's account.

Step Information

Note:You must have the Atom Management privilege to modify schedules and properties for deployed processes. If you have the Atom Management Read Access privilege, you can view information about process schedules and properties, but you cannot perform any actions.
Select the specific Atom in the environment where the processes to be scheduled was deployed to.

Example

Step Information

Note:If there are multiple Atoms installed, you need to select the specific Atom under the environment that you want to schedule the process.
Under the Runtime section, select Deployed Processes. This will show all processes that have been deployed to the environment and installed on the selected Atom.
Find the process you wish to schedule and click the arrow to bring up options about the specific process. Select Edit Schedules:

Example
Now on the Scheduling modal page, you can add a schedule for this process. Enter desired scheduling information for the process.

Step Information

Note:All date/times are stored and transacted in the UTC time zone.

Example
Press OK to save the schedule. This will activate the schedule for this Atom and environment. You can also stop this schedule or all schedules from this page as well.

Please view Boomi's documentation around scheduling deployed processes:

https://help.boomi.com/bundle/integration/page/r-atm-Deployed_Processes_panel.html

Process Reporting

Process reporting is the way in Boomi you can view details about processes that were executed including viewing Boomi documents and logs about the specific process executions. You can also manually execute a process outside of scheduled times here.

From the Boomi home page, navigate to Integrations.
Click on the Manage menu and select Process Reporting.
From here you can use many of Boomi's filtering tools to find the specific process you wish to view details about. By default, the list shows processes for the past hour but you can change that to the past day, week, or a custom date range.
When viewing the process reporting page, you will notice a status indicator icon.
Step Information
- Green – Process executed successfully.
- Red – Failed process.
- Gray clock – Process is currently executing.
Note:a successful execution does not necessarily mean everything ran without issues. There might be some occurrences where certain errors were triggered in the process like no data retrieved or invalid date to/from HTTP REST client API calls. You will need to search through the logging to try to determine that. This is like finding errors in the Cloud Inventory Platform Transaction Workbench.

For each process, you can click the document icon to view logging as well as download a copy of the logs that you can view in a text editor.

Please view Boomi's documentation around process reporting here: https://help.boomi.com/bundle/integration/page/c-atm-Process_reporting.html

NetSuite Process Information

The following section lists the main processes used for NetSuite/CI integrations.

(main) NS Replicate Items

This process replicates NetSuite items to the Item table of Cloud Inventory®. Lot, serial, assembly, and kit items are all replicated.

(main) NS Replicate Purchase Orders

This process replicates purchase orders from NetSuite into Cloud Inventory®.

(main) NS Replicate Sales Orders

This process replicates sales orders from NetSuite into Cloud Inventory®. Use this process the first time an order needs to be replicated to Cloud Inventory®.

(main) NS Replicate Sales Orders - Update

This process replicates updated sales orders from NetSuite into Cloud Inventory®. Use this process to replicate orders that have been modified in NetSuite when they already exist in Cloud Inventory®.

(main) NS Replicate Transfer Orders

This process replicates transfer orders from NetSuite into Cloud Inventory® as a sales order for outbound picking/shipping processing.

(main) NS Replicate Transfer Orders - POs

This process replicates transfer orders from NetSuite into Cloud Inventory® as a purchase order for inbound receiving processing.

(main) NS Replicate Vendor Returns

This process replicates Vendor Return Authorizations (VRMA) from NetSuite into Cloud Inventory® as a sales order for outbound picking/shipping processing.

(main) NS Replicate Customer Returns

This process replicates Return Authorizations (RMA) from NetSuite into Cloud Inventory® as a purchase order for inbound receiving processing.

(main) NS Replicate Work Orders

This process replicates work orders from NetSuite into Cloud Inventory®.

(main) NS - Post CI Transactions To NetSuite

This process post Cloud Inventory® transactions back to NetSuite. Cloud Inventory® transactions include:

Adjustments
Inventory Adjustments
Miscellaneous Issues
Miscellaneous Receipts
Cycle Counts (NS Adjustments)
Lot Split Adjustments
Inventory Transfer
Pick Confirm (NS Inventory Transfers)
Ship Confirm
Replenishment (NS Inventory Transfers)
Receipts
Putaway (NS Inventory Transfers)
WO Issues
WO Completions

Boomi Information

The Boomi Community is the place to go for all of Boomi's documentation as well community forums to search for solutions and report issues.

Boomi Community: https://community.boomi.com/

Boomi Training: https://train.boomi.com/

There was a problem loading this topic

Mobile Enterprise Platform