SAP XI - Functional Specification Web viewSAP Process Integrations (SAP PI) Project ... Functional...

SAP Process Integrations (SAP PI) Project– Interface Technical Specification –

Section I: Initial Information Requirements(to be filled out by the requester from the business)

1. General Information

Working Name of Interface: UIK1:

Business Owner:

Tel. No.: e-mail:

Business criticality2: Highly critical Critical Non-critical

Reaction time3: Immediate Normal Earliest convenience1Unique Identifier Key2Impact on business in event of failure:Highly critical: E.g. immediate production-stop, significant loss of revenue (reaction time: < 1h, support: 24x7h).Critical: E.g. deadlines missed, delivery delay etc. (reaction time: < 3h, support: every day during daytime).Non-critical: E.g. loss of revenue < 20% (reaction time: 1 working day, support: On working days during normal office hours).3Immediate: Resolution within 2 hours, support 24x7h.Normal: Resolution within the next working day, support during normal office hours.

History:

Version Date Description of changes

0.1 02-03-2010 Document created

0.2

0.3

Issue:This section should cover the issues that are currently unresolved for the interface. It can also be known as a limitation, like the partner number must exist.

1. Issue

Issue Next action

DescriptionPlanned go-live date:

of 9


Description of business process:

<In what business process is the scenario used>

of 9


2. Involved Systems, Message Communication and Interfaces

Overview of Communication<Insert screenshot of the scenario. >

of 9


2.1 Message Communication

Message Details

Frequency5: ? orders per week

Estimated Size6: ?

5Specify how many messages are sent via PI in which period of time (e.g. 100 per day, 10 on the 1st day of month, etc.).6Specify the expected size of an average message (KB or MB). Please note if and when any peak values will be expected.

2.2 Interfaces

Dependencies

Are there any dependencies to other messages known?7

No Yes

If yes, specify

related interface (name/ID)

type of dependency 7E.g. messages of interface x need to be processed before message processing of interface y can start.

of 9


Section II: Technical Development Concept(to be filled out jointly by an PI developer and a system consultant from the business)

Please create Section II for each interface: Copy structure if necessary (e.g. for responses)

1. General Information

Complexity of Development8:

High Medium Normal

PI Developer: e-mail:8Estimated development time (including testing):High: >10 man days (e.g. complex scenarios with complex mappings, ABAP/Java developments).Medium: 5-10 man days (e.g. scenarios with standard mappings, BPM but no ABAP/Java developments).Normal: < 5 man days (e.g. simple scenarios with adapter configuration, without mappings).

2. Overall Process Description

Processing within Sender

Processing within PI

Business Scenario:

A regular mapping is performed.

Describe if there are any areas of interest to developers

BPM:

Additional Description:

Processing within Receiver

IDOC is processed and a MIGO transaction is created.

3. Integration Repository ObjectsSee the Scenario

3.1 Mapping

of 9


Interface Mapping9

Mapping step

Step #10 Mapping

What are the interesting parts of this mapping? For example, why did you use counters or are there details which are difficult to read.

If it is a complex mapping, consider adding an Excel document with the mapping structure. See http://figaf.com/services/pi-documenter.html to create a mapping documentation.

9Should only be completed if it is complex mappings10Repeat line for each mapping step

4. Integration Directory

Scenario

Name:

Communication Channel

Party:

Service Name:

Name:

Type: IDoc RFC XI JDBC Mail JMS File HTTP SOAP Other, Details:

Configuration11: Parameter Value

Images from configuration

11Based on the AE instance type used, enter the configured parameters and their values.

4.1 Receiver Configurations

Routing Condition:

Additional Description:

of 9

http://figaf.com/services/pi-documenter.html


Communication Channel

Party:

Service Name:

Name:

Type: IDoc RFC XI JDBC Mail JMS File HTTP SOAP Other, Details:

Configuration12: Parameter Value

Images from configuration

12Only if the meaning should be explained

Value Mappings

Agency: Agency:

Scheme: Scheme:

of 9


Section III: Operational Support(to be filled out jointly by an PI developer and a consultant from the business)

1. Monitoring

Within Sender (if knowen)

Monitoring Solution13:

Contact information14:

Additional information15:

Within PI




Within Receiver (if knowen)




13Specify the type of monitoring solution (e.g. CCMS).14Enter contact information of person/department/service provider regarding operational support of the corresponding technical system.15Enter additional information on how the monitoring solution works or implement links/files for corresponding manuals.

2. Error Handling within PI

Error16 Area17 Solution18

16Specify the type of error or enter the corresponding error code.17Specify the area where the error occurs (e.g. adapter engine, mapping).18Describe how the error can be solved or implement links/files to referring documents.

of 9


3. Contacts to Solution Owner

Name Tel. No. Availability19

19Specify when the solution owner (somebody from the business) can be contacted in the event of failure (e.g. 24x7, during normal office hours, every day during daytime).

of 9

SAP XI - Functional Specification Web viewSAP Process Integrations (SAP PI) Project ... Functional...

Documents

Transcript of SAP XI - Functional Specification Web viewSAP Process Integrations (SAP PI) Project ... Functional...