System Landscape (Dual Development System)

Dear SAP Experts,
We have Two-System Landscape(DEV-PRD) Whereas cross-client data is used in both the Customizing and quality assurance clients.
Currently, our company, just merged with another non-SAP-using company. The First move is to implement FI module and subsequently, all modules that we are now using.
My boss discussed with me if we could create another DEV server for company B to use for their customizing and QA clients as not to impenge on our already customized set up.
Please advise if this set up is possible, and if not, Can anyone kindly give an advise how to approach my problem?
I'll give good points for the help that i can get.
Best Regards,
Jay

You can do this. We currently have two Dev environments one for projects based on NetWeaver integration with our ECC systems and one for regular development / run and maintain.
I suggest doing a system copy of your development and rename the SID / hostname were it appears in the profiles and home directories for UNIX platforms. Then perform post steps for SE06, printers, profiles, RFC etc...
For Microsoft install a CI instance and do a database copy to have current data. Then do post copy steps in SAP.
Although SAP suggests not to refresh Development systems, we do it at least once a year to get current applicaiton data.
Think of it as a sandbox.
If you don't want to integrate your data with the new system, skip the database copy portion for Microsoft and do a fresh install for Unix.
Hope this helps.

Similar Messages

How can I make my storyboard landscape during development?

It switches to landscape when I launch the sim but not in the IDE.
I'm just getting into this even though I have been signed up for a year or so.
Any help would be appreciated.
Thanks

Converting a two system landscape to three system landscape

Currently, I have a two system landscape: DEV (development) and PRD (production) in STMS
I would like to add a QAS system so I will end up with DEV-QAS-PRD in STMS
I would like to keep all data the way it is. I don't want to lose any logs or files in the data and cofiles directories.
This is how I have this planned:
-Include the QAS system in the existing Tranport Domain.(stms in QAS)
-In transaction STMS go to OVERVIEW -> Transport Routes -> Standard Configuration -> Three systems in group
and then save the configuration.(stms on the TDC)
I'm thinking this will preserrve the current log files and the corresponding data and cofile files.
If you have done this, I would appreciate any comment or advise.
Thanks.

Addition to above suggestion - Adding new system to existing landscape doesn't make any change to the data/cofiles. Process just adds additional system.
Regards,
Nick Loy

ChaRM - possible to have 2 different system landscapes in one project?

Hi,
can anyone tell me if it is possible to have 2 different system landscapes in one project. One landscape for developing and testing the Change Requests and another one for developing and testing the Bugfixes.
Thanks,
Martin

As Rick, mentions, there's no default way.
Having said that, there's nothing stopping you from doing it yourself. You can add a kind of language selector to the layout and set that for every html5 output. With some JavaScript, you can have the user switch between your outputs. It would look like content categories, but you'll have build it yourself.

Diff between Project Landscape and System landscape

Hai Gurus
Explain the thread
Thanks & Regards
Srikanth

http://help.sap.com/saphelp_sm32/helpdata/en/62/afcc3a9e8d6526e10000000a11402f/content.htm
SAP LANDSCAPE:
Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD.
DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training.
PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.
Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage).
As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).
You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.
But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV).
The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.
The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.
In summary:
Landscape : is the arrangement for the servers
IDES : is purely for education purpose and is NOT INCLUDED in the landscape.
DEVELOPMENT ---> QUALITY -
> PRODUCTION
DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.
QUALITY : is where the core team members and other members test the customization.
PRODUCTION : is where the live data of the company is recorded.
A request will flow from Dev->Qual->Prod and not backwards.
1. Sandbox server:
In the initial stages of any implementation project, You are given
a sandbox server where you do all the configuration/customization as per the companies business process.
2. Development Server:
Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.
3. Production Server:
This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production.
These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.
Presentaion Server- Where SAP GUI have.
Application Server - Where SAP Installed.
Database Server - Where Database installed.
What is the meaning of "R" in R/3 systems?
R/3 stands for realtime three tier architecture. This is the kind of architrecture SAP R/3 system has.
R/3 means three layers are installed in Different system/server and they are connected with each other.
1)Presentation
2)Application.
3)Data base server.
Reward if useful

System landscapes

HI Basis Guru's,
I need to give a presentation on system landscapes to my entire project Team members.
i prepared the technical architecture.
can any one send me some documents or links , so that i can explain and present it with good explanation
pls send me if u have [email protected]
Thanks,
Ravindra

SAP Landscape:
Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD.
- DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
- QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training.
- PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.
Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).
You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.
But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.
The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.
In summary:
Landscape : is the arrangement for the servers
IDES : is purely for education purpose and is NOT INCLUDED in the landscape.
DEVELOPMENT ---> QUALITY -
> PRODUCTION
DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.
QUALITY : is where the core team members and other members test the customization.
PRODUCTION : is where the live data of the company is recorded.
A request will flow from Dev->Qual->Prod and not backwards.
1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process.
2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.
3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production.
These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.
Presentaion Server- Where SAP GUI have.
Application Server - Where SAP Installed.
Database Server - Where Database installed.
Regards,
Rajesh Banka
Reward points if helpful.

What is System landscape

Hi Experts !!
What is system Land Scape and in what way it is used may i know. From previous thread i am not able to find exact meaning
Regards
hat

Hi,
Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different landscape Development, Quality, Production.
It is again depends on the organization's requirement. Depending upon the client requirement we can extend the
Quality Systems & Production Systems to more than one.
- Development would have multiple clients for ex: 100- Golden for only configuration, 190- Sandbox,110- ABAP Development
- Quality may again have mutiple clients for ex: 200 -Integration Test, 201- for testing.
- Production may have something like a 300 Production.
Landscape : is the arrangement for the servers
IDES : is purely for education purpose and is not included in the landscape.
DEVELOPMENT ---> QUALITY -
> PRODUCTION
DEVELOPMENT : is where the the consultants do the customization/ configuration as per the company's requirement.
QUALITY : is where the core team members and other members test the customization/ configuration.
PRODUCTION : is where the live data of the company is recorded.
A request will flow from Dev->Qual->Prod and not backwards.
Hope it will help you,
Thanks Nirali P

ChaRM config - system check error

Hi All ,
I am working with the basis team to move forward with ChaRM - Solution Manager. We have a two system landscape with Development (DSM) and Production (PSM) (domain is set up as DOMAIN_DSM - exists in STMS).
We have most of the configuration / system landscapes done . When we do the ChaRM check ( solar_project_admin--> select project --> system lanscape --> Change request --> check) for a project that involves system (DBW - BW Development and a different transport domain DOMAIN_DBW , does not exist in STMS for DSM) it comes up with a system error saying - No domain for system DBW.
It seems to be checking the tabel TMSCSYS for systems DBW and when it does not find it there it complains. The question is do we have to set up these system in STMS in solution manager ?
any help would be appreciated . if you want to send me a doc please do it at amohamm at yahoo
thanks.
ali.

The problem was solved by activating the domain links for the multiple domain scenario . Please make sure that you carry out this activity - " You must perform all TMS activities in your satellite systems and not in your SAP Solution Manager system " .
Ali.

System copy for QAS

We are Go Live before 2 years.
Our SAP Landscape is Development->Quality->Production.
Now we want to refresh Quality server thru system copy.
So we can have same data, config and abap development as our Production. So it very useful in testing.
At present there are many abap developments which are not transfer to production due to some reasons.
So we are facing problem during testing as Production and Quality abap developments are different in some cases.
Is is advisable to re-fresh quality with production thru system copy?
Request you all to please share your experience.
Regards,
-dt

Hi,
Thanks for you inputs.
So I will prepare a list of developments are under testing and not transported to production.
after system copy I need to import transport requests of the same in Quality.
Those development which not required to transport in production, that request no need to transport in quality. As I have mention in my post that there are certain old developments which are not transported in production and no need to transport in future also.
This is my first experience on SAP. Is it advisable to refresh quality server. In companies what standard practice follow after go live.
Regards,
-dt

Com.sap.ip.bi.bex IView - SYSTEM parameter in Portal

Dear Experts,
We are calling the iview com.sap.ip.bi.bex from the Portal system passing the parameters u201CSystemu201D and u201CTemplateu201D to invoke BI queries in a BI 7 system.
eg: http://<sap portal server>/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.bex?System=BISystemAlias&TEMPLATE=ZYQ_PD_LOGISGENEX
But we find diferences if we use uppercase or lowercase letters in the parameter u201CSystemu201D across our landscape.
Development Portal System
SYSTEM => Error (#1.5#00145E23B5DD007200000028000014240004987887685067#1293543342088#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/irj#com.sap.ip.bi.base.exception.BIBaseRuntimeException#YP05914#3173##n/a##593456c6128711e0bd5b00145e23b5dd#SAPEngine_Application_Thread[impl:3]_5##0#0#Error##Plain###Exception thrown: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error) => Portal System Error
System => OK
system => Error (#1.5#00145E23B5DD00630000008900001424000498788A81C074#1293543394086#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/irj#com.sap.ip.bi.base.exception.BIBaseRuntimeException#YP05914#3242##n/a##7bd9384b128711e0c7b300145e23b5dd#SAPEngine_Application_Thread[impl:3]_17##0#0#Error##Plain###Exception thrown: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error) => Portal System Error
QA Portal System
SYSTEM => OK
System => OK
system => OK
Production Portal System
SYSTEM => OK
System => Error (Internal error. No esid found) => This is a BI System Error
system => OK
This issue is strongly bothering us, since we cannot transport from Development to Production because they behave differently.
Any ideas?
Thanks in advance,
Fede

Dear Pramod and N Bansal,
Thank you very much for your help!
Finally my problem was solved. The problem was never about the parameter, as we thought initially. When we used SYSTEM, Portal didn't recognize de parameter, and it only worked because when the parameter is spelled wrong (or it's absent), the BI Master System is used.
The correct parameter is (and it always was) "System".
Moreover, we realized that it's not enough to define the alias of the referenced BI system in the Portal System. It's also mandatory to define that same alias in the default system that is created in the installation of the BI system (located at pcd:portal_content/Systemlandscape/SAP_BW of the BI System).
I hope this could help others having the same problem.
Thanks again for your help.
Fede

Transport managemnet system

How does Transport works in Netweaver enterprise portal in 3 system landscape
regards

Hi Muhammad,
The three system landscape is
Development --> Quality --> Production
Create the objects (Roles, Worksets, pages, ivews, folder) in Development portal.
Then using the path
System Administration --> Transport --> Export
you can export the objects from Development server.
Then loggin to Quality portal server and follow the path
system Administration --> Transport --> Import
and import the .epa file from the Development server.
Then do the testing in Quality portal server. If everything is fine then
loggin to production portal and import the .epa file
Regards
Arun

Versioning and parallel development streams for worldwide SAP roll-out

Hi SDN folks,
My customer is in the process of a worldwide roll-out of SAP. They have a transport environment for ECC that looks like this:
D -
>    QA -
> R   -
>   P
We have SAP Charm installed and running in solution manager - to manage the creation of transports in the D system.
The problem we are facing is how to manage parallel development changes and configuration changes.
For example - if we have developers working on a change that is in test in the QA environment - and we hit a production emergency in P - we then need to make an emergency change to the P version (which would only be available in P and R) - and transport this change through to P - in the process - overwriting the changes that our developers are working on in the D and QA environments.
We also have the issue of objects for multiple countries being developed and configured in parallel - and so there will be version conflicts up the to the QA system as well.
Is there any kind of solution for the management of parallel development streams - and versioning - for all custom code / development objects and for configuration changes(other than introducing a second development system)?
Is there any kind of 3rd party product for SAP that helps to solve this issue?
Currently we are considering development freezes, manually renaming objects with versioning identifiers (will only work for some objects), manual backups of versions. - none of these seem to be a tidy universal solution, is there one?
Any help / directions you can offer will be appreciated,
many thanks,
Julian

Hi Julian,
Thanks for the clarification!
Managing production support and new development after go live is always a challenge. It can be addressed in many ways, but it is most important to create a set of rules and stick to the procedure. If you do not want a "second" landscape, you are going to have objects "overwritten" in the D and Q systems when you need to make a production fix -- as you must revert the object in D to the P version to make the fix. Even with a second landscape, objects will have to be merged somehow when a fix is promoted to production.
As I said above, what you can do is have your developers save their current development in released transports before making the production fix. This saves a version that must be merged with the fix, anyway. That is:
Object A is the produciton version and must be fixed.
Object A' is the current development version (unfinished) and is saved into a released transport request.
In D, Object A' is reverted to the A version and corrected for the production error, creating object A'' that is promoted to production.
Object A' and A'' are manually "merged" into A''' as the new current development version.
Yes, objects are overwritten with this method. However, you can always retrieve what has been overwritten since it has been saved in a released transport.
Another option is to bypass Q for production fixes. I.e. D -> R -> P. However, this invalidates the objects in Q until the merged version is created in D and transported to Q.
In any method you choose to do this -- dual development landscapes or not -- discipline and managment are a must.
Best Regards,
Matt

Has anyone implemented ChaRM in a 4-tier or 5-tier landscape?

Iu2019ve setup ChaRM with a 3-tier landscape DV1-QA1-PRD and everything works as advertised. I used the transport route, DV1/120 -c- /QA1/ (clients 149/150) -QA1 -d- PRD/150. Where -c- is a consolidation route and -d- is a delivery route.
Now I need to do a proof of concept to see if I can get CHaRM to work with our current landscape. We have a dual development path and need to make sure we sync our DEV and QA systems. The lanscape Iu2019m trying to use is DV1-QA1-PRD-DV2. The transport route Iu2019m trying is DV1/120 -c- /QA1/ (clients 149/150) -QA1 -c- PRD/150 -d- DV2/120. Iu2019ve tried various combinations and the only way I can get it to work is DV1/120 -c- /QA1/ (clients 149/150) -QA1 -d- PRD/150 -d- DV2/120. When I release and import into PRD it goes to both PRD and DV2. While this gets the transport to my support dev box I need to have another step in the workflow. What Iu2019m looking for is the workflow to act like dev-qa-qa-prd.
Has anyone setup a 4-tier or 5-tier landscape with release and import steps between each system? If so what did you use for your transport route and were they other config changes needed after the route?
Thanks for your time.
Jeff

Hi Jeff
Have a look at these
http://help.sap.com/saphelp_smehp1/helpdata/en/a3/0aae435a1342e8a56998d83a797161/content.htm
/people/dolores.correa/blog/2009/08/27/change-request-management-scenario-retrofit-functionality
Hope it helps
Santosh

Best practices for a development/production scenario with ORACLE PORTAL 10G

Hi all,
we'd like to know what is the best approach for maintaining a dual development/production portal scenario. Specially important is the process of moving from dev. to prod. and what it implies in terms of portal availability in the production environment.
I suppose the best policy to achieve this is to have two portal instances and move content via transport sets. Am I right? Is there any specific documentation about dev/prod scenarios? Can anybody help with some experiences? We are a little afraid regarding transport sets, as we have heard some horror stories about them...
Thanks in advance and have a nice day.

It would be ok for a pair of pages and a template.
I meant transport sets failed for moving an entire pagegroup (about 100 pages, 1Gb of documents).
But if your need only deals with a few pages, I therefore would direclty developp on the production system : make a copy of the page, work on it, then change links.
Regards

ABAP development license and AAK install

Hello,
What is the ABAP development license? Is it a license that has to be registered within our SAP system that our development is done on? Or is it just a license number that we reference on our test reports, certification etc? Just wondering what work, if any, is involved here.
AAK install. Is this just a typical install through SAINT?
Thanks.
Regards,
Scott

Hello Roy, Scott and Abraham,
Yes, indeed you will have to maintain such a development landscape, purchasing development license is not sufficient. Every customer Add-on must be delivered using a development namespace (i.e. /ABC/<name_of_object>), it is not advisable to delivered Add-on in customer namespace (i.e. starting with Z***).
AAK or Add-on Assembly Kit will be delivered to only those vendors who sign up for ABAP Add-on certification with ICC.
Hope this helps.
Regards,
Srini

System Landscape (Dual Development System)

Similar Messages

Maybe you are looking for