cancel
Showing results for 
Search instead for 
Did you mean: 

Imported Ojects and Basic Objects

former_member201264
Active Contributor
0 Kudos

Hi all,

Can u please explain in brief for following one.

Defference between Imported Ojects and Basic Objects in the integration Repository.

which to use when?

Thanks & Regards,

sreeni

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Kancham,

If you have some objects required in yr component which are already a part in other component then you can define dependency of that SWC in yr SWC ,all the objects tht were part of the dependent SWC comes under the node called Basis objects.

While in yr SWC if you have to import some data types ,interface definition etc which are exteranlly defined and you wish to use them in yr SWC then u import then in the list they are displayed under imported objects

Regards,

**grant points if this info is useful

Answers (2)

Answers (2)

Former Member
0 Kudos

hi,

As explained above , In general , we will create all Interface objects and mapping objects , integration scenario objects ...later these will be used for integration configuration .

Imported Objects :

Also will used to import the RFC , IDocs from external R3 servers , to take the interface structure of idoc or rfcs.. under imported objects . when we imprt these objects , we dont need to create data types, message types,message interfaces , these will be automatically created.

Bsic Objects : we can have the SAP R3 contents like SAP APPL or other already available objects , we can get this type of adding to your SWCV . by doing the depedences in SLD , so that these can be added to your SWCV.instead of creating or copying those namespaces / objects , directly we can refer from your own swcv.

i hope it is clear..

http://help.sap.com/saphelp_nw2004s/helpdata/en/10/8b9c4f1c79024595308d2f4a779c5e/content.htm

Regards

Chilla

Former Member
0 Kudos

Hi,

When developing an interface in XI, we can start from scratch and define all the datatypes, message types, message interfaces, mappings, etc. All of these items are basic objects that make up of what are required to processing a message thru XI.

However, there will be many situation when we will be working with other systems which may already have the interfaces defined, e.g. RFC, IDOC, webservice providers. In these cases, we do not need to define those interfaces from scratch again, we can just import their metadata into the IR and use them. This will eliminate not only much work, but also eliminate errors that might occur if we were to defined them ourselves.

There are also situations we may migrate application from other systems to XI. If those application were developed based on standards, e.g. defined their interfaces in XSD and/or developed thier mappings in XSLT, then we can also import these already-defined objects into XI.

So, the metadata from RFCs, IDOCs, webservices and XSDs, and XSLT mapping programs, when imported into XI are imported objects. RFCs and IDOCs are imported in the "Imported Objects" under the SWCV. Webservices and XSDs are imported in the External Definitions under Interface Objects under the namespaces. XSLTs are imported in the Imported Archives under the Mapping Objects under the namespace.

In addition, when we develop mapping programs using java or message mapping with user-defined functions, we may also use java class which were developed outside of XI. These classes must be imported into XI in the form of JAR or ZIP files. The ZIP or JAR files are imported in the Imprted Archives under the Mapping Objects under the namespace, the same location as for XSLTs.

In summary, imported objects are things developed outside of XI, but can be used by XI. Basic objects are the minimum things needed to process messages thru XI.

Hope this helps,

Bill

bhavesh_kantilal
Active Contributor
0 Kudos

Bill,

<i>Hope this helps,

Bill</i>

have never seen a more detailed and descriptive answer. It has to help

Regards

Bhavesh