Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

After migration from BI 7 to BI 7.3 through RSECADMIN some doubts

Former Member
0 Kudos

After migration from BI 7 to BI 7.3 through RSECADMIN, for some of the existing analysis authorizations

Version status - Active

Runtime Version - Active, Executable

but for some existing AA's

Version status - Active

Runtime Version - Inactive, Not Executable

Can anyone suggest that whether it is fine or not. And what is difference between active version and runtime version in BI 7.3?

Regards

Saurabh

1 ACCEPTED SOLUTION

shivraj_singh2
Active Participant
0 Kudos

Saurabh,

You may also want to check notes

1917777

1982399 - has a report to remove inactive authorizations

1616753

Regard,

Shivraj

10 REPLIES 10

Former Member
0 Kudos

Also after creating an AA, while activating it the system pops up with a transport request, aany idea guys?

0 Kudos

Hi Saurabh,

Yes - 7.3 requires an activation to be transported along with the analysis authorisation, both are needed for the auth to work.

Tom.

0 Kudos

Saurabh,

Analysis authorizations have changed slightly in SAP NetWeaver 7.3. An authorization is now a TLOGO object (analytic security object) and can be transported to other systems. That is the reason for the transport prompt and also for the the active status.

Regards,

Shivraj Singh

0 Kudos

Guys

Thanks for the reply, but still I have a couple of doubts.

1. Why for some of the analysis authorizations the runtime version active and some inactive. Do we need to again activate the already activated AA's and include in the transport?

2. The Migration of AA has to be done separately in each system or we can transport the same AA's from DEV system to QA and then to PRD?

Thanks for your feedback in advance.

Regards

Saurabh

0 Kudos

Hi Saurabh,

1. Yes, you need to activate the authorisation and transport the activation alongside the AA.

2. Your transports should follow the usual development path through from dev.

Tom

shivraj_singh2
Active Participant
0 Kudos

Saurabh,

You may also want to check notes

1917777

1982399 - has a report to remove inactive authorizations

1616753

Regard,

Shivraj

0 Kudos

Hi Shivraj/Tom,

One last question, the migration step we need to execute in all the systems (DEV->QA->PRD) and after that we can transport the ASO in activated version? Is the right way to proceed.

Pls suggest

Saurabh

0 Kudos

No, The migration or Upgrade happens in Dev and AAs are transported to QA & PRD.

Regards,
Shivraj Singh

0 Kudos

Hi Shivraj

Again one doubt.

After migration from BI 7 to BI 7.3, I found out that some extra AAs has been generated.

Ex - For AA Z******* a new Z*******_ got generated and it contains a different info-object from the original one.

Do you have any idea on this?

Regards

Saurabh

0 Kudos

Saurabh,

It is common to have additional AAs as result of generation process. To find the exact nature and purpose of these additional AAs you will have to open them and investigate these new AAs. Also look at the roles in which these new AAs are getting inserted. The short/long text of these AAs can also provide useful information. I am not aware of any standard logic behind generation of  these AAs, these more specific to the way previous AAs were configured.

Regards,

Shivraj