list the prerequisites, oneworld dependencies, and configuration tasks that are needed to complete subsidiary implementation.

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** To complete a subsidiary implementation in NetSuite OneWorld, you need to consider the following prerequisites, OneWorld dependencies, and configuration tasks: Prerequisites: 1. A clear understanding of your company's structure and how it will be represented in NetSuite OneWorld. 2. A plan for how to handle existing data, especially customers and transactions, as these will be tied to a primary subsidiary and cannot be easily moved. OneWorld Dependencies: 1. Subsidiaries: In OneWorld, a subsidiary is required on all transactions and entities. Some will default from the primary subsidiary of the vendor or customer, but others will need to be manually selected. 2. Primary Subsidiary: Be careful about what subsidiary you pick as “primary” / “legacy” for any pre-OneWorld data. Once a customer or transaction is associated with a subsidiary, it cannot be easily moved to another subsidiary. 3. Access and Permissions: Access to data is controlled at the subsidiary level. Staff will need access to a subsidiary to see its data. Access does not automatically inherit from parent to child subsidiaries. Configuration Tasks: 1. Enable OneWorld: This can be done in both production and sandbox environments. However, it's recommended to test in a sandbox environment first. 2. Set up Subsidiaries: Define your company's structure by setting up subsidiaries. This includes selecting a primary subsidiary for pre-OneWorld data. 3. Configure Access and Permissions: Ensure that staff have access to the necessary subsidiaries. This may involve granting access to multiple subsidiaries or the parent company. 4. Handle Existing Data: Existing customers and transactions will be tied to their primary subsidiary. If necessary, create duplicate records and merge them to move them to the correct subsidiary. Remember, once OneWorld is enabled and subsidiaries are set up, it can be difficult to make changes. Therefore, careful planning and testing are crucial to a successful implementation.