Pricing Procedure: requriement routine and mandatory field

Hi,
In pricing procedure, which setting has higher proirty between logic included in requirement routine or mandatory field configuration?
I have a condition type to store list price (copy of PR00), and it is configured as mandatory.
However, I want to include a requirement routine saying that 'Only for a specific order type and sales organization, set this condition type PR00 as optional.
That way I can set this PR00 as possible to override the amount.
Any ideas?
Thank you in advance.
Pinkytak

I agree with all other solutions, but pricing anyway is very flexible to have to make routines.
If you want just to overwrite the amount, mandatory or not has little to do. Just allow manual changes in the condition type properties.
But if i understood your requirement correctly, i propose,  you let the mandatory condition type run normally, and  in certain sales type you insert another one, which with condition exclusion, will "deactivate" the mandatory one. In that way, you'll keep the initial one for reporting and statistical reasons.
If you come back with your business requirement (not the technical one) i'm confident that we'll come up with better solutions.
Regards
Agis
Edited by: Agis Katsafouros on Apr 20, 2010 1:50 PM

Similar Messages

  • Diff pricing procedure for invoice and sales order?

    can u please help me out in the following question
    Is it possible to have different pricing procedure for sales order and invoice?

    hi venkat,
    yes we can very well have different pricing procedures for order and invoice. for the combination of
    sales org + dist chan + div + <b>document pric proc</b> + cust pric proc --- > Pric Proc.
    we determine the pric procedure. So, just have a different document pricing procedure for sales order document type and invoice document type. You can have a different pricing procedure with this change.
    Hope it helps. Pl reward if useful.
    Thanks
    Sadhu Kishore

  • Different DOCUMENT PRICING PROCEDURES in SalesOrder and Billing

    Hi Experts,
    Can you please explain how system reacts and how it calculates PRICING if we maintain different DOCUMENT PRICING PROCEDURE in OR and different DOCUMENT PRICING PROCEDURE in F2?
    Thanks,
    Kanna.
    Edited by: kanna palle on Aug 29, 2008 3:17 PM

    It will use the dopp as the absis to derive the pricing procedure to calculate.Hence the pricing for Order and billing will be totally different. It depends on what pricing procedures you have maintained at both levels and if the conditions therein are different and for which conditions are different then it will have very little meaning though pricing will be calculated. Copy control would have no meaning then.Hence you should ensure consistency of data when redetermining pricing as well.
    regds
    Jude

  • Diff pricing procedures for contract and invoice

    Hi all,
    My client is into service industry.He is using two pricing procedures for contracts and invoice. Now the requirement is they want to use a single pricing procedure for both contracts and invoice. Now i need club them into one and i need to delete some condition types which are not in use.What are all the factors do i need to consider before clubing them into one??
    Can anybody guide me in this regard?/

    You need to foreclose all your existing contracts and create a new one with the new pricing procedure
    G. Lakshmipathi

  • Is it possible to have different pricing procedure for SO  and invoice?

    Hi,
    Is it possible to have different pricing procedure for SO
    and invoice?

    Hi Kiran35086 
    --Yes you can have it.But it is based on the business requirement
    --Create 2 Document pricing procedures & assign one in VOV8 & another in VOFA
    --In Sales Document VOV8 you maintain different  document pricing procedure Ex A
    --Go to VOFA & select your billing document type in Account assignment/pricing assign the document pricing procedure.EX- B
    --Create condition records in VK11 for the condition types which are included in the pricing procedures
    --Maintain pricing procedure determination in OVKK with 2 different Document pricing procedure & save it
    --When you raise SO in VA01 you will find one pricing procedure & when you raise billing in VF01 you find another pricing procedure in conditions.
    Let me know if your problem is solved
    Regards
    Pradeep

  • New pricing procedure for debit and credit memo

    Hello Sir,
    After defining new pricing procedure of debit and credit memo for retro billing.copy control using pricing type b in VTFF but it take billing pricing in credit and debit memo.not in new pricing .Is am missing something please suggest proper solution .

    Thanks for precious time given please go through this
    Tax Calculate
    Basic
    10.0000
    100.0000
    12%
    1.2000
    12.0000
    2%
    0.0240
    0.2400
    1%
    0.0120
    0.1200
    Total
    11.2360
    112.3600
    12.50%
    1.4045
    14.0450
    Net
    12.6405
    126.4050
    tax calculate like this but it come
    Basic
    10.0000
    100.0000
    12%
    1.2000
    12.0000
    2%
    0.0240
    0.2400
    1%
    0.0120
    0.1200
    Total
    11.2360
    112.3600
    so,plz suggest how it calculate including vat
    vat/cst

  • Credit memo and mandatory fields in Sales order

    Dear all,
    I have 2 problems, hoping these are not too basic questions I'm asking here.
    1). I have created a sales order for credit memo's and I'm using the standard billing type G2.
    The amounts are negative in the order & in the billing document, however, when transferring to FI, it is posted as a normal invoice (Debit customer) instead of credit memo.
    Where are the posting keys defined or where do you determine which kind of posting will happen in FI based on the billing document?
    2). When creation a sales order (VA01), the sales office and sales group should be mandatory fields. What is the best way to do this? Or is the only option to go via the document completeness check?
    Many thanks!
    Best regards.

    Hi There,
    > 1). I have created a sales order for credit memo's and I'm using the standard billing type G2.
    > The amounts are negative in the order & in the billing document, however, when transferring to FI, it is posted as a normal invoice (Debit customer) instead of credit memo.
    >
    > Where are the posting keys defined or where do you determine which kind of posting will happen in FI based on the billing document?
    This is the standard SAP behavior. Simple thing, All the values are negative so when it will post to FI
    It will be like
    Dr  Customer Invoice amount ( which is negative ) so end result is +ve. ( as Debit is -)
    I hope its understandable.
    For example:
    While creation of simple invoice say of 1000 $
    Entries were Dr Customer 1000 $
                         Cr Revenue    1000$
    Now After Credit memo
                        Dr Customer    -1000 $
                         Cr Revenue    -1000 $
    Which will nullify each other.
    > 2). When creation a sales order (VA01), the sales office and sales group should be mandatory fields. What is the best way to do this? Or is the only option to go via the document completeness check?
    The best way is to include these two fields in the Sales order incomplete procedure in OVA2. Put Error/warning as required by you.
    Thanks,
    Raja

  • BAPI function module name and mandatory fields

    Give the name of BAPI function module for pricing change into the transaction VA05 ?
    What are the mandatory fields ?
    Please give a exemple code to do this.

    Hi,
    VA05 is for list of sales order. But if you want to change pricing of material stocks go for follwoing fn module.
    BAPI_SALESORDSTCK_PRICE_CHANGE
    If you want other BAPI for sales related, just go to SE37, give BAPISALE and press F4, you will get all the BAPI fn modules.
    Rewards points if helpful.
    Regards,
    CS.

  • Pricing procedure mm Packing and forwarding to be calculated on Basic price

    Hi experts
    we are having one pricing procedure where in details are as follows.
    basic price                                                 100
    excise                                                           12.36
    total                                                             112.36
    P & F 2 %  0n (112.36)                                   2.24
    total                                                             114.60
    Vat 5 % 0n (114.60)                                       5.73
    Grand total                                                   120.33
    Now we require new pricing procedure wherein  Packing & forwarding to be calculated on basic price & not on basic + excise
    so can we change in same pricing procedure or we have to create new ?
    Can you elaborate with the  configuration steps ?  Any changes required in Tax procedure also or not ?
    Thanks in advance
    regards

    Hi,
    No need you can add the condition type to the pricing procedure at spro--mm---purchasing--pricing procedure ---calculation schema with proper calculation to get the percentage on base price and add to the total .
    Regards,

  • Behaviour of radiobutton and mandatory fields in a selection screen

    Hello all
    In the selection screen in a report , I have one mandatory field F1 and 2 radio button  p_val and p_prov. there's no relationship between p_prov, p_val & F1.
    I have 2 others fields p_dom and p_seg which are active when I select p_val : they are also mandatory when selecting p_val.
    p_prov is the default radiobutton so p_dom and p_seg are inactive when the screen appears
    I have 2 problems :
    1 - First I select p_val (the message for F1 as mandatory appears -> normal) so p_val appears selected but The 2 fields p_dom and p_seg are not active. I would like them to be active even I have not filled F1.
    2- I fill F1then I select p_val, so p_dom and p_seg are active, I fill only p_dom but not p_seg : I select radio button p_prov (the message for p_seg as mandatory appears -> normal) : p_prov appears selected but I don't want it.
    Thanks for your help.
    below the code of selection screen with event at selection-screen output :
      SELECTION-SCREEN BEGIN OF LINE.
      PARAMETERS : p_val RADIOBUTTON GROUP GR2 USER-COMMAND radio.
      SELECTION-SCREEN COMMENT 4(37) text-132.
      SELECTION-SCREEN END OF LINE.
      PARAMETERS : p_dom TYPE GSBER OBLIGATORY MODIF ID SC1.
      PARAMETERS : p_seg TYPE FB_SEGMENT OBLIGATORY MODIF ID SC1.
      SELECTION-SCREEN BEGIN OF LINE.
      PARAMETERS : p_prov RADIOBUTTON GROUP GR2 DEFAULT 'X'.
      SELECTION-SCREEN COMMENT 4(37) text-133.
      SELECTION-SCREEN END OF LINE.
    AT SELECTION-SCREEN OUTPUT.
      LOOP AT SCREEN.
        IF SCREEN-GROUP1 = 'SC1'.
          IF p_prov = 'X'.
            SCREEN-INPUT = '0'.
            SCREEN-REQUIRED = '0'.
          ENDIF.
          IF p_val = 'X'.
            SCREEN-INPUT = '1'.
            SCREEN-REQUIRED = '1'.
          ENDIF.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.

    hello Jerome,
    Here you go.
    2 things to remember:
       1. Remove the obligatory addition from all fields.
       2. Remove the input required while changing the screen elements.
    PARAMETER: f1 TYPE c LENGTH 10.
    SELECTION-SCREEN BEGIN OF LINE.
    PARAMETERS : p_val RADIOBUTTON GROUP gr2 USER-COMMAND radio.
    SELECTION-SCREEN COMMENT 4(37) text-132.
    SELECTION-SCREEN END OF LINE.
    PARAMETERS : p_dom TYPE gsber MODIF ID sc1.
    PARAMETERS : p_seg TYPE fb_segment MODIF ID sc1.
    SELECTION-SCREEN BEGIN OF LINE.
    PARAMETERS : p_prov RADIOBUTTON GROUP gr2 DEFAULT 'X'.
    SELECTION-SCREEN COMMENT 4(37) text-133.
    SELECTION-SCREEN END OF LINE.
    AT SELECTION-SCREEN OUTPUT.
      LOOP AT SCREEN.
        IF screen-group1 = 'SC1'.
          IF p_prov = 'X'.
            screen-input = '0'.
          ENDIF.
          IF p_val = 'X'.
            screen-input = '1'.
          ENDIF.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    AT SELECTION-SCREEN.
      CHECK sy-ucomm <> 'RADIO'.
      IF p_val = 'X'.
        IF p_dom IS INITIAL OR p_seg IS INITIAL.
          MESSAGE 'Fill Mandatory fields' TYPE 'E'.
        ENDIF.
      ENDIF.
      IF f1 IS INITIAL.
        MESSAGE 'Fill F1' TYPE 'E'.
      ENDIF.
    Thanks,
    Jinesh.

  • Different pricing procedure between CRM and ERP

    Hello,
    we`re using a CRM system which is connected to a ERP system. As not all pricing conditions from ERP are needed in CRM (an in addition the ERP pricing procedure is very complex), we would like to use a different (with less conditions) pricing procedure ind CRM.
    But now, when we transfer an order from CRM to ERP, the pricing procedure from ERP gets downloaded into the order in CRM and the prices are lost. Therefore I have 2 questions:
    1. Is it not possible to have a different pricing procedure in CRM than in ERP?
    2. Is it possible to stop transferring the pricing procedure from ERP back to CRM when transferring orders?
    Thank you in acvance for your help
    Jan

    Hi, Jan.
    1. Is it not possible to have a different pricing procedure in CRM than in ERP?
    Yes. You can use different  pricing procedure for you business documents.
    We use this for quotation management with inergation CRM-ERP.
    But, You must use same Condition Types and other objects.
    Denis.

  • Pricing Procedure for RFQ and Contract

    Hi All,
    I have  configired new pricing procedure for external purchaseing documents import and export business.
    This pricing procedure is working fine for  PO but while manitan quatation and create contract Iam not able see configured pricing procedure.
    Please let me know how to resolve this issue.
    Thanks
    Nagaraj.K

    Hi
    Have you maintained a supplementary pricing procedure, if not please maintain a pricing procedure similar to RM0002, assign this to the Basic condition type PB00 or your customized one.
    Thanks & Regards
    Kishore

  • Examples of pricing procedure related frieght and vat

    hi friends
    i want to create pri proc with fright and vat
    please give some examples of pri proc related to frght vat
    waht r the pre confguration requ for frieght and vat

    The following are the VAT Condition Types i found in my system.
    J1AP   -        VAT Perception I
    J1AQ   -        VAT Perception II
    J1AR   -        VAT Surcharge RNI
    J1AU   -        VAT
    Creating Pricing Procedure
    simple pricing procedue
    Reward Points if useful.

  • Plant field validation and mandatory field in CC master

    Can we have a validation of a field e.g. Plant in WBS level and substitution at the same time.
    In projects Plant gets substituted during saving project from Cost center master data. At the same time can I maintain a validation that if this field is not updated it would would not allow save project.
    Which one Validation or Substition is prioritized first during project saving?

    Hi,
    I think it is possible to have substitution and validation at the same time. SAP document says " If you have defined a substitution that contradicts a validation condition, the system informs you of this by displaying a message. We can therefore say that validation has priority, or is u201Cstrongeru201D than substitution."
    Warm regards,
    Srinivas Potluri
    Edited by: Potluri Srinivas on Aug 2, 2011 7:07 PM

  • Diff betwn Manual field in Pricing Proc(V/08) and in Condition type Screen

    Hi,
    Can anyone please help me in knowing what is the difference between "Manual" field maintained in Pricing Procedure(V/08) and "Manual" field maintained in V/06.
    Thanks in advance.
    Regards,
    Rianka.

    Hi,
    Let me explain with some cases.
    Case 1:  I need a pricing condition type to get the value from condition records and at the same time user can be able to modify it
    Keep manual indicator in V/06.  There is no need to keep manual indicator at V/08.
    Case 2:  I'm having a manual header condition type for which user will enter the value at document
    Keep it as manual in both the places.
    Case 3:  I'm getting a value from EDI such as customer expected price which should not be edited inside the conditions.
    Keep it as manual in V/08 and restrict manual entry through V/06.
    You dont need to keep access sequence for condition types which are marked as manual in V/08.  It should get value either using routines in Altcalc type or manual entry inside the document by user.  And all the header conditions are set as manual in V/08.  Hope now it clarifies.
    Regards,
    P Gomatheeswaran.

Maybe you are looking for