BC Sets Lessons Learned

[Former Member]

Hello Everybody,

we are targeting to using BC Sets for a global rollout project. There will be several successive versions of the template.

We have a rough knowledge of BC Sets, we know how to create, activate or check them but we are lacking of experience of how to structure the bc sets apropriatelly to ease the activation and to avoid running into problems when delivering 3rd, 4rth, etc. version.

Can sombody provide me with lessons learned, what is must do what is to avoid?

Do sombody have experiance wit the rest of the customizing which is not bc set compatible and must be delivered together with the bc set package?

thank you all in advance

greetings

roland

[Former Member · Accepted solution]

Hi Roland,

The benefit of the capturing the IMG settings in BC set is for easy re-usability.

So the BC set should be created with the proper naming convention to uniquely identify the business process.

Let us consider some example.

You are doing R/3 implementation. Your company has 75 plants spreading across three company codes.

Out of 75 plants, your pilot lot golive will only for 20 plants. You have gone live with 20 plants. remaining 55 plants yet to go live.

All your configuration settings has been captured in BC sets.

The name of the BC sets are:

1. Z_SD_ORD_PROCESS---Sale order processing for FG

2. Z_MM_SUB_PROCESS---Sub contractor material processing

3. Z_PP_ORD_PROCESS----Production order processing for Semi finished goods.

Now by seeing the name of the BC set we can understand, what kind of IMG settings it contains. (Naming BC set is very important---the BC set should be process centric)

So pick the relevant BC set & active it in your remaining rollout plants.

Note:

You can parameterize the BC set values when you activating the BC sets in rollout plants

Regards

Senthil

[Former Member · Accepted solution]

Thank you Senthil for the reply, this is a good aspect. but we expect the situation that we have e.g. Z_MM_SUB_PROCESS delivered, and soon we develop Z_MM_SUB_PROCESS_01.

In this new Version we have

changed fileds

new fields

deleted fields

what have to be done by the local implementation to avoid troubles. Where is the advantage to the normal transports.

regards

roland

[Former Member · Accepted solution]

Dear Roland,

To avoid local troubles, do NOT keep so many versions of BC sets for same process.

If you have so many versions of BC set for same process, if u activate one BC set, the previous BC set values will be overwritten.

The advantage over normal transport is:

In normal transport request, once you released the transport request, u can not retain the old values until otherwise you create one more transport request.

But in BC set, with one BC set you can keep on overwrite the IMG settings. So number of transports will get reduced.

Regards

Senthil