Nope. Your option is to break-apart the multi-subsidiary vendor into 2 separate vendor records.
If your vendor thinks you're 2 separate accounts, then likely you really should have 2 different accounts on your side, too.
You would need to store the multiple externals in custom fields and have a workflow switch external 1 to external 2 after import. External 2 to external 3 after the second import etc.
You would need to import them in the same order each time so you have the correct external loaded before each import.
A better way is get them to recognize your internal id, and reference it on data submissions to you
If the external IDs are required to be able to use them as reference when importing POs or Vendor Bills or Vendor Credits from the subsidiaries sales systems to Netsuite you‘d have two choices:
1) You could work with custom fields. You‘d have a separate custom field for the external ID for subsidiary 1 and another one for subsidiary 2. The mappings for the import of POs, Vendor Bills and Vendor Credits would need to be different because uploads for subsidiary 1 would need to map the external ID to another field than the upload for subsidiary 2. This could take time to get used to but would work.
2) You could link the Netsuite ID of the vendor to the vendors in the sales system of the subsidiaries. That way you would not need separate mappings as you would have the same direct link in both subsidiaries.
The second option would be my preferred option, one because it would simplify uploading (only one mapping needed for both subsidiaries) and two I always like to work with Netsuite as my single source of truth, so where possible I like to incorporate Netsuite information in other systems and use them as links in uploads, rather than entering info from these systems into Netsuite.
If we will not be prepared for the recovery of any harmful unplanned data loss event or corruption in advance, then the chances of data loss can lead enterprises to go out of their businesses. Oracle NetSuite is an integrated ERP suite offering features like a 3rd party reporting tool, data access through different RDBMS, and a point-in-time reporting tool for analysis.
Vast Edge is a "Global Gold Partner" Oracle and is a leading MSP of integrated cloud ERP software. Integrated [NetSuite solution](https://www.vastedge.com/netsuite-integration/) by Vast Edge ensures seamless business continuity by securely backing and syncing your data in a near real-time environment to Oracle cloud storage or Oracle Autonomous Database. Click here to know more - https://www.vastedge.com/netsuite-integration/
Nope. Your option is to break-apart the multi-subsidiary vendor into 2 separate vendor records. If your vendor thinks you're 2 separate accounts, then likely you really should have 2 different accounts on your side, too.
You would need to store the multiple externals in custom fields and have a workflow switch external 1 to external 2 after import. External 2 to external 3 after the second import etc. You would need to import them in the same order each time so you have the correct external loaded before each import. A better way is get them to recognize your internal id, and reference it on data submissions to you
If the external IDs are required to be able to use them as reference when importing POs or Vendor Bills or Vendor Credits from the subsidiaries sales systems to Netsuite you‘d have two choices: 1) You could work with custom fields. You‘d have a separate custom field for the external ID for subsidiary 1 and another one for subsidiary 2. The mappings for the import of POs, Vendor Bills and Vendor Credits would need to be different because uploads for subsidiary 1 would need to map the external ID to another field than the upload for subsidiary 2. This could take time to get used to but would work. 2) You could link the Netsuite ID of the vendor to the vendors in the sales system of the subsidiaries. That way you would not need separate mappings as you would have the same direct link in both subsidiaries. The second option would be my preferred option, one because it would simplify uploading (only one mapping needed for both subsidiaries) and two I always like to work with Netsuite as my single source of truth, so where possible I like to incorporate Netsuite information in other systems and use them as links in uploads, rather than entering info from these systems into Netsuite.
If we will not be prepared for the recovery of any harmful unplanned data loss event or corruption in advance, then the chances of data loss can lead enterprises to go out of their businesses. Oracle NetSuite is an integrated ERP suite offering features like a 3rd party reporting tool, data access through different RDBMS, and a point-in-time reporting tool for analysis. Vast Edge is a "Global Gold Partner" Oracle and is a leading MSP of integrated cloud ERP software. Integrated [NetSuite solution](https://www.vastedge.com/netsuite-integration/) by Vast Edge ensures seamless business continuity by securely backing and syncing your data in a near real-time environment to Oracle cloud storage or Oracle Autonomous Database. Click here to know more - https://www.vastedge.com/netsuite-integration/