/OSGMBH/D2S_MOVE_DOCUMENT Function Module

Two preconfigured modules are supplied as standard. They are contained in the sub-package /OSGMBH/DEXP10_D2S.

The /OSGMBH/D2S_MOVE_DOCUMENT function module is used to move a document within the enaio® system to a technical cabinet for enaio® repository-manager.

Interface

An object in a non-technical cabinet is the starting point. Depending on the parameterization of the call, this object is either moved to a technical enaio® cabinet and a reference document is created in the non-technical cabinet or a reference document is created in the technical cabinet.

The enaio® calls for moving/linking take place from SAP®. The object in the technical cabinet is created using ArchiveLink functions, which generates an ArchiveLink DocID. This ID can later be used to create an ArchiveLink link entry by calling the /OSGMBH/D2S_INSERT_CONNECTION function.

The module has the following import and export parameters:

Parameters in the module	Parameters in the Enterprise service	Data type	Optional	Description/examples
Export parameters
ENAIOID	Enaioid	STRING		Technical object ID of the metadata object in the non-technical cabinet
D2EPROJECT	D2eproject	STRING		ID of the data2ecm project with the settings to be applied
ENAIOCABINET	Enaiocabinet	STRING	Optional	obsolete: no longer used, to be discontinued
ENAIOARCHIVECABINET	Enaioarchivecabinet	STRING	Optional	obsolete: no longer used, to be discontinued
PROTECTION	Protection	STRING	Optional	Access protection for the document in the technical cabinet, default: 'rucd'
ALVERSION	Alversion	STRING	Optional	ArchiveLink version, default: '0046'
MOVE	Move	CHAR(1)	Optional	X: Physically move the file from the non-technical cabinet to the technical cabinet Space: Create reference document Default: 'X'
PLOGLEVEL	Ploglevel	Integer	Optional	Log level for SAP® application log (1–5), default: '3'
Export Parameters
PE_DOCID	PeDocid	STRING		ArchiveLink DocID of the document in the technical cabinet
PE_OSID	PeOsid	STRING		enaio® object ID of the document in the technical cabinet
PE_RC	PeRc	Integer		Return code 0: no error 8 and all other values: error
PET_MESSAGES	PetMessages	/OSGMBH/D2S_MSGTAB		Table with status information, separate description

Status Information

The value '0' is returned in the PE_RC field if the function could be executed without errors. In the event of an error, '8' is returned. In this case, the PET_MESSAGES table contains information on the cause of the error. This table contains the columns MESSAGETYP and MESSAGE. The value '1': error is currently only used for MESSAGETYP. The MESSAGE column contains one or more error messages. In addition, information is written to the SAP® application log. These messages can be viewed via transaction SLG1 and the /OSGMBH/D2E object type.

Customizing the enaio® data2ecm Project

The ID of an enaio® data2ecm project is transferred in the interface of the block for moving. In this manner, further technical settings for the connection between SAP® and enaio® are transferred. The following settings must be made in this project. Details on customizing enaio® data2ecm can be found in the documentation of the module.

The connection settings to the enaio® system, enaio® gateway, and the 'dms' and 'license' services are specified in the 'External systems' section. The content repository to be used and its assigned technical cabinet must also be specified here. The 'D2S' and 'DOC' licenses must be integrated into the 'license' service by default.

In the project settings, the communication form must be aligned to the respective enaio® system, that is, /OSGMBH/DX_EXPORTER_REST for connection via the 'dms' service. The business add-on remains empty; it is not used. All relevant SAP® systems must be assigned to the respective enaio® system and the relevant cabinet from which the original objects originate.

At least one combination of SAP object type and document type must be entered in the table of assigned document types, which is also assigned to the desired content repository in transaction OAC3. The document types assigned here must be deactivated to ensure that this project is not used for the normal function of enaio® data2ecm. We recommend using the document type that will later be used to enter the document link. It avoids inconsistencies.

Example for an appropriate enaio® data2ecm project: