Question:
In our current BW prod, we have Infopkg/Infopkg group set up as "Changeable Original" in RSA1-->TransportConnection-->Object Changeability. We notice that we can create and modify new infopkg/infopkg group that we created directly in BW Prod, but we cannot not modify any infopkg/infopkg group that were transported from BW Dev.
We have to ask the Basis team to open up the BW Prod system to modify these transported infopkg/infopkg group.
For all of you out there, what is the best practice for maintaining these infopkg/infopkg group?
1/ Should we transported ALL infopkg/infopkg group from BW DEV for any needed changes?
2/ Or should we always create the infopkg/infopkg group in BW Prod so that we can have the flexibility in maintaining and modifying?
3/ Or may be a mixture of 1 and 2 above? and Why?
Please let us know which way that you maintain the infopkg/infopkg group, and the pro & con of it.
Thanks,
Kevin-
Answer:
First of all the reason you're not able to change Ipkgs / IPKgrps that came from Dev / QA in Prod is b'cos of the object chageability flag.
Set it to everything changeable instead of changeable original . This should let you change even transported objects .
I would recommend a one time initial transport of the pkg / groups / chains from dev to qa to prod so that you have your base objects avail. in all environments . But from an ongoing maintenance / support / testing standpoint its not a practical approach to send transports . So in this case the obj. chageability flag should take care of it .
It can be a hard sell with Basis folks in case they are aware of this and do not understand BW functionality well enough to agree to this approach .
Hope this helps.
ST
Answer:
ST, thanks for your valuable inputs. We are in a very similar situation like you just explained.
BW fans, we really need your inputs on this topic. Please drop a few lines
for us as how you currently maintain Infopkgs/Infopkg groups/Process Chains in your BW production environments.
Thanks a million,
Kevin--
Answer:
My personal opinion (not a rule though) is that InfoPackages and InfoPackage Groups should be maintained directly in productive environments... at least that's how it works best here at this project.
I guess there are pro's and con's about various approaches...
cheers,
El Belgio