PI01-Condition Type

Hi Friends,
STO between two plants of different company codes.
US-Receving Company Code
India-Supplying Company Code
The scenario is like this:
Sales order is created in US.
Based on the Sales order, US will generate Purchase Order(STO) to India.
Plant(India) will transfer(VL10B/VL02N)the goods to Plant(US).
Plant(India) will raise the Intercompany invoice to Plant(US).
*Condition type IV01 is the Revenue and Cond.type VPRS is the Cost to INDIA*
****Pricing PRocedure is ICAA01***
MIGO and MIRO in US Company.
As the goods were received in US plant they will deliver the goods to the Customer in US w.r.t. Sales Order.
Then Billing to Customer in US by US Company.
**Cond. type PI01 is the Cost to the Receving Company Code(Revenue to the Supplying Company Code which is having cond.type IV01 copy of Cond.type PI01)
****Pricing Procedure is RVAAUS**
1)I want to know that if cond.type PI01 is the cost to receving co.code(US) then cond.type VPRS is?
2)In Pricing Procedure RVAAUS do we need to have Cond.type PI01 and VPRS?
with regards
Azeez.Mohd

Hi,
PI01 condition type represents costs to Ordering company code (in other words revenue to supplying company code).
It is statistical condition type & meant for information purpose only.
Condition records for PI01 are created with the following key combination:
Ordering sales Org + Supplying Plant + Material
PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
Hope this provides you with your answer,
Regds,
Rupali

Similar Messages

  • Reference condition type wrt IV01 and PI01..

    Hi PPL,
    Can u plz explain Referrence Pricing condition wrt to the condition types :
    IV01  and PI01,
    Both are condition tyres pertaining Inter company ,IV01 has a Reference condition Type PI01 assigned to it.
    What does it mean in the inter company scenario.Points for sure..:-)
    Best Regards,
    Subbz..

    Hi,
    PI01 condition type represents costs to Ordering company code (in other words revenue to supplying company code).
    It is statistical condition type & meant for information purpose only.
    Condition records for PI01 are created with the following key combination:
    Ordering sales Org + Supplying Plant + Material
    PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
    The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
    The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
    Hope this provides you with your answer,
    Regds,
    Rupali

  • Intercompany billing - using condition type PI01 = VPRS

    In the intercompany billing we are going to configure the condition type PI01 to copy the amount in the condition type VPRS in the order. Can anyone give me a proposal of how to do this?

    Hi,
    Check copy controls from Delivery to blling document - VTFL is there any thing missing Header as well as item level, at what lelvel your determining the price.  pricing at main item level or batch level.
    Pricing should be at main item level
    There will be two items 1 is main item 2. is Batch item
    chek cumulate cost has checked on main item or not
    and also gothrough the related Notes:
    Regards,
    MH

  • In Stock trasfer order how to pick pricing condition types

    Dear Experts,
    I am new to SAP MM my question is In Stock transfer order (plant to plant through purchasing) it is picking PI01 pricing condition types? how it is picking? what are the Accounting doc are updating?

    Hi,
    Goto the following node SPRO > IMG > Materials management > Purchasing > Conditions > Define Price determination process > Define shcema determiantion
    Define schema for transport orders under which you will be able to see RM2000, when you try to open the RM2000 through M/08 transaction code.
    You will be able to see the PI01 as the basic price condition type.
    Accounting entries
    During Goods Issue.
    The stock account in the supplying plant gets Credited with the MAP value.
    The stock account in the receivving plant gets debited with the MAP value.
    If there exists any diffeence then the key AUF will get hitted.
    During Goods Receipt.
    No accounting doucment gets generated.
    Regards,
    DilliB

  • Condition Types in Price Determination Process

    Hi
    Can any one explain me about in Detail about the VARIOUS TABS that  work in the CONDITION TYPE  of PRICE DETERMINATION PROCESS
    Thanks & Regards,
    Senmani.

    hi
    hi
    control data 1 :
    Condition Class is a grouping that lets you control each condition type differently.
    For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
    Condition category (examples: tax, freight, price, cost)
    A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
    Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
    Calculation type
    Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
    The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
    Rounding rule
    The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
    Example
    In the standard rounding rule '_', values are rounded off according to business standards:
    10.454 -> 10.45 DEM
    10.455 -> 10.46 DEM
    In rounding rule 'A', values are always rounded up:
    10.459 -> 10.46 DEM
    10.451 -> 10.46 DEM
    In rounding rule 'B', values are always rounded down:
    1045.9 -> 1045 LIT
    1045.1 -> 1045 LIT
    In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
    Structure condition
    controls whether the condition type should be a duplicated condition or a cumulated condition.
    This control is only helpful when you use bill of materials or configurable materials.
    Aduplicated condition is duplicated into all assigned items.
    A cumulated condition contains the net value of all assigned items.
    control data 2 :
    promotions
    Specifies that the condition type in question is only valid for Promotions.
    Use
    Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
    Accrual (e.g. Freight)
    Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
    Use
    If you mark this indicator, the condition appears in the document as a statistical condition.
    Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
    Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
    Solution: For this reason more indicators are being set up in 4.0 for the condition type:
    'Variant condition' (KVARC)
    'Internal costing condition' (KFKIV)
    The characteristic values O and I for the condition category must no longer be used.
    For more information, see the note 93426.
    inv.list condi
    Condition for invoice list
    Marks the condition type as relevant for internal costing.
    Quantity conversion
    This field controls the quantity conversion during determination of the condition basis.
    The field is only relevant for calculation rule 'C' (quantity- dependent.
    It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
    Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
    Rounding errors can occur during quantity conversion.
    Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
    Condition for inter-company billing
    Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
    Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
    Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
    Scale :
    Scale basis indicator
    Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
    Checking rule for scale rates
    Indicates whether the scale rates must be entered in ascending or descending order.
    Scale Type
    Indicator that controls the validity of the scale value or percentage:
    From a certain quantity or value (base scale)
    Up to a certain quantity or value (to-scale)
    Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
    Formula for scale base value
    Formula for determining the scale base value.
    Use
    You can use this formula to specify calculation methods that are not provided in the standard system.
    reward points if helpful
    thanks and regards
    ravikant dewangan

  • Intercompany condition type

    Dear Sap Experts,
    For inter company pricing condition type PI01 which has been maintained 22 requirement in pricing procedure and it  defined in VOFM. But  how we can understand each  logic of  23  as well  as other  copying requirements adn requirements.
    Regards
    Ishikesh

    hi
    For understanding the logic u need to have ABAP prog knowledge then u can understand
    goto VOFM and from the menu select REQUIREMENTS and PRICING
    now u can see all the routines here select any routine and click on note pad icon or press F5
    regards

  • How to prevent consecutive entries of same condition type in a sales order

    Hi,
    My client is using manual condition type for the basic price "ZBPR". Now system allowing multiple entry against this condition type in the pricing screen during order creation i.e in the first line if we put Condition Type "ZBPR" and putting some value as amount, then again if I put "ZBPR" as condition type and give some other value as amount then system is allowing this and doing all the subsequent calculation.This is not acceptable by the client.
       The functional person regarding this is saying this can be done by using routine.Can some body tell me which routine should I take for this if that is possible by routine and the required code.Also say if there is other way to solve this.
    Thanks,
    Manas.

    Hi ,
    u can do it thru VOFM(tcode)--->Menu -> Formulas>condition value , but in this case u need to derive the value of this condition type by using ur own logic.
    Re: vofm-routine
    Regards
    prabhu

  • How to restrict duplicate condition type in sales order

    Hi All
    Is there any standard method to restrict user for adding a particular discount condition type more than once in sales order. condition type is manual and its records are also being maitained manually.
    Else would I will have to create userexit at sales order level or a routine in pricing procedure. I doubt on creating a rotuine in pricingprocedure because in pricing procedure there is already a restirction to add similar condition type more than once.
    Thanks

    create a routine and add this routine to the discount condition type only.

  • Creation of New Condition Type

    Hello SAP Folks,
    I have one issue related to pricing. See the case is i have to produce an extra cost in the Sales Order which is actually depended
    upon the net price. This condition type is percentage based and calculation works in the following way:
    Let the new condition type be Z123 and Net price be PR00.
    So for year variation 1-2 year, the condition type Z123 will be 1.5 times of PR00
                                      2-3 year, the condition type Z123 will be 2.0 times of PR00
                                      3-5 year, the condition type Z123 will be 3.0 times of PR00
    Can anyone throw light on how to configure this condition type ???
    Regards,
    Sarthak

    Hi,
    For Z123 Condition type make (V/06)
    Cond. class A Discount or surcharge
    Calculat.type A Percentage
    Plus/minus A Positive
    and all other settings are same as Discount condition Type
    For making Z123 customize an Discont Condition Type (EX:K004,)
    Then while creating the condition record give the percentage as 150% 1-2 yearin valid from and to date,
    give the percentage as 200% 2-3 yearin valid from and to date, give the percentage as 300% 3-4 yearin valid from and to date, and save the record. (VK11)
    In the pricing procedure For step z123 condition type from which you want the % that is step of PR00 should be mentioned in the FROM and TO column.(V/08)
    This will result as per your requirement

  • In import Pricing Proceedure,  Some Condition types added to Material Cost

    HI,
    In Import Pricing procedure, Some condition types (Like Basic Customs Duty,Edu Cess & Hier Edu Cess) are added to material cost. The remaining are not added. What is the configuration to add condition types to Material cost?
    Note -  we have added FR3 account key for all condition types. Then why few condition types are added to material cost and why others are not added to material cost?
    Can any one please help me on this..
    Thanks
    KB

    Assign key "NVV" to those condition types which are to be loaded to material cost.
    Hope this resolves ur problem

  • Condition type freight is not getting displayed in print preview

    Hi,
    I created PO, and while seeing its print preview:
    Condition type freight is not getting displayed.
    Where i missed?
    Uts

    hi,
    Inddition to M/08...(As given above)...
    Also do check the smart form or SAP script...used for the output...check it with the ABAPer...whether the field is liable for o/p or not??
    Smart form is attached at message type of message determination..
    Regards
    Priyanka.P

  • Pricing: New condition type not getting listed in options in product master

    Hi,
    I have created a new pricing procedure and also created a new condition type for it. I am trying to create a condition record in the product master for this  condition type but the condition is not there in the list of conditions. How can I inlcude it in the condition list?
    Even the new condition type I have created by copying 0PR0 is not getting listed in the options, whereas 0PR0 is getting listed.
    Regards,
    Meenakshi
    Edited by: Meenakshi Sawhney on Sep 9, 2010 8:27 AM
    Edited by: Meenakshi Sawhney on Sep 9, 2010 8:29 AM

    Hi Meenakshi,
    you need to enhance the condition maintenance group in the customizing, which is assigned to the product master. Please check: IMG: Customer Relationship Management -> Master Data -> Products -> Special Settings for Sales Operations -> Assign Condition Group to Application CRM and IMG: Customer Relationship Management -> Master Data -> Conditions and Condition Technique -> Condition Technique: Basics -> Create Maintenance Group.
    Best Regards,
    Michael

  • Statistical condition types not getting displayed in invoice

    We  have configured the tax collected at source (TCS) condition types and make them as statistical in the pricing procedure. Now, the issue is when we are using them the values for these condition types are getting calculated correctly as the total value is correct but in the invoice their individual values are not getting displayed.
    In the analysis also we can see that the condition records are found but being statistical condition they should get displayed in the invoice as only the correct total value will not serve the purpose, please help
    Thanks & regards
    Puneet Agrawal

    Hi
    Keep a break-point (hard) in these program lines and debug and see that whether the condition type(KSCHL) related to Taxes is appearing here or not.
    If the condition type for taxes is coming then you can print the taxes.
    First check the related condition type for Taxes in T685 table and see here in the code.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Condition types not getting displayed

    i have uploaded a smartform & copied the standard program(/SMB40/FM06P) of it into my system.the condition type texts & their amounts are getting displayed  for import purchase order(conditions are getting picked from me22n--->conditions) but for domestic invoice  im unable to display condition type texts & their amounts.(these are picked from me22n-->invoice---->taxes).
    in program lines this code exists.
    <FS>   like EKPO.
    <KO>  like  KOMV.
    input parameters            output parameters
    ZXEKKO                        G_KSCHL
    L_NETWR                      G_VTEXT
    <KO>                             G_KWERT
    G_VTEXT                        G_FRAKWERT
    G_FRAKWERT               G_TAX
    G_TOTAL
    <FS>
    G_TAX
    L_KWERT
    CLEAR: g_vtext,g_kwert,l_kwert.
    CHECK NOT <ko>-kwert = <fs>-netwr.
    Get Condition Type Text from table T685T and the value
    SELECT SINGLE vtext INTO g_vtext FROM t685t
    WHERE spras = sy-langu
    AND kschl = <ko>-kschl.
    IF sy-subrc = 0.
    MOVE <ko>-kwert TO g_kwert.
    ENDIF.
    Check document currency
    IF NOT l_netwr IS INITIAL.
    WRITE g_kwert TO l_kwert CURRENCY zxekko-waers.
    ENDIF.
    *Determine if the discount is based on %
    IF g_vtext CS '%' OR
    g_vtext CS 'percentage' OR
    <ko>-kschl = 'SKTO'.
    <ko>-kbetr = <ko>-kbetr / 10.
    MOVE '%' TO <ko>-waers.
    ENDIF.
    Determine Tax
    IF g_vtext CS 'tax'.
    ADD <ko>-kwert TO g_tax.
    CLEAR g_kwert.
    ENDIF.
    Determine Freight Charges
    IF g_vtext CS 'Freight'.
    ADD: <ko>-kwert TO g_frakwert.
    CLEAR g_kwert.
    ENDIF.
    i feel the data is coming from above code only.please suggest where i have to make changes so that it picks data from ME22N->INVOICE--->TAXES which has conditions for domestic purchase order.please help.

    Hi
    Keep a break-point (hard) in these program lines and debug and see that whether the condition type(KSCHL) related to Taxes is appearing here or not.
    If the condition type for taxes is coming then you can print the taxes.
    First check the related condition type for Taxes in T685 table and see here in the code.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Pricing condition types in SRM 7.0

    Hi,
    We are using SRM 7.0, we have decided to go ahead with the pricing proceedure and the condition types which are there in ECC the same should be replicated to SRM.
    We have created the same pricing proceedure and the calculation scheema in SRM.
    Now my requirement is when i create a PO with the conditions and when i am transfering to ECC the PO should also be with the condition types. It should be a similar PO in ECC.
    Is this can be addressed.

    Hello All,
    As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.
    On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.
    If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction
    ME32K in ECC) and nothing can be transfer from other source.
    Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.
    Thanks,
    Yatin

Maybe you are looking for