Page tree
Skip to end of metadata
Go to start of metadata

The following items are the primary considerations for setting up Organizations within Unanet:

 

Introduction: The term Organization is used in Unanet to represent a number of similar but distinct foundational elements. An Organization can represent your organizational tree including corporate entities such as business units, divisions, departments, groups, and subgroups. It can represent your customers (those whom you are charging for your goods and services) and your vendors (those whom you are paying for their goods and services). All organizations whether internal (People Organizations or Project Owning Organizations) or external (Customer/Project/Vendor Organizations) are managed in a single list. These are organized through the creation of a hierarchy and by setting their Organization Type. For example, internal organizations such as business units, divisions, and departments may all reside under the same organizational tree and have a common Organization Type of INTERNAL. Customers may all live under an organizational tree called CUSTOMERS and have a common Organization Type. The example below demonstrates the concept of Unanet organizations for a company called ACME. A key concept to remember is that all of these organizations are managed in the same set of screens in Unanet.

 

  • ACME (all of the organizations below this hierarchy have an Organization Type of INTERNAL)
    • ACME-SE
      • ACME-SE-FINANCE
      • ACME-SE-IT
    • ACME- SW 
      • ACME-SW-PROFSERV
      • ACME-SW-SALES
    • ACME-NE
      • ACME-NE-CYBER
      • ACME-NE-SALES
  • CUSTOMERS (all of the organizations below this hierarchy have an  Organization Type  of CUSTOMER)
    • IBM
    • RAYTHEON
    • SEARS
    • JCREW
  • VENDORS (all of the organizations below this hierarchy have an Organization Type of VENDOR)
    • CYBERTECH_SERVICES
    • SIGNS_R_US
    • DB_CONSULANTS_INC

 

Once Organizations are set up, they are associated with other Unanet structures. For example, an employee in Unanet belongs to a specific organization based on where they work and what they do. In our example, a professional services employee working out of the Southwest region will belong to the organization ACME-SW-PROFSERV. When the organization is used in this context, it is referred to as a Person Organization.
Just as employees fall within a specific node in the organizational tree, so do projects. In fact, each project may have two organizations: one which is the internal grouping or "owning" organization and one which is the external customer grouping or Project Organization.  
  • The organization that "owns" a project is generally the organization that assumes the costs and revenue of the project and holds the "Remit To" information for billing purposes. In this example a project might be "owned" by ACME-SW-PROFSERV. Unanet calls this type of organization the Project Owning Organization.
  • ACME's customers are also set up as Organizations in Unanet. When used in this way, customers are referred to as Project Organizations (different from project owning organizations).  

Similarly, vendors are referred to as Vendor Organizations.

Finally, when using Unanet Financials, a Financial Organization represents a legal entity for which a separate set of books is maintained for the various departments, regions, and divisions within the legal entity. The designation of Financial Organization is a flag on the organization itself. All Person Organizations (for employees but not contractors) and all Project Owning Organizations must be organizations which have been designated in the organization profile as Financial organizations. 

Description:

Organizations are used in Unanet for reporting and restricting access.

  • Reporting: Organizations are a primary and key reporting field. In creating any report, the first thing the report criteria will ask you for is if you would like to filter by organization. As a result, you will typically set up your Organizations to represent such external and internal entities as customers, internal divisions, departments, or lines of business.
  • Restricting Access: Organizational relationships are helpful for restricting access since users can be assigned organizational access to any or all of the organizations within a given org tree. 

Organizations can be displayed in a list view.

Navigate: Organizations > List.

 


Additional Information:

Help Docs - Organization


  • No labels