Best Of

Hi @User_QQ76D

Create a custom record (e.g., Custom Intercompany Staging) and create the following custom fields. 

1. From Subsidiary: custrecord_icto_from_sub (Type: List/Record > Subsidiary)
2. To Subsidiary: custrecord_icto_to_sub (Type: List/Record > Subsidiary)
3. From Location: custrecord_icto_from_loc (Type: List/Record > Location)
4. To Location: custrecord_icto_to_loc (Type: List/Record > Location)
5. Item: custrecord_icto_item (Type: List/Record > Item)
6. Quantity: custrecord_icto_qty (Type: Integer or Decimal)
7. Created Order: custrecord_icto_created_order (Type: List/Record > Transaction) (Uncheck 'Mandatory')
8. Error Log: custrecord_icto_error_log (Type: Long Text) (Uncheck 'Mandatory')

Save the following code as a .js file (e.g., UE_Create_ICTO_From_Staging.js) and upload it to your File Cabinet.

/**

• @NApiVersion 2 .1
• @NScriptType UserEventScript
• @NModuleScope SameAccount
• Description: Automatically creates an Intercompany Transfer Order when a Custom Staging Record is created via CSV or UI.
  */

define(['N/record', 'N/log'], (record, log) => {

const afterSubmit = (context) => {

    // Only run on creation of a new staging record (prevents duplicates if someone edits the record later)

    if (context.type !== context.UserEventType.CREATE) {

        return;

    }


    const stagingRec = context.newRecord;

    const stagingRecId = stagingRec.id;

    const stagingRecType = stagingRec.type;


    try {

        // 1. Get values from the custom staging record

        const fromSubsidiary = stagingRec.getValue({ fieldId: 'custrecord_icto_from_sub' });

        const toSubsidiary = stagingRec.getValue({ fieldId: 'custrecord_icto_to_sub' });

        const fromLocation = stagingRec.getValue({ fieldId: 'custrecord_icto_from_loc' });

        const toLocation = stagingRec.getValue({ fieldId: 'custrecord_icto_to_loc' });

        const item = stagingRec.getValue({ fieldId: 'custrecord_icto_item' });

        const quantity = stagingRec.getValue({ fieldId: 'custrecord_icto_qty' });


        // Validate that required fields are present

        if (!fromSubsidiary || !toSubsidiary || !fromLocation || !toLocation || !item || !quantity) {

            throw new Error('Missing required fields on the staging record.');

        }


        // 2. Initialize the Intercompany Transfer Order

        // We use dynamic mode so NetSuite automatically sources pricing, accounts, etc.

        let ictoRec = record.create({

            type: record.Type.INTER_COMPANY_TRANSFER_ORDER,

            isDynamic: true

        });


        // 3. Set Header Level Fields

        ictoRec.setValue({ fieldId: 'subsidiary', value: fromSubsidiary });

        ictoRec.setValue({ fieldId: 'tosubsidiary', value: toSubsidiary });

        ictoRec.setValue({ fieldId: 'location', value: fromLocation });

        ictoRec.setValue({ fieldId: 'transferlocation', value: toLocation });


        // Default order status to Pending Fulfillment (Optional - configure as needed)

        ictoRec.setValue({ fieldId: 'orderstatus', value: 'B' }); 


        // 4. Add the Line Item

        ictoRec.selectNewLine({ sublistId: 'item' });

        ictoRec.setCurrentSublistValue({ sublistId: 'item', fieldId: 'item', value: item });

        ictoRec.setCurrentSublistValue({ sublistId: 'item', fieldId: 'quantity', value: quantity });

        ictoRec.commitLine({ sublistId: 'item' });


        // 5. Save the Intercompany Transfer Order

        let newIctoId = ictoRec.save({

            enableSourcing: true,

            ignoreMandatoryFields: false

        });


        log.audit('ICTO Created successfully', `Staging ID: ${stagingRecId} | ICTO ID: ${newIctoId}`);


        // 6. Update Staging Record with the success link

        record.submitFields({

            type: stagingRecType,

            id: stagingRecId,

            values: {

                'custrecord_icto_created_order': newIctoId,

                'custrecord_icto_error_log': 'Success'

            }

        });


    } catch (error) {

        log.error('Error creating ICTO', `Staging ID: ${stagingRecId} | Error: ${error.message}`);


        // If it fails, update the staging record with the error message so the user can fix it

        record.submitFields({

            type: stagingRecType,

            id: stagingRecId,

            values: {

                'custrecord_icto_error_log': error.message

            }

        });

    }

};


return {

    afterSubmit: afterSubmit

};
});

Deploy the Script

1. Go to Customization > Scripting > Scripts > New.
2. Select your uploaded .js file.
3. Click Create Script Record and name it something like “UE Create Intercompany Transfer Order”.
4. Go to the Deployments tab.
5. In the Applies To dropdown, select your Custom Record (e.g., Custom Intercompany Staging).
6. Set Status to Released and Log Level to Debug.
7. Save.

I've managed to get this working following the below

https://www.tanwasripan.com/blog/integrating-copilot-studio-with-netsuite-ai-connector

Hope it helps.

Hi Vicki Bollinger

From my experience and customer feedback, NetSuite Automated Cash Application works best for high‑volume, straightforward transactions, especially when invoices and payments align cleanly on customer, subsidiary, and currency, but it still requires careful setup and monitoring. A noted limitation is that it does not allow generating payments against invoices in a secondary subsidiary or currency for multi‑subsidiary customers, which is a valid enhancement request for complex intercompany and global AR scenarios.

Hope this helps.

Initially I assumed that altering the address wouldn't affect the GL, allowing us to proceed with changing the address accordingly. However, upon attempting to do so, I discovered that updating the address for a closed period was not possible, even with the "Allow non-GL changes" feature enabled.

Do I need to reopen the account period just to update the invoice address? Is there a way to update the record without reopening the account period?

Thanks in advance.

Hi. @Bry Cabria-Oracle

There was an issue with the access role. I will let you know what I did to get over this issue.

Thank you,
Shubham Singh.

After our upgrade to 2026.1 we noticed that "Transaction Name" columns in saved searches are no longer a link? Name (customer) and Item both still function as a link to that record, and I checked a main line true and false search but neither allows the "Transaction Name" to be clicked.

Our team uses a lot of transaction line item views that are set to include a linked transaction (purchase order, item fulfillment, etc.). They can still use "View" in the leftmost column to link to the primary transaction of the result, but overnight all of the links to related transactions are broken.

I don't remember seeing anything about it in the release notes- is this an expected change? Or is there some hidden logic now that it is only a link if the search meets certain criteria? (similar to how inline editing is only available under certain conditions)

Hi @User_F2RD3,

Manuel here from NSAW support team.

This behavior is by design, not an environment issue.

While the NAW Licensed Author role allows users to create and share decks/cards, it does not include catalog administration privileges. Specifically, it does not grant the ability to:

• Create folders under /Shared Folders/
• Move content into Shared Folders (without write access)
• Manage folder-level permissions

The reason you’re seeing:

• No option to create a shared folder
• “OK” button disabled when moving content

is because your role likely does not have write access to Shared Folders, or you don’t have an elevated role such as BI Service Administrator.

To proceed, one of the following is required:

• Grant write access to a specific Shared Folder location
• Or assign a role with broader catalog permissions

Reference:
https://docs.oracle.com/en/cloud/saas/netsuite-analytics-warehouse/nsawa/administering-oracle-netsuite-analytics-warehouse.pdf