NW Dev Studio, CMS, Dev, consolidation and production stack levels

What are the rules for the stack levels when related to NW development. If my nw dev studio is on stack 11 and my SLD CMS is on stack 10 and my target deployment on DEV is stack 8, what are my limitations.? Does anyone know of any restrictions SAP has related to webdynpro development and stack level.
Thanks
Mikie

it is strongly recommended to <b>keep DevStudio and target run-time system on the same level</b>
NWDI servers are release independent, they should contain proper content:
- SLD content should be updated to the "highest" level in landscape (11 in your case)
- CMS should be in sync with SLD
- CBS build space should contain build plugins and libraries corresponsing to the target run-time
NWDS sp11 will produce sp11 compatible components,
if build space contains fitting to run-time (sp8) build plug-ins there are chances to have successful local build, but errors during build on CBS
if build space contains fitting to NWDS (sp11) build plug-ins there are chances to have successful local and central (CBS) build, but problems at run-time.
Hope to not confuse you with all these permutations
Cheers.

Similar Messages

  • In all Systems( DEV , qualituy and Production ) Application data is same?

    Hi SDN team , need clarification from experts.
    Thanks alot for giving me advise to resolve my issues. .Need another clarification also from experts.
    SAP_EXPA(SAP_ALL with cross-client customizing) , can be selected if I  want to transport to  a New system( no clients available) ..Am I right?
    1) using SAP_ALL , i think user'data and roles alos will be copied ..Am I right?
    2) Document says SAP_CUST (Client-specific customizing including authorization profile is copied. The application data is deleted, the user data is retained.)
    here I have a question like
    a) what authorization profile will be copied , is it user specific?
    b) What exactly the  meaning of "Application Data is deleted " I hope in all Systems( DEV , qualituy and Production ) there is same Application data maintained. Pls correct me if I am wrong.
    Thanks in advance
    Regards
    Rajani

    Hi Rajani,
    Below are the answers to your queries:
    1) SAP_EXPA(SAP_ALL with cross-client customizing) , can be selected if I want to transport to a New system( no clients available) ..Am I right? 
    Ans YES (infact it has to be a new system only otherwise Client-independent data and thus all clients in the target system are affected by this and can be destroyed! )
    2) using SAP_ALL , i think user'data and roles alos will be copied ..Am I right?
    Ans YES
    3) Document says SAP_CUST (Client-specific customizing including authorization profile is copied. The application data is deleted, the user data is retained.
    here I have a question like
    a) what authorization profile will be copied , is it user specific?
    Ans YES ( User Master Reacords are deleted)
    b) What exactly the meaning of "Application Data is deleted " I hope in all Systems( DEV , qualituy and Production ) there is same Application data maintained. Pls correct me if I am wrong.
    ANS:
    Application data is dependent upon Customizing data. Therefore, the data can only exist consistently together with it. Application data is always deleted in target clients, with the exception of a copy with SAP_USR or SAP_USER.
    Hope this is useful
    Regards
    Umesh

  • Dunning report difference in dev,testing and prod server in sap

    Hi all..
    we are facing a problem while executing the tcode f150 in dev,tsting and production server.
    while giving the same run on and identification,the different parameters are coming and the status is geting changed.
    in ker,the process is getting compelted,in testing the process is getting sceduled,complete but getting the status as"process completed but job deleted".
    and in production,the status like testing server is coming but some tabs(from the too bar where delete,etc lies)are not getting to see,its not showing up.
    please tell me if we can check it through some tcodes,or eliminate the eorr.
    we are not able to locate the cause behind.thanks in adv.

    Hi chandu,
    In my previous Organisation we got exactly the same landscape for BW as you described.BCS(BAYER COPSCIENCE LTD) operates a BW System Landscape with one centralized  Global Development System and three regional Quality Assurance and Production Systems located in Europe, Asia Pacific and Americas. This Landscape is to ensure consistent data models to be available in all regional systems as well as to minimize development efforts and make use of respective synergies.
    This is perfectly working  for BCS ,and I think, this is the most approriate way of handling of resources.
    Regards
    CSM Reddy

  • Hierarchy Inconsistent in DEV/Q and Prod

    Hi All,
    I created a GL Account hierarchy in DEV, QA and Production separately. I added all the GLs similarly in all the 3 systems, the issue is for some reason one GL Account from the hierarchy is not getting picked in the report output only in Production. On the other hand, the same GL is showing up in the report in Dev and QA. Again when I create a power user report, the amount against that GL show up. I tried all the possible ways to fix this, i tried recreating the hierarchy in prod already twice and every time amounts for only one specific GL don't get displayed in the report output. Can anyone suggest a way to fix this?
    Thanks for your help!

    is your hierarchy generic or sap standard, make sure our hierarchy is activated in rsa6 PRd qas and dev system, replicate the data source in BW system and do a test run and load in to PSA see if its shows in PSA and also check the value in  Hierarchy tcode( dont recall it on top of my head). if it all works then something in the query is cauing the issue could be some filter.

  • Significance of IBase, Component and Product ID while creating Change Reque

    Hello,
    When we create a change request via SOLMAN_WORK_CENTER, we are supposed to provide values for
    1) IBase
    2) Component
    3) Product ID
    Ibase can be defined as the way SAP differentiates in a multiple system (APO, CRM, ECC) environment, the corresponding environment.
    The values corresponding to IBase can be obtained via IB51,52 and 53 tcodes.
    Can the value for IBase obtained via SMSY t code also?
    What does component and Product ID signify?
    Where can we get values for Component and Product ID?
    Is Product ID the same as value we get from menu Option System->Status->Installation Number
    Is it necessary to provide all 3 values (i.e. IBase, Component , Product ID) while creating change request?
    If Not, how will SolMan identify which system the change should point to?
    Or only value for Ibase is enough?
    Thanks,
    Vikas

    Ibase can be defined as the way SAP differentiates in a multiple system (APO, CRM, ECC) environment, the corresponding environment.
    The values corresponding to IBase can be obtained via IB51,52 and 53 tcodes.
    Can the value for IBase obtained via SMSY t code also?
    No
    What does component and Product ID signify?
    Product ID is not mandatory. I actually hide it in the CRMD_ORDER screen.
    Where can we get values for Component and Product ID?
    Is Product ID the same as value we get from menu Option System->Status->Installation Number
    Component  - IB52 as you already mentioned
    Product ID - in a customizing table, I've seen it once but can't remember where honestly. As stated, I don't bother with the field
    Is it necessary to provide all 3 values (i.e. IBase, Component , Product ID) while creating change request?
    The iBase and component are mandatory, odd thing is if you enter the component without entering 1 in the iBase, SolMan will fill the 1 in for you.
    If Not, how will SolMan identify which system the change should point to?
    By the logical components assigned to your maintenance project. You can actually have transports for more than one production assigned to your change document. For instance you could have a BI and ECC transport assigned to the sane change document. Your tak list will have the dev, testing and production systems for each logical component assigned.
    Or only value for Ibase is enough?
    I was having this discussion with someone the other day. Since the logical components assigned to the mianteance project really determines what systems you can create transports for, what is the value of the component field? Best I could determine was when you use the Logon on to System action, it points to the one listed in the component field only. other than that, I'm not sure.

  • How to have an overview on Product Group level

    Hi All,
    Customer want to have a planning in SNP to reflect their several levels of product? For example as the below structure,
    SKU numbers->Sub Brand->Brand-> Product Group
    How to have an overview on Sub Brand, Brand and product Group level?
    Best Regards,
    Bin
    Edited by: Bin Li on Mar 6, 2009 9:44 AM

    Hi Bin,
    You can define your various hierarchies of planning in SNP through Master planning object structures. (/SAPAPO/MSDP_ADMIN - Administration of Demand Planning and Supply Network Planning )
    Regards,
    R. Senthil Mareeswaran.

  • How to Transport changes from Dev. to Quality and production

    Hello Friends,
    I've done the below changes in IR
    1.Added idoc in Imported Idocs
    2.Added new Interface Mapping
    3.Added new Message Mapping
    In ID:
    Chagned Receiver Agreement
    Changed Interface Agreement
    Please let me know how i can move the changes to Quality and Production..
    Pls. provide me the steps to create Transport and how to transfer.
    Thanks in advance!!!
    Best Regards
    Prasad

    Hi,
    By using File system or cms you can transport, better to do the configuration steps manually to avoid ther errors.
    We can do some changes to move
    Moving Dev to QA changes
    1.SLD: are there any changes we need to do.
    If you have common SLD, then I doubt if you may need any changes on SLD side.
    The Business systems you had used will be the same you may use in Q-Landscape.
    2.IR: are there any changes we need to do.
    ---> No changes required, you need to export .tpz file from Development box and have to import it in Q-box
    3.ID: do we need to recreate it fully or after importing,just change the Communication channels will
    do.I am confused here.
    You need to reconfigure all communication channels, if SLD changes are OK then business system will
      change automatically and in communication channel just filled in correct IP/password etc.
    ---> Similar to IR, you can transport these objects also. But you may need to do related changes to communication channels, if you will be referring to different Sender systems and Receiver systems.
    Then as mentioned in previous posts you may need to maintain those Business systems in SLD also.
    4.RWB: such as alerts,and if there are any...
    --> The Alerts will not be transported....you need to create it as new setup for every box.
    Check this link
    http://help.sap.com/saphelp_nw04/helpdata/en/09/88f339db9911d2b41a00609419f767/content.htm

  • Dev and Production BW systems not in sync.

    Hello All,
    We have been using two BW systems for our implementation project. One is the development and second one is production BW system. I observed that few BW objects have different configuration (like update rules, user exits, queries , web templates…etc…) in the production compared to the development system.  Now my requirement is to find out the all the BW objects in the production that having different status than development.  So that I can make corresponding changes in the development system as well in order to sync dev and production systems.
    1.     Is there any tool/transaction is available by which I can retrieve the list of the BW objects and may be delta changes between dev and prd systems.
    2.      Or any standard process exists to sync the both versions.
    Any help to this will be highly appreciated.
    Thanks in advance.
    Regards
    Harsh.

    Hi Harsh,
    For the Transfer rules/update rules you can do a remote compare of the Generated Program which would give you an idea whether they are in sync or not. Likewise you can do remote compare of the User exit fn module.
    Bye
    Dinesh

  • Org.structure differs on dev and production

    Hi,
    I'm developing a workflow and in one of the steps (activity step), I assign agent using organizational structure (position from HR). The problem is, that the org.structure differs on dev system and on production system. Mainly the IDs of position posts differ. How to solve this? Thanks in advance.
    Best regards,
    Tomas

    >
    Tomas Linhart wrote:
    > thanks for answer, I guess that's the best way of handling such situation. I'm going to creat custom table holding position used in workflow mapped to real position ID from org.structure. Or more generally, holding WF post mapped to org.structure type (position, job, ...) with corresponding ID in org.
    I don't see why you need a custom table?
    The org issues aside, all that is needed is to assign your org unit to the task. Then leave the agent assignment blank in your WF. Job done.
    The other option is to create a dummy rule, which you thought was to be avoided. I don't agree, it takes 5 minutes, less effort than a table, less non-standard stuff ==> less explaining to people how to maintain & easier to troubleshoot.
    Edit: Forgot to answer your other question
    > I'm not sure if you consider org. replication the same as transport of org. I was thinking of transport myself, just didn't know the way how to. I've found transaction RE_RHMOVE30 (also acessible from customizing), that should do that, but am not sure, if that's the right one and/or what options to select when transporting. Also, I'm not sure if this would ensure the position/job IDs are the same on both systems.
    Replication would be carried out via transports. The RHMOVE* reports can also be used, or you could even set up an ALE connection between DEV and PRD. However I still would not recommend it. The development system is where you would need to create test users and/or org units. The other alternative is to have a master data client. All of these are a great deal of work which only make sense in certain types of environments - certainly not for the sake of a workflow.
    Edited by: Mike Pokraka on Sep 27, 2009 9:52 PM

  • ONE BI publisher for DEV and Production

    Hi,
    is there anyway I can setup ONE BI publisher for both the dev and production environment. the dev and production are in
    separate boxes? the reason I need to do this is that oracle charges licenses fees for the development as well.
    Thanks,
    Odeh

    Hi,
    Iis technically possible to have two different databases pointing at BI Publisher, but you want to make sure the users can access the correct reports. But what I would say is that it isn't a particular good way to have your environments setup. The point of having a dev and a prod environment is to ensure that things are tested and proof of concept can be carried out without affecting the live systems. I would suggest that the separate licenses is worth the cost from my own personal experience, otherwise you risk having a live environment that is quite unstable.
    Suzanne

  • Best methodology to have dev and production?

    HTML DB users-
    A customer asks what are some of the better methodologies to have a development and production environment with HTML DB? They are used to having controlled releases of new features and fixes into the production environment and want to do that as well with HTML DB.
    We would like your thoughts...
    The customers exact question:
    Our thinking is that we develop in a development workspace and app and then migrate via export and import to a production workspace and app.
    What we have encountered is several issues:
    1) After the workspaces have been set up the user can only point to one at a time.
    2) We get integrity violations in the export an import.
    Is there a better methodology/solution?
    You help is greatly appreciated.
    Cheers,
    -david

    david,
    Different options for separating production from development environment are discussed in this best practices whitepaper:
    http://www.oracle.com/technology/products/database/htmldb/pdf/Oracle_HTML_DB_Best_Practices.pdf
    Do you have more details on the two issues that were raised about the current approach:
    1) After the workspaces have been set up the user can only point to one at a time.
    2) We get integrity violations in the export an import.
    Why can the user only point to one at a time? What does that mean? Can you describe the steps used to export and import and show as error messages?
    Sergio

  • Sql server Configuration option when moving packages from dev env to production env

    hi folks:
      Our SSIS engine is SQL2008R2 and I am in charge of ssis package development and deployment from dev env to production env. 
      This is what I've done using configurations to move packages from dev to production.
      1. on my local machine, I've created a database called SSIS_Config and a table that stores all 
      configration settings
      CREATE TABLE [dbo].[SSIS Configurations]
    ConfigurationFilter NVARCHAR(255) NOT NULL,
    ConfiguredValue NVARCHAR(255) NULL,
    PackagePath NVARCHAR(255) NOT NULL,
    ConfiguredValueType NVARCHAR(20) NOT NULL
    2. on dev ssis server, there is the same table [dbo].[SSIS Configurations] on SSIS_Config db which stores all configurations
    Once package has been deployed to dev env and run with success, I'll move it from dev to prod
    3. On Prod ssis server, there is the same table [dbo].[SSIS Configurations]  on SSIS_COnfig db which stores all configurations
    once ssis pkg has been deployed using deployment manifest, it runs without errors as all production db connection
    will be updated manually in the table [dbo].[SSIS Configurations] 
    Our production env is unique as it's completely locked down and the only way to connect is through remote in session. 
    At this moment, I am maintaining three [dbo].[SSIS Configurations]  tables : on my local machine, on SSIS dev server and on SSIS prod server. 
    This works fine so far as I am the sole developer... Soon, we will have more developers joined to develop ssis package .
    I am wondering if there is anyway to cut the table maintained on my local machine and only use ones on dev server and prod server ? 
    I've tried using the table on dev server to disperse connectionstrings, it works file on dev env.  However, when I deployed to product server,
    since there is no sql connection between dev and prod, the configuration information can not be retrieved and theirfore package is failed.
    Any ideas on how to move packages from local to dev to prod env.? 
     Thanks
     Hui
    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Thanks Nearby BI guy. Am I correct  that  in your SSIS packages, there is only one connection manager which gets ConnectionStr  populated from package configurations which is .xmlconfig
    file and  you then use expressions to populate  connectionStrs of other connection managers through the ssisconfiguration tables? 
    Also for the one on Production environment, the contents of .xmlconfig has to be manually
    changed in order to match the one on production env.
    Is that correct?
    I am thinking about using environment variables to point to the Config Database on each
    local/dev/prod environment, but some environments may have strict policy on the usage of environment variables.
     thanks
     Hui
    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

  • Transporting from DEV server to Production Server

    Dear Experts,
    Like in ABAP and other SAP modules we are having Transport Requests to transport from Dev server to Production server In XI how can we transport all the configuration done by me from Dev server to Production server.

    Hi,
    In XI we can transport in two ways :
    1) File Transport
    2) Using CMS which needs configuration to be done
    Using the File Transport you can easily the Export the Objects and Import the Objects in the Target system.
    Select the Object in the Design or Configuration ->right Click you will find Export option.
    When you select the It creates the .tpz file which can be imported in the Target System
    Using file transfer or CMS we transport xi objects.
    Transporting XI from DEV to QA
    Look into this blog for how to export / improt IR and ID objects,
    XI Software Logistics II: Overview
    XI Software Logistics 1: SLD Preparation
    Transporting IR,ID Objects using File System
    http://help.sap.com/saphelp_nw2004s/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/5e56006c17e748a68bb3843ed5aab8/frameset.htm
    Regards
    Ganga

  • How dev, QA and producation environment would be organized in InfoView

    Hi,
    Please let me know about following things
    1. How Dev, QA and Producation environment would be organized in InfoView
    2. How to navigate among  Dev, QA and Producation environment in InfoView
    3. While login , can we only login for production environment
    Regards,
    Manjunath

    You can definitely have three different data sources (DEV, QA, Prod) leveraged by your single environment. This would be just for reporting data sources though, and not the CMS database itself.
    Reports would be associated with the different data sources depending on the stage of development, and would be accordingly stored in one of three folder trees set up in your single environment. Then access to the trees would be controlled by security set in the CMC.
    Development would take place in the /DEV folder tree, and it would then be moved to the /QA tree for testing, and ultimately the production tree for consumption. Just keep in mind that when you are updating content in the different trees (vs. creating new content) that you will need to overwrite existing content in the trees if you wish to preserve the instance history and CUID (which may be referenced in openDocument links, for example).

  • Release Build for Dev vs. Production environment

    I'm working on a very small project that performs an LDAP
    search using a CFC on our Dev box. The folder structure between
    Development and Production are the same so when I create a release
    build and copy it from the dev environment to the production server
    I get a "send" error on the client. The compiled release build is
    copied to the same folder structure location as it was on the dev
    box, but I believe the application is still trying to point to the
    dev box ip address vs. the production server address. How do I
    handle exporting a release build for a different server than the
    one I'm developing on?

    How is your classpath build up?
    if it's like this:
    SET CLASSPATH=c:\prod;c:\dev
    try
    SET CLASSPATH=c:\prod
    CLASSPATH=%CLASSPATH%;c:\dev
    if that doesn't work try setting your classpath to nothing:
    SET CLASSPATH=%CLASSPATH%
    Please tell me if this helped, I've had a lot of problems with my PATH and CLASSPATH to, and I ain't sure I gave the solution. So please reply to let me know this is the answer or not.

Maybe you are looking for