RE: [sap-log-sd] Partner Function SH Already Exists

Reply from Dave Thornburgh on Jan 24 at 5:44 PM
TW -

For point 1, I don't really need to go much further than SAPMV45A, form KUWEV_SELECT_POSITION. There are a great many spots in order processing that require the structure KUWEV to be filled with details from the shipto partner. The very first statement in this form (which fills KUWEV) is "perform xvbpa_lesen(sapfv45k) using 'WE'". In other words, SAP has exactly one idea of what a shipto is, and you cannot extend that concept because they hard-coded it in the logic.

On point 2, I meant a custom partner function, not type. In other words, I was referring to what you had already proposed.

For 3, talk to your ABAP resource about finding user exits in the programs that maintain customers - like XD01. In the user exit, if the account group is allowed only one SH according to your business rules, then throw an error if the user violates the rule. In document maintenance, the impact depends on what you code. Obviously, SH will need to be marked not-unique so that some account groups can have multiples. Your user exits will need to enforce uniqueness for the limited account groups.


---------------Original Message---------------
From: Typewriter
Sent: Tuesday, January 24, 2012 12:07 AM
Subject: Partner Function SH Already Exists

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.

Reply to this email to post your response.
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
Copyright © 2012 and message author. 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Dave Thornburgh  
16 achievements
Mark as helpful
View this online
Ask a new question
In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements