Pricing Priority

My pricing requires the "shipping type" which is located is in the header, under the shipping tab. The pricing is successful but the problem is when this "shipping type" field is empty, the price is not pulled up and when you put the shipping type (after the material is provided), the price is not still pulled up. It seems that the you need to first put the shipping type before the material so that the configured price will be applied.
1. Is there a way to redetermine the price even if the shipping type is applied first (before the material)?
2. Or is there a way I can put that configure the shipping type to have value first before filling-up the material section? How to do it?
Pls help. Thank you.

Hi Anwar,
I have not tried the solution with incompletion log for the given problem. As I understand, your problem is determination of pricing at line item after change in value in header.
Generally, SAP performs some pricing redetermination for certain fields i.e. Change in Ship to party triggers the tax redetermination.
For the given scenario, an alternative solution is to implement userexit USEREXIT_NEW_PRICING_VBKD in MV45AFZB with the following code:
if vbkd-vsart ne *vbkd-vsart.
new_pricing = 'B'.
endif.
New pricing should be selected based on requirement which suits you. If you choose B, system will redermine the complete pricing including resetting any manual price change.
Regards,
Naveen Aggarwal

Similar Messages

Material price to be defaulted in shopping carts from Contracts in ECC

Hi Guys,
We are having a scenario wherein we need to get the price in shopping cart from contracts in ECC.In our case for a material only one contract exists for a given time frame in the ECC.We are working on classic scenario in SRM 5.5 as an add on to ECC.Any help to get this working will be highly appreciated.
Thanks in advance.
Regards,
Pawan.

Hi Pawan,
As long as you dont have the Configuration Step "Sourcing Via Vendor List activated", all contracts that you have created for a material will automatically show up in the source of supply as the proposed SOS. This and Info records are displayed on the SOS tab on the SRM Shopping cart via an RFC call that Standard SRM Does.
Pls try out a scenario:
1.) Create a contract for a material in ECC
2.) Replicate the material in SRM
3.) Create a Shopping cart in SRM with that material
4.) you will automatically see the contract beoing displayed on the SOS.
Following are the pricing priority in SRM.
Price Determination in EBP
Priorities
1.) Manual price (only if field is open for input)
2.) Contract
3.) Catalog
4.) Price from product linkage or from product
So as long as you dont have a manual price for the Shopping cart, the price will be adopted from the contract. i would suggest for materials with contracts, update the s/c price with the BBP_DOC_CHANGE_BADI at the time of submission with an RFC call to ECC to obtain the right proce from the contract.
Hope this info helps !!
Pls assign points, if answer helps you
Sundeep

Price from Pur Info record not picking up

Hi All,
We have a requirement to pick Price from Purchasing Info record for Standard Cost estimate (CK11N/CK40N).
The purchase info record has been created and price maintained in both u201CNet Priceu201D and u201CEffective Priceu201D fields in info record.
I have selected Strategy L Price from Purchasing Info record and maintained sub-strategies 3, 4 and 5 in Valuation variant:
Strategy 3 u2013 Net Quotation Price
Strategy 4 u2013 Gross Quotation Price
Strategy 5 u2013 Effective Price from Quotation
Though I maintained the above, system is not picking up price from info record in CK11N.
Am I missing anything on this?
Any help is appreciated.
Thanks.
Regards,
Sree

Sreechakravarty,
Per your description, system picked up the price other than the Purchase Info Record price, right? If so, you can try to remove other pricing priorities while only leave the pricing priority "L", and then run CK11N again to see whether system can find the info record, otherwise system will give error message such like "can not find material price in plant code &1/batch &2".
If the system do can not find the purchase info record, you should check anything wrongly maintained to the info record such like valid period. Make sure the valuation date you entered during CK11N should be within the valid period of the info record.

Manual Pricing for configured materials in Sales Order

We use variant config for our goods produced and the pricing results from what is configured. Thsi works fine.
However, occasionally there is a need to replace this pricing with a manual price entered into the Amount column on the order line. The PR00 condition comes in OK but we find that if changes are made then the configured prices are re-applied as well so the order line ends up with 2 types of pricing in effect.
How can I stop this happening i.e. to get SAP to use only the manual pricing if a price is entered into the Amount field?
Thanks
Jim

Jim
Are you sure that you are using PR00 for configurable mat, Ideally it should be VA00
Leaving that aside, if you keep the condition type as Manual entry as priority or No restrictions, in the Manual entries, then when the automatic entries are overwritten by manual entries, only one record will exist and the automatically updated record will no more be in the screen. Please try it.
There is also a OSS note for this, though I dont knwo the number. You can try for it.

SALE ORDER PRICING

Hi gurus,
I was created one sale order.While i want to give the Taxes mandatory.ie vat -4% 12.5%etc... and cst percentage give to mandatory. is it possible?
Regards,
T.Murugu

Hello Muruga,
Yes you can maintain VAT and CST condition types as mandatory condition types in your pricing procedure through these settings
-->Go to V/06 Transaction select your condition types then go in to the details of the condition type here you can find the field called Manual entries under Changes which can be tab
Maintain this field as B Automatic entry has priority
-->Go to V/08 transaction then select your procedure then go in to the control data here you check the Mandatory for VAT and CST comdition types.
Maintain the condition records properly to those condition types.
Now system will take those values automatically while creating sales order.
I hope it will help you,
Regards,
Murali.

Pricing value not to editable in billing creation

Hi experts,
I have checked the posts to find how to make the Pricing not editable when creating invoice {in VF01}, but cannot find the correct post that suits my req.
Our business req is to allow user to change it in sales order creation,though we create condition records via Vk11, still we keep it open in the Sales order creation.
The requirement is only to grey out all values for all condition types that are copied from Sales order.
What should be the correct Pricing Type to be used in VTFL for delivery to billing copy control.
In V/06, for Manual entries we use C - Manual entry has priority &
Amount/percent is selected & Value is not selected.
Please advice.
Rgds,
Pri

Hi Priya,
I might be totally wage, in my approach, but:
why don't you use Two different Pricing Procedure - One, in Sales Order; and Another, in Invoicing.
Assign, both Pricing Procedure to, Sales Order and Invoicing, in T. Code: OVKK, respectively.
Also, make a Z-Copy of Condition Type (say, ZPR0 - a copy of PR00) and maintain Condition Type (in T. Code: V/06), i.e.
_Untick the Box: Amount/percent, for ZPR0 in V/06, it will be greyed out in billing, whereas, mark tick at Box: Amount/percent, for PR00.
Maintain, similar Condition records for PR00 and ZPR0, in T. Code: VK11.
Best Regards,
Amit

Pricing error in intercompany billing

My client is using the intercompany billing process.
There is a BOM item with item category group LUMF and the pricing happens at sub item level. In the sales order and the customer billing document the pricing happens at sub item level only.
But in the intercompany billing the pricing happens at both main item and sub item levels. The pricing procedure is dfferent here.
Both the sales pricing procedure and intercompany pricing procedure has the condition type ZI11. The requirement 22 is attached to the condition type at both the pricing procedures.
In the intercompany pricing procedure, subtotal L is assigned to the condition type ZI11.
The condition type ZI11 is configured as under.
Access Seq : ZI11
Condition class : B (Prices)
Cond category : C (Qty)
Rounding rule : commercial
Manual Entries : B (Automatic entry has priority)
Item condition
Amount / percent
Int-comp Billcond
Can anyone tell me why the item is priced at both main & sub item level in the intercompany billing.
Regards,
Bala

Hi,
Please check with the defination of the Item cateogry for the Main Item for the InterCompany Invoice.
The relevance for pricing should be ticked off.
Reward points if it helps.
Regards,
Harsh

Problem with new pricing procedure - free of cost

i set up a new pricing procedure where i have zsed (special excise duty) and zmws (sales tax) set as manual, it's not valid on some free sample orders. but when i goto create order it does not show up under conditions, even though i've maintained it for that material in vk11. and when i click on condition type in conditions, it doesn't show up in the drop down either (at the order level). if i just type zsed it says zsed cannot be processed manually.
but if i change the pricing procedure and take off the manual check mark, the tax shows up on the same order automatically (from vk11) but i can't delete it there.
suggestions? i need for it to show up or have an option where if it shows up i can delete it. thanks!

fyi,
If you set the "Manual" indicator in pricing procedure against to any condition type, then you can enter this condition type value in particular transaction. ( But for this condition type details, " changes can be made- setting maintain as "D" not possible to process manuall). Same "manual" logic in the pricing procedure will not work.
Because controls in Condition type has priority than anyother.
Now coming to your question,
If I understood it properly,
ZSED is not applicable to every free of cost order, but it may be applicable to other orders ( excl: FOC orders). Expecting ZSED Condition type maintained in both pricing procedures ( FOC sales pricing procedure & non FOC sales procedure).
if you set the " Manual entries has priority"/ tick mark delete check box in ZSED, then it will allow to enter manually/delete the condition type in FOC order as well as non FOC orders too.
Then there could be chance that user may delete/manually enter ZSED in non FOC sales.
better way would be, create new conditiont table by including Sales document type ( assume you created new document type for FOC sales) with other required fields ( eg: customer/material etc..,).
assign this condition table in top of all the accesses in ZSED's access sequence.
Maintain Condition record.
By doing so, Condition record is applicable only to FOC doc type sales- if maintained , else it will search next condition record.
which will not effect the non FOC sales & user cant delete ZSED from non FOC sales.
Hope it helps

Explain the Pricing Procedure

Hi Friends
Explain how the pricing is determined for an item, starting from the sales order
Discuss the full cycle also make a mention on the Condition type controls, and Maintain pricing procedure controls.
Kindly explain it with an example.
Thanks

Pricing Procedure is indeed an heart of SD module, reason being if everything else is working fine, but price is not being calculated correctly, the purpose of billing fails.
An Overview of Determination & Configuration of Pricing Procedure is as follows:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Determine Pricing Procedure.
Step 5: Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

Pricing procedure execution...

Hi Folks,
How SAP reads the pricing procedure..
Example
Con.Type      Requirement        Routine
ZSAA            601                     901
ZSAB            602                     902
Doubt 1: -Is system reads this pricing procedure line by line or coulmn by column?, In the debug we noticed it goes column by colmun? why?
Doubt 2: - I want to know the value found for ZSAA during the execution of 602 requirement. Example scenario is if ZSAA is more than 100$ don't execute ZSAB.

Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.

How to copy Value of fright from pricing procedure to the tax procedure

Dear All,
Please note, I have a condition type in Pricing procedure i.e. ZRCO-this is for fright which will be added by the user in the PO.
I want to copy the same value to ZRC1 which is a condition type in tax procedure.
Kindly advise, is there any way we can do this automaticaly. My requirement is to add the fright to the gross price while caluclating the VAT in tax procedure.
Rgds,
Raghavendra N N

Hi,
There is a Field for Manual entries in configutration for Conditions : Condition Types.
Manual Entries Indicator which controls the priority within a condition type between a condition entered manually and a condition automatically determined by the system.
Make the following entries according to your requirements:
_: No limitations
A: Freely definable
B: The automatic entry has priority. If a condition record exists, the condition cannot be entered manually.
C: The manual entry has priority. When you enter the condition manually, the system does not check whether a condition record exists.
D: Cannot be processed manually
Hope this will help.

How to design a Pricing Procedure with both MWST and MWSI in it ?

Hi there.
My business requirement dictates that I can have both Tax inclusive(PR01/MWSI) and Tax Exclusive(PR00/MWST) items within a Single Sales Order.
I know that One pricing procedure can only be assigned to 1 Document Type. So,
Has anyone successfully created a Pricing Procedure that incorporates both the MWST and MWSI tax components ? If so, could you post a sample of the pricing procedure in order for me to understand how I should group the discounts/surcharges and reflect the Subtotals, as well as incorporate the MWST and MWSI all within a single Pricing Procedure ? I will also need to include the PR01 and PR00 conditions into the procedure too, right ?
Really really hope someone with the experience, can aid me on this. I cannot find any relevant materials on this matter, both in OSS Sapnotes and within this forum.
regards
Poo

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Similarly in MM Module we have Pricing Schema.
Regards,
Rajesh Banka
Reward points if helpful.

11i Advanced Pricing Questions on usage of Item Category Segment Values

Hi All,
we are on 11i, i am trying to setup on modifiers using Item Categories. Customer has 4 segment category structure.
Category structure= Vendor, Group, Style, Price code , here is how Data looks = 060.10.800.40
In 11i, can we setup Modifiers on Segment1 & Segment 2 ( 060.10), so system picks up all values for segment3 and segment4.
I understand R12 can do this as per Metalink Note: 746020.1. is this supported in 11i.? I am unable to accomplish this.
regards
girish

Hi
Please donot post more questions in a single thread. If you post it separately, you will get many responses and detailed explanations from more members.
Regarding your queries.,
1. Relevant for delivery field in Item Category is for TEXT Items and for others you should configure the field in Schedule lines.
3. Shipping conditions will be defaulted from the CMR of SP. If a value exists in the sales document type (eg. OR) then it will have priority and will replace the value defaulted from CMR.
5. The pricing applies to Item Level only. But you cannot determine different procedures for different line items.
6. Header conditions will not have access sequence and you cannot create condition records for header conditions in VK11.
7. In consignment process - the first two steps are mandatory i.e., Consignment fillup and consignment issue.
The other two steps are required only if there are returns from the customer(not consignee) and if there are any unsold stocks at the consignee.
Thanks,
Ravi

Pricing schema for purchase info records

hi guys!
does anyone knows either SAP standard got function to define pricing schema for PIR? if yes, can you please tell me how to set it up step by step?
Thanks a lot,
crystal.

Hi,
there is no separate pricing schema for reading info records.
When creating PO, the system first searches for a purchasing
info record with the combination of vendor/material at purchasing
organization/plant level. If there is no such info record, the system
then search at purchasing organization level. If there is no such
info record here either, you must enter it manually.
If the purchasing info record exist, then valid conditions have
priority during price determination. If an info record does not
contain any conditions or invalid conditions, the system read from
last purchasing document in the info record and then suggest the price
from here. The price determined in this way are default values that
can be changed by the buyer if necessary.
You can save useful quotation data for a material in purchasing
info record. The info record can be created automatically by
setting the info update indicator during quotation maintenance
in the item detail.
Please first check is there any valid info record exist for this
material/vendor. You can always create/change/view it manually
via Ta ME11/ME12/Me13.
Please read also the notes 392988, 456691.
Regards,
Edit

Varient condition is not picked in the pricing procedure.

Dear Friends,
I am creating a sales order where, I am getting a message that VA00 condition is not determined. I analyze the pricing,and find out that the condition record is not determined by the system. Message number is 106. I already maintained the condition record for VA00.
Thanks,
Abhishek Kumar

Hi,
Only if you have created the variant and assigned the same in VK11 then the system will fetch that during pricing
otherwise for VA00 manual entries has a priority so you can add the condtion type manually and give the value to it manually.

Pricing Priority

Similar Messages

Maybe you are looking for