Test

How to Use Interface-Documentation
on SAP Solution Manager

Ulf Kretzschmar,
SAP Deutschland AG & Co. KG

NetWeaver Process Integration

Motivation



Get a link between Business Process and assigned Interface Central repository to maintain the documentation for the complete processes (including interface documentation) Needed for Business Monitoring of interfaces using the SolManGraphical overview to give everybody the same understanding of the whole process / landscape






© 2010 SAP AG. All rights reserved. / Page 2

Agenda

1. New functionality for Interface Documentation (ST SP15 and ST SER2008_1) 2. How to structure / name Business Scenarios – possible ways
3. How to document Interface Scenarios

© 2010 SAP AG. All rights reserved. / Page 3Structure on Business Scenario Level – already existing
Business Scenario:
Used to group business processes The following hierarchy applies:



Business Scenarios



Business Processes



Business Steps

© 2010 SAP AG. All rights reserved. / Page 4

New functionality in Solution Manager (as of ST SP15 /18 and STSER2008_1)
New structure element in Business Blueprint structureto link Interfaces to the related Business Processes
Interface Scenario:

Hierarchy elements for interfaces

 

Interface Scenario

Interface
(with attributes) Interface Step (with attributes) – used for e.g. ALE scenarios

© 2010 SAP AG. All rights reserved. / Page 5

Agenda

1. New functionality for Interface Documentation

(ST SP15 and ST SER2008_1)

2. How to structure /name Business Scenarios - possible ways
3. How to document Interface Scenarios

© 2010 SAP AG. All rights reserved. / Page 6

How to structure / name Business Scenarios => Benefit


Interface Steps:


represent actions which are related to business process



responsible for data transmission like send an Order IDOC or receive Invoices
Steps have to be placed in order as theyare used





Why using Interface Steps on Business Scenario Level?


The business level serves to document the Business Process themselves The step from and to PI can be used to create test cases To get all involved systems in the graphic for a complete process view Also needed / used for monitoring To get the possibility to link business scenario and interface

   

© 2010 SAPAG. All rights reserved. / Page 7

How to structure / name Business Scenarios => Logical Component
 Logical Component is an administrative entity which assigns logical systems,

in the entire system landscape and across projects, to the following:



a main instance of a product with a product version
the system roles or phases in a project

 for Interfaces the following entriescan to be used
  

SAP to SAP (ALE) and vice versa SAP to nonSAP and vice versa using PI SAP to nonSAP and vice versa using middleware X

=> sending SAP system e.g. Z_ECC_AFS, => Z_PI_7_ 1 => Z__

© 2010 SAP AG. All rights reserved. / Page 8

How to structure / name Business Scenarios => Naming Rules
 

The names for this steps should be picked up from an interface list /database where all interfaces have unique ID’s It should be a combination of:
IF__[xxxx]
  

IF_
IF ID_ [xxxx]

– stands for Interface
– Interface ID number taken from Interface data base - If the process on sending side is the same for multiple receivers then you can put more then one ID in the name e.g. IF_IF1176_DailySales&CustomerRet IF_IF2272_DailySales&ReturnsToRMS could then move toIF_IF1176_2272_DailySales&CustomerReturns



Logical Interface Name (NO system information)
STEP Name
e.g.IF_0123_SPOTransmissionToSourcing

e.g.

Logical Cpomponent
or SAP system (ALE)

e.g. Z_PI_7_1 or
e.g. Z_ERP_AFS / Z_ERP_FI/CO

e.g. IF_0125_SPOConfirmationFromSourcing
© 2010 SAP AG. All rights reserved. / Page 9



How to structure / name Business Scenarios Business...