Characteristic /ERP/GL_ACCT for Embedded BPC

[Former Member]

In Embedded BPC, the Characteristic "/ERP/GL_ACCT" was used as the account dimension.

However, I notice that it only one attribute and does not include all the attributes which is included in standard BPC such as ACCTYPE, RATETYPE etc,

If there is currency translation is need in the planning model, how could the system know which rate should be applied since there is no RATETYPE in the account dimension?

[lucas_costa3]

Hi Jian,

In Embedded you need to set up a Currency Conversion Planning Function. It works quite different then the business rule for standard model and it supposed to work more seamlessly with ERP settings. For instance you can set the currency translation type to use the mechanism being used in FI .

Take a look at T-code RSCUR for the currency translation type.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0d5bf96-b19b-2c10-e3b6-e2f12a3de...

Cheers,

Lucas

[Former Member]

Do you mean that in Embedded BPC, we do not use business rule to do the currency translation? However there is still currency translation business rule I Embedded BPC.

[Former Member]

Hi Jian,

The currency translation rule was added when the consolidation functionality was added to BPC Embedded in SP09.

I have yet to make it work, the complete lack of documentation makes working with it a challenge.

From what I know, there seems to be two different ways to do currency conversion:

1. the IP way

2. A BPC way, which needs it's own rates cube, and then works using business rules.  For this way you need all the properties that you needed in standard such as ACCTYPE, RATETYPE.  You then run the conversion from the consolidation monitor.  Though debugging is a bit of a problem, as the only feedback from here is "failed".  No log or indication why it failed.

Regards,

Mark

[lucas_costa3]

As Mark said the BR is available from SP09, but only for consolidation models that basically will utilize the standard environment engine. Check note: 2240898

If you have another planning models you'll need the use approach I gave in the previous post.

Cheers,

Lucas