Reply from Typewriter on Jan 24 at 12:06 AM Hi Dave,
Many thanks for your post!
Could you please answer, comment on the below points -
1. "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)."
Could you tell some of the areas in the sales document process, where ZH (copy of SH) would cause a problem?
With your input, I would do some tests and check those areas.
2. "is with a new custom partner type."
A ship-to party or a copy of SH comes under the partner type Customer KU. Why do you suggest to create a new customer partner type?
Please explain both from SAP "technical" perspective and from business logic perspective.
3. "user exits in both customer maintenance and document maintenance, to enforce the one-shipto limit on certain account groups."
- how exactly do I go forward with the suggestion - user exit in customer maintenance?
- when you suggest user exit in document maintenance, how does that impact the one-shipto limit for an account group?
Side by side, I shall do some tests with ZH and then entire OTC cycle (sales order, delivery and billing) to see if there are any issues with using something other than WE as Shipto party.
| | | ---------------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. __.____._ |  _.____.__ |
