on 11-01-2011 7:08 AM
The requirement is ( for TAN), same pricing proc should flow from SO to invoice. But 2 c.types are NOT updating (calculating) in
invoice.
Right now, pricing type configured is G.
with G, the two condition types are NOT getting updated/calculated in invoice.
But with pricing type B, those 2 C.types are getting updated/calculated in invoice. ( which is exactly the requirement)
Now, the client DOES NOT want to use B.
The 2 c. types are :
'FOB Price' -
Cond. class B Prices
Calculat.type C Quantity
Cond.category (blank)
Rounding rule Commercial
StrucCond. (blank)
'Frieght & insurance'
Cond. class A Discount or surcharge
Calculat.type B Fixed amount
Cond.category F Freight
Rounding rule Commercial
StrucCond. (Blank)
Request any expert to guide me on this urgently.
Rgds
Sumanth.G
Hi,
Your above solution was an absolute bulls eye for one of my problem in account determination.
I am facing another strange problem which is as below
Scenario
Delivery w/o reference to order
Delivery captures pricing accurately.
Post PGI when tried to bill the delivery, the pricing elements are not getting transfered to the biling document (checked in the conditions screen of the billing document).
The copy control is set as per SAP standards. i.e LO (del w/o order type) TO F2 ( Del related billing type)
Even tried ti maually update the condition in the billing doc screen but system gives error " Condition ZPRC is missing in pricing procedure A V"
Please suggest.
Regards,
Sachin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since for both the condition types, the condition class is different, definitely, both the condition types should flow into your sale order.
If it is not flowing, you need to check in condition tab by clicking the "Analysis" button.
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Sumanth,
But with pricing type B, those 2 C.types are getting updated/calculated in invoice. ( which is exactly the requirement)
Now, the client DOES NOT want to use B.
While using B, whether the remaining conditions are getting updated?
If so , can you give the reason why business doesnt want to use B.?
Is there any specific reason for the same (ie, is it affecting any other condition types)
Check and revert back.
Thanks & Regards,
Hegal K Charles
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Jignesh
current pricing type: G
'Analysis' at invoice item level: ( for condition types)
'FOB Price'- Condition has been found (without condition record) Alt cal tyope :12
'Frieght & insurance ' - Condition has been found (without condition record) Alt calc type :903
**
with G (in SPRO) - at invoice, item level, "condition value" column (1st column) ( not "condition amount') is NOT getting calculated.
so, users are "manually updating" with pricing type :B at invoice item level.
Rgds
Sumanth.G
Edited by: SUMANTH GURURAJ on Nov 2, 2011 10:27 AM
Dear Jignesh
To make it more clear
FOB Price = 'Base Price' - (sum of ' frieght' & 'insurance')
The above logic is in Alt calc Type :12 & is assigned to 'FOB Price' in pric proc.
'Frieght' & 'insurance' are MANUAL HEADER conditions.
Now, with G,
at header level in invoice, when we enter 'frieght' & 'insurance' manually, the 'FOB Price' is NOT getting calculated. ( in 'condition value' column).
With B, the 'FOB Price' is getting calculated' ( as described above)
The problem, is the client does NOT want to use B ( for below mentioned reasons)
with B, only the current billing date is considered.**
*The client wants SO PRICING DATE ( which G is fulfiling) ( but G hs limitation, as explained above)*
Any other pricng types, which u suggest?
or shall I try to insert a condition category to 'FOB Price' (which is blank now)
Request an expert to kindly guide me on this.
Immediate help would be appreciated.
Rgds
Sumanth.G
Edited by: SUMANTH GURURAJ on Nov 2, 2011 3:25 PM
User | Count |
---|---|
101 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.