Currency JPY (japanees yen)

Hi All,
I am making the PO with currency JPY, and want to enter the price like 5.8 (in decimal) but system is not allowing me to enter the price in decimals. other than JPY i used USD and EURO and INR but there is no problem for these currency.
while we print the PO system is printing only "1" in Price column.
Thanks
Pankaj Garg

Dear Pankaj,
Kindly consult your ABAPer.
As in the PO print out the amount will be validated for decimal places.
For JPY it is madatory we should not use any decimal places in PO.
Inform your ABAPer to pass the amount by adding decimal places in side the program to bypass the validation in the program, again make the output amount as with out decimal places. If you do so then you can take the print out.
kindly check the Conversion rate is maintained as 100 JPY:1 INR
Rgds
Srini
Edited by: Srinivasan KR on Mar 9, 2009 11:32 AM

Similar Messages

WRITE command gives unexpected value when currency is JPY (japanse yen)

Hi All
I am getting unexpected value for below WRITE command but only when the currency is JPY (Japan Yen)
lv_amount = 1215.40
lv_currency = u2018JPYu2019.
write lv_amount to ev_amount_ext left-justified no-gap NO-GROUPING currency lv_currency.
Value wrongly gets as ev_amount_ext = 121540 (Decimal takes as full value)
Appreciate your help if you have any idea on this please
Many Thanks
Iver

Hi,
use like this
lv_amount = '1215.40'
lv_currency = u2018JPYu2019.
write lv_amount to ev_amount_ext left-justified no-gap NO-GROUPING currency lv_currency.
other wise.
data lv_amounts type string.
move lv_amount to lv_amounts.
lv_currency = u2018JPYu2019.
write lv_amount to ev_amount_ext left-justified no-gap NO-GROUPING currency lv_currency.

Error in PO net price currency JPY

sir,
PO was created with currency japanese YEN using Tcode ME21N . The net price was showing 142502300 (in JPY).
when checked in EKPO table , it saved with a value 1425023.00 instead of 142502300 .
what can be done to correct this.
In PO Print out , it showing values as 1425023.00 which is wrong.
SPRO>> NET WEAVER >> GENERAL SETTINGS >> CURRENCY>> SET DECIMAL values FOR CURRENCY CODES is showing 0 decimals against JPY (Japanese YEN)
I want to know where else the Decimal values could have been set to 2 decimal places.
FOr other currencies like US Dollars there is no error.
Regards,
Srinivasa Murthy

sir,
In OY04 i deleted entry related to Japan Yen ie. with 0 decimals.     This solved my problem. But already created orders with Japanese YEN had to be deleted .
For the orders created with new configration , the issue is rectified and    Net price in ME21N as well as the PO value in EKPO table showing same value with 2 decimals.
Thank you very much .
Regards,
Srinivasa Murthy

Txn : FF_5 and FEBA - Japanese currency JPY is showing decimals- Wrong

Dear Experts,
I am loading the bank statements sent by Bank of America where in there are Japanese currency JPY
for which decimals are not suppressed. When load this statement by using transaction FF_5 and then
look into FEBA at my surprise the Japanese currency JPY is showing decimals which is wrong.
I could not find any suitable user exit to fix this issue.
Could you please throw me a light how to fix these issue.
Many thanks in advance.
Best Regards
Chandra

Hi
To solve this kind pf problem, you need to use this syntax while writing data
write wa-value to wa2-value CURRENCY 'JPY'.
This will write the value in japanese format.
To make it generic instead of JPY, just pass your file currency value.
Cheers
Ravish

Problem with the currency JPY

Hi.
I have set up a table, in which a column is as price inputfield and another as currency column defined.
The price column is defined as 'currency' with 2 decimals, and the currency defined as 'cuky'
Now the problem comes, if I change the currency from JPY to other currency or reverse, the price will be substract by 100 or reverse.
can anyone help?
best regards

>
bxjy bxjy wrote:
> thanks for your reply.
> but is there any way to disable the functionality dynamically?
>
> best regards
If you use a field that doesn't have the data dictionary reference between the currency and the currency code field, then this funtionality won't be there. However the functionality is there for a good reason so be careful when removing it.

While displaying Local currency(JPY)....

Hi,
Here when I was displaying local currency for JPY the amount is displaying 188.76 instead of 18,876.
Can any body tell me why it is so.
I am displaying in ALV.
Can I know how to overcome out of this in ALV and in normal reporting.
Thanks in advance.
Message was edited by: Deepak333 k

Hi
check the table TCURX for enter JPY, in this table you can see how many decimals are allowed for a currency.
There is zero decimals for JPY, so 18,876 are stored as 188.76.
If you wrote: WRITE '188.76' CURRENCY 'JPN', you'll see 18,876.
So in your catalog table, for the field amount, you should indicate the reference currency field (CFIELDNAME and CTABNAME) or set JPN in the field CURRENCY.
Max

Currency JPY

hi guys,
I am creating an idoc where i have to send amounts in doc currency and loacal currency.
whenever the doc currency is JPY the amount send is wrong cause if the amount entered in the document is 1000 then its stored as 10.00 in the BSEG table.
i am not sure if this rule applies to any other currencies as well.
is there a FM that i can use to convert the amount to actual figure.
thanx and regards,
Tarun Bahal

Hi,
Please use below fm to convert currency.
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY_N'
    EXPORTING
     client                   = sy-mandt
      date                    = p_ep_bldat "Posting date
      foreign_amount          = p_ep_hwbas "Amount
      foreign_currency        = c_eur "JPY
      local_currency          = currency "To currency
   RATE                    = 0
     type_of_rate            = 'M'
READ_TCURR              = 'X'
   IMPORTING
EXCHANGE_RATE           =
FOREIGN_FACTOR          =
     local_amount            = p_ep_hwbas "After converting value
LOCAL_FACTOR            =
EXCHANGE_RATEX          =
FIXED_RATE              =
DERIVED_RATE_TYPE       =
   EXCEPTIONS
     no_rate_found           = 1
     overflow                = 2
     no_factors_found        = 3
     no_spread_found         = 4
     derived_2_times         = 5
     OTHERS                  = 6          .
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
If usefull please reward .
Thanks

Why does the currency display in Yen?

How do I change the price column back to read US dollars instead of Chinese Yen? I don't know what the conversion rate of Yen to Dollars is, and I sure as **** don't want to buy a song for $200. I did not change anything in the first place in iTunes window, it just appeared like that one day and I can't figure out how to change it. And I'm certainly not going to buy any songs in Yen.
Windows XP Pro

In the main store window, go down to the bottom of the page. At the bottom of the page, there is a flag icon with a dropdown arrow. Click on that arrow & put yourself back in the US store.

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).

Error: decimal places not allowed

Hi,
I am entering a PO in currency JPY(Japanese Yen).However when I try to enter a PO with net price for one of the items as say 2.71,it gives error decimal places not allowed.
I have maintained currency rate as 100 local currency=3.1 Yen
It only gives problem while using this currency.
What is the way out ?
Regards,
manOO

Hi,
Check the config of the currency code (OY04), it is probably set to not allow decimal places.
If this is the case, don't change it, simply enter a price of 271 with a price unit of 100, in the PO. This will give you a price of 2.71 for one
Steve B

Ekpo-netpr is 83,000,000.00 but the screen value is 8,300,000.000

the po price display 8,300,000.000 via me23n, but in table, the value of ekpo-netpr is 83,000,000.00.
the two value is not same, how can i get the correct po price.

unfortunatly you didnot tell the currency.
If it is a currency with 0 decimals like Yen then the value in table is always stored with 2 decimals according to the domain of the currency field but displayed using the decimlas from the currency table.
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).

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

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

Purchase Order for Japanese Yen

HI All,
My issue is only with Japanese Currency. When I am creating a PO, NETPR field of EKPO table is stored with higher value. However BSEG table is updated with the correct amount. Pls see the following example for better understanding :
PO Rate : 8,500,000.000 JPY (1 Qty)
Amt shown in NETPR/EKPO : 85,000,000.00 JPY (1 Qty)
Amt in BSEG : 8,500,000.000 JPY (1 Qty)
Exchange Rate : 37 Rs. per 100 Yen
Because of the above my register is showing higher value of purchase. I am not able to understand why EKPO table is stored with higher value.
Any help will be appreciated...
Thanking You,
Subrato

try to check what do you get on the screen when you use "Write EKPO-NETWR currency JPY" ?
Does it show correct value ?
Things to check -> all rate types used in your docs (you may use different rate types for FI & PO). Are your rates defined using proper factors ?
JPY in non-decimal currency, and SAP always store values in the tables with 2 decimals... so if you do not use addition "currency" in your write command -> you are going to get wrong results.

Problem with decimal in Japan currency

Hi Gurus,
I have a problem with Japan currency that when When i take the printout of document with JPY 5,168,277 it is wrongly printing as 51,682.77 but in document display it is showing correclty as 5,168,277. But when i check this in BSEG table it was wrong updated as 51,682.77 (WRBTR field) i hope it is picking the amount from this field for printing .
For the above i made changes in OY01 but i find there was no use.
In OY01 the decimal place setting is 1,234,567.89 the middle one of the three.
When i post the same amount to japan co code in currency JPY and if i check in BSEG table
Amount in LC                                      51,682.77
Amount          (WRBTR)                       51,682.77
Orig.reduction                                      0.00
G/L amount                                         5,168,277
When i post the same amount in non japan co code in JPY Currency and check in BSEG(area where i am facing problem)
Amount in LC                                      47,550.22
Amount          (WRBTR)                       51,682.77
Orig.reduction                                      0.00
G/L amount                                         5,168,277
Please tell me how to correct this.

May ne u can check this OSS note also 137626
Summary
Symptom
1. Which currencies have to be defined separately with regard to the number of decimal places?
2. What do I need to observe when maintaining decimal places for currencies?
3. Which Customizing presettings does SAP deliver in table TCURX (decimal places for currency codes)?
4. Does SAP deliver the Customizing presettings of decimal places for currency codes (Table TCURX) for upgrade installations?
5. Which information does SAP use for the specification of these Customizing presettings?
Solution
1. question: Which currencies have to be defined separately with
            regard to the number of decimal places?
Answer:
The number of decimal places can vary for currencies. Currencies which do not have two decimal places must be defined in table TCURX (decimal places for currency codes).
You can maintain this table via the R/3 Implementation Guide (Global Settings -> Currencies, Transaction OY04).
If a currency is not defined in Table TCURX (decimal places for currency codes), this currency is regarded as currency with two decimal places.
2. question: What do I need to observe when maintaining decimal places
            for currencies?
Answer:
During operation, you must neither delete currencies used nor change their definition of decimal places. Amounts in posted documents could become invalid or incorrect as a result.
3. question: Which Customizing presettings does SAP deliver in table
            TCURX (decimal places for currency codes) ?
Answer
At present, SAP delivers the following Customizing presettings for table TCURX:
ISO Currency Decimal places
Code
ADP   Andoran Peseta                            0
AFA   Afghani Afghani                          0
BEF   Belgian franc                             0
BHD   Bahraini dinar                            3
BIF   Burundi franc                             0
BYB   Belorussian rubel (old)                   0
BYR   Belorussian rubel (new)                   0
CLP   Chilean peso                              0
COP   Columbian peso                            0
DEM3 (Internal) German Mark (3 Dec.)           3
DJF   Djibouti franc                            0
ECS   Ecuadorian sucre                          0
ESP   Spanish peseta                            0
GNF   Guinea franc                              0
GRD   Greek drachma                             0
HUF   Hungarian forint                          0
IDR   Indonesian rupiah                         0
IQD   Iraqui dinar                              3
ITL   Italian lira                              0
JOD   Jordan dinar                              3
JPY   Japanese yen                              0
KMF   Comoros franc                             0
KRW   South Korean won                          0
KWD   Kuwaiti dinar                             3
LAK   Laos new kip                              0
LUF   Luxembourg franc                          0
LYD   Libyan dinar                              3
MGF   Madagascan franc                          0
MZM   Mozambique metical                        0
OMR   Omani rial                                3
PTE   Portugese escudo                          0
PYG   Paraguay guarani                          0
ROL   Roumanian Lei                             0
RWF   Rwanda franc                              0
TJR   Tadzhikistani rubel                       0
TMM   Turkmenistani manat                       0
TND   Tunesian dinar                            3
TPE   Timor escudo                              0
TRL   Turkish lira                              0
TWD   New Taiwan dollar                         0
UGX   Uganda shilling                           0
USDN (Internal) US Dollar (5 dec.pl.)          5
VND   Vietnamese dong                           0
VUV   Vanuata vatu                              0
XAF   CFA Franc BEAC                            0
XOF   CFA Franc BCEAO                           0
XPF   CFP Franc                                 0
4. question: Does SAP deliver the Customizing presettings of decimal
            places for currency codes (Table TCURX) for upgrade
             installations?
Antwort
Table TCURX (decimal places for currency codes) is a client-independent table of the delivery class "C" (Customizing table). Therefore the table contents for this table can only be delivered with new installations.
For upgrade installations, new or changed contents of Table TCURX are not delivered.
5. question: Which information does SAP use for the specification of
             these Customizing presettings?
Answer
Currency codes and decimal places for currency codes are defined in ISO standard 4217. For the specification of decimal places for currency codes, SAP uses this ISO standard.
For some currencies, for example, for the "Turkish lira", the decimal places which are used in reality deviate from the ISO definition. In many of these cases, SAP decided to adhere to the definitions generally used.
Example:
ISO standard 4217 defines two decimal places for the Turkish lira (TRL), however in reality zero decimal places are being used for the Turkish lira. SAP delivers zero decimal places as Customizing presetting for "Turkish lira".
Header Data
Release Status: Released for Customer
Released on: 14.08.2007 13:12:09
Priority: Recommendations/additional info
Category: FAQ
Primary Component: XX-CSC-XX Country specific Customizing & Functionality (Standard R/3)
Secondary Components: FI Financial Accounting
Releases
Release Independant
Related Notes
434349 - Change of decimal places of currencies
126531 - Collective note preliminary availability Colombia
Print Selected Notes (PDF)

Currency JPY (japanees yen)

Similar Messages

Maybe you are looking for