SLD Naming strategy

I have different application that sends files into FTP in different folders.
Do I need to create <b>one</b> business/techical system in SLD with generic name like FILE_SYSTEM? This system will have several channell in ID.
Or I need to create each business/techical system  for each applicatiuon in SLD.
What are your suggestions?

Hi Sergey,
both is possible. One more alternative is only to create a business service without SLD entries. If you have a good reason to reduce number of directory objects use only one system with more channels; if you prefer a extendable solution (X-Path routing) use more systems with only one channel.
Regards,
Udo

Similar Messages

  • SLD landscape Strategy

    Hi All
    Can anyone please point me to SLD installation/implementation  strategy. Can SLD/Solution Mgr can be installed on the physical box.
    Thanks you.

    Hi Julio,
    SLD is a concept introduced by SAP from its netweaver releases. Yes solution manager can be installed on a physical box.
    For SLD implementation strategy please visit:
    http://help.sap.com/bp_epv170/EP_US/Documentation/How-to/Configuration/Post_Install_SLD_NW_2004s.pdf
    Please award points for helpful info.
    Regards.
    Ruchit.

  • SAP File System Access - SLD Naming Convention/Suggestions

    I would like to access our ECC file system to pick up files we will use to create Idocs.   
    I'm wondering the best way to describe the file system access in the SLD.   
    I have a business system for the main client on the ECC  system (BS_ED1CLNT010) for example but the OS isn't client specific.    I could use this as the Business System in the scenario and define a file adapter that connects to the unix server.
    Any thoughts?

    Maybe I didn't frame my question properly.  
    In the ECC system we have multiple clients (20,30,40, etc).  If I am going to post an Idoc to a client in this system I need to define each as a business system in the SLD and import this to the Integration Directory.    So I would have BS_XXXCLNT010, BS_XXXCLNT020, etc, one for each client.   These all share the same Technical System.    If I want to post an Idoc to a client on the ECC system I have to define a Business System and interface to that and every client that will receive an Idoc. (as well as the ALE settings on the ECC)
    Each of these reside on the same SAP server (sap00001 for example) and there is a directory (/public for example)  on this server.     This isn't client specific.  
    I wish to pick up a file from the ECC file system and post a client on the ECC system (maybe different ones based on the data in the file).   
    I don't want to define the file adapter under BS_XXXCLNT020 since it isn't specifc to client 020 although that would work.  
    Do I create a new TS in the SLD as third party, stand alone java, and a BS for that?    TS_XXX_FILESYSTE (3rd party).  BS_XXX_FILESYSTEM for the TS?
    I'm really looking for clarity in the definition of the SLD.

  • How to configure AS400 System in SLD

    Hi,
    Am in need to configure AS400 system into SLD.  Driver and connection are done. Am in need to add the system into SLD.
    do we need to add AS400 DB2 system as the third party system?

    Prem,
    It depends upon your client standards and SLD naming conventions. If there are mulitiple interfaces to this system, then I would create a 3rd party business system in SLD. After creating you need to assign the corresponding target system, so that when you transport it will take care. Once created you need to import it into your configuration and do your interfaces configuration accordingly.
    Regards,
    ---Satish

  • Difference in SLD for PI 7.1 and PI 7.0

    hi All,
    Can anybody tell me if there is any difference between SLD for PI 7.0 and PI 7.1
    If yes , also please provide the material for SLD PI 7.1
    thanks,
    Loveena

    Hi Loveena,
    Please find below a link to Webinar on 'SAP NetWeaver PI 7.1 and SLD - Upgrade Strategy'.
    [Webinar|https://www.sdn.sap.com/irj/sdn/webinar?rid=/library/uuid/c04ef63b-97c0-2a10-b8bf-a26ef311743a]
    This will surely help you...
    Best Regards,
    Sushil.

  • What are developers​' opinions on how best to handle upgrading large code libraries with multiple apps to new a labview version?

    I have a large set of code that I've painstakingly migrated from one labview version to another over the years.  I have lots of deployed applications that I need to continue to support.  From experience and interaction with other developers, I don't think I can continue to migrate every application to a new labview version when I upgrade going forward.  Every application seems to break in one way or another, the builds don't work right and need to be re-done, and its too much time to get all my applications working and tested again.  That opinion is solidified by NI's policies that make it impossible to install old toolkit versions on new labview versions, for example.  Compatibility is often being sacrificed so NI can develop labview in the direction they choose.  So I have to take the position that whatever version I write an application in will probably need to be maintained in that labview version throughout it's life.
    In light of this, how are other developers managing older applicatiosn written in older versions of labview.  Right now I have a virtual PC on my system with 7.1, 8.0, 8.2, and 8.5 all running on different virtual PC's so I can keep each installation separate.  I strongly recommend this approach.  But keeping my large libraries of code separate is tough.  They are many GB, they all link to each other, and I always get worried even when I separate them in different directories that somehow labview will search in the wrong place and find the wrong version of a sub-vi.  Are other people also trying to maintain separate copies of all their code in different labview versions?  How are other people managing this problem?
    -Devin
    I got 99 problems but 8.6 ain't one.
    Solved!
    Go to Solution.

    Hi,
    The following directory hierarchy, coupled with a "hierarchical" VI naming strategy, have been effective (for me) at preventing "cross-linking" across projects and LV versions. The storage hierarchy was designed for use within an SCC environment, but works fine independently. Hierarchical-naming insures unique names for application-specific files. Use of Project Libraries (in LabVIEW 8.x) addresses the problem of having different VIs with the same name, still, it gives me warm-fuzzies to have app-specific files named uniquely, and I can't imagine not using Hierarchical-naming anymore - it's described at-length in section 2.1 of attached .doc..
    Note: It's been my experience that companies identify resources as supporting specific "Programs", where a Program is related to a product or "family" of products, so, under <Programs> (below) each "Program" subdirectory encapsulates product-specific (or product-family-specific) applications. Also, assuming no SCC tool is being employed the <Production> directory (below) exists as a repository for distributables.  All distributables required to reproduce a test-station should be located under <Production>.
    <Software_Root>
    <Development>
    | <Common>
    | | <LabVIEW_61>
    | | | <Drivers>
    | | | | <DMM>
    | | | | <OS>
    | | | | <PS>
    | | | <Utilities>
    | | |   <File>
    | | |   <Error>
    | | |   <String>
    | | <LabVIEW_711>
    | | <LabVIEW_82>
    | | <LabVIEW_851>
    <Programs>
    * Program-specific applications that (probably) have distributables
    | <Program_#1>
    | | <Application_#1>
    | |   <Docs>
    | |   <Source>
    *       Individual, application-specific, VIs go here
    | | <Application_#2>
    | | <Application_#3>
    | <Program_2>
    | | <Program_3>
    | <Tools>
    *   Tools are NOT "program"-specific, and, may have distributables
    |   <SomeTool>
    |   <SomeOtherTool>
    <Production>
    | <COTS&Freeware>
    | <Programs>
    | | <Program_1>
    | | | <Application_#1>
    | | | | <Application_#1_Rev#1>
    | | | |   Application_#1.bld>
    | | | |   <EXE>
    | | | |   <Installer>
    | | | |   <Source>
    | | | |     Application_#1.llb>
    *           Distributable is created from LLB "snapshot", not directly from development tree
    | | | <Application_#2>
    | | | | <Application_#2_Rev#1>
    | | | |    Application_#2.lvproj>
    | | | |   <EXE>
    | | | |   <Installer>
    | | | |   <Source>
    | | | |     Application_#2.llb>
    | <Tools>
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
    Attachments:
    StyleGuide.doc ‏941 KB

  • Duplicate names in AD

    I need to create 2 user's with same first and lastname in AD.
    We calcualte sAMAccountName, userPrincipalName and CN using rule library.
    We are just incremeting a digit to the about all, and the first and lastname remaing same.
    Our accountId is mapped to a employeenumber and samaccoutname, userprincipalname and cn are derived values and identity template is used.
    I could create a duplicate in IDM but could not in AD.
    Getting error:
    Unable to set user info: 'SetInfo(): 0X80072035: , 00002016: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0 , The server is unwilling to process the request.
    Can anybody tell me why the server is unwilling to process the request.

    Hello Michael,
    the only source for duplicate suggestions and entries I ever noticed came from duplicate Address Book cards (synching problems with Mobile Me) and myself accidentally creating duplicate faces. I spend some time experimenting with the Photo Stream and Mobile Me albums, trying to create duplicate faces by importing from this sources, but that did not duplicate anything. Maybe you can create duplicate faces by importing from face book, but that I cannot try.
    It is very easy to accidentally create duplicate faces without noticing, if you open the "Faces" from the Toolbar and not from the Library Inspector, especially if you have set "limit suggestions to the project".
    If you do that, you will have to enter the full name for a face the first time you use it in this project, and if you type the name slightly different from your previous version, you have created  a duplicate entry.
    It is useful to occionally open faces from the Library Inspector to see all faces, not just a subset restricted to a project or folder,  and to check for duplicate stacks of faces.
    I have adopted the following strategy to avoid the creation of duplicate faces:
    For family and friends (names I have to enter often) I use very short nicknames and prefix those names with an underscore character and disable "limit suggestions to the project". The underscore character as first character ensures that I only will be presented with the names I want, when I start to type the name. (footnote: I noticed that Kirby Krieger recommended a similar naming strategy  for keywords, to prevent duplicate keywords when assigning keywords from the "add keywords" field)
    Faces of people I only met once I label with "limit suggestions to the project" turned on, for their faces will only turn up in one project.
    So there is still the open question what else might cause duplicate faces - let's hope for some more posts here
    - Léonie

  • Outlook syncs duplicate names

    when i sync my nano with outlook i get names duplicated and even triplicated...whats up with that???
    any help is appreciated...

    Hello Michael,
    the only source for duplicate suggestions and entries I ever noticed came from duplicate Address Book cards (synching problems with Mobile Me) and myself accidentally creating duplicate faces. I spend some time experimenting with the Photo Stream and Mobile Me albums, trying to create duplicate faces by importing from this sources, but that did not duplicate anything. Maybe you can create duplicate faces by importing from face book, but that I cannot try.
    It is very easy to accidentally create duplicate faces without noticing, if you open the "Faces" from the Toolbar and not from the Library Inspector, especially if you have set "limit suggestions to the project".
    If you do that, you will have to enter the full name for a face the first time you use it in this project, and if you type the name slightly different from your previous version, you have created  a duplicate entry.
    It is useful to occionally open faces from the Library Inspector to see all faces, not just a subset restricted to a project or folder,  and to check for duplicate stacks of faces.
    I have adopted the following strategy to avoid the creation of duplicate faces:
    For family and friends (names I have to enter often) I use very short nicknames and prefix those names with an underscore character and disable "limit suggestions to the project". The underscore character as first character ensures that I only will be presented with the names I want, when I start to type the name. (footnote: I noticed that Kirby Krieger recommended a similar naming strategy  for keywords, to prevent duplicate keywords when assigning keywords from the "add keywords" field)
    Faces of people I only met once I label with "limit suggestions to the project" turned on, for their faces will only turn up in one project.
    So there is still the open question what else might cause duplicate faces - let's hope for some more posts here
    - Léonie

  • R3_BACKEND Business System.

    I'm trying to complete a SAP example which was taught at a developer course.
    The purpose of the exercise is to implement a simple one-way, asynchronous link between a file sender and the R3 system, using XI.
    When I'm configuring the Receiver Determination at the Integration Directory, it is said to choose  the existing service for the target R/3 system R3_BACKEND. The problem is that the spec R3_BACKEND doesn't exist.
    I suppose i have to create a new service at the SLD named R3_BACKEND which will consist of a RFC connection to a R/3 system. Is this the right way of having the service available? Can you help me with another suggestions?
    Thank you all for your attention

    The scenario I'm trying to implement is an inbound IDOC scenario.
    I've configured the rfc connections on R/3 and the SLD; the ALE settings and XI accounts were already configured.
    Thanks for your guidance describing the steps for the correct implementation.
    In step1 I was missing the creation of the IDOC port on the XI machine. The connection to the R/3 system is fine.
    In step2, the mapping produced no errors. Nevertheless, in the control record (EDI_DC40) I disabled the field maybe that is the problem.
    Step3, the IDOC receiver communication channel was created and checked.
    Step3a, the connection to SLD was checked and was ok.
    I still have some doubts. When all the process is finished and the change list is activated, the IDOC should be automatically generated on the R/3, right?
    Detailed description of my scenario:
    I have a scenario with the following components.
    Test_Scenario
         -Service without party
         - Business System
              --     Legacy_bs
                        --Communication channel
                                  --- File adapter: File (reads from a .xml)
              --    R3_BACKEND
                        --Communication channel
                                  --- File adapter: IDOC
         -Receiver Determination
              -- Legacy_bs |Vendor_out
         -Interface Determination
              -- Legacy_bs | Vendor_out | R3_BACKEND
         -Sender Agreement
              -- Legacy_bs | Vendor_out ||
         -Receiver Agreement
              -- Legacy_bs || R3_BACKEND | CREMAS.CREMAS03
    I'm not finding any mistakes on the configs...Any ideas?
    Thanks
    Gonçalo

  • A Creative ViZen line would sell like crazy

    Some constructi've critisism.
    Creative's archille's heel is that they always come up with crappy names for their mp3 products.
    Why does Creative always come up with names for their products that are hard to remember and easily confused with other products that they have?
    Why can't they just come up with a name that is short and sweet, distinct and easy to remember?The longer the name, the easier it is to forget.
    That's a big reason that the iPod is so huge. The name is so easy to remember and its catchy. There is a certain flow to the term "apple ipod" and it sticks in people's heads. It makes marketing very easy.
    Zen Vision:M ? come on... that's so easily confused with their Zen Vision.. uh is there a Zen Vision Sleek too? I forget... it's hard to keep track.
    ANYWAY its so obvious...
    "Zen" *is* a great base for a name. "Vision" makes sense too because of what the product does.
    But Creative Zen Vision? Yeah its a logical name but it has absolutely *no* ring to it. No flow. It's hard to remember. it makes marketing pretty difficult if people can't remember what the product is called.
    Creative Zen Vision:M is even worse. That's an even bigger mouthful. And what does the M stand for anyway? It's not memorable.
    What's easier to say? What's easier to remember? "Apple iPod" or "Creative Zen Vision:M"?
    So... instead of Creative Zen Vision:M..
    Why not call it simply.. Creative ViZen?
    Sounds like... Creative Vision.. that would be pretty catchy I think... Creative ViZen.
    Something easy for ppl to remember. After all, "creative vision" is a common phrase that everybody has heard hundreds of times. By putting the "Zen" name in it.. i think that would sell alot better than a mouthful / hard to remember name. Why didn't anyone at Creative think of it's It's so obvious :P
    And models can be differentiated with a number to signify gigabytes so this first one can be called the...Creative ViZen:30
    If the next one is 60 gigabytes then obviously it would be called the.. Creative ViZen:60
    People would know the capacity of the product without having to read the fine print! Now wouldn't that be amazing?
    Anyway, their naming strategy needs work.
    A possible conversation:
    "hey what do u have there?""a Creative Zen Vision:M""uh.. creative zen.. whats that?""its like an iPod but better""oh its a knock off"
    this would sound better:
    "hey what do u have there?""a Creative ViZen""oh i've heard of those.. can i see?"
    Just my 2 cents
    Creative ViZen vs. Apple iPod
    that sounds like a winnable marketing fight.and hey.. what the heck does "ipod" mean anyway?!?

    Creative ViZen is more descripti've, catchy and easily attached to the name Creative.
    If you're just some person in the street and hear the word "zen", you think of some buddist meditation thing.
    If you hear the word "vizen", you make a connection to the word "vision" and Creative has made a big step towards brand recognition because it plays on the phrase "creative vision" that *everybody* has heard hundreds and even thousands of times.
    ViZen would be "their own" word.
    iPod is Apple's word.
    Get it's
    Zen aint their word. It's been around for centuries and the word Vision has been around even longer.
    The number of words is less important than the number of syllables.
    apple ipod = 3
    creative vizen = 4
    Creative Zen Vision:M is 7 syllables for crying out loud and it doesn't even tell the casual person on the street what it is. It's clunky and cumbersome. No flow.
    Its also confusing giving 2 products the same name. There is the portable media player and this mp3 player. They just put a :M at the end which means nothing to Joe Blow. What the...
    I am actually more informed that the average person. Ever been to their store/buying page? zen touch zen sleek zen nano zen touch zen etc... and they all look the same. I was confused and I can imagine Joe Blow going to the online store and seeing all this zen stuff, getting all confused and saying "to heck with it, i'll just get an ipod, at least i'll know what i'm getting" Why confuse the customer? Not good.
    Even though Zen Micro is a good name, it doesn't say anything... apart from being a small "zen"
    Creative is seen as a follower but that shouldn't be the case.
    I remember when all they had were sound cards and the nomad, or nomad jukebox and that was years before the iPod. I was lookin for drivers for my sound card and i see a "nomad" thing mentioned. I didn't know what it was until i looked at the product page then forgot about it.
    Even then, they just called everything nomad, which is an odd word and it starts with the word "no"
    Not a good selling point either.
    Creative sure knows how to shoot themselves in the foot when it comes to naming their mp3 products :P
    I heard something about marketing once and it was this. You can have the best product the world has ever seen but if you don't have a marketing strategy, you have nothing.
    Just look at AMD. They are where they are because they had a plan since 999 when they came out with the Athlon cpu. "Athlon" didn't mean anything but that was ok because it was short, sweet and it was *their* word. Now "Athlon" means something and when you hear that word, you think of AMD.
    The main thing is that they gave more bang for the buck vs Intel's cpus. But they also had a strategy when it came to mass appeal and came up with a good, short, distincti've name that is *theirs* I have always been a big AMD fan and was one of the first on their bandwagon. I had bought the brand new, top of the line cutting edge Athlon XP 800+... woohooo! (upgrading now to an Opteron 65 )
    See what AMD does? They *invent* nice words. Athlon, Opteron, Sempron.
    With the Zen Vision:M, Creative is giving more bang for the buck than Apple, but "Zen" and "Vision" are ordinary words that will never be glued to Creative the way that Athlon is glued to AMD or the way iPod is glued to Apple.
    I always root for the underdog that deli'vers more bang for the buck. Which is why I chose AMD over Intel and which is why I would like to see Creative not shoot themselves in the foot with these brutal names.
    I have never owned an mp3 player before but when I do, it will be a Creative mp3 player. *NO* way will I buy an iPod. I was actually considering the Zen Micro Photo but this product is very good too and eventually will probably end up getting a Creative Zen Vision:M... "whatever that is" LOL

  • Library naming and sorting strategy

    Hi all
    I am new to Aperture and before I start importing all my pics I am trying to determine my filing strategy. Basically my pictures consists of Holiday Snaps and hobby Portfolio type pics.
    I am thinking of creating two libraries. One Snaps and One Portfolio. Then categorising by dates then events within each.
    I would be interested in hearing how you guys are organising your pictures so that I can finalise my method.
    Thanks Carlo

    Reading this
    http://discussions.apple.com/message.jspa?messageID=11232422#11232422
    will help you think through determining your filing strategy. Many things work. Try to define your needs. Make practice Libraries (a few Projects with photos) and use them to test your structure.
    I'd put them all in one Library. (What about those great family shots that should be in your portfolio? The ones that you cropped and tweaked -- in which Library? -- and want to re-tweak for something you just thought of?) I would not categorize by date (Ap3 has that built-in). I would settle on a file-naming convention and stick to it rigorously (and I would start every file name with "YYYY-MM-DD_"). The benefits of a referenced Library are more than worth the small set-up cost (in time).
    I now keep three root folders in my Library:
    • New Imports
    • Store & Cure
    • Serve
    I create a new Project for every shoot.
    . Projects stay in the Folder "New Projects" until I have stacked, keyworded, added "Places" information, written a short description in the Project description field (including some text tags I use to track the development of the shots in the Project), and made my initial "selects". Since I am moving tens of thousands of images into Aperture, I find it useful to sequester the Projects which have been imported but not had any "intake" administration done to them or their images.
    . Projects are then moved into the "Store & Cure" Folder, under which I have a full hierarchy of Folders which meet my needs. You may have two second-level Folders, "Family" and "Art Shots". This will allow you to quickly search on one, the other, or both. I do adjustments on my "selects" within the "Store & Cure" Folder.
    . My third top-level folder does not contain any Projects. It is for output. Here I create albums (Smart or otherwise) for each of the Clients/jobs/sets/projects (small "p") that I have -- essentially, every group of images that is going to be output as a group. I have a Smart Album called "Portfolio" here (based on keyword). I plan on setting up two second-level folders: "Active" and "Archive".
    I am, admittedly, overly hierarchical, and wont to expand functionality obsessively. Ap3 gives the user +tremendously useful tools+ for file and image management. I hope my details give you some ideas as to how to best exploit those tools for your needs.

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

  • SLD Strategy

    Hi,
    We are currently installing XI and are looking at a strategy for an SLD....we only have an SLD installed for the XI dev box.
    Is it best to
    i) Create one SLD...but if you have installed it on DEV should u move it to production?
    ii) create two sld's....one for dev,qa and another for production?
    iii) Create Master for full SAP landscape and then have XI SLD read from the Master....and if so do u still have a two XI SLD's?
    Thanks in Advance
    Jim
    Does anyone have any advice or could tell me what strategy they followed.

    Hi,
    Thanks for the advice....
    I just have another question....
    Michal your advice of one SLD seems to tie into all the documentation and makes sense but.....
    When applying SP to J2EE or ABAP can that affect the SLD...
    What my colleagues fear is that we apply or SP to dev,qa and then when you go to production the worst thing happens and the SLD is affected screwing up the system. They feel if you had a seperate SLD at qa or dev you avoid this scenario.
    I don't have enough knowledge to argue this point but i would of thought the SLD is designed not to be affected by any upgrades or SP's.
    Thanks
    Jim

  • Defining an SLD Strategy for XI Migration using CMS

    Can the following scenario occur?  Please explain if any of my assumption are incorrect.
    -> An XI DEV, QA, and PRD environments each with a separate "slave" SLD.
    -> A separate "master" SLD that contains all XI dimensions (i.e. transport, solution, and technical).
    -> This "master" SLD will deploy all relevant SLD components (Products (versions), SC (versions), Technical Systems, and Business Systems) to the specified SLD "slave" environment.  For instance, the master SLD will provide only DEV SLD components to the DEV "slave" SLD specific instance.  No QA or PRD SLD relevant components will be stored on the DEV "slave" SLD. 
    -> All Integration Repository (IR) and Integration Directory (ID) objects will be exported from DEV "slave" SLD and imported into the "master" SLD.
    -> All ID components will have transport targets defined in the master SLD for DEV to QA and QA to PRD, respectively.
    -> CMS will perform all transports from DEV to QA and from QA to PRD for both IR and ID components by defining "tracks" for specific SC and development configurations for each of the development states of an SC.

    The following scenario can occur.  That's what we're doing at our customer site.
    -The only thing is that you can import QA and PRD relevant components to DEV.  If you want to define the transport targets between the systems, then this information will need to be the individual SLDs (slave SLDs).
    I hope this helps.
    Regards,
    Jay Malla
    SAP XI Consultant
    Licensed To Code

  • Strategy/Recommendations for SLD content

    Hi All,
    lets take below business case of a project:
    there are 3 non-SAP applications.
    nonSapApplOne_Java
    nonSapApplTwo_DotNet
    nonSapApplThree_CustomLegacy
    there are 2 SAP applications.
    sapApplFour_ECC6_Module_HCM
    sapApplFour_ECC6_Module_FICO
    sapApplFive_R3
    I would like to know the options/recomendations for creating Products/SWCVs and BusinessSystems.
    e.g.
    should we create each product for each application (for each sap and nonsap applications)?
    should we create one product for nonSAP applications, and one product for SAP applications?
    should we create one product for entire project, and a SWCV for each application (for each nonsap and sap application)?
    or can we represent/separate the applications by namespaces within same SWCV?
    should we create a separate SWCV for storing the objects that use multiple applications design objects e.g. mapping objects, process integration scenarios etc.?
    for each SAP module like HCM, FICO, should there be different namespaces when integrating with other applications.
    do we need to use business system groups for organising sap and nonsap business systems.?
    these mostly need to be designed/decided in the beginning of the project, as it forms the base of the rest of the deveopment.
    Can you pls share your comments and recommendations for above kind of queries.
    thanks in advance,
    Madhu.

    should we create one product for entire project, and a SWCV for each application (for each nonsap and sap application)?
    I am not sure what is meant by a Product! The creation of a SWCV should be related to a business unit that your organization has (at least we follow this practice). Suppose your organization has three Business Units (Sales, Manufacturing, Maintenance) then in such a case you can create three different SWCV with each containing BU-specific development. So all the development related to Sales will come under the SWCV for sales and so on.
    or can we represent/separate the applications by namespaces within same SWCV?
    answer as implied above.....not a good practice to develop namespaces based on the applications...namespaces should be related to the interface name...say you have an interface for salesorder transfer from system X to Y then your namespace should reflect salesorder in it and if you have multiple salesorder processes then you can append some terms to the NS which will help differentiate between the individual SO processes.
    should we create a separate SWCV for storing the objects that use multiple applications design
    objects e.g. mapping objects, process integration scenarios etc.?
    If you mean object reuse...then you can define a common namespace within a SWCV and develop the commonly used objects in it and then refer these in other flows (namespaces) defined within the SWCV.
    for each SAP module like HCM, FICO, should there be different namespaces when integrating with other applications.
    Suppose you have 5 different Integrations involving HCM ---> FICO (or other combination) then your namespaces should be in such a way that there is a clear differentiation between the 5 integrations
    For more information on how your objects should be defined you can go through this document:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90b213c2-d311-2a10-89bf-956dbb63aa7f
    All the above mentioned points are my personal...the implemenation should be in accordance to the best practices suggested by SAP and secondly according to the organizational needs.
    Regards,
    Abhishek.

Maybe you are looking for