Reply from Typewriter on Jan 26 at 11:03 AM Hi Dave, Alfred, Thank you! Without having partner function SH (WE) in the partner procedure (in the partner procedure there is ZH) assigned to the sales document type the sales process can NOT be completed In VA01, the field "Ship-to party" KUWEV-KUNNR is remaining blank. During the creation of delivery too, with out WE, the following error is populating - Goods recipient missing in partner det. procedure Conclusion - Without partner function SH (WE) in the partner procedure of CMR, Sales document type, Delivery type etc. (e.g. and also according to business requirements of the client) sales process can NOT be completed. PS - I have marked both your posts as helpful.
| | | ---------------Original Message--------------- From: Dave Thornburgh Sent: Monday, January 23, 2012 3:05 PM Subject: Partner Function SH Already Exists TW - I think you have fairly well investigated this, and correctly determined that you cannot have SH unique in one PDProcedure, and also have it non-unique in another. Your only way to proceed, then, is with a new custom partner type. Ultimately, though, I think you'll find that this won't work in the case of SH. There are a great many areas in sales document processing where the code looks specifically for the SH party (actually, in the database it's represented as WE internally). The logic of SD requires that you have the WE partner function, and it doesn't have a mechanism to figure out what custom partner function you might be trying to use in its place. To make a long story short (too late), your best bet would probably be to investigate the use of user exits in both customer maintenance and document maintenance, to enforce the one-shipto limit on certain account groups. Dave | | Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today. _.____.__ |