Multi Subsidiary Inbound Support

You can create Multi Subsidiary transactions by setting subsidiary on inbound e-documents record.

There are two ways to set Subsidiary on inbound e-document record:

1. Manual Selection: You can choose the desired subsidiary through the subsidiary drop down which consists of all the subsidiaries available in the account on the inbound e-document record. If you choose a subsidiary other than the available ones, you will get an alert asking to choose an appropriate subsidiary.

2. Plugin Implementation: You can also implement the Custom Plugin as provided in the sample to automatically populate the subsidiary on creating the inbound e-document record using any of the available methods. The plugin should be provided in the e-document template record dropdown field 'Inbound Multi-Subsidiary Custom Data Source Plugin Implementation'.

After providing the subsidiary on the inbound e-document record or providing the plugin in e-document template, it will mark the inbound record as multi-subsidiary inbound record.

If the plugin execution is failed, or the plugin implementation shows an inactive subsidiary id or unavailable subsidiary id, the inbound e-document record will be created with the 'Incomplete' status.

There are two ways to update the status from 'Incomplete' to 'For Conversion':

1. You can update the plugin implementation, edit and save the inbound record. It will auto-populate the subsidiary on the inbound record with the subsidiary id in plugin implementation at the expected path.

2. If there are multiple inbound records with 'Incomplete' status, you can run the Map Reduce Script 'Update Inbound Subsidiary MR' by updating the plugin with an appropriate subsidiary. This MR will pick all the inbound records with status 'Incomplete', which have empty subsidiary field and plugin selected in e-document template record to populate the subsidiary Id by executing the plugin.

Plugin script:

          /**
 * @NApiVersion 2.x
 * @NScriptType plugintypeimpl
 * @NModuleScope Public
 */
define(['N/render'], function (nsrender) {
   
    function inject(params) {
        // the expected structure should be defined same as below,
        // as this path is used by EI script to fetch subsidiary details
            var customObj = {
              subsidiaryId: "1" // internal id of the subsidiary
            };
        
        return {
            customDataSources: [
                {
                    format: nsrender.DataSource.OBJECT,
                    alias: "subsidiaryDetails",
                    data: customObj,
                },
            ],
        };
    }

    return {
        inject: inject,
    };
}); 

        

General Notices