cancel
Showing results for 
Search instead for 
Did you mean: 

Currency Conversion of AS_IS Accounts with ENTITY_FX Taking Place

Former Member
0 Kudos

Hi - We are running BPC 10 NW, SP 9.

We have one company for which no currency conversion takes place.  For this company, we've designated it with a unique FX_TYPE, and in our currency conversion business rules, we've specified [AS_IS] for this Entity FX type.  For this company, we load directly in USD and CAD.  For AUDITTRAIL members where IS_CONVERTED is set to "G", this works fine where for any account (irrespective of RATETYPE) it goes from USD/G_NONE to USD/G_XXX when currency conversion is run.  And likewise for CAD.

However, for AUDITTRAIL members that have a IS_CONVERTED value of "Y", these USD and CAD amounts disappear and don't move up the consolidation hierarchy when currency conversion is run.  The values simply disappear.

I thought that having [AS_IS] for a given Entity FX Type means that group currency values go from G_NONE to G_xxxx, yet I'm not seeing this.  What am I missing or with version 10 NW is there something else that needs to be done, e.g., a property, etc.?

Accepted Solutions (0)

Answers (4)

Answers (4)

ricardo_honda
Discoverer
0 Kudos

Hi Karthik Natarajan,

We are using [AS_IS] to assign group dimension, as we already have transactional data in USD (instead of LC).

We were facing some issues in currency conversion, which were solved by note 1682227. Please check the following link.

http://scn.sap.com/thread/3355482

ps. in IS_CONVERTED property (Audit dimension), we are using "Y" for all members that need to be considered in Currency Conversion - for all the other members, we left them blank..

Hope it helps..

Best regards,

Ricardo

Former Member
0 Kudos

Hi Karthik,


I thought that having [AS_IS] for a given Entity FX Type means that group currency values go from G_NONE to G_xxxx, yet I'm not seeing this.  What am I missing or with version 10 NW is there something else that needs to be done, e.g., a property, etc.?

[AS_IS] basically means that no conversion from LC to a reporting currency (such as USD or CAD) takes place but that the system uses values entered directly in this reporting currency.

BR,

Arnold

Former Member
0 Kudos

Thanks Arnold.  However, I'm trying to keep the values of CAD and USD loaded into the system via AS_IS for this company - I use the FX_TYPE to filter and keep it as such, but it doesn't appear to be working.  And even for other companies where an account is set to NOTRANS (AS_IS), if the AUDIT member in which USD and CAD data exists at unconsolidated SCOPE, once currency conversion happens, the data gets wiped out.

Former Member
0 Kudos

Hi Karthik,

Are USD and CAD members of your currency dimension with CURRENCY_TYPE = R? And are you running a currency conversion as

*RUN_PROGRAM CURR_CONVERSION

CATEGORY=%CATEGORY_SET%

CURRENCY=%CURRENCY_SET%

TID_RA=%TIME_SET%

RATEENTITY=GLOBAL

*ENDRUN_PROGRAM

Then [AS_IS] should leave those values untouched.

BR,

Arnold

Former Member
0 Kudos

Hi Karthik Natarajan,

  1、Fx_TYPE is used to select entity specific currency translation parameters in the business rule tables via the Entity FX Type column(from BPC440). not what you thoughts.

2、 If  AUDITTRAIL member property 'IS_COVERTED' be set as Y, it means the currecy translation converte these data from LC not reporting currency to group currency. For your question, I think USD and CAD may be reporting currency. so these data will not be converted into group currency.

Message was edited by: Harry Liu

Former Member
0 Kudos

One follow up item - for our ACCOUNT dimension, certain members have a RATETYPE of "NOTRANS" which in our currency conversion rules corresponds to [AS_IS].  And this is true for these accounts, regardless of the entity.  And yet for NOTRANS accounts for all companies, when currency conversion is run, the values disappear.  They're all in G_NONE, but don't go up to G_xxxx.

Former Member
0 Kudos

add a new rule like below show and try it again

rule id : NOTRANS

forluma column: COPYLC

others columns retain blank.

Former Member
0 Kudos

Hi Henry - My issue with COPYLC is that it will copy LC to CAD (one of the reporting currencies), but what about the USD amount already in place?  It needs to also copy over the USD amount.  But it cannot retranslate anything.

Former Member
0 Kudos

COPYLC just means copying values from LC to group currency by factor 1.

I have a question why you load data in USD and CAD on the same entity?

if you want to convert data to two group currency, you just need add these currency to the Group dimension's property Group_currency,and set the entity's curreny property by using its local curreny. then the data will be translated into USD and CAD and copy to the group level.

about [AS_IS], please see the illustrate below

N-1:

    LC:USD=1:2

   act1 using [END]

   act2 using [AS_IS]

entity    currency          account     signeddata

E1            LC                      act1    100

E1            LC                      act2    200

after currecy translation

entity1    currency          account     signeddata

E1            LC                         act1    200

E1            LC                         act2    400

N:

LC:USD=1:2.5

entity1    currency          account     signeddata

E1            LC                         act1    200

E1            LC                         act2    300

after currecy translation

entity1    currency          account     signeddata

E1            LC                         act1    500 (200*2.5)

E1            LC                         act2    650 (400+100*2.5)

650= 400+100*2.5  ----for 400,copy from the last period of last year

Hope it's clear for you usderstanding

Former Member
0 Kudos

Harry - in this entity, we don't convert anything.  We report in both USD and CAD, which are group currencies and we bring both into BPC.  Whether it's from SAP or journal entries, but none of these values are to be converted, irrespective of AUDIT, which is why we've set to AS_IS (NOTRANS).  But each time the currency translation occurs, USD and CAD data get wiped out.