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>

Similar Messages

  • CRM 2007 - Pricing procedure could not be determined

    Hi Gurus
    We starting an implementation of CRM 2007.
    For my Service Ticket transaction we are receiving the message "Pricing procedure could not be determined". We  do not need any Pricing as this is purely a service orientated call centre and pricing has no impact on the services we provide.
    We're using the dummy service product "INVESTIGATION".
    I've tried modifying the customizing to use a Pricing Procedure but this has failed to work.
    Is there config which will prevent this error from showing up in the first place.
    Maximum points for a speedy response.
    Many Thanks
    Panduranga

    Hi Vishant
    I checked the following
    1. Assign the sales area of your sold to party a customer pricing procedure.
        In transaction BP for my customer in role "Consumer" data is as follows:
        Sales Org - Defined
        Dist Channel - Defined
        Billing Tab
                Cust Pric Procedure: Standard
    2. Assign your transection a document pricing procedure.
         Transaction has Leading Category "Service Process" is not possible to assign a document pricing procedure. Unless you know of another way?
    3. for document pricing procedure, customer pricing procedure and sales area data, define the pricing procedure to be used.
        Under SPRO - IMG - Customer Relationship Management -
                  Basic Functions - Pricing - Pricing in the Business
                  Transaction - Determine Pricing Procedure.
        Sales Org, Dist Channel, Division, Doc Procedure (S - Service Process), Cust Pric Procedure (Standard), Procedure ((0CRMBP) used this as it only has one condition)
    4. in product master data, define the values of condition types being used in the pricing procedure (if you dont need the prices, you can just define them as zero).
    Added conditions to the Product
    Unfortunately I'm still receiving the same error, can you assist further?
    Regards,
    Panduranga

  • Getting Error "Pricing Procedure could not be determined" in CRM Functional

    Hi Experts,
        While creating Quotation for Products, am getting error message of  " Pricing Procedure could not be determined".
    Kindly reply, how 2 resolve this by steps-by-steps.
    Thanks..
    Edited by: poorav4293 on Aug 6, 2011 12:27 PM

    Hi,
    Go to SPRO-> IMG-> Basic Functions-> pricing. Here goto second node & select determine pricing procedure.
    Here check the combination....
    sales org-distribution channel-doc price-cust price-pricing procedure.
    Here see the corresponding pricing procedure which should be proper based on the condition types.
    Thanks!
    Aswith.

  • Pricing Procedure could not be determined

    Hi..
    basic doubt -- but causing issue.
    I have assigned the combination of sales area + Doc. Pric Proc + Cust Pric -- > Pricing Procedure in customizing.
    customer pric prc. -> assigned to BP sales area , billing data (Also seen on Prices tab of transaction)
    Doc pric proc - > assigned to the transaction used.
    Sales area of transaction -- > same as used to assign pric proc
    Still error creating transaction - TA standard order, Message no. CRM_PRIDOC_COM401 - Pricing Procedure Could not be determined. Also the error says to assign a pricing procedure to the combination of sales area + doc pric proc + cust Pric proc which I have already done.
    But on the prices tab of transaction I cant see the "Pricing Procedure" and a blank screen on Conditions Tab of transaction.
    any clue.. pl help

    Hi,
    Please check again if your SALES AREA at header level is picked correctly and which matches with the SALES AREA in the PRICNG procedure determination
    ALSO if the above is maintained correctly, it might happen that you have created the transaction earlier then you have assigned the sales are to the Customer along with the BILLING tab information.
    Run one report
    HRBCI_ATTRIBUTES_BUFFER_UPDATE
    If you have done the second one then just delete the customer, assign any other customer with which this issue would not appear and the error would go. Now again delete the customer and reassign your previous customer and check.
    Regards
    Surendra More

  • Error message: the appropriate pricing procedure could not be determined

    Hi SAP friends,
    What does this error message means please?
    The appropriate pricing procedure could not be determined because no entry with keys 'M100 20 P1' 'A' '1' exists in table 683V.
    Tcode: VA01 (sales order).  
    Regards,
    Bahia.

    Hi Bahia,
                    This error means the pricing procedure has not been done.To assign your pricing procedure to sales area go to the transaction "OVKK" and specify sales org/dist channel/div/document pricing procedure/customer pricing procedure and the defualt condition type. This would solve your problem.
    Regards
    Ram Pedarla

  • I want to keep two price in one pricing procedure can it be possibl;e

    i ve two price in my pricing procedure
    wen i m giving the price of second  one first one is comming inactive
    so how to configure and shuting out this problem
    please help me GURUs
    with hope
    subrat

    like this
    basic price @36.11 for 300unit is 10833
    MRP @117 for 300units 35100
    MRP price after [email protected]% 23341.50
    Total basic price 10833
    assesable price after abatement 23341.50
    assesable value 10833
    excise duty on MRP after abatement@16% 3735
    CESS on excise duty @2% 75
    CESS duty for secandary higher education@1% 37
    total net sales 14680
    sales tax [email protected]% 1835
    total value 16515

  • Relation between Tax procedure and Pricing procedure

    Dear All,
    I would like to get more clarity on Tax procedure, Pricing procedure.
    a) Why do we have Tax procedure and assigned to Country?
    b) If the tax procedure has been created and assigned to Country-IN (in FI module), then why do we need to create pricing procedure with same condition type for purchasing in MM module?  We are even creating lot of pricing procedure for Sales in SD module.
    Regards
    Manivannan R

    Hi
    Tax
    During SD document transactions, tax calculation procedure TAXUSX is only relevant to determine the tax liability accounts for output sales tax. Notice that in pricing procedure RVAXUS, the condition types XR1 - XR6 carry the tax rates and tax amounts - resulted from the external tax system calculation - which is posted to tax G/L accounts. However, the tax accounts are not specified in the pricing procedure but rather in the tax calculation procedure.
    Tax codes are the link between pricing procedure and tax calculation procedure.
    Pricing
    The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
    Which sub-totals appear during pricing
    To what extent pricing can be processed manually
    Which method the system uses to calculate percentage discounts and surcharges
    Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
    Example
    Example of a Pricing Procedure
    If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
    Pricing Procedures in the R/3 System
    The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
    Creating and Maintaining Pricing Procedures
    You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
    To reach the pricing procedure screen from SD Customizing:
       1. Choose Basic Functions
       2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

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

  • How to design a Pricing Procedure with both MWST and MWSI in it ?

    Hi there.
    My business requirement dictates that I can have both Tax inclusive(PR01/MWSI) and Tax Exclusive(PR00/MWST) items within a Single Sales Order.
    I know that One pricing procedure can only be assigned to 1 Document Type. So,
    Has anyone successfully created a Pricing Procedure that incorporates both the MWST and MWSI tax components ? If so, could you post a sample of the pricing procedure in order for me to understand how I should group the discounts/surcharges and reflect the Subtotals, as well as incorporate the MWST and MWSI all within a single Pricing Procedure ? I will also need to include the PR01 and PR00 conditions into the procedure too, right ?
    Really really hope someone with the experience, can aid me on this. I cannot find any relevant materials on this matter, both in OSS Sapnotes and within this forum.
    regards
    Poo

    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.
    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.
    It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
    Similarly in MM Module we have Pricing Schema.
    Regards,
    Rajesh Banka
    Reward points if helpful.

  • Excise Pricing procedure for Stock Transport Order in MM  with TAXINN

    I am an SD guy running STO  from manufacturing plant to sales depot
    AND not able to create JEX proforma excise invoice from NL
    to TEST my configuration, I created excise invoice in J1IS with respect to goods issue from NL from UB  means configuration is ok
    BUT base amount in J1IS is coming as zero because of missing excise conditions in MM  STO pricing procedure
    CAN anybody give me a sample EXCISE pricing procedure for STO
    AND  do i need to create records for the condition types in FV11 OR  MEK1 please clarify
    I know that calculation type 362 attached to BASB in TAXINN has something to do with this
    I am able to see chapter ID in J1IS
    And the relation between condition types in TAXINN and excise pricing procedure for STO
    And I am able to create excise invoice in J1IG with zero excise values
    I also maintained pricing procedure determination for JEX in OVKK that is document pricing procedure N pricing procedure JINSTOCK
    I think my explanation is sufficient enough
    please give A sample of TAXINN

    Hi Yoga,
    Here u not need to do VL10b.just follow this steps and try.
    In PO,Document type is UB and Item Category is U.
    After creating PO,In MB!B with reference that PO number and using movt type 541
    then u can see that stock in Transit.Now u do GR with respect to PO number.
    Thanks & Regards
    Suresh.
    > Hello MM Gurus,
    >
    > I am doing Stock transport order between 2 plants
    > under same company code.
    > I have maintained all the required settings.Following
    > is the process flow.
    >
    > 1.Creation of Purchase order with document type
    > UB.(ME21N)
    > 2.Creation of outbound delivery with respect to
    > Purchase order.(VL10B)
    > 3.Post Goods Issue from the supplying plant. (VL02N)
    > 4.Creation of Excise Invoice in supplying plant.
    > (J1IS)
    > 5.Goods receipt at the receiving plant.(MIGO)
    >
    > While I am doing Goods receipt in the receiving
    > plant, system is giving an error
    > message "Maintain Vendor for the Excise Invoice" -
    > Message no. 4F185.
    > Why this message is coming and how to resolve this?
    >
    > Thanks & Regards
    > Yoga

  • Pricing procedure issue ..

    Hi Expert,
    I have assigned pricing procedure to sales org. 1500 so that i am able to create sales order through VA01. I have assigned it through view V_T683V. Now i want to create MAM order in sales org. 1500 but at the time of creation i am getting error message as "No pricing procedure assigned". MAM order is created with tcode JHA1x.
    Please tell me what settings i need to do ?.
    Thanks.

    Thanks for your inputs Balaji,
    Below is the error message which i am getting and it's diagnosis.
    Pricing procedure could not be determined
    Message no. J7 513
    Diagnosis
    The pricing procedure is determined using the sales area, a document pricing procedure in the sales document type and a customer determination procedure in the sold-to party's customer master. The system was unable to determine a pricing procedure in sales area for document pricing procedure and customer determination procedure .
    Procedure
    You can either change the customer determination procedure in the sold-to party's customer master or set up a pricing procedure in sales area for document pricing procedure and customer determination procedure .
    From this could you please tell me where exactly i need to make changes?

  • How to activate new pricing procedure for old Pur Document

    Dear all,
    we have added some condition type  in our pricing procedure,every thing is ok but my question is this new condition added in pricing procedure are not reflecting in previously created purchasing document/po, how can we do it
    I kw that if we create new po all condition will be reflec as per in pricing procedure
    shakir

    Hi
    Assign Document pricing procedure Z in VOV8 for CR document type , Now do the pricing procedure determination in OVKK with sales area + Cupp+Dupp=new pricing procedure
    Example :
    In OVKK, determine with 1000 + 10+ 10 + A+ 1 = standard pricing procedure for normal sales
    For credit memo in OVKK determine with 1000 + 10+ 10 + Z+ 1 = New pricing procedure for Credit memo
    Then when you create a sales order (with document type CR ) with reference to billing document then the new pricing procedure will get copied.
    Regards
    Srinath

  • Pricing procedure in sap

    hi
    could any body tel me
    pricing procedure in sap............

    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.
    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.
    It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
    Similarly in MM Module we have Pricing Schema.
    Regards,
    Rajesh Banka

  • How to Change Contract pricing Procedure

    Is there a way after the contract has been created to change the pricing procedure it uses. I know you can do this in the sales order.
    Will reward any help.
    Thanks,
    Richard

    Hi
    Pricing procedure is determined from the customer master(customer pricing group in the sales area tab) + document pricing procedure in the order type + sales area
    So if you want to change the contract pricing procedure, change the document pricing procedure in the contract type you are using.
    And make sure there is a combination maintained for the new document pricing procedure in IMG to determine the pricing procedure in the contract.
    Regards
    Sreekar M

Maybe you are looking for

  • RRW3_GET_QUERY_VIEW_DATA in BW 3.0

    Hi erveryone, we needed the FM RRW3_GET_QUERY_VIEW_DATA  in an BW 3.0 environment. SAP Note 675000 showed us a way to create this FM in BW 3.0. After creating the FM it seems that we now have the problem, that all the  parameters in I_T_PARAMETERS ar

  • Home sharing to migarte from old PC to new PC not working

    I tried to set up home sharing to migrate from an old PC to a new PC.  Once set up and running, I can only copy from the new to the old and the old library never loads on the new PC.  Is there a configuration I need to change?

  • Vendor not released warning as an error message in shopping cart

    Hi, When we are creating a Purchase order in SRM R/3 system, If we select a vendor which is not released then we get the Error message saying Vendor is not released and processing stops there. Similarly while creating a Shopping cart with the same ve

  • How can I get rid of Japanese tokens/signs in the tabnames?

    On top of the tab-sitenames are strange Japanese tokens on the righthand-side. I can't get rid of them, even restart does not work. It's only visible in Firefox, not in my other browsers!

  • Need Info about Transcore AI1200 Reader

    Hi, Can anybody will answer these queries?? a) Is the interface/adapter to Transcore AI1200 Reader available? b) What happens in case there is a communication failure between the Reader and the Sensor Edge server. i.e. how would the Sensor edge handl