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: 

CUA(SAP Solution Manager 7.0) is not compatible to Child system.Child system is upgraded to BI 731

Former Member
0 Kudos

Hi,

I am unable to update user from cua to child system after child system got upgraded to BI 731.

I have reconfugured cua  but unable to create user,assign role in child system and also when cua got reconfigured other issue in child system is password reset got runtime issue.

CUA(SAP Solution Manager 7.0) is not compatible to Child system.Child system is upgraded to BI 731

In CUA System componets:

SAP_BASIS 700 0016 SAPKB70016 SAP Basis Component

SAP_ABA 700 0016 SAPKA70016 Cross-Application Component

PI_BASIS 2006_1_700 0006 SAPKIPYM06 Basis Plug-In (PI_BASIS) 2006_1_700

ST-PI 2008_1_700 0008 SAPKITLRD8 SAP Solution Tools Plug-In

SAP_BW 700 0018 SAPKW70018 SAP NetWeaver BI 7.0

SAP_AP 700 0012 SAPKNA7012 SAP Application Platform

BBPCRM 500 0012 SAPKU50012 BBPCRM

CPRXRPM 400 0013 SAPK-40013INCPRXRPM SAP xRPM/cProjects/cFolders 4.00 (ABAP)

ST 400 0017 SAPKITL427 SAP Solution Manager Tool

ST-A/PI 01Q_700 0001 SAPKITAB7K Servicetools for other App./Netweaver 04

ST-ICO 150_700 0015 SAPK-1507FINSTPL SAP Solution Manager Implementation Content

ST-SER 700_2008_1 0004 SAPKITLOO4 SAP Solution Manager Service Tools

VIRSANH 530_700 0016 SAPK-53316INVIRSANH SAP GRC Access Controls 5.3 for 700 HR a

In Child System:

SAP_BASIS 731 0008 SAPKB73108 SAP Basis Component

SAP_ABA 731 0008 SAPKA73108 Cross-Application Component

PI_BASIS 731 0008 SAPK-73108INPIBASIS Basis Plug-In

ST-PI 2008_1_710 0008 SAPKITLRE8 SAP Solution Tools Plug-In

BI_CONT 747 0005 SAPK-74705INBICONT Business Intelligence Content

SAP_BW 731 0008 SAPKW73108 SAP Business Warehouse

ST-A/PI 01Q_731 0000 - Servicetools for SAP Basis 731

VIRSANH 530_731 0000 - SAP GRC Access Controls 5.3 for 731

Please let me know any solution.

Thanks

Mir

2 REPLIES 2

Former Member
0 Kudos

Hi Mir,

SAP recommends that the CUA central system is at the same release of the highest child system or an equivalent patch level. See the CUA FAQ. From the data you posted, I would assume that your CUA is a lot elder than the 7.31 SPS08 of your child. To my understanding the equivalent SPS for 7.00 is SPS29. As there had been numerous changes especially inthe security functionlity, like the introduction of security policies for users, it might simply be, that you need to upgrade your CUA master to a later SPS as well or even better put it on 7.31.

Regards,

Patrick

holger_biber
Explorer
0 Kudos

Dear Mir,

a CUA central system having SAP_Basis release 7.00 should even though be able to connect child systems having higher releases like 7.31, but ...

  1. We recommend using the highest possible SAP_Basis release for the CUA central system as only this grants the support of all new features for all child system releases.
    Example:
    The 7.00 central system is not able to support the salted hash and Security Policies what a 7.31 will do.
  2. If point 1. isn't possible we strongly recommend to install at least this Support Package at the CUA central system fulfilling the equivalence level to the newest SP of all your child systems.
    (In your special case this isn't given as SAPKB73108 is available since April this year and SAPKB70016 was as of April 2008. The current available SP for 7.00 is SAPKB70029!)

For password issues regarding child systems, please, also check for related notes e.g.:

1300104, 1301479, 1306019 (subsequent: 1325775 & 1636845) or 1879283.

If you have:

  • checked and installed all necessary corrections
  • deleted the 7.31 child system from CUA using report RSDELCUA in central and child system
  • cleaned up the BD64 in child system
  • attached the child system newly by using transaction SCUA once again

and the issue still persists I would prefer to handle special issues in a customer message.

Best Regards,

Holger