Complex Customer Hierarchy

Our institution is transitioning from 3 abstracted CRMs systems to SAP. Currently, we person duplicate lawsuit records crossed these CRMs due to the fact that each strategy is utilized for antithetic merchandise ranges.

The archetypal program is to support these duplicate/triplicate lawsuit accounts successful SAP, arsenic each account, though representing the aforesaid entity, often has antithetic payers, transportation addresses, and assigned income representatives. However, we're exploring if a much structured attack is possible.

Example of our lawsuit structure: 

We merchantability products to assorted schools nether the New York City Department of Education done antithetic contracts. In our CRMs, each schoolhouse isn't treated arsenic a azygous entity; instead, antithetic departments wrong the aforesaid schoolhouse are handled arsenic abstracted entities. 

For example:

1. The subject section of a precocious schoolhouse purchases laboratory instrumentality and is billed separately.
2. The diversion section of the aforesaid precocious schoolhouse besides buys from america but is treated arsenic a chiseled entity.

Ideally, we'd similar to operation our lawsuit hierarchy successful SAP arsenic follows:

1. Parent Account: New York City Department of Education
2. Child Accounts: Individual Schools
3. Sub-Child Accounts: Departments wrong each schoolhouse (e.g., Science Department, Athletic Department)

Questions are:

1. Is it imaginable to make this hierarchical operation successful SAP?
2. If so, tin each kid and sub-child relationship person its own:

• Sales representative
• Payer
• Delivery address
• Other unsocial attributes