BPC Script Logic - account mapping deliver wrong result

[Former Member]

Hi,

I want to perform a simple account mapping / Transformation. I have maintained my source accounts (Attribute A2003A2) and targets accounts (Attribute A2003A1) as attributes value in account Dimension (see Appendix "Master data"). Is it possible to map the accounts via script logic?

My script seems to be faulty and processing time is very long. Is there improvement?

[former_member186338]

Hi Alisher,

Please provide info inline with:

First - explain the logic in words...

Second - provide script text, not picture - no way to copy/paste

And in general:

To implement mapping you have to define target in some property.

Then:

*REC(EXPRESSION=%VALUE%,ACCOUNT=ACCOUNT.SOMEPROPERTY)

Vadim

[former_member186338]

Can you explain the relation matrix between ACCOUNT ID, SEGMENT and required target ACCOUNT and SEGMENT?

[Former Member]

basically there are between source accounts and target accounts no fixed relationship: M:N. The segments remain unchainged. that was the reason why I could not staple my source accounts with account ID in master data. If I concatenate the source accounts with the segment, the result is unique, but not with the target accounts.

matrix.txt.zip

[former_member186338]

Sorry, but absolutely not clear! Provide meaningful sample, please!

[former_member186338]

"The segments remain unchainged."

I don see the reason to take segment into consideration.

Looks like each account has single target account for all segments. Please correct me if I am wrong!

Vadim

[former_member186338]

Just checked your matrix - independent on segment each account has only one target account. In this case you need just a single property with target account ID, Scope all segments and write result to the ACCOUNT=ACCOUNT.TARGETACCOUNT

No FOR/NEXT!

Vadim

[former_member225135]

Hi Alisher,

The same result can be achieved through bpc delivered Account based Calculation which i think works much more faster than script logic.

Regards,

Rahul

[former_member186338]

Hi Rahul,

Mapping using property is also fast and easy to maintain if properly implemented

Vadim

[former_member225135]

Agreed

But ABC is easy to be maintained as compared to script logic.

I would prefer ABC over script for author's logic.

and one can can avoid a bit of script coding

Regards,

Rahul

[former_member186338]

You create simple script only once All changes are done by maintaining property values! To my mind it's easier then maintaining hundreds lines of ABC rule... Also using property mapping you can create Excel reports to check mapping.

[Former Member]

With the business rule unfortunately does not work because the second dimension of the source is represented by a u-type dimension.