Picing procedure determinatin ( OVKK)

Hi Friends,
In pricing procedure determination ( ovkk) screen, we maintain  one condition type beside of pricing procedure , what is the exact functionality of that condition type.
Thanks inadvance
Nrasimha.

Please search the forum.  This question has been answered many times in the forum.
thanks
G. Lakshmipathi

Similar Messages

  • How to assign Pricing Procedure in OVKK?

    Hi,
    Just like to confirm if I am using right procedure to assign Pricing Procedure in OVKK.
    I am copying the following,
    SOg ..DC.. DIV.. DPP.. CPP..
    1000..10...  00....A.......1...
    PRICING PRO..C TYP
    RVAA01...          PR00
    and changing to already created DC and DIV in my Enterprise Structure, maintaining the rest as it is.
    Hope you guys will guide me , as always.
    Thanks.
    Naz

    hi,
    Pricing Procedure
    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.
    Hope this helps you.
    Regards,
    Jaiprakash.P.T

  • Picing procedure change for ope SO

    Hi all i have changed to a new pricing procedure .
    My open SO which has old pricing procedure when i am creating the billing automatically it is updating to the new pricing procedure ., is there any way to make open SO in old pri procedure have the old one in the billing also.

    Dear Mahesh,
    Standard SAP would redetermined Pricing Procedure when you create the Invoice thru: Sales Area + Doc. Pricing Proc + Cust Pric Proc.
    In you case I doubt whether the setting 'D' in VTFL or VTFL would help because system will anyways determine the new Pricing Procedure which is currently attched to the combination of Sales Area + Doc. Pricing Proc + Cust Pric Proc.
    Thus, I believe you will have to develop new Copy Control Routine or Use available User Exits with help from your ABAPer.
    Hope this helps...
    Thanks,
    Jignesh Mehta

  • How  does systemn determin pricing procedure of billing type

    How does system determinate pricing procedure of F2???????????????????
    By doc.pric.proc? but in IMG, it is empty!!!
    and I don't think it is reference sales order's pricing procedure
    because if you use OR + TAN, the reference document of billing is delivery order!!!!!!

    Hi zhang
    In pricing procedure determination OVKK , whatever DuPP you maintain that is linked to Billing document
    In VOV8 we can see the CuPP  of the document . so if the DuPP is linked to CuPP in OVKK then the same pricing procedure will be flowing to billing document also  . Apart from that in VOV8 also make sure that , in billing data you are maintaining the billing  type
    Regards
    Srinath

  • Pricing procedure error in Sales Order

    Hi,
    I have made all necessary SD config. setting for pricing procedure creation and determination in Sales orders. But while creating a sales order I am getting an error as "No pricing procedure could be determined as entries are missing in TAble 683v. but I can see the relevant entry in this table. How this error can be rectified. i am unable to procees for sales order creation.

    Hi,
    Check in sales document type - VOV8 Which document price procedure you maintained under transaction flow tab
    Check in customer master which customer master pricing procedure maintained in sales area data >> sales tab >> pricing/statistic.
    Then in pricing procedure determination OVKK maintain
    Sales orgz + Dchl + Div + Document price procedure + Customer price procedure = PRICED PROCEDURE
    Kapil

  • 2 pricing procedures for the same sales area

    Hi Gurus.,
                  My client requirement is the client requires 2 pricing procedures for the combination of Same sales areaDEocument Pricing procedurecustomer pricing procedure in OVKK
    He doesnt want to use new sales area or new document pricing procedure or new customer pricing procedure,I know that in standard SAP it is not possible.
    Can any of the gurus throw some light on this.Some work around is required here,So can u please say the required changes in Standard functionality.
    Thanks & Regards
    Narayana
    Message was edited by:
            manam narayana
    Message was edited by:
            manam narayana
    Message was edited by:
            manam narayana

    Hi Gurus.,
                   First of all thank you very much for giving me so tremendous response, But my client requirement is,
                  He has one customer and for that customer when raising an order ,for some orders Tax shouldnot caliculate and for some orders Tax should be caliculated,
            For example :  If he gives price 100,Then the base price should be 100,For some orders he  gives price as 130 rs which is inclusive of tax like 110 should be the base price and 20 rs tax should get caliculated
               So i have tried in the pricing procedures and we have standard pricing procedure RVAA01 & RVAB01 ,In which RVAB01 is the price inclusive of tax procedure,We can assighn different pricing procedures if any of the combination in OVKK is changed,But he dont want to change the combination in OVKK.
            So client asks now when he raise an order he decides how the price should be caliculated, i.e the price may be he give price or price inclusive tax,of which the pricing procedure should automatically split the tax and price accordingly,He is asking in the way like when we raise a sales order we should do like a pop up box should appear asking which pricing procedure should be selected,So on selecting the pricing procedure the order should caliculate based on the selected pricing procedure
    Thanks & Regards
    Narayana

  • Error Message regarding define pricing procedure determination

    Hi Guru:
    I encountered the issue when defining pricing procedure determination,when I tried to input the sales organization,distribution channel and pricing procedure and condition type into the column,the error message popped up and said "An entry already exists with the same key" how to fix?

    Dear Friend,
    The error message is self-explanatory. It means that already there exits the Combination of  Sales Org / Div / DC & Pricing Procedures on OVKK.
    Check the existing entries in OVKK & maintain a new entry with different Combination of Sales Org / Div / DC / Doc Pricing Proc / Cust Pricing Proc.
    Hope this helps...
    Thanks,
    Jignesh Mehta

  • Intercompany Billing - pricing procedure

    Hi,
    Can somebody please explain to me what is the exact pricing procedure in intercompany billing, where would IV condition type fit in and what sort of pricing procedure to use.
    If somebody can send screenshots of the steps, it would be of immense help to me...
    Thanks in Advance,
    John.

    Dear John,
    You can do like this,
    -->You can define new pricing procedure for inter company process in the IMG T.Code V/08
    IMG->Sales and Distribution>Basic functions>Pricing>pricing control-->Maintain pricing procedure
    -->Maintain the condition types as per the requirement in your inter company billing pricing procedure.
    To determine this pricing procedure while creating inter company billing you need to do these settings
    -->Define new document pricing procedure and assign this document pricing procedure to your inter company billing type(IV) through this IMG path.
    IMG->Sales and Distribution>Basic functions>Pricing>pricing control-->Maintain pricing procedure determination
    -->Define document pricing procedure
    -->Assign document pricing procedure to billing document
    -->Now you determina the inter company billing pricing procedure through OVKK transaction with this key combination.
    Sales areaInter company billing document pricing procedureCustomer pricing procedure----->Inter company billing pricing procedure.
    -->Maintain proper condition records if required in VK11 transaction.
    -->Now system will determine the newly defined inter company billing pricing procedure when you create intercompnay billing document(IV).
    I hope this will help you,
    Regards,
    Murali.

  • Returns pricing procedure for sales document RE !!

    Hi, friends !
    I have doubt in the logic that while doing sales flow from order to billing it picks one pricing procedure. And for returns i want another pricing procedure should be picked.
    As we are giving reference fo Invoice for Returns document it normally picks the old pricing procedure but not the new pricing procedure.
    Please let me know how to configure to pick the new pricing procedure for RE document type.
    Thanks & Regards,
    Sreedhar.
    Email ID: [email protected]

    Hiii Sredhar How are you !!!! where are u !!!
    Go through this steps
    --> First you define the New pricing procedure in the transaction V/08.
    >You define the new document pricing procedure in the IMG path>SPRO>Sales and distribution>Basic functions>Pricing>Price control>Define and assign pricing procedures>Define Document pricing procedure.
    -->Now you assign this Document pricing procedure to the Return order type in the detail screen.
    -->Now you determine the pricing procedure through OVKK transaction with new defined document pricing procedure and pricing procedue.
    -->Maintain the condition records for that condition types.
    -->Now you create the Return order it will pick the new pricing
    Still if it not picks check the Copy control settings In the VTAF transaction
    Go to item details there you eneter "B" carry out new pricing in the Pricing type field
    I hope it will help you
    Regards,
    Your Murali.T

  • Pricing step by step procedure

    Dear Experts,
    pls send me the pricing notes ( step by step procedures) at my mail id
    [email protected]
    always reward point ...
    Thanks b4 hand
    Vaibhav

    Hi Vaibhav,
    Following are the steps you need to follow for pricing.
    Reward if this helps you...
    PRICING (PG)
    This concept is based on condition technique.
    It’s the combination of:
    1)     Condition Tables
    2)     Access Sequence
    3)     Condition Types
    4)     Pricing Procedure
    1. Condition Tables: - Condition table contain the key fields for maintaining condition records.  I.e. in other words condition records are stored in condition table.
    Note: - A condition type can have multiple condition tables.
    Note: - A condition table can be used for multiple condition types.
    Defining condition tables: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define condition tables [V/03]
    Create condition tables
    Enter a table number beyond 600
    From the field catalogue, which is there on the right side of the screen select the required key fields.
    To get the valid on / valid to fields while maintaining the condition records we need to check the field “with validity period”.
    Go to icon Technical View
    The fields which are marked, as footer field appears at the footer level at the condition records and the remaining fields appears at the key level.
    Select the Icon Generate for generating the condition table.
    To save the condition table, select the button Local object.
    2.     Access Sequence: - Access sequence is a search strategy with the help of which the system gets the valid condition records.  It contains the required condition tables in the required order.
    Note: - If required an access sequence can be used or assigned to multiple
    Condition types.
    Note: - The order in which the condition table are placed in access sequence
    is important generally it is most specific to most generic
    Defining Access Sequence: -
    SPRO
    Sales and distribution
    Basic functions
    Pricing
    Pricing control
    Define access sequences
    Maintain access sequences
    Go to new entries and define the access sequence.
    Select the defined access sequence and go to accesses.
    Go to new entries and place the condition tables in the required order
    While placing the condition tables check the field “exclusive”.  By doing so if the system finds a valid condition record in the first condition table it will not go to the next condition table
    Select the condition table and go to fields the system gives the warning message “the field assignment has not yet been made” say enter till we get the fields.
    Repeat the same step for all the condition tables and save it.
    Note: - After defining the access sequence assign it to the corresponding condition type.
    3. Condition Types: -
    Defining condition types: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define condition types.
    Maintain condition types.
    Functionality of a condition type: -
    Access Sequence: - In this field specify the corresponding access sequence for the condition type.
    Condition class: - It is the preliminary structuring of condition types.
    Ex: - Surcharges or discounts and price
    Plus/Minus: - If we specify negative here a condition type becomes discount and if we specify positive it becomes surcharge.
    Calculation type: - Determines how the system calculates price discounts and surcharges in a condition type.
    For Ex: - the system can calculate a price as a fixed amount or as a percentage based on the quantity, weight, or volume.
    Condition Category: - It’s a classification of conditions according to pre-defined categories.
    Rounding Rule: - The rule that determines how the system rounds of condition values during pricing.
    Manual Entries: - Indicator which controls the priority with in a condition type between a condition enter manually and a condition automatically determined by the system.
    Amount / Percent: - If we check this field the amount / percentage of a condition type can be change during the document processing.
    Quantity Relation: - Specifies whether the conversion factors for the units of measure in the condition type can be change during document processing.
    Delete: - If we check this field the condition type can be deleted during the sales document processing.
    Value: - If we check this field the condition value can be changed during the document processing.
    Calculation type: - If we check this field the calculation type can be change during the document processing.
    Item condition: - If we check this field for a condition types it becomes item condition, which has to be enter at the item level only.
    Header condition: - If we check this field for a condition type it becomes header condition, which has to be entered at the header level only
    Ex: - RB00 (Discount).
    Note: - After entering the header condition type click on the button activate.
    Note: - The condition amount of the header condition is copied as it is to all the line items in the document
    Group condition: - If we check a header condition as a group condition the condition amount is distributed proportionately among all the line items in the sales document.
    Valid from & valid to: - specifies the beginning and ending of the validity date that the system automatically proposes when we create condition records for the condition types.
    Scale Basis: - Determines how the system interprets a pricing scale in a condition, for Ex: - the scale can be based on quantity weight and volume.
    Check value: - Indicates whether the sale rates must be entered in ascending or descending order.
    Note: - Header condition won’t be having access sequence.
    4. Pricing Procedure: - Pricing procedure contains all the required condition types in the required order.
    Defining Pricing Procedure: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define and assign pricing procedures.
    Maintain pricing procedures
    Go to new entries and define the pricing procedure.
    Select the defined pricing procedure and go to control data
    Go to new entries and place the required condition type in a specified order.
    Step: - Specifies the number that determines the sequence of a condition type with in a procedure.
    Counter: - Specifies the sequence number of a condition type with in a step in the procedure.
    Condition type: - Specify the condition type.
    From & To: - If you specify the reference steps in these fields, the condition values of the two steps specified and the condition values of the steps in between are totaled.
    Manual: - If we check this field the condition type is only included in determination either if they are entered manually or if they are transferred from an external process such as costing.
    Mandatory: - Indicates whether a condition type is mandatory when the system carries out pricing using the pricing procedure.
    Statistical: - This indicator causes a condition type to be set in the document statistically only.
    Print ID: - Controls the issue of condition lines when printing the documents such as order conformations or invoices. [X]
    Sub Total: - Controls whether and in which fields the condition amounts or subtotals are stored.
    Requirement: - For the condition type to be executed in the sales document the requirement specified here must be satisfied. [2]
    Alternative calculation type: - Specifies the alternative formula to the calculation type in the standard system that determines a condition.
    Alternative condition base value: - Specifies the formula for determining the condition basis as an alternative to the standard.
    Account key: - This field along with few other fields enables the system to post the sales values to different General Ledger Accounts.
    Ex: -
    ERL          Sales Revenues
    ERS          Sales Deductions
    ERF          Freight Revenue
    Accruals: - This is exclusively for rebate condition types. [B001 & B002]
    Key, which identifies various types of General Ledger accounts for accruals posting.
    Note: - to maintain the requirements and routines use the transaction code
    [VOFM]
    Pricing Procedure Determination: -
    SPRO
    Sales and Distribution
    Basic Functions
    Pricing
    Pricing control
    Define and Assign Pricing Procedures.
    Define Pricing procedure determination [OVKK]
    We have to assign the pricing procedure to the combination of Sales Organisation, Distribution Channel, Division, Document Pricing Procedure and customer pricing procedure.
    Sales Organisations     Distribution Channels     Divisions     Doc. Pricing Procedure     Cus. Pricing Procedure
    1000     10     00     A     01 & 02
    2000     12     00     A     01 & 02

  • Free Goods and Excise

    Hi Friends,
    I have a scenario as
    My client gives some free goods as free items in order. But these free items are excisable....so how do configure this scenario.
    Where for customer it is free goods, but for company point of view, company has to pay the excise duty to authorities.
    Kindly guide on the same.
    Thanks in advance
    Shailesh

    Dear Shailesh,
    You can do like this,
    1.You can define different pricing procedure for the FREE goods.(T.code V/08)
       ->In the Free goods pricing procedure you maintain Excise related condition types(T.code V/06)
       -->You maintain R100 condition type for 100% discount after the total value.(T.code V/08).
      -->Maintain seperate Account key for R100-Condition type, also assign same account key to the Price condition type (in Free goods pricing procedure only)
    Maintain same account key for the Price condition type and R100 - condition type.(T.code V/08)
    2.You define Different sales document type for FREE goods processing. (T.code VOV8)
    -->You assign document pricing procedure C-Free of charge to this sales document.(T.code VOV8)
    3.You determine the Free goods pricing procedure in OVKK transaction for this combination.
    Sales areaFree goods Document pricing procedure(i.e C)Customer pricing procedure--->free goods pricing procedure.
    4.When you do the Free goods process customer account should not get effet to avoid this ,you ask FI people to create seperate G/L account to post the Free Goods process values.
    In VKOA transaction you assign free goods G/L account for R100 -->Condition type account key with other key fields(same G/L account For sales revenue and 100% discount).
    Maintain the Condition record for R100 condition type with 100% in VK11 transaction
    Now when you create Free goods sales order system will pick the Free Goods pricing procedure in that pricing Excise values and Price will come  but Total value will zero due to 100% discount.
    When you release to accounting
    Excise values will posted to the respective G/L accounts.
    Price and 100% discount will posted to the respective Free goods G/L account.
    Note:- Make sure that you have done the CIN configuration settings regarding Excise duty.
    I hope this will help you,
    Regards,
    Murali.

  • How to block certain Distribution Channel / Billing type combination?

    Hello,
    Is there a possibility to prevent creating biling document if it contains certain combination of Distribution channel in document header and billing type (i.e. F2 / 20)?. Some user exit?
    Thanx.

    Few options are there
    1)  Try with billing user exit USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
    2)  Have a separate billing type for the distribution channel which you dont want to generate billing where you can have a different doc pricing procedure.  Dont assign this document pricing procedure in OVKK
    3)  If you go for separate billing type, you can also avoid maintaining copy control in VTFL
    4)  Apart from all the above options, you can also add this logic in your existing routine such that if the combination of particular distribution channel and F2 comes, it should not be generated / saved.
    thanks
    G. Lakshmipathi

  • Return Order incomplete because of missing address indicator (VBPA-ADRDA)

    Hello,
    Using the VA02 to create a subsequent retun order results in a complete return order created. However, when I use BAPI BAPI_CUSTOMERRETURN_CREATE to create the return order, the incompletion log identifies a missing address indicator   (VBPA-ADRDA) for the ship-to party. Both sold to and ship to party are defined as one time customers. Looking at the entries in table VBPA the problematic customer holds 'D' as the address indicator value while the other customer holds 'E' as the missing address value.
    What could be the reason for the missing address indicator for that specific customer while creation works fine using the subsequent retun order creation?
    Thanks in advance, Ziv.

    1: You took care of the copy controls.
    2: Whats the item category you are using in your return order. Please mark that item category as not relevant for pricing. Uncehck the pricing field in VOV7 for this item category. Also check the incompletion procedure to make sure "pricing" is not an entry.
    3: Please check the pricing procedure you are using for the return order type, uncheck any "Mandatory " pricing conditions.
    4: In the pricing procedure determination OVKK, please check you have the required entry for the return pricing procedure.
    Please test with these changes and see the results,
    Regards
    Sai

  • Line item extract and delete query

    If you change the default view for a scenario and line-item detail has been entered,
    you should first extract the line-item detail and save it. Then delete the line-item
    detail from the scenario before changing the view. You must change the extracted
    line-item detail to match the new default view before loading it.
    The above is a reference from HFM-Admin guide.
    Could any one tell how to extract or delete line item??
    Thanx in Advance

    Dear Sree,
    Here my query is addition and deletion of line items in delivery suggestionable or not if not any alternate solution please............
    -->You can delete the line item in the delivery if PGI not done for that delivery,
    -->But system will not allow you the new item in the delivery,because as per the standard functionality system will copy the items from the sales order and this is advaisable also.
    -->So if you want to add new item add in the sales order then create delivery for that order.
    -->Still you want to add item at delivery ( for your business requirement) you need to do the item categroy determination for the deliveries through 0184 transaction.
    -->Redetermine the pricing at billing level for that item by maintaining proper copy control settings between delivery and billing at item level in VTFL transaction.
    Maintain pricing type field as B-Carry out new pricing
    Make sure that you done the pricing procedure detrmination with the combination of billing document pricing procedure in OVKK transaction.
    I hope this will help you,
    Regards,
    Murali.

  • Stock Transfer Pricing

    Hi Friends;
    I am facing problem during stock transfer process. Cycle is STO with delivry & billing.
    Process as Follows;
    Purchase order Me21n -> Me29n - PO release->  Vl10a Delivry as per purchase order -> Billing vf01.
    Now my problem is in billing  pricing procedure is not being determined even assigning in pricing procedure assignment for particular billing.
    How It could be solved.
    Avinash

    Well Avinash..if i am correct in understanding ur problem...then while VF01 system is not determining the pricing procedure...
    pls check in pricing procedure determination OVKK,  whether for combination of below three, u have pricing procedure assigned
    1. sales area that u r using
    2. Document procedure(assigned to billing type that u r using)...this u will get in OVTP
    3. Customer pricing procedure(assigned to internal customer..which reflect in delivery, billing)...this in customer master.
    i hope this resolves ur issue
    Regards
    jagdish

Maybe you are looking for