Settings have to be made in the system for other applications as well as in Customizing for Conversions . Use the Implementation Guide (IMG) for instructions of the individual activities where you enter the required data.
Decide whether you want to check in files to a secure area that you want to convert into the SAP System. Secure storage areas are storage systems controlled by the Knowledge Provider such as vault, archive, and the SAP database .
By deciding to check in and store the files you make it possible for the files to be accessed from any workstation. A disadvantage of this is that the data must be transported often. Note the following:
Checking an Original Application File into a Secure Storage Area |
Note |
Yes |
In Customizing for Conversions you must not set the following indicators:
|
No |
Example Under WinNT a file c:\users\test.doc is created and put in a document info record of the SAP Systems as an original application file. Problem The conversion server that is running on another computer cannot access this file. Solution Allow other computers to access c:\users . Connect c:\users to the local computer as well as the conversion server with a logical drive, for example x: Process the file locally under the name x:\test.doc . Crate an original application file in the document info record of the SAP System using this name. End of the example.
|
Maintain the conversion data.
See: Maintain Customizing for Conversions
Assign SAP authorizations for users.
Each user that starts a conversion (implicitly) needs the following authorizations:
Authorization Object |
Use |
C_DRAW_TCD |
Check in and check out of original application files |
C_STUE_BER |
Process bills of material (only necessary when converting assemblies) |
S_BTCH_ADM S_BTCH_JOB |
Batch administrator Operations for jobs in background processing |
Call RFC modules |
Verify that a DEFAULT entry for the frontend computer is defined in Document Management.
This setting ins in Customizing of Document Management; under