Storing PC Files, and Documents Entered Using External Entry Dia (SAP Library

Storing PC Files, and Documents Entered Using External Entry Dialogs

In the two-step storing procedure, you should first define that the function Archive from frontend is made up of the following two steps:

Store file on frontend and

Store file from frontend

In the following steps, you set up the procedure for the functions Store file on frontend and Store file from frontend.

After selecting the function Store from frontend and the document class, enter ARCHIVELNK as the communication type. This means that the function Store from frontend is split up into the subfunctions Store file on frontend and Store file from frontend.

Function Store file on frontend

This function is used to transfer the name of the file to be stored, to the R/3 System: The R/3 System finds out the name of the file currently being processed from a frontend application (absolute path incl. file name). The frontend application returns the absolute file name of the file currently being edited. Via the R/3 System, it is possible to transfer the variable archiv_id to the entry component to allow the entry component to carry out possible checks if, for example, archiv_id does not fit in with the entry component.

For the file resulting on the frontend, you must check whether the editing/creating application supports OLE Automation as a server. Examples of such applications are WinWord, MS Excel or internal scan dialogs that were certified for R/3 Release 3.0.

OLE application

After selecting the function Store file on frontend and the document class, enter OPEN as the communication type.

Non-OLE application

If files that have not been edited/scanned/generated by an OLE-capable application are to be stored, you can enter the file name of the file to be stored in the R/3 System.

After selecting the function Store file on frontend and the document class, enter ARCHIVELNK as the communication type.

Example of application maintenance for the function Store file on frontend

Microsoft Word 7.0 for Office 95 is used here as an example.
The OLE class name of the object used is "Word.basic".
The following calls are executed:

Call method "TOOLSOPTIONSSAVE" with parameters 0, 0, 0.
This deactivates any dialog boxes for the following "FILESAVE".

Call method "FILESAVE". You call this in order to ensure that the current status of the document is also stored.

Call method "FILENAME"
This ascertains the name of the current file.

This would normally suffice because SAP ArchiveLink contains the necessary values. The following method calls are required because it is not always possible for one application to open and read a file which has been opened by another application.

Call method "FILESAVEAS C:\SAPFILE"
This saves the current edited file under the name C:\SAPFILE.

Call method "FILENAME"
This ascertains the name of the current file (in this case C:\SAPFILE).

Call method "FILECLOSE"
This closes the current file (in this case C:\SAPFILE).

Call method "FILEOPEN"
This call reopens the original file.

The administration in SAP ArchiveLink is as follows:

Method: TOOLSOPTIONSSAVE 0,0,0
Method FILESAVE
Method FILENAME = @FPA
The name of the current file is ascertained and assigned to the SAP ArchiveLink variables @FPA (frontend path)

Method FILESAVEAS C:\SAPFILE
Method FILENAME = @DPA
The name of the current file (in this case C:\SAPFILE) is ascertained and assigned to the SAP ArchiveLink variables @DPA

Method FILECLOSE
Method FILEOPEN @FPA

Function Store file from frontend

This function is used to store the file whose name was transferred to the R/3 System by the function Store file on frontend: The R/3 System transfers the absolute file name of the file determined in the function, to the application, requests the application to store and expects a unique ID for the stored document to be returned. Via the R/3 System, it is possible to transfer the variable archiv_id to the entry component to allow the entry component to carry out possible checks if, for example, archiv_id does not fit in with the entry component.

It is necessary to ask whether the frontend has an internal component that is capable of OLE and to which files can be transferred for storing.

OLE-capable components:

After selecting the function Store file from frontend and the document class, enter OPEN as the communication type.

Non-OLE-capable components:

The file must be imported into the R/3 System, and stored via the application server. In this case, after selecting the function Store file from frontend and the document class, enter ARCHIVELNK or TABLE as the communication type.

ARCHIVELNK

ARCHIVELNK here means that the file is imported from the frontend and transferred as a file to the content server via server communication.
The setting ARCHIVELNK is also supported by systems certified after R/3 Release 2.1.

TABLE

TABLE here means that the file is imported from the frontend and transferred as an internal table to the content server via server communication.
The setting TABLE requires an content server that was certified after R/3 Release 3.0.