Ansicht
Dokumentation

Document management: Changes to processing of original application data ( RELNPP_BD_3.0_DVOR )

CPI1466 during Backup   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Short text

Document management: Changes to processing of original application data

Description

On the Basic data screen, the procedure for maintaining original application data has been changed. New functions for archiving original application files and for processing files which are already archived are also available.

The following changes have been made to the maintenance procedure:

• You now maintain original application data using the fields File 1 and File 2.
  In these fields, you enter the key of the application you want to use for processing the original application file. Once you have selected the application, you see the description of this application on screen.

• To enter data on where the file is stored, choose menu option Extras -> Originals -> Storage data or the Storage data pushbutton.

• Enter a data carrier, then enter the path to the original application file. You can display possible entries using the file system.
  In the IMG, you can define how the search for original application files in the file system works:

• "Mount Points/Logical Drives"
  In this step, you define a path for each combination of computers, which your system uses to access the file system.

• "Workstation Applications"
  In this step, you enter file formats which are relevant to original data of the application and which should be used in file selection using the file manager. If you select original data from your document info record via the file manager, the system only lists files with the formats you enter here.

The following new functions for processing original application files have been developed:

• Additional files

In the dialog box for storage data, you can maintain up to 99 additional files for each original application file. For example, a text file can have any of the following additional files: style sheet, graphics, and a spreadsheet. The additional files are identified by a two-character counter. As for the original application file, you enter a data carrier and a path in the file system. Also as for the original file, you can use the file system to display possible entries and select additional files.

As these additional files are functionally linked to the original application file, certain functions for the original file are automatically executed for the additional files. For example, if you archive original application files to the SAP database, a vault or an archive, the additional files are saved to the same place.

• Save to SAP

This function is used to save an original application file to the SAP database. In the "Document Types" step of the IMG, you define how big a file you can save to your SAP database. This value for the file size also determines whether this function is active for a document info record (0 = inactive).

• Save to vault

A vault is a server define in the IMG. For security reasons, you cannot access the vault directly via the file system. In the "Data Carriers" step, you define a path for a data carrier of data carrier type "vault",but you do not see this path when you process a document info record. The system assigns the file name from an internal number range. As you do not work with this internal name, the name is not displayed.

Note:

Original application files and any additional files which have been saved to the SAP database or the vault are processed in the same way as archived original application files. The application cannot access an archived file directly. For this reason, the system creates a copy of the file.

1. If you want to change the file, you see a dialog box in which you enter the data carrier and path where you want the system to put the copy. As a default, the system proposes the path under which the file was stored before it was archived.
2. If you want to display the file, the system automatically determines the path from the settings made in the IMG. In the IMG step "Data Carrier Types", a path for all data carriers of this type is entered. In the "Workstation Applications" step, you can enter a specific file suffix for the copy.

• Retrieve from archive

In the SAP System the last processing status of the file is archived in the SAP database, the vault or the archive. If you change this archived data and maybe destroy the file, or if serious errors occur, you can use this function to undo all changes made up to the last change status since archiving.

If you are working in change mode, the system proposes the path and name under which the file was stored before it was last archived.

1. If a status with change type "Original processing" (o) is defined in the status network for the document type, the system sets this status. The name of the user is automatically copied across as the name of the person responsible for the record. Only this user can edit the document info record until another status is set. Other users can only display the document and, if they have the authorization, set another status.
   The data carrier and path entered in the dialog box for provision of stored application data are copied automatically to the storage location fields.
   This data is then automatically updated by the system.
2. If a status with change type "Original processing" (o) is defined in the status network, but this status cannot be set because it cannot follow the current status in the status sequence, you cannot change the original application file.

• EPS print file

With this function, you can produce an EPS print file from either file 1 or file 2, which you can insert into a SAPscript text using an INCLUDE. The standard text key is the same as the document key.

Example:
INCLUDE '000DRWADTEST 00000' OBJECT TEXT ID ST

Requirements:
First you must have produced an EPS file from the original application file, using an external program.

When you execute this function, you enter the EPS file you produced earlier in a dialog box. You can select any server in the file system. Make an entry in the Height in cm field to define the height of the graphic when it is inserted in a standard text. The width is scaled so as not to distort the graphic for this height.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

In the IMG, you can make entries that control processing of original application data. To do this, complete the following steps:

• Define document types

• Define data carriers

• Define mount points/logical drives

• Define workstation applications

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 8432 Date: 20240523 Time: 065735     sap01-206 ( 154 ms )