Moving documents stored in NW04 internal DMS to external content server ...
Hi all !
is it possible to move documents, stored in NW04s databse (DMS) to an external content server;
we want to swap all documents to an content server;
thanks
oliver
Hi,
We have to do the following post install activities to connect to Content server from DMS.
On SAP Systems (ECC) using CSADMIN t-code we have done the following post installation steps to check whether Content Server is reachable from SAP system.
When use hit CSADMIN option on the screen
Here we need to uncheck the Check Signature check box as we are not using certificates.
Here we need to give HTTP server (Content Server ) info like host name and the port number service is(1090) running.
2. Using OAC0 t-code create Repository on SAP system (ECC)
Then from here Hit CS ADMIN to create rep on Content Server.
Thnaks,
Tanuj
Similar Messages
-
DMS Document Storage in External Content Server
Dear All,
We are working on a DMS scenario, where we need to store the document in an external content server, and not in SAP DB. We are evaluating the solutions around the content server, and we see that SAP provides a HTTP Interface to SAP Content Server, and this interface can be configured through OAC0 and OACT, and managed through CSADMIN. Now, a set of questions:
1. If we intend to use SAP Content Server, do we need to purchase additional license for it? Our understanding is that the software is delivered with SAP Installation DVD, and as such no licensing charges are required.
2. If we DO NOT intend to use SAP Content Server, and rather use an external content server (Possibly utilizing the File System at the OS level as a repository), how will the configuration of OAC0 and OACT look like in such a case? We definitely can not use HTTP Content Server as storage type, How will the entries be organized in this case?
Has anyone worked on a scenario like this? It will be really nice if you can share your experience and expertise in this regard.
Awaiting replies.
Thanks and Sincere Regards,
SidHi Ravindra,
Thanks for the clarification. Do I understand correctly that, for a external content server (without an installation of SAP Content Server) also, we need to specify the storage type as HTTP Content Server ? But in such a case, how will the work processes be handled? As I understand, SAP Content Server engine will handle the incoming/outgoing requests through a Web Server. So, don't we need a similar arrangement for an external content server also? In that case, will the connection parameters be for a HTTP Content Server or for RFC Archive, where we can specify a RFC Destination of type G and connect through it?
Thanks and Regards,
Sid -
Confuguration of DMS using an external content server and KPRO
Hello all,
I am working in a new EH&S SAP environnement.
The aim is to configure a DMS to link EH&S with an external content server Documentum using Kpro.
I have done the following IMG activities:
- Specify Content Servers (Tcode: OAC0)
- Maintain Categories (Tcode: OACT)
- Specify links
- Specify Data Carriers
- Define document types
- Assign EH&S Document Types to Data Carriers
But i am facing to the following problems:
- CG36VEN: error: "could not create report for specification XX, variant XX and lang. EN.
- CG34: error: cannot display document MSDS
- CG4B: error: cannot display document TEST
Are there other actions to be done in the IMG activities?
Any idea to help me please?More details:
I am working in a new EH&S SAP environnement.
I have installed a new DMS link witn an external documentum content server and he is working fine.
My aim is to configure EH&S to link SAP EH&S with my DMS.
Actually my connexion between EH&S and DMS is not working.
Can you tell me what are actions to be done to link EH&S to my DMS.
Thanks,
Ludovic Roux -
Hi All,
Plz let me know that how the DIR is getting path of content server where it needs to get saved.
Means i want to know that where we have to put the path of Content server into the system(SPRO) .I found some place to put the same in "Define Data Carrier" but still i am not getting that how the DIR if finding that particular path..how it is linked as we put only Storege category during CV01N not datacarrier anywhere.
Thanks & Regards,Hi,
Content servers are used to save large quantities of documents, either within SAP Media on the SAP database, or in an external system via an SAP-certified interface. The Document Modeling Workbench in SAP Media is structured so that one document class (for example, a physical storage place) is available for each business object. A content server therefore contains one memory space for every business object. In SAP Media Systems, documents are stored in the SAP Media database or on an external content server.
Using Content Server with database storage gives you a very stable, secure and fast environment. You can store documents in R/3 as well, but that is really only a good solution for few documents.
Additional information is available in the SAP Library under SAP R/3 and R/3 Enterprise ® SAP R/3 Enterprise Release 4.70 ® SAP SAP NetWeaver Components ® SAP Web Application Server ® Basis Services/Communication Interface (BC-SRV) ® ArchiveLink (BC-SRV-ARL) and Knowledge Provider (BC-SRV-KPR).
You can also check the document available on KPro
http://help.sap.com/saphelp_erp2005/helpdata/en/15/aea9375d79fb7de10000009b38f8cf/frameset.htm
KPro is mainly used to store and retrive content from Content Server.
Also check this link for KM,
http://help.sap.com/saphelp_erp2005/helpdata/en/42/d289ba46076bb2e10000000a1553f6/frameset.htm
Hope this helps.
Regards,
MRK
(reward points if useful) -
Linking a CRM case to a document in an external Content server - CRM 6.0
Hi,
We are creating a case from a scanned document, the document is stored in a separate content server. Now we need to link the created case to the scanned document in the content server. We need to be able to access the document/image from within the create case using WebClient
Kind RegardsPradeep,
Yes my users are over a 10 state area geographically, with u201Cpotentialu201D handheld access to the documents that would be attached to functional locations and equipments using the CV0*N access. They would have no need to u201Ccheckout/checkinu201D documents in the field, but would need view access or print access from their field device via a work order wrote against the equipment or F.L. to which the documents would be attached. I envision a separate small group of users that would actually u201Cmanageu201D the documents themselves such as u201Ccheck out/update/check back inu201D to the separate server location where the file(s) are located.
I understand in principle (I think) the DMS storage, but again, if I select u201Ckprou201D (currently unselected for my document type) you make the following comments: u201C2. 'kPro Storage' option (may store in SAP DB,HTTP Content Server), herein you can store 'n' originals/documents and 'n' additional files, AND
HTTP content server You may either use the SAP Content Server or an external/third-party content server.Typically, content server is opted for when operating in a distributed environment(users accessing from several locations)/index based search is needed/n:n mapping scenario exists.
Logical repository
This storage type allows access to different physical repositories, independently of the client and the system ID.u201D
So based on these comments, are you saying I should select u201CKprou201D for my particular document type and that I should define the external server as either an u201CHTTP content serveru201D or either a u201Clogical repositoryu201D? If yes, then as I commented in my 1st ask, please advise how u201CI should use for "Maintaining the Storage System" since based on the selection of "Storage Type" whether HTTP content server or Structure Storage System, or Logical repository decides how the rest of your screen looks for further selection.u201D Thanks in advance. -
Storing of HR documents with archive link in DMS?
hi experts,
how to store HR documents with archive link in DMS?
i found somewhere it is possible with tr. code OAWD,OAAD
is helpful..or is there any other way for storing HR documents
becz i am not able to do it..
if any one guide me it will be very helpful to me.
thx..pts will be awarded be sure..hi sam ra,
SAP ArchiveLink - Scenarios in
Applications (BC-SRV-ARL)
SAP ArchiveLink® is one of the SAP Basis cross-application communication interfaces between
the SAP System and external components. External components may be general desktop
applications or external storage systems. The integration of SAP ArchiveLink in the various SAP
applications enables the storage scenarios explained in this cross-application documentation.
The documentation is structured as follows:
An Introductory Section (Seite 10) containing general information about storing using SAP
ArchiveLink and about the following documentation
An application-specific section for each SAP application component (for example, FI, SD,
HR) with the relevant storage scenarios
For information on related areas, see the following documentation:
SAP ArchiveLink (Extern)
SAP Business Workflow (Extern)
Archiving and Deleting Application Data (Extern)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink - Introduction
April 2001 9
SAP ArchiveLink - Introduction
The following sections contain general information about this scenarios documentation.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink and Application Scenarios
10 April 2001
SAP ArchiveLink and Application Scenarios
SAP ArchiveLink® is one of the integrated interfaces in the SAP Basis System that can be used
to store all kinds of documents in external content servers.
SAP ArchiveLink therefore complements the existing range of SAP application software. For a
detailed description of SAP ArchiveLink, see Introduction to SAP ArchiveLink (Extern).
The SAP application components, for example, SD, FI, HR and MM, support storing using SAP
ArchiveLink by providing various application scenarios. Inbound documents, outbound
documents, print lists, archive files, desktop files and binary files are supported.
How the inbound documents are entered in the system and forwarded for processing and storing
depends on the storage scenario used. For information about the possible Storage Strategies
(Extern) , see the documentation SAP ArchiveLink (Extern).
This documentation describes the storage scenarios that are integrated in the SAP applications,
for example, how Sales and Distribution (SD) documents can be stored in external storage
systems using SAP ArchiveLink.
Archiving in databases using the ADK (Archive Development Kit) is not the same as
storing using SAP ArchiveLink.
For informationen about data archiving using the ADK archiving transaction, see the
documentation Archiving and Deleting Application Data (Extern).
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink: Overview
April 2001 11
SAP ArchiveLink: Overview
Background
There is a growing trend nowadays to transfer stored data from paper/microfiche to external
content servers (for example, archives). Companies are obliged by law and/or internal
standards to keep documents for a certain length of time. Traditionally, paper archives or
microfilms have been used, but these methods are very expensive, either due to copying costs or
the large amount of space required by such archives. By contrast, electronic storing methods are
a much cheaper option and represent an important part of the paperless office concept.
SAPs R/3 System supports a variety of business processes, which can involve documents both
in paper form and in electronic form. The documents either serve to trigger all kinds of processing
steps in FI, SD, HR and so on, or they are documents relating to processes in one of these
application areas.
When linked to SAP applications, content servers and the SAP ArchiveLink interface allow
flexible access to all document searches available in the SAP System and can therefore lead to
considerable time savings. In addition, a combination of the SAP System and SAP ArchiveLink
allows users multiple access (parallel and direct) to stored documents from their work center
without the need for time-consuming searches, which guarantees faster access to documents.
The subsequent sections of this documentation describe the integration of SAP ArchiveLink in
the functions of various application components within the SAP System.
Concept
SAP ArchiveLink provides the following interfaces:
User interface
Application Interface
This interface consists of function modules, which must be integrated in the SAP
applications, if SAP ArchiveLink functions are to be used.
Business objects are linked to stored documents and object methods are available that
allow storing using SAP ArchiveLink to be integrated flexibly in SAP Business Workflow.
Interface between SAP and external components and general desktop applications
External components may be HTTP content servers, for example. General desktop
applications may be MS Word and MS Excel, for example.
Positioning SAP ArchiveLink
SAP ArchiveLink enables
Incoming documents to be stored in the SAP System
Information from the SAP System (for example, outgoing documents and print lists) to be
stored
Direct access from SAP application components to stored documents
Integration of external content servers with the SAP System
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink: Overview
The SAP ArchiveLink-specific Terms (Extern) document, technical document class, document
type, object type and synchronous storing and asynchronous storing are explained in the
SAP ArchiveLink documentation, which also contains information on the Administration Concept
(Extern) (content servers, links and link tables).
Technical Basis
Links from documents to business objects are created by the generation of a link table entry,
which contains both a unique identification for each business object using the object type and
object key and a reference to a stored document using the content server ID and a unique key for
each document stored in this content server. It is therefore possible to create a link between a
business object and any number of documents using a simple 1:n relationship in a table. No
entry is required in the application tables in which the business objects are managed. If the link
table entry for an stored document is deleted, all references in the SAP System to this stored
document are also deleted. This technique allows the options for accessing stored documents to
be integrated flexibly into the SAP System.
Application Interface
The interface to the SAP applications contains the following functions:
Linking business objects with stored documents
This function is used to display, retrieve or store stored documents directly from the
business object. An example of this is the link between an F1 business object invoice
and original invoices that have been scanned into the system.
Linking business objects with stored outgoing documents
This function is used to store documents generated using SAPscript and link them with
the relevant business objects. Examples of documents are outbound quotations, order
confirmations, purchase orders and invoices.
Storing print lists
The process for storing print lists is the same as for outgoing documents.
As of R/3 Release 4.6C, application objects archived in data archiving (ADK) are not
stored using SAP ArchiveLink, but rather using the Content Management Service
(Extern) of the SAP Knowledge Provider (Extern) (KPro).
Integration Status
Many applications in the SAP System are linked directly or indirectly with SAP ArchiveLink:
Direct link
FI
MM
SD
Indirect link
Via the DMS (document management system): MM, PP,...
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink: Overview
April 2001 13
SAP ArchiveLink is centrally integrated in the DMS and all applications with object
links to the DMS are therefore linked to SAP ArchiveLink.
Via MC (Message Control): MM, SD,...
The integration of SAP ArchiveLink in message control allows outgoing documents to
be stored.
Via SAPconnect and the Business Workplace: Faxes
Inbound faxes can be processed directly in the Business Workplace, stored and
linked with business objects without having to be printed first.
Generic Object Services
For R/3 Release 4.0A, generic object services are provided for four SAP ArchiveLink
functions via the system menu for all SAP applications.
From the business objects implemented in the SAP applications, four SAP ArchiveLink functions
can be executed in all applications and independently of which application is involved:
You can display the hit list of stored documents
You can assign stored documents subsequently to a business object.
You can store documents in dialog
You can create a bar code for a business object
These functions are integrated into all SAP applications via object services. There is no need for
special function modules to be integrated in the applications. For more information, see Generic
Object Services (Extern).
For these functions to work smoothly, object orientation in the SAP application and
support of object services are important.
For more information, see Business Context Facilities and Generic Object
Relationships (Extern).
Business Applications
MM
The following documents relating to purchasing in MM can be stored:
Outgoing purchasing documents
Requests for quotation
Purchase orders
Scheduling agreements
Forecast delivery schedules
Contracts
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink: Overview
14 April 2001
Incoming purchasing documents
Quotations
Order confirmations
Incoming invoices and credit memos
Incoming delivery notes
Print lists
For more information about storing in MM, see SAP ArchiveLink - Storage Scenarios in MM
(Seite 74).
SD/WS
The following are examples of sales documents that can be stored:
Incoming customer inquiries and customer inquiry changes
Outgoing customer quotations
Incoming purchase orders and purchase order changes
Outgoing order confirmations
For more information about storing in SD, see SAP ArchiveLink - Storage Scenarios in SD [Seite
50].
PA
The following personnel administration and payroll documents can be stored:
Incoming HR master data documents
Incoming recruitment documents
Incoming travel management documents
For more information about storing in PA, see SAP ArchiveLink - Storage Scenarios in PA [Seite
204].
QM
The following QM documents can be stored:
Incoming documents for quality notifications (for example, customer complaints)
Outgoing documents for quality notifications (for example, letter of complaint to vendor)
Outgoing quality certificates
For more information about storing in QM, see SAP ArchiveLink - Storage Scenarios in QM
(Seite 93).
The DMS and Applications Connected with the DMS
In the DMS and in applications that are connected with the DMS (often MM and PP), the
following documents can be stored:
Incoming documents
Originals managed in the DMS (PC files)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink: Overview
April 2001 15
For more information about storing in the DMS, see Storing in Document Management (CADMS)
(Seite 24).
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Customizing
16 April 2001
Customizing
Customizing is divided into three areas:
General Customizing for SAP ArchiveLink
Customizing for SAP Business Workflow
Application-specific Customizing for individual SAP ArchiveLink scenarios
General Customizing for SAP ArchiveLink
To make these settings, proceed as follows:
Use the Implementation Guide (IMG):
Basis Basis Services SAP ArchiveLink
For further information, see the Customizing (Extern) section in the documentation SAP
ArchiveLink.
Customizing for SAP Business Workflow
For the storage scenarios that use SAP Business Workflow:
Storing for Subsequent Entry (Extern)
Storing for Subsequent Assignment (Extern)
Storing and Entering (Extern)
Storing and Assigning (Extern)
you must make Workflow Customizing settings.
For further information, see the section Specific Customizing (Extern) in the documentation SAP
ArchiveLink and the IMG (Basis Basis Services SAP ArchiveLink).
Application-Specific Customizing
In the individual application scenarios, further customizing settings are required. The
application-specific customizing for each SAP application component is described in the following
sections of this documentation.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Aim of this Documentation
April 2001 17
Aim of this Documentation
This documentation describes the SAP ArchiveLink scenarios that are delivered as part of the
standard system by SAP. There is a section for each storage scenario. The documentation
describes the standard software.
Each storage scenario description is assigned to one of the big application components in the
SAP System. Storage scenarios in the following application components are currently described:
BC (Basis)
CA (Cross-Application Components)
FI (Financial Accounting)
SD (Sales and Distribution)
MM (Materials Management)
IS-RE (Real Estate Management)
QM (Quality Management)
PP (Production Planning and Control)
PM (Plant Maintenance and Service Management)
PA (Human Resource Management)
PY-DE (Payroll Germany)
The individual storage scenarios are structured as function descriptions and generally contain the
following sections:
Section Description
Use Business background
(this section is sometimes separate from the pure function description).
You learn which application scenarios SAP ArchiveLink supports, which
employees are involved and the advantages and simplifications offered by SAP
ArchiveLink.
This information is enough to give you a first overview of the storage scenarios.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Aim of this Documentation
18 April 2001
Prerequisites Technical implementation
You become familiar with the document types and the corresponding technical
document classes that form the basis of the scenario. You discover which object
types and link tables are used.
This information is particularly useful if you are planning to enhance or change
the scenario.
Preparation and Customizing
The settings that are necessary to adapt the scenario to the specific
requirements of your corporate structure are described.
The settings described are scenario-specific and usually complement the SAP
application component Customizing.
Activities This section describes the technical and business connection of the scenario to
the R/3 application and how the corresponding application functions are called.
This documentation is not intended to replace the SAP ArchiveLink
documentation and should only be seen as a central reference point for
documentation relating to the implementation of SAP ArchiveLink in the individual
SAP applications.
To find out more about using SAP ArchiveLink and make full use of the functions for
enhancements and in-house developments, see the SAP ArchiveLink (Extern)
documentation.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink - Storage Scenarios (BC)
April 2001 19
SAP ArchiveLink - Storage Scenarios (BC)
Ablegen von Listen mit SAP ArchiveLink (Extern)
The following sections describe storage scenarios in R/3 Basis (BC):
Storing Lists in the Report Tree
Storing Print Lists
Storing SAPoffice Documents
See also:
General Introduction (Seite 10) to this scenario documentation
SAP ArchiveLink (Extern) documentation
General Report Selection (Extern) documentation
BC - ABAP Programming (Extern) documentation
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Lists in the Report Tree (BC)
20 April 2001
Storing Lists in the Report Tree (BC)
Use
This section describes the storing of lists generated by executing reports in report trees. The
process is not application-specific and is usually possible for any list unless storing is specifically
prohibited in the program.
Users can access reports that they require in the hierarchical structure of the report tree easily
from all applications, via general report selection in the SAP information system.
The SAP standard report tree contains several standard reports for all applications. To access
reports from a particular application, you must expand the structure until you reach a list of
reports on the lowest level. Here you select and execute the required report. You can display the
result on the screen or print it via the spool system.
Companies can configure the standard report tree to suit their requirements. For example, you
can add your own reports or pre-generated lists and even change the entire structure.
Prerequisites
Technical Implementation (BC)
Object type
SREPOTREE
Document type
ABAP
Link table
TOA01
For further information on executing reports and displaying pre-generated lists in report trees,
see General Report Selection (Extern).
Technical Implementation (BC)
Although storing lists generated in the report tree is similar for all applications, the report tree
available to you may vary from the SAP standard, since your company can adjust the SAP
standard report tree to suit its requirements.
For further information on Customizing the report tree, see the Implementation Guide (IMG).
Choose
Tools Business Engineer Customizing
Implementation projects Display SAP Reference IMG
and then Basis Reporting - Report tree.
Activities
Storing lists
When you have executed a report in the report tree, you can save the result list there and store it
simultaneously.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Lists in the Report Tree (BC)
April 2001 21
To save your list and store at the same time:
1. Choose System List Save Report tree.
2. Select Store in the dialog box displayed and specify where the list should be stored in the
report tree. Specify the values for Report tree and Nodes.
3. Choose Save.
You have now saved your list in the report tree and the process is complete.
Displaying information on storing lists
You can check whether a list has been stored in the report tree:
To check whether a list has been stored:
1. Position the cursor on the relevant list.
2. Choose Utilities List information.
The System displays a dialog box. The check boxes indicate whether the list has been
stored.
Displaying stored lists
To display a stored list in the report tree, choose the relevant list by double-clicking.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Business Workplace Documents
22 April 2001
Storing Business Workplace Documents
Use
Documents stored in the Business Workplace (Extern) are usually stored in the R/3 database (PC
documents and binary documents can also be stored in an HTTP content server). To save
memory space in the database, you can store documents in an external storage system using
SAP ArchiveLink. The content of the documents that you have stored using SAP ArchiveLink is
then deleted from the database.
You can only retrieve Workplace documents stored using SAP ArchiveLink from the
external storage system, from within the R/3 System. Direct access within the
storage system is not possible.
Prerequisites
Technical Implementation
Object type
SOFM
Link table
TOA01
Document class
BIN
Document type
SOAARCHIVE Description: Office data object
Preparation and Customizing
To store documents from the Business Workplace, a content server must be maintained for the
object type SOFM and the object class SOAARCHIVE in Customizing (Extern) for SAP
ArchiveLink.
To perform mass archiving of Workplace documents, you need authorization (Extern) for
Workplace administration. This authorization is contained in the role SAP_BPT_USER.
Activities
Proceed as described in Mass Archiving (Extern).
The procedure for displaying and changing documents stored in the archive is no different for the
user than the procedure for documents stored in the R/3 database. Calling documents from the
archive usually takes longer, however.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink - Storage Scenarios (CA)
April 2001 23
SAP ArchiveLink - Storage Scenarios (CA)
The following sections describe the storage scenarios in the R/3 application component CA
(Cross-Application):
Document Management System (CA-DMS)
Data Achiving (CA-ARC)
See also:
General Introduction (Seite 10) to the scenario documentation
SAP ArchiveLink (Extern)
Application Data Archiving (Extern)
Document Management System (Extern)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Optical Archiving in Document Management (CA-DMS)
24 April 2001
Optical Archiving in Document Management (CA-DMS)
eingehende Dokumente (Seite 30)
You can use SAP ArchiveLink® to archive documents from the document management system
(DMS) in optical archiving systems.
Documents Input when Processed (CA-DMS) (Seite 30)
Checking a Document into an Archive (CA-DMS) (Seite 31)
Displaying an Archived Document (CA-DMS) (Seite 32)
Copying an Archived Document to a Document Info Record (CA-DMS) (Seite 33)
Digital Original Application Files (CA-DMS) (Seite 25)
Archiving an Original Application File (CA-DMS) (Seite 26)
Creating a New Version (CA-DMS) (Seite 27)
Changing an Original Application File for an Existing Version (CA-DMS) (Seite 28)
Displaying an Archived Original Application File (CA-DMS) (Seite 29)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Digital Original Application Files (CA-DMS)
April 2001 25
Digital Original Application Files (CA-DMS)
For each document info record, you can maintain and archive two original application files.
Each original application file can be linked to a maximum of 99 additional files. These are
archived automatically when you archive the original application file.
Functions
You process original application files with the following menu option of the document info record:
Extras Originals File 1(2)
The following functions for archiving and processing archived original application files are
available:
Archiving an Original Application File (CA-DMS) (Seite 26)
Creating a New Version (CA-DMS) (Seite 27)
Changing an Original Application File for an Existing Version (CA-DMS) (Seite 28)
Displaying an Archived Original Application File (CA-DMS) (Seite 29)
Notes on archiving original application files
The system checks the application that is used to process the original application file (for
example, WinWord 7.0).
In the IMG for the Document Management System in the activity Define workstation
applications, you define the archives for the various applications (for example, archive A2
for the application WinWord 7.0).
The system does not log the archiving of original application files. However, in the IMG for
the Document Management System, you can define in the activity Define document types
that all field changes are to be logged (Indicator: Create change documents).
If you have archived an original application file with the function Check in archive, you
can track any changes to the storage data (fields Data carrier and Original) in the change
documents.
Notes on processing archived original application files
You have two options for processing an archived original application file:
Creating a New Version (CA-DMS) (Seite 27)
Changing an Original Application File for an Existing Version (CA-DMS) (Seite 28)
See also:
Figure: Changing an Archived Original Application File (Extern)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Archiving an Original Application File (CA-DMS)
26 April 2001
Archiving an Original Application File (CA-DMS)
You archive an original application file if you want to save the current processing status for
documentation purposes.
See also:
Figure: Archiving Original Application Files (Extern)
To archive an original application file:
1. Process the document in change mode (Basic data screen).
2. Choose Extras Originals File 1(2) Check in archive.
The system saves the original application file to the optical disk defined in Customizing.
You see a dialog box with the following message:
Document archived successfully
3. You can check which archive the document was saved to.
To do this, display the data carrier and path for the original application data by choosing
Storage data.
The data carrier and the path where the original application file was stored before being
checked in the archive is no longer displayed. The system has overwritten this data with
the archive data.
If the document type is defined such that all field changes are logged, you can still
display the previous storage place (Goto Display changes).
4. Save your document info record.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Creating a New Version (CA-DMS)
April 2001 27
Creating a New Version (CA-DMS)
This means that you keep the old version (for example, 00) containing the archived original
application file and create a new version (for example, 01) directly from the old version. For the
new version, you then change the original application file.
To process the archived original application file (new version):
1. On the Basic data screen, choose Document New version.
The system copies the data of the existing version (for example, 00), including the archived
original application data.
2. In the new version (for example, 01), the original application file is still archived.
3. Choose Extras File 1(2) Change.
The system automatically creates a copy of the checked in original application file.
Enter the target for the copy. This path identifies the place where the original
application file for the new version (for example, 01) is stored.
If the system accepts your entries, you see a dialog box with the following message:
Data copied from archive
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Changing an Original Application File for an Existing Version (CA-DMS)
28 April 2001
Changing an Original Application File for an Existing
Version (CA-DMS)
This means that you change the version whose original application file has been archived. There
is only one version in this case.
You can display the processing status that the original application file had in the archive from the
status log if the following applies:
When checking the original application file into the archive, you set a status for which the
Indicator: Audit function is selected. This indicator causes original application files that are
checked into the SAP database, a vault, or an archive with this status to be stored automatically.
To change the archived original application file (existing version):
1. Choose Extras Originals File 1(2) Change.
The system automatically creates a copy of the archived original application file.
2. You see a dialog box, where you can enter the target for the copy. As a default value, you
see the path where the file was stored before being archived.
To accept the default value, choose Continue.
If you want the file to be copied elsewhere, enter the required data (data carrier,
path, and file name) in the dialog box. This path identifies the place where the
original application file for the same version is stored. The system overwrites the
previous archive data.
If the system accepts your entries, you see a dialog box with the following message:
Data copied from archive
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Displaying an Archived Original Application File (CA-DMS)
April 2001 29
Displaying an Archived Original Application File (CADMS)
To display an original application file, you always use the following function, whether the data is
stored on a server or in an archive:
Extras Originals File 1 (2) Display.
The system automatically determines the path in the computer network. If the original application
file is stored in an archive, you see a dialog box with the following message:
Data copied from archive
You can display archived data only from computers that have SAP ArchiveLink
software installed.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Documents Input when Processed (CA-DMS)
30 April 2001
Documents Input when Processed (CA-DMS)
You process documents input when processed in the Archive menu of the document info record.
The following functions are available:
Checking a Document into an Archive (CA-DMS) (Seite 31)
Displaying an Archived Document (CA-DMS) (Seite 32)
Copying an Archived Document to a Document Info Record (CA-DMS) (Seite 33)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Checking a Document into an Archive (CA-DMS)
April 2001 31
Checking a Document into an Archive (CA-DMS)
You use this function to check a scanned-in document (image) into an optical archive.
See also:
Scenario: Checking a Document into an Archive (Extern)
To check a document into an archive:
1. Two windows are active on your computer screen:
a scan window with a scanned-in document
a window for the R/3 document management system
2. In the document management window, choose the function you require (Document
Create or Change).
Enter the required data on the initial screen and choose ENTER. You see the Basic data
screen.
3. Choose Archive Check into archive.
The system checks whether a status network that supports a status of status type A
(archived) is defined for the chosen document type.
Archiving is possible in the following cases:
if the status network does not support a status of status type A
if the status network supports a status of status type A at the current processing
stage.
The system automatically sets the status of status type A and records the status
change in the status log.
The system automatically determines the archive that is defined in the IMG
functionOptical Archive.
When the data has been archived, you see a dialog box with the following message:
Document archived successfully
4. Save your document info record.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Displaying an Archived Document (CA-DMS)
32 April 2001
Displaying an Archived Document (CA-DMS)
You use this function you to display documents that were either scanned in when processed,
then archived, or copied from the archive from the document info record.
This function is only active it at least one document has been archived for the chosen
document info record.
To display a document from the archive:
1. Choose menu option Archive Display from archive.
2. What you do next depends on the situation:
If only one archived document exists for the document info record, the system goes
directly to the display program (viewer) and displays the document.
If more than one archived documents exist for the document info record, you first
see a dialog box listing the archived objects with the date on which they were
archived.
On the list, select the archived objects you want to display in the viewer.
Choose the Choose pushbutton.
The system goes to the first selected object.
In the viewer, you can switch between the objects you selected by choosing the
appropriate function (Object + or Object -) from the Goto menu.
3. To exit the display function for archived objects, close the viewer with Document Exit.
You can now continue processing the document info record.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Copying an Archived Document to a Document Info Record (CA-DMS)
April 2001 33
Copying an Archived Document to a Document Info
Record (CA-DMS)
This function allows you to copy a document that has been archived by another application (for
example, SAPoffice) to a document info record.
See also:
Scenario: Copying an Archived Document to a Document Info Record (Extern)
Figure: Copying an Archived Document to a Document Info Record (Extern)
To copy a document from an archive:
1. Two windows are active on your screen:
a window showing the document in the display program (viewer) of the archive
a window for the R/3 document management system
2. In the document management window, choose the function you require (Document
Create or Change).
3. Place the cursor on the viewer window again.
Choose Edit Select
This selects the scanned-in document for processing in the document management
system.
4. Place the cursor on the document management window.
Choose Archive Copy from archive.
The system makes the same status checks as described in Checking a Document into
an Archive (CA-DMS) (Seite 31).
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink and Application Data Archiving (CA-ARC)
34 April 2001
SAP ArchiveLink and Application Data Archiving (CAARC)
Use
You can use the Archive Development Kit data archiving transaction and SAP ArchiveLink to
store archive files in external archives. For more information see: Technical Background (CAARC)
(Extern).
Prerequisites
You must enter the following settings in customizing in order to use the SAP ArchiveLink
interface to archive application data:
Platform-independent filename
Document type
Automatic transfer of archive files
Activities
Checking Storage Status of Archive Files (CA-ARC) (Seite 38)
Storing Archive Files Manually (CA-ARC) (Seite 39)
See also:
Setting Platform-independent Filenames for SAP ArchiveLink (CA-ARC) (Seite 35)
Setting Archive File Document Type (CA-ARC) (Seite 36)
Storing Archive Files Automatically (CA-ARC) (Seite 37)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Setting Platform-independent Filenames (CA-ARC)
April 2001 35
Setting Platform-independent Filenames (CA-ARC)
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Customizing function.
4. In archiving object-specific customizing choose Technical Settings.
5. In the logical filename field enter a filename that refers to the exchange directory of the
attached SAP ArchiveLink archive system. For example, the logical filename
ARCHIVE_DATA_FILE_WITH_ARCHIVE_LINK. The system delivers the following standard
defined filename:
, if you use this runtime variable in the specification of the
physical path. For example, the physical path could be:
ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK. See the FILE transaction
documentation for further information.
See also:
Setting Archive File Document Type (CA-ARC) (Seite 36)
Storing Completed Archive Files in the Archive System Automatically (CA-ARC) (Seite 37)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Setting Archive File Document Type (CA-ARC)
36 April 2001
Setting Archive File Document Type (CA-ARC)
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Customizing function.
4. Choose Technical Settings in archiving object-specific customizing.
5. Choose the document type Archive in the group box Archive System Link.
See also:
Setting Platform-independent Filenames for SAP ArchiveLink (CA-ARC) (Seite 35)
Storing Completed Archive Files in the Archive System Automatically (CA-ARC) (Seite 37)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Completed Archive Files in the Archive System Automatically (CA-ARC)
April 2001 37
Storing Completed Archive Files in the Archive System
Automatically (CA-ARC)
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Customizing function.
4. Choose Technical Settings in archiving object-specific customizing.
5. Mark the checkbox Exec. automat. in the group box Archive System Link.
See also:
Setting Platform-independent Filenames (CA-ARC) (Seite 35)
Setting Archive File Document Type (CA-ARC) (Seite 36)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Determining Whether an Archive File is Stored in the Optical Archive (CA-ARC)
38 April 2001
Determining Whether an Archive File is Stored in the
Optical Archive (CA-ARC)
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Management function.
4. Set the cursor on the file whose archive residence you want to know, and double-click.
The Archive Management: Archiving File Detail popup appears. Read the Storage option
status text.
See also:
Storing Completed Archive Files in the Archive System Manually (CA-ARC) (Seite 39)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Completed Archive Files in the Archive System Manually (CA-ARC)
April 2001 39
Storing Completed Archive Files in the Archive System
Manually (CA-ARC)
Only archive files whose data objects have been deleted in the database can be
stored in an external archive system.
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Management function.
4. Set the cursor on the file which you want to store in the external archive system.
If you want to store all the files in a session, set the cursor on the session number.
5. Choose the Store function.
The Archive Management: Store via ArchiveLink popup appears.
6. Choose the Store Files function.
The file is passed to the external archive system.
See also:
Determining Whether an Archive File is Stored in the External Archive (CA-ARC) (Seite 38)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink - Storage Scenarios (FI)
40 April 2001
SAP ArchiveLink - Storage Scenarios (FI)
The following sections describe storage scenarios in the Financial Accounting (FI) application
component.
See also
The general introduction (Seite 10) to this scenario documentation
SAP ArchiveLink (Extern)dokumentation
Financial Accounting documentation
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Print Lists (FI)
April 2001 41
Storing Print Lists (FI)
Use
In the FI application component, you can use SAP ArchiveLink to transfer the following print
lists to an external storage system:
Compact document journal (RFBELJ00)
Line item journal (RFEPOJ00)
Open item account balance audit trail (RFKKBU00)
Accumulated account balance audit trail (RFKLBU10)
Storage using SAP ArchiveLink has the following advantages:
Reduced burden on online system
Safer storage
Faster, easier access
Prerequisites
Technical Realization (FI)
Following improvements to the print reports, the print lists are now provided with an index when
they are stored, enabling you to access objects (including sub-objects) at a later date.
A particular account in the account balance audit trail.
The system also generates a link to any stored documents that might exist, enabling you to
display the corresponding stored document from the stored print list.
For a detailed description of how to store print lists, refer to Print Lists (Extern) in the SAP
ArchiveLink documentation.
There are no plans for enhancements.
Preparation and Customizing (FI)
No special Customizing settings are required to be able to store print lists in FI. For
information on the Customizing settings for SAP ArchiveLink, see Customizing (Seite 16).
Special authorizations are not required.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Print Lists (FI)
42 April 2001
Activities
For notes on using these functions (in particular displaying stored print lists) see
Searching for, Displaying and Printing Print Lists (Extern) in the SAP ArchiveLink
documentation.
To store print lists in the FI application component, proceed as follows:
1. Run the appropriate program and enter your selection criteria.
2. On the selection screen, choose Optical archiving and enter the following information in
the dialog box that is now displayed:
Object class: DRAW (document)
Object type: D01 (print list)
Identification: XXX (three figure alphanumeric code of your choice)
Text: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (up to 30 characters
long).
3. Now choose Execute in background or Execute + Print.
To view the stored list, from the R/3 System initial screen, choose
Office Business Documents Find lists. Enter the name of the report program and
any additional selection criteria. Choose Enter. From the list that is now displayed you
can select a print list and display its contents.
When displaying the list, you can also display the incoming and outgoing documents
(provided these were also stored). You do this via hyperlinks which are recognizable
as such by being underlined.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Incoming Documents (FI)
April 2001 43
Storing Incoming Documents (FI)
Use
In the FI application component, you can transfer incoming documents (invoices, credit memos)
to an external archive system using SAP ArchiveLink. Data can be stored in different ways:
Store for subsequent entry
Store and enter, and
Late storing with bar codes
Assign, then store
For detailed information on the ways in which you can store documents, see Storage
Strategies (Extern) in the SAP ArchiveLink documentation.
The procedure Store for entry later with document parking is different to other storage
methods. Under this procedure, processing is even more automated than it would otherwise be.
The accounting clerk responsible for parking documents receives an incoming document (an
invoice for example) via SAP Business Workflow. In the entry transaction to which the invoice
is subject, the clerk can park this document using the existing incoming document. He or she can
then send the parked invoice together with the incoming document for further processing
(approval or additional investigation) to the relevant colleague. This colleague can then complete
processing and post the invoice.
Prerequisites
Technical Realization (FI)
Object type
BKPF (financial accounting document)
Link table
TOA01
Document class
FAX
Document type
In the standard system, the following document types are supplied for the R/3 FI application
component.
FI document Document type
Incoming invoice without invoice verification FIIINVOICE
Incoming credit memos without invoice verification FICREDIT
Incoming invoice parking FIIINVPREL
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Incoming Documents (FI)
44 April 2001
Fast invoice entry FIIPAYMEN2
Incoming payment FIIPAYMENT
Enhancements
You can define your own document types under
Tools Business Documents
Document types Global document types and
Tools Business Documents
Document types WFL document types.
You can define your own transaction links under
Tools Business Documents
Document types Workflow parameters.
Further information
For basic technical information on adding SAP ArchiveLink functions to the R/3 application
components, refer to the section Incoming Documents (Extern) in the SAP ArchiveLink
documentation.
Preparation and Customizing (FI)
The basic preliminary settings that you must make in SAP ArchiveLink are described in
Customizing (Seite 16)
You need to make settings in Customizing for Financial Accounting only for the activity Late
storing with bar codes. For more information, see the documentation for the activities Specify
Control Parameters for Bar Code Entry and Maintain Document Types for Bar Code Entry
located in Customizing for Financial Accounting under Financial Accounting Global Settings
Document Document Header.
Activities
Scenario: Assignment and Storage in FI
For information on this procedure, see the following sections of the SAP ArchiveLink
documentation:
Scenario: Late Storage with Bar Codes in FI
For information on this topic, see:
Process: Late Storing with Bar Codes (Extern)
Concept: Storing with Bar Codes (Extern)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Incoming Documents (FI)
April 2001 45
Scenario: Store for Subsequent Entry in FI
For information on this topic, see:
Concept: Store for Subsequent Entry (Extern)
Process: Store for Subsequent Entry (Extern)
Store for Subsequent Entry (Extern)
Scenario: Entry and Storage in FI
For information on this topic, see:
Concept: Store and Enter (Extern)
Process: Store and Enter (Extern)
Store and Enter (Extern)
Document Processing Functions
In certain document processing transactions in FI you have direct access to the functions
available under SAP ArchiveLink. These transactions include:
Changing documents (FB02)
Displaying documents (FB03)
Changing parked documents (FBV2)
Displaying parked documents (FBV3)
When carrying out these transactions, you can use the following functions:
Subsequently assign a stored document from the external content server (see Assign
Stored Documents Subsequently (Extern))
Display the stored document for an FI document from the external content server (see
Searching for Incoming Documents (Extern))
The assignment and display functions might typically be accessed as follows:
1. From the General Ledger menu, choose Document Display.
2. Enter the document number and the company code in which it was posted. Choose
ENTER.
The system now displays the R/3 document.
3. To display the stored document for this R/3 document, choose Environment Object
links
To assign this document to a document already stored, choose Environment Assign
original.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Incoming Documents (FI)
46 April 2001
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Outgoing Documents (FI)
April 2001 47
Storing Outgoing Documents (FI)
Use
You can store documents transferred from the General Ledger (FI-GL), Accounts Receivable (FIAR)
and Accounts Payable (FI-AP) application components using SAP ArchiveLink. Documents
that you created using SAPscript are stored in an external storage system and linked to the
documents or accounts from which they are derived. You can store the following outgoing
financial accounting documents:
Payment advice notes
Checks
Correspondence like payment notifications and bank statements
Dunning notices
Storage using SAP ArchiveLink takes place using Business Transaction Events, to which end
SAP supplies sample function modules that you can activate by making the appropriate
Customizing settings.
If you already use your own programs (user exits) or Business Transaction Events to
manage printing, faxing, email or dispatching, check whether you need to replace
these developments with a function module enhanced to perform these functions.
IMPORTANT: Ensure that no data is overwritten.
Prerequisites
Technical Realization (FI)
Object type
BKPF (financial accounting document)
BUS3007 (customer account)
BUS3008 (vendor account)
Link table
TOA01
Document class
PDF
Document type
The following document types exist in the standard system:
FI document Document type Function module
Payment advice note FIOPAYAVIS FI_OPT_ARCHIVE_PAYMENT_ADVICE
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Outgoing Documents (FI)
48 April 2001
Check FIOPAYMENT FI_OPT_ARCHIVE_ PAYMENT
Correspondence:
Payment notification
Bank statement
FIOPAYCONF
FIOACCSTAT
FI_OPT_ARCHIVE_CORRESPONDENCE
Dunning notice FIODUNNING FI_OPT_ARCHIVE_DUNNING_NOTICE
If you make changes in Customizing to the object types and document types, you will need to
adapt the corresponding function modules in each case.
Enhancements
There are no restrictions to the way in which sample function modules in the standard system
can be enhanced. They can also be duplicated for additional document types and object types as
many times as necessary.
You can define your own document types in the Basis Implementation Guide under
Basis Services SAP ArchiveLink System Settings Maintain Document Types.
To define you our own object types, on the SAP R/3 screen, choose
Tools Business Framework BAPI development Business Object Builder.
The sample function module FI_OPT_ARCHIVE_CORRESPONDENCE contains the
correspondence types SAP01 (payment notificiation) and SAP08 (account statement).
Additional correspondence types can be added to this function module. You can define
correspondence types in Customizing for Financial Accounting under the
Implementation Guide under
Financial Accounting Global Settings Correspondence Define Correspondence
Types.
Preparation and Customizing (FI)
To activate storage for financial accounting documents using SAP ArchiveLink, make the
following settings in Customizing:
1. If you want to make changes to the function modules (changing the document type
defined in the standard system for example) copy the sample function modules to your
name range. You should then make these changes in the source text.
For a detailed description of the procedure for copying sample function modules to your
name range, see the IMG documentation for the activity Use Business Transaction
Events (located under Financial Accounting Global Settings.)
2. Define the storage method in the function modules. Enter the setting in source text for
the parameter c_itcpo-tdarmod. The following settings are possible:
2 Store only
3 Print and store
3. Create a product with which all function modules that you want to activate can be
summarized at a later date.
To do this, choose the activity Use Business Transaction Events, located in Customizing
for Financial Accounting under Financial Accounting Global Settings. On the SAP
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Outgoing Documents (FI)
April 2001 49
Business Framework: Business Transaction Events screen, choose Settings Products
... of a customer. Mark this product as active by selecting the Active indicator.
4. Assign the function modules to processes (Events).
To do this, choose the activity Use Business Transaction Events, located in Customizing
for Financial Accounting under Financial Accounting Global Settings. On the Business
Framework: Business Transaction Events screen, choose Settings P/S function
modules ... of a customer. In the table that is now displayed, enter the names of the
function modules that you want to activate, together with the Events or products required.
Enter also the name of the product already created.
The names of the processes defined in the standard system are as follows:
Function module Process
FI_OPT_ARCHIVE_PAYMENT_ADVICE 00002050
FI_OPT_ARCHIVE_ PAYMENT 00002060
FI_OPT_ARCHIVE_CORRESPONDENCE 00002310
FI_OPT_ARCHIVE_DUNNING_NOTICE 00001040
Activities
Storing outgoing documents (FI)
Outgoing documents are stored automatically if you have carried out the above-mentioned
settings in Customizing.
Displaying stored documents
Stored documents can be displayed as follows:
On the SAP R/3 screen, by choosing Office Business Documents Documents
Find lists
From the Accounts Receivable or Accounts Payable menu by choosing Master records
Display.
Enter the customer or vendor you wish to display, select one of the indicators under
Company code data and choose ENTER.
On the screen that is now displayed, choose System Display relationships Stored
documents.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink - Archiving Scenarios (SD)
50 April 2001
SAP ArchiveLink - Archiving Scenarios (SD)
The following sections describe the archiving scenarios in the R/3 application component SD
(Sales and Distribution):
General sales and distribution (SD)
Sales support (SD-CAS)
See also
General Introduction (Seite 10) to this scenario documentation
SAP ArchiveLink (Extern)documentation
Sales and distribution (Extern) documentation
Sales support (Extern) documentation
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Optical Archiving of Incoming Original Documents (SD)
April 2001 51
Optical Archiving of Incoming Original Documents (SD)
Betriebswirtschaftlicher Hintergrund (SD) (Seite 52)
Weitere Voreinstellungen (Extern)
Spezial-Customizing (Extern)
Ablegen für spätere Erfassung (Extern)
Zuordnen und Ablegen (Extern)
Spät ablegen mit Barcode (Extern)
Ablegen und Erfassen (Extern)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Business Background (SD)
52 April 2001
Business Background (SD)
The Sales and Distribution application component contains an SAP ArchiveLink function that
provides sales personnel with a quick and efficient means of optically archiving and processing a
wide range of incoming documents including inquiries, purchase orders, contracts, and
complaints. SAP ArchiveLink offers easy online access to these archived documents during the
planning, processing, and analyzing of business transactions in Sales and Distribution.
The SAP ArchiveLink interface supports the following archiving scenarios for incoming
documents in SD:
Early archiving
Late archiving
Late archiving using bar codes
Simultaneous archiving
Early Archiving
In the early archiving scenario, incoming paper documents are archived in the R/3 System before
an SD document is created.
In early archiving, the archiving process usually begins in a central mailroom where a designated
person opens, presorts, prepares, and records (scans) the incoming mail. Once an incoming
document is scanned and an incoming document type is assigned to it, the system triggers the
SAP Business Workflow to notify the authorized employee(s) that an incoming document has
been received and is due to be processed. When the employee accesses the archived
document, the system automatically calls up the relevant business transaction, such as Create
sales order, according to the incoming document type. After the employee creates and saves the
SD document, the system automatically assigns the archived document to it.
For a detailed description of early archiving, see Early Archiving (SD) (Seite 54).
Late Archiving
In the late archiving scenario, incoming paper documents are archived in the R/3 System and
assigned to existing Sales and Distribution documents.
In late archiving, an employee processes an original document directly from paper or carries out
a sales activity before receiving an original document. At a later point in time, the original
document is scanned into the system and archived as a facsimile. It is then assigned to the
existing SD document by:
The person at the archiving station who scans the original documents
The person responsible for processing the SD document
As in the scenario for early archiving, the archiving process usually takes place in a central
location at the company.
For a detailed description of late archiving, see Late Archiving (SD) (Seite 55).
Late Archiving Using Bar Codes
Late archiving using bar codes is a special form of late archiving. In this case, however, a bar
code is attached to the incoming document either in the mail room or at the time of processing.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Business Background (SD)
April 2001 53
An SD document is created from the original document whose bar code ID is linked to the SD
document number. Later, the original document is scanned into the system which recognizes the
bar code ID and automatically makes the proper assignment to the SD document.
For a detailed description of late archiving using bar codes, see Late Archiving Using Bar Codes
(SD) (Seite 56).
Simultaneous Archiving
Simultaneous archiving is a special form of early archiving in which the incoming document is
scanned into the system, optically archived and, at the same time in another window, the
corresponding SD document is created or changed. The system does not activate SAP
Business Workflow in this case; no mail is sent.
For a detailed description of simultaneous archiving, see Simultaneous Archiving (SD) (Seite 57).
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Early Archiving (SD)
54 April 2001
Early Archiving (SD)
The following steps describe a typical scenario in which incoming paper documents are archived
before a Sales and Distribution document is created:
1. A clerk in the central mail room of a company receives a letter from a customer who wishes
to buy several products.
2. The clerk scans the letter into a scanning system.
The system displays the letter in the scan dialog window.
3. Using the SAP ArchiveLink interface in the R/3 System, the clerk or another designated
employee selects the function for early archiving and chooses an appropriate incoming
document type for the scanned document, for example, the general description Customer
response to a sales activity, SDIACTRESP.
4. The clerk confirms the assignment of the incoming document type.
This triggers a workflow in which a mail is sent to the employee who is responsible for
creating sales documents, in this case Mr. Jones in the Sales department.
All employees who are to be notified by SAP Business Workflow must first be listed
in the companys organizational structure (see Customizing for SAP Business
Workflow).
5. Mr. Jones receives the work item in his integrated inbox. When he calls up the work item for
processing, a dialog box appears in which Mr. Jones can confirm or overwrite th -
Using a single Content server for DMS and also for Archive link documents
Hi,
We have Planned for a single content server for managing the documents in DMS, parallelly as DMS Standard SAP objects are not available for all SAP transactions, i have proposed for making use of SAP Archivelink funtionality to maintain the documentations where Std SAP DMS does not provide a Solution.
so here the question is
can a single content server be used as a content repository for Both DMS and archivelink,
can any one having done this pls state if it is possible to create different or Many Content repositories for DMS, Archive link in the same server,
is this a virtual creation or can we assign each repository a specific storage space which it should not exceed.
Thanks and regards
SathishHi sathish,
-- Through the ArchiveLink docuemnt Management interface, an SAP sytem can use various content servers as storage media. similarly, one contnent server can be used by multiple SAP systems.
-- A Content server always has a single database assigned to it. A database can therefore be used by only one content server.
-- A databse is split into as many repositories as necessary. The design of the repository is mapped in the SAP system.A repository contains documents.
Depending on your requirements,(if u have limited documents or with low requirements) you can use the same content server for both DMS and Archivelink.
The number of documents stored on the content server is limited only by the size of the database.
Its better to have an external content server for archiving purpose, if your database size is increasing. Since the archiving systems storage is not dependent on the database.
U can also refer to the below thread :
How to Archive SAP DMS Data?
hope this helps....
regards
kavitha -
Document transfer from SRM to DMS through content server
Hi Everybody,
In one of scenarios we need to transfer documents attached to the shopping cart line items in SRM to R/3.
For that we followed the following procedure.
1.In the SRM to R/3 system, the attachments are driven by the BADIs.
2.In the BADI, if we define DMS_C1_ST as the storage category for R/3 Database, the DMS should work
3.The existing DMS, the customized content server is Z_DMS.
4.Using SRM (with Z_DMS)we are able to create the Document Info Record
5.The attachments are not reflected in DMS (driven through SRM)
6.When the attachments are added in the DMS manually, DMS works perfect
I am thinking there might be some configuration required in content server for the conversion of original application files.
If anybody have the solution for this please post here.
Thanks,
Rajesh.Hi
<b>Please refer to the links below -></b>
Re: Attachments in PR and PO
Re: Sending attachments from SRM to SAP Purchase Requisition
Re: Transfer SC attachment from srm 5.0 to backend R/3
Re: Attachments to backend
Re: Attachments in PR and PO
Re: URL vs. document attached in back end EBP 4.0 Classic/4.7 E
http://help.sap.com/saphelp_47x200/helpdata/en/41/648838ab4e8a11e10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/49/b32640632cea01e10000000a155106/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/d6/806c39917d423ee10000000a11402f/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/9b/c2b9375e62545ce10000009b38f889/frameset.htm
Do let me know incase you still have any queries.
Regards
- Atul -
Storing documents with BDN to content server
Hi,
Could anyone please tell me if it is possible to store documents to a content server using BDN (transaction OAOR)? So far I can only store documents to the R3 database. In the Archive Link customizing the link table should be updated with the right entries containing the relevant document type, document class, and repository id.
Every hint is much appreciated.
Regards
Thomas HørlyckThanks for the answer, but my question was whether it is possible to store documents to an external content server using transaction OAOR (Business Document Navigator). Right now it is only possible to store documents to the R3 database with OAOR.
Regards
Thomas Hørlyck -
Store document into Content Server
Dear All;
l have the following requirement for Content Server;
- Generate the PR/PO form via print program.
-Approver's signature will be display accordingly by the approval level. EG: 1st level approver 'A' have been approved. Signature of approver 'A' will be display on the generated PR/PO form. - Convert the generated form into PDF format. -To attach the supporting document via Generic Object Services (GOS). -To store the PDF form & attached documents into Archived Link content server with URL address returned.
-An notification mail will send to respective approver based on release strategy configuration.
Basically it is Workflow integrate with Content Server. There are few thing for me to do here:
1. Store the PO/PR document into Content Server
2. Run the workflow and view the attachement and add new attachement to Content Server from the Workflow process.
3. Return the URL address to the user for the document that saved into Content Server
l'm trying to do the first requirement now.
The user will create the PR in tcode ME52N and PO in tcode ME22N, they can create the attachement and view the attachement, and the attachement are stored in the ECC6 database.
l have installed the Content Server 6.40 with Filesystem (not the MaxDB) cause user do not want to buy the MaxDB license.
The Content server 6.4 installation is completed, l can configure the CSDMIN in ECC6,
In OAC0, l have created the Content Repository=ZA,
Document Area = ARCHIVELINK
Storage type = 04 HTTP Content server
Version=0046
Http Server = 10.120.0.10
Port Number = 1090
HTTP Script= ContentServer/ContentServer.dll
Transfer drctry =
10.100.0.10\cm\exdir /# \cm\exdir is a directory in Content Server. #/
the physical directory created in the Content Server as
10.120.0.10\cm\za
In OAC2, l have created a new Document type=ZCS, the document class=PDF
In OAC3, l have created the following:
Object Type= BUS2012, Document Type= ZCS, Link=X, Cont.Rep.ID=ZA, Link=TOA01, Rentention=99
Object Type= BUS2105, Document Type= ZCS, Link=X, Cont.Rep.ID=ZA, Link=TOA01, Rentention=99
(Honestly, l'm not quite sure the BUS2012 will work, it created by functional team, which l'm sure it actually represent the business object for PO and PR)
With these, l think the linkage between business object and logical archive is established, but when l saved the attachement in ME22N and ME52N, the document still save into ECC6 Database, not the Content Server, because in the /cm/za directory in the Content server still empty.
Anyone please advise any documentation/steps do store the document in Content Server from PO/PR and with returned URL to the users.
Please help..
Many thanks
JordanDear all;
Thanks for the information, l manage to store document actually.
l used the OAAD to test to stored, once it is working, then l can use the option 'Store business document" ME23N and ME52N transaction code.
One question here l would like to check:
The WorkFlow team said that the Generic Object Service (GOS) - "Create Attachement" option in ME23N can actually store the document to Content Server instead of store into R3 Database. He claimed some Basis have done it before, can anyone clarify if it is true?
In OAC0, l have ZB Content Repository, set the "Storage Type = 04 HTTP Content Server" in order to save the document to Content Server. The Document Area=Archive Link.
With these setting l can only use the "Store Business Document" option to store the document to Content Server, not the "Create Attachement".
l try to change the Document Area with different option like DMS, BDS etc but l can't get the Content Rep ID for ZB in OAC3 to link the Object Type?
Anyone can help?
Many thanks.
Jordan Tan -
SAP Content Server and DMS configuration
Hello,
I need help in configuring the relation between DMS and SAP Content Server. I need to make documents to be stored in a Content Server Repository and can't see clearly how to configure it from SPRO transaction.
Thanks!
PatriciaHello,
can you tell as the solution for this problem please?
i got the some error message - but only on one server?!
the note 925327 dosn't help's
thank you
thomas berger -
Migrate the document from database to Content Server
Dear All;
There is a ECC6 using for 5 years and I am setting up a External Content Server which link to this ECC6 server, from now on the new incoming documents like scanned document, email etc will save to Content Server.
However, for the past 5 years those old incoming documents that save in the ECC database, how can l migrate it to Content Server? In the past the document mostly save with GOS (generic object service) option.
Please advise.
Thanks
JordanHi Jordan,
from DMS point of view I would recommend you to see the reports DMS_KPRO_CONVERT and DMS_KPRO_CONVERT2 which can be used to transfer original files from older storage to KPRO storage logic.
If you want to move the originals from an archive or vault to a Content
Server, please use the DMS_KPRO_CONVERT and DMS_KPRO_CONVERT2 report I
would kindly ask you to see teh documentation on DMS_KPRO_CONVERT report
in transaction SE38, which explains the whole process and gives
necessary information.
This conversion program offers two possibilites:
- Complete migration:
The meta data of the document info record and the checked-in original
application files are migrated together. The checked-in original
application files are transported into the storage catgories.
- Step-by-step migration:
In the first step meta data is migrated. The original application files
remain in the old storage data. The migration of original application
files starts after you have processed the files with the integrated
viewer and checked them into a secure storage area.
I hope this information could be useful for you. Further I would
really recommend you to get in touch with your local consulting
organisation because this is a very critical and individual process.
To grant that the whole migration is done correctly I can only advise
you to contact your local consulting organisation.
Best regards,
Christoph -
KM Repository to Store Documents on Content Server
Dear All,
We are running on EP 7.0 and having a content server 6.0.
Currently our KM documents are stored on Portal Database
I want a repository where i can get all KM Functionality and Uploaded document should be stored in external content server instead of PortalDB.
Physical location of file should be on Content Server
Please suggest me Process Steps
Regards,
Tushar DaveHi Tushar,
In KM, the repository Managers can be comfigured to connect to other external servers.Like if you have external file servers or webDAV servers, you can connect those with SAP KM and the contents of the external servers are available through the KM.
SAP KM have some predefined repository managers for all those. If you want to refer those repository managers, then
GOTO System Adimistration>Sys configuration>KM-->repository managers
There you can find number of standard repository managers provided by SAP for diffrent type of external servers.
Regards
Manisha -
DMS Content server restriction
Hi All,
In the past we have tried to restrict user access to DMS data (on content server) using DOC type/status restriction. Now we are trying to explore the possibilities of restricting users from accessing export control data from a specific content server.
1. Is there a authorization object using which we can define what content server one have access/restriction?
2. If answer is NO is there a standard method industry is following for this?
Suresh.Authorization Object C_DRAW_TCD (Activities for Documents)
The following table shows authorization object C_DRAW_TCD. This object controls which users can process which document info records, based on a combination of activity and document type.
Fields
Possible Values
Description
ACTVT
(Activity)
01
02
03
06
17
Create
Change
Display
Delete
Maintain number range object
DOKAR
(Document type)
The activities can be executed for the document type.
Authorization Object C_DRAW_TCS (Status Dependent Authorization)
The following table shows authorization object C_DRAW_TCS. This object controls which users can process which document info records, based on a combination of activity, document type, and status.
Fields
Possible Values
Description
ACTVT
(Activity)
01
02
03
06
Create
Change
Display
Delete
DOKAR
(Document type)
The activities can be executed for the document type.
STATUS
(Document status)
Authorization Object C_DRAW_STA (Document Status)
The following table shows authorization object C_DRAW_STA. This object controls which status(es) can be set for which document type.
Fields
Description
DOKAR
(Document type)
The statuses are allowed for this document type.
DOKST
(Document status)
Authorization Object C_DRAW_BGR (Authorization Group)
The following table shows authorization object C_DRAW_BGR. This authorization object allows you to limit access to individual documents.
Fields
Possible Values
Description
BEGRU
(Authorization group)
0000 - ZZZZ
Used to restrict the authorizations for document maintenance further.
Authorization Object C_DRAW_DOK (Document Access)
The following table shows authorization object C_DRAW_DOK. This authorization object controls which original data of a specific document type there are access authorizations for.
Fields
Possible Values
Description
ACTVT
(Activity)
52
53
54
55
56
57
Change application start
Display application start
Display archive application
Change archive application
Display archive
Store archive
DOKAR
(Document type)
Here you enter the document type that access to original data is allowed for.
Authorization Object C_DRAD_OBJ (Object Link)
The following table shows authorization object C_DRAD_OBJ. This object controls which users can process which document info records, based on a combination of activity, object, and status.
Fields
Possible Values
Description
ACTVT
(Activity)
01
02
03
06
Create
Change
Display
Delete
DOKOB
(Object)
You must enter the data base table for the objects here (for example, MARA for material record).
STATUS
(Document status) -
Link SAP DMS to Content Server
Hi all,
Im user in SDN community, i saw you responding some question about SAP DMS, i have the following scenario :
1.- I use SAP DMS in this moment and attach files from the server file.
2.- Actually i have KM in the company, here have many document for common use to the company. for instance quality control specification documents.
I need link SAP DMS to KM (Content Server), How can i attach files content in km to SAP DMS from transactions CV01N and CV02N. What´s customizing activitys i need apply?
Best Regards,
Jhonny Mogollón
Consultor SAP
InfogesaHi Jhonny,
in the standard of transaction CV01N or CV02N you see the original area at the bottom tab Document Data or you can navigate directly to tab Originals. Both times you find the same small icons. To add an original you can use whether the CREATE(white sheet) or OPEN button. If you choose CREATE a pop-up window appears where you can enter all original related data (workstation application, description, ). In the path field you can enter the path to the original manually or you can browse for it using the F4 help. Since you select the correct file on your PC or Server please press OK and the path will be entered in the pop-up field automatically.
After you entered all this data and confirm you will return to the CV01N or CV02N screen and see that the original file is added. However the displayed lock sign is still open which means that the original is not checked in at the moment. Please use the small green CHECKIN icon and select a suitable storage category on the next screen. After confirming your selection and saving the document the original is checked in correctly.
Regarding the customizing I would kindly ask you to check the following settings:
1. Storage category:
Please check if a storage category is maintained in your system. I would recommend you to use the Content Server (KPRO) storage type. Therefore please go to transaction DC10 and choose the
relevant document type. Display its details and you will find a flag called Use KPRO. Please flag it to use the KPRO storage type which is recommended by SAP. You can manage your storage categories and KPRO settings by transaction CSADMIN.
2. Workstation Application:
To store originals in DMS it is necessary to have some workstation applications defined in transaction DC30. These applications are necessary to handle originals correctly. Please maintain a workstation application for each file format to avoid problems in the future. For all further information please see the blue information button in transaction DC30.
Best regards,
Christoph
Maybe you are looking for
-
On Step 1 of 7, the "Mailbox role: Client Access service," I got an error during installing: Error: The following error was generated when "$error.Clear(); Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, I
-
Have read so many discussions about how to fix Error 7 Windows 126, but none seem to give a real answer. I have uninstalled all Apple programs from my computer. I have scanned for viruses and cleaned out everthing....The install of 10.6 is fine unt
-
Hi all, I have a requirement to create a payment term 30 Days, 3 % Cash Discount . This means if payement is done with in 30 days 3% discount will be given. But there is no specification of net days here. SO does that mean that net is 31 days? Also,
-
Wanted to know if anyone else was having this same font annomaly? When in Mail, if I ever need to change my text colour to black through the "Click to choose text color" toolbar option (for example if I have copied text that was in a different colour
-
For a particuar material, not able to raise GRIR
friends, I have a requirement. for a particular material x, the user is not able to raise GRIR. When attempted, the message displayed is as follows: "QM VIEW/Inspection Type 01 for x not maintained. Message No. 81000"...but when i checked the q