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

Similar Messages

Transport strategy for your transport landscape is inconsistent

Hello everybody,
we had 4 system landscape.
DEV>QAS>TST-->PRD.
we move the request from DDEV >QAS>TST and then forward request from TST to PRD system.
Now, we have delete the system TST from TMS, after deletion it give the warning.
Transport strategy for your transport landscape is inconsistent.
Message No. XT481
Please suggest, what is meaning of this warning and how to correct.
Thanks
Ganesh

You need to do following
1. Logon to domain controller client 000 -->STMS --> Overview System --> Select TST --> SAP System --> Delete
2. Reconfigure STMS DEV>QAS>PRD
3.STMS --> Overview Transport Routes --> Configuration --> Distribute and Activate (To All System)
Note : You should do this from Domain Controller client 000
I assumed you know Step 2. If you dont please let me know i can guide you on that as well
Cheers !
Manish

Transport strategy for BOE landscape

I am looking for a transport strategy for BOE landscape from security viewpoint. Basically we want to transport crystal reports, webi reports and folders along with security principles (BW roles/users included). Can anybody provide more info on this?
Regards,
Prasad

Yeah...we have LCM (XI 3.1 onwards) and Import Wizard for BOE tranports. But if we use BW roles as principles, transporting reports/folders with Security doesn't give desired results.
For example, if I am transporting a webi report with principle DEV001@RoleA from Dev to QA/PRD, I would get a new group in QA with name DEV001@RoleA instead of QAS001@RoleA. *I am looking for a pointer change here from DEV001 to QAS~001*. I think we have this feature of changing system pointers for Connections/Universes/Crystal Reports in LCM.
I know we need to move crystal reports and publish them again in QAS/PRD but this way we need to assign security for folders. I want to avoid these efforts by doing one time configuration in DEV and moving it to QAS/PRD through LCM. This is more consistent with current SAP Netweaver transport strategy.
Regards,
Prasad

Patch strategy for ECC6 in SAP NW2004s environment

Hi Experts,
Our SAPNW04s landscape consists of ECC6, BI 7.0, EP7.0 , SRM, XI, Solution Manager systems. We are drafting patch upgrade strategy for the ECC6 system & have 2 options:
Option 1: Apply patches only in ECC6 & not in other components.
Option 2: Patch ECC6 together with other components like SRM, BI, EP etc.
Option 2 will make things complicated but for Option 1 below are the 2 concerns/questions raised:
1. Option 1 will lead to doing UAT twice for Business Processes which have a tight integration with ECC6, for ex. UAT for data extraction needs to be done after applying patches both in the ECC6 & the BI systems. This will lead to arrange for more user resources.
2. Due to the tight integration between ECC6 & other components applying patches alone in the ECC6 might lead to other systems like BI, EP,SRM, XI etc at a lower level & they might not be able to connect to ECC6 or work properly with ECC6.
Can somebody share how they are managing the ECC6 patches upgrade in a big NW2004s environment with other components present, are the ECC6 patches done standalone & other systems like EP, BI follow their own different time schedules for patching or ECC6, BI, EP are recommended to be done together.
Are there any best practices recommendations from SAP on the same?. Can somebody share the blueprint or any strategy document they are using.
Thanks,
Abhishek

Hi Abhishek,
For the reasons you outline in 2, it is recommended to patch entire business scenarios (i.e. business processess that are coupled integrated across systems) together. Rather than go into a full discussin here, I recommend you see my paper [How To Design a SAP NetWeaver - Based System Landscape |https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50a9952d-15cc-2a10-84a9-fd9184f35366].
Best Regards,
Matt

Release strategy for Transport requests

Hi,
Can anybody give me the detail steps to configure release strategy for transporting requests?
we are having Dev and Prd systems.
Regards,
Vinnu.

Hello,
I hope you have configured TMS for two system landscape.
Just make the transport routes also, make DEV system as a Domain Controler.
Then transport requests will automatically come in to the request queue.
Using tx stms_import , import those request sequentially !!
Note: Points always encourage me to reply !!

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.......

Solution Manager Landscape Strategy

Hi Everyone
Can anyone please point me the document that talks
about Solutiom Manager landscape strategy. Is it recommend to
have Sandbox, Dev/QA/Prod instance of Solutiom Manager or we just need
one instance and connect all other system.
Thank you

I will add my two cents...
A three SM landscape strategy works pretty good:
#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.
This type of landscape satisfies ITIL requirements as changes made to solman itself are migrated from #2 to #3; changes are not made directly in the prod box.
Hope this helps,
Jen

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

Release strategy for quantity contract

Hi Gurus,
In quantity contract .. target value will not filled by the value(in header details) as it is quantityt contract.
We may have different line items with different cost..
my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
please explain/clarify
regards
subbu

Hi,
The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined based upon the total net value of the entire purchasing document.
Cheers,
HT

Release Strategy for SA/Contract/PO

Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
Prabhu

Hi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards

Release Strategy for Contract is not getting picked whereas it is ok for PO

Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
Satish

S0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you

Data conversion strategy for new SOB

Dear Viewers
on 11.5.10
We are creating a new SOB with a change in currency from Feb-11 as this is the requirement
For the same, we need to do data conversion.
I have a confusion for Purchase Orders and Sales Orders
Purchase Orders:
Open purchase orders will be converted, means the unfulfilled PO`s i.e the ones not received and are fully open.
The PO`s which have been recieved but not delivered, Requested the users to clear the intransit receipts.
The PO's which are partially received, what to be done for them?
If a PO is fully received and Delivered will not me converted to the new SOB as its not an open PO
but If invoice comes after Feb-11, than how the matching will be done?
What if a return has to be made moving forward in FEB-11 under new SOB
Sales Orders:
Open sales orders will be converted, that is the ones that have been entered and not yet booked.
Users have been requested to clear off the Sales order lines which are already pick confirmed but not yet shipped, hence they will be shipped and interfaced to AR
For the Sales orders that have been booked, those lines that are not yet processed further will also be converted.
Now what if a receipt comes after feb 11, how to handle this as the sales order wiould not have been converted?
Please give your advise on the data migration strategy for PO`s and SO's.
Please do add any point that may have been missed by me
Appreciate your help
Thanks
Emm

Hi David,
for master data conversion you can use LSMW and the RE-FX BAPIs. (please refer to SAP note [782947|https://service.sap.com/sap/support/notes/782947] ).
Regards, Franz

Release strategy for Schedule lines in SD

Hello All
Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
Thanks in advance.

Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias

Release strategy for Scheduling Agreement(SA)

Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0

Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
   Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

System and landscape estiamte for SCM on Hana for Practice use

Hi All ,
We want to know the System and landscape estiamte for SCM on Hana for Practice use.
Regards,
Abhishek

Hi,
Perhaps this link could help
http://wiki.sdn.sap.com/wiki/display/SMSETUP/MaintenanceofProductintheSystemLandscape
Also check out the note :
For SCM Add-On Products like SAP SNC, SAP EM, SAP F&R the basis component (SAP Netweaver Release) has to be also assigned as relevant Product Instance
Might be helpful, if you check the product versions being reported for the system in the SLD.
Regards,
Srikishan

Landscape Strategy for SM1 & SM2

Similar Messages

Maybe you are looking for