Rebates-while entering condition type b002

Hi..
    While doing the rebate procissing i am getting an error  " Sales volume for aggrement is not current " Plz help me in solving  this  .

Hi Srinivas
Chk this
Rebate  Agreement  Processing:
Step-1: Img/sd/bf/rebate agreements/define agreement types
              Eg: 0002-Material Rebate
Step-2: Define Condition type group
          Eg: 0002- --
Step-3:  Assign Condition  type to condition type group
Step-4: Assign condition type group to rebate agreements.
Step-4: Activate Rebates in,
               -Billing documents (B1,B2,R3,R4,F2,G2,L2)
          -Sales Organization
          -Customer master –sales area data-billing tab-rebate field
Step-5: Create Rebate agreement condition records,Tcode-VBO1
                   Enter agreement type,(Material Rebate)
               Select “Conditions”
               Enter Rate-1000/-
                    Accruals-50/-
          Click on “Settlements for Material” & Save
     Message: Material Rebate “ZZ” has been created.
Step-6: Create sales order-VA01
                    -VL01N
                         -VF01
Step-7: Got VBO2-Change rebate agreements condition record,
                Enter agreement type”ZZ”
          Change the agreement status to “B”
Select “ Sales Volume” ,select the line item ,press F3,
(NOTE: If you cant see the accruals amount,
          Got SE38,
     Enter prog: SDBONT06,(Update the billing documents program)
     Enter agreement no: ZZ
     Log,
     Remove the mark in the field of “error”
Select ,” statement of sums” and execute
Press F3 & generate.
           ( Now go VBO2, check the accruals amount)
Goto “Rebate Payment / Final settlement/Using payment scree-F6”
                Save the agreement type.
Message: Credit memo request(R4) automatically created.
Step-8: Goto VBO2- check the “Agreement status”
          You ll observe – as “C”
Step-9: Goto VA02- enter credit memo request,
                       Remove the billing block
                   Save
Step-10:Create  Billing (VF01)
     Enter Credit memo req
          Save
     Observe the rebate amount
     By goto-item- conditions
Step-11:Goto VBO2-
          Enter Rebate Agreement type-ZZ,
          Agreement status Shown as “ D”
Settings:
Pricing procedure—
                           Frm     Subto          Acctkey      Accruals
59     0            Total discount               
60      0            Rebate basis             7
61     0          Kf00                        4            ERF
62     0     Bo02        Material rebate     60            ERB          ERU
Account determination: VKOA
Rebate account key-ERB (883000)
Accruals     - ERU
Create sales revenue account(FS00)-12345 by copying from 800000 &assign this account against Accountkey “ERU”
V-KOFI-INT-TATA-01-03-ERB-800000- ___
V-KOFI-INT-TATA-01-03-ERU-12345  -12345
Reg
Annie

Similar Messages

  • Getting error while creating condition type in SPRO

    Hi ,
    can somebdy tell me why i am getting the following error while creating condition type in SPRO
    No valid change license available for message /sapcnd/
    and also while rule determination using condition type we are getting the following error.
    system error:system cannot read the structure for table
    reg
    venkat

    Hi Venkat,
    Do you have the error number code!?
    Regards,
    Michel  Bohn

  • RECN (Process Contract) Error while adding condition type

    Hi All
    I am processing the contract (RECN). While adding a new condition type, it gives me thr error
    Parameter KWH (area unit) for calculation formula Y3 has errors
    Moreover when i defined this calculation formula (Y3), units KWH are not coming in area unit field (F4-possible entries).
    Pls help me with that.
    Thnx in advance
    Deepak

    Hi,
    i am assuming you have added customised formula to condition type while creation of conditon. for the formula there is no link to Badi.
    if the above is right, you need not to add any formula and parameter while creation of conditon,first remove the formula form the conditon and assign standard one.
    then select the formula after inserting the condition. error about the formula may be  no value is being supplied from the formula.
    thanks
    Jilani

  • Enter condition type several times in a sales order

    Hello Gurus,
    I have a Pricing Procedures with net price minus some discounts and sales price. This is standard. One of the discount condition types you can enter manually in a sales order. Now my problem. This discount  condition type you can enter several times in a sales order. How I can solve this for one time enter.
    Regards
    Artur

    Yes, it is a standard behaviour only, you can only control with User exit only. Include MV45AFZZ , co ordinate with your ABAPer for the same.
    Regards,
    Ramesh

  • No accounting document generated while new condition type is added

    Hi
    I added a new condition type to the pricing procedure. While creating the invoice if i try giving a value to the new condition type then i get the message "No accounting document generated", but when i leave it as blank then there is no problem with the a/c docs.
    I assume I haven't done the complete settings correctly. Pls help.
    I am using  RVAA01 as the pricing procedure for standard order.
    Regards,
    Sujai

    Hi,
    As I do not have access to your system, can not comment in details.
    But if I have to add a tax codition in pricing, what I would do is :
    Create a tax condition, assign it in tax procedure.
    Copy it as sales pricing condition.
    Assign it in pricing procedure.
    Create condition record for tax condition in VK19.
    Check tax code in FTXP & its assignment in OB40.
    Create condition record for MWST.
    I think you need to check the above configuration.
    Savita

  • Columns "Max Pr Pts" and "Pt Min Prc" not coming automatically when we enter condition type 0LM1

    Hi,
    In the product master data COMMPR01, If we search any sales product and in condition tabs , when we give condition types 0LM1 in conditions, Max Pr Pts and Pr Min Prc columns are not getting added automatically as displayed below(The screen shot was taken in the another where it is working)
    Could you help us to find how these two columns comes automatically when enter the condition 0LM1 in the product under condition tab.
    System Details : QD3/504
    Best Regards,
    Manmohan

    Hi Manmohan,
    For Loyalty related functionalities, please use the Set Type - REWARD_PRO_LOY  to the product categoty.
    Details are given in SAP note:1331970.
    Regards,
    Srinivas

  • Related to condition types and access sequence

    Dear all,
           i want to know abt one scenario, m using a pricing procedure with my service PO: ZVSTOT, in this Procedure, 12 condition types are there, during searching i found tat 3- 4 condition are are using different different access sequence, so i want to know tat in what procedure, we do it, what is use of it.?
    plz reply me.

    Hi Nisha,
    Prcing procedure configured in your service PO PO: ZVSTOT, Based on this pricing procedure system adopted the condition type in PO.
    Please go through this below link to better understanding the MM-Pricing procedure
    http://it.toolbox.com/wiki/index.php/Pricing_Determination_Process_-_MM
    http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
    CONDITIONS OR PRICING PROCEDURE or PRICE DETERMINATION PROCESS
    We deal with the Pricing Procedure for vendors.
    PB00 Gross Price (info record, contract, scheduled Agreement)
    PBXX Gross Price (PO)
    FRA1 Freight
    RA00 Discount on net
    RA01 Discount on Gross
    ZA00 Surcharge on net
    SKT0 Surcharge / discount
    ZPB0 Rebates
    MWVS Input Tax
    MWAS Output Tax
    BASB Base Amount
    RM0000 Calculation Schema or Pricing Procedure
    (PB00 & PBXX)
    RM0002 Calculation Schema or Pricing Procedure
    (PB00)
    PB00 --> AB00
    Copy the Standard one and create new one (ours)
    RM0000 contains all the condition types
    Pricing Procedure (PP)
    We define the pricing procedure to define condition supplement for the material price. The condition supplement specifies the discount, surcharge, freight etc that we want a system every time to access material price condition records.
    The total value of the material is calculated or based on all addition and subtraction i.e. discounts, surcharge, tax freight etc
    Condition Table
    It is a table, which defines the structure of condition record key.
    Condition Record
    It is a data record used to store conditions or condition supplements, i.e. condition like, discount, freight, and surcharge, Tax etc.
    Condition Type
    It is used for different functions. In Pricing the condition types leads you to differentiate different types of discounts, in output determination, batch determination, difference between two output types, such as delivery note or order confirmation, between different strategy types
    Access Sequence
    It specifies the order in which system searches or access the condition records from condition table
    Difference between PB00 & PBXX
    1. Condition maintained in PB00 is time dependent whereas PBXX is time independent.
    2. Condition type PB00 u2013 used for IR, RFQ, Contract, Schedule Agreement
    Condition type PBXX u2013 used for PO.
    Calculation Schema
    The main function of calculation schema is to provide framework of steps for the price determination process to specify the discounts, surcharge, freight rebate etc.
    It also determines the sequence of conditions that are to be followed and in which sequence.
    Schema Group Vendor
    The main function of it is to identify or to pick the right process and conditions for a particular vendor.
    Schema Group Purchasing Organization
    Key that determines which calculation schema (pricing procedure) is to be used in purchasing documents assigned to the relevant purchasing organization.
    Schema Group
    It allows to group together the purchasing organizations, which uses the same calculation schema.
    Steps: -
    1. Create Access sequence
    2. Create condition types
    3. Create pricing procedure or calculation schema
    4. Link pricing procedure & access sequence to condition type
    5. Create schema group for vendor
    6. Create schema group for purchase organization
    7. Assign schema group vendor-to-vendor master record in purchasing data view
    8. Assign schema group purchase organization to our purchase organization
    9. In inforecord purchase organization data enter condition types and pricing or calculation procedure
    CUSTOMIZE SETTINGS: -
    SPRO > IMG>MM>PUR>Conditions -->Define price determination Process
    1. Define access sequence
    2. Define Condition type
    3. Define cal. Schema
    4. Define schema group
    o Schema group vendor
    o Schema group purchasing group
    5. Assignment of schema group to PUR org
    6. Define schema determination à determine cal schema for standard PO.
    With Thanks,
    Thiru

  • Condition value of Tax condition type gets added to Total Value in Contract

    Hi All,
    I'm currently investigating an issue where there are 2 line items in an SAP Sales Contract. There is a human error in the second line where the billing end date is less than billing start date in the billing plan.  Consequently, the second line has null Outgoing target value.
    However, the header Total value in the Contract  gets wrongly calculated as Basic condition value of 1st line  + Condition value of tax condition type of line one due to this.   When I modify the billing end date for the second line item to be a date greater than the billing start date, the above problem disappears and the total value of the contract does not include the tax component.
    For eg.
    Normal Error free  Contract
    Total Value at Header =   700.00 EUR
                       Material          Outgoing Target val
    Item 0010    MAT1               450.00                          ( 450 + 50 (tax )  )
    Item 0020    MAT2               150.00   
    Contract with billing plan error in second line
    Total value at Header =   550.00 EUR 
                            MAterial       Outgoing target val          
    Item 0010         MAT1             450.00                    ( 450 + 50 (tax ) )
    Item 0020         MAT2              0.00         
    Any inputs would be most welcome.
    Regards,
    Venkatesh.
    Edited by: Venkatesh Gopalarathnam on Jan 24, 2012 9:48 AM

    No, i didn't.
    Actually, i enter condition type and amount in sales order manually.
    At that time my program which i modified at 'Define And Assign Pricing Procedures' in IMG should be run. 
    But the result of running is different from my purpose.
    To change Condition value of condition type in sales order, are there any solution?

  • Determination of Base price condition type depending on Item Category

    Dear All,
    The requirement I have is as stated below:
    There are two materials A and B that are individually sellable materials. But during a specific time period the company decides to give a scheme where in Material B is given as free when a particular quantity of material A is purchased. Irrespective of the scheme, material B can also be individually purchased during the scheme period.
    Now in the former scenario where material B goes free with material A in the same order, the base price of material B should not go to revenue G/L but to a different G/L called Scheme G/L. To counter this scheme G/l there is another counter G/L into which 100% discount on base price to material B goes.
    In the latter case, if material B is sold individually, then the base price should go to Revenue G/L and not scheme G/L and the 100% discount is not applicable.
    Can you please guide me on how to configure this.
    The approach I have taken is as follows:
    The condition types for base price are ZBPR and ZBP1(reference condition type of ZBPR)
    Item Categories to be considered: ZTAN and ZTNN (for material B going as free during the scheme)
    The requirement is such that, whenever the item category for a particular material is ZTAN, the condition type to be picked must be ZBPR while the condition type ZBP1 must be deactivated.
    Similarly, if the item category for the line item is ZTNN, then the condition type to be picked must be ZBP1 and the condition type ZBPR must be deactivated

    Dear All,
    I have fulfilled this by doing rev acct determination in vkoa using item category and moving it up the order. Also I used a requirement in v/08 for 100% discount on free material.
    This has resolved my issue and i am now closing this thread.
    Thanks and Regards,
    Rohan
    Edited by: Lakshmipathi on Apr 2, 2011 10:53 AM
    Since you have arrived at a solution, please change the status of the thread to "Answered"

  • Numerator and Denominator for converting of condition type incorrect

    Hi.
         i create credit memo request which refers from invoice. When i have entered condition type, i found that condition value of its is incorrect because the numerator and denominator do not equalize with conversion factor in tab Sale A of item. However, the numerator and denominator affect the condition base value.
       I think that it is error from standard system, but i don't know where the point of it is. Please suggest me.
    PS. The materials in invoice is material variant of which conversion factor in sale order is instead from user exit.
    Best Regrads.,
    Autsnee P.

    Hello
       As a process you have done well. But I suspect there could be an error at " condition value ". Because when you use the division function we have to CLEARLY specity the UNIT and DEPENDANT DECIMAL.  To give you an example
            Example:1 " Procurement order ".
               If a procurement amount = say <1 Million.
              Business say to 20% of amount to be distributed to Inventory Dept. Here you have to declare a division condtion. with BASE UNIT and decimal unit.
               By nature system trys to compare with the previous available data.            
             I hope I answered your question. It was nice answering your question. Feel free to reach SDN if you have any questions. What are the action item at Intregatrion scenario.
    Thanks in advance for your co-operation
    Ashok Babu
    Enterprise Business process Architect
    SAP XI Senior Consultant

  • Duplicate condition types in processing rebates

    Hi,
    I have created two rebate agreements in the system right now.
    Whenever i run a sales cycle the condition type BO01 is used twice instead of once which results in giving discount twice for the same order.
    Is there any way to avoid duplication of condition types.
    How to solve this issue, pl help..

    Hi
    You have maintained two rebate arrangemnts here and sytem is determining accordingly.
    Thats the reason you need to ensure the combination being used in the condition type.
    If both the records are valid i am not seeing an issue here.
    If your issue is same condition type. then you need to maintain different condition types for different combinations,.
    For example: Key Combination -> Condition type
    Customer/ Material - B001
    Customer/ Sales area - B002
    Maintain two condition types for both combinations instead of maintaining it is the same.
    So they get determined accordigly.
    Thanks & Regards
    Kishore

  • Bringing the nor rebate condition type in rebate credit memo request.

    Dear Gurus,
    Is it possible, to bring the discount condition type say Zxxx(which is not a rebate relevant)
    in the rebate credit memo request.
    In the credit memo request,  while doing price analysis I can see the condition type Zxxx with the message condition record found and manually removed.
    For the condition type I do not check the Delete Indicator.
    I don't know why it is happening..
    Kindly suggest me with your valuable thoughts.
    I need to bring the non-rebate relevant condition types in the rebate credit memo reqquest.
    Thanks & Regards,
    Venkatesh.S.P.

    Hi Gurus.
    Follow my business scenarie:
    This is GAS & OIL  company, in this business, they work with price including taxes, we are now implemented a rebate solution, but the accrual values follow the same business rule, including tax.
    At the moment to create a credit memo request for rappel, the system trasfer only tha rappel condition type with the final settlement value and calculate the tax condition type..
    In the credit memo pricing procedure, I need to split the net value by formula.
    this is my pricing procedure configuration:
    level          Cnd Ty                                         Level                Subto     Form
    15     0     BO02     Price                               
    600     0                  Sales Total                                             B     I     
    710     0     MWIG     tax                                       600     600          G     
    730     0     NTPS     Net Value                                                                       988
    810     0                  Net Value                               730     730     B     4     
    820     0                  tax                                       710     710     B          
    840     0                  T O T A L                               810     830     B     A     
    Formula 988
    FORM FRM_KONDI_WERT_988.
      XKWERT = XWORKI - XWORKG .
      XWORKG = 0.
      PERFORM XKOMV_KBETR_FROM_KWERT USING XKWERT.
    ENDFORM.
    This is my result in the rebate credi memo:
    Header     Net Value     100     usd               
    cnd ty     descrip     Value     curre     quan     um     cond value
    BO02     Rappel     100              USD     1              UN     100-
    MWIG     tax             16,000     %                              16-
    there are our expected result:
    Header     Net Value     84     usd               
    cnd ty     descrip                  Value             curre     quan     um     cond value
    BO02     Rappel                     100               USD     1             UN     100-
                 Total Rappel             100               USD     1             UN     100-
    MWIG     tax                         16,000     %                                              16-
    NTPS     Net Value                  84               USD     1             UN     84-
                    tax                               16               USD     1             UN     16-
                 T O T A L                      100               USD     1             UN     100-
    The problem is , the system never execute the formula 988
    There are a possibility to get this...a user exit, formula..that we can use..
    Please. any information we are appreciate.
    regards

  • Multiple rebate condition types in one invoice

    I had defined multiple rebate condition types as Y000, Y001 and Y002, which are montly offtake rebate, distance rebate and yearly offtake rebate.
    Y000 and Y001 can be in the same validity period and also will be applicable to the same invoicee.
    When i create a rebate agreement for customer for Y000 and go for the settlement of the rebate it is happening fine.
    But for the same customer, i had defined Y001 as a rebate agreement type for the same period and materilal.
    The sales volume is not updated in the rebate agreement. Evenif I do VBOF the sales volume is not updated.
    the error that comes while doing VBOF is :
    "7000158055 Document number RCFL 7000158055 2011 was already assigned
    7000158053 Document number RCFL 7000158053 2011 was already assigned
    7000158052 Document number RCFL 7000158052 2011 was already assigned
    7000158054 Document number RCFL 7000158054 2011 was already assigned"
    Please help me to solve this problem.
    Mrs. Swati Pawar

    Hello Swati,
    the suggestion of JP is correct.
    I explain it better.
    - the document type of FI document created from SD depends on the customizing of billing type field TVFK-BLART. If it is blank, then by default is 'RV'.
    - if the number range assigned to the account document type is External, then the FI document gets the same number of the SD invoice.
    - transaction VBOF creates FI document referred to SD invoice. If it has external number range, and an FI document already exist with same number (created when SD invoice has been released to accounting), then the errof F5152 occurs.
    SOLUTION:
    in the selection screen of VBOF there is the field FI-Doc-type. Here you should specify the FI document type that should be created by execution of VBOF, and of course it must have number range internal.
    Please try this.
    Best regards,
    Ivano.

  • Error in pricing when trying to manually enter Shp. Cost  condition type

    Greetings everyone!
    I'm creating my own pricing procedure and I've added Shp. Cost (0HD0) condition type to it and when I'm trying to enter a price per KG it gives me an error:  "Material Test Product, condition 0HD0 : unit of measure KG is not allowed Invalid manual change to zero of condition pricing unit". Product's unit of measure and weight has been maintained though. It also happens if I use standard pricing procedure with that condition type in it... Why is that happening? Is there any workaround for that?
    Thanks in advance.
    Regards,
    Alex.

    Hello Alex,
    Any solution to question yet? I am facing same issues and I am curious to the solution to this.
    Kind regards,
    Carla

  • Error while posting in accounts: Condition type does not exist in COPA

    Hi,
    I'm trying to post an invoice into accounts but I'm constantly encountering a Error message as : Assign condition type in COPA.
    This error is appearing whenever I'm assigning the pricing procedure and KOFK account entries to a new sales organization.
    The error does not appear for my previous Sales org. Also I check with the COPA settings, it does not allow us to enter the condition type mentioned in the error.
    Could anyone suggest a solution
    Regards
    Rasheed

    Dear Customer,
    To solve error KE391, the corresponding value field assignment          
    must be done in transaction KE4IM.                                                                               
    Currently, the value field assignment is available for this             
    condition type in transaction KE4I (SD conditions assignment).                                                                               
    In this case you have to maintain the assignment to a value field in    
    transaction KE4IM. After including the corresponding assignment in      
    KE4IM, the error KE391 should not come anymore.                                                                               
    Please, check this.
    I hope that the information are helpful.
    With best regards
    Claudia Neudeck

Maybe you are looking for