Strategy/Recommendations for SLD content

Question

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.

Answer 1

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.