Save Rma

As part of Export processes, the Rma Export process also has two parts. The first part is located in a Plugin \RocketWeb\NetSuiteRma\Plugin\Magento\Rma\Model\Rma::aroundSaveRma() and it has a simple workflow. If conditions:

Module is Enabled
Feature is Enable
Is not marked to be skipped, and
Is not exported before (doesn't have netsuite_internal_id)

are all met, an Export Queue Message is created with Rma Id attached to it & sent into the Queue.

Initializing NetSuite Rma in NetSuite

According to the NetSuite workflow, we need to initialize the Rma before creation. In order to achieve this, the NetSuite Connector sends Initialize Request with Invoice Id. For details see - \RocketWeb\NetSuiteRma\Model\NetSuiteRmaRepository::initialize(). This request returns either success, with Rma created, or error.

Transform Magento Rma into NetSuite format

The transformation of the Magento Rma into NetSuite format is different from similar scenarios for other entities. The main difference is Initialize Request. In fact, the transformation process is the editing of the Rma returned by it (see: Initializing NetSuite Rma in NetSuite). During transformation, the NetSuite Connector updates the Items list.

For details see - \RocketWeb\NetSuiteRma\Model\Process\Export\Service\RmaPrepare::prepare()

Adding NetSuite Rma to NetSuite

Since we have Rma updated in the Export Mapper, the NetSuite Connector builds an Add Request and sends it to NetSuite. For details see - \RocketWeb\NetSuiteRma\Model\NetSuiteRmaRepository::add().

Updating Magento Rma

In case of a successful Add Request, the NetSuite Connector updates the Magento Rma entity with netsuite_internal_id to avoid further exporting, and the Magento and NetSuite entities become linked.

Browser not supported