SPRO settings in production?

Question

Hi,
May i know whether we can do SPRO settings in Production system???
I had done some setting in Dev system and transported those objects to production!!!
But still some functionalities are missing for those objects!
has anyone done SPRO settings in production???
Raj

Answer 1

Hello Raj,
As you are saying that some of the functionality are missing in SPRO in production client, the reason behind this is:
The settings in production system are different then in dev/quality/test.
There is a concept of enhancment IDs and Switches/BC-set in IMG structure( hope you are aware of that), now based on the status of enhancment IDs or switches the node is displayed or hidden, the enhancment IDs or Switches might be active in dev/quality/test system but there are posibility that the same is not active in production system.
The steps to activate a switch in production system is entirely different then in dev/quality/test system
Some background information concerning BC Sets. They are
basically containers for customizing data - table entries. When a BC
Set is activated in a particular client/system, the table contents are
written into the Database (created for first time, or overwrites the
existing data). For this activation - the SCPR20PR logs give you the
status.
When it comes to a Productive client, BC Sets cannot be activated - for
security reasons. Hence, if we need customizing data from a BC Set into
a Productive client, it is always transported from a Dev or Quality
system. But, the Activation logs (SCPR20PR) in the Productive client
does not recognize any Transports. So, the logs continue to show only
the information which is particular to the Productive local client -
1) No logs if BC Set was never activated (or)
2) Error message if the client role was Productive.
This will continue to be the case, even if the BC Sets were activated
successfully in the DEV system, and transported to the Productive
client. Why ? The reason is that the transport request simply contains
Table entries.
It does not contain any Log information that can be updated into the
Productive Client.
So in future, where ever a BC Set has to be activated in the Productive
client, one must activate them in DEV/TEST system and transport them.
The logs in the productive client will continue to be unchanged even
after this transport is imported. But the required Data will be
successfully present on the Productive client already.
As mentioned remember that activation of BC Set cannot be
done in prodcution system directly.  The process to follow in order to
activate a BC set in production system is to transport the activation
data from the DEV or QA system.
Follow these steps:
1. Log on to your DEV system.
2. Set the client settings to Automatic Recording of changes (in SCC4
   transaction).
3. Goto transaction SCPR20 - - BC Set activation.
4. Activate the BC Set.
A pop up to enter the request number will be displayed.
5. Record the activation data in the request.
6. Release this request and import this request into the production
   system.
Now the activation data will be updated in the production system.
The IMG nodes, menu nodes will be visible in the system.
Hope the information is usefull.
please reward points.
Regards
Mayank