Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

00126 - Adding Modules to a Live System

00126 - Adding Modules to a Live System

ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Adding Modules to a Live System

Hello AKL:

Think about this:
D01 -> Q01 -> P01 -> S01

Where S01 starts as a copy of P01 and is upgraded as a sandbox. All of the
upgrade work can be completed on the sandbox and initial testing can be
performed all the way up to the time that integration testing would be
starting. With the structure above, production support stays the same until
time for integration testing at which time all changes would need to stop
anyway. At that time, D01 and Q01 would be upgraded and configuration
changes (identified in the sandbox) would be executed in D01 and transported
to Q01. After transports were completed, integration testing would start.
If you add S01 into the landscape as shown above, any configuration changes
made as a part of normal production support would be transported from D to Q
to P and S. I would limit changes to D to only those required to fix
problems.

Anyone else... Any comments...
Best regards,

Alan Olson
SAP America Platinum Basis
3530 Dain Rauscher Plaza
60 South 6th Street
Minneapolis, MN 55402
(612) 359-5108
(612) 359-5003 (fax)

-----Original Message-----
From: ANG Kiam Lian [mailto:Ang.KiamLianZU...]
Sent: Wednesday, December 20, 2000 8:12 PM
To: 'sap400Zm...'
Cc: TEOH Paik Heong
Subject: Adding Modules to a Live System


We are live and our current landscape is D01 -> Q01 -> P01. We are starting
a new phase to add some modules into the current system. Concurrently, there
may be some enhancements made to the current system. After some discussions,
it was decided that we will create 2 more instances, D02 and Q02, for the
new phase.

D02 will be a DB copy from production P01. What we want is whatever is
imported into P01, we want the request to be added into D02's buffer
automatically. Then, maybe once a week, we will review these requests before
importing them into D02.

To perform QA testing, Q02 will be a database copy from production again. We
will import all requests originating from D02 into Q02. This will be like a
dry run for live implementation.

We are at 45B V4R4.

1. Will the following landscape achieve what I have described?

Transport route 1: D01 (Integration) -> Q01 (Consolidation) ->
P01 (Delivery) -> D02 (Delivery)
Transport route 2: D02 (integration) -> Q02 (Consolidation) ->
P01 (Delivery)

2. How do I stop requests from being added to P01's buffer after they are
imported into Q01?

Any help appreciated.

akl.
Business Solutions Division
United Overseas Bank
Ang.KiamLianZU...
_________________________________________________________
If you can't solve a bug, call it a feature. - S.A.



Durban Tours - Südafrika Safari

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3608 Date: 20230205 Time: 122923     sap01-206 ( 2 ms )