Storage of Incoming Documents (PM-SMA-SC) 

Use

In the Service Management (SM) application component, you can use the SAP ArchiveLink to store incoming documents in external content servers.

See also Business Background (PM-SMA-SC).

 

Prerequisites

Technical Realization (PM-SMA-SC)

Document Type

The following global document type for "storage for subsequent entry" in the SM application component is already defined in the standard system:

Field Description

Content

Document type:

PMISERVICE

Description:

Service notification

Operation category:

NCI_INPUT

Object type:

BUS2080

Method:

CREATE

Task:

TS00007869

 

Object Types Used

The interface between the R/3 functions and SAP ArchiveLink is realized using object technology. In this SAP ArchiveLink scenario, the system processes the following application object:

Object Type BUS2080 (Service Notification)

Standard Tasks

Standard tasks are single-step tasks provided by SAP which describe simple business activities from an organizational viewpoint. In each case, a single-step task refers to one object method (technical link to R/3 functions) and is linked to the people who can process the object.

Standard Task TS00007869 (ImageAssign)

 

Preparation and Customizing (PM-SMA-SC)

General Customizing for SAP ArchiveLink

In order that you can store incoming documents, you must first make Customizing settings for SAP ArchiveLink to maintain the following:

For more information, see the sections Special Customizing and Presettings for Storage Strategies in the SAP ArchiveLink documentation.

Customizing for the SAP Business Workflow

The SAP Business Workflow automatically informs the people responsible that an incoming document has been stored and that a service notification must be created. The Customizing for the SAP Business Workflow includes the following:

For the scenario of storage for subsequent entry in SM, the object type is BUS2080 (service notification).

In the standard system, the following workflow parameters have been defined for storage for subsequent entry in the SM application component:

TYPE (for service notification type)

See also:

The section Special Customizing in the SAP ArchiveLink documentation.

 

Activities

The scenarios for storage for subsequent entry usually include two or more people who work at different locations within the company. Each of these people must execute the relevant storage functions depending on their task area.

When storing for subsequent entry, one person scans the incoming documents in a storage unit and assigns them to document types. This is performed using the storage functions in the Office menu.

When storing for subsequent entry, a second person (in a different department) processes the work items which have been generated by the storage operation and the SAP Business Workflow. In the SM application component, this is usually the person who created and/or processed the service notifications.

For more information, see the following documentation:

The section Storage for Subsequent Entry in the SAP ArchiveLink documentation.

PM - Service Management: Service Processing