Sap Sale Module: RE:[sap-log-sd] No Customer Master record exists for sold to party 961000005.

Posted by alokkt (Mr)
on Jun 19 at 12:03 PM

...this is the way it should be. This just shows that even for same customer system keeps as many customer masters as there are sales area. Thus the lesson from here is that we should keep our organization structure as minimal as possible because if we add more organizational units, master data multiplies exponentially
I have come across organizations that used four divisions in the first rollout, in the first upgrade they used just one. (means that much less master data. The next logical question is how they did divisional reporting and analysis if they had just one (product) division?....they used product hierarchy(hierarchy makes up for divisions). These are hard learned lessons ....there is no better learning then learning by mistakes ...
sorry for any digression
regards
alok
***the subtle and sublime logic comes late ...so wait

---------------Original Message---------------
From: Typewriter
Sent: Sunday, June 19, 2011 9:57 AM
Subject: No Customer Master record exists for sold to party 961000005.

Hi Jim, alokkt,

I tested as you advised -
In VA01, gave Order type & Sales area; in field "Sold To" gave Customer A which is not created for the sales area of my sales order. System takes 2 options -
1. Gives pop-up to choose one of the possible sales areas, if user accepts a "permitted" sales area, then the sales area of the sales order changes.
2. If you say no to 1, then system gives error message -

No sales area could be determined
Message no. VP102

If I am overlooking something, please advise.

Regards,

__.____._