Determination of Pricing Procedure in SRM

Hi all,
I have worked on IPC CRM 4.0 and I know the settings related to Pricing.  Now, in <b>SAP SRM 4.0</b>, I am not able to figure out on what key fields Pricing Procedure is determined and where are the corresponding settings in SPRO.
Please Help!!
Thanks in Advance,,,
Regards,
Pratik

Hello Vangala,
     I have gone through the above settings again, but there is no settings given for  Determination of Pricing Procedure. Can you please be more specific.
Few more doubts:
1. What are the key fields on which Pricing Procedure is determined?
2. I am able to see only one Pricing procedure in SPRO->Supplier Relationship Management->SRM Server->Cross-Application Basic Settings->Pricing->Edit Calculation Schema; Is there any way through which I can view multiple Pricing Procedures.
Waiting for ur response.
Regards,
Pratik

Similar Messages

  • Maintain "Determination of Pricing Procedure" with different sales orgs. ID

    Hi experts,
    We have different sales orgs. ID for some of our sales orgs. in our Development/Quality/Production systems. When we maintained the "Determination of Pricing Procedure" in Development system for our new company and transported it to Quality system an error occurred. The sales org. ID we maintained in D wasn't available in Q. So we still have the same problem in Q as we had before. I have noticed that we have different ID for another company in our CRM system but it seems that someone has maintained "Determination of Pricing Procedure" manually for each system without any transport even if I don't think that's possible, but it look so. See pictures below:
    Development system:
    Quality system:
    O 50000125 in D is the same as O 50000075 in Q. This is working fine, but I don't know how you change it manually in Q as it seems to have been done in above picture!?
    O 50000178 in D is our new company. After transport to Q the same ID with the same values are transported correct. But the ID for the company in Q is O 50000150. So of course we still have the same problem in Q that we had before the transport.
    Does anyone know how to solve this? I guess you can't just change things manually in Q or is the correct way to do?
    Thank you in advance.
    Best regards,
    Hannes de Richelieu

    Hello Hannes,
    this really is a common issue. Org-Model can be maintained in every client and as the IDs are generated they can differ even if only the sequence in which you created the units is not the same in D/Q/P.
    What you might be interested in is report RHMOVE30. It is used to "transport" the Org-Model between Clients. Have a look here: http://scn.sap.com/thread/3537400
    This way you maintain the model once and distribute it across systems. My advise would be to take the one you have in P and refresh D and Q from it. You are still able to make adjustments in D and Q for testing. After a certain timeframe I would then refresh D and Q again to get them in sync.
    cheers Carsten

  • Regarding the pricing procedure in SRM

    Hi gurus,
    Can anybody tell me how the pricing procedure in SRM to be used  ???......And can i use this for bid invitation.
    Kindly help....
    Regds
    Kumar

    Hi
    Please check the in OVKK, weather you have maintained correctly or not.Also check in the Billing document type details what is the Document pricing procedure that has been maintained.
    Regards
    Srinath

  • How to determin the pricing procedure in copy control from invoice to so

    Hi,
    I have a request to create a sales order reference to a invoice. But in SPRO pricing procedure determination,i config different pricing procedure. 
    e.g. invoice ---procedure A
           sales order-----procedure B
    when i create the sales order , the procedure is A which is copied from invoice ,but i hope the procedure is B.
    how should i config the copy control. I have tried the B and C in pricing type of copy control.
    Thanks

    HI
    Try to maintain Different Document pricing procedure in Sale Document type and Billing type
    and also maintain settings in OVKK and test the cycle
    check and revert
    Regards,
    Prasanna

  • Pricing Procedure in SRM

    Hi,
    Can anyone explain how pricing procedcure works in SRM system. do we need to maintains Pricing procedure in MM?
    Thanks,
    Raj

    Dear,
      About SRM price:
    Condition for a product and a vendor
    condition for contract
    condition for BID
    condition for Catelog
    Priorities:1、Contract;2、Catalog;3、vendor;4、Product

  • Settings for pricing procedure in SRM

    Hi,
    We're implementing the ECS version and would like to know the settings that have to be done to setup the pricing. I understand we have the settings under configuration to  setup the condition types and pricing procedures in a similar way as it is in the R/3 backend system. But, we're unable to understand the settings that need to be done to link it to certain criteria for a particular Purchase order. For eg. in R/3 , we have the vendor schema in the vendor master data which is the link in combination with Purchasing Org to decide the Pricing procedure. But I don't find this data or such linkage in SRM.
    Can anyone provide an explanation or documentation for this.
    Any help will be highly appreciated.
    Regards,
    Lakshmi

    Hi,
    if anyone has a solution, I'm also interested how to customize pricing in SAP SRM 5.0.
    Regards,
    Sven

  • Pricing procedures SRM

    In ECC, one can have different pricing procedures in purchase order like local schema, imports schema etc. which can be selected by schema group vendor. How is this handled in SRM?

    Hi
    Which SRM version are you using ?
    <u>In SRM 5.0 , in case of extended classic scenario(ECS) , the final price is transferred as net price in SAP backend system. In the case ECS in SRM , IPC should be there and is mandatory. For ECS,IPC is mandatory.But with SRM 5.0,you dont need seperate installation of IPC,you have the Internal IPC for which you just need to see whether the VMC is activated.The VMC is exclusively used as a runtime environment for selected SAP Java components for example, Internet Pricing Configurator.</u>
    <u>Follow the below path in SRM 4.0 system -></u>
    SPRO-SRM-SRM server-Cross Appl Basic settings-Pricing...
    <b>Please go through the following pointers, which will definitely help -></b>
    Pricing Conditions
    Re: Determination of Pricing Procedure in SRM
    http://help.sap.com/saphelp_srm30/helpdata/en/72/f40f3c98ddaa4ce10000000a11402f/content.htm
    Condition types from SRM to backend
    Conditions for Pricing
    Pricing on SRM
    <u>Few SAP OSS Notes -></u>
    Note 782991 BAPI_PO_CREATE1 displays message V1 206
    Note 72199 Problem analysis update business volume data
    Note 90508 Tax condition type MWST in purchasing
    Note 175594 Double conditions after pricing procedure changed
    Note 32332 No order value update in Purchasing Info System
    Regards
    - Atul

  • Pricing Procuedure in SRM

    Hi Experts,
    I have doubts related to Pricing -
    1) In the case of R/3 we can define our own access sequence where as i do not see that option in SRM. So, does this mean we cannot define our own.
    2) Also, how does this access sequence, unlike in R/3 i dont think schema group vendor is there in SRM.
    Any help is welcome.
    Thank You
    Abhi

    Hi
    Which SRM version are you using ?
    Follow the below path in SRM4
    <b>SPRO-SRM-SRM server-Cross Appl Basic settings-Pricing...</b>
    <u>For pricing procedure(as in R/3) in SRM, you can find information related to this at</u>
    http://help.sap.com/saphelp_srm30/helpdata/en/72/f40f3c98ddaa4ce10000000a11402f/content.htm
    <b>See the related links -></b>
    Re: pricing procedures SRM
    Determination of Pricing Procedure in SRM
    No pricing procedure could be determined
    Pricing conditions in SRM
    Re: How To Transfer Pricing Types from R/3 to SRM
    Do let me know.
    Regards
    - Atul

  • Pricing procedure not getting determined in sales order

    Hi All
    I have did all the configuration settings for determining  the pricing procedure in the sales order,but it is not getting in the order.
    The assignment  sales area + customer pricing procedure + document pricing procedure are fine
    And in the customer master the customer pricing procedure is maintained properly
    And in document type TA,the document pricing procedure is maintained properly.
    Without IPC is it not possible to get the prcing procedure of CRM in to the sales transaction.
    I dont have IPC installed on my system.
    Appreciate ur help
    Regards
    Sreekar M

    Thanks Shalini for the information
    Then i think i cant create a billing document in CRM with reference to sales order...as the sales order is incomplete
    Is creation of delivery possible in CRM?
    Regards
    Sreekar M

  • Multiple pricing procedure determination problem

    Dear Experts,
    I have a situation in pricing procedure determination. Please advice. The details are given below.
    Pricing procedure is determined for the combination of Sales Org,
    Division, Distribution Channel, Customer Pricing Procedure and Document
    Pricing procedure.
    Say there is a sale happening through following organizational units.
    Company Code: 4260
    Sales Org: 3260
    Division: 02
    Distribution Channel: D1
    Customer: 9000000
    But the material is delivered from the plant that belongs to a different
    company code.
    Plant company code: 4262
    The customer 9000000 has customer pricing procedure maintained as 1 in
    the customer master.
    This will create following documents
    Sales order OR from 3260 to 9000000
    LF delivery
    F2 invoice from CC 4260 to customer 9000000.
    IV inter-company invoice from 4262 to 4260 through following sales area.Sales org: 3262
    Division: 04
    Distribution Channel: 99 (inter-company)
    Here the payer is 4260 which will have a customer pricing procedure
    maintained in the customer master (say 1-standard). The document pricing
    procedure is A.
    The pricing procedures determined for F2 invoice and IV invoice will be
    as per the below assignment.
    3260 02 D1 A 1 PRIPRO1
    3262 04 99 A 1 PRIPRO1
    The requirement is to determine another pricing procedure say PRIPROF
    which is specific to formula average pricing for both the invoice types
    i.e. F2 and IV. The determination will happen from below assignment.
    3260 02 D1 A F PRIPROF
    3262 04 99 A F PRIPROF
    The problem here is that we can not maintain two different customer
    pricing procedures (1 and F) for a single inter-company customer 4260.
    Therefore 3262 04 99 A F PRIPROF assignment is not possible as 4260 can
    either have 1 or F as Customer pricing procedure.
    And 3262 04 99 A 1 PRIPRO1 assignment is already in use so we can not
    replace 1 with F and change the pricing procedure from PRIPRO1 to
    PRIPROF.
    Can you please advice how can we resolve the issue of having multiple
    customer pricing procedure requirements for same customer to determine
    different pricing procedures?
    Thank you.
    WIth regards,
    Sahir Gaulkar

    Hi Ashish,
    Refer this links to understand links b/w the tables.
        http://www.sap-img.com/general/sap-r3-tables.htm.
        http://www.sap-img.com/sap-sd/important-tables-for-sap-sd.htm
    Thanks,
    Swamy H P

  • Error in Pricing Procedure Determination in Sales Order

    Hi All,
    I have created a Pricing Procedure and asiigned it with the SALES ORG, DIV, DISTR CHANL, CUSTOMER PRCDR and DOCUMENT PRCDR in SPRO.
    i have assigned the Cust Doc Prcd with the BP and the Docuemnt Prcdr with the respective transaction. And also created the Basic Price for product and Discount Price for Sold To Party via CONDITION MAINTENANCE.
    Still getting this error.
    Looking for the solution.
    Thanks,
    VS

    If you have check what RK suggested and is ok, then check also the customization of your transaction in spro>crm>transactions>basic settings>define transaction types.
    go to your transaction type and then in left panel select customazing header. there check if you have defined under pricing data the doc.pric.proc. (document pricing procedure)
    and also if you are not always using customer pricing procedure it is good to define in spro for determination of pricing procedure 1 determination rule which has filled only the folowing data:
    - sales organization
    - distribution channel
    - document pricing procedure (the one you defined on transaction - which I described above)
    - procedure
    and division (if you use the dummy one) and customer pricing procedure leave empty. this way the procedure will be determined even if it's not found from customer sales data
    And also be aware that once the error message for determination of pricing procedure appears it can't be removed so don't try the determination with already corrupted transaction.

  • Pricing Procedure Can't be determined

    Hi,
    I am working on CRM 5., When i create the sales order i am getting the following error "Pricing Procedure Can't be determined" I have maintained the pricing procedure in CRM.
    Is there any link with IPC and How to know whether IPC has been installed or not?
    Thanks

    Hi Devi,
    The error is because your pricing procedure is not being determined by your Customizing settings.
    You need to maintain the Pricing Procedure determination setting which can be determined using Sales Organization,Distribution Channel,Division,Customer Pricing Procedure and Document Pricing Procedure.
    For this you need to have appropriate Sales Organization,Distribution Channel,Division in your sales order at header level in Organization tab.
    Customer Pricing Procedure it is assigned to the business partner. You can find the same under Sales Area data, Billing tab.
    Document Pricing Procedure , is maintained in customizing of the transaction type at third level customizing.
    To maintain the determination of pricing procedure follow below mentioned IMG path
    Customer Relationship Management>Basic Functions>Pricing>Pricing in the Business Transaction>Determine Pricing Procedures
    M sure, once these settings are maintained you will surely be able to determine the price.
    Best Regards,
    Pratik Patel
    <b>Reward with Points!</b>

  • Problem in pricing procedure of scheduling agreement

    Dear All,
    I am creating a scheduling agreement, when i am giving condition type at item level a message occur "Condition type XXXX is not in procedure A M ZB1002" Message no. VK045.
    I am not able to understand from where this pricing procedure is picking. But in Define Schema Determination the pricing procedure is different, it is ZBLOSR.
    The same case is happening in info record while maintaining condition type, the same pricing procedure ZB1002 is picking up by default. I want to change the pricing procedure.
    Please help.....

    hi..
    have u maintained the combination of schema group for vendor schema group, purchasing org and pricing procedure...
    and assign this vendor schema group to vendor master...
    From this combination system getch the pricing procedure for particular vendor...
    go to spro..MM ..Purchasing..Condition...Define Price Determination Process..Define Schema Group..
    check these settings...
    Hope it works..
    Thanks..

  • Explain the Pricing Procedure

    Hi Friends
    Explain how the pricing is determined for an item, starting from the sales order
    Discuss the full cycle also make a mention  on  the Condition type controls, and Maintain pricing procedure controls.
    Kindly explain it with an example.
    Thanks

    Pricing Procedure is indeed an heart of SD module, reason being if everything else is working fine, but price is not being calculated correctly, the purpose of billing fails.
    An Overview of Determination & Configuration of Pricing Procedure is as follows:
    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. 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.
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table: 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: 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: 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: 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: 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.
    Step 5: Condition record: 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.

  • 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.

Maybe you are looking for

  • Creating a new row in a JTable

    How do i make a new row in a JTabel?

  • Upgrade issue in phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative

    Hello Team, Got hanged at the phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative,. Error: Checks after phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative! Last error code set: Detected 1 aborted activities in 'PHASES.ELG'<br/> Calling 'D:\usr\sap\X

  • GS60 won't detect all the external devices anymore and D drive disppeared

    Help!!! I just bought a msi gs60 six months ago. The laptop can't detect any flash drives or external storage devices anymore, but was able to read from smartphone. Also, more importantly, the computer has lost its second hard drive, which was 800 gb

  • Import from camera

    Any idea how to import from a camera these days? In Aperture it found the camera automatically and you could select photos and import. With Photos it seems that if I go to File > Import I can find my camera shown as an external drive but I can't then

  • Visual Studio 2008 & Oracle Problem

    Hi there, I've been going through a bunch of legacy reports in a project I support, they had got out of date with the database, so I was verifying the database for each one. They use data from an Oracle 10g database using a mixture of tables and view