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.

Similar Messages

  • Currency Conversion issue for YTD model

    Hello,
    Currently our Client is using YTD (year to date) model to maintain data into BPC 7.5NW, and planning to use BPC for currency conversion from LC to USD. They are not converting the values in Transactional system. When performing this all Balance sheet accounts will be using YTD model for conversion, but income statement accounts should be using Periodic values for conversion.
    We have two different Entity FX types: one is USDFNC - USD functional and NUSDFNC - Non USD functional. One of the differences between these two FX types is CTA account, USDFNC is using expense Account to Book CTA and NUSDFNC is using Equity Account to book CTA.
    To achieve the above mentioned requirement, I did configure BPC as follows:
    1) Use RATE type AVG (average for Income statement accounts)
    2) Use RATE type END (spot rate for Balance sheet Accounts)
    3) In business rules for Account rate type AVG- formula would be [AVG], apply to periodic flag will be checked.
    5) in business rules for Account Rate Type END - Formula would be [END], apply to periodic flag will be blank.
    6) To calculate CTA for ENTITY FX type- NUSDFNC, I configured the following in Account Rate type AVG - destination account is equity account, Formula is [END]-[AVG], apply to periodic flag will be blank and Entity FX type is NUSDFNC.
    7) To calculate CTA for ENTITY FX type- USDFNC, I configured the following in Account Rate type AVG - destination account is expense account, Formula is [END]-[AVG], apply to periodic flag will be blank and Entity FX type is USDFNC.
    Above configuration is giving me correct converted result for all Balance sheet accounts and income statement accounts are showing the correct values when I use the formula (current period LC amount-previous period LC amount)*(current period AVG rate). But I saw difference in Balance sheet, so further analyzed CTA (currency Translation Accounts) and found that the difference is because of CTA amount only. Similar CTA differences exist for both USDFNC entities and NUSDFNC entities. So, I think my logic to calculate CTA is not working.
    I am using the standard script logic to run Currency Conversion:
    *RUN_PROGRAM CURR_CONVERSION
         CATEGORY  = %CATEGORY_SET% 
         TID_RA = %TIME_SET%
         CURRENCY = %RPTCURRENCY_SET%
         RATEENTITY = GLOBAL
    *ENDRUN_PROGRAM
    *COMMIT
    Can any one help me to understand whether this configuration is correct? I feel that I may need to change the logic for calculating CTA. But not sure about what and where
    Edited by: amarnathputta on Nov 24, 2011 5:36 AM

    Thank you Ethan,
    Let me try to explain this with few dollar amounts:
    Let us consider that I have data for 1st month (Jan) of the year 2011,
    Net income for Jan. 2011 in LC = 59916152.19
    Net income for Jan. 2011 in USD calculated using Average rate is  = $ 9,223,013.14
    CTA for the same month is  (net income in LC X spot rate) - net income in USD at average rate =((59916152.19)*(0.154617))-9223013.14 = 41,042.564
    This value is correct.
    For the month of Feb 2011:
    Net income for Feb.2011in LC = 60415519.01
    Net income for Feb.2011 in USD at average rate (with periodic flag on) = 9,300,112.38 ( I calculated this value manually and it is correct after conversion)
    calculated CTA for the same month is (60415519.01*0.154083)-9300112.38 = 8,892.035.
    But actually BPC calculated CTA is 18,547.56 (I felt that this may be because I am not using the Flag apply periodic value while calculating CTA and when I flagged that, BPC is giving me a very big difference in CTA)
    My balance sheet is exactly off with the difference in CTA.
    Hope this helps you to understand my problem.
    Edited by: amarnathputta on Nov 25, 2011 2:43 PM

  • Currency conversion issue in SPM. We are getting incorrect results with SPM conversion function from one of the document currency to USD.

    Currently we are using SPM 2.0 version and we have been facing currency conversion issues.
    Please help me in following aspects.
    1) Where actually currency conversion happens in SPM. Is it the global program which does the conversion or other way.
    2) We have conversion issue for one of the currency where conversion function is giving incorrect results when converting from one of the document currency to USD. here The respective document currency is considering the 1:1 ratio with Dollar which is actually incorrect.
    3) We have verified in both BI side(currency tables) and even ECC side.
    Please help me in understanding this issue and let me know if you need more information on this.
    Its an production issue and appreciated your immediate inputs.
    Thanks
    Kiran

    Hi Arun,
    The following information may be helpful to you.The SSA_HELPER_PROGRAM has options regarding currency settings.
    EXCH_RATE_TYPE: This flag governs the exchange rate type which will be used for currency conversion in data management. For example if RSXAADMIN contains an entry EXCH_RATE_TYPE = „ZSPM‟ then the conversion type used for currency conversion is ZSPM. The default value for the exchange rate type is „M‟. More details can be found in the note 1278988.
    CURRENCYCONVERSION: By default data management converts all the measures in transaction currency to reporting currency and copies over to the corresponding measure in reporting currency. If the measure in reporting currency is already available in source it might be desirable to disable the currency conversion. To disable the conversion you can make an entry CURRENCYCONVERSION = „ „ in the table RSXAADMIN. This can also be achieved by running the program SSA_HELPER_PROGRAM with the option DEACTIVATE_CURRENCYCONVERSION. The conversion can be reactivated by running the same program with option ACTIVATE_CURRENCYCONVERSION.
    UNITCONVERSION: Similar to above. To deactivate unit conversion you can use the program with option and DEACTIVATE_UNITCONVERSION and to reactivate ACTIVATE_UNITCONVERSION. By default both the conversions are switched on
    EXTERNAL_CURRENCIES: Normally most of the international currencies are stored with two decimal places however certain currencies do have 0 and 1 decimal place too. For example JPY has 0 decimal places. SAP internal format stores even these currencies with 2 decimal places and at the time of display it changes the value to right decimal places. In case a file from external source is loaded to SPM it might have the format with 0 decimal places in the file. To convert it to SAP standard format post processing needs to be done on this value. If that is the case you can set the flat EXTERNAL_CURRENCIES = „X‟ in the table which will enable the post processing for these values. This flag can also be set and reset using the helper program using the option TURNON_EXT_CURRENCY_FORMAT and TURNOFF_EXT_CURRENCY_FORMAT.
    Kind Regards,
    John Harris
    Senior Support Engineer, SAP Active Global Support

  • Account determination for condition type

    Hi Guru,
    I have  requirement where I  need to assign G/l account in VKOA for condition type used for discount and markup same time. I know I can aasign trade discount to this condition type but how about markup. can we assign two diffeent account to same condition type based on uses.
    Thanks

    This is pricing conditions not condition type like KOFI. The pricing condition are like base price, discount , markup, special custmer discount, ect. You can see these contions in sales order under condtion tab. My issue is there one condtion that user use some time for discount and some for mark up and requirement is when this condition is used for discount, it post to one account and if used for mark ,should go to different accoount. In VKOA  sequence 501, we can only assign one account to one condition. if some one know how to assign two G/Ls to one condition .

  • Help - Business Partner "Error in conversion Customizing for address types"

    Hi Experts,
    I am encountering an error with maintaining the Payer/ee in the Payment Details (SI) tab under Counterparty company code.
    The error message I get is below --
    *Error in conversion Customizing for address types (-> note 594871, III)
         Message no. FTBU800*
    I need your kind help please to troubleshoot this issue.. I receive the same error when i book deals and try to view the "Payment Details" tab during TX01 or TM01. I am not sure anymore what could be causing this problem.
    Thanks,
    David

    Hello Raj,
    Impliment the correction as specified in the sap Note 594873.. sect III.
    You can take the help of your basis team for downloading it Using Tcode "SNOTE" and if you have sufficient authorizations you can do it your self..
    another option is to down load the Note from the service market place and get the correction implimented manually by a technical consultant.
    Wish you success.
    M. Naveen Kumar

  • Currency Conversion issue in BW reporting

    Hello Experts - I have a Revenue KF in COPA cube. For one specific record the currency type is TWD. When I run the report using the Key Figure (along with other Chars), the value is multiplied by 100. I do not have any scaling factor set at the report level or currency conversion set for the Key Figures. It works fine for other records with other currency types. Does it has any thing to do with the TCURF / TCURV tables? Appreciate your help.
    Rgds,
    Venu.

    Hi Venu,
    For different currency types there are scaling factors set by default. When you will run the report, the displayed result is calculated with the scaling factor.
    Regards,
    VA

  • BAPI to reverse Goods Issue for movement type 601

    Hi Everyone,
    Does anyone know of any BAPI that could be use to reverse Goods Issue for Movement type 601?
    I tried using BDC of transaction VL09 and was able to reverse the GI document successfully but the return message type was 'E' with unreadable message -
    Tabelle 'E' enth#t keinen Eintrag f# 'Ch 004 &'
    When I tried using BAPI_GOODSMVT_CANCEL, I get the error message 'E M7 130 Material document cannot be processed'.
    Best Regards,
    Junwen

    hi, Junwen!
    the following code works pretty well:
          fp_vbeln = vbeln_val.
          fp_budat = budat_val.
          fp_tcode = 'VL09'.
          fp_vbtyp = 'J'.
          CALL FUNCTION 'WS_REVERSE_GOODS_ISSUE'
            EXPORTING
              i_vbeln                         = fp_vbeln
              i_budat                         = fp_budat
            I_COUNT                         =
            I_MBLNR                         =
              i_tcode                         = fp_tcode
              i_vbtyp                         = fp_vbtyp
            TABLES
              t_mesg                          = it_mesg
           EXCEPTIONS
             error_reverse_goods_issue       = 1
             OTHERS                          = 2.
    luck.

  • Unable to manually change the amount for condition type PB00

    Hi Gurus,
    My client is using ECC5.0.
    Here when I try to change the amount for condition type PB00 using transaction ME22N, I am not able to change the value. I donu2019t get any error, but as soon as I change the value and press Enter the system replaces my entered value with the original value.
    Confusing part is that I am able to change the amount of condition price PB00 manually using transaction ME22. I donu2019t have any such problems there.
    Also I am able to manually change the amount of condition type PBXX using ME22N.
    Only in the case of PB00, if I use ME22N to manually update the amount I am not able to change it.
    Kindly help me, to find a reason as to why this could be happening, and correcting if possible?
    Thanks in advance,
    Imran

    Hello Imram,
    The purpose of maintaining 2 condition types  ie PB00 and PBXX in  a pricing procedure is that PB00 is automatic gross price determination and PBXX is manually giving gross price.
    If you go to T.Code : M/06 and check the condition types, you can see that PB00 will be having an access sequence but not PBXX.
    So if you have to manually give the gross price, you have to use PBXX.
    Regards

  • Requirements not fullfilled for Condition type - Pricing Procedure

    When I am doing the pricing procedure, the error thrown is "Requirements not fullfilled for Condition type". Can any one suggest how to fix this problem ?

    Hi Sunil,
         Please first of all check the condition type in Pricing Procedure. In condition type column check the requirement. Here conditon is,  once requirement is fulfilled which you have mentioned in the condition type then only it will be executed. Take a help of  ABAP'er regarding this requirement if it is customized requirement.
    We should know the purpose of requirement in condition type.
    Venkat.

  • Authority check in for condition type

    Hi
    What do you mean by an authority check on condition type.. especially Pricing..
    There are authority check that are embedded as Reqt and AltCTy in the IMG at the pricing procedure level for different condition type.
    Could someone explain me what they are for..?
    Thanks
    Jac

    Hi,
        authority check is the std sap methodology of check the permitted authorisation values for every transaction  and every user.
    here in this example;authority object is used to maintain or change condition record for allowed condition types.
    scenario eg;if we maintain create value for user mukund for pr00 condition type ,system allows me only for creating .if we maintain change value for user sherin for condition type,system allows to change the values.
    net net i can create and u can change ,not visa-viz or any body else cannot do it.
    hope this is clear.if it helps  REWARD!!!!!!!

  • Restriction for condition type

    Hi,
    I want to restrict some users to do not change the basic price (PR00) in sale order (VA01/VA02), Plz let me know how I can do this.
    regards,
    sps.

    The objects concerned have to be:
    V_KOND_VEA Maintain condition: Auth. for use/appl./cond.type/table -- (Deals with condition records)
    V_KONH_VKO Condition: Authorization for Sales Organizations
    V_KONH_VKS Condition: Authorization for Condition Types
    But in the standard system VA02 has these objects set to No check in SU24. You may have to modify this to Check/maintain and then maintain the values in the users role. Like you can have:
    Object : V_KONH_VKS Condition: Authorization for Condition Types
    Condition Type: PR00
    Actvt : 03
    Thanks & Regards
    JP

  • Why not all billing documents are posted to CO-PA for condition types?

    Hello!
    I have following problem.
    In transaction KE4I I have configured several condition types to post for specific value fields.
    For some billing types it works but for some doesn't work.
    For all domestic invoices it works but for abroad invoices it doesn't work.
    Billing documents for abroad invoices are also posted to CO-PA but for another value fields, not for that I expect.
    Where is problem?
    I am waiting for help.
    Best regards
    Bogdan

    Hi.
    In both pricing procedures there are same condition types. The only difference was check box "Condition is used for statistics".
    After marking this check box it still doesn't work.
    There are placed the same condition types in all billing documents (domestic and abroad) . So I am supprised that for domestic billing documents field value in CO-PA is calculated for condition types placed in KE4I.
    But for abroad billing documents the same field value is not calculated for the same condition types placed in  KE4I.
    Where is a problem?
    I need help.
    Best regards
    Bogdan

  • Provision account key missing for condition type FRA1 in schema ZIMPOR

    Hi,
    While maintaining the condition value in PO, the below message displayed.
    "Provision account key missing for condition type FRA1 in schema ZIMPOR"
    Thanks and regards
    Murugesan

    Go to
    Spro>MM>Pur>Conditions>Define Price Determination Process>Define Calculation Schema
    here select ZIMP and click control data
    in that maintain "Account key" for FRA1 cond type in the Account key Column..
    (Second column from right side)

  • Provision account key missing for condition type ZPFV in schema ZUELOC

    Hi
    We have defined the condition type ZPFV for freight value & mentioning the same while creating po and in past we had prepared so many po by using this.
    we hv not change any thing & today we are getting message " Provision account key missing for condition type ZPFV in schema ZUELOC"
    What to do???????
    Thanks
    Ketan Vala

    hi..
    If the accrual is ticked in condition type in M/06, it should have an account key assigned to the condition type in the pricing procedure in M/08.
    Go to your contion type ZPFV and check whether you have checked Accrual or not..
    then go to ur pricing procedure ZUELOC and check the last two colums for your condito type i.e. Account Key and Accrual Key.
    Maintain these..
    try this if it works.
    Thanks...

  • Change accural key for condition type

    Hi,
        The accural key for condition type " special addition custom duty" is maintained wrongly in our Prd system .As a result wrong GL is getting posted.
    We want to change the accural key for this condition type.
    Not sure of the implications....
    There will be a problem with the existing Purchase Orders for which GR posted and Invoice pending.
    If  the new PO is created, the condition type may be fetched through the Info records. Info records will fetch the last purchase order and if the last PO is created before the changes done then the old accural key may appear in the new PO.
    How to handle this...?
    What is the standard process to handle the mistakes in the condition types?
    Regards,
    Rajesh Satope

    Hi Rajesh Satope,
    For "clean" open PO's (no GR or invoice) you can obtain the new codition type settings by applying "Update prices" at the bottom of the conditions screen. I am not sure though how can you do it for many PO's at once.
    For PO's with partial transactions posted, I believe you will have to complete them with the old setting, i.e. the balance on the accrual account booked via the GR shall be cleared on the same account by the invoice - so you shouldn't run "Update prices" for such PO. I think even SAP standard prohibits this.
    BR
    Raf

Maybe you are looking for