Master data attribute added and transport

[Former Member]

Dear Experts

I have added a few attributes to a master data object. Its a standard business content like 0xxxxxx infoobject.

When I changed added attributes, many transformations and DTPs were de-activated.

I am seeking your advise what is the best practice to handle the transportation of such change to production such that i will know exactly what are all the de-actived objects so that i can re-activate them and ensure production is unaffected adversely.

What i know is when changing the master data, upon reactivation, there is a list of de-activated objects shown. Is this info sufficient and is there any order i need to follow when re-activating the affected objects?

I am not totally familiar with all the stuff in production and worry that i may miss somethings causing problems i cannot detect.

Could you share with me how you normally go about such changes?

Thanks.

regards

Pascal

[Former Member · Accepted solution]

Hi

Changing a Master data object affects the Transformations and respective DTP's associatd with it and Mutliproviders/Infosets build directly on top of it. cubes and ODS wil not have effect I supose.

If you have done the changes already in development system , check the where used list of Master data object in production system (display infoobject --click on three arrows button) which will list you all the objects. better to take screeen shots to know what are all objects are active and what are all inactive.

If you have not done the changes in development, check it in development. and then compare if allthe objects are in sink with production, coz say if someone has created a Transformation(any object realted to Master data object) in development which is not in production, and if you collect this object and move the Transport will fail.

First move the Master data object with changes.

Collect only those objects which were deactivated and available in production. Colllect TR's in one request, DTP's in one and MP 's in one.

First move Transformations followed by DTPS' and Multipproviders.

Also check all the objects you activated matched the list of deactivated objects at the time of activation(While activation take this also in a wordpad,screeshot).

Hope this helps,

Aparna Duvvuri

Edited by: Aparna Duvvuri on Nov 24, 2011 8:22 PM

[Former Member]

After you re-activate and capture the master data in a transport request, there is a list of affected objects in the log displayed - this shows the status of activation.

You'll have to capture these objects in a different transport request and then send it to the further target systems.

Also, have a list of dependant objects existing in Production system - which are active.

This will help you in case you've missed any object and you can activate it manually, if possible.

[Former Member]

Hello Everyone,

Copy Vishal,

Do you mean also get a list from Production a where-used list of objects affected by this master data object and directly re-activate these existing active objects after transport?

Where-used list shows the master data 0<infobject> is used in the following :

1. Infocubes

2. DTPs

3. Infoobjects

4. Infosets

5. Transfer Rules (3.x)

6. Infosources (3.x)

7. Multiprovider

8. DSO

9. Transformations

A. Update rules

If my understanding is correct, the DTPs and Transformations or Update rules will have different technical Ids in the Production system.

My concern is , given many objects do not belong to me, if I were to club all these into transport requests and transport into Production, if some affected objects are under development or changed , these unfinalised / untested changes could be transported into Production causing all sorts of problems.

Also, the Production system could have changes done directly in Production system and was not transported from Development system. I mean inconsistency between Dev and Prod.

Given all these concerns, how should I proceed with the transport?

Please could you advise further ?

regards

Pascal

[Former Member]

As per my experience: the where-used list shows all the possible places where the Master data characteristic has been used.

Now, when you make changes to the Master data, it is not necessary that all of the objects listed in the where-used list would be affected. The objects which are affected will be shown in the log while you actiavte the Master data object after changes.

DTP's and Transformations may have a different technical ID in Dev & Prod, but this is not always true provided these objects were transported - transformations will anyways be transported, DTPs can be created in each system.

It is always better to transport the objects - DTP and infopackage can be exceptions.

Coming to your question of objects that may be under development:

Yes, this is true. There can be many such objects which have a different version in Dev and Production. This is a pain area, and you'll have to check these/ confirm with your team if someone is owrking on them or not. It may happen so that the inactive object is actually captured in another request. In such cases, if its possible, activate the objects independently in the target systems - for ex. transformations/ DTPs/ Process chains.

But, if there is another infoobject or a cube or dso undergoing changes, then it would need the intervention of the person responsible and how he wants to take it forward.

And, while clubbing objects - i always follow some rules:

Club similar objects in a request - for ex. Transformations. DSO and cube in a different request.

In this was the number of transports increases but transport management becomes a lot easier.

Hope this helps.