why we need two namespaces having same interface , what is the use of having two namespaces with same structure

[former_member613349]

In my system somebody created  two namespaces in s/w component with same service interface, I think one namespace is enough to use in ID or else we can reuse the same namespace again  if we needed but what may be the purpose of creating 2 namespaces with same datatype and messagetype, service interface and messagemapping and operaional mapping

[anupam_ghosh2 · Accepted solution]

Hi Satish,

                    The namespace in project reflects many information such as

1. type of sender

2.name of receiver

3.kind of interface say file to file etc.

4. process area say finanace, metering, billing etc

This helps us to locate specific interface quickly.

Thus if there are multiple namespace  with same objects probably the user wanted to create a separate identity because of the reasons mentioned above.

Regards

Anupam

[former_member613349 · Accepted solution]

Hi Anupam Ghosh

Thank for ur reply

I am new to sap pi can u please explain  how can we get to know

the below

1. type of sender

2.name of receiver

3.kind of interface say file to file etc.

4. process area say finanace, metering, billing etc

by creating the two different namespaces with same objects

Regards

Satish

[Former Member · Accepted solution]

Hi Satish

Check both the namespace names. Normally the name space naming convention include the properties mention by Anupam.

1. type of sender

2.name of receiver

3.kind of interface say file to file etc.

4. process area say finanace, metering, billing etc

Exmple :    urn:abc:com/OTC/0059/Invoice/Legacy/Legacy_To_ECC

OTC--is the process area ( order to cash)

0059-- WRICEF or interface ID

Invoice:  The data contains details about invoice

Legacy : sender system

Flow :  Legacy_To_ECC ( legacy will send the invoice and ECC will receive it)

[anupam_ghosh2 · Accepted solution]

Hi Satish,

                   take for example this namespace

urn:myTeltwo.com/Finance/0021/ECC1/myIncar/Idoc_to_File

myTeltwo.com:  Name of the project

Finance: name of the process area to which this interface belongs

0021: Interface seq number

ECC1: source server SAP

myIncar: target server

Idoc_to_File: type of scenario.

Regards

Anupam

[ajeyagv]

Hi Satish,

Sometimes two Service Interfaces with same name may have different structure. During that kind of times having different namespaces come into help. You said you found two software components have same interface name, check whether they have same structure or not. If they have same structure then, you are right. The point of creating another Service Interface with same name and structure was pointless. The person could have used already defined Service Interface.

[Muniyappan]

Hi satish,

we needed but what may be the purpose of creating 2 namespaces with same datatype and messagetype, service interface and messagemapping and operaional mapping

it is not useful creating two namespaces with same objects.

i guess some people might have created for learning purpose.

Regards,

Muniyappan.

[iaki_vila]

Hi Satish,

The only things that i can think for that purpose are:

1. Two different client consumers of  that scenario and the previous programmer wanted the client were identified by the namespace. He needed two different configurations, etc. If this was the point, It would be better to use the party concept in the configuration.

2. The previous programmer used one of the namespaces for his test purposes.

Regards.

[Former Member]

Hello Satish,

are the objects identical? It could be a way of designing the same interface, but implement it in a different manner. This should be well-documented then and it is not very recommendable.

It may be useful to put the two Service Interfaces (Inbound and Outbound) in namespaces of the respective systems, but purely duplicating all objects doesn't make any sense.

Regards,

Jörg