Condition type currency conversion during PO

Dear Friends,
In the PO, the vendor is from Japan, so the document currency is in Japan. But the freight condition currency is in MYR which we dont want to convert into JPY. Here the system converts all the condition type currencies into document corrency i.e. JPY in this case. After Goods Receipt, when I see the FI document in MIGO T-Code, all the posting comes in JPY and when i change the postings into local currency i.e. into MYR, there is a difference of RM0.02(2 sens) in the posting. As the freight condition value is in MYR, we dont want system to change it to JPY as freight charge not relevant for PO printout. Because os the conversion factor, a podting having difference of 2 sens is done.
Please advice how to solve the issue.
Thanks & Regards

Hi Indranil,
In m/06 , I have maintained Condition class A    & Condition category as B for that condition type
Also can you also explain what you meant by "As far my knowledge goes either you maintain it in your tax procedure or in your pricing procedure".
Regards,
DGN

Similar Messages

  • Condition Type not considered during Tax calculation in PO

    Dear Experts ,
    I made  a new condition type called Freight before CST , as this was a requirement for one of my PO.
    This new condition is such that its to be considered before calculation of CST , but added after excise duty calculation .
    CST =%{(net price + excise duty) + Freight }
    I added this condition type in my calculation schema , the issue is when I make a PO , the rates & calculation are done correctly in the condition Tab in Item Detail, & also in the Header , but in Tax/Invoice tab ,the CST is not calculated correctly.
    Kindly let me know where I need to do corrections.
    Regards,
    Divakar

    Hi Indranil,
    In m/06 , I have maintained Condition class A    & Condition category as B for that condition type
    Also can you also explain what you meant by "As far my knowledge goes either you maintain it in your tax procedure or in your pricing procedure".
    Regards,
    DGN

  • Currency conversion via Currency Type.

    Hi all:
    I have defined a Conversion Type to do currency conversion during transformation. Why can I use it only when the target is an Infocube and not when the target is a DSO?
    Thanks.
    Regards.

    Hi,
    unit conversion is not supported yet, when the target is DSO.for conversion we can use routine.
    for more details..PFB the link
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60c0ef09-c1a8-2b10-eb87-824b23577923
    thnks.

  • Conditions Types during creation of Quotation

    Dear All ,
              I want to know from where the condition types are fetched during creation of quotation in ME47 . These condition types are not fetched from vendor schema thats for sure . I want to know which pricing procedure is responsible for quotation creation .
              My requirement is I have to create a quotation comparision sheet for my vendor and I want to know from which table I should take the values of condition types to achieve my target .
    Regards
    Abhijit Das

    Hi Sachin ,
    I am trying to create a Quotation in ME47 .The condition types I can find init to maintain are
    P000 : Gross Price
    R000 : Discount On gross
    R001 : Discount Of quantity
    R002 : Absolute Discount
    R003 : Discount % on net
    But my client requires more condition types like Packing & Forwarding ,Excise , CESS , VAT /CST , FREIGHT .
    I want to know how I will enter these condition types in Quotation . After maintaining these entries only I want to compare the quotations through ME49 .
    But system is not allowing me to enter these conditions
    HI Sachin
    I am Kalyan,
    To Maintain these conditions in Quotation, use Transaction ME47, Go to Maintain Quotation Overview Screen
    Now select the Line item for which u like to add the conditions as u mentioned, choose the Item conditons Icons (Shift + F6),
    Now, Select / Choose the Validity period will proceed to another screen, where we can edit the changes.
    Here u can add additional Price like freight, discount etc. here. And SAVE it.
    Thanks and Regards
    Kalyan,

  • Currency in Condition type not updating

    Dear Team,
    The currency in PO condition type is not updated when the defaulted currency in PO header is modified.
    I want the system to automatically update the PO Condition type currency when the header currency is updated.
    Apperciate ur immedaite assistance.
    Zulfikar

    The PO Curreny Can not be changed bcz of the below reasons.
    As a basic rule, the currency cannot be changed if there has already been a goods receipt against a document.
    If the document contains external service and/or limit items, or if an invoicing plan has been assigned to an item, the currency cannot be changed following the receipt of an invoice either.
    If external service items exist, the currency also cannot be changed if services that have actually been performed have already been recorded or if the item in question has been assigned to a preventive maintenance (servicing) plan.
    But for a New PO and no GRN is done , in that case once you change the Currency in the Delivery/invoice tab at PO Header ,
    then the Currency for Conditions also changes..

  • Some Condition types missing during extraction from 2LIS_11_VAKON

    Hi,
    I am extracting conditions data to BI from ECC through 2LIS_11_VAKON. This datasource uses the fields from table KOMV. The Field KSCHL (Condition type) is also being taken from KOMV structure.
    My problem is some condition types are missing during extraction. Say, for example, for a Document condition i have 22 Condition types in KONV table but when i extract the data to BI, nearly 7 conditions are missing, i am getting only 15 condition types for the same document condition in BI.
    Why is this happening? I dont have any filters set. Moreover, this is happening in the Datasource level itself.
    Please advice. Any help on this is highly appreciated.
    Regards,
    Murali

    Hi Murali,
    try to have the manual check with set of data..there must be some mistaken in And and OR logic.
    Thanks,
    Deepak

  • How to rescrict the user to enter a manual condition type once in pricing

    Hi All,
    We are using a condition type ZSP1 in our pricing procedure. I want that the user should be able to enter the condition type only once during pricing.
    eg Suppose the user has entered ZSP1 as 100 in the sales order , then he should not be able to enter ZSP1 again in the pricing. Only one entry should be allowed for the condition type ZSP1
    Please respond if you need any further clarification.
    Regards
    Adity

    Hi,
      you can Restrict the entry of Condition type Twice with Following User Exit
    USEREXI
                             USEREXIT_PRICING_PREPARE_TKOMK
    USEREXIT_PRICIN
    we have Implemented for one our Client

  • PO Condition types exch rate

    Dear All,
    My company code currency is INR. We have defined a PO with condition types(currency EUR) and maintained the exch rate(different from OB08 rate). While doing GR, system is picking Spot rate (OB08) for Material line items and for condition types, system is taking PO exch rate.
    Not able to understand why system is picking different exch rates for material & condition type lines.
    Can some one please clarify this?
    Regards,
    Ganagdhar

    Please review the following notes
    128    Exchange rate differences between GR/invoice
    331910 MR1M, MIRO: Postings in foreign currency/local currency
    191927 Posting logic: GR for foreign currency PO

  • Related to condition types and access sequence

    Dear all,
           i want to know abt one scenario, m using a pricing procedure with my service PO: ZVSTOT, in this Procedure, 12 condition types are there, during searching i found tat 3- 4 condition are are using different different access sequence, so i want to know tat in what procedure, we do it, what is use of it.?
    plz reply me.

    Hi Nisha,
    Prcing procedure configured in your service PO PO: ZVSTOT, Based on this pricing procedure system adopted the condition type in PO.
    Please go through this below link to better understanding the MM-Pricing procedure
    http://it.toolbox.com/wiki/index.php/Pricing_Determination_Process_-_MM
    http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
    CONDITIONS OR PRICING PROCEDURE or PRICE DETERMINATION PROCESS
    We deal with the Pricing Procedure for vendors.
    PB00 Gross Price (info record, contract, scheduled Agreement)
    PBXX Gross Price (PO)
    FRA1 Freight
    RA00 Discount on net
    RA01 Discount on Gross
    ZA00 Surcharge on net
    SKT0 Surcharge / discount
    ZPB0 Rebates
    MWVS Input Tax
    MWAS Output Tax
    BASB Base Amount
    RM0000 Calculation Schema or Pricing Procedure
    (PB00 & PBXX)
    RM0002 Calculation Schema or Pricing Procedure
    (PB00)
    PB00 --> AB00
    Copy the Standard one and create new one (ours)
    RM0000 contains all the condition types
    Pricing Procedure (PP)
    We define the pricing procedure to define condition supplement for the material price. The condition supplement specifies the discount, surcharge, freight etc that we want a system every time to access material price condition records.
    The total value of the material is calculated or based on all addition and subtraction i.e. discounts, surcharge, tax freight etc
    Condition Table
    It is a table, which defines the structure of condition record key.
    Condition Record
    It is a data record used to store conditions or condition supplements, i.e. condition like, discount, freight, and surcharge, Tax etc.
    Condition Type
    It is used for different functions. In Pricing the condition types leads you to differentiate different types of discounts, in output determination, batch determination, difference between two output types, such as delivery note or order confirmation, between different strategy types
    Access Sequence
    It specifies the order in which system searches or access the condition records from condition table
    Difference between PB00 & PBXX
    1. Condition maintained in PB00 is time dependent whereas PBXX is time independent.
    2. Condition type PB00 u2013 used for IR, RFQ, Contract, Schedule Agreement
    Condition type PBXX u2013 used for PO.
    Calculation Schema
    The main function of calculation schema is to provide framework of steps for the price determination process to specify the discounts, surcharge, freight rebate etc.
    It also determines the sequence of conditions that are to be followed and in which sequence.
    Schema Group Vendor
    The main function of it is to identify or to pick the right process and conditions for a particular vendor.
    Schema Group Purchasing Organization
    Key that determines which calculation schema (pricing procedure) is to be used in purchasing documents assigned to the relevant purchasing organization.
    Schema Group
    It allows to group together the purchasing organizations, which uses the same calculation schema.
    Steps: -
    1. Create Access sequence
    2. Create condition types
    3. Create pricing procedure or calculation schema
    4. Link pricing procedure & access sequence to condition type
    5. Create schema group for vendor
    6. Create schema group for purchase organization
    7. Assign schema group vendor-to-vendor master record in purchasing data view
    8. Assign schema group purchase organization to our purchase organization
    9. In inforecord purchase organization data enter condition types and pricing or calculation procedure
    CUSTOMIZE SETTINGS: -
    SPRO > IMG>MM>PUR>Conditions -->Define price determination Process
    1. Define access sequence
    2. Define Condition type
    3. Define cal. Schema
    4. Define schema group
    o Schema group vendor
    o Schema group purchasing group
    5. Assignment of schema group to PUR org
    6. Define schema determination à determine cal schema for standard PO.
    With Thanks,
    Thiru

  • Currency conversion issue for condition type

    Hello,
    I am creating two invoice document.
    1. Customs Invoice (ZCDS)
    2. Inter company invoice.(IVA)
    both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
      ZCDS
    IVA
    Regards,
    Jagjeet

    Hi Jagjeet,
    For IVA invoice type -(For condition type- YUMU)
    Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
    For ZCDS Invoice Type -(For condition type- YUMU)
    Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
    Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
    To solve your problem write code in User exit - userexit_pricing_copy to change  konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
    Regards,
    Vikas Mulay.

  • Currency Conversion for Exchange rate type "AS02"

    Hi Experts,
    I am gonna post the most challenging problem (regarding currency conversion) I ever faced in my 1 year of BW Carrier.Kindly provide a solution.
    There are three types of currency to be used in the query for Key Figure 0NET_VALUE (so total 3 Key Figures to be created)
       1.Document currency (may be any currency)
       2.Local Currency (must be EURO)
       3.Global Currency (must be USD)
    From Document currency to Local Currency(EURO) we are using Exchange rate Type "M" (in Conversion Type created in Trans RRC1) [There is no problem in this conversion]
    Problem starts now--->
    From Local Currency(EURO) to Global Currency(USD) we have to use Exchange rate type "AS02" (in conversion type to be created in RRC1)
    but there is a Business requirement  that currency rate should be as per the last day of the entered period;and this logic should work for the range of periods also.
    Example :
    we are executing query for the period 006/2006 (posting Period)
    Last day of this period is 06/30/2006,
    Currency rate would be as per 06/30/2006
    And this currency rate should be same throughout the period 006/2006 in query
    The example was for single period,but logic must be incorporated for the range of the periods.

    Hi..
    There is no corresponding source key figure in the InfoSource for the target key figureof the InfoCube.
    a. A source key figure of the same type can be assigned to the target key figure
    (for example, sales revenue instead of sales quantity revenue).
    If the currencies of both of the key figures are the same, no currency
    translation can take place.
    If the currencies are different, a translation can take place either using a
    currency translation type or by simply assigning a currency.
    The following table provides an overview of possible combinations with different
    currencies in the source and target key figures:
    if Source key figure currency  is fixed , Target key figure currency is variable  then Currency translation (CT)  No CT
    if Source key figure currency  is fixed , Target key figure currency is fixed  then Currency translation (CT)   CT
    if Source key figure currency  is variable , Target key figure currency is fixed then Currency translation (CT)   CT
    if Source key figure currency  is variable  , Target key figure currency is variable  then Currency translation (CT)  CT or assignment
    b. If there is no corresponding source key figure of the same type, then you have
    to fill the key figure for the data target from a routine.
    If the target key figure has a fixed currency, no currency translation is
    carried out. This means that if translation is required, you have to execute
    it in the routine.
    If the target key figure has a variable currency, you also have to assign
    a variable source currency to the routine. Using the F4 help you can
    select a currency from the variable currencies in the communication
    structure. You have two options:
    – You can select a variable currency and assign it.
    – You select a currency translation type and a currency into which you
    wish to translate (‘To’ currency).
    The ‘To’ currency is, by default, the target currency if it is included in the
    communication structure.
    Creating a Routine for Currency Translation:
    If you want to translate currencies in the update even though the currency translation is not
    available for one of the above reasons, you can create a routine. Choose Routine, set the
    Unit Calculation in the Routine and choose Create Routine. In the routine editor you get
    the additional return parameter UNIT, the value of which is used to determine the target
    1.  save the query  and it under role
       see to it is in   :  Restricted and calculated key figures --->   properties of k.f
    2. exeute the query
    3. the currency translation --> by target currency  usd  choose  OK
    conversion type :  MEANTODAY Fixed target currency current date (MT)
    4.  Go back to the query definition by chossing chage query ( global definiton)
    5.  in the context menu for % share sales vouume of incoming orders,  choose properties --> formula collision -->  result form this formula choose OK
    Note that -
      your should alos set the currency translation in the  properties for the  two key figures sales voule EUR , choose properties ---> currency  conversion key :  fixed target currency ,  currrent date ( MT) -->  target currency  : American Dollar .  choose   OK
    <b>The translation key is a combination of different parameters that establish how the exchange rate for the translation is executed.
    The parameters that determine the exchange rate are the source and the target currency, the exchange rate type and the time reference for the translation.</b>
    The source currency is determined from the data record or dynamically from the master data of the specified InfoObject (currency attribute)
    The target currency can either be fixed in the translation key or selected at the time of translation.
    You can also use an InfoObject (currency attribute) to determine the target currency.
    The exchange rate type distinguishes exchange rates that are valid in the same time frame next to each other, for example, the bid rate, ask rate or middle rate. The exchange rate types are stored and can be maintained in a central table (TCURV).
    The time reference for the currency translation can be either fixed or variable
    The fixed time reference can either be a fixed key date that is stored in the translation type, or be determined using the system date when executing the currency translation.
    If the time reference is variable, then the point in time for the exchange rate determination comes from the value of a time characteristic (InfoObject). The reference can, for example, be the end or the start of a fiscal year or a calendar year, a period and a month – or even to the exact day. It can also be determined using a customer-specific InfoObject (for example, trading day).
    Currency translation in the BEx
    When selecting a translation key with a fixed target currency     this currency will be added automatically to the query definition
    Also, you can use translation keys selecting their target currency at the time of translation. These can be applied in two different ways:
    Selection of a specific target currency in the query definition (1)
    Entry by variable (2)
    Dynamic translation keys require input from the InfoCube !
    InfoObject value will be read during query execution
    Examples:
    dynamic time reference (p.eg. 0CALDAY)
          time characteristic
    target currency determined by InfoObject (currency attribute)
         characteristic which contains currency in its attribute table
    the corresponding InfoObject has to be part of the InfoCube
    1.Define the currency attribute in the InfoObject maintenance
    The currency attribute has to be a unit InfoObject of type currency
    The unit InfoObject must be an attribute of the characteristic
    The currency attribute should be filled in the master data table of the corresponding InfoObject (manual maintenance or upload via InfoSource)
    2.Enter the InfoObject in the translation key maintenance
    Only InfoObjects with a currency attribute can be used in translation keys (p.eg. 0COMP_CODE)
    At the time of currency translation the value for the source currency / target currency is then derived for every record from the master data table of the specified InfoObject
    All values for a query are translated ad hoc (after having executed the query) using a translation key
    Depending on the translation key a fixed target currency will be used for translation or you will be able to select the target currency
    The ad hoc currency translation offers only restricted functionality (selection of translation key and target currency) compared to the currency translation in the query definition
    Do not forget to create your translation keys before starting your work in the Business Explorer Analyzer
    Example:
    You load the following record to your InfoCube:
    Company Code:                1000
    Amount in Source Currency:      500,-
    Source Currency:                FRF
    Target Currency:               ?
    In the Update rules, you are now using a translation key which derives the target currency from the InfoObject 0COMP_CODE. During the Update Process the target currency will then be read for Company Code 1000 from the master date table of 0COMP_CODE.
    With the currency translation in the Business Explorer, the source currency can currently only be determined from the data record.
    Only translation keys with a fixed exchange rate type can be used in the BEx
    Translation keys with a dynamic time reference (from an InfoObject) can only be used in the query definition. It is not possible to fill the InfoObject by a variable !
    Translation keys getting their target currency from a currency attribute can only be selected in the query definition
    When getting the dynamic reference from an InfoObject (p.eg. 0CALDAY) the currency translation will apply to each record read from the database. That means it will use the date in this record for the currency translation.
    When using a variable you will restrict the output of your query to a certain amount of data. For example, you would translate all invoices of March 11 with the translation date March 11
    This means, the requirement “show me all invoices in my cube in group currency, conversion date: 14.07.2001” could not be solved by a variable input for 0CALDAY
    I hope this would help...
    with regards,
    hari

  • GL : after journal import currency conversion type change to User

    Hi
    I have following data in GL_Interface table
    User_currency_conversion-type = 'Corporate'
    Currency_conversion_date = '9/21/2008' ( Get from Gl_Daily_rates)
    Currency_conversion_rate = Null
    As per GL_Daily_Rates the conversion_rate is 1.5 for this currency to functonal currency.
    After journal import, gl_je_header is populated with
    User_currency_conversion-type = 'User'
    Currency_conversion_date = '9/21/2008'
    Currency_conversion_rate = 1
    Can you please explain, why the User_currency_conversion-type and Currency_conversion_rate are changed to above values ?
    If you have any good document of "Journal Import Rules and Logic" , please share
    Thaks in Advance

    Hello Mr. G. Lakshmipathi,
    Thanks! I'll try this function module READ_EXCHANGE_RATE.
    However, I think this issue is not really related to the exchange rate. The amount conversion from USD to JOD happens correctly based on the current pricing forumla that we are using i.e. amounts in JOD have 3 decimals after conversion from USD, but when they are stored in pricing structure, the last decimal is truncated as the currency against the 3 condition types is USD (USD has 2 decimals). Hence, the amounts have 2 deicmals.
    Thanks,
    Amit

  • Currency by default into the conditions types

    Hi Experts,
    I have the following scenario. The Company where I work carries out purchase orders that requires to maintain two kind of currency for two conditions types. So, I wonder if it's possible to customize the currency by default into the conditions types, so this way the company will be able to create a purchase order by treating different kinds of currencies although the header document shows just one of those.
    I'll appreciate any idea about explained above.
    Best Regards.
    José

    HiI,
    NARMALLY SYSTEM WIL Lallow to create PO with the document currency of the vendor or the local currency of the plant /materials and with other currency by a curency conversion.
    If your intenstion to see that differant conditions in the PO need to have differant currencies , you need to give the conversion in the PO items condition if the header currency  is differant from the conditions currency.
    You can create the condition record at MEK1 to get defaulted into PO with the currency you want .with proper condition tables.
    Regards,

  • Currency Translation Type in queries using currency conversion

    I have a question on the Currency Translation Type (EUR_VAR) that is used in all of the queries using currency conversion on the fly. (currency is maintained automatically nor in table.)
    User wants to use 2 different exchange rates in a single query. The months in 2010 (Actuals) are to
    be converted using Xchangerate-type EURO and the months in 2011 (Planned) to use Xchangerate-type USD.
    But store different rates with different starting dates. This is however not possible because the Currency Translation
    Type is set-up (1) to work with Query Key date - rather than a characteristic in the data and (2) apparently these
    currency translation types only work with time characteristics like 0fiscyear
    My idea is therefor to:
    1. Create a new variable (similar to EXC_RATE) to prompt for a 2nd Exchange Rate type when query starts
    2. Create a new Currency Translation Type (next to EUR_VAR), referencing the new variable or sticking to fixed Xrate type, fixed to EUR
    Is this possible to create Idea (2)
    Many Thanks in Advance.

    The best way would be to create two curr conversion types , one converting to EUR and other to USD .Put them in properties of coressponding KFs in query.For timref in RSCUR , variable time ref can be used individually for two conv types.

  • Error during currency conversion and consistency check in a sales order

    Hi Experts,
    I am facing the below error in the sales order. The sales order is having so many items. The below error is coming for few items only. I have checked the currency exchange rates also. All are maintained properly.
    Please advice me how to fix this error or which class,methods are responsible for checking the above details while saving the order.
    Thanks,
    Sri

    Hi Christophe,
    FYI
    Error during currency conversion frm &1 to &2 (date &3, ref. curr. &4)
    Message Class - CRM_CUMULATED_I
    Message No     - 013
    Error during currency conversion for &1 and &2
    Message Class - CRM_CUMULATED_I
    Message No     - 008
    Consistency check: Logical key does not match
    Message Class - CRM_CUMULATED_I
    Message No     - 011
    Thanks,
    Sri

Maybe you are looking for

  • Single Sign on in a 3 tier architecture between SAP Netweaver CE and R/3

    Hi All, I am trying to implement SSO using SAP logon tickets in a 3 tier architecture between NW CE and R/3. But so far I have not been able to crack this. Let me describe the scenario in detail: We have two Java EE applications on Netweaver CE7.2 Ap

  • SQL Query for Date field updation

    I want a query from u.. Hope u help me with a solution soon.. My Q: I want to update a date field in Oracle database. But the condition is that i shouldnt change the hours, minutes & seconds of the date field. generally , if we update the date field

  • Help in IDOC_INPUT_ORDERS Function module

    Hi, I am writing a program to generate an IDOC using IDOC_INPUT_ORDERS Function module . But I am a little confused as to what has to be passed as input_method,mass_processing which are the import parameters of this function-module . If anyone has a

  • Weblogic 12.1.2 with Hibernate 4.3.6 (JPA 2.1) as Persistence Provider

    Hello, Could I apply the javax.persistence_2.1.jar to PRE_CLASSPATH variable to get JPA2.1 in Weblogic 12.1.2 (not 12.1.3), using Hibernate 4.3.6 as my Persistence Provider? Best Regards, Luís

  • IPod Touch locked out

    My daughter locked her iPod Touch, I believe it's 3rd Gen. I have no idea which operating system it has (it was a gift from a friend). Anyway, she forgot the password and it's now locked out. She's tried to connect it to iTunes, but it's not being re