Error Conversion Currencies.

Dear Experts,
I have a failed load to the cube from ODS. The problem is the currency conversion in the update rule. The monitor details is as follows.
Data Package 1
Error conversion foreign curr. -> local curr.: 0000421784 20071008 USD -> TMZ
Error conversion local curr. -> stat. curr.: 0000501365 20080205 XZD -> TMZ
Error 2 in the update
Data Package 2
Error conversion foreign curr. -> local curr.: 0000421784 20071008 USD -> TMZ
Error conversion local curr. -> stat. curr.: 0000501365 20080205 XZD -> TMZ
Error 2 in the update
I hope someone can help me with the right ABAP or anything to resolve this in the update rule
If anyone can explain how to solve this problem, I will reword generously.
Thanx

Hi,
Check thses tables.
Table TCURR - Exchange rates
Table TCURF
Table TCURV - Exchange rate types for currency translation
Table TCUR*
Table TCURC - Currency Codes
The update of exchange rates is updating tables TCURR and TCURV. If you run at the same place the transfer of global settings, the tables TCURF, TCURS, TCURT, TCURV, TCURW, TCURX, TCURC and TCURN are updated.
For details check the programs RSIMPCUST (global settings) vs. RSIMPCURR (exchange rates).
You can maintain exchange rate factors in TCURF table via RSA1>source system>context menu (transfer global settings check only currencies)/transfer exchange rates, this updates TCURF table but also updates all currency related tables. You need to check what all tables you need to update. Also you can look into standard program RSIMPCUST to know what all currency tables will be updated.
If you want to maintain them directly in BW then go to SPRO > Genral settings and Currencies (SPRO -> Global Settings -> Currencies).
OB08 maintains the enties for currency conversion, here you can check whether the exchange rate is maintained to convert the currency from one curr to other.
this info may be helpful.
Thanks,
JituK

Similar Messages

Error during currency conversion and consistency check in a sales order

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

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

Error conversion Foreign curr. to local currency

HI experts,
Can you please let me know the solution for the below error which i found during loading Datasource
2LIS_11_VAITM for the cube sales overview
*Under :*
Data Package 1 ( 2637 Records ) : Errors occurred
Update rules ( 2637 -> 566 Records ) : Errors occurred
Data records for package 1 selected in PSA - 13 error(s)
*Record 237 :Error conversion foreign curr. -> local curr.: 0000007470 20090123 GBP -> EUR*
Please provide solution for the above error?
Thanks,
Hameed.

Hi Hameed,
check the TCURR table on both the BW and R/3 side.
Then if the GBP to EURO conversion is not maintained then make an entry in the TCURR table.
If the entry is there and not maintained then maintain with correct ratio by changing the entry.
then load the data ..
May it solve your problem..
Regards,
Ravi Kanth

Error Conversion foreign curr. (Data Records were recognised as incorrect)

hi all
I am working on SAP BW 3.5 version on Production Server
I am fetching Data from SAP R/3 system to BW 3.5 systems for SD Order and Billing
Data is correctly Loaded for SD Orders and when I am trying to Load Data for SD Billing,I am got the following Error
Data Records were recognised as incorrect, butStatus is Green
Error Request is;
Error Conversion foreign curr.- Local currency ; 0110005292 20050425 GBP - INR
Please let me know on this Error
thanks in Advance

Check currency conversion key in RRC3 transaction.The key should have defined in such a way it translates any currency

Error : enter currency when we create opportunity (default currency error).

Hi,
We did default currency as Before saving itu2019s showing error : enter currency. I redefine attribute structure.currency context node: BTPRICINGSET View : BT111h_OPPT/details component : BT111H_OPPT.and also redefine curr, currtotval and also for item attribute : currency level view : bt111h_oppt/itemlist context node : btadmini.
If I choose edit then select form list then it's getting saved and if I hit enter button on Exp. Sales volume(structure.currency) it's saving without errors. Why data is not refreshing when we save? please guide me. and implemented BADI also itu2019s not reflecting in web ui only reflecting gui.
I redefine get and set methods. Below is code
METHOD GET_CURRENCY.
*standard code
DATA: current TYPE REF TO if_bol_bo_property_access.
DATA: dref    TYPE REF TO data.
DATA: lr_collection TYPE REF TO if_bol_bo_col,
        lr_entity        TYPE REF TO cl_crm_bol_entity,
        lr_BTPricingSet TYPE REF TO cl_crm_bol_entity.
value = ''.                       "#EC NOTEXT
* get entity BTAdminI
IF iterator IS BOUND.
    current = iterator->get_current( ).
ELSE.
    current = collection_wrapper->get_current( ).
ENDIF.
* get related entity BTPricingSet
TRY.
      lr_entity ?= current.
      lr_collection = lr_entity->get_related_entities(
             iv_relation_name = 'BTItemPricingSet' ).
      current = lr_collection->get_current( ).
*     Create dependent objects
      IF current IS NOT BOUND.
        IF lr_entity->is_changeable( ) = abap_true.
          lr_BTPricingSet = lr_entity->create_related_entity( iv_relation_name = 'BTItemPricingSet' )."#EC NOTEXT
        ENDIF.
      ENDIF.
      TRY.
          dref = current->get_property( 'CURRENCY' ).       "#EC NOTEXT
        CATCH cx_crm_cic_parameter_error.
      ENDTRY.
    CATCH cx_sy_ref_is_initial cx_sy_move_cast_error
          cx_crm_genil_model_error.
      RETURN.
ENDTRY.
IF dref IS NOT BOUND.
    value = 'BTPricingSet/CURRENCY not bound'.              "#EC NOTEXT
    RETURN.
ENDIF.
TRY.
      value = if_bsp_model_util~convert_to_string( data_ref = dref
                                  attribute_path = attribute_path ).
    CATCH cx_bsp_conv_illegal_ref.
      FIELD-SYMBOLS: <l_data> TYPE data.
      ASSIGN dref->* TO <l_data>.
      CONCATENATE <l_data> '-CURR/QUANT CONV FAILED-' INTO value
                  SEPARATED BY space.                       "#EC NOTEXT
    CATCH cx_root.
      value = '-CONVERSION FAILED-'.                        "#EC NOTEXT
ENDTRY.
***custom code
value = if_bsp_model_util~convert_to_string( data_ref = dref
                                  attribute_path = attribute_path ).
if value is not initial.
value = value.
else.
clear : value.
    if value is initial.
      value = 'SGD'.
      endif.
endif.
ENDMETHOD.
METHOD SET_CURRENCY.
DATA:
    current TYPE REF TO if_bol_bo_property_access,
    dref    TYPE REF TO data,
    copy    TYPE REF TO data.
DATA: lr_collection TYPE REF TO if_bol_bo_col,
    lr_entity        TYPE REF TO cl_crm_bol_entity.
FIELD-SYMBOLS:
    <nval> TYPE ANY,
    <oval> TYPE ANY.
*   get current entity
IF iterator IS BOUND.
    current = iterator->get_current( ).
ELSE.
    current = collection_wrapper->get_current( ).
ENDIF.
* get related entity BTPricingSet
TRY.
      lr_entity ?= current.
      lr_collection = lr_entity->get_related_entities(
             iv_relation_name = 'BTItemPricingSet' ).
      current = lr_collection->get_current( ).
    CATCH cx_crm_genil_model_error .
ENDTRY.
*   get old value and dataref to appropriate type
TRY.
      TRY.
          dref = current->get_property( 'CURRENCY' ).       "#EC NOTEXT
        CATCH cx_crm_cic_parameter_error.
      ENDTRY.
    CATCH cx_sy_ref_is_initial cx_sy_move_cast_error
          cx_crm_genil_model_error.
      RETURN.
ENDTRY.
*   assure that attribue exists
CHECK dref IS BOUND.
*   set <oval> to old value
ASSIGN dref->* TO <oval>.
*   create a copy for new value
CREATE DATA copy LIKE <oval>.
*   set <nval> to new value
ASSIGN copy->* TO <nval>.
*   fill new value using the right conversion
TRY.
      CALL METHOD if_bsp_model_util~convert_from_string
        EXPORTING
          data_ref = copy
          value    = value.
    CATCH cx_sy_conversion_error.
      RAISE EXCEPTION TYPE cx_bsp_conv_failed
        EXPORTING
          name = 'CURRENCY'.                                "#EC NOTEXT
ENDTRY.
*   only set new value if value has changed
IF <nval> <> <oval>.
    current->set_property(
                    iv_attr_name = 'CURRENCY'               "#EC NOTEXT
                    iv_value     = <nval> ).
*this is code which I added
current->set_property( iv_attr_name = 'CURRENCY' iv_value = 'SGD' ).
ENDIF.
ENDMETHOD.
rose.
Edited by: rose01 on Sep 23, 2010 6:14 AM
please guide me
Edited by: rose01 on Sep 23, 2010 6:31 AM

Rose,
Try removing the custom code in GET_CURRENCY. That is not necessary. Just retain the code in SET_CURRENCY. Put break point in SET and test.

Give me details about rule details functions conversion, currency etc in bi

give me details about rule details functions conversion, currency etc in bi when creating transformation

Rule Type
Use
The rule type determines whether and how a characteristic or key figure, or a data field or key field is updated into the target.
Direct Assignment:
The field is filled directly from the selected source InfoObject. If the system does not propose a source InfoObject, you can assign a source InfoObject of the same type (amount, number, integer, quantity, float, time) or you can create a routine.
If you assign a source InfoObject to a target InfoObject that has the same type but a different currency, you have to translate the source currency into the target currency using a currency translation, or apply the source currency.
If you assign a source InfoObject to a target InfoObject that has the same type but a different unit of measure, you have to convert the source unit of measure into the target unit of measure using a unit of measure conversion, or apply the unit of measure from the source.
Constant:
The field is not filled by the InfoObject; it is filled directly with the value specified.
Formula:
The InfoObject is updated with a value determined using a formula.
Read Master Data:
The InfoObject is updated by reading the master data table of a characteristic that is included in the source with a key and a value and that contains the corresponding InfoObject as an attribute. The attributes and their values are read using the key and are then returned.
The Financial Management Area characteristic is included in the target but does not exist in the source as a characteristic. However, the source contains a characteristic (cost center, for example) that has the Financial Management Area characteristic as an attribute. You can read the Financial Management Area attribute from the master data table and use it to fill the Financial Management Area characteristic in the target.
It is not possible to read recursively, that is, to read additional attributes for the attribute. To do this, you have to use routines.
If you have changed master data, you have to execute the change run. By reading the master data, the active version is read. If this is not available, an error occurs.
If the attribute is time dependent, you also have to define when it should be read: at the current date (sy-date), at the beginning or end of a period (defined by a time characteristic in the InfoSource), or at a constant date that you enter directly. Sy-date is used as the default.
Routine:
The field is filled by the transformation routine you have written.
The system allows you to select whether the routine is to be valid for all attributes for this characteristic, or only for the attributes displayed.
Transformation rules generally only have one return value. If you select Return Table, the corresponding key figure routine no longer has a return value; it has a return table. You can then generate any number of values from a data record.
For DataStore objects and InfoObjects: you cannot use the return code in the routine for data fields that are updated by being overwritten. If you do not want to update specific records, you can delete these from the start routine.
If, for the same characteristic, you generate different rules for different key figures or data fields, a separate data record can be created for each key figure from a data record of the source.
With InfoCubes: You can also select Routine with Unit. The return parameter 'UNIT' is then also added to the routine. You can store the required unit of the key figure, such as 'ST', in this parameter. You can use this option, for example, to convert the unit KG in the source, into tons in the target.
If you fill the target key figure from a transformation routine, currency translation has to be performed using the transformation routine. This means that automatic calculation is not possible.
Time Update:
When performing a time update, automatic time conversion and time distribution are available.
Direct Update: the system automatically performs a time conversion.
Time Conversion:
You can update source time characteristics to target time characteristics using automatic time conversion. This function is not available for DataStore objects, since time characteristics are treated as normal data fields. The system only displays the time characteristics for which an automatic time conversion routine exists.
Time Distribution:
You can update time characteristics with time distribution. All the key figures that can be added are split into correspondingly smaller units of time. If the source contains a time characteristic (such as 0CALMONTH) that is not as precise as a time characteristic of the target (such as 0CALWEEK), you can combine these characteristics with one another in the rule. The system then performs time distribution in the transformation.
The time distribution is always applied to all key figures.
Initial:
The field is not filled. It remains empty.
No Transformation:
The key figures are not written to the InfoProvider.
Unit of Measure Conversion and Currency Translation
You can convert data records into the unit of measure or currency in the target transformation.
Assigning InfoObjects for Converting Amounts or Currencies
Use
An InfoObject has to be assigned to a source field of a DataSource if currencies or units of measure need to be converted. The translation types require InfoObjects as input fields to carry out a conversion. You therefore have to assign the appropriate InfoObject to the source field.
If the target has a fixed unit, you only have to assign an InfoObject if you want to carry out a conversion. Otherwise, you can select the No Conversion option.
Procedure
1.      You are in the rule details. Select the rule type Direct Assignment.
2.      Select an appropriate key figure in the InfoObject Assignment field in the Source Fields of Rule area.
3.      Choose the required conversion in the Currency field.
4.      Choose Transfer Values.
Example
In your transformation, you want to assign the AMOUNT field of the DataSource to the FIX_EUR InfoObject in your target, carrying out a currency conversion. To do so, you assign the FIX_EUR InfoObject to the AMOUNT field in the rule details so that the currency can be read from the InfoObject.
Hope this helps u...
Regards,
KK.

Error: Conversion foreign curr. - local curr when load to SD cube

Hi Experts,
I have issue regarding loading data from R/3 to SD: Sales Overview cube. After I did filling set up table and loaded it. It show errors as Error: Conversion foreign curr. -> local curr.: 0090010996 00000000 GBP -> DKK.
I have searched and found many threads about this error but none of them could fix my problem. I did try to transfer global setting and currency conversion and load but still got error.
I am wondering if any of you have had this experiece and how did you solve it?
Thank you in advace
BS

Hi Ajeet,
Thank you for your reply. I have checked mapping they are all correct.
I checked on TCURR table in R/3. Currency GBP has maintained valid from 01.01.2008.
The error occured when local currency is not the same to document currency as:
Date 03.03.2008
Local Currency     DKK
Document curreny             GBP
But There is no error if local currency = Document currency as:
Date 03.03.2008
Local Currency     DKK
Document curreny             DKK
regards,
BS

Error Transaction Currency Differs - Goods Receipt PO

Hi
I am trying to creat a goods receipt po for a overseas order which is in US $
(System Currency in AUS $)
When I try to add the Goods Receipt po i get the following error
Transaction currency differs from account or BP currency
[Goods Receipt PO - Rows- warehouse Code][line:0 ]
[Message 173-57]
Do u have any idea why am i getting this error.
thanks for the help in advance.
Sanjaya

Hi Sanjaya,
Me again, I will be more detailed this time.
The SO/PO will not be a problem as there is no Journal Entry created for those documents. For a Goods Receipt there is a Journal Entry created.
The Journal will debit Stock and credit Allocation Cost account.
The checks to be done:
- The Business Partner must be set to either multi currency or the same currency as the document.
- On the Item Master Data -> Inventory/Stock Data tab, check if the Item set to:
Set G/L Accounts by: WareHouse, Item Group or Item Level.
If it is set by Warehouse check the warehouse on the row level, if it is not already displayed use form settings to display it. Open it and check the above mentioned accounts. In this case they must be set as multi currency.
If it is set to Item Group please check the Item Group on the Item Master Data of all the Items involved in the Goods Receipt PO. Go to these Item Groups and check the above mentioned accounts. Again, they need to be set to multi currency.
If it is set to Iem Level, please use the Form Settings to display the allocation cost account and the stock account. The accounts will be displayed on the Inventory/Stock Data tab for each warehouse row. make sure that the accounts here are multi currency.
If it still does not work, in the Goods Receipt PO use form settings to display the GL account on the row level. Please make sure that for every row the account that is displayed is set to multi currency.
If there should still be problems start checking the tax accounts, after that if they are using additional expenses check those accounts as well.
This should hopefully solve it.
Thanks,
Jesper

Error Converting Currency -- Load from SAP ECC / R/3 to BW / BI

Hi,
I have a custom extractor pulling data from ECC.
However, I am getting the following error.
'Error Converting Currency from USD4 to on 8/27/2008'
RSA3 works fine. PSA load fails and the above message can be seen in the application log in ECC.
Any ideas?
Points will be assigned.
Thanks,
Edited by: Rajen SAP BI on Aug 29, 2008 2:23 AM

I believe in the transfer rule info object 0currency should be assigned with field from transfer structure which contains Currency . Once the assignment is done , delete data from info cube and reload the data and this time it should give
corresponding currency along with Amount.
Once you are able to see the currencies along with amount second step would be to create Currency translation ( RRC1 ) Put description ( Fixed Currency USD )
Tab page exchange rate : Rate type M
Source currency : From Data record
Target currency : Fixed ( USD )
Time ref. Fixed time ref. (Current datE) ( varies per scenario )
Save it.
Or
Use this function module for converting currency from one format to another format...
CONVERT_TO_FOREIGN_CURRENCY...

File Adapter: Initialization error: Conversion initialization failed

Hi all,
I'm trying to establish a file adapter (FTP, File Content Conversion).
In the adapter monitor I' ve got the following error:
Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
Configured at 14:49:34 2005-08-29
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
My content conversion parameters are:
BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
20,50,50,1,10,50,10,50,5,20,20,15,15
BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
HouseNo,PhoneNumber,Fax,BankId,BankAccount
BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
trim
BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
ignore
What could be the error or where I have to look for it?
Thanks,
Fabian

Yes,
Recordset name: BP_BusinessPartnerMasterData_IncomingData
Recordset structure: BP_BusinessPartnerMasterData_IncomingData
The corresponding Message Type:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
     <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
     <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               f323a4b018a911da9fd9000bcd69ce64
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Number">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8500fe111da89f2d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Id from Sender for BP
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name2">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8510fe111dacfd7d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Last name or Company name
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name1">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8520fe111da94bad1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         First name or Company name 2
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Gender">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8530fe111da99add1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         m or f or blank
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="1" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Birthdate">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8540fe111dab156d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="City">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8550fe111daa58cd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Postcode">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8560fe111dac0c2d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Street">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8570fe111dabbd3d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="HouseNo">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8580fe111dab63fd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="5" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PhoneNumber">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8590fe111dac782d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Fax">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85a0fe111daa9ebd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankId">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85b0fe111dace1ed1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankAccount">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85c0fe111da8801d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>

ADF error-"Row currency has changed since the user interface was rendered"

Hi,
I have created a ADf page and then created entity and view object for a table.
I have created fields which are binded to the the view object .
when i open the page after deploying it i get the following error
"Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[]"
Please help me
Edited by: 798554 on Sep 28, 2010 10:45 PM

That's a common exception in ADF. If you click the browser back button, you can get this message. You could search for a solution in other posts, perhaps like that:
JBO-35007: Row currency has changed.. when Rollback fom a Dialog page
http://cn.forums.oracle.com/forums/thread.jspa?messageID=3913201
http://programming.itags.org/development-tools/68191/
You should also mention your JDev version!
NA
http://nickaiva.blogspot.com/

ERROR :Conversion of file content to XML failed at position 0

Hi Frnds,
I have a File to File scenario, while testing I am getting the following error:
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 1 according to structure 'TA_830':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
Can any one please tell me why Iam getting this error even I have provided the following informantion in channel configuration. Here TA_830 is the record name.
TA_830.processFieldNames     fromConfiguration
TA_830.fieldNames     SEG_NUM,PROCESS_DATE,PAYEE_BCODE,ISSUE_SEQ_NUM,CR_DATE,PAYER_BCODE,PAYER_ID,ENTRY_SEQ_NUM,TRAN_TYPE,PAYMENT_TYPE,PROCESS_FLAG,REF_NUM,PAYER_ACC,VAL_DATE,ISO_CURRENCY,AMOUNT,RESV_11,SEG_NUM,EXCHG_RATE,ADDR1,ADDR2,ADDR3,ADDR4,RESV_18,SEG_NUM,BANK_ID,BANK_CODE,ADDR1,ADDR2,ADDR3,ADDR4,RESV_5,SEG_NUM,ACCOUNT,ADDR1,ADDR2,ADDR3,ADDR4,RESV_6,SEG_NUM,MESSAGE1,MESSAGE2,MESSAGE3,MESSAGE4,RESV_6,SEG_NUM,MESSAGE1,MESSAGE2,MESSAGE3,MESSAGE4,RESV_6,SEG_NUM,PROCESS_DATE,PAYEE_BCODE,ISSUE_SEQ_NUM,CR_DATE,PAYER_BCODE,PAYER_ID,ENTRY_SEQ_NUM,TRAN_TYPE,PAYMENT_TYPE,PROCESS_FLAG,TOTAL_AMOUNT,RESV_59
TA_830.fieldFixedLengths     2,6,12,5,6,7,5,5,3,1,1,16,24,6,3,15,11,2,12,24,24,24,24,18,2,1,24,24,24,24,24,5,2,24,24,24,24,24,6,2,30,30,30,30,6,2,30,30,30,30,6,2,6,12,5,6,7,5,5,3,1,1,16,59
TA_830.fieldContentFormatting     nothing
Regards,
Shiva.

Hi,
As you are using Fixed Length File...use below specified parameters:
TA_830.fieldName:          Names of Fields in teh File
TA_830.fieldFixedLegths: Lenghts as per your file
TA_830.keyFieldValue:    If you use any value as key
TA_830.lastFieldsOptional: YES
TA_830.endSeparator :        'nl'
This will help you out..
Thanks,
Kishore.

Error: Conversion of complete file content of 'filename here' to XML format

"Error: Conversion of complete file content of 'filename here' to XML format failed"
We process inbound files every hour, we now got this message we have never seen. But every hour, for three hours, one in many files that are processed get this error. But the file ends with success, and after spot checking the file looks like it made it into SAP.
What is happening? Anybody know?
Thank-You.

hey
did u see any adapter with red button?
i m pretty sure there will some sender adapter with red button(meaning error)
also whatever message failed,can u copy that payload from sxmb_moni and test the message mapping under test tab in IR
thanx
ahmad

Error: Transaction currency differ from Account or BP currency

Hi all
While adding Goods Receipt PO I am getting this error "Transaction currency differs from account or BP currency-Goods Receipt PO"
For your information I am using Foreign Vendor dealing in UD Dollar and following setting in Basic Settings:
1)Local currency = Indian Rupee
2)System Currency= US Dollar
3)Default Account Currency = All Currencies
PLz solve the issue.
Kush

Hi Khushwant
Check the related G/L accounts are set to multi currency. In this case Trading Stock and Allocation Account. If you are using Freight charges (Additional Expenses) then check their G/L accounts too.
Kind regards
Peter Juby

Foreign conversion currency posting

Dear ALL
In my Client place when they purchase in export orders they billed the goods in the current foreign currency rate for example use 46.20 when they issue the payment to vendor through bank cheque payment that time the foreign currency rate may be higher or lower value . for this process how to make accounted the difference loss amount what are the entries and valuation conversion currency process what we have to do. Pl guide to do this process.
Regards,
Girija

Hi,
You have to maintain Exchange rates for different types in OB08 as per your requirement.
Also while posting invoice you can put the different excange rate from the one maintain in OB08 for particular Invoice provided the exchange rate difference is within the tolerance limit.
Then you have to define G/L accounts for Automatic account assignment is FBKP -- Automatic Posting - Exchange Rate Difference.
So, while making payment system will automatically calculate Gain/Loss due to exchange rate difference & will post the same to these G/L accounts.
Regards,
Sheetal

Error Conversion Currencies.

Similar Messages

Maybe you are looking for