on 10-26-2011 6:12 PM
Hello All,
Three quick questions on BC sets if anyone can help me with:
1. Do we activate the BC sets in GRC PRD system or transport them from QAS. The guide says transport them but our Basis team activated them directly in PRD. Is there any risk in activating them directly in PRD? Though I have checked they activated the relevant ones only.
2. Is there any negative impact on the system having all the BC sets activated even though we do not need some of them?
3. Can the BC sets be de-activated once they are activated, in case we do not need them or activated them by mistake and realise we do not need them.
Thanks a lot.
Hi Guys,
Can anyone please help wtih this one?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please find below my comments below your question.
1. Do we activate the BC sets in GRC PRD system or transport them from QAS. The guide says transport them but our Basis team activated them directly in PRD. Is there any risk in activating them directly in PRD? Though I have checked they activated the relevant ones only.
My Comments: SAP recommends: BC Sets can only be activated if there is no production client in the system. Please note that: Activating a BC Sets copies all data from the BC Set into the original tables. The existing entries in the original tables are overwritten. So BC Sets should only be activated if there is no production client in the system. Otherwise it might create inconsistencies in the system.
2. Is there any negative impact on the system having all the BC sets activated even though we do not need some of them?
My Comments: In most cases there is no negative impact but why' are you going to activate everything even if you don't require them?
3. Can the BC sets be de-activated once they are activated, in case we do not need them or activated them by mistake and realise we do not need them.
My Comments:I don't think You'll be able to do so. It is just like applying patch and you want to downgrade to a lower patch.If you'll try to find some way and try out, definitely it'll create lot of inconsistencies in the system. So I'll advise not to do any experiment like this with the Prod system.
Thanks,
Guru
Hi Guru,
Thanks for the reply. However I am not sure I got the first answer correctly. I'll put it like this:
I have activated the relevant BC sets in my Development box. Should I transport these to my PRD box or should I again go to the Production Box and activate them, like I did in Development box?
Cheers.
Hi
As far as I am aware, as most of the settings are transportable, there is nothing wrong with the approach of transporting your customised settings of the BC sets to the other systems. Usually a transport would get created when a BC set is activated. I am assuming your prod system is locked down for config.
Good luck
Hi,
When you have activated the BC sets in your Development box, it must have asked you for creating a transport request. So you need to just export the Transport request(s) from your dev and import into your PRD box. You shouldn't activate them in PROD system. I hope you get it this time. Go ahed and import the Transport Request. Good Luck.
Regards,
Guru
Hello Kaushal,
I tried transporting the BC set transport request created in Development system into our QA system and it ended with an error RC = 8
When i checked the transport log it showed me the following error :
It shows error below this line
start import R3TRCDATVC_GRFN_MSMP_WORKFLOW
1 duplicate key error during insert into table GRFNMWCNRULEID occured
End import R3TRCDATVC_GRFN_MSMP_WORKFLOW (with warnings)
Further logs showed
1 entry for GRFNMWCNRRESLT merged (400EIFGRAC_USERACCRVW_INITIATOR GRAC_DEFAULT_RESULT); as part of view V_GRFNMW_ACRES
E071-LOCKFLAGs 000018 - 000036 updated ('2', 19 entries).
102792 32436212
When i checked if BC set was activated or not
BC Set: GRAC_ACCESS_REQUEST_APPL_MAPPING it said
Has the BC Set already been activated in the current client? No
Along with the following comment
GRACAPPLMAPPING Checked activation of data for object GRACAPPLMAPPING not allowed for techn. resons
I also did the "Key Conflict Check" in GRD & GRQ but it said "There are no Key conflicts"
I also compared the Table: GRFNMWCNRULEID in GRD it contained 68 values ( 7 of which are custom rules e.g) custom agent , custom initiator)
whereas in GRQ it showed 61 values (all standard agents, initiator agents etc)
Should i manually "activate" this BC set in QA system ?? or How can i fix this error ??
Thanks in advance.
Regards,
Victor
I also have questions about transporting BC Sets. I did transport to production the change request generated by the activation step in development, but now the number of entries in tables differs between development and production. Wondering if I need to "fix" by activating in production and how this has gone for other brave transporters who have gone ahead of me on AC10.0.
Thanks,
Heraleen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.