Curso basico CM

8/2/2019 Curso basico CM

1/43


2/43

SAP AG 2004, SAP TechEd / DM251 / 2

Contributing Speaker(s)

Chris Ritterhern,Director of Technology, GEMS Inc.

Ulrich Spinola,Senior Consultant, SAP AG

Joachim BeckerProduct Manager, SAP AG


3/43


Learning Objectives

As a result of this workshop, you will: Be able to work with Cases in Case Management

Be able to configure cases to fit your needs (company specific

processes)

Be able to work with the Registry

Know the basic principles of the Service Provider Framework

(which is the heart of SAP Records Management)

This hands-on session offers you first experience

with the system and gives you an introduction

into system configuration (customizing). Learn

more details in

Extending SAP Records Management and Case Management

Using New Services (DM351)


4/43

Service Provider Framework

Summary

Case Management

Case Configuration


5/43


Summary

Case Management

Case Configuration


6/43


Digital Records

put arbitrary information objects together

(Business Objects, documents, processes)

form a structure (according to the business process)

document business processes (ensure legal compliance)

Digital Cases

actively process tasks

improve foundation for decisions

Digital Documents

scanned documents, stored securely, retrieval supported

create and change documents in the SAP system

ArchiveLink documents, document info records, interactive

forms

New!

SAP Records Management is About Management of


7/43


Case Notes

1 : 1Header data

Case Record(Linked objects)

LogProcessRoute

Case

Sub-components

Overview on Cases And Case Components


8/43


Demo

Demo


9/43


In this first exercise we create a demo case Problem Message

this is not a real life scenario but a demonstration of thefunctionality that is offered in the system.

Start Case Management (transaction code SCASE)

Choose RMS_ID S_CMG_DEMO

Create a new case of case type PMSG (Problem Message)

Maintain attributes of the case.As Header enterProblem Message ##

(where ## is your group-number). Edit a short problem description.

Fill in additional information into Linked Objects.

Create the process route.

Change the status into In Process.

Start the Business Workplace(transaction code SBWP)

Accept your work item and complete it

Exercise 1: Working With Cases (Beginner)


10/43


Records Management System (RMS_ID)

Patient

files

Personnel

records

Budget

planning

records

Dr. Jones,

Orthopaedist

Mrs Yukava,

HR

Mr Smith,

Administration


11/43


Organizer: Element Types And Types

1. To start Case Management use

transaction code SCASE. The Organizeris started.

In the Role Based View you see a list ofavailable Types and Element Types.

Types are preconfigured in the system.

Cases

Records

Business Objects Documents

Element Types are definitions forinformation objects.

2. To create a Problem Message click onProblem Message and choose Create in

the context menu (right mouse click).


12/43


Maintain Attributes And Edit a Problem Description

3. Maintain attributes

of the case (some

attributes are

available as drop-

down-boxes). You can

close the attributes

section.

4. Choose Description

as note type.

Enter your text and

press Copy.


13/43


Move on to The Attached Case Record

5. Click the LinkedObjects button and

confirm that you want

to save the problem

message.

C R d (E t )


14/43


Case Record (Empty)

6. To fill the

attached Case

Record choose

one of the

activitiesCreate orFind.

C R d (P ti ll Fill d)


15/43


Case Record (Partially Filled)

If youve finished to fill

the Linked Objects,

save the problem

message and continue

with the definition of

the process route.

D fi iti f Th P R t


16/43


Definition of The Process Route

7. Insert a sequential process

step and enter your User IDand activity Display.

8. Change the status into In

Process and save your

problem message.


17/43


Summary

Case Management

Case Configuration

Configuration of Cases


18/43


Header

Record LogProcessNotes

Definition of process

specific attributes,

groups, order of attributes

You can add further

subcomponents

Definition of a record

model and the possible

content of recordsDefinition of note types

Definition of the

process route

(workflow tasks, agent

assignment, process

route template )

Definition of a status

profile and how the

system reacts on changes

of the status

You can add additionalfunctions (function

profile) like further

push buttons

Configuration of Cases

Customizing Case Management: Case Type


19/43


The case type bundles allsettings for the case andits sub-components.

Case Type

Settings for

Case Records

Settings for

Case Notes

Attribute profile

Function profile

Status profile

further profilesand settings

RMS ID

Customizing Case Management: Case Type

Implementation Guide / Case Type Definiton


20/43


Implementation Guide / Case Type Definiton

Implementation Guide

for Case Management:

transaction code:

SCASE_CUSTOMIZING

The Case Type

combines all profiles

Example: Attribute Profile


21/43


The attribute profile defines the attributes that are available

for cases of a certain case type.

General attributes for cases are defined in the table

SCMG_T_CASE_ATTR.

To include new attributes, you need to create a new table with

the same key like SCMG_T_CASE_ATTR.

Add the name of your table to the attribute profile and define

which attributes you want to use. You also can define groups

of attributes and the order how the attributes should appear on

the screen.

Example: Attribute Profile

Exercise 2: Configuration of Cases (Advanced)


22/43


Exercise 2: Configuration of Cases (Advanced)

In this second exercise we configure a new case type with slightlydifferent behavior.

Create a new attribute profile ZATPRO##. (where ## is your group number)

the profile includes: Header, Case Type, Company Code, Priority,Created By, Created On, Person Resp., Status

Define a new Case Type CT##(copy PMSG). YourCase Type should use ZATPRO##as attribute profile.

Optional (you need to know SP Framework):

Change the Record Model for the Case Record.

Create a new element type for a Case.

Create a new element type for a Case Record.

Create a new record model for theCase Record and apply your modelto your Case Type.

Test your new Case Type.

Attribute Profile


23/43


Attribute Profile

To use the additional

attribute CompanyCode the trainer created

the database table

ZCMG_T_CASE_ATTR.

Definition of the attribute

profile with rows and

columns for the

attributes.

Header for the new Case

Type definition CT##.


24/43


Summary

Case Management

Case Configuration



25/43


SAP Records Management

integrates various information

objects from various sources

SAP Records Management is not

restricted to a predefined set ofinformation objects but open for

extensions instead

The open infrastructure behindSAP Records Management

is implemented in ABAP Objects

is service oriented (ESA)

can be used in other application

contexts as well (not only

documents, records and cases)

Material

Invoice

Personnel

ContactBusiness Objects

from SAP and

Non-SAP systems

Desktop

Documents

and

Templates

Processes

Web Content

? etc....

How Are Elements Integrated in a Record?


26/43


g

SAP Records Management is based on the Service Provider

Framework. Each service provideris responsible for theintegration of a particular group of elements.

Service provider for Business Objects

Service provider for general documents

Service provider for scanned documents

(stored via ArchiveLink)

Service provider for Process information

(SAP Business Workflow)

Service providers for transactions, reports

Service provider for records and models of records

Examples ofService Providers:


27/43

Example of Entities: BOR Objects


28/43


1 RMS Accounting

2 RMS HR

BOR Object

Type

SP BOR Objects

Element

Invoice

No. 1000100

n

ET Invoice

1 RMS Accounting

2 RMS HR

What is Special With Case Management?


29/43


CaseService Provider

SCMG_SP_CASE

RecordService Provider

SCMG_SP_CASE_RECORD

Subcomponents

NotesService Provider

SCMG_SP_CASE_NOTES

Cases are realized by a Service

Provider that combines other

Service Providers.

Technical View on Case Management


30/43


Case Management runs in a separate area: S_AREA_CMG.

For Cases SAP delivers the following new Service Providers:

SCMG_SP_CASE for Cases

SCMG_SP_CASE_NOTES for Case Notes

SCMG_SP_CASE_RECORD for Case Records (Linked objects)

SCMG_SP_CASE is responsible for the behavior of the Case

and the others determine the behavior of subcomponents.

Another new Service Provider SCMG_SP_CASE_LOCATOR

implements an alternative Search for Cases.

Registry


31/43


Definition of

service

providers and

element types

in the registry.

Youll find Case

Management in:

Application

Registry >S_AREA_CMG

Connection Parameter for SP Workflow,SP ArchiveLink, SP Business Objects


32/43


SP ArchiveLink, SP Business Objects

Demo


33/43


Demo

Case Notes


34/43


The Case Type is linked to an element type forCase Notes.

The element type for Case Notes belongs to the

Service Provider SCMG_SP_CASE_NOTES.

You need to maintain a value for the connection

parameter OBJECT

The default is the SAPScript text-object

SCMG_CASE.

You can adopt this text object to your needs

(activity in the implementation guide)

Case Record / Linked Objects


35/43


When defining a case type you need to maintain an element

type for a case records and a record model.

The service provider SCMG_SP_CASE_RECORD implements

the behavior of case records.

The service provider SCMG_SP_RECORD implements the behaviorof a standard record (which is not part of a case).

Important: when classifying the element type for case records,

do not assign a type and set the parameterORG_HISTORY=NO_ENTRY.


36/43


37/43


Summary

Case Management

Case Configuration

Summary


38/43


SAP Records Management includes tools for the management of

electronic records, documents, cases and processes.

Cases are used to actively process business tasks.

Cases include attributes, Notes, a Case Record (Linked Objects)

and other information that is used in the process context.

It is possible to extend cases by additional components.

Cases are configured by defining a Case Type and some profiles

(attribute profile, terminology profile, status profile etc.

SAP Records Management relies on an open infrastructure: theService Provider Framework.

SP Framework allows to enhance the application by additionalservices (e.g. integration of third party applications).

Records Management / Case Management is included in variouspreconfigured application solutions.

Further Information


39/43


Public Web:www.sap.com

SAP Service Marketplace: service.sap.com/recordsmanagement/

Related Workshops/Lectures at SAP TechEd 2004DM102, SAP Records Management: Cases Drive your Business Process,

1-hr Lecture, BeginnerDM 351, Extending SAP Records Management and Case Management

Using New Services, 4-hr Hands-on, Advanced

BPM101, Interactive Form-based Processes in mySAP ERP 2004, 1-hr

Lecture, BeginnerBPM152, SAP NetWeaver BPM: Build Your Own Workflow, 2-hr Hands-on,

Beginner

Related SAP Education Training OpportunitiesBIT640 SAP Records ManagementE-Learning (Ramp-Up Knowledge Transfer / Online Knowledge Products)

SAP Developer Network


40/43


Look for SAP TechEd 04 presentations and videos on

the SAP Developer Network.

Coming in December.

http://www.sdn.sap.com/

Questions?


41/43


Q&A


42/43


Please complete your session evaluation.

Be courteous deposit your trash,and do not take the handouts for the following session.

Feedback

Thank You !

Copyright 2004 SAP AG. All Rights Reserved


43/43


No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other

software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or

registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein

as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other

countries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group

shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an additional warranty.