technical specification?

[Former Member]

Any one provide me information about the technical specification?

[Former Member · Accepted solution]

Look at this thraed for more info on TS

[Former Member · Accepted solution]

Hi,

Usually technical specification contains:

1) Source and Target system info.

2) Process flow along with diagram

3) Integration Repository objects (DT,MT,MI,MM,IM,External definition,BPM)

4) Integration Directory Objects (Business system and service name,CC sender and receiver,Reciever determination, Interface determination, Sender and receiver agreement.

U have to follow the project specific naming std and used in design and directory.

chirag

[former_member556603]

Hi Giri,

That one is Confidential....We dont have a right to send outside...

If u have any concerns tell me i will guide you..

Table of Contents

1. General Information

1.1. Interface Information

1.2. Associated Documents

1.3. References

2. Technical Details

2.1.1. Flow Description

2.1.2. Flow Diagram:

2.1.3. Technical Specification

2.1.4. System Documentation

2.1.5. Source System Description

2.1.6. Destination System Description

2.2. Integration Repository

2.2.1. Interface Objects

2.2.1.1. Data Types:

2.2.1.2. Message types:

2.2.1.3. Message Interfaces:

2.2.1.4. Data Type Enhancements:

2.2.1.5. Context Objects:

2.2.1.6. External Definition

2.2.2. Mapping Objects

2.2.2.1. Message Mappings

2.2.2.2. Interface Mappings

2.2.3. Integration Scenarios & Integration Processes

2.2.3.1. Integration Process Description

2.3. Configuration objects

2.3.1. Configuration Scenario

2.3.2. Business System / Service

2.3.3. Communication Channels

2.3.4. Receiver Determination

2.3.5. Interface Determination

2.3.6. Sender Agreement

2.3.7. Receiver Agreement

2.3.8. Testing

2.3.9. Test Plan Specification

3. Approval

3.1. Approval Interface Specification

3.2. Approval Test Specification

Based on the Above Steps Prepare Tech Specification ..

Reward points if it is useful...

Thanks,

Satya

[Former Member]

Hi,

Technical Specification is nothing but it is easy way understand the what your requirement.If u fully understand the Technical Spec,u have to complete 30% of the requirement.

Before that The requirement comes in Functional Spec From the client side.the team will be understand the functional spec and it will be converted to the Technical Spec.

Regards,

Sateesh N

[Former Member]

Hi giri,

Technical spec contents vary from Organization to Organization but ultimately it will have all the IR and ID objects and end point details

Skeletal structure of TS :

Name :

orgranization name, scenario name etc

Index :

index table of the contents

Introduction :

where it lists few points about the project and the purpose.Pictorial view of the requirement.

ABAP developement :

if any custom IDOC/ BAPI programs are involved, its listed here.

In few cases, seperate TDs for ABAP and XI is maitained.

XI Developement :

SLD Details :

IR Objects :

DT, MT, MM, IM, MI with names are mentioned here

if DT is to be picked up from a customer structure, the link to the same is specified. Else, name of each field with length, occurance, description is mentioned

sameway, MM rules if exists in a different sheet, a link to it is provided.

ID Objects :

Buss service/ systems used along with the names

CC names and parameters

then finally, links to any other docs, if required.

Regards,

nikhil.

[Former Member]

Hi Giri

Functional specs are inputs from functional or business users what they would like to see in report For eg: Monthly Incoming Orders for all sales organizations for different sales groups and sales offices-customer wise.This is a simple example and u will get different requirements like this.from this starting point u decide to follow Top Down or Bottom approach.First u see from which tables the data is getting stored and u see whether a business content datasource have all required fields coming from this table and ifnot enhance it in source system.Check the relevant objects in BI,if you have business content delivered objects if not create custom "Z" infoobjects,DSO or Infocubes etc..from technical point of view this are technical specifications like specifying similar datatype and length of objects.

if you have knowledge on the client business then you can prepare the functional specifications . Based on the functional specifications technical consultants prepare the technical specifications

follow these links

How to write a technical spec

Technical Spec for Interfaces...

/message/1865271#1865271 [original link is broken]

regards

Sandeep Sharma

If helpful kindly reward points

[Former Member]

Technical spec is a document having all information of scenario ,, wht are the names of softwere component, namespace,data types , messages types,message interfaces,message mapping and interface mappings in IR and including sample structure.

In ID its having all information abt names of busyness service , Busyness sys and communciation channel names and why type of adapter u r using and any value mappings are used or not...

By verifying functional spec we prepare technical spec....

acccording to techncial spec we develop the interfaces...

Technical spec is a document having all informati

[Former Member]

End to end information details of the scenario contained in the technical spec through this we start developing scenario. From functional spec we will prepare technical spec as per the naming standard provided.

Technical specs contains information about : Name of the owner, version management with changedescription,Functionalowner,Businessrequirement,Processflowdiagram,SWCV,Namesapce information, Integration repository information, Integration directory information, Error handling and validation.