Sales pricing procedure

Hi,
In 000 client i have checked sales pricing procedure jinfact where for all tax components accounting key exd has been given is there any special purpose for doing like this.
And also i want to know how to copy the same to 800 client.
thanks in advance.
SAP_CIN

Hi,
scc1 is used to copy users from one client to another
while sccl is used to copy data from one client to another
Regards,
Srinivas Muthyala

Similar Messages

Consignment Sales - Pricing Procedure

Dear Experts,
is pricing procedure of Consignment Sales difference than Normal Sales. if somebody can provide a expert opinion and any note url link for Consignment Sales Pricing Procedure.

Hi,
Pricing Procedure will be same for CONSIGNMENT Process and Normal Process.
In the CONSIGNMENT based on the flow, for some scenarios the pricing is not required.
This can be controlled in the OVKK transaction
In Consignment goods are goods which are stored at the customer location but which are owned by the company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer can usually return consignment goods that are not required.
Consignment Fill-Up: Consignment fill-up replenishes the stock at the customer site. Since the goods remain the property of the company, this process is not relevant for pricing and consequently not for invoicing either.
No Invoice triggered in this scenarios
Consignment Issue: The Consignment issue enables the customer to withdraw consignment goods from the special stock that are to be used or sold.
Since the goods are moved from the customer stock, Invoice will be generated to Bill customer
Consignment returns: Consignment returns enable your customer to return goods to the consignment stock that has already been issued from it.
In this process, we have to credit the customer
Consignment Pick-Up: The company uses consignment pick-up to take back consignment goods that are faulty or excess materials that the customer does not need. This process is not relevant for billing since the goods remain the property of the company.
please revert bakc if you frther details,
thanks,
santosh

Problem of DIFF (Rounding Off) Condition Type in Sales Pricing Procedure

Hi All,
This problem is related to Sales Order. The system is not picking up a condition type in the pricing procedure.
For example when I am raising a sales Order where the Trade Price is being calculated with the help of a Alternative Calculation Type , Subtotal 1 , X in the the Print column and Posting Key ERL are assigned to it.Here in the end the condition type DIFF is not getting populated in the pricing though it is maintained in the pricing procedure. When I am checking in the pricing analysis the error message and its detailed description which is shown as follows -
DIFF 011 Condition ignored (requirement 013 not fulfilled)
The requirement 1. was assigned to this condition in the pricing procedure. This requirement was not met in the preliminary condition step, and so the condition was excluded from further processing.
You can use Additional information to display the requirements used.
Now considering the above scenario please suggest to attain my requirement.
Thanks & Regards
Priyanka

Dear Priyanka,
The "reqt" field in the pricing procedure basically tells d system that the routine mentioned in this field is a sort of prerequisite without fullfilling of which the associated condition type will not get xecuted.
In ur case u have selected "1" which is for condition types A001, B001 etc used in "material listing / xclusion" function.
For condition type DIFF, the correct value is "13" i.e "Rounding as per T001R".
So just replace "1" with "13", things will b fine.
Please close the thread if answered.
regards
Param

Want to updated sales pricing procedure through quotation

Hello Friends,
In general scenario: we update any condition type in vk11 tcode and tht is reflected in quotation pricing.
my requirement : while creating quotation if the user changes any price for any condition tht should automatically get updated in pricing procedure for tht particular condition type.
pls suggest how it is possible??
Regards,
Sunny

Hi Sunny,
you can write exit in VA21 to update the sales pricing .
Thanks & Regards,
Devalla T Kumar

Config required for EK02 condition type in Sales Pricing procedure

Dear friends,
I am trying to derive a costing run for sales order. I would like to know what are the config steps required to arrive a percentage factor for GP.
Kindly guide me in this regard,
Thanks in advance,
Vinayak

Hi,
If you are doing sales order costing then you will have to define the condition type EK02. Go to V/08. Select the Procedure used in SD. Click on Control. Enter the condition EK02 - Calculated Cost and mark it as statistics.
You sales order cost will be stored in such condition type.
Regards,
Jigar

Sales Pricing Procedure : Statistical Condition type and Reqt.

Hi,
I wish to know what else is the use of marking the condition type statistical except the ones i know. (a) now included in the final price. but will be seen in the condtions (b) Can be used to send that value to a particular account.
What is the use of the following routines in the Reqt. field and what do they do
a. (2) - Item with Pricing. Now in this routine it check "prsfd". which is field called carry out pricing in the table.
Can someone explain me how this works. Also if you can explain how these subroutines genrally work. It would be great.

Hi Dheeraj,
What you told is correct that Statistical Condition means that the condition item is ignored. In other words, no flow records are generated in the cash flow.
While regarding Requirement, it is pre-requisite to take that particular Cond type (to which it is assigned) into consideration while carry out pricing.
Like in your case Requirement "2" (item with pricing), the condition type(s) to which it is assigned would be taken into pricing only when item has pricing attched to it.
Regards
SD

Trading Sales Pricing procedure

Hello Experts,
We have multple plants
Plant A, B and C are manufacturing plant
Plant D is Trading plant
we are doing intercompany sales and direct purchase fron Supplier in all plant includibg trading plant.
In Trading pland (D) purchasing material from Vendors, capturing Excise duties in RG23D Register and passing the same duties to customer while selling the material in practically.
we are creating sales order then outbound deliveries, with reference to outbound deliveries doing J1IJ for refering excise invoice from RG23D.
Its taking proper excise duties as per standard calculation. But...
while creating VF01 Billing the captured excise amount in J1IJ transaction is not flowing in Billing (VF01).
i want the same amount in VF01 which is captured in J1IJ transaction.
Please guide to how to link.
Regards,
Ajay

Not sure still what exactly you expecting from my end. As already asked, you need to go to VF02, input that billing document and execute. There again go to condition tab, select the tax condition type and double click on that. Now you can see a tab popping up where some tax code is there. Make a note of it and go to FV12, input those CIN condition types and check whether for the given combination, the same tax code is maintained.
G. Lakshmipathi

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

Difference among different pricing procedure

Hi,
I want to know that, what is the difference among different pricing procedure,Like
Standard,return,sample,scrap and credit memo.
Please reply soon.
Regards
prabudh

Hell tiwari,
<b>**Please Do reward if it helps**</b>
sales org + dist chan + div + document pric proc + cust pric proc --- > Pric Proc.
we determine the pric procedure. So, just have a different document pricing procedure for sales order document type and invoice document type. You can have a different pricing procedure with this change.
There are two simple reasons for making any Pricing Procedure in SAP SD Modules.
1) Business Reason. What are the pricing aspects or strategies you want to apply for the client requirement in order to sell their
goods or render services, is all about the reason for various pricing procedures.
Eg: Domestic sales pricing procedure,
- Export Pricing Procedure,
- A rebate pricing procedure or
- A High Discount oriented pricing Procedures.
- A repair pricing procedures.
You have your own conditions intended to few transactions only. Put all this conditions as a set defining your own Procedures. It may even include special requirements and formulas applied for such Pricing Procedures.
2) A special pricing procedures, in order to facilitate added functionalities of SAP pricing architecture, we must define new
pricing procedure. SAP Standard programmes checks these special Indicators in-order to do some required functions.
As a example 1, you need to have a Pricing procedure for condition supplement inorder to use the condition supplements. The condition supplement pricing procedure must be given in the condition type definitions (v/06) of the Pricing Condition where you need to supplement, without which SAP SD Condtion Supplements functionality doesnt work.
As a example 2, you need to have a Pricing procedure for Inter Company Billing Conditions(IV01 & IV02) inorder to be active for Inter Company Billing specific transactions. Thus make sure that, the procedure wouldnot apply for non-Inter company transactions.
Eg: KA0000 for Condition Supplement for KA00
- PR0000 for Condition Supplement for PR00
- ICAA01 for Inter-Company Billing
In V/08 of defining a new Pricing Procedure, in main screen, you have a field called TSPP (Transaction Specific Pricing Procedure). This has to be ticked on for Intercompany Billings.
The SAP help reads for this field as Under: Transaction-specific pricing procedure
Pricing procedure transaction-specific indicator
Before Release 4.0A, no special pricing procedures were used for intercompany billing and rebate credit memos, programs were just set accordingly to deal with these situations. As of Release 4.0A you are offered greater flexibility in the form of the option to define special pricing procedures for intercompany billing and rebate credit memos. For reasons of future compatability, you will still be able to use the old program specifications. For this reason, you must set this indicator if you want to create a special pricing procedure. This is to prevent the program settings being used.
This indicator is also used as of Release 4.0A to redetermine the condition class and the statistical condition indicator when copying from a reference document.
Example:
You copy prices from a shipment document to the billing document. The prices should lead to a surcharge in the billing document. This is guaranteed by the redetermination of the condition class in the pricing procedure.
Same case with Standard Pricing procedure or Inter Company Pricing Procedure.
Regards
AK

VAT in Pricing procedure

Dear all
Actually I want to add condition type ZVAT as a vat- tax in my pricing procedure
How can I add condition record for it ?Because once I add in VK31 at that time error comes
TAX CODE IN THE PROCEDURE TAXINJ IS INVALID
Can any body guide me!!
jayesh

Dear Jayesh,
I think you are talking about error message FICORE704, aren´t you?
In relation to tax and how it should be configured, please see the information below:
In the pricing procedure, RVAXUS, the condition records for condition type UTXJ determines the tax code for a given line item. Condition records read indicators on the customer and material master records to determine the tax codes. Condition records are stored in condition
tables and read based on the sequence specified in the access sequence.
Since the tax calculation procedure is stored by tax code, determination of the tax code triggers the call to the tax calculation procedure.
Condition types XR1-XR6 are used with the external tax calculation procedure (TAXUSX) while JR1-JR4 are used with the internal tax calculation procedure (TAXUSJ).
The primary goal of condition type UTXJ is to determine the tax codes so the tax calculation procedure can be accessed. TAXUSJ needs to have tax code and jurisdiction to access the tax calculation procedure.
TAXUSX only needs the tax code to access the tax calculation procedure.
All subsequent tax levels (XR1, XR2 or JR1, JR2) in the procedure are automatically filled with the respective tax rate/amount. XR1 or JR1 equals the region (state) tax rate, and XR2 or JR2 equals the county tax rate, and so forth.
UTXJ initiates the tax calculation in SD by determining the tax code.
Other condition types for taxes in SD are XR1-XR6 for TAXUSX and JR1-JR4 for TAXUSJ.
Tax condition type UTXJ is linked to access sequence UTX1. One of the tables defined to UTX1 is condition table 40 which has a definition consisting of country, region, customer tax indicator and material tax
indicator.
When using TAXUSJ, the tax code from this condition record along with the tax jurisdiction are sent to the tax calculation procedure where the tax rate is stored. The tax rate is sent back to the sales pricing
procedure.
When using TAXUSX, the tax code from this condition record could be sent directly to the third party tax package. An option on the tax code determines if the third party tax package will be called.
Please see note 388112 which details how to change a pricing procedure on a production system. It is not specifically for adding UTXJ, etc but for general changes.
See note 392696 - R/3 Tax Interface Configuration Guide
I hope this information is helpful!!
Regards
David Merino

Relation between Pricing procedure &Tax Proc , how the whole procedure work

Hi Gurus,
I need want to know in detail , How a pricing Procedure is linked to the FI Tax procedure and how the whole mechanism work .
Pls clarify and explain me the whole process , As i have seen that the Tax condition type we maintain in pricing , we alos mentioned in Taxinj and step is also given in FTXP .
So pls give me more clarity on this
Regards
Umang

For A /P tax condations , tax amount posted to accounts from tax procedure.
For A/ R taxcondations ( which condations we are using in sales pricing procedure)
tax amount posted to accounts from sales pricing procedure
It is helpful give rewards points
Regards
Raj

Change sales pricing (VK11) automaticaly while creating sales quotationVA21

Hi friends,
Anybody can say that which BAPI can be use to change in pricing procedure for quotation
Exactly my requirement is as when the user enter the sales quotation ( in VA21 ) they put the price but when the price is changed than it should automatically maintained in sales pricing procedure in VK11.
Thanks & regards,
Devalla T Kumar
Edited by: Devalla Tarun Kr. on Dec 26, 2008 8:02 AM

>
Devalla T Kumar wrote:
> Exactly my requirement is as when the user enter the sales quotation ( in VA21 ) they put the price but when the price is changed than it should automatically maintained in sales pricing procedure in VK11
> Edited by: Devalla Tarun Kr. on Dec 26, 2008 8:02 AM
So
1) They manually enter a price condition in VA21 = Do Nothing
2) They change a previously entered price condition while still in VA21 = Execute T-Code VK11 and create a record for it.
You still need to provide more info, and ask more questions.
What if the user entered the price incorrectly? You are going to create a master record in VK11 in the system of that.
What if another user enters a price at the same time as another user? Price records have date validity.
What should happen in Change (ala VA22) mode ? If they enter/change the price record then, should you create another record ? This will not be valid for any prior Quotations; or should you change teh existing record, back dated to the original creation date, and then update all previous quotations that contain this record?
You are going to need to provide more detail here, as these are only a couple of situations that can occur and may need to be dealt with somehow

Various pricing procedures

hello SD Gurus, please provide various examples of pricing procedures which are normally used

hi
commonly used pricing procedures are Standard ,Customer specific and document specific
There are two simple reasons for making any Pricing Procedure in SAP SD Modules.
1) Business Reason. What are the pricing aspects or strategies you want to apply for the client requirement in order to sell their
goods or render services, is all about the reason for various pricing procedures.
Eg: Domestic sales pricing procedure,
- Export Pricing Procedure,
- A rebate pricing procedure or
- A High Discount oriented pricing Procedures.
- A repair pricing procedures.
You have your own conditions intended to few transactions only. Put all this conditions as a set defining your own Procedures. It may even include special requirements and formulas applied for such Pricing Procedures.
2) A special pricing procedures, in order to facilitate added functionalities of SAP pricing architecture, we must define new
pricing procedure. SAP Standard programmes checks these special Indicators in-order to do some required functions.
As a example 1, you need to have a Pricing procedure for condition supplement inorder to use the condition supplements. The condition supplement pricing procedure must be given in the condition type definitions (v/06) of the Pricing Condition where you need to supplement, without which SAP SD Condtion Supplements functionality doesnt work.
As a example 2, you need to have a Pricing procedure for Inter Company Billing Conditions(IV01 & IV02) inorder to be active for Inter Company Billing specific transactions. Thus make sure that, the procedure wouldnot apply for non-Inter company transactions.
Eg: KA0000 for Condition Supplement for KA00
- PR0000 for Condition Supplement for PR00
- ICAA01 for Inter-Company Billing
Here I would like to remind about a important field in pricing.
In V/08 of defining a new Pricing Procedure, in main screen, you have a field called TSPP (Transaction Specific Pricing Procedure). This has to be ticked on for Intercompany Billings.
The SAP help reads for this field as Under:
Transaction-specific pricing procedure
Pricing procedure transaction-specific indicator
Before Release 4.0A, no special pricing procedures were used for intercompany billing and rebate credit memos, programs were just set accordingly to deal with these situations. As of Release 4.0A you are offered greater flexibility in the form of the option to define special pricing procedures for intercompany billing and rebate credit memos. For reasons of future compatability, you will still be able to use the old program specifications. For this reason, you must set this indicator if you want to create a special pricing procedure. This is to prevent the program settings being used.
This indicator is also used as of Release 4.0A to redetermine the condition class and the statistical condition indicator when copying from a reference document.
Example:
You copy prices from a shipment document to the billing document. The prices should lead to a surcharge in the billing document. This is guaranteed by the redetermination of the condition class in the pricing procedure.
Same case with Standard Pricing procedure or Inter Company Pricing Procedure.
to view different pricing procedure u can proceed through the t-code<b> V/08</b>
Message was edited by:
SHESAGIRI GEDILA

Freight costs in Pricing procedure and Shipment costs

What is the difference between freight costs in pricing procedure for a sales document and shipment costs in shipment documents. Arent they meant for the same thing. Why do we have to create them separately.

hello, friend.
freight charges in the sales pricing procedure may be represented by condition type KF00 (standard). this condition type is a surcharge to your customer, meaning there is an inflow into your company. this surcharge may be manually entered (if configuration allows this) in the condition tabs of your sales order or this could automatically be entered if the appropriate condition records (via VK11 or VK31) have been created.
the shipment costs in shipment documents is what your company is billed or quoted by your forwarder, shipper or other transport related agent. the shipment cost data will be used by the system to calculate and settle shipment costs. when you have freight condition records (via TK11), purchase-vendor records and if all route/connection point/etc. settings correct, all shipment cost data will be determined when you do shipment cost document creation. you may also manually enter cost items, depending on the configuration.
hope this helped. is so, will appreciate reward.
regards.
jty

Reg:Getting MAP into Sales Pricing Calculation

Hi Gurus,
Could you provide information to get the Moving Average Price into the Sales Pricing Calculation in IS Retail?
Regards,
R.K

Hi,
Please configure condition type VPRS in your Sales pricing procedure and mark it as statistical.
Then allow the cost calculation indicator in your Item catogry definition.
Please maintain the same and check with the sales order pricing.
It should pick up the Standard price or Moving average price from material master.
Reward points if this helps.
Regards,
Harsh

Sales pricing procedure

Similar Messages

Maybe you are looking for