Client strategy for DEV system in an implementation proj

Hi,
Can some one advise a good client strategy for an impl project? here's and example and questions i have. if you have a better strategy, pls advise. We want to follow this on ECC 6 DEV system -
10 - Sandbox (play around before doing config - no transports)
20 - Golden client (do real config here, and do development here - transports will start from here)
30 - Test client (for SCC1 testing)
I am assuming I should do DEVELOPMENT in the same golden client - does that make sense? Else, which should i have a new client? in that case, how will transports move?
Thanks for all your help

Hello Jerryp,
Our customer has similar setup:
100 - Sandpit
200 - Dev and Cust
300 - Testing
400 - Sandpit 2
Whenever we need to do any unit tests in client 300, we copy over customizing by using SCC1 transaction (client copy via transport request).
For example whatever development (code or customizing) we do in 200 is copied over to 300 by SCC1. This ensures the client dependent customizing is in sync with client 300 without destroying data.
Also, periodically we refresh client 100 and 400 and with data and customizing from 300. No development client independent changes are possible in the sandpit and testing clients.
Regards,
Siddhesh

Similar Messages

Couldn't create jco client connection for logical system

Dear Experts,
we are facing a strange issue in our custom webdynpro java application, few of our portal users are getting the "couldn't create jco client connection for logical system" for Model Data JCO Destination. below are details
1. portal version 7.02 SP14 (we have recently updated to SP14 from SP02-- is this is causing the issue ?)
1.1. updated the NWDI track with SP14 SCA files as well as added latest WD Runtime SCA file deployed the applications to Production also.
2. above said exception is inconsistent and happening for only few users
3. ping and test of jco destinations are successfull in content administration as well as in SLD, destinations were added in the SLD system.
4. cleared the JCO ARFC meta data cache in webdynpro console
5. jco destinations are configured using uid/pwd, configured user is not locked active and tested in the backend by logging in with the same user.
6. restarted the portal server
even though, we are getting the above said exception for few of portal users randomly.
Please help me on this ASAP, as i am not getting any further help on this.
Thanks,
Ram.

Hello Ram,
Check the JCo Pool Configuration settings of your JCO Destination. This message normally comes when the maximum connections has been reached. Increase the "Maximum Connections" to some number depending on the usage. A good habit is to disconnect the jco connection after executing the same in your webdynpro code if you don't want it to be synchronous.
<ModelName>.modelInstance().disconnectIfAlive()
Hope this helps.
Regards
Vijay

Client strategy for SAP Discovery system

Hello,
We have installed SAP Discovery system and would prefer to create custom clients copied from the standard clients for use by the users. Please let me know if there are any restrictions or possible problems creating custom clients in SAP Discovery system.
Thank you,
Vijaya

Hi,
There are no restrictions for creating custom clients on the Discovery System box.
It is highly recommended to backup your current server before customizing the box so you can return to the original state if needed.
Regards,
Amir

Problem Addition Reporting Client tools for Hyperion System 9.3.1

Hi,
I'm using Hyperion System 9.3.1 (on SQL Srv).
I had no Reporting tools installed.
Then Reporting Client 9 products has been installed and configured successfully.
After that I logged into Workspace, system lost any apps and tools. Nothing except Shared Services (User Mngmnt).
When I tried to reconfigure Reporting products I got error "Invalid DB schema for Reporting product".
New DB schema has been created for this products and deploied it. But I have no positive result.
What can be a reason?

Hi
"Invalid DB schema for Reporting product" is a bug, have a patch to solve, i dont remember the number.
The workarround:
- Make Backup of DB.
- Drop DB table
- Reconfigure the Reporting creating a new table
- Restore Backup

Back up strategy for java systems (EP7.0)

Hi Gurus
We are using windows server 2003 Ent and SQL server 2005 for our ECC 6.0 system (dual stack). and one more Enterprise portal 7.0. on different box with the same OS and DB.
As i am new to MS sql can any body let me how to proceed with the back up policy especially with the JAVA systems
This is i am planning.
Whole Database Full - Offline Monthly
/usr/sap/<SID> Full- Online Daily
transaction logs every 4 hours
Any way frequency does not matter. but are these above steps are suffienent to recover or do we need to keep more on backup.
kindly suggest us.
Thanks in advance.
Regards
BALAJI

Hi Bala,
Do have a look at these threads, while they may not answer your question they seem to have some good inputs
1 - How to backup MSSQL database in ECC6
2 - https://cw.sdn.sap.com/docs/DOC-40515;jsessionid=1B4BAE46AE116F95C178F7D34A259E6F
In one of my assignment where the setup was more like the one you mentioned we did the following:
BI-Weekly
Windows Filesystem Backup
Whole Database - Offline Backup
Everyday:
SID backup - online
Apart from that we also included plans for backuping the UME Database (it was a directory), TREX
Good Luck!!!
GLM

Regarding Client Role change in DEV system.

Hi All,
I had some requirement from SapHR they want to do some Holiday calender changes in Sap Level.
and we have only Test Role client in our Dev System. They want me to change the Client Role from Test to Customizing Client.
Kindly let me know if Client Role is changes from TEST to CUSTOMIZING. is there any inconsistany in TMS.
Thanks,
Abdul

Hi,
Run BDLS to change the source system assn. Then check to see if all your transfer structures are active and also your source system is now the correct one. Easiest way is to goto RSA7 on the src system and see where the system is pointing to.
Cheers,
Kedar

What is the best SLD strategy for CE?

We have some options like a single centralized SLD or a local SLD or something between them, e.g. an SLD for dev systems, etc.
Could you share your opinion -- what is a good SLD strategy for CE? Thanks!

Hi,
It wud depend on the landscape u have and requirement stategy.............
If you have a productive version...............obviously centralised SLD wud be preferred.....
Either case......juz to touch-base features of CE 7.1 i.e for exploration and R&D purpose..........lacal SLD and developer edition wud do.......

Landscape Strategy for SM1 & SM2

Hello all,
I am new to Solution Manager (and SAP in general) so I came here to seek for your opinions.
I have SM1 and SM2 installed in one box. SM1 serves as our playground (sandbox) and SM2 serves as the semi-prod.
SM1 is in Solution Manager 7.0 EHP1 SPS 20 while SM2 is still in Solution Manager 7.0 SPS 16.
Currently, I have 11 other systems as follows:
- ECC 6.0 (1st and 2nd instances)
- PI (with SAP NetWeaver 7.1)
- XI (with Netweaver 04)
- EP with NW 7.0 (1st and 2nnd instances)
- BI with SAP NetWeaver 2004s (1st and 2nnd instances)
- SRM 7.0 EHP1 SPS 03
- APO (SCM 5.00) (1st and 2nd instances)
all 1st instances are treated as dev systems while 2nd instances are treated as semi-prod systems
How can I go about the Landscape stategy for the two? That is, which systems to connect to SM1 and which sdystems to Connect to SM2?
i was thinking of the following concepts:
1st option:
#1   SM1 (dev't) - only satellite systems that are NOT on the path to production would be connected here - such as a sandbox. This solman system would be used for configuration of solman itself example, your solman team would configure solman functionality here. It is also a good practice environment for PM's because it would have a small landscape attached to it your sandboxes, remember? Migrations start here for solman functionality...
#2   SM2 (semi-prod) - ALL path to production satellite systems are connected here, except your sandboxes which were connected to SM1. This system also serves as a target system for migrations that came from the dev system (SM1) for solman functionality itself. This is the main solman box that most users will access for project management, blueprinting, config, charm, and so forth.
can this be possible?
2nd option:
#1   Sandbox Solman - no satellite system connectivity; open access; used for the purposes of testing patches and exploring solman functionality - mostly for basis' purposes.
#2   'Development' Solman - only satellite systems that are NOT on the path to production would be connected here - such as a sandbox. This solman system would be used for configuration of solman itself example, your solman team would configure solman functionality here. It is also a good practice environment for PM's because it would have a small landscape attached to it your sandboxes, remember? Migrations start here for solman functionality...
#3   'Production' Solman - ALL path to production satellite systems connected here, except your sandboxes which were connected to #2 remember?. This system also serves as a target system for migrations that came from #2 for solman functionality itself, This is the main solman box that most users will access for project management, blueprinting, config, charm, and so forth.
for the 2nd option, I will have to install a new SolMan system to have a three landscape.
please advise.
your insights will be very much appreciated.
thank you.
charisse

Hello Charisse,
I am not sure you are understanding the use of Solution Manager to manage your system landscape.
Typically one Solution Manager will manage the entire system landscape, and systems of all types, PRD, QAS, DEV, SANDBOX, TRAINING, etc.
You can still have DEV and TEST and Sandbox Solution Manager systems, but they would be for those functions, developing, testing, learning and would not be managing your system landscape as that would be the role of a production Solution Manager system, normally.
You should start here - https://websmp207.sap-ag.de/solutionmanager, then also navigate to the "Media Library" where you will find a collection of Presentations, Articles and Brochures, Documentation, Technical Papers and How-To's.
Of course you will find the Knowledge Transfer Ramp-up Kits very helpful - http://service.sap.com/rkt-solman
And also the help library is often quite useful - http://help.sap.com - select the Solution Manager product and then select the applicable version.
You should find these resources quite helpful in determining a strategy for your system landscape and grow your Solution Manager knowledge.
Regards,
Paul

Clients in DEV system

Dear experts! We have standard 3-tiers SAP landscape: DEV- QAS - PRD systems in separate servers. My question is about DEV system clients. By now we have 3 clients in DEV system: 100 client (only Customizing, transport allowed, "Golden" client without any data),300 client (Sandbox) and 500 client (ABAP programming, some application data present, transport allowed). Now we're implementing Change Management with SAP Solution Manager. CHaRM supposes only one dev client with "transport allowed". So, we decided that our ABAP-programmers have to develop their programs in 100 client. But they are not very happy to develop programs in the client without any data! I 've read in SAP Help that DEV system has to consist of Golden(Customizing) client, Sandbox and Unit Test. But I can't find out the answer: where ABAP programmers have to work? Please, suggest me the right answer. Thanks.

If this modification is included in a transport request:
In STMS you will need to add the transport to the DEV buffer by opening up the DEV buffer first, then choosing Extras -> Other Requests -> Add (input the transport number that contains the client-specific changes)
Then highlight that transport in the buffer and hit the import button (little truck) and specify the client you need it to go to in the dialog box.
If the request also needs to go to other clients inside the same system, then choose the options "Leave transport in queue for later import" and "import transport request again" and that will prevent you from having to add the request to the buffer again.

No F4 value for system and client field for create job request

Hi,
While creating a job request in Solution manager system filed and client filed F4 is not working , it does not show any value.
Do you have any idea regarding this issue.
Thansk & Regards,
kaushal

Hello Kaushal,
you habe to link user, key user i.e. a business partner (BP), and managed system and this work like this:
a) User <-> BP: start transaction BP, assign role Employee to your business partner and enter the user name on tab Identification
b) BP <-> managed system: start transaction BP, select role General and enter the External System Identifier (format: <managed system ID> <installation number> <client> <user in managed system>) on tab Identification
Alternative: Use transaction BP_GEN to create valid business partners for managed systems
See also the Solution Manager Implementation Guide (IMG):
-> transaction SPRO
.> SAP Solution Manager Implementation Guide
-> SAP Solution Manager
-> Cross-Scenario Settings
then
-> Business Partners
and
-> iBase
(Note that IMG path (and labels) might vary in between support packages)
Kind regards,
Martin
http://service.sap.com/jsm

Implementation strategy for non sap sources

hai friends,
could anyone help with the
'implementation strategy for non sap sources'.

Hi,
Its the same as with R3 sources.Only difference is you'll have different underlying interfaces. Non SAP systems can either be flat files, ETL systems or legacy systems using ETL connection, Oracle or Java systems XML, etc.
But your stategy would remain the same only per your non sap source system, the transactions and the ways you configure your datasources would differ.
Cheers,
Kedar

XI, SLD & multiple clients for DEV & QA

Ref: Re: 3rd party tech systems for multiple business systems...
I have a question regarding the avoidance of duplicated Configuration (Collaboration Profiles, Logical Routing & Collaboration Agreements) for different clients in the DEV/QA landscape.
As we know: many projects have multiple clients in DEV and QA. Here is an example landscape:
SXD_100 - Dev XI server
SED_100 - config dev
SED_200 - ABAP dev
SED_300 - unit test
SED_400 - sandbox
[ 1 technical system : 3 business systems ! ]
LDEV Legacy system
[ 1 technical system : 1 business system ]
SXQ_100 - QA XI server
SEQ_100 - clean config QA
SEQ_200 - ABAP QA
SEQ_300 - data migration prep
SEQ_nnn - yada, yada...
[ 1 technical system : nnn business systems ! ]
LQA Legacy system
[ 1 technical system : 1 business system ]
The problem:
SED_400->LDEV is used for prototyping integration
SED_100->LDEV is used for config development
SED_200->LDEV is used for ABAP development
SED_300->LDEV is used for unit tests
Receiver Determination is able to look into the message for a dynamic receiver, but we are not able to have a sender like "SED*"
The question:
Do we really need multiple sets of configuration in the Integration Directory? Is there a way to re-use the configuration for SED_100->LDEV for the other development efforts?
Any feedback would be greatly appreciated.
Rgds,
Derek

Hi Derek,
Since there can only one business system in SLD per client in SAP R/3.
e.g
SED_100 will have lets say BS_100_Dev
SED_200 and BS_200_Dev
In QA
SEQ_100 -> BS_100_QA
SEQ_200 -> BS_200_QA
It is not possible to configure the single scenario catering the Dynamic (multiple) sender agreement to Reciever.
But for QA you can use set transport target in SLD to reflect the BS_100_Dev -> BS_100_QA, where ever used.
This doesnot solve the problem of having dynamic sender service, it is just for information.
We also faced the same problem of testing a scenario from different clients of SAP :(.
Cheers,
Satish

TDMS for refresh DEV system

Hi,
Does anybody have experience with refreshing a DEV system using TDMS?
Our DEV system consists of 2 clients, One used by programmers with no data in it, and a second client with some transactional data for performing the first tests before something is transported to QAS.
The repository of a DEV system will never be the same as on a production system (people are programming simultaneously), so the scenario I had in mind was to create the DEV system as a shell from the production system, create 2 clients and use a TIM for the second client.
But then all the program specific data which is stored in DEV gets lost (e.g. program versioning).
Does anyone know how to keep this data?
Kind regards,
Nicolas

Hello
Their are some main concerns before a TDMS TDTIM transfer can be done, these are -
1) The table whose data is to be transfered from sender system to receiver system should exist in both the system.
2) Key fields should be exactly identical.
3) Their may be some extra fields in the receiver, this will not pose any issue but if their is an extra field in sender then its data could not be transferred. So to solve this either mark this table as not use or change the table in receiver to add the missing field.
As a part of TDTIM both the system will be analyzed for consistent repository and any discrepancy will be notified to the user then user needs to decide whether he marks the inconsistent table for no transfer or corrects the inconsistency before proceeding further.
Best regards,

Mass transport strategy but satellite system is configured for ChaRM

We want that all transports are automatically transported in the development test client.
We have calling a job with program TMS_BCI_START_SERVICE in the satellite system. But this program can only be used for mass transports and does not work when single transports strategy is activated.
Question:
Is there no solution to transport all this transports automatically in development test client via mass transport strategy if satellite system is configured for ChaRM scenario?
Thanks a lot in advance.
Regards Urs

Hello Michele,
Please, check the point 5 in the link below:
/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
I think that this information can help you.
Best Regards,
Diego Fischer

Multiple clients in CRM Dev/QA system

Hi All-
I've seen in various places that it is recommended to only have one client in a CRM system. I have worked at many sites that have several CRM clients in a system without issues.
Can any one point me to an SAP Note or document that recommends only one client per CRM system? I realize that there are possible issues with the CRM pricing and cross-client customizing downloads but these can usually be worked around. What other issues are a concern?
Any SAP document about this would be great.
Thanks!
Tim

Tim,
Unless you are going to have multiple back ends or some business scenario that requires multiple clients in CRM Production, then don't do it in CRM Dev/QA.
The reason why don't do multiple clients in a CRM system that is connected to an ERP backend is the following:
CRM configuration is dependent on downloaded configuration from the ERP system.
A normal CRM system should only have one backend connection.
Now why would you want want to have a Dev and QA system that does not reflect how your production system works. In fact in the case of CRM you are making more work and creating systems that do not accurately mirror production.
The whole gold client concept in CRM is honestly a bad idea when you have single ERP backend, because it just causes more work for people and it my opinion its a way of people trying to stay busy than add real value.
Now if you really want to keep busy maintaining middleware and keeping things in sync, go for multiple clients in Dev/QA. The best part is when something in Prod breaks you won't have any environment that mirrors Prod correctly from a middleware perspective. In my opinion if you are that concerned about configuration and master data mixing then you probably need a CRM sandbox instance to try things out.
Take care,
Stephen

Client strategy for DEV system in an implementation proj

Similar Messages

Maybe you are looking for