Naming convention in a real time XI project

[Former Member]

Hi,

I am new to XI implementation project. I need inputs on how to create a better, reusable, modularized design w.r.t creation of Products, SCV, Namespaces, Data types, Message types, Message interfaces, Message Mapping and Interface mappings, and Integration scenarios.

For Ex: If there is a requirement of PO Invoice integration with source being XML file from a vendor and the target being an IDOC (INVOIC01) file to theSAP ERP system.

What is the better way to create the objects considering reusability across projects ?

1.Do we need to have a separate Product, SCV, Namespace

for Sender and Receiver ?

2.Does the data type and message types are tightly

coupled with the specific sender and target in terms

of SCV, Namespace etc., ? In other words, can we have

a separate SCV, Namespace etc., to hold the data types

message types so that they can be resusable across

any sender or target ?

3.This left with mapping objects which can have a

separate SCV and Namesapce sepcific to

implementation.

4.Finally, the integration scenarios, can we have a

separate SCV and Namespace for sender, Receiver and the

mapping ?

Please suggest.

[former_member206604]

Hi,

Check out this blog this might be helpful

/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation

Thanks,

Prakash

[former_member206604]

Hi

Also check out these blogs

/people/thorsten.nordholmsbirk/blog/2006/07/25/structuring-integration-repository-content--part-1-software-component-versions

/people/alwin.vandeput2/blog/2006/06/07/d-xie-soap-part-4-xi-software-component-architecture-for-point-to-point-scenarios

Thanks,

Prakash

[Former Member]

Thanks for the Blogs. I appreciate that. However i have one question. If we have a third SCV to cater to mapping, can we access the message type and the data types of the sender and the receiver SCVs, in this third SCV ??

[former_member206604]

Hi,

Yes you will be able to access the message types in the third SCV.

Thanks,

Prakash

[moorthy]

HI,

If so, it is always prefer to create a Software component dependency to each other.

To know about this-

/people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies

Regd. Standards etc, refer this -XI faq from Michal-Last part- Best Practices-/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

Regards,

Moorthy

[former_member186609]

Hi, you can use the first version of the naming guide:

https://websmp207.sap-ag.de/~sapidb/011000358700004455192006E/NameConventions.pdf