Pricing condition question

Hi Gurus,
I need your help
1) Want to configure a pricing condition which can be used only in a purchase order, but NOT in a contract/outline agreement. Is it possible? If yes, then how?
2) Want to configure a pricing condition which when added in a purchase order, will Not add the corresponding charges against the cost of material, but instead will get posted to a seperate G/L account. What special I have to do for it's configuration?
I do Not want to add a seperate line in the PO with a NLAG material accounting for those charges. The business wants the charges as a pricing condition (since we have the flexibility to put a different Vendor in a condition type )
Thanks,
Kumar

Hi,
1.Why you want a condition which can be used only in a purchase order, but NOT in a contract/outline agreement? What is the real business requirement!
2.For Not to add the corresponding charges against the cost of material,follow the steps:
Create a condition type (copied from standard FRB1 or FRA1 or FRC1 condition type ) in M/06 t.code & select check box of "accrual" selected in control data-2 & the Cond.category must be B(Delivery Cost) in control data-1 .
And
In the schema (M/08), keep an accounting key & an accrual key for that condition type
In OBYC only assign G/L account (separate) for accrual key with chart of account, valuation modifier & valuation class.
Now create PO( during saving PO, you can see net value not included amount in that condition type  in PO & assign as needed by you separate vendor to that condition type)
Go for MIGO & do GR and see all accounting entries with a separate entries for separate G/L account
For more check link:
http://wiki.sdn.sap.com/wiki/display/ERPLO/PostingplanneddeliverycosttoNon-inventoryaccount
Regards,
Biju K

Similar Messages

  • BAPI_QUOTATION_CREATEFROMDATA2 pricing condition question

    I am using XI to pass sales data from SQL Server into IDOC QUOTATION_CREATEFROMDATA201 to be processed by BAPI BAPI_QUOTATION_CREATEFROMDATA2 for the purpose of created new sales quotations.
    I am having a problem with pricing. I am populating a PR00 condition value within QuotationConditionsIn and the corresponding entries in QuotationConditionsInx. The data makes it into the new quotation, but there is a problem...there are 2 PR00 conditions. An existing one created by SAP automatically and the one from the IDOC, which has the proper value but is in state "inactive".
    Is there a way to tell SAP to use the incoming PR00 condition value and/or remove or deactivate the auto-generated PR00 condition record?
    Any help would be greatly appreciated.
    Thanks,
    Nathan

    Hi Thomas!
    Then we can go further in note 593246:
    you should
    1. Switch for activating the new condition item handling:
    Import parameter LOGIC_SWITCH-COND_HANDLE = 'X'.
    6. Addition of a condition with amount '0.00':
    ORDER_CONDITIONS_IN-ITM_MUMBER = '000010'
    ORDER_CONDITIONS_IN-COND_TYPE = 'PR00'
    ORDER_CONDITIONS_IN-COND_VALUE = '0,0000'
    ORDER_CONDITIONS_IN-CURRENCY = 'EUR'
    ORDER_CONDITIONS_INX-ITM_MUMBER = '000010'
    ORDER_CONDITIONS_INX-COND_TYPE = 'PR00'
    ORDER_CONDITIONS_INX-UPDATEFLAG = 'I'
    ORDER_CONDITIONS_INX-COND_VALUE = 'X'
    ORDER_CONDITIONS_INX-CURRENCY = 'X'
    Result: The condition is created with amount '0.00'.
    Regards,
    Christian

  • Question regarding usage of CRM pricing conditions using date ranges

    Hi,
    I wonder if someone has a suggestion regarding how to set up pricing conditions in CRM to accomplish the following scenario:
    For existing customers we want to “freeze” the product price for certain customers,
    but at the same time let other customers get another prize for the same product
    and period.
    (We have scenarios where the product price changes retroactively, years back in time, but only for those custoemrs that  fulfill a specific criteria at the time where the prize change was decided to take place..)
    We want the prize to be dependent on the customer status AND when this status was set
    (before a specific date), but there doesn’t seem to be a way to set up pricing
    conditions with date ranges (i e "customer status changed before YYYYMMDD
    renders prize X").
    Since we are talking about quite a lot of customers we do not want to add each and every
    one of them as “individual price items” in the pricing conditions tables.
    Does anyone have an idea regarding how to set this up?
    Thanks
    /Marika Wasserman

    Hi Marika,
    condition records have validity (FROM - TO). Let us assume you have a condition record for product A with 50 EUR per piece and this record is valid from 01.01.2014 until 31.12.2014.
    If you create CRM Sales Order having product A at 4.12.2014 and this date is used as pricing date for the conditon determination, then it will find this condition record with price 50 EUR per piece. This 50 EUR should be the froen price.
    Now how can you achieve that for the same CRM Sales Order another product price is determined for certain customer or a certain customer group?
    The idea is to pass an additional pricing attribute, e.g. customer group. Then you can create a new condition table with this field with the key fields product and customer group. In the access seqeunce first the new condition table is checked and if no record is found, then the second conditon table is checked as shown below:
    Access Sequence ABC
    Access 10: condition table with key fields product + customer group
    Access 20: condition table only key field product
    Instead of customer group you define also any other field. You create your own implementation of the BAdI  CRM_COND_COM_BADI that passes this field with a value to pricing.
    Best regards,
    Baris Yalcin

  • How to update pricing condition in sales in batch in the evening

    Gurus,
    I have a situation where I am supposed to update the freight charge condition type ("ZFR9" in my organization) on a scaled basis, depending on how much the customer (ship-to) has ordered on the same date. Since this changes from time to time, I need to write a program that does the following in the background in the evenings.
    1) Accumulate the wt of the material ordered by the same ship-to customer on the same delivery date.
    2) Find the scaled freight rate from a central universal freight charge table.
    3) Update the ZFR9 by this new frieght rate in all such sales order/line items that have the delivery date in question.
    The problem with using BDC is that the condition type ZFR9 appears on different lines depending on presence or absence of other condition types.
    Also I could not find any BAPI that does the update on a line item pricing condition.
    I am on 4.6C.
    Thanks for any help you can offer me.
    Regards
    Raju

    Guys,
    I am trying to make this work. I am able to add extra pricing conditions to sales order but I can not understand
    - how to change the value of an existing condition type OR
    - how to delete the condition type from the sales order line item
    Here is the sample code that I am using to test this out (most of the information is hard coded so that I can focus on a particular record)
    REFRESH RETURN.
        CLEAR   RETURN.
        REFRESH ORDER_ITEM_IN.
        CLEAR   ORDER_ITEM_IN.
        REFRESH ORDER_ITEM_INX.
        CLEAR   ORDER_ITEM_INX.
        REFRESH PARTNERCHANGES.
        CLEAR   PARTNERCHANGES.
        REFRESH CONDITIONS_IN.
        CLEAR   CONDITIONS_IN.
        REFRESH CONDITIONS_INX.
        CLEAR   CONDITIONS_INX.
        CLEAR SALESDOCUMENT.
        CLEAR ORDER_HEADER_INX.
    Move screen accepted docnumber TO SALESDOCUMENT.
        MOVE P_VBELN       TO SALESDOCUMENT.
        ORDER_HEADER_INX-UPDATEFLAG = 'U'.
        APPEND ORDER_HEADER_INX.
    Move screen accepted line item
        ORDER_ITEM_IN-ITM_NUMBER = P_POSNR.
        APPEND ORDER_ITEM_IN.
    Move screen accepted line item
        ORDER_ITEM_INX-ITM_NUMBER = P_POSNR.
        ORDER_ITEM_INX-UPDATEFLAG = 'U'.
        APPEND ORDER_ITEM_INX.
    Set the condition value
        CONDITIONS_IN-ITM_NUMBER      = P_POSNR.
        CONDITIONS_IN-COND_ST_NO      = '230'.
        CONDITIONS_IN-COND_COUNT      = '01'.
        CONDITIONS_IN-COND_TYPE       = 'ZSR3'.
        CONDITIONS_IN-COND_VALUE      = '333.00'.
        CONDITIONS_IN-CURRENCY        = 'USD'.
        CONDITIONS_IN-COND_UNIT       = 'LB'.
        CONDITIONS_IN-COND_P_UNT      = '100'.
        APPEND CONDITIONS_IN.
        CONDITIONS_INX-ITM_NUMBER     = P_POSNR.
        CONDITIONS_INX-COND_ST_NO     = '230'.
        CONDITIONS_INX-COND_COUNT     = '01'.
        CONDITIONS_INX-COND_TYPE      = 'ZSR3'.
        CONDITIONS_INX-UPDATEFLAG     = 'X'.  " update
        CONDITIONS_INX-COND_VALUE     = 'X'.  " update
        CONDITIONS_INX-CURRENCY       = ''.   " no update
        CONDITIONS_INX-COND_UNIT      = ''.   " no update
        CONDITIONS_INX-COND_P_UNT     = ''.   " no update
        APPEND CONDITIONS_INX.
        WRITE: / 'BAPI Called for', P_VBELN, P_POSNR .     
        CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
          EXPORTING
            SALESDOCUMENT               = SALESDOCUMENT
      ORDER_HEADER_IN             =
            ORDER_HEADER_INX            = ORDER_HEADER_INX
      SIMULATION                  =
      BEHAVE_WHEN_ERROR           = ' '
      INT_NUMBER_ASSIGNMENT       = ' '
      LOGIC_SWITCH                =
          TABLES
        RETURN                      = RETURN
       ORDER_ITEM_IN               = ORDER_ITEM_IN
       ORDER_ITEM_INX              = ORDER_ITEM_INX
      PARTNERS                    =
      PARTNERCHANGES              = PARTNERCHANGES
      PARTNERADDRESSES            =
      ORDER_CFGS_REF              =
      ORDER_CFGS_INST             =
      ORDER_CFGS_PART_OF          =
      ORDER_CFGS_VALUE            =
      ORDER_CFGS_BLOB             =
      ORDER_CFGS_VK               =
      ORDER_CFGS_REFINST          =
      SCHEDULE_LINES              =
      SCHEDULE_LINESX             =
      ORDER_TEXT                  =
      ORDER_KEYS                  =
         CONDITIONS_IN               = CONDITIONS_IN
         CONDITIONS_INX              = CONDITIONS_INX
      EXTENSIONIN                 =    .
        IF sy-subrc = 0.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
               EXPORTING
                    WAIT = 'X'.
    IMPORTING
      RETURN        =
        ELSE.                                           
         WRITE: ' BAPI RETURN CODE = ', SY-SUBRC.              
        ENDIF.

  • Pricing Condition in scheduling agreement

    Hi Gurus,
    I'm working with scheduling agreements and I figured that whenever I create scheduling agreements, pricing condition PB00 gets defaulted to the scheduling agreement,
    Can you guys be kind enough to tell me what configuration is driving this?? How can we make changes to the config settings so that I can have a condition type of my choice assinged to the scheduling agreenment??
    More over I have a requirement to have a tiered pricing in scheduling agreement. I do know that this is driven by SCALES in SAP however as per my requirements I need to have SCALES per formulas. In the condition type configuration we do have a field for SCALES where we can assign the formulas but whenever I click on this field a screen pops up with some ROUTINES.
    Can someone tell me how can I define the ROUTINES and the ABAP formula for this ROUTINE so that I can have my tiered pricing conditions accomplished??
    Any feedback on this will be highly appreciated!!
    Thanks folks,
    Dhaval Joshi

    Hi Ramesh,
    Thanks for the heads up. I looked at the config for the schema dtermination and I see that the pricing procedure RM0002 has not been assinged to any vendor POrg schema in this configuration.
    I then looked at the config for the condition type PB00 --> pricing procedure RM0002 has been assigned to the condition type PB00 and since we don't have any entries maintained for RM0002 in the schema determination config I was just wondering if this is what is influencing the automatic proposal of the condition type PB00 in my scheduling agreement.
    Also can you please tell me what is a difference between a Purchasing Document (BIG) and Purchasing Document (Small) in the schema determination config.
    All I wanted to accomlish here is my teired pricing to work when I assign scales on the condition type in the scheduling agreement ( not in the PIR)
    What currently happening in my case is ....
    Example: Scale From 1 pc - 100.00 USD
    from 50 pc - 90.00 USD
    from 100 pc - 80.00 USD
    Target quant. 100 pc
    schedule lines 30 pc
    20 pc
    The problem is  that the goods receipt of 30 pc is valuated at the price 80.00 USD It always takes a lowest price on the scale.
    I've tried looking for OSS notes and also looked enough on the forums but I could not get any resolution to this question.
    I would appreciate if I could get any heads up from your side.
    Cheers,
    Dhaval

  • Pricing Conditions and how the pricing date is determined

    Hi all,
    Small question, i ahve some pricing conditions that use the Serives Rendered date and others that use the Pricing Date from an order, how is the condition decided on what date it uses?
    Hope i have expplained this ok, if not and you need more info let me know.
    Regards
    Steve

    Hi
    There is a difference between Service Rendered Data and Pricing Date.
    Normally Freight Conditions are maintained on Service Rendered Date so the freight will be picked on the basis of date on which the Actual Delivery done, whereas Pricing date is used for other conditions so that price will be based on the date on which the document created and the Pricing Date maintained in that.
    In the same way there is a Billing Date which came in Invoice so price will be based on the date of Invoicing.
    If you maintain the record in VK11 and test a cycle you will be able to find the difference easily.
    Regards
    Amitesh

  • User Exit / BAdI to update the pricing conditions of the Purchase Order

    Hello SAPients,
    This is my requirement:
    "Copy the Pricing Conditions from the Shipment Cost Document (VI01 / VI02) to the automatically generated Purchase Order".
    I'm using the enhancement V54U0002 (Function Module EXIT_SAPLV54U_002) to EXPORT  the values of the Pricing Conditions to memory and I have used the enhancement MM06E005 ( FM EXIT_SAPMM06E_006, 007, 012, 013, 014, 016, and 017) to IMPORT the values from memory and store them in TKOMV. But, when the PO is generated the values don't stay, they are always changed with the standard PBXX pricing conditions.
    My question is: Does anyone know the User Exit / BAdI that I can use to change the Pricing Conditions of the Purchase Order?
    <<removed_by_moderator>>
    Thanks!
    Edited by: Vijay Babu Dudla on Jan 14, 2009 11:08 PM

    >
    kartik tarla wrote:
    > check this badi
    > ME_PROCESS_PO_CUST
    >
    > and the following user exit
    > Goto-> include RV61AFZA then search for
    > USEREXIT_PRICING_RULE see if its helpful to u.
    Hello Kartik / SAPients,
    I tried with ME_PROCESS_PO_CUST but didn't work. The system doesn't execute that code. Any other idea would be greatly appreciated.
    Thanks.

  • Pricing condition for Taxes in R/3 not being calculated.

    We have SRM4.0 in classic mode with R/3 4.6C. In SRM we configured Tax calculation is in R/3. When creating the shopping cart, EBP calls R/3 via RFC for the Tax % and displays the tax information in the cart successfully. The cart is saved and the completed PO is created in R/3. However, our pricing condition for tax, at Pur.Org/Material group in R/3 does not get calculated - so in the item condition screen, no tax is calculated. If i go into the change PO and in Item conditions/Update, (G-Copy Pricing and Redetermine taxes) then it is OK (but this is not ideal). When i do an RFC trace, using RSRFCTRC, i can see my Pur Org, Material Group and Tax code all being passed to R/3. Also, when i do a manual SE37 test on funct.mod. BAPI_PO_CREATE, it does calculate tax correctly - i am stuck - any help appreciated. rgs Adam

    Dear Poster,
    As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
    Best Regards,
    SDN SRM Moderation Team

  • Recording for a LSMW: item pricing conditions

    Hi Experts,
    I need your help! I am trying to do a recording for modifying sales orders conditions (for items): VA02, item 10, GO TO PRICING CONDITION ZXXX, change value to Z, go to item 20, GO TO PRICING CONDITION ZXXX, change value to Z,....
    My question is: how do I indicate the recording itself that a certain pricing condition has to be modified. Do not forget we are talking about items and the cursor will be in a different place in every item.
    Good ideas will be rewarded, that´s obvious.
    Regards,
    F

    Thanks Chandra. The FM you suggested worked fine for my problem / Regards Thomas

  • Copy Pricing Conditions from Sales Order to Billing

    Hi,
    Is there anyway to copy pricing conditions for item level from Sales Order to Billing Document at the time of creation of Billing Document.
    Thanks

    This question is not on topic for the Web Dynpro ABAP forum and has been locked.

  • How maintain pricing conditions in CCM 2.0

    Hi,
    We are using CCM 2.0, and SRM 5.0.
    Please let us know how should we maintain the pricing conditions in
    CCM, say when we enter item price in the individual item attributes, we
    want to maintain different prices, say if 10 items are purchased they
    cost Rs 100 and if 20 items are purchased they cost Rs 75, and so on
    and so forth, and also tax conditions such excise duty, sales tax etc.
    Please let us know how can we achieve the same through CCM.
    Kindly revert back at the earliest.
    Thanks,
    Swetha

    Hello,
    first part of your question can be achieved in standard /CCM/PRICE attribute.
    Gordan

  • MM - Purchasing Information Record/Pricing Condition

    Hello MM world,
    I'm taking this opportunity to log an issue I can't find an answer for and I would appreciate to know if someone out there would share his/her knowledge with me.
    So here's the question:
    I'm trying to determine an additional pricing condition type (discount) during the creation of a purchasing info record (me11).  The default PB00 gross price condition type is automatically proposed.  Attached to that condition type, you can indicate a pricing schema/procedure that has what they refer to as ‘condition supplements’.  The condition supplements pricing schema looks like an ordinary pricing procedure, however, SAP has confirmed that condition technique or access sequence determination does not work within the info record due to conflicting validity period between the info record and the additional pricing condition types.  So, what I am wanting to do is write both a requirement and alternative condition routine for the ZPIR condition to calculate the discount amount.  This will work fine, however we can only hit the routines IF the ZPIR condition supplement is automatically proposed.  If the condition type is presented, we can hit the routines without a problem…..the challenge is, we cannot figure out how to automatically propose the condition supplements, in our case ZPIR, without clicking the icon  during create.
    So, what I am wondering is if it is possible to write something in the requirement or alt condition routine attached to PB00 to programmatically add ZPIR to the info record, which would then invoke the requirement and alt condition routine that would determine the discount value.
    Or is there anything else we can do to make this work?
    Thanks a lot, I appreciate any input.
    Mo

    Hi Mo Arabat,
                       Looks good .Once agarin check up your configuration throug this link.
    http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
    Cheers
    Hareesha k

  • Pricing condition record, calculation type F volume, scale basis E net weig

    HI SAP Gurus,
    I have a question on pricing condition records.
    I have a requirement that needs to populate discount based on total net weight on the PO.  For example, if total net weight is greater than 1000 LB, it should give 10 cents discount per GAL.  The base UOM of the material is EA, GAL is an alternative UOM and Order Pricing Unit.  I can make the pricing condition works if the discount is per LB.  However, it doesn't work for discount given per GAL.  The calculation type is F volume and sacle basis is E net weight.  Pls advise what I need to do to make it work.  Thank you so much!

    closed

  • Regarding Pricing condition

    Hi Friends
           I have a Question that I re determined pricing condition type Pr00 but it showing in Transaction Code vk11 only not showing in vk31 and if enter in vk31 manually the error is coming that the table 304 is not defined for this condition type what is it mean and why it is not coming in T code  Vk31 Please give detailed answer ?

    Hello,
    Please take into consideration that the transactions VK31, VK32, VK33 and VK34 are running under a totally different logic than the transaction VK11 - VK14.
    The logic doesn't work through condition tables, because of the fact that the condition sets can be selected by different types of conditions.
    I know the error you are talking about. It is VK024. This occurs because only conditions that appear in the F4 dropdown list will work for you. If it's not there then you will get the error.

  • Pricing condition,automatic display without doing VK11 firstly, how ?

    Hi all, another question.
    I have a pricing condition in my sale order. and its value is determined by Pricing Conditions Routines with Conditions Value.
    How can it automatic display in the condition of my sale order, without doing VK11 firstly.
    My english is poor, so I hope u can understand these.

    Hi
    As I said in my previous thread , go to VOFM->Pricing, and check in the requirements if any standard requirements are meeting your requirement or not .If it is not meeting then create a new requirement with the help of  technical consultant.  and assign the requirement  in the Pricing  procedure requirement feild for the condition type and then check wheather it is capturing the price or not in the sales order and billing documents.
    Regards
    Srinath

Maybe you are looking for