SAPERION ECM Migration Tool for SAP ArchiveLink · PDF fileHere, the new SAPDocID and the new content repository ID are filled into the link table. ... SAP Object SAP business object

SAPERION ECM Migration Tool for SAP

ArchiveLink

Copyright © 2016 Lexmark. All rights reserved.

Lexmark is a trademark of Lexmark International, Inc., registered in the U.S. and/or other countries. All other trademarksare the property of their respective owners. No part of this publication may be reproduced, stored, or transmitted in anyform without the prior written permission of Lexmark.

Table of Contents

1 Introduction ......................................................................................................... 1

1.1 Distribution .......................................................................................................... 1

1.2 Preliminary Notes ................................................................................................ 1

1.3 Technical Requirements SAP .............................................................................. 1

1.4 Preparation .......................................................................................................... 1

2 Migrating Incoming and Outgoing Documents ................................................ 2

2.1 Preparing Migration ............................................................................................ 2

2.2 Starting Migration ............................................................................................... 2

2.3 Postprocessing Migration ................................................................................. 3

3 Migrating Print Lists ........................................................................................... 4



3.3 Postprocessing Migration ................................................................................. 6

4 Migrating ADK Files ............................................................................................ 6



4.3 Postprocessing Migration ................................................................................... 8

1.1 Distribution

1

SAPERION ECM Migration Tool for SAP

ArchiveLink

1 Introduction

1.1 Distribution

The SAPERION ECM Migration Tool for SAP ArchiveLink (in the following "Migration Tool") is provided

as SAP transport. The installation runs via the SAP Transport Management System. Adaptations in SAP

and/ or SAPERION are not necessary (except customizing).

1.2 Preliminary Notes

The SAPERION SAP Migration Tool is used to migrate objects that have been stored in a non-SAPERION

archive by the SAP R/3 ArchiveLink. The migration is processed by SAP standard means. Customizing,

monitoring and processing are executed in the SAP system. The migration can be processed in a batch

mode with the distributed reports for each single object.

The objects to be migrated are loaded from the old archive and then deposited the SAPERION archive.

Regardless of whether it is a print list, ADK files or documents the migrated objects are copied into a

migration table from which the migration will be started. After the successful migration a postprocessing

for changing the document-IDs or customizing is necessary.

1.3 Technical Requirements SAP

From SAP Rel. 4.7

Supported object types:

+ Incoming documents

+ Outgoing documents

+ Drag & drop documents

+ Archive files of SAP ADK (REO files)

+ Print lists (ALF)

1.4 Preparation

It is mandatory that one or more new content repositories are configured for the deposit of documents

in SAPERION according to the ArchiveLink specification.

2 Migrating Incoming and Outgoing Documents

2

Write permission on the archive directory must exist.

2 Migrating Incoming and Outgoing Documents

2.1 Preparing Migration

To prepare for the migration of documents the documents to be migrated have to be copied into the

migration table. The delivered report "/SAAG/MIGRTION_DOC_01_INIT" can then be executed in a

batch mode.

Fig. 2–1: Selection of documents

For the selection of documents the above shown user interface is available.

Archiving Date Archiving date from - to

Client Client

Content Rep Source repository with documents

Archiving Object Document types of archived documents

The selected documents are copied into the migration table "/SAAG/MIG_TAB_D" and flagged by the

migration status "NEW". The monitoring of the migration progress is processed via this table. For a

complete migration of all documents they have to be copied completely into this migration table.

2.2 Starting Migration

The migration of documents is processed with the delivered report

"/SAAG/MIGRTION_DOC_02_MIGRATE" in a batch mode. Only documents with the migration states

"NEW" or "ERROR" are considered.

2.3 Postprocessing Migration

3

Fig. 2–2: Starting migration of documents

Following start parameters for the migration are predefined:

Client Client

Content Rep Source repository with documents

Numbers Numbers of documents per task

Migration Content Rep Target repository for documents

New Selection of the migration status "NEW"

Error Selection of the migration status "ERROR"

SAPDocID Enter a SAPDocID for document relevant migration

After the migration of documents has been completed the status "NEW" is updated to "MIGRATED" or

in cases an error occurs to "ERROR". For the purpose of documentation the old and the new SAPDocID

and also the content repository ID are saved.


If the migration is completed error-free all linking entries of document-document type have to be

reworked. For this the purpose the report "/SAAG/MIGRTION_DOC_03_FINISH" is available.

3 Migrating Print Lists

4

Fig. 2–3: Postprocessing migration

For the postprocessing of linking entries you have the following options:

+ Original Content Repository

Here, only the new SAPDocID will be filled into the link table, the content repository ID will not

be changed.

+ New Content Repository

Here, the new SAPDocID and the new content repository ID are filled into the link table.

After successful completion of the postprocessing program the documents have the status

"COMPLETED" in the migration table.

3 Migrating Print Lists


To prepare for the migration of print lists the print lists to be migrated have to be copied into the

migration table. The delivered report "/SAAG/MIGRTION_PL_01_INIT" can then be executed in a batch

mode.

Fig. 3–1: Selection of print lists

For the selection of print lists the above shown user interface is available.


5

Archiving Date Archiving date from - to

Client Client

Content Rep Source repository with print lists

Archiving Object Document types of archived print lists

SAP Object SAP business object for deposited print lists

The selected print lists are copied into the migration table "/SAAG/MIG_TAB_PL" and flagged by the


complete migration of all print lists they have to be copied completely into this migration table.


The migration of print lists is processed with the delivered report

"/SAAG/MIGRTION_PL_02_MIGRATE" in a batch mode. Only print lists with the migration status


Fig. 3–2: Starting migration of print lists

The following start parameters can be predefined for the migration:

Client Client

Content Rep Source repository with print lists

Numbers Number of prints list per task

Migration Content Rep Target repository for print lists

New Selection of migration status "NEW"

Error Selection of migration status "ERROR"

SAPDocIDEnter a SAPDocID for document relevant

migration

4 Migrating ADK Files

6

After the migration of print lists has been completed the status "NEW" is updated to "MIGRATED" or





reworked. For this the purpose the report "/SAAG/MIGRTION_PL_03_FINISH" is available.





be changed.



After successful completion of the postprocessing program the print lists have the status "COMPLETED"

in the migration table.



To prepare for the migration of ADK files the ADK files to be migrated have to be copied into the migration

table. The delivered report "/SAAG/MIGRTION_ADK_01_INIT" can then be executed in a batch mode.


7

Fig. 4–1: Selection of ADK files

For the selection of ADK files the above shown user interface is available.

Archiving Date Archiving date of ADK files from - to

Content Rep Source repository with ADK files

The selected ADK files are copied into the migration table "/SAAG/MIG_TAB_A" and flagged by the


complete migration of all ADK files they have to be copied completely into this migration table.


The migration of ADK files is processed with the delivered report

"/SAAG/MIGRTION_ADK_02_MIGRATE" in a batch mode. Only print lists with the migration status


Fig. 4–2: Starting migration of ADK files

The following start parameters can be predefined for the migration:

Content Rep Source repository with ADK files

Numbers Number of ADK files per task

Migration Content Rep Target repository for ADK files


8

New (All) Selection of migration status "NEW"

Error Selection of migration status "ERROR"

SAPDocIDEnter a SAPDocID for document relevant

migration

After the migration of ADK files has been completed the status "NEW" is updated to "MIGRATED" or





reworked. For this the purpose the report "/SAAG/MIGRTION_ADK_03_FINISH" is available.





be changed.



After successful completion of the postprocessing program the ADK files have the status "COMPLETED"

in the migration table.