Ansicht
Dokumentation
SDOK_PHIOS_CHECKIN - Check In Physical Documents to Knowledge Provider
ABAP Short Reference RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
Functionality
This function module is used to check in physical documents.
When being checked in, physical documents with the status "initial" can have their status changed to "protected" or "no content".
When a document gets the status "protected", files are copied from the file system of the front-end computer to the Content Server, thus creating physical documents with content. The status indicator "checked out" is then removed from the documents that the current user had checked out.
When the document status is set to "protected", one entry is written to the table COMPONENTS for each component of the physical document. (The table OBJECT_FILEINFORMATIONS is obsolete and should no longer be used.) Each table entry contains the following information about the component:
- Document class
- Document ID
- Source directory on the front-end computer
- File name
- File size
- MIME type
- File type flag:
- ,,T : text file
- ,,B : binary file
- ,,initial value : if no file type could be specified
Document class, document ID, source directory, and file name are mandatory data. If no MIME type is specified, components that are flagged as text are set to MIME type "text/plain". Otherwise, the MIME type is left blank. If no file type is specified, and if the MIME type is "text/...", the file type is set to text. Otherwise, the file type is set to binary.
When a physical document is checked in without content, that is, when the status indicator is set to "no content", all that is required in the table COMPONENTS is one entry per document, specifying the class and the document ID.
After the function module is called, an entry is created in the table COMPONENTS for every document whose status was changed. The data for each entry is obtained from the call.
During the checkin process, each document is either completely checked in, or not checked in at all. If individual documents cannot be checked in, the names of these documents and the appropriate error code are entered in the table BAD_OBJECTS. The most common error codes are as follows:
,,0:,,bad class:,,,,,,,,no class could be determined for phyiscal document(s)
,,1:,,not_existing:,,,,,,document does not exist
,,2:,,not_allowed:,,,,,,operation cannot be executed
,,,,,,Possible causes: another user has already checked out or reserved this document, or the document does not have status "initial"
,,3: missing_directory:,,,,source directory not specified
,,5: transfer_error:,,,,,,error with data transfer
,,6: not_authorized:,,,,,,you have no authorization for this function
,,7:,,connection_error:,,,,a connection to the database could not be set up
,,8:,,bad_storage_category:,,the storage category entered for this physical document is unknown
,,17:,,missing_filename:,,,,the file name was not specified
Example
Notes
It is not currently possible to check in files from the file system of the application server, or from just any content client.
If the function module is likely to be called several times in succession, and if data is transferred via FTP, you can set the FTP_KEEP_OPEN_FLAG flag to ensure that the same FTP connection is used for all transfers.
Further information
Parameters
BAD_OBJECTSCLIENT
COMPONENTS
FTP_KEEP_OPEN_FLAG
OBJECT_FILEPROPERTIES
PARENTKEY
VSCAN_PROFILE
Exceptions
Function Group
SDCLGeneral Data in Customer Master ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 4106 Date: 20240523 Time: 071404 sap01-206 ( 70 ms )
