Skip to Content
author's profile photo Former Member
Former Member

Modifications in report.

Hi mates,

I want to modify existing report , which is there in <b>production</b> and <b>dev</b> system. Could you tell me in which system( pro or dev) it is better to change the report, why?

Regards.

hari

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 29, 2007 at 07:09 AM

    Hi,

    This is really make more problems in future not only technical wise, business wise also.

    Assume this situation:

    Today your touching the query in production for small change. All will work fine. User also will accept. In future, user will come to you for changing small thing in info provider itself like query change.

    Then that time you dont have any way to go with dev to QA and prod for change. Coz already u did some change in production directly. User dont know whether you are doing the change in query or Info Provider. This will create more risk coz it may delete the data in production system. So hole business may be collapsed.

    They will not accept the risk. Coz they dont know about landscapes. They know only small change and big change. So dont change users mind. Maintain the sequence.

    As a BW Consultant, we only know the risk. So there is only one way for doing change that Dev to QA and the Prod.

    Regards,

    Vivek V

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 29, 2007 at 01:33 PM

    Hi Hari,

    You've got very good suggestions on why it's very important to make changes to any object in Dev and then move it to QA and Prod. I'd also like to add another reason of why this rule should be followed - for SOX (Sarbanes Oxley) purposes and if there are any internal audits done on the practices follwed by the Software team, there'll be just too many red flags for you to go back and justify to the auditors why changes were done in prod rather than follow the norm. I always found myself in a similar situation with business users saying "oh we dont have time, why dont you do the changes in Prod" etc, but explaining them clearly the procedures and the risk associtaed with it, they eventually stopped asking me that question and plan ahead of time to request for any changes.

    Best Wishes....

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 29, 2007 at 06:10 AM

    Hi,

    We need to follow some rules here. We do any modifications in DEV and do the testing in QA ,if we are getting required results in QA, then only we need to import into production.

    With rgds,

    Anil Kumar Sharma .P

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      Ofcourse it may save your time now. But one day it will take double of this saved time,if you keep on going to modifications in Prod directly.

      If you feel that it saves time, why we need a such landscape in which we have DEV,Qa and PROD.Why can not we have only onw PROD. It reduces the cost also.

      It is 100% wrong to make changes in PROD. Assume we did some changes to Query in PROD directly. ans assume we did a little change in DEV and imported that change into PROD, then you will loose all changes that you did in the production directly.

      So Remember that no body is exception to the principles and rules we decided.So for anybody's request of change we need to come DEV only.

      With rgds,

      Anil Kumar Sharma .P

  • author's profile photo Former Member
    Former Member
    Posted on Jun 29, 2007 at 06:14 AM

    the usual practice is to change in DEV and transport to PROD. even though u have the system open for developing queries for power users - or who ever

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.