Hi!
We have two applications in one appset. In first Application PB_KeyFigure we have such dimensions:
DPB_KeyFigure (Account),
DPB_Category,
DPB_Time,
DPB_Entity,
DPB_DataSource,
DPB_Currency,
DPB_Correction (User_defined)
Second Application PB_Balance with dimensions:
DPB_Account,
DPB_Category,
DPB_Time,
DPB_Entity,
DPB_Currency,
DPB_DataSource,
DPB_Version (User-Defined),
DPB_PayType(User-Defined),
DPB_Type(User-Defined)
Accounts from DPB_KeyFigure correspond to Accounts from DPB_Account as 1:1, and sometimes one DPB_KeyFigure can corresponds several DPB_Accounts. Our business process is that users input data in Application PB_Keyfigures and than data coping into Application PB_Accounts according to dependencies of DPB_KeyFigure and DPB_Account. We develop following logic
*FOR %MY% = F01.TRAN.GR.01, F01.TRAN.GR.02, F01.TRAN.GR.03, F01.TRAN.GR.04, F01.TRAN.FAR, F01.TRAN.SUB, F01.TRAN.SER.INFRA, F01.TRAN.SER.LOK AND %ACC%= AC5110, AC5120, AC5180, AC5190, AC5210, AC5220, AC5350, AC5360
*XDIM_MEMBERSET DPB_KEYFIGURE = %MY%
*XDIM_MEMBERSET DPB_CATEGORY = Predv_PB
*DESTINATION_APP=PB_Balance
*SKIP_DIM=DPB_KEYFIGURE
*SKIP_DIM=DPB_CORRECTION
*ADD_DIM DPB_ACCOUNT = %ACC%
*ADD_DIM DPB_ACTIVITY = ACT_TRAN
*ADD_DIM DPB_TYPE = PPB
*ADD_DIM DPB_PayType = PT_FUND
*ADD_DIM DPB_Version = Ver1
*WHEN DPB_CATEGORY
*IS "Predv_PB"
*REC(EXPRESSION=%VALUE%)
*ENDWHEN
*COMMIT
*NEXT
We have more than 1,5 thousand of DPB_KeyFigures Accounts and writing such logic take a long time and doesn't effective. And difficult to change logic if dependencies between DPB_Keyfigure and DPB_Account change.
Can anybody give some advices how better organize this operation?
Thank you for help.
Best Regards,
Iaroslav