Querry over pricing procedure used in creation of BIlling request

Hi,
     While creation of BIlling request via DP90 , system considers DIP Profile & pricing procedure and brings data /rates to billing procedure ..
I am trying to understand the pricing procedure, i am using standard pricing procedure RVAA01 ->
When i check the conditions Tab for a particular materials it has the below condition types :-
1. EK01  
,PR00,MWST,DIFF,VPRS ..
Anbody pls give idea on how these conditions types are determined ..??
I have checked & found condition record only for PR00 & MWST .. i could not find condition record for VPRS Condition type but how is it determined ?
regards
giri

EK01 comes from the actual cost on the service order
PR00,MWST,DIFF,VPRS  from memory these are all condition records created via EK11
PeteA

Similar Messages

  • Pricing procedure using AltCaltype & Altbase value

    How to create Pricing procedure using AltCaltype & Altbase value.Can any one provide an example for it

    Hi Pradeep,
    There are very basic questions in pricing. You can search the forum and you will definitely get lot of answers for this.
    However, Alt calculation type and AltCnBV are the ABAP routines assigned in the pricing procedure. There are lot os standard routines given by SAP and if in case they do not meet your business requirement, then you can create one and assign in the pricing procedure to meet the busines requirement.
    Examples:
    Alt Calculation Type: This defines how the value for a condition type is to be calculated. Suppose, net price =qty*unit price
    Alternative formula for condition base value : Suppose you have a freight charge of $100 to be distributed on 3 different line items proportionately based on the individual weights in the sales order, you can define the routine and assign it in this field in the procing procedure
    Regards,
    Raghav

  • How to extract values from pricing procedure for conditions in CRM Billing?

    I have a number of conditions in the pricing procedure in CRM Billing that I would like to extract to SAP BW. How can this be done?
    Is there a standard extractor for CRM Billing similar to the SD Billing extractor "Extraction of SD Billing Conditions" (2LIS_13_VDKON)?
    If there is no standard extractor, is there another way to extract the conditions and the related values?
    I am using the standard CRM Billing Extractor 0BEA_CRMB already, so maybe an append could solve my problem. How can this be done? In what CRM-tables can I find the values from pricing procedure for conditions in CRM Billing?

    you may want to post that last question in a CRM forum... in ECC it would be table KONV

  • How we can configure new pricing procedure at the time of billing document

    Hi SD Gurus,
    Can u plz tell me how we can configure new pricing procedure at the time of billing document level.
    Thanks & Regards,
    Sreenivas.P

    Hello,
    Why?
    The sales order confirms the price given to the customer.  If you have re-determined a new price/discount then you may consider in VTFL to use pricing type C.
    Regards
    Waza

  • Different pricing procedure for order document and billing document

    In which scenerio order and billing has diffrent pricing procedure?

    Hi,
    intercompany billing is one of the scenario.
    Business case: -
    Customer orders goods to company code/Sales organization A (Eg.4211/4211).Sales org 4211 will accept and punch the order in the system with sold to party as end customer code in the system. Company code/sales org B (Eg.4436) will deliver the goods to end customer and raise an intercom any billing on 4211 with reference to delivery. This can happen only after 4211 raises invoice to his end customer to whom the material has been delivered by 4436.
    SPRO Customization required:-
    1. Assign plant of delivering company code (Eg.SI81) to sales org/distribution channel combination of ordering company code (Eg.4211/RT)
    2. Maintain intercom any billing type as IV for sales document type OR
    3. Assign Organizational Units By Plant (Eg.SI81/4211/RT/11)
    4.Define Internal Customer Number By Sales Organization (Eg.4436 will create customer master for 4211 company code and that number will be maintained in this relationship:-4211/231)
    5. Automatic posting to vendor account (Optional)
    6. Maintain pricing procedure determination for 4211/RT/A/1/RVAA01-For customer sales and billing
    Maintain pricing procedure determination for 4436/RT/A/1/ICAA01-For intercompony billing
    Master data to be maintained:-
    1. Create end customer master in company code/sales org 4211/RT/11
    2. Create customer master for 4211 company code/sales org in 4436/RT/11
    3. Maintain PR00 as price for end customer-Active in RVAA01
    4. Maintain PI01 as price which has to be paid to 4436-Statistical in RVAA01
    5. Maintain IV01 as inter-company Price-Active in ICAA01
    Process:-
    1. Create OR with sold to party as end customer.
    2. Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as intercomany sales.
    3. Pricing procedure is RVAA01
    4. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery.
    5. Ordering sales org will create billing document F2 with reference to delivery for end customer.
    6. Delivering sales org will create intercompany billing IV with reference to delivery document.
    I hope this helps you.Reward points if solution is useful.
    Regards,
    Amrish Purohit

  • Different  Pricing Procedure for Sale order and Billing Document

    Hello Experts
    As per scenario,we create Excise Invoice (T-Code J1IIN) on Basis of Proforma Invoice.Proforma Invoice and Excise Invoice follow Pricing from Sale Order.AS per pricing Some excise condition types are get update in Proforma and excise Invoice.
    AS Per Customer Payment Confirmation we Create Export Billing Invoice (T-code VF01) on basis of Outbound delivery.
    Issue -: AS per export Billing Rule we don't want to update Excise Condition type in Export Billing Document,and at same time it should not create any accounting entries for same condition type. we Dont want excise Duity in Export Billing Document as Export Billing Doccumnet aslo Follow Pricing procedure of Sale order
    Should i create new Pricing procedure or what other things to solve above issue.
    Please help me out
    Thanks and Regards
    Pash@SD

    Hello,
    The key to your requirement can be maintenance of Excise condition type with proper access sequence and accordingly maintain condition record for them.
    You create an access sequence with following access:
    - Country / Plant / PlntRegion / Region / Price grp / Mat.pr.grp / Materia
    - Country / Plant / PlntRegion / Region / Price grp / Mat.pr.grp
    - Country / Plant / PlntRegion / Region / TaxCl1Cust / Mat.pr.grp
    - Country / Plant / PlntRegion / TaxCl1Cust / Mat.pr.grp
    For export maintain condition record based on any key combination, say for
    Country / Plant / PlntRegion / TaxCl1Cust / Mat.pr.grp - Tax % - Tax Code
    FR / 1000 / KR / 03 (EXPORT) / 04 / 0% / V1
    I hope this can assist you.
    Thanks & Regards
    JP

  • Different pricing procedures on Sales order and billing documents

    Hello All,
    I have come across a situation where I will have to maintain seperate pricing procedures for Sales order and the corresponding billing document.
    I was just wondering if this is normal. In my previous projects I always had same pricing procedure for the order and the billing.
    Please share your experience.
    Appreciate your help.
    Thanks,
    Raj

    Hello Friend
    This is a very common requirement in many implementations depending on the scenario
    Sales order with one pricing procedure The same sales order when goes for billing
    Billing document with another pricing procedure
    Settings needed
    Order type VOV8 has a document pricing procedure  Say A
    Billing type VOFA has a document pricing procedure  Say B
    Sales area 1000,10,00 and CPP is 1
    OVKK settings is like this
    1000,10,00 DPP A, CPP1 Pricing procedure is  RVAA01
    1000,10,00 DPP B,  CPP1 Pricing procedure is RVAA02
    The control data in both  RVAA01 and RVAA02 is different
    In VTFL between your del type to billing type aunder the header that item level The pricing type should be B (carry out new pricing) if delivery related billing
    In VTFA betwen your ord type to billing type aunder the header that item level The pricing type should be B (carry out new pricing) if ordery related billing
    Now the same sales order will carry PP RVAA01at order level and RVAA02 at the billing document
    There can be some business scenarios you want to add some extra discount at the time of billing
    That time you have a discount type added in the billing PP so that it is reflected in the billing
    This is scenario dependent
    Hence SAP has given the option of DPP in VOFA so that by billing documentwise we can differentiate
    To achieve this Copy control settings and DPP should be different both in VOV8 and VOFa
    Regards
    Raja

  • Customer pricing procedure table

    Hie can you please let me know customer pricing procedure table for sales document?
    I want to know the customer pricing procedure assugned to Sales document in table level.
    thanks and regards,
    Marry.
    Edited by: marrysap on Jun 7, 2011 4:23 PM

    Hi There is no table where you can see the customer pricing procedure used for sales document
    If you want to see then you might need to write a querry
    SQVI
    Select tables
    VBAK
    KNVV
    Selection parameter
    Sales document number
    Customer number
    Output
    Sales document number
    Customer number
    Cust. Pricing procedure
    Thanks

  • How  does systemn determin pricing procedure of billing type

    How does system determinate pricing procedure of F2???????????????????
    By doc.pric.proc? but in IMG, it is empty!!!
    and I don't think it is reference sales order's pricing procedure
    because if you use OR + TAN, the reference document of billing is delivery order!!!!!!

    Hi zhang
    In pricing procedure determination OVKK , whatever DuPP you maintain that is linked to Billing document
    In VOV8 we can see the CuPP  of the document . so if the DuPP is linked to CuPP in OVKK then the same pricing procedure will be flowing to billing document also  . Apart from that in VOV8 also make sure that , in billing data you are maintaining the billing  type
    Regards
    Srinath

  • Rebate fixed amount condition in the pricing procedure

    Hi SD Gurus,
    i'm using rebate fixed amount conditions (Lum sum).
    The situation from a business point o f view is the following: i pay the customer 1000$ once he made something.
    This kind of condition is not relevant for accruals since they have to be built manually (manual accrual). As a consequence i'm note sure if this condition shoul be put in the pricing procedure used for invoices. In the other and for sure this condition should be inserted in the pricing procedure for manual accrual/credit note.
    What is your point of view!!
    Thanks
    C

    if you are going to use Rebate, then there is no need to add condition type in standard pricing procedure, if you have designed your pricing procedure, include condition types for rebates as in standard pricing procedure.
    This condition type is linked to Rebate type.
    I think you first try the scenario in IDES and then do the same settings as per yoru requirement.
    If you want step-by-step procedure for rebates will help you
    Please refere the thread
    rebate documentation
    Regards
    Jitesh

  • About tax in the pricing procedure

    Hi Gurus,
    I need your help. Our client says that the tax was incorrectly calculated from the start of SAP application.
    Before SAP Application, their tax is computed as follows based on the Pricing procedure used:
    19% on Freight
    6% on Value of goods
    But now this is how tax is incorrectly calculated:
    6% on net value of goods
    I need your help on how I will solve this issue. This tax calculation should only be applied to sales to domestic Intercompany customer.

    Hi,
    Can you pls explain little more clearly with example in the pre and post SAP scenarios.
    Kind Regards
    Chakradhar

  • Redetermination of pricing procedure and its condition types during credit

    Hello ALL,
    please provide the solution to redetermination of pricing procedure and its condition types during credit  memo request
    with referance to invoice
    And kindly provide the step by step process of rebates
    regards,
    Thanks

    Hi,
    In standard setting the copy control from billing to sales document uses data transfer routine 052 (FV45C052). Within the standard the pricing procedure is copied from the billing document to the sales document and will not get redetermined. This is standard design.
    However, if you would like the sales document (credit memo request) uses its own pricing procedure instead of copy that from the billing, you can implement this by using your own routine. In that case, please see note 14136 for a sample.
    Please notice that you would also need to assign a different document pricing procedure for document type of credit memo request in VOV8. Then enter the new entry in OVKK to determine the pricing procedure for the new combination.
    Regards,
    Alex

  • Cin pricing procedures

    what r the major differences between TAXINJ and TAXINN. which would be very useful in present scenario. and advisable,
    will reward

    Refer link below hope it helps
    TAXINJ/TAXINN are the two different pricing procedure used in CIN.
    TAXINN only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination.
    Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
    Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
    When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
    TAXINN AND TAXINJ difference ? AND Which is better ?
    TAXINJ & TAXINN are Tax Procedures in India. TAXINJ is old version & TAX INN is new version. Both has its own advantage & disadvantage.
    Upto 4.6C & partially 4.7 version of SAP, TAXINJ was used. TAXINJ is formula based calculation, in which we maintain the tax rate in Tax Code itself. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST & permutation & combination of these, we require that many Tax Codes. For example:
    Tax Code: A1
    Taxes: 16% Excise Duty + 2% Education Cess + 12% VAT
    Tax Code: A2
    Taxes: 16% Excise Duty + 2% Education Cess + 8% VAT
    Tax Code: A3
    Taxes: 12% Excise Duty + 2% Education Cess + 12% VAT
    Tax Code: A3
    Taxes: 12% Excise Duty + 2% Education Cess + 8% VAT
    From 4.7 version onwards of SAP, TAXINN is being recommended & used. TAXINN is more user friendly & condition record based. In TAXINN, Tax Codes are statistical & of not much relevance, but are required to be maintained in condition record for taxes condition type. This makes Tax Codes simpler. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST, we need not have the tax codes to that combination. For example:
    Tax Code: A1
    Can be used for any rate of excise duty, as tax code is only required to be maintained statistically in condition record.
    Tax Code: A2
    Can be used for any rate of VAT, as tax code is only required to be maintained statistically in condition record

  • Pricing procedure for billin

    Hi,
           How system copies pricing procedure from sales document to billing document

    as you know pricing procedure is determined by
    sales area + doc. pricing pro. + customer pricing procedure
    document pricing procedure will come from sales document types and Billing Types.
    customer pricing procedure will come from customer master
    Between the sales document and billing document the only factor that could change is the document pricing procedure
    If they do not differ the same pricing procedure would be used and the control would be as per the configuration given in the copy controls.
    If they differ then new pricing procedure determination will be carried out but for that in copy control we need to maintain PRICING TYPE AS B carry out new pricing else it will give you error saying pricing procedure could not be determined

  • How to replicate a new pricing procedure from SAP ERP?

    Dear Experts,
    I have set up a new pricing procedure in the ERP backend and I would like to replicate this to SAP CRM.
    A replication using object DNL_CUST_CNDALL has been executed once in the past.
    What would be the best way for me to download the new pricing procedure without overwritting any of the existing pricing settings in SAP CRM?
    Thanks,
    Dan

    Hello Dan,
    The views in CRM pricing customizing do not allow to change the pricing procedures, condition types and access sequences that have been downloaded from the ERP system. You will see a field in customizing Source System with value A indicating that these were not created originally in CRM and the view does not go to edit mode.
    In case a i.e. condition type had been created originally in CRM with the same name as a condition type that exists in the ERP the download of the adapter object will not delete the condition type that was created in CRM.
    Therefore it is safe to execute the initial download of the adapter object DNL_CUST_CNDALL without filtering. If you have many pricing procedures in the ERP and you do not want to transfer its customizing to CRM you can create your own adapter object by copying the content of DNL_CUST_CNDALL ( to be on the safe side and keep the original) and then add a filter in your adapter object ,for example in pricing procedures using field KALSM of table T683S, including all the pricing procedures that must be transferred to CRM u2013 those that were transferred in the past and the one that you want to transfer now .However this filter is optional, most SAP customers do not change the standard filters.
    The usual options are:
    -- Download only DNL_CUST_CNDALL (or a Z object that was created based on DNL_CUST_CNDALL) which contains client dependent and also  independent customizing ( i.e access sequences, condition tables).  Condition tables may be generated too and it can take longer, maybe up to 45 minutes or so.
    -- If you have made changes only to pricing procedure(s) or condition types u2013 client dependent customizing--  it will be enough if you download only DNL_CUST_PRC. As there is no generation of condition tables the download will be faster.
    But you must consider that you should not download both adapter objects at the same time ( overlapping times), as part of the content being downloaded is the same and the database will be inconsistent. This can cause errors in pricing, not a severe issue, as it can be solved by a new download of  DNL_CUST_CNDALL, but an issue that causes trouble as it is sometimes difficult to determine the root cause of the problem. So if you for whatever reason ( i.e. additional changes in a condition type) download both adapter objects you should always check R3AM1 and download the second object when the download of the first one has finished ( green light in transaction R3AM1)
    Best Regards
    Luis Rivera

Maybe you are looking for