Storage of Incoming Documents (QM-QN-NT/NM) (SAP Library - SAP ArchiveLink

Storage of Incoming Documents (QM-QN-NT/NM)

Use

In the R/3 application component Quality Management (QM), you can use the storage scenarios Storage for subsequent entry and Assignment and storage to store incoming documents in an external storage system.

The following storage scenarios are possible:

Process Flow: Storage for Subsequent Entry (QM-QN-NT/NM)

Process Flow: Assignment and Storage (QM-QN-NT/NM)

Process Flow: Combination of Both Storage Scenarios (QM-QN-NT/NM)

Prerequisites

Technical Implementation (QM-QN-NT/NM)

General Settings for Document Types

Field description	Storage for subsequent entry	Assignment and storage
Document type:	QMILETTER1	QMILETTER1
Description:	Customer complaint	Customer complaint
Operation type:	NCI_INPUT	NCI_INPUT
Object type:	BUS2078	BUS2078
Method:	CREATE	None
Task:	TS00007869	None
Parameter:	TYPE Q1 (notification type Q1)	None

Document type:	QMILETTER2	QMILETTER2
Description:	Complaint against a vendor	Complaint against a vendor
Operation type:	NCI_INPUT	NCI_INPUT
Object type:	BUS2078	BUS2078
Method:	CREATE	None
Task:	TS00007869	None
Parameter:	TYPE Q2 (notification type Q2)	None

Document type:	QMILETTER3	QMILETTER3
Description:	Internal problem notification	Internal problem notification
Operation type:	NCI_INPUT	NCI_INPUT
Object type:	BUS2078	BUS2078
Method:	CREATE	None
Task:	TS00007869	None
Parameter:	TYPE Q3 (notification type Q3)	None

Document Types for Quality Notifications

In the standard system, the following document types are defined for quality notifications:

QMILETTER1: Documents for a customer complaint
QMILETTER2: Documents for a complaint against a vendor
QMILETTER3: Documents for an internal problem notification

The technical document class FAX is assigned to these document types.

See also:

SAP ArchiveLink documentation, section Specific Customizing

Object Types That Are Used

Object technology forms the basis of the interface between the R/3 functions and SAP ArchiveLink. In this SAP ArchiveLink scenario, the system processes the following application object:

Object type BUS2078 (quality notification) (QM-QN-NT/NM)

Standard Tasks:

Standard tasks are single-step tasks provided by SAP that describe the elementary business activities from an organizational point of view. A single-step task refers to one object method (technical connection to R/3 functions) and is linked to the people responsible for processing the object.

Standard Task TS00007869 (ImageAssign) (QM-QN-NT/NM)

Preparation and Customizing (QM-QN-NT/NM)

General Customizing for SAP ArchiveLink

To store incoming documents, you must first make Customizing settings for SAP ArchiveLink:

Maintain global document types
Maintain presettings
Maintain links

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

Customizing for SAP Business Workflow

SAP Business Workflow plays an important role in the scenario "Storage for Subsequent Entry". SAP Business Workflow automatically notifies the persons responsible for processing that an incoming document has been stored and that a quality notification is to be created. Customizing for SAP Business Workflow covers the following:

Maintaining Workflow document types

For the scenarios Storage for subsequent entry and Assignment and storage in QM, the corresponding object type is BUS2078 (quality notification).

Maintaining Workflow parameters

The Workflow parameters specify the quality notification type that the system creates. For the scenarios Storage for subsequent entry and Assignment and storage in QM, the following Workflow parameters are defined in the standard system:

- Method parameter

TYPE (for quality notification type)

- + (Value assigned to method parameter)

Q1 for notification type "Customer complaint"

Q2 for notification type "Complaint against the vendor"

Q3 for notification type "Internal problem notification"

See also:

SAP ArchiveLink documentation, section Specific Customizing

In the QM application component, you do not need any Customizing settings for the scenarios Storage for subsequent entry or Assignment and storage.

Activities

The scenarios Storage for subsequent entry and Assignment and storage usually involve two or more persons responsible for processing at different locations within the company. They must execute the storage functions corresponding to their areas of responsibility.

In both these scenarios, the person scans the incoming documents and assigns them to document types. This step takes place using the functions for storing business documents in the Office menu.

In the scenario Storage for subsequent entry, a second person responsible for processing (in a different department) processes the work items generated by the storing procedure and SAP Business Workflow. In QM, this is usually the person who creates and/or processes the quality notification. The procedure is identical for Assignment and storage, except that SAP Business Workflow is not involved.

For more information, see the following documentation:

Storage for subsequent entry: Assign document types and process work items:

SAP ArchiveLink documentation, section Storage for Subsequent Entry

Assign and store

SAP ArchiveLink documentation, section Assignment and Storage

Process quality notifications:

Quality Management ® Quality notifications