Import meterial pricing procedure steps, accruvals doubt in freight conditi

pls guide me , what steps are involved to import meterial in pricing procedure?
accrols and account keys maintain for freight conditon types , both we have to maintain or only one? if maintain in automatic account determination maintain same G/L ACCOUNT number will maintained or different no's will be maintained?

Hi Sai
Your import pricing procedure shall contain the following:
1) Delivery costs for Custom clearance
- Custom duty
- CVD
- Ecess on CVD
- SEcess
- Ecess on customs
- Addl custom duty
2) Delivery cost for agent charges
3) Local freight charges
All the above condition types are delivery costs only.
For every condition type, you will maintain the vendor, so that the respective condition delivery costs can be processed based on the document.
As soon as the material received at port, you will do MIRO for all the duties
By the the material reached banglore, you will do goods receipt.
The local freight can be processed based on the requirement (either before GR or after).
warm regards
sairam akundi

Similar Messages

CIN pricing procedure steps

Dear SAP's
Can any one send me the screen shots for Cin pricing procedure configuration on domestic sales, deemed export sales and export sales.
my mail id is [email protected]
thanks and points will be rewards if useful
regards,
Reshmi

Hi reshmi,
please do send me the CIN install steps and study material to [email protected] ,it ll be grt helpful to me thanks in advance
Regards
Balaji

Notes or patch for Import/STO pricing Procedure.

Hi All..
I want to copy Import -JIMPORT and STO pricing procedure.
I am having RM0000 only.
I am in ECC6 but its not there.Can you pls tell me the patch or notes that i have to apply to get the Import pricing procedures.
Earliest help will be useful.
Thanks
R.Kanann..

Hi Sai
Your import pricing procedure shall contain the following:
1) Delivery costs for Custom clearance
- Custom duty
- CVD
- Ecess on CVD
- SEcess
- Ecess on customs
- Addl custom duty
2) Delivery cost for agent charges
3) Local freight charges
All the above condition types are delivery costs only.
For every condition type, you will maintain the vendor, so that the respective condition delivery costs can be processed based on the document.
As soon as the material received at port, you will do MIRO for all the duties
By the the material reached banglore, you will do goods receipt.
The local freight can be processed based on the requirement (either before GR or after).
warm regards
sairam akundi

Pricing Procedure : steps between 2 condition types

Dear Members,
please let me know,
In the pricing procedure, I don't have space between 2 steps. i.e step 120 and 121, however I would like to introduce a step inbetween then with a new condition type (discount).
can i use the counter step, I am getting a warning message that , this can only be used for manual condition.
please let me know, what is the best way to achieve this ..
Thank you
Anitha

Hi,
In my opinion, counters works good if the sub-steps are used to add value to the main step.
Sometime ago, I was in the same situation and I changed the step numbers in the existing procedure. That created a mess in the old documents. I was forced to run some programs to open all the old documents and re-save so that correct pricing was maintained.
My suggestion would be copy the existing program and rename to a new program. Change the steps numbers and insert the condition types as you wish, then assign the new procedure in the pricing settings.
There are few OSS notes available, please check before you touch anything in the pricing procedure. For example check OSS Note 388112 - Change of pricing procedures in the production system
Regards,

Pricing Procedure Configuration steps with screenshots

Hi,
Can anybody send screenshots as per above said subject.
The main reasion now I am working in implementation project.
If you are able to give your contact no,I will be greatfull to you.
Regards
ramakrishna
9618087321

You can confi. new Pricing procedure and can go for pricing manually or automatic. If you need pricing automatic you have to go for use of Access Sequences and Schema Group of Vendor. You can customize your pricing procedure according to your requirement such as like Domestic, Import and Stock transport.
For the above individually you have to configure Pricing Procedure and the following steps are:
SPRO->MM->Purchasing->Conditions->Define Price determination process
1. Define Condition Table:
2.Define Access Sequence,
3.Define Condition Type,
4.Define Calculating Schema,
5.Assign Calculation Schema, Access Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organization,
8.Assign Schema Group Of Vendor to Purchasing Organization,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
10.Assign Vendor to Schema Group Of Vendor (XK02)
11.Maintain Condition record(MEK1)
After above steps , you can go for create PO in ME21N.
In the case of Import PO, you have to activate Import PO.
SPRO->Materials Management -> Purchasing -> Foreign Trade/Customs ->Control Foreign Trade Data in MM and SD Documents ->Incompleteness Schemas for Foreign Trade Data .
For more check the links:
http://**********************/2008/09/price-determination-process-or-pricing.html
http://www.scribd.com/doc/7149675/Steps-for-MM-Pricing-Procedures
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
Please refer the following threads
Pricing Procedure for PO
pricing procedure steps reg.,

Excise duty in the Pricing Procedure for Local Purchase / Importation

Hi,
I'd like to know how to set up the pricing procedure for the purchase of an IS Oil Material; for local purchase and importation, especially with regards to the excise duty posting.
Local purchase: the vendor will bill us inclusive of the ED tax he previously paid, so the tax is just passed on to us.. My receiving location has ED paid status. In the PO item, we need to see this price (inclusive of tax) in the net price field.
Importation: the vendor only bills us the cost of the material. When we received the fuel, we paid ED tax to local tax authorities.
I know that both in these scenarios, the system has to determine the excise duty.
My questions are (1) how do you set up the excise duty condition type in the pricing procedure(or do they have to be maintained in the pricing procedure?) ? and (2) how do you set up this condition type in the config?
Thank you and hoping for your immediate feedback.
zccr

Hi,
You can use same pricing procedure
put 4 in subtotal in pricing procedure against the Discounr or freight cond
and in taxinn
BASb ALTCBV 362 and for jmop 363
But this will work only if same discount or freight value is in IV as that given in PO
if freing value changes in IV then its a problem
This is SAP bug, and SAP workes in that way only, freight value should be same in PO and IV
other solution
in taxinn create tax code like v8 vat 4% for 003 tax clasification
in ftxp create tax code V8 desc vat 4%
in fv11 for jvrd put 4
and at the time of IV put this tax code for freight amount
and for regular material value V1 tax code
this will work only if u have used acess seq MWST instead of JTAX pr JST1
hope this helps
Vipin

Step number in the pricing procedure

Hi experts,
Pls advise the reasons. How to solve them without changing the step number?
Q1: As long as HM00 is the first step number in the pricing procedure, the value of HM00 cannot be distributed among items.
Example:
Pricing procedure:
step no.         conditon type
10                      HM00 (statistical)
30                      NETW (ERL)
Sales order (HM00 = $100):
item 1     NETW = 0
item 2     NETW = $100
Q2: When putting a conditon type between PR00 & subtotal in the pricing procedure, such as VPRS, the value of subtotal cannot be the same as PR00.
Example of sales order:
PR00 (unit price) = $19.95 per 10kg
VPRS (internal price) = $10 per 1kg
subtotal = $2 per 1kg
Request: PR00 = subtotal = $19.95 per 10kg

hello, cathy.
i do not have access to my references now, but please allow me to advance a general concept.
in SAP standard, HM00 is a group condition, and fixed value. the distribution of this value is controlled by certain logic. as in other header condition types, distribution of this amount can be based on either the value or quantity contribution of the different sales order items.
what serves as the basis for distribution of HM00, i do not recall but i will get back to you on this... or perhaps another consultant can give it sooner.
as to your second issue, i will try to understand your situation better. but generally VPRS is statitical and not meant to come between PR00 and the sub-total. VPRS has a different logic compared to the other condition types, and is intended to return a statistical presentation of profit margin in the condition tabs. if fact, in pricing procedure RVAA01 you will notice that VPRS is grouped with the other statistical condition types just before the profit margin.
regards.

Run out of step numbers in the Pricing Procedure

Hello gurus,
Has anyone come across the following situation: Within the pricing procedure I want to insert a new condition type but there are no 'free' numbers available within the procedure steps to enable me to do this
e.g: These are the steps in the Pricing Procedure
Step     Cntr     Ctype     Description
290     0     ZLTS     Type1
293     0     ZLTD     Type 2
296     0     ZDIF     Type 3
297     0     ZLEX     Type 4
299     0          Net Value Before Tax
300     0     MWST     Type 5
302     0     ZWR2     Type 6
303     0     ZWR3     Type 7
My new condition type should be applied on the Net Value Before Tax and before VAT (MWST) but there is no available step number i.e Net Value Before tax = step 299 and MWST = 300.   i.e new condition type should go in between 299 and 300.   Any ideas of how to get around this?
Many thanks in advance....

hi,
you can shfit 299 0 Net Value Before Tax to 298, but you need to check all the alternative calculation types if any susbsequent condition is making us of this step in their calculations. We, use the step numbers(STUNNR) in our alternative calculation types, so if you change their number or sequence you will disturb the calcuation of other pricing conditions.
so please evaluate from that angle.
regards
sadhu kishore

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.

Inclusion of two condition types in pricing procedure

Dear Sir,
There is a import pricing procedure ZIMPRT in SAP system.The client wants to include two condition types
ZPOR= Port handling charges
ZFCP+CLEARING AND FORWARDING CHARGES.
iIs it possible to do so.I?
What are the factors I need to consider for iincorporating two condition types in Import Pricing Procedure
Regards
Manash Das

Hi,
Yes you can do it & as needed you can includes two condition types {ZPOR (Port handling charges) and ZFCP (CLEARING AND FORWARDING CHARGES)} in import pricing procedure ZIMPRT. As already have condition types in import pricing procedure ZIMPRT, you need to take care following:
1.u201CStepu201D for both condition types ZPOR & ZFCP (position of the both condition types) in which sequence and exactly where both of the conditions with in a import procedure
2.u201CFromu201D: Which is base to the both condition types ZPOR & ZFCP for calculating further value.
3.u201CFrom & Tou201D: What are the ranges between the steps from and to can be used to specify the range between both condition types.
4.Both condition types ZPOR & ZFCP are preferred for manual entry or automatic.
5.Both values of condition types ZPOR & ZFCP are needed to be given deletion option, if needed.
6.Both condition types ZPOR & ZFCP needed accounting key & accrual key or not which further needed to be captured all related respective cost to separate G/L account( where accrual key assigned to G/L account in OBYC t.code)
Regards,
Biju K

Pricing procedure (Jurisdiction based)

Dear Experts,
We are setting up the pricing procedure for USA with Jurisdiction code and the pricing procedure is YBUS02. We created one Tax code for all Jurisdiction codes and while creating the Tax code.. we maintained the Tax rate as "100%" for JR1, JR2, JR3 and JR4. And then maintained the exact tax rate in VK19 for each Jurisdiction codes such as CA0010000 = 5%, CA0011000 = 4%, CA0012000 = 3%.   But after maintaining the tax rate in VK19, the Tax rates are getting changed in FTXP instead of 100%.
Could you please confirm whether this is right procedure or what could be the reason for getting changed in FTXP.
Thank you.
Regards,
Mani

HI Mani,
Please review your process like the follow recommendation:
1) The tax jurisdiction conditions (JR1,..., JR4) have to be maintained
   with condition type (KNTYP) '1', '2', '3', '4' in SD and on FI side.
   Look also at FI side:
   SPRO:
   -> Financial Accounting
      -> Financial Accounting Global Settings
         -> Tax on Sales/Purchases
            -> Basic Settings
               -> Check Calculation Procedure
                  -> Define Condition Types
Please maintain the correct entries on FI side and the deepest
    level for tax jurisdictions (BSET-TXJDP) will be filled correctly.
2) The sequence of the pricing procedure is very important.
   A statistical condition should never be included into the tax base.
   Furthermore the FROM-TO step of the tax conditions has to be
   referenced to the last subtotal line.
   Otherwise the tax code will not be transfered corretly and the
   tax base would be incorrect.
   The tax conditions JR1, JR2, JR3 and JR4 need to have the manual
   flag in the pricing procedure (T683S-KAUTO). Otherwise two condition
   types would be available in the document. For your reference you
   could use the standard pricing procedure RVAJUS.
   The account keys should be adjusted to the ones that were maintained
   in FI, transaction FTXP.
I hope it can help you to solve the issue.
Regards
Ruy Castro

Pricing procedure i

hii Experts
I know how to configure pricing procedure in MM
Now some experts can tel me how i can develop more knowledge MM pricing procedure in SAP.???
what is best way to become good in pricing procedure ....
Explain me the way with some some future examples ...
Thanks

Hi,
Access sequence:* An access sequence is a search strategy with the aid of which the SAP System searches for valid condition records of a certain condition type from the valid table and fetches the value in PO. *Condition type:* The condition types are used to represent pricing elements such as prices, discounts, surcharges, taxes, or delivery costs in the SAP System. These are stored in the system in condition records. Basically in Pricing procedure there 16 step/ column which are their own importance in pricing procedure the derive the value based on this configuration. Would like brief each and every field as under. *Step:* Number that determines the sequence of the conditions within a procedure. (This starts calculation based on from and to) *Counter:* Access number of the conditions within a step in the pricing procedure. During automatic pricing, the system takes into account the sequence specified by the counter. Ex if you are having freight condition type it is be possible to have different freight combination as per qty freight, fixed value freight & freight % on gross in this case you can have same from but o,1,2 different counter as whichever is applicable system will draws this condition fro step & counter. *Condition type:* The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount, gross, freight, *Description:* Description of the condition type. *From:* Condition step, the value of which is the basis for percentage surcharges. If you specify a to reference step at the same time, the condition values of the two steps specified and the conditions values of the steps in between are totalled. *To:* Condition step up to which the condition values of the previous steps are totalled. Percentage surcharges are calculated on the basis of the total. If you specify a from reference step at the same time, the condition values of the two steps specified and the condition values of the steps in between are totalled. *Manual:* Conditions, that are given this indicator in the pricing procedure, are only included in determination either if they are entered manually, for example, on the condition overview screen in Pricing or if they are transferred from an external process. Here user has to enter the value system will determine automatically *Requirement:* Indicates whether the condition is mandatory when the system carries out pricing using this pricing procedure. For example, you always want to include a tax condition (VAT or sales tax) during pricing; you can set this indicator for the appropriate tax condition type. *Statistical:* This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value or adding to the value Ex; if Gross + discount+ freight= 1000 this is statistical value). *Print:* Controls issue of condition lines when printing documents such as order confirmations or invoices. *Subtotal:* Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored. If the same fields are used to store different condition amounts, the system totals the individual amounts. Ex if you wish to add freight to the Gross then taxes on the gross have to use subtotal 4 condition value of which will added to the gross. *Requirement:* If the requirement is fulfilled then output determination also takes into consideration output type or the access sequence, for which the requirement has been specified. *Calculation type:* Alternative formula to the formula in the standard system that determines a condition. *Condition base* calculation: Formula for determining the condition basis as an alternative to the standard. *Account key:* Key that identifies different types of G/L account. The account key enables the system to post amounts to certain types revenue account. For example, the system can post freight charges (generated by the freight pricing condition) to the relevant freight revenue account. *Accruals:* Key which identifies various types of G/L accounts for accruals or provisions. Hope this helps you.
Edited by: Shubham RT on Aug 17, 2010 1:53 PM

Different Tax base in pricing procedure for a single sales order for different line item material.

Hi,
I have a scenario wherein in a sales order, for two different material, the tax base of pricing should get triggered on the basis of sold to party and the material entered at line item level.
Logic triggers on the basis of Region of Customer & a unique field in the Material Master but problem comes in the calculation of Tax base as the sequence of condition type (from – to) is already defined in the pricing procedure to pick from a particular step but in second line item the base is different i.e. the sequence of condition types that are maintained in pricing procedure should be different for Tax to calculate differently.
Kindly suggest if the same can be handled in a single pricing procedure and dynamically taking care of condition type sequence through Alt Cal Base Formula, so far I’ve tried both Alt Cal Formula & Base but it is not working
Client doesn’t want to go ahead by creating two different orders (through separate Pricing Procedure) for that. They want to have both materials in same order.
Kindly suggest a suitable way to handle this scenario.
Regards,
Aashika Agarwal

Hi,
Click on the ''check availability'' button at item overview and then click on ''One-time delivery'' on the top. This will ensure that you will have only one delivery for whatever quantity is confirmed on that date.
If you want to apply this rule for all orders across a sales area, then you can do the below configuration step :
SPRO->sales and distribution->basic functions->availability check with ATP logic->Define default settings-> Here in avail. checking rule select A (one time delivery). This will ensure that all orders created for a particular sales area will have only one delivery.
Hope this helps.
Regards,
Palani

Pricing Procedure could not be determined

Hi..
basic doubt -- but causing issue.
I have assigned the combination of sales area + Doc. Pric Proc + Cust Pric -- > Pricing Procedure in customizing.
customer pric prc. -> assigned to BP sales area , billing data (Also seen on Prices tab of transaction)
Doc pric proc - > assigned to the transaction used.
Sales area of transaction -- > same as used to assign pric proc
Still error creating transaction - TA standard order, Message no. CRM_PRIDOC_COM401 - Pricing Procedure Could not be determined. Also the error says to assign a pricing procedure to the combination of sales area + doc pric proc + cust Pric proc which I have already done.
But on the prices tab of transaction I cant see the "Pricing Procedure" and a blank screen on Conditions Tab of transaction.
any clue.. pl help

Hi,
Please check again if your SALES AREA at header level is picked correctly and which matches with the SALES AREA in the PRICNG procedure determination
ALSO if the above is maintained correctly, it might happen that you have created the transaction earlier then you have assigned the sales are to the Customer along with the BILLING tab information.
Run one report
HRBCI_ATTRIBUTES_BUFFER_UPDATE
If you have done the second one then just delete the customer, assign any other customer with which this issue would not appear and the error would go. Now again delete the customer and reassign your previous customer and check.
Regards
Surendra More

Pricing Procedure (Debit Memo)

I have a pricing procedure at oder level let suppose ABC, I made delivery and billing all is well till that.
Than if delivered quantiy is less than the target quantity client will suppose to create a debit memo sort of penality to the customer, reference to that invoice quantity confirmation source is POD.
My debit memo pricing procedure is different from ABC, mean a PROO and MWST is appear on that not other charges or condition type.
I have assign the procedure at debit memo sales document type but what happen when in VA01 give the reference of invoice and copy the item the whole same (ABC) pricing is came up on the order (Debit Memo Request) which is not required I want the actual procedure will call.
If after this i directly go to the billing document after approval of this document my actual pricing procedure is there, but a different condition type is present in the 2nd pricing procedure that will not come, so I manually press the "Carry out new pricing" so that condition type than will appear..
Hope my gurus understand the problem. I want that actual pricing procedure is available at order if not that all the condition type will appear at the time of billing. I cant set the carry out new pricing setting in the copying control because if i done this the whole condition type of order will aappear at billing as well.
if have any query please feel free to ask.
Regards,

Dear W,
I have a pricing procedure ABC having following condition types
1. PR00
2. ZSED
3. ZWEH
4. MWST
sales to order above procedure work and i got the accounting documents and invoice.
My 2nd pricing procedure is XYZ for Debit Memo and assign on document type, have th efollowing steps.
1. PR00
2. MWST
3. ZHE1
4. ZHE2
when i create debit memo with reference to invoice at debit memo (Sales document type) the pricing procedure ABC is come automatically, and when I go to billing the actual pricing procedure is come, plus i have to press maullay carry out new pricing button, other wise the common condition type is came at billing, if in copying control if i by default maintain the carry ou tnew price system duplicate the condition types.
Hope you will now understand my issue and give any value added feedback for the resolution of hte issue.
Regards,

Import meterial pricing procedure steps, accruvals doubt in freight conditi

Similar Messages

Maybe you are looking for