Namespaces 

Definition

Namespaces in the Integration Builder are namespaces in the sense of XML namespaces that are sub-divided further into semantic units within the Integration Builder software component versions. Objects of a namespace can only be shipped as part of the corresponding software component version and not separately.

The SLD also works with namespaces but these have nothing to do with the namespaces of the Integration Builder (see: Namespace).

Use

General

Each object for a namespace has a unique name within this namespace. An object is identified uniquely by a namespace + object name.

Basically, a namespace in XML can be any constant value. Note the following two conventions:

Conventions for XML Namespaces

Prefix	Use
http://	When you specify an HTTP address as a namespace this does not mean that you can access additional information about the namespace from this address (in some cases an XML schema definition is hidden behind the address). The HTTP address used merely ensures that the name of the namespace is unique. SAP namespaces adhere to the standard http://sap.com/xi/<Name>.
urn:	Namespaces with this prefix have no value in the sense that they are not connected with a web page in the Internet.

It is assumed that conventions ensure that namespaces are unique.

Also see: http://www.w3.org/TR/REC-xml-names/

Namespaces

To create objects (mappings, interfaces, Business Scenarios) in the Integration Builder, you must create at least one namespace for an imported software component version. Each software component version can have multiple namespaces. A namespace can be assigned to multiple software component versions, but only one software component.

Predefined Namespaces

Besides the namespaces you create yourself, there are also some predefined namespaces. The table below contains some examples:

Namespace	Use
urn:sap-com:document:sap:idoc:messages	Namespace for imported IDoc interfaces
urn:sap-com:document:sap:rfc:functions	Namespace for imported RFC interfaces
http://sap.com/exchange/MessageFormat	Internal namespace for fields in a message header

Integration

Whether objects from one namespace can reference objects from another namespace depends on the type of object and on the software component versions that the namespace is assigned to. See:  Object References.

Namespaces for one software component version are usually transferred to the subsequent software component version. However, it is also possible to delete empty namespaces and to move existing namespaces to other software component versions.