Comparing Impacts to Database for CRM "Consumer" customer vs "Sold-To"

Question

What is the database impacts of creating "Consumer" customers (Account Group 0170) vs "Sold-To" customers (Account Group 0001)?
Scenario:  Mulling over web-enabling functionality that would come through CRM and replicate to R/3.  Anticipate around 50,000 new "customers" (consumer) to be created in a year.
Concern has been raised that this would have a large impact on the database.  Currently, we only have 20,000 active Sold-To customers, so the number is a bit daunting for some.
I know that Account Group 0170 customers only create a KNA1 record in R/3, as opposed to the creating records in KNA1, KNB1, KNVV, KNVP, etc. which happens in R/3.
The question put to me is what will this impact be? 
If we create 50,000 new consumer customer records, is this equivalent to creating only 10,000 new Sold-To's?  Is it equivalent to 20,000 new Sold-To's?  Is there some sort of standard?
How would I measure this?
Any thoughts are greatly appreciated.

Answer 1

Dear Tom,
You are aware, CRM system is used for all pre-sales processes. These pre-sales processes can be considered to be over when we create an order in CRM. This is because generally all orders flow back to R/3 and are processed further in R/3.
Thus creation of consumer vide ISA or web u2013enabling functionality is nothing but a presales activity. Once the consumer is created, one should validate the sanctity  of the consumer. Once itu2019s confirmed that the consumer is genuine and can be converted to Sold to party,  create a new BP with in SP role. Now transfer only this BP to R/3 (A/C group 0001) . Why unnecessarily load R/3 system with consumers data when its of no use in R/3 transactions. This way you restrict data creation in R/3. Keep consumers in CRM system only. In CRM they can be archived periodically.
Please let me know if this helped you in answering your question.
Regards
Dinesh