Need example

[Former Member]

Hi Gurus,

What are the conditions where we go for two Software component versions?Real example would be of great help.

Regards,

Alex.

[former_member193376 · Accepted solution]

Hi

Software Component and Software Component Version are objects that are showed at Integration Repository(Design) of XI, when you use the option Tools->Transfer from System Landscape Directory...->Import Software Component Versions...

They are used to encapsulate interface objects relative to the systems that they represent.

For example, suppose that in your company you have a non-SAP system called "Inforoad", used to helpdesk team registers support calls, and you need to integrate this system with the SAP Solution Manager. I will need to have a Software Component for "Inforoad" system, to build the interface objects inside namespaces created inside the SWCV(Software Component Version) - note: this was a real scenario to me ;o).

Additionally, objects belonging to SAP Solution Manager(for example, RFC Functions), may be imported inside a Software Component Version relative to Solution Manager.

As you can see, this is very useful to organize the interface objects that you need to use. Suppose that you create a single "fake" software component version and, inside it you create all interfaces objects, relative to all interfaces between all systems existing in your integration scenario...this will lead to very difficult maintenance, and posterior monitoring of interfaces build in these conditions.

So, basically, it´s a question of better organize your integration environment. There is some times when you will not create a software component version to encapsulate interface objects: when you need a interface between a real system, like SAP or even a non-SAP system, and some type of service, like an interface to send an e-mail: in this case, you will not consider the mail server as a system(do this sounds like consider an Excel Sheet as a System), so probably you will create the interface objects relative to it(data type, message type, message interface, message mapping...), inside the software component version of the sender system, in this example.

I hope this info helps you !

Thanks

Saiyog

[Former Member]

Hi

check these link

Regards,

Suryanarayana

[Former Member]

Hi,

The real and simple example is, One SWCV is just used for importing IDOCs & RFC from R/3 so this SWCV will be dedicated to R/3. And in other SWCV you develope your scenario.

Basically it totally depends upon your project landscape how they want to manage the things...

[Former Member]

Hi Alex,

We have used 2 swcv for one object development where the message interface was developed in one swcv and the message mapping and the interface mapping , ccBPM etc was developed in another swcv.It all depends upon the functional requirements.

Regards,

Arijit

[Former Member]

Hi,

There is no such requirement to create 2 Software components.

the use of SWCV is just the change the version of the SWC.

Thanks,

Madhu

[Former Member]

Hi,

Underlying Software Component Versions

http://help.sap.com/saphelp_nwpi71/helpdata/en/44/63977c40b54ddfe10000000a1553f7/content.htm

Thanks,

Boopathi

[Former Member]

Hi,

If you want you can create the Normal scenario itself with Two SWCV.

and the same time you can create it with a single SWCV also.

I dont think there is such cases that we have to go for 1 or 2 SWCV

Depends on You

Regards

Seshagiri