Best way to come up with Software Components in PI...Please, suggest

[Former Member]

Hi

We have interfaces to be developed for trading partners and we have about 150 trading partners.

Is it a good idea to create one software component for each trading partners, in this case we would have to create 150 software components and a common software component which stores the structure

-

---

(or)----

---

Would you suggest segregating these trading partners in to 5 software components and have about 20 namespaces for each trading partner distributed among these 5 software components...this way we create only 5 SC and distribute the trading partners based on line of business(1 SC for retail, 1 SC for wholesale ....)

So Experts, please suggest your best practice....SC for each trading partner(150 SC) over 1 SC for each line of business and then namespace for each trading partner distributed under the 5 Software components.

Thank you!

[Former Member · Accepted solution]

Hi,

if you create one SWCV or one for each that would be a mess.

sencond option would be the ideal one, which will help in support work.

Regards,

Sukarna.Chirumamilla

[Former Member]

Hi Patrick

What is the business case you have for 150 partners

I prefer first consider the business use case and development type then create the SWCV for them

For example

I have 100 partners and business is Shipment notification -> requirement technically is They will do a Shipment notification post (XML) and data need to be sent to SD in ECC or APO etc.

I will create 1 SWCV for SD and one namespace http://company.com/xi/in/shipmentnotice and all 100 can use this.

Suggestion is don't go by number, keep your system & landscape clean and meaningful

Thanks

Gaurav

[Former Member]

Thank you for your response! Gaurav

We would have a set of EDI transactions for each of the 150 trading partners.

So here is the business scenario:

-We have 150 trading partners

-Each trading partner will have couple of EDI transactions.

-Some of the EDI transactions are common to some trading partners

Eg: 5 trading partners have the same mapping for a few EDI transactions.

From your response I understand it best to reduce the no.of SWC and organize these by a set of namespace under a couple of SWC (based of line of business eg.1 SWC for Retail with namespace for 20 trading partners,2 SWC for wholesale namepaces with 20 trading partners .......)

Gaurav,

Please, do let me know what your best practice would be.....as one more thought to consider is how best we can handle common message mapping(to use one mapping in the case mentioned above where 5 trdaing partners have the same mapping logic for a set of EDI transactions).

Thank you!

Edited by: Patrick Jones on Nov 11, 2008 3:11 PM

Edited by: Patrick Jones on Nov 11, 2008 4:13 PM

[bhavesh_kantilal]

Rather than partner based strcuturing do it on the basis of end systems.

Partners would end up talking to same VAN in most of the cases right?

My normal way of doing it, and it has fit in most of cases is to create one SWCV for every end system and one for the integration content.

All the End system SWCV's will contain the DT, M^T and MI for the corresponding systems and the Integration SWCV will contain the Mappings.

Refer to one of the best blogs on SDN on this topic,

Regards

Bhavesh

[Former Member]

Hi Patrick!

Try to keep it as simple as possible. 150 SWCVs are really not a good idea. But it depends on your requirement. Please keep in mind that the versioning concept of XI/PI highly relies on the SWC/SWCV. So if you create a new SWCV all the objects contained in this are copied to the new version.

I would suggest you to find a (business related) logical grouping cirteria like retailers and so on.

Regards,

Volker