Hi Harsha,
The concept remains the same. I.E. in the condition table you shall have to introduce a field "Ship To", then put that condition table in your access sequence. The access seq you have to assign to a condition type. This condition type can be freight condition type or tax condition type or anything.
From another "side", user has to create master data (i.e. condition records) here user can give different values of condition types for different SH parties.
In short, it is all about setting up the condition technique properly (according to your requirements) and the business requirement can be satisfied.
ps - for those condition types in your pricing procedure that are not different depending upon the different condition types, user / configurer doesNOT have to introduce the field "SH" in the condition table.
| | | ---------------Original Message---------------
From: Harsha Halyal
Sent: Thursday, November 24, 2011 5:27 AM
Subject: Two Ship to Party
@ Typewriter
Your answer is justifiable when you doing it by considering base price(PR00) but in our case the price changes between two SH because of change in fright and change in tax so total pricing procedure changes between these two SH. How can we do this .?
@ Nishi & Rajesh
The price changes between two SH because of change in fright and change in tax so total pricing procedure changes between these two SH. How can we do this .? |
| __.____._ Copyright © 2011 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| |  Typewriter
SAP Logistics Sales and Distribution Helper
Posted helpful replies on 50 threads in a group to earn a Silver Achievement Popular White Papers
In the Spotlight SAP BusinessObjects: Dashboards and Analytics. Learn more about this Toobox.com Marketplace online course.   _.____.__ |
