cancel
Showing results for 
Search instead for 
Did you mean: 

authorization error running a package

Former Member
0 Kudos

Hi Bpc Friends

An user run a package that call the below script

*RUN_PROGRAM CALC_ACCOUNT
CATEGORY = %CATEGORY_SET%
CURRENCY = LC,GBP,USD
TID_RA = %TIME_SET%
OTHER = [ENTITY=%ENTITY_SET%;GROUPS = G_NONE;DATASRC = T_COMP]
CALC = CF010
*ENDRUN_PROGRAM

*COMMIT

He got the following error:

but he doesn't need the access to datasrc=MJ_GSALLOC, the script specified datasrc=T_COMP and T_COMP doesn't include MJ_GSALLOC

Accepted Solutions (1)

Accepted Solutions (1)

former_member186338
Active Contributor
0 Kudos

For CALC_ACCOUNT you can't use in OTHER the dimensions used in the rule setup (like ACCOUNT, DATASRC, FLOW...).

Simply create new rule with source audit = T_COMP

Former Member
0 Kudos

thanks Vadim but I don't understand why other users that have the same write access to T_COMP don't get that error

Former Member
0 Kudos

Vadim I have a question, instead of changing the business rule, could I change the script logic specifying datasrc in the following way:

*XDIM_MEMBERSET DATASRC= bas(T_COMP)

*RUN_PROGRAM CALC_ACCOUNT
CATEGORY = %CATEGORY_SET%
CURRENCY = LC,GBP,USD
TID_RA = %TIME_SET%
OTHER = [ENTITY=%ENTITY_SET%;GROUPS = G_NONE]
CALC = CF010
*ENDRUN_PROGRAM

*COMMIT

former_member186338
Active Contributor

"same write access to T_COMP don't get that error" - something is not the same 🙂

In general the setting

DATASRC = T_COMP]

will be ignored. And the rule will process based on

audit (datasrc) = CUP_IFRS

Former Member
0 Kudos

thanks Vadim.

What do you think if instead of changing the business rule I will change the script logic as below

*XDIM_MEMBERSET DATASRC= bas(T_COMP)

*RUN_PROGRAM CALC_ACCOUNT
CATEGORY = %CATEGORY_SET%
CURRENCY = LC,GBP,USD
TID_RA = %TIME_SET%
OTHER = [ENTITY=%ENTITY_SET%;GROUPS = G_NONE]
CALC = CF010
*ENDRUN_PROGRAM

*COMMIT

former_member186338
Active Contributor

*XDIM_MEMBERSET has no effect on *RUN_PROGRAM CALC_ACCOUNT

Please create a new rule!

Former Member
0 Kudos

thanks Vadim, I need the approval from Finance

What about the following:

*SELECT(%datasrc%,[ID],DATASRC,ID=bas(T_COMP))

*RUN_PROGRAM CALC_ACCOUNT
CATEGORY = %CATEGORY_SET%
CURRENCY = LC,GBP,USD
TID_RA = %TIME_SET%
OTHER = [ENTITY=%ENTITY_SET%;GROUPS = G_NONE;DATASRC =%datasrc%]
CALC = CF010
*ENDRUN_PROGRAM

former_member186338
Active Contributor

I have told you already that DATASRC in OTHER has NO effect!

Third time - create a new business rule!

Former Member
0 Kudos

thanks

I though that it was necessary to specify base members

former_member186338
Active Contributor

Base members has to be used in OTHER, but for dimensions like ENTITY, INTCO, userdefined etc.

Answers (1)

Answers (1)

former_member186338
Active Contributor
0 Kudos

Rule screenshot missing!

And T_COMP is a parent member, what do you mean by

OTHER = [...DATASRC = T_COMP]

Only base members can be used in other!

Former Member
0 Kudos

thanks Vadim for your answer

I mean tom call the program calc_account for dimension DATASRC=T_COMP

all the rows for this business rule have source audit (datasrc) = CUP_IFRS and destination audit (datasrc) blank

former_member186338
Active Contributor

Please explain you DATASRC structure!

How CUP_IFRS is related to T_COMP?

Just create another rule with source audit = T_COMP

Former Member
0 Kudos

CUP_IFRS is the parent, MJ_GSALLOC and T_COMP are descendant and T_COMP has a number of leaves