What kind of problems we will get into if we will ...
# ask-stanley-ai
n
What kind of problems we will get into if we will start creating separate departments for other subsidiaries with same name
c
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. ****** Creating separate departments for other subsidiaries with the same name can lead to several issues: 1. Duplication of Departments: In NetSuite OneWorld, departments are shared between subsidiaries, similar to the chart of accounts. If you try to create a department with the same name for each subsidiary, you will encounter an error message stating that the name already exists. This is because departments are not subsidiary-specific but are shared across the entire organization. 2. Data Management Issues: If you manage to create departments with the same name under different subsidiaries, it could lead to confusion and data management issues. It might be difficult to distinguish between departments of different subsidiaries if they have the same name. 3. Subsidiary Management Issues: If you are using OneWorld, be careful about what subsidiary you pick as “primary” / “legacy” for any pre-OW data. All your customers might get stuck in the wrong subsidiary and there’s no good way to get them into the right one. You cannot change the primary subsidiary of a customer record once they have transactions associated with them. This could lead to issues if you are using departments to structure your brands instead of subsidiaries. 4. Access and Permissions: Something being at the parent level doesn’t automatically mean that people with access to sublevels get access to that record. You would have to explicitly grant access to data at the parent level too. It doesn’t inherit permissions. So any customer is basically 'stuck' to a subsidiary once it is created. You need access to that subsidiary to do anything related to the customer. 5. Legal and Leadership Decisions: Whether or not to have a separate subsidiary is really a legal/leadership question more than an accounting one. If you want them to be an independent legal entity then you need to account for it accordingly (create a subsidiary). If the intent is to shut down the other entity entirely and have everything under one legal entity, then you should have everything under one subsidiary. In conclusion, creating separate departments for other subsidiaries with the same name can lead to duplication, data management issues, subsidiary management issues, access and permissions issues, and may require legal and leadership decisions.
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.832242668
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.811488628
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.806679547
Please provide your feedback on this answer.