PO Price in 'JPY' Currency.

Hi Everybody ,
  I have the problem in 'JPY' Currency , I print PO Price in 'JPY'  on po form but this price removed decimal places.
eq.  Po Price is 100. but Po Form Print 1. What is that problem?
   I want Print PO Price 100.
How I print this price?
anybody tell me.
Thanks
S.Muthu,

Hi Narendra,
But only the item price in the printout is wrong, the total amount below is correct. for example:
qty              unit price         subtotal
8pc               70.00             560.00
                         total   =    56,000

Similar Messages

  • Inforecord Net price issue JPY currency

    Hi Experts
    I am facing an issue in Inforecords Net price when net price is mainatined in JPY currency
    The data maintained and as can be seen using ME13 for Net Price for example is 1 JPY
    Where as when I fetch this data using EINE table the value is shOWNn as 0.01
    ( Same is the case when Net price is maintained as 232,687  JPY. In EINE table NET price field this is shown as 2326.87JPY
    Please advice why the system behaviour is as mentioned above . Also how can we overcome this issue.
    Thanks and Regards
    Vikrant

    This is because the field is technically defined as currency field with 2 decimals.
    Please read OSS Note 53206 - Processing of currency fields.
    it explains whatyou have to do in your programs

  • Sending Mail with HUF / JPY currency in Workflow

    Hi Friends ,
    I have the below requirement .
    I have to send PO for approval throug Workflow . I am using " SO_NEW_DOCUMENT_SEND_API1"  inside one method to send mail through Workflow .
    My Requirement -  For JPY / HUF currency PO , Price of PO has to be sent to the Approver which has to be displayed in the Format of Approver's User settings in the mail . Decimal Notation should be as per  Approver's User settings.
    My Issue - When the workflow triggers user WF-BATCH takes care of fetching the PO price as per its format .( Decimal notaion mentioned for WF-BATCH user ) . Now this has to be changed as per the Approvers formal ( decimal notation ) in the mail that is being sent to Approver after the method execution .
    Brief clarification of the issue is mentioned below -
    My WF-BATCH user has format of decimal notaion -   (1.234.567,89) ,
    Approver's has format of decimal notation -  X (1,234,567.89)
    The PO price in HUF currency is being picked by WF-BATCH user in the method as per its decimal notation .
    This formal has to be changed to Approver's decimal notaion format in the method so that same format can be sent in the mail .
    If any one has come across this type of requirement , guidance to solve this will be highly appreciated .
    Thanks
    Prabhudutta

    Hi,
    You can solve in two ways.
    1. Transfer the the value WF-INITIATOR to the method. Then update the Sy-uname start of the method or before the calling the " SO_NEW_DOCUMENT_SEND_API1".
    SY-UNAME = lv_user ( where lv_user holds the wf-initiator value[leading US must be removed] )
    ( background user will be changed from WF-BATCH to wf initiator )
    2. convert the date format by using the follwing methods before calling the FM  " SO_NEW_DOCUMENT_SEND_API1".
    /MRSS/RMOR_USER_CONVERT_DATE
    CONVERT_DATE_TO_External
    CONVERT_DATE_TO_INTERNAL
    Hoping that this might help you.
    Thanks and regards,
    SNJY
    Edited by: Sanju.pal on May 19, 2011 7:17 PM

  • JPY Currency wrong calculation through BAPI

    Hi SAP Gurus,
    If i try craete Purchase order by BAPI_PO_CREATE for JPY currency,
    For Ex : If we input 1 JPY as net price in BAPi and after creating PO
    it is reflecting 100 JPY
    Suggest on this how take a call
    Regards,
    Vinod

    hi
    JYP currency dont have dcimals so if u have value of 1.00 then it will get read as 100 only
    so either u give decmals in jpy currency or try some abaping for this
    go to OY04 here give the decimals
    regards
    KI

  • JPY Currency issue in SRM 5 Limit Items

    Hi
    We are having an issue JPY Currency issue in SRM Limit Items (550 SP 13).
    Basically the currencies like JPY, KWR where there are no decimals causes value to be multiplied by 100.
    There are lot of notes and threads on JPY currency issues.
    But I have not found one that helps fix SRM Limit Items.
    Let me know if there is a note or thread that talks about it.
    We are on SRM 550 SP 13.
    Thank You
    Nikhil

    see MDM forum

  • Purchase Order with JPY Currency

    Hi Friends,
    While raising PO with currency JPY, there is an unusual issue noticed in all POs. The netprice is getting truncated by 02 zeros in the end always.
    For ex, if a PO with JPY currency is raised with netprice as 98000.00 (Ninety Eight thousand), table EKPO is getting updated with Netprice as 980.00 (Nine hundred eighty) only. This is happening for all POs raised with currency as JPY. But this is not the case for POs with INR, USD or EUR currency. This issue is happening for all POs with currency with JPY.
    Can you pl proivde your expertise as to why this is happening?
    Regards
    Amitava

    from OSS note 1176399:
    SAP format for amounts
    In an SAP system, amounts (data type CURR) are always stored in the database using exactly two decimal places. It does not matter how many decimal places are actually allowed for the relevant currency.
    However, amounts are displayed on screens as converted in accordance with their number of decimal places. The number of decimal places, and therefore the shift of the decimal point, is stored in the table TCURX.
    Example
    The currencies JPY (Japanese Yen) and TWD (Taiwanese Dollar) do not have any decimal places. An amount of 123456 JPY is stored on the database as 1234.56 JPY; however, on the screen (for example, in the PSA maintenance, in the query or in the LISTCUBE) it is displayed as 123,456 JPY (when using the comma as the thousand separator).

  • Problem with JPY Currency

    Hello Experts,
    We are facing problem with values which are related to JPY Currency.
    In the DSO out put for Key figure Amount in doc currency it is showing 110,43 when you double click it is showing actual value that is 11043.
    Because of wrong valus we are getting negative values in the Query.
    For other currecies values are correct.
    Can any body share why it is displaying wrong values.
    Regards
    Ram

    Hi,
    I understand your problem,
    You can multiply your values by 100 in the transformation start routine to transfer correct valeus.
    Hope this helps.
    Regards
    Venkat

  • Asian (JPY) currency Decimal Places Issue

    HI All,
    Need your help, we have a program which creates a BDC session and when the user tries to process it it throws an errror for amount in asian currencies like JPY - no decimal places allowed for currency, in the background it calls the FBB1 transaction.
    The original amount is in USD however after conversion when we store it back to amount field which is of type
    "glpct-tslvt"  it stores the amount in JPY currency with decimal places so for example :
    USD amount  = 93,214. 00
    JPY amount = 115,021. 86
    guess the amount is stored with decimals in BSEG table, so now when we try to process the session with the JPY amount with decimals it throws an error.
    I have tried the
    CALL FUNCTION 'CURRENCY_AMOUNT_SAP_TO_DISPLAY'
    and
    CALL FUNCTION 'BAPI_CURRENCY_GETDECIMALS'
    it gives me the correct value for amount so for above example  JPY amount = 115,021. 86 by using the mentioned two methods i am able to get the currency in this format  11502186.00 but still has two decimal places, i think it still will not work when we process the session for FBB1.
    Need your help people, appreciate your co-operation.

    sorry to revive an old thread...but we are having an issue with JPY in our electronic bank statements.
    the BAI format for our JPY account has for example 900 yen which according to our finance department is really 9 yen. the bank claims this is a known issue and the BAI format documentation seems to be confirming the bank's position in that the decimals are implied according to the currency code (whatever that means in SAP terms is a bit foggy to us).....
    currently we wrote a custom code to suppress the last two zeros (when they are zeros) but i feel this error is caused either by a wrong setting in our currency or translation tables in SAP or something else since our feeling is that this should work right out of the box without any custom programming...any ideas???...where we shoudl start looking in our currency config....does the 100:1 or 1:1 translation ratio between JPY/USD make any difference...should we try and use a function module to convert the currency ...any ideas or hints are welcome
    thanks
    Ram
    [email protected]

  • JPY Currency problem

    Hi all,
    I have created an Import PO with rate 62500 JPY (decimal places are are not allowed in PO),
    But in table level the rate is stored as 625.00 (with 2 decimal)
    due to which during GR goods are validated for 625.00 instead of 62500.
    Kindly suggest some idea.
    Rgds
    Srini

    Hi Yogi,
    I’m facing decimal places problem with the field BSEG-WRBTR for the currency
    JPY as no decimals are allowed in standard system. Error: Formatting error in
    the field BSEG-WRBTR & Decimal places are not permitted
    Our client is posting accounting document through frontend system (interface).
    It comes to SAP in xml format.
    I have debugged and noticed that it’s taking 2 decimals even the amount in
    the xml has no decimals.  I’m trying to restrict
    decimal for JPY in the interface program.
    I have checked in OY04, but for
    JPY currency not maintained any decimals.
    Kindly share your valuable suggestions.
    Thanks,
    Rajasekhar S

  • Re-configure JPY currency

    Hello peeps,
    Good evening!
    I want to ask again your help regarding currency configuration specifically for 'YEN'.
    Is it possible to set the JPY currency to 2 decimal place just like the USD currency? If possible, how? Is there any effect with the existing data or transactions in the system?
    Hope you can give me a bit of advise..
    Thank you very much..
    April =)

    OY04 is the tcode where you make this change.
    Here is an extract of the warning that SAP posts for such changes :
    In the R/3 System tables currency fields are stored as decimal figures with a variable number of decimal places. The decimal point is not stored in the field in the database. Instead, each currency field refers to a currency key field. In this transaction you assign the number of decimal places to this currency key uniquely.
    Example: If you have set currency USD to have two decimal places and you post an amount of 100 USD, an amount of 10000 USD is stored in the currency field in the database. Not until this amount is processed further or is output does the system use the currency key from the reference field to determine the number of decimal places via this table. In this way the table content can be interpreted correctly for further processing or formatted for output with the correct Punctuation.
    If after posting you changed the number of decimal places for USD, for example, to 3, the existing field content of 10000 would be interpreted for futher processing or output as 10 USD (10.000). This would mean that the contents of tables across the system would, for all currency fields containing an amount in USD, be interpreted incorrectly by 10 per cent. To change the number of decimal places for a currency already in use, you must convert all the tables in the R/3 System that contain currency fields, so that the data integrity   
    remains. This cannot, however, for both organizational reasons and under the runtime aspect be carried out in a productive system. 
    The following changes to the TCURX table can thus lead to the loss of data integrity if you make the changes in a productive system or transport them into a productive system:      
    o Change to the number of decimal places of an existing currency                           
    o Deletion of an entry from the TCURX table   
    o Deletion of an entry from the TCURX table   (corresponds to changing the decimal places to the standard value of two decimal places)           
    o Insertion of an entry in the TCURX                  
      (corresponds to changing the standard value of 2 decimal places to a different value), if this is a currency code that already exists
    Uncritical changes are any made to this table during the Customizing of a new installation or the insertion of TCURX even during operations, if the currency codes have just been entered in the TCURC table using transaction OY03, signifying that no postings to these currency codes can have been carried out yet.

  • FAGLB03 - *"No Authorization for Transfer Prices, Third Local Currency"*

    Hi Experts,
    I am getting error while process the line item avilable in the T.Code FAGLB03- New GL Display.
    When I am double clicking any line item the system giving this below error.
    "No Authorization for Transfer Prices, Third Local Currency"
    Hope it would be same gap in the configuration level.
    Experts, please advice asap.
    Warm Regards,
    Sivakumar Sathiyamoorthy

    Hi,
    Note 1238115 - FAGLB03: Authorizations not always checked
    Sorry for inconviniecy caused
    Regards,
    jigar

  • Unit Price In BP Currency

    Hi,
    I have done following setup:
    Local Curency: INR
    System Currency: USD
    I have prepare BOM for Sales Item for which i get Product Price from BOM in INR which is obtained in Sales Quotation as unit selling price.
    I want to divide  this unit price by Current rate as entered in BP currecy rate so as to obtain Unit price in BP currency.
    can ay one suggest some solution

    What do you mean by
    "I have prepare BOM for Sales Item"
    "i get Product Price from BOM in INR which is obtained in Sales Quotation as unit selling price"
    "I want to divide this unit price by Current rate as entered in BP currecy rate so as to obtain Unit price in BP currency"
    can ay one suggest some solution"
    May I ask that you explain your question in a bit more detail that is understandable.

  • JPY Currency Decimal Places

    Hi  All
    Today we noticed a difference in the way SAP handles a PO which has document currency JPY. The price displayed on screen for the PO was 790 JPY, but the value stored in the tables was 0.79.  Any reason why this like this ? How does standard SAP handles such cases ?
    Regards
    Kasi

    Hi
    There are certain currencies like JPY/Yen for which amounts are automatically handled by SAP. Currency JPY has 0 decimals. Refer TCURX table for the details of decimal places for currencies.
    In the case of JPY, system automatically multiplies values when displayed from table to screen and divides vice versa.
    FM 'CURRENCY_AMOUNT_SAP_TO_DISPLAY' is used for this conversion.
    Amount 7900 JPY on screen will be stored as 79 in SAP tables.
    Also, in the case of exchange rate conversions, the rate maintained are for 1:100 to USD (ex). while other currencies would hold 1:1 conversion rate.
    You can also check with FI consultants for more details
    Thanks
    E.Avudaiappan

  • PO Net price for JPY

    Hi,
        I have a situation in PO netprice for currency JPY. Fro example, the net price on the PO (ME23N) shows as 131,325,000, but at the table level (Both EKPO and conditions) it shows like 1,313,250.00 . The last two digits are taken as decimals, but they are not decimals. The correct value is displayed correctly in ME23N, but the value stored in DB is wrong.
    My question is , is it possible to store the right value in DB or each time do I have to multiply by 100 to get the correct value for JPY? Thanks,
    Regards,
    Sundar.

    Hi Sundar,
    Transaction SE16 is a technical view to databases/tables and is designed and created for programmers but not for normal users.                           
    You didn't encounter an error, this is just the way the R/3 works with its data internally. If your issue is about a report, You have to adjust your reports according to the way R/3 handles currency amounts.Let's me explain, the value of data stored in EKPO depends on the decimal places defined for the currency. Standard is taken as 2.                
    Therefore the value will be the same as order price only if the currency is defined for two decimal places (default is 2).                               
    Currencies which do not have two decimal places must be defined in table TCURX (decimal places for currency codes). You can check tableTCURX for JPY - CURRDEC = 0. Zero decimal places are defined for currency JPY.                                                                   
    So, if you want to use EKPO-NETPR for your own applications, you must also consider table TCURX. All currencies that do not have any decimal places at all (TCURX-CURRDEC = 0) must have EKPO-NETPR multiplied by 100. 
    Hope this explain your issue !!!
    Regards,
    Mauro

  • JPY  Currency With Decimal upto 2,3 Decimal

    Dear Expertise
    How to handle the Currnecy in JPY with upto 2 decimal
    i need it IN PO with  upto 2 Decimal like price is 34.68 JPY.
    Hows Its Possible !
    Rgds
    Pankaj Agarwal

    Dear Pankaj,
    The correct transaction to set the cdecimal for urrency was OY04.
    However, normally this need to take place at very beginning of your system implementation
    as it was not good to adjust it later on as this might create inconsistency in your system
    if you already had existing purchasing document.
    You still can try to change it but i will advice you to make it at test system and see if the result
    was ok. Also, I just want to tell you normally JPY don't use decimal place as the currency was
    too small and decimal point of 2 actually was no meaning and in standard system normally we use
    it without decimal places compare to USD where the currency was big.
    Hope this information will help,
    Ian Wong

Maybe you are looking for