Japanese yen conversion

Hi,
I have one issue..In the PO number of quantity is 5.000 and rate 300 it is appearing in PO the amount is 1,500 JPY. But in the EKPO table EFFWR field it is showing 15.00...it is only for japanese Yen only...Some purchase order currency is USD, that is appearing in case 2000..in the EFFWR shows 2000$...But Japanese yen only having an issue while writing a code...It is showing whatever stored in table 15.00. Is there any conversion factor to consider while fetching the value...Please suggest me..
Thanks
RB

this is something thing to do with decimal places check table TCURX it has number of decimal places each currency has even though its displayed in the table like that when it fetch data it converts it to the correct order.
hope this help,
but it might be bit late now
Nafran

Similar Messages

Japanese yen currency conversions

Hi,
In SAP when i display the document it shows the correct amount like 48000247 for japanese yen.But when i go and look in BSEG i am seeing the value as 480002.47 .As BSEG is having that value even BW is pulling in the same value of 480002.47 .When i look in TCURX it shows 0 decimals for Japenese YEN.we are not doing reporting in BW.In our system BW just needs to extract data from SAP and send it to openhub.After extraction we want in BW to display as 48000247 instead of 480002.47.
Any pointers will be of great help.
Thanks,
Vijay.

Hi Vijay,,
Regarding your case, it think ..
It's because of ratio ..
You can check it within TCURF table ..
e.g.
from JPY : USD = 100 : 1
So in the routine of JPY currency, you must devide it by 100
The function to get the factor of corresponding currency is:
CURRENCY_CONVERTING_FACTOR
Hopefully it can help you a lot.
Regards,
Niel
thanks for the points you choose to assign.

Japanese Yen currency issues

hello, friends.
there is a situation where japanese yen is divided by 100. for example, the procurement price of a material is Yen 3,000,000. but it shows up as 30,000 in a purchase order.
a SAP Note 647667 says this is due to a source code error, especially where currency conversions apply and the currency involved does not have decimal places. but our BASIS says this SAP Note is applicable to SRM, and not to ERP.
has anyone encountered a similar problem? what was your solution?
many thanks.

hello, friend.
the exchange rate is correct. in OY04, the number of decimal places is 0.
in another thread with a similar issue, the supposed solution was to delete OY04, and in OY01 we maintain the currency with decimal places. however, i am hesitant to use this approach as i have seen problems when changes are made in OY04. in fact, when OY04 is accessed, there is a warning that states that existing data will be distorted; this i have witnessed as well.
hope there is a standard remedy.
thanks.

How do I find the symbol for the Japanese Yen?

I'm trying to add the Japanese Yen symbol to a document written in English. I have a US purchased MAC set to English.
G5 and Powerbook G4 Mac OS X (10.4.6)

Option/alt + y. ¥
Keyboard Viewer (activate in system prefs/international/input menu) lets you see which key does what.

Handling of Japanese Yen in ADOBE interactive form

Hello Everybody,
Could somebody provide me with the example of the script to handle Price filed for US and Canadian Dollars ( $zzzzzz9.99) and Japanese Yen ( zzzzzzzzz9)
I understand that I need to have a script that will adjust formatting of the amount field based on the value of the currency field. However I have never done these scripts and am looking for any example...
Thanks you in advance,
Felix

Hello Raju,
Thank for quick reply... It does remove decimal point and "00" in case of whole amount - so I am half way there
I was just wondering if there was a way to change amount display format based on the currency field. What I mean is that when I have Canadian or US dollars I want to display those decimal zeros and when currency is changed to JPY I want to suppress them. I also need to make sure that in case of a Yen user does not enter any decimals values...
I would appreciate your suggestion.
Thanks,
Felix

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.

ITunes store only comes up in Japanese yen - help!

When I perform a search for a particular song, the choices are priced in yen. When I click to buy a song, much of the text is square characters (presumably Japanese characters that my software does not recognize). How can I resolve this problem? Thank you.

Go to the Music Store Home Page, scroll down to the bottom and select your country from the drop down menu in the center of the screen - next to what is most likely showing a Japanese flag.

Why are the prices shown in Japanese YEN!!!!?????

I am located in Budapest, Hungary, however the characters and prices on my itunes is in Japanese! Is this something there is a setting for that I can simply change? I've tried uninstalling and reinstalling, but the same thing happened!! WHY????
Thanks,
ames101

You can select the country of the iTunes Music Store by using the Change Country item at the bottom of the main iTMS windows in iTunes.
But there is no store for Hungary, so unless you have a credit card issued by a bank in a country that does have an iTMS - the billing address also needs to be in that same country - you won't be able to purchase from the iTunes Music Store. Sorry, but that's mandated by the record companies who do not want to allow cross-border sales.

Japanese Yen multiply by 100 automatically

Hi Experts
In a customized transaction with table control in module pool. I have two columns Amount(Currency) and Currency(Currency Key)
When I put 100 and press enter it muliplies the value by 100 and shows as 10,000 JPY.
This is only done for Currency JPY and KRW.
I searching for SAP Note for this, can any one please suggest an alternative.
My System is ECC 6.0
Thanks

You can also use FM BAPI_CURRENCY_CONV_TO_EXTERNAL
In this FM you will have to pass the Currency Key and Amount in Internal format, to get the amount in External format.
Or you can use the write statement with the currency key to write the amount in external format
Thanks in Advance.
Regards,
Rajesh

My itunes library when using my phone is in Japanese, and the currency is set to yen. I have changed the settings via the flag at the bottom of itunes on windows but its only changed on my windows itunes.

The currency on my itunes store when using my iPhone is in Japanese yen, the menu is in Japanese too. I have changed the country using the flag at the bottom of itunes for windows, I have synced my iphone and restarted it, but it still has not changed. I also cannot set up a payment method for itunes as it keeps asking for japanese bank details? Help!

The currency on my itunes store when using my iPhone is in Japanese yen, the menu is in Japanese too. I have changed the country using the flag at the bottom of itunes for windows, I have synced my iphone and restarted it, but it still has not changed. I also cannot set up a payment method for itunes as it keeps asking for japanese bank details? Help!

Report Painter Currency Help

Hello Gurus!!
I'm a report painter user for almost a month, i've been doing a report using multiple currencies, it has worked well, but i need it now to make it to a target currency (lets say, Japanese Yens, YEN), the money is originally in mexican pesos (MXN), the company money unit is dollars (USD).
I want to make a conversion directly from MXN to YEN, but the sistems makes this conversion: MXN->USD->YEN, i've made lots of changes on the system, and still can't find out how to resolve this, i need direct conversions, not the triangulation its making, hope u can help me, thanks!!

Hi,
You can copy and create the new report with column defined with basic key figure as "Total Cost in Object Currency".
You also have the option to translate the report from one currency to another inn final output.
Hope this helps.
Assign points if helpful.
Regards,

Exception currencies TCURX table, R3 - BW loading issue

Hello Friends,
I am facing issue in report values for amount in local currency key field. Its value not matching with R3 values. Decimal places are shifted in report.
We are on BI7 (RSDS data source).
There is data coming from R3 into one DSO from different different data sources (Sales, Billing, Purchasing etc) and then getting loaded to cube for reporting.
Few data sources are standard like LIS and few are Z data sources.
This issue must be related to exception currencies maintained in TCURX table. Becauase we are getting issues only for those currencies.
For Ex: See R3 and report value is different.
R3 value:71.230,00 KWD
Cube value:71.230,00 KWD
Report value: 7.123,000 KWD
BW report is showing discrepancy for KWD, CLP (TCURX) currencies for Actual amount in LC key figure.
Can you please explain how to handle fix here?
I have heard that the ECC to BW the respective customization needs to be considered into account in the source system itself.
So can we ask our R3 team to fix this issue for exceptional currencies on R3 side. And any particular information that we will have to share with R3 team to get this corrected?
Please share your inputs on this.
Thank You.

Hi P.K,
We too have faced same issue in last project, we followed some procedure as I attached below.
Please go through the attached document and understand.
Issue description: SAP stores all Amount values of different currencies with a fixed interpretation of having two decimal places. There are few exceptions to this rule for the currencies which has no meaning for the decimal places like 'Chilean Peso', Japanese Yen, South Korean Won, Paraguayan Guarani and many other currencies which we talk in the below sections. For few Currencies the fractions are needs to be stored more than 2 decimals due to the currency values and this document describes the procedures that needs to be followed to have the right reporting.
Analysis provided: Kenya Sales KPI’s values display by multiple of 100.
This document describes the procedure to handle the currencies which has the decimal places other than 2 in the table TCURX.
About TCURX table:
Currencies which do not have two decimal places must be defined in table TCURX (decimal places for currency codes). The table determines the number of decimal places in the output according to the currency key. If the contents of currency exist in table TCURX as currency key CURRKEY, the system sets the number of decimal places according to the entry for the field CURRDEC in TCURX. 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.
Impact of TCURX in BW on data:
Currently in my present system the following currencies were listed in the TCURX Table:
Details of the Currencies
In the above table some of the Currencies are obsolete.
Data load from Source to BW:
In the Source I have the data like below:
For one of the company the total net Sales is present as 675772,43 CLP (Chilean Peso) in the source system for the period Jan’12.
When the data is loaded into BW:
The data in the Source and in the Cube is matching each other.
Data reported in the query looks like below:
The data in the query gets multiplied by 100 which results in 67577243.00 CLP this is due to the fact that when we execute the query, the query looks at the possible entry of the the currency in the table TCURX. If the entry is available as 0, then it will multiply by 100 as normally as per SAP, all Currencies are stored with two decimal places.
Corrective measures / steps which user should take before raising an issue:
This behavior is due to the fact that the Query always looks at the TCURX table while execution and if there is an entry in TCURX then it will be considered as below:
[Amount Value] * [10 ** (2- (CURRDEC entry in TCURX table))]
In present case as the entry is marked as 0 in TCURX table the result will be like below:
                       = Amount*10**(2-0) = Amount*10**2 = Amount * 100
This will be corrected as below:
All amount related entries at the data source level should be marked to ‘External Format’.
Earlier the same was like below with the internal format.
In 3.x we have the option to choose the same at the infopackage level with 'Currency Conversion for External Systems':
The above change in the data source will provide the below results:
During data loads: When we load the data into BW having amount fields in it, it checks the TCURX table for the currency entry. If the currency entry is present in TCURX table, it divides the amount value by 10** (2- (CURRDEC entry in TCURX table)).
Query Output: The exactly reverse happens while displaying such values in the report output. The amount value will be multiplied by 10** (2- (CURRDEC entry in TCURX table)) while displaying in the report output.
One of below example shows the results as below from the flat file when the format is changed to External.
From Flat file: Sample content from Flat file
In the Cube: Output from the Cube for the same entry
Values are divided by 100 as for Currency IDR the entry is marked as ‘ZERO’ in TCURX table for number    of Decimal places.
In the Query: Out of the Query looks like below:
Values the source value matches with the target value where the values of the cube get multiplied by 100.
Points to be noted: This procedure is only with the amounts having CURR data type.
If the amounts are used as FLTP type then this issue can also be avoided.
All the currencies having entry other than 2 in the field CURRDEC of table TCURX will be affected by this phenomenon.
The division will be carried out at the time of loading while multiplication will be carried out at the time of report output display.
Mainly this needs to be considered when dealing with the Flat file data loads which holds the currencies and for the ECC to BW the respective customization needs to be considered into account in the source system side.
Regards,
Vijay

ABAP Data type to XI data type mapping

Hi,
I am creating a message type in XI corresponding to a ABAP structure. There are couple of data types on the ABAP side (for example: RAW, QUAN, CURR CUKY, UNIT, NUMC etc) which i have no idea on what it should be mapped to on the XI side(xsd:string, xsd:token, xsd:int etc).
Is there is any document on mapping from ABAP data type to XML data type ? if yes please send it across.([email protected])
if no doc available, if some body could let me know what these ABAP data type would map on the XI side it would great.
Best Regards,
Kiran

Hi Kiran,
just some more background information to the data types CURR, CUKY, QUAN, UNIT:
1) Each field of data type CURR must be assigned to a field of data type CUKY (the financial amount must be assigned to a currency) and each field of data type QUAN must be assigned to a field of data type UNIT (each quantity must have a dimension). If you want to know this assignment for your specific ABAP structure, you can find it using transaction SE11 with your ABAP structure and go to the tab Currency/Quantity fields. Here you find the information under Reference table and Ref. field.
2) The default number of decimals for a field of data type CURR is 2, but this can be overwritten by the assigned CUKY field. You can check the actual number of decimals for a specific currency with transaction OY04. Here are all currency list that do not have 2 decimals.
3) The default number of decimals for a field of data type QUAN is 3, but this can be overwritten by the assigned UNIT field. You can check the actual number of decimals for a specific unit with transaction CUNI. Click on Units of measurement (pick the correct dimension first), double click on your unit and you find the info in the field Decimal places.
4) Depending on the data you receive your conversions can get quite tricky. Lets take as an example a field of type CURR. If you find the value 1000 in there, this would convert to 10.00 USD if the assigned CUKY field contains the value USD (US dollar). But the same value ca represent 1000 JPY (Japanese Yen) if the assigned CUKY field contains the value JPY. What i try to say is that the value in the field of type CURR alone does not give you the actual amount, you have to know the value of the CUKY field as well. Similar for QUAN and UNIT.
Regards,
Claus

Errors during Loading TD from Flat file to PSA

Hi Guys,
I got some errors while loading the flat file transaction data into PSA using infopackage.
Could you guys can help me to solve the below errors. It would be more appreciated if you guys could send some material which tells about these types of errors more detailly.
Points will be awarded.
Field /BIC/ZIO_PRIC ( Position 4 ): External length specification will be ignored
Message no. RSDS101
Diagnosis
The value 23 is specified as output length in Field /BIC/ZIO_PRIC ( Position 4 ). It is also specified that the data is shipped in internal format.
System Response
The length specification for output length is ignored. If the data in the source actually have the specified lengths, this results in conversion errors.
Procedure
Select the external format if required.
Field /BIC/ZIO_PRIC ( Position 4 ): Amount field in internal format; check settings
Message no. RSDS099
Diagnosis
Setting made for Field /BIC/ZIO_PRIC ( Position 4 ) states that the data from the source is available in the internal format.
This is not usually the case for this source system type.
System Response
If you do not change this setting, the data has to be available in the internal SAP format.
Example:
For the Japanese Yen this means: 1000 JPY has to be delivered from the source as 10.00 JPY.
Procedure
Check the data format of the source and where necessary, change the setting to External.
Field /BIC/ZIO_PRIC ( Position 4 ): Missing reference to currency field/unit field
Message no. RSDS151
Diagnosis
If an amount or quantity field is not delivered with values in internal format, an associated currency field or unit field must be specified so that the currency or units can be converted during data import.
System Response
The DataSource can not be activated.
Procedure
Specify a reference field if the data is delivered in external format.
Specify a reference field even if the currency or unit is constant. Fields with fixed values are not part of the data source; they are filled by the system when loaded.

Hi JUergen.
The order of the fields are same as datasource. I didn't make any field for amount in a flat file as it is defined as fixed currency usd when i created a key figure. i don't think so we have to create a field unless we take 0currency is a unit for price instead of fixed currency.
Though we got the above error, it still allows activates the datasource but the 10.00 usd shows as 1000 usd.
Cheers,
Shrinu

HTTP to SOAP

Hi All:
XI is consuming a webwervice http://www.webservicex.net/CurrencyConvertor.asmx
But when I am executing this scenario I am getting an Erro in the Adapter Engine
Result:
<SAP:Error><SAP:Category>XIAdapter</SAP:Category><SAP:Code>PARSING.ADAPTER.SOAP_EXCEPTION</SAP:Code><SAP:AdditionalText>soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
 at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
 at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
 at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText></SAP:Error>
For SOAP receiver adapter I provided the following URL and paremeters
Target URL : http://www.webservicex.net/CurrencyConvertor.asmx
Configure Proxy :
Host : IP
Port : 8080
Anyone has an idea why I am getting this Erro? appriciate your inputs
WSDL..using for Inbound Interface..
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://www.webserviceX.NET/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://www.webserviceX.NET/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
 <s:schema elementFormDefault="qualified" targetNamespace="http://www.webserviceX.NET/">
 <s:element name="ConversionRate">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="1" maxOccurs="1" name="FromCurrency" type="tns:Currency" />
 <s:element minOccurs="1" maxOccurs="1" name="ToCurrency" type="tns:Currency" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:simpleType name="Currency">
 <s:restriction base="s:string">
 <s:enumeration value="AFA" />
 <s:enumeration value="ALL" />
 <s:enumeration value="DZD" />
 <s:enumeration value="ARS" />
 <s:enumeration value="AWG" />
 <s:enumeration value="AUD" />
 <s:enumeration value="BSD" />
 <s:enumeration value="BHD" />
 <s:enumeration value="BDT" />
 <s:enumeration value="BBD" />
 <s:enumeration value="BZD" />
 <s:enumeration value="BMD" />
 <s:enumeration value="BTN" />
 <s:enumeration value="BOB" />
 <s:enumeration value="BWP" />
 <s:enumeration value="BRL" />
 <s:enumeration value="GBP" />
 <s:enumeration value="BND" />
 <s:enumeration value="BIF" />
 <s:enumeration value="XOF" />
 <s:enumeration value="XAF" />
 <s:enumeration value="KHR" />
 <s:enumeration value="CAD" />
 <s:enumeration value="CVE" />
 <s:enumeration value="KYD" />
 <s:enumeration value="CLP" />
 <s:enumeration value="CNY" />
 <s:enumeration value="COP" />
 <s:enumeration value="KMF" />
 <s:enumeration value="CRC" />
 <s:enumeration value="HRK" />
 <s:enumeration value="CUP" />
 <s:enumeration value="CYP" />
 <s:enumeration value="CZK" />
 <s:enumeration value="DKK" />
 <s:enumeration value="DJF" />
 <s:enumeration value="DOP" />
 <s:enumeration value="XCD" />
 <s:enumeration value="EGP" />
 <s:enumeration value="SVC" />
 <s:enumeration value="EEK" />
 <s:enumeration value="ETB" />
 <s:enumeration value="EUR" />
 <s:enumeration value="FKP" />
 <s:enumeration value="GMD" />
 <s:enumeration value="GHC" />
 <s:enumeration value="GIP" />
 <s:enumeration value="XAU" />
 <s:enumeration value="GTQ" />
 <s:enumeration value="GNF" />
 <s:enumeration value="GYD" />
 <s:enumeration value="HTG" />
 <s:enumeration value="HNL" />
 <s:enumeration value="HKD" />
 <s:enumeration value="HUF" />
 <s:enumeration value="ISK" />
 <s:enumeration value="INR" />
 <s:enumeration value="IDR" />
 <s:enumeration value="IQD" />
 <s:enumeration value="ILS" />
 <s:enumeration value="JMD" />
 <s:enumeration value="JPY" />
 <s:enumeration value="JOD" />
 <s:enumeration value="KZT" />
 <s:enumeration value="KES" />
 <s:enumeration value="KRW" />
 <s:enumeration value="KWD" />
 <s:enumeration value="LAK" />
 <s:enumeration value="LVL" />
 <s:enumeration value="LBP" />
 <s:enumeration value="LSL" />
 <s:enumeration value="LRD" />
 <s:enumeration value="LYD" />
 <s:enumeration value="LTL" />
 <s:enumeration value="MOP" />
 <s:enumeration value="MKD" />
 <s:enumeration value="MGF" />
 <s:enumeration value="MWK" />
 <s:enumeration value="MYR" />
 <s:enumeration value="MVR" />
 <s:enumeration value="MTL" />
 <s:enumeration value="MRO" />
 <s:enumeration value="MUR" />
 <s:enumeration value="MXN" />
 <s:enumeration value="MDL" />
 <s:enumeration value="MNT" />
 <s:enumeration value="MAD" />
 <s:enumeration value="MZM" />
 <s:enumeration value="MMK" />
 <s:enumeration value="NAD" />
 <s:enumeration value="NPR" />
 <s:enumeration value="ANG" />
 <s:enumeration value="NZD" />
 <s:enumeration value="NIO" />
 <s:enumeration value="NGN" />
 <s:enumeration value="KPW" />
 <s:enumeration value="NOK" />
 <s:enumeration value="OMR" />
 <s:enumeration value="XPF" />
 <s:enumeration value="PKR" />
 <s:enumeration value="XPD" />
 <s:enumeration value="PAB" />
 <s:enumeration value="PGK" />
 <s:enumeration value="PYG" />
 <s:enumeration value="PEN" />
 <s:enumeration value="PHP" />
 <s:enumeration value="XPT" />
 <s:enumeration value="PLN" />
 <s:enumeration value="QAR" />
 <s:enumeration value="ROL" />
 <s:enumeration value="RUB" />
 <s:enumeration value="WST" />
 <s:enumeration value="STD" />
 <s:enumeration value="SAR" />
 <s:enumeration value="SCR" />
 <s:enumeration value="SLL" />
 <s:enumeration value="XAG" />
 <s:enumeration value="SGD" />
 <s:enumeration value="SKK" />
 <s:enumeration value="SIT" />
 <s:enumeration value="SBD" />
 <s:enumeration value="SOS" />
 <s:enumeration value="ZAR" />
 <s:enumeration value="LKR" />
 <s:enumeration value="SHP" />
 <s:enumeration value="SDD" />
 <s:enumeration value="SRG" />
 <s:enumeration value="SZL" />
 <s:enumeration value="SEK" />
 <s:enumeration value="CHF" />
 <s:enumeration value="SYP" />
 <s:enumeration value="TWD" />
 <s:enumeration value="TZS" />
 <s:enumeration value="THB" />
 <s:enumeration value="TOP" />
 <s:enumeration value="TTD" />
 <s:enumeration value="TND" />
 <s:enumeration value="TRL" />
 <s:enumeration value="USD" />
 <s:enumeration value="AED" />
 <s:enumeration value="UGX" />
 <s:enumeration value="UAH" />
 <s:enumeration value="UYU" />
 <s:enumeration value="VUV" />
 <s:enumeration value="VEB" />
 <s:enumeration value="VND" />
 <s:enumeration value="YER" />
 <s:enumeration value="YUM" />
 <s:enumeration value="ZMK" />
 <s:enumeration value="ZWD" />
 <s:enumeration value="TRY" />
 </s:restriction>
 </s:simpleType>
 <s:element name="ConversionRateResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="1" maxOccurs="1" name="ConversionRateResult" type="s:double" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="double" type="s:double" />
 </s:schema>
</wsdl:types>
<wsdl:message name="ConversionRateSoapIn">
 <wsdl:part name="parameters" element="tns:ConversionRate" />
</wsdl:message>
<wsdl:message name="ConversionRateSoapOut">
 <wsdl:part name="parameters" element="tns:ConversionRateResponse" />
</wsdl:message>
<wsdl:message name="ConversionRateHttpGetIn">
 <wsdl:part name="FromCurrency" type="s:string" />
 <wsdl:part name="ToCurrency" type="s:string" />
</wsdl:message>
<wsdl:message name="ConversionRateHttpGetOut">
 <wsdl:part name="Body" element="tns:double" />
</wsdl:message>
<wsdl:message name="ConversionRateHttpPostIn">
 <wsdl:part name="FromCurrency" type="s:string" />
 <wsdl:part name="ToCurrency" type="s:string" />
</wsdl:message>
<wsdl:message name="ConversionRateHttpPostOut">
 <wsdl:part name="Body" element="tns:double" />
</wsdl:message>
<wsdl:portType name="CurrencyConvertorSoap">
 <wsdl:operation name="ConversionRate">
 <documentation xmlns="http://schemas.xmlsoap.org/wsdl/"> Get conversion rate from one currency to another currency Differenct currency Code and Names around the world<blockquote>AFA-Afghanistan Afghani ALL-Albanian Lek DZD-Algerian Dinar ARS-Argentine Peso AWG-Aruba Florin AUD-Australian Dollar BSD-Bahamian Dollar BHD-Bahraini Dinar BDT-Bangladesh Taka BBD-Barbados Dollar BZD-Belize Dollar BMD-Bermuda Dollar BTN-Bhutan Ngultrum BOB-Bolivian Boliviano BWP-Botswana Pula BRL-Brazilian Real GBP-British Pound BND-Brunei Dollar BIF-Burundi Franc XOF-CFA Franc (BCEAO) XAF-CFA Franc (BEAC) KHR-Cambodia Riel CAD-Canadian Dollar CVE-Cape Verde Escudo KYD-Cayman Islands Dollar CLP-Chilean Peso CNY-Chinese Yuan COP-Colombian Peso KMF-Comoros Franc CRC-Costa Rica Colon HRK-Croatian Kuna CUP-Cuban Peso CYP-Cyprus Pound CZK-Czech Koruna DKK-Danish Krone DJF-Dijibouti Franc DOP-Dominican Peso XCD-East Caribbean Dollar EGP-Egyptian Pound SVC-El Salvador Colon EEK-Estonian Kroon ETB-Ethiopian Birr EUR-Euro FKP-Falkland Islands Pound GMD-Gambian Dalasi GHC-Ghanian Cedi GIP-Gibraltar Pound XAU-Gold Ounces GTQ-Guatemala Quetzal GNF-Guinea Franc GYD-Guyana Dollar HTG-Haiti Gourde HNL-Honduras Lempira HKD-Hong Kong Dollar HUF-Hungarian Forint ISK-Iceland Krona INR-Indian Rupee IDR-Indonesian Rupiah IQD-Iraqi Dinar ILS-Israeli Shekel JMD-Jamaican Dollar JPY-Japanese Yen JOD-Jordanian Dinar KZT-Kazakhstan Tenge KES-Kenyan Shilling KRW-Korean Won KWD-Kuwaiti Dinar LAK-Lao Kip LVL-Latvian Lat LBP-Lebanese Pound LSL-Lesotho Loti LRD-Liberian Dollar LYD-Libyan Dinar LTL-Lithuanian Lita MOP-Macau Pataca MKD-Macedonian Denar MGF-Malagasy Franc MWK-Malawi Kwacha MYR-Malaysian Ringgit MVR-Maldives Rufiyaa MTL-Maltese Lira MRO-Mauritania Ougulya MUR-Mauritius Rupee MXN-Mexican Peso MDL-Moldovan Leu MNT-Mongolian Tugrik MAD-Moroccan Dirham MZM-Mozambique Metical MMK-Myanmar Kyat NAD-Namibian Dollar NPR-Nepalese Rupee ANG-Neth Antilles Guilder NZD-New Zealand Dollar NIO-Nicaragua Cordoba NGN-Nigerian Naira KPW-North Korean Won NOK-Norwegian Krone OMR-Omani Rial XPF-Pacific Franc PKR-Pakistani Rupee XPD-Palladium Ounces PAB-Panama Balboa PGK-Papua New Guinea Kina PYG-Paraguayan Guarani PEN-Peruvian Nuevo Sol PHP-Philippine Peso XPT-Platinum Ounces PLN-Polish Zloty QAR-Qatar Rial ROL-Romanian Leu RUB-Russian Rouble WST-Samoa Tala STD-Sao Tome Dobra SAR-Saudi Arabian Riyal SCR-Seychelles Rupee SLL-Sierra Leone Leone XAG-Silver Ounces SGD-Singapore Dollar SKK-Slovak Koruna SIT-Slovenian Tolar SBD-Solomon Islands Dollar SOS-Somali Shilling ZAR-South African Rand LKR-Sri Lanka Rupee SHP-St Helena Pound SDD-Sudanese Dinar SRG-Surinam Guilder SZL-Swaziland Lilageni SEK-Swedish Krona TRY-Turkey Lira CHF-Swiss Franc SYP-Syrian Pound TWD-Taiwan Dollar TZS-Tanzanian Shilling THB-Thai Baht TOP-Tonga Pa'anga TTD-Trinidad&amp;Tobago Dollar TND-Tunisian Dinar TRL-Turkish Lira USD-U.S. Dollar AED-UAE Dirham UGX-Ugandan Shilling UAH-Ukraine Hryvnia UYU-Uruguayan New Peso VUV-Vanuatu Vatu VEB-Venezuelan Bolivar VND-Vietnam Dong YER-Yemen Riyal YUM-Yugoslav Dinar ZMK-Zambian Kwacha ZWD-Zimbabwe Dollar</blockquote></documentation>
 <wsdl:input message="tns:ConversionRateSoapIn" />
 <wsdl:output message="tns:ConversionRateSoapOut" />
 </wsdl:operation>
</wsdl:portType>
<wsdl:portType name="CurrencyConvertorHttpGet">
 <wsdl:operation name="ConversionRate">
 <documentation xmlns="http://schemas.xmlsoap.org/wsdl/"> Get conversion rate from one currency to another currency Differenct currency Code and Names around the world<blockquote>AFA-Afghanistan Afghani ALL-Albanian Lek DZD-Algerian Dinar ARS-Argentine Peso AWG-Aruba Florin AUD-Australian Dollar BSD-Bahamian Dollar BHD-Bahraini Dinar BDT-Bangladesh Taka BBD-Barbados Dollar BZD-Belize Dollar BMD-Bermuda Dollar BTN-Bhutan Ngultrum BOB-Bolivian Boliviano BWP-Botswana Pula BRL-Brazilian Real GBP-British Pound BND-Brunei Dollar BIF-Burundi Franc XOF-CFA Franc (BCEAO) XAF-CFA Franc (BEAC) KHR-Cambodia Riel CAD-Canadian Dollar CVE-Cape Verde Escudo KYD-Cayman Islands Dollar CLP-Chilean Peso CNY-Chinese Yuan COP-Colombian Peso KMF-Comoros Franc CRC-Costa Rica Colon HRK-Croatian Kuna CUP-Cuban Peso CYP-Cyprus Pound CZK-Czech Koruna DKK-Danish Krone DJF-Dijibouti Franc DOP-Dominican Peso XCD-East Caribbean Dollar EGP-Egyptian Pound SVC-El Salvador Colon EEK-Estonian Kroon ETB-Ethiopian Birr EUR-Euro FKP-Falkland Islands Pound GMD-Gambian Dalasi GHC-Ghanian Cedi GIP-Gibraltar Pound XAU-Gold Ounces GTQ-Guatemala Quetzal GNF-Guinea Franc GYD-Guyana Dollar HTG-Haiti Gourde HNL-Honduras Lempira HKD-Hong Kong Dollar HUF-Hungarian Forint ISK-Iceland Krona INR-Indian Rupee IDR-Indonesian Rupiah IQD-Iraqi Dinar ILS-Israeli Shekel JMD-Jamaican Dollar JPY-Japanese Yen JOD-Jordanian Dinar KZT-Kazakhstan Tenge KES-Kenyan Shilling KRW-Korean Won KWD-Kuwaiti Dinar LAK-Lao Kip LVL-Latvian Lat LBP-Lebanese Pound LSL-Lesotho Loti LRD-Liberian Dollar LYD-Libyan Dinar LTL-Lithuanian Lita MOP-Macau Pataca MKD-Macedonian Denar MGF-Malagasy Franc MWK-Malawi Kwacha MYR-Malaysian Ringgit MVR-Maldives Rufiyaa MTL-Maltese Lira MRO-Mauritania Ougulya MUR-Mauritius Rupee MXN-Mexican Peso MDL-Moldovan Leu MNT-Mongolian Tugrik MAD-Moroccan Dirham MZM-Mozambique Metical MMK-Myanmar Kyat NAD-Namibian Dollar NPR-Nepalese Rupee ANG-Neth Antilles Guilder NZD-New Zealand Dollar NIO-Nicaragua Cordoba NGN-Nigerian Naira KPW-North Korean Won NOK-Norwegian Krone OMR-Omani Rial XPF-Pacific Franc PKR-Pakistani Rupee XPD-Palladium Ounces PAB-Panama Balboa PGK-Papua New Guinea Kina PYG-Paraguayan Guarani PEN-Peruvian Nuevo Sol PHP-Philippine Peso XPT-Platinum Ounces PLN-Polish Zloty QAR-Qatar Rial ROL-Romanian Leu RUB-Russian Rouble WST-Samoa Tala STD-Sao Tome Dobra SAR-Saudi Arabian Riyal SCR-Seychelles Rupee SLL-Sierra Leone Leone XAG-Silver Ounces SGD-Singapore Dollar SKK-Slovak Koruna SIT-Slovenian Tolar SBD-Solomon Islands Dollar SOS-Somali Shilling ZAR-South African Rand LKR-Sri Lanka Rupee SHP-St Helena Pound SDD-Sudanese Dinar SRG-Surinam Guilder SZL-Swaziland Lilageni SEK-Swedish Krona TRY-Turkey Lira CHF-Swiss Franc SYP-Syrian Pound TWD-Taiwan Dollar TZS-Tanzanian Shilling THB-Thai Baht TOP-Tonga Pa'anga TTD-Trinidad&amp;Tobago Dollar TND-Tunisian Dinar TRL-Turkish Lira USD-U.S. Dollar AED-UAE Dirham UGX-Ugandan Shilling UAH-Ukraine Hryvnia UYU-Uruguayan New Peso VUV-Vanuatu Vatu VEB-Venezuelan Bolivar VND-Vietnam Dong YER-Yemen Riyal YUM-Yugoslav Dinar ZMK-Zambian Kwacha ZWD-Zimbabwe Dollar</blockquote></documentation>
 <wsdl:input message="tns:ConversionRateHttpGetIn" />
 <wsdl:output message="tns:ConversionRateHttpGetOut" />
 </wsdl:operation>
</wsdl:portType>
<wsdl:portType name="CurrencyConvertorHttpPost">
 <wsdl:operation name="ConversionRate">
 <documentation xmlns="http://schemas.xmlsoap.org/wsdl/"> Get conversion rate from one currency to another currency Differenct currency Code and Names around the world<blockquote>AFA-Afghanistan Afghani ALL-Albanian Lek DZD-Algerian Dinar ARS-Argentine Peso AWG-Aruba Florin AUD-Australian Dollar BSD-Bahamian Dollar BHD-Bahraini Dinar BDT-Bangladesh Taka BBD-Barbados Dollar BZD-Belize Dollar BMD-Bermuda Dollar BTN-Bhutan Ngultrum BOB-Bolivian Boliviano BWP-Botswana Pula BRL-Brazilian Real GBP-British Pound BND-Brunei Dollar BIF-Burundi Franc XOF-CFA Franc (BCEAO) XAF-CFA Franc (BEAC) KHR-Cambodia Riel CAD-Canadian Dollar CVE-Cape Verde Escudo KYD-Cayman Islands Dollar CLP-Chilean Peso CNY-Chinese Yuan COP-Colombian Peso KMF-Comoros Franc CRC-Costa Rica Colon HRK-Croatian Kuna CUP-Cuban Peso CYP-Cyprus Pound CZK-Czech Koruna DKK-Danish Krone DJF-Dijibouti Franc DOP-Dominican Peso XCD-East Caribbean Dollar EGP-Egyptian Pound SVC-El Salvador Colon EEK-Estonian Kroon ETB-Ethiopian Birr EUR-Euro FKP-Falkland Islands Pound GMD-Gambian Dalasi GHC-Ghanian Cedi GIP-Gibraltar Pound XAU-Gold Ounces GTQ-Guatemala Quetzal GNF-Guinea Franc GYD-Guyana Dollar HTG-Haiti Gourde HNL-Honduras Lempira HKD-Hong Kong Dollar HUF-Hungarian Forint ISK-Iceland Krona INR-Indian Rupee IDR-Indonesian Rupiah IQD-Iraqi Dinar ILS-Israeli Shekel JMD-Jamaican Dollar JPY-Japanese Yen JOD-Jordanian Dinar KZT-Kazakhstan Tenge KES-Kenyan Shilling KRW-Korean Won KWD-Kuwaiti Dinar LAK-Lao Kip LVL-Latvian Lat LBP-Lebanese Pound LSL-Lesotho Loti LRD-Liberian Dollar LYD-Libyan Dinar LTL-Lithuanian Lita MOP-Macau Pataca MKD-Macedonian Denar MGF-Malagasy Franc MWK-Malawi Kwacha MYR-Malaysian Ringgit MVR-Maldives Rufiyaa MTL-Maltese Lira MRO-Mauritania Ougulya MUR-Mauritius Rupee MXN-Mexican Peso MDL-Moldovan Leu MNT-Mongolian Tugrik MAD-Moroccan Dirham MZM-Mozambique Metical MMK-Myanmar Kyat NAD-Namibian Dollar NPR-Nepalese Rupee ANG-Neth Antilles Guilder NZD-New Zealand Dollar NIO-Nicaragua Cordoba NGN-Nigerian Naira KPW-North Korean Won NOK-Norwegian Krone OMR-Omani Rial XPF-Pacific Franc PKR-Pakistani Rupee XPD-Palladium Ounces PAB-Panama Balboa PGK-Papua New Guinea Kina PYG-Paraguayan Guarani PEN-Peruvian Nuevo Sol PHP-Philippine Peso XPT-Platinum Ounces PLN-Polish Zloty QAR-Qatar Rial ROL-Romanian Leu RUB-Russian Rouble WST-Samoa Tala STD-Sao Tome Dobra SAR-Saudi Arabian Riyal SCR-Seychelles Rupee SLL-Sierra Leone Leone XAG-Silver Ounces SGD-Singapore Dollar SKK-Slovak Koruna SIT-Slovenian Tolar SBD-Solomon Islands Dollar SOS-Somali Shilling ZAR-South African Rand LKR-Sri Lanka Rupee SHP-St Helena Pound SDD-Sudanese Dinar SRG-Surinam Guilder SZL-Swaziland Lilageni SEK-Swedish Krona TRY-Turkey Lira CHF-Swiss Franc SYP-Syrian Pound TWD-Taiwan Dollar TZS-Tanzanian Shilling THB-Thai Baht TOP-Tonga Pa'anga TTD-Trinidad&amp;Tobago Dollar TND-Tunisian Dinar TRL-Turkish Lira USD-U.S. Dollar AED-UAE Dirham UGX-Ugandan Shilling UAH-Ukraine Hryvnia UYU-Uruguayan New Peso VUV-Vanuatu Vatu VEB-Venezuelan Bolivar VND-Vietnam Dong YER-Yemen Riyal YUM-Yugoslav Dinar ZMK-Zambian Kwacha ZWD-Zimbabwe Dollar</blockquote></documentation>
 <wsdl:input message="tns:ConversionRateHttpPostIn" />
 <wsdl:output message="tns:ConversionRateHttpPostOut" />
 </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="CurrencyConvertorSoap" type="tns:CurrencyConvertorSoap">
 <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
 <wsdl:operation name="ConversionRate">
 <soap:operation soapAction="http://www.webserviceX.NET/ConversionRate" style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
</wsdl:binding>
<wsdl:binding name="CurrencyConvertorHttpGet" type="tns:CurrencyConvertorHttpGet">
 <http:binding verb="GET" />
 <wsdl:operation name="ConversionRate">
 <http:operation location="/ConversionRate" />
 <wsdl:input>
 <http:urlEncoded />
 </wsdl:input>
 <wsdl:output>
 <mime:mimeXml part="Body" />
 </wsdl:output>
 </wsdl:operation>
</wsdl:binding>
<wsdl:binding name="CurrencyConvertorHttpPost" type="tns:CurrencyConvertorHttpPost">
 <http:binding verb="POST" />
 <wsdl:operation name="ConversionRate">
 <http:operation location="/ConversionRate" />
 <wsdl:input>
 <mime:content type="application/x-www-form-urlencoded" />
 </wsdl:input>
 <wsdl:output>
 <mime:mimeXml part="Body" />
 </wsdl:output>
 </wsdl:operation>
</wsdl:binding>
<wsdl:service name="CurrencyConvertor">
 <wsdl:port name="CurrencyConvertorSoap" binding="tns:CurrencyConvertorSoap">
 <soap:address location="http://www.webservicex.net/CurrencyConvertor.asmx" />
 </wsdl:port>
 <wsdl:port name="CurrencyConvertorHttpGet" binding="tns:CurrencyConvertorHttpGet">
 <http:address location="http://www.webservicex.net/CurrencyConvertor.asmx" />
 </wsdl:port>
 <wsdl:port name="CurrencyConvertorHttpPost" binding="tns:CurrencyConvertorHttpPost">
 <http:address location="http://www.webservicex.net/CurrencyConvertor.asmx" />
 </wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks
Farooq.

Hi Farooq,
Check if these threads can help you...
Problem with SOAP adapter
/people/thomas.jung3/blog/2005/06/05/web-services-the-case-of-the-missing-soap-action-header
*************Reward points if helpfull...***********

Japanese yen conversion

Similar Messages

Maybe you are looking for