Skip to Content
0

DESTINATION_APP mapping member from different accounts and models based on their properties

Jan 19 at 02:27 PM

49

avatar image

Hi gurus,

I have this particular scenario with a Destination_App logic case I am moving data from SOURCE to TARGET Model A to Model B the tricky part is that the dimensions are not the same.

The Requirement:

I need to send data from Source Model to Target Model using DESTINATION_APP but the members coming from the one Source Model Dimension JOB_CODE need to be filtered by a property "PARENTH1 = IUP" and its records "mapped" or moved to a Target Model MPU_UNIT Dimension in which the "only" members that should be affected are the ones which "ID" property is matching with "DESC" property of the incoming members from JOB_CODE from the Source Model.

The question:

Is this possible?and if so, would my code work satisfied the requirement? Thanks in advance.

Dimensions in Source Model

Dimensions in Target Model

*XDIM_MEMBERSET AUDIT_TRAIL = RATE_NPD,RATE_DBP,RATE_DDF
*XDIM_MEMBERSET CURRENCY = LC
*XDIM_MEMBERSET POSITION_ID = PINR
*XDIM_MEMBERSET POSITION_TYPE = PTNR
*XDIM_MEMBERSET MEASURE = PERIODIC
*XDIM_FILTER JOB_CODE = [JOB_CODE].PROPERTIES("PARENTH1")="IUP" 

*DESTINATION_APP = MPU

*ADD_DIM MPU_COMP = CCNR
*ADD_DIM MPU_COST = MSA
*SKIP_DIM = ORG_UNIT
*SKIP_DIM = POSITION_ACTION
*SKIP_DIM = POSITION_ID
*SKIP_DIM = POSITION_TYPE

*RENAME_DIM JOB_CODE = MPU_UNIT

*WHEN TIME 
*IS *
*REC(EXPRESSION=%VALUE%,JOB_CODE=JOB_CODE.MPU_UNIT) 
*ENDWHEN 

*COMMIT
position-model.png (24.0 kB)
mpu.png (22.2 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Vadim Kalinin Jan 19 at 03:12 PM
0

Do you need an answer?

Then please, prepare your question in line with: https://blogs.sap.com/2014/01/31/how-to-ask-questions-about-script-logic-issues/

Please don't include commented code!

Please use correct line breaks!

Show 7 Share
10 |10000 characters needed characters left characters exceeded

Yes, I guess my question would be; If it is possible to use the property filter for *RENAME_DIM for the Source Dimension and for the Target Dimension as well, since I only need the records with "X" property to be affected in Target Source?

0

Sorry, I do not understand you!

Please read again: https://blogs.sap.com/2014/01/31/how-to-ask-questions-about-script-logic-issues

Provide examples of dimension members and property values!

*RENAME_DIM is just rename dim - nothing more...

You can use property in the source dimension, not in target

0

P.S. Provide screenshots of source and target dimensions administration pages.

Explain the logic to be implemented.

0

Hi Vadim,

I updated the question and the content, I hope that adds a little more clarity to my situation. Thanks

0

Still not clear!

Have to repeat: "Provide screenshots of source and target dimensions administration pages."

JOB_CODE (with DESC property visible) and MPU_UNIT

Strange idea to filter PARENTH1 = IUP

Why not *XDIM_MEMBERSET JOB_CODE=BAS(IUP) ????

0

*XDIM_MEMBERSET JOB_CODE=BAS(IUP) I guess I could use that instead.

We are trying to map the members that will received data from source model to target model useing the *DESTINATION_APP

0

Third time:

Have to repeat: "Provide screenshots of source and target dimensions administration pages."

JOB_CODE (with DESC property visible) and MPU_UNIT

????

0