Skip to Content
0
Former Member
Sep 06, 2007 at 09:23 PM

Error converting currency to standard currency

209 Views

We've just installed standard business content for SRM Contract ODS. The standard InfoSource we installed is 0BBP_TD_CONTR_1. Two loading errors occur:

1st error:

No return value <> 0 allowed in update routines in transfer mode

Diagnosis

The return code was set to <> 0 in routine 'r0063_0SR_TARGVDC ', but the corresponding data field is updated with MOVE. You therefore can not prevent the update of a single data field for certain key values.

System Response

The load process is terminated.

Procedure

When you update with MOVE, you do not have to update all the data records. In this case you should use a start routine in the update rules in which you delete the data records that you do not want to update from table DATA_PACKAGE. Set the return code for all routines affecting a data field that is updated with MOVE to 0 (also the corresponding key field routines).

Procedure for System Administration

2nd error:

Error converting currency to standard currency (see long text!) RSBCTBBP

Diagnosis

Record number 1 : Error during currency conversion to standard currency.

The currency JPY of field 0OUTAGTARGT could not be determined.

Procedure

Possible causes are listed below:

- Could not find currency tables RSCURTRT or TCURR

- Could not determine conversion date

- Could not find an exchange rate for currency JPY in table TCURR

Check the erroneous data record, currency unit, and date.If all data is

available, check whether the standard currency was created correctly.

You can change it in transaction <rscur> by changing the settings for InfoObject 0SR_DEFCUR.

Furthermore, the global settings must be transferred from the source system in order to get the currency keys of the currencies (maintained for currency JPY in table TCURR). Use transaction <rsa1> to transfer the global settings. Select 'Source Systems' and choose the entry 'Transfer Global Settings' for the respective source system.

Note: we've transfer the global settings at currency from our SRM source system already, but we still get the same error msgs.

Any idea/solution?

Thanks