Design ,Technical & functional Documents

[Former Member]

We are going to send PO(R/3) to our Supplier network thru XI and also we are going to receive the Invoices into our R/3 System.

For the Above scenario we need the following Documents

1)Design Documentation

2) Functional Documentation

3) Technical Documentation

I want to know what Information I need for the above classifications and also who will be incharge for the above like who will execute the Design Documentation, Who will write the Functional and Technical Documentation?

If there is any useful documents available?

Thanks.

[former_member192029]

Hi

Here you go

https://websmp101.sap-ag.de/~sapidb/011000358700004874282004E

and check the weblog

/people/michal.krawczyk2/blog/2005/04/09/xi--saps-document-templates

Cheers

Jawahar Govindaraj

Message was edited by: Jawahar Govindaraj

[Former Member]

Jenni

Design Documentation tell us how the interfaces are going to work for the entire project. So usually Architects or Senior guys who have indepth experience of XI will usually write this.

Functional Documentation tell us the functioanlity of the interface. This is written by the Functional guys who have indepth knowledge about the functionality what they are looking from the interface. They may even take the help of technical guys to some extent.

Technical Documentation tells us how the interface is going to be worked technically. Here we will mention what are the adapters, naming conventions etc we are going to use for the interface. This is written by the XI developers. This are purely my views and this may change from person to person jenni.

For further info go through the urls:

Regards,

---Satish

[moorthy]

Hi Jenni,

You can follow ASAP implementation Methodology for this.

http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm

<i>1)Design Documentation</i>

>>>Contain entire system landscape design, all interface design, Number of interfaces, Source and Target System Details,Volume of messages, Security, Assumptions,,Naming standards etc

<i>2) Functional Documentation</i>

>>>Specific to Interface level,Mappign Rules, Validations used, Business Logic etc

<i>3) Technical Documentation</i>

>>>For XI developer,i.e it should contain, Mapping Rules, Source Structure,Target Structure, Usage of BPM, Source System Information/Target System Informations like Logical Systems, Business Service/System, IR objects and ID Objects..

Usually Techncial Documentation is done by XI developer, and Design Document is done by Solution Design Team, Functional Document is done by Both different system specialists.

Hope this helps,

Regards,

Moorthy

[Former Member]

Krishan Moorthy, would you please explain these two points in detail

1) Contain entire system landscape design, (We are going to exchange PO and Invoice between our R/3 system and 3rd Party Suppliers)

2) all interface design (We have PO, PO change, Inoice Interfaces)

Thanks

[moorthy]

Hi Jenni,

<i>1) Contain entire system landscape design, (We are going to exchange PO and Invoice between our R/3 system and 3rd Party Suppliers)</i>

>>In this your entire Integration is with Thirdparty Suppliers and the R/3 system. SO you can show this with diagramatically with XI is an Centralized Integrtaion Tool. And it should depict all the systems which all are coming into entire integration of your project. If you have one integration, then it is something like Thirdparty->XI->R/3.. But if you see in broad perspective, this document should give you entire picture of your integrtaion.

<i>2) all interface design (We have PO, PO change, Inoice Interfaces)</i>

>>Each Inteface Description.. SOmething like listing out/Table.

In this list , you need to mention Source system,Target System, How often(Schedule), Volume of messages for each interfaces etc..

Hope it clears ..

Regards,

Moorthy