SAP ArchiveLink is used to store batch records
in optical archives.
In this IMG activity, you define the assignment of object types and document
types of the batch record to content severs and
link tables.
The object type and document types for the batch record have been predefined by SAP as follows:
| Object Type | Document Type | Description |
|---|---|---|
| BUS3053001 | PIEBRCONTE | Batch record: table of contents |
| BUS3053001 | PIEBRDEVIA | Batch record: deviations |
| BUS3053001 | PIEBRMATLI | Batch record: material list |
| BUS3053001 | PIEBRMESSA | Batch record: process messages |
| BUS3053001 | PIEBRORDER | Batch record: process order |
| BUS3053001 | PIEBRPRLOS | Batch record: inspection lot |
| BUS3053001 | PIEBRSHEET | Batch record: PI sheet |
| BUS3053001 | PIEBRUSER | Batch record: user-defined data |
| BUS3053001 | PIEBRVERS | Batch record: version data |
| BUS3053001 | EBR_DOC | Batch record attachment: DOC |
| BUS3053001 | EBR_RTF | Batch record attachment: RTF |
| BUS3053001 | EBR_PDF | Batch record attachment: PDF |
Note
You can use any type of content server with SAP ArchiveLink. However, to comply with the guidelines on Good Manufacturing Practices (GMP), you should only use optical archives for your batch records.
You have made the general settings for SAP
ArchiveLink (see R/3 Library, section Basis Services
-> BC - SAP ArchiveLink and R/3 Customizing,
section Basis Services -> SAP
Archive Link)
Here, you have, for example, defined your content servers (see
Maintain Content Repositories).
If you want to include more files to your batch
records as attachments in addition to the standard documents, you must define
a separate document type for these files (see Customizing for
ArchiveLink, section System Settings
->
Maintain Document Types)
If more than one content server is connected, you should assign object types and document types to content servers and link tables only after a thorough analysis of the number of documents and the access frequency to archived documents.