cancel
Showing results for 
Search instead for 
Did you mean: 

Use one dimension to feed 2 other dimensions

Former Member
0 Kudos

Is there a way to use one dimension to push data into two other dimensions using push logic? The client has one dimension in App1 that is a combination of 2 dimensions in App2 ie the Costcenter dimension in App1 is a combination of Plant and Account in App2.

Now they want to push data from App1 into App2 using the Costcenter dimension to populate the Plant and Account.

I have Plant and Acct properties in the Costcenter dimension for mapping.

I tried to use *Rename_dim CC= CC.Plant and *Rename_dim CC=CC.Acct but would get errors when validating the logic script.

Any help would be greatly appreciated.

Accepted Solutions (0)

Answers (3)

Answers (3)

sorin_radulescu
Employee
Employee
0 Kudos

Yes you are right.

I understood your problem now,

Actually you need Rename twice.

What was the error message received when you tried to validate the logic?

Regards

Sorin Radulescu

Former Member
0 Kudos

Parameters

COSTCENTER: 70101014

When I test the logic using the logic debugger, I get the error:

Validate member failed:

70101014

70101014

70101014

70101014 on COSTCENTER dimension

When I run the logic thru data manager, the package is successful but the end of the detail status log is 'No records to process'

The push logic should ideally take the Costcenter 70101014 from App1 and take the first 4 char (7010) and record to the Plant dimension in App2 then take the last 4 char (1014) and record to the Account dimension in App2

Logic script:

*DESTINATION_APP= APP2

*RENAME_DIM CC = ACCOUNT

*RENAME_DIM CC= PLANT

*WHEN CATEGORY

*IS "AOP"

*REC(CC=CC.RPT_A,CC=CC.PLANT,CATEGORY=AOP)

*ENDWHEN

*COMMIT

Former Member
0 Kudos

Does anyone have any suggestions to help me with this issue?

sorin_radulescu
Employee
Employee
0 Kudos

The problem is the fact that you are using Rename.

You can use Rename for one dimension but for the other one you have to use ADD not one more time rename.

Regards

Sorin Radulescu

Former Member
0 Kudos

If I cannot use Rename for the other dimension, how can I use ADD and have it refer to the property needed to populate the Plant dimension in App2? Doesn't ADD mean hardcoding one member ID?

Former Member
0 Kudos

Hi,

Assuming that each CC member in App1 corresponds to single specific Plant-Account intersection I'd suggest using CC dimension properties PLANT and ACCOUNT.

The you could use *REC instruction with %CC%.PLANT and %CC%.ACCOUNT parameters to populate that particular interserction using the value of current CC member.

Hope this helps,

Madis

Former Member
0 Kudos

The Plant and Account dimension does not exist in App2.

I did try using the properties in the *REC but got errors that Plant is an invalid dimension in lookup rule.

*REC(CC=CC.RPT_A, PLANT=CC.PLANT)