...

...

...

Function 

The SAP object types are mapped to yuuvis® Momentum object types that are defined in the repositorymanager app schema. The access to yuuvis® Momentum is managed via a technical user account having that has full access to objects of types defined in the repositorymanager app schema.

Each tenant can have a single ILM repository and several ArchiveLink repositories (if needed), since ArchiveLink model includes the ContentRepository field.

Inserting a Document in yuuvis® Momentum by Barcode Upload

...

At this point it is not yet allowed to set the 'Barcode sent to R3' document flag. All other index data of the document and components need to be already filled in, in particular the unique DocID.

In regular intervals, yuuvis® Momentum REPOSITORYMANAGER determines all documents that have a barcode and no BarcodesenttoR3 flag. For these documents, an entry will be inserted in the barcode file, which is written in the configured Work/Barcode directory.

Reporting the Document to the SAP System

By calling the WriteBarcodeFile function WriteBarcodeFile, the REPOSITORYMANAGER service determines in cyclic intervals all barcodes and document IDs that have not yet been reported to the SAP system. The corresponding values of the documents to be reported are written to a file in the Work\Barcode directory by the REPOSITORYMANAGER service. This file contents 's content may look as follows:

<Barcode1> FI <Document-ID1> 20090623 FAX
<Barcode2> FI <Document-ID2> 20090623 FAX
<Barcode3> FI <Document-ID3> 20090623 FAX

Barcode values cannot contain any spaces because the space is they are used as a separator separators here.

The documents concerned affected by this process can be specified flagged using the BarcodesenttoR3 field as otherwise this field's value is set to to true. This This field will be created in the REPOSITORYMANAGER service by when reporting the barcode to the SAP system.

The barcode file is read again and the information contained information in it is reported to SAP. For each reported document, the the BarcodesenttoR3 document document flag will then be set in yuuvis® Momentum. This is a sign that the barcode has been reported successfully. Additionally, all information about the sent barcode will be entered in the current barcode file of the Success subdirectory of the Work/Barcode directory. If errors occur, an entry will be made in the current barcode file in the Error directory parallel to the , which is on the same level as theSuccess directory. There is also exists an RDY file in this context.

...

When the barcode is reported to SAP, the document ID and the barcode will be are entered into in the SAP table BDS_BAR_EX for open external barcodes. This table includes all externally captured documents that own a barcode and are therefore identified by a document ID, but could not have been internally assigned to an SAP object and a business process respectively in the SAP system.

Barcode files are exchanged in the <WorkingDirectory> in the barcode subdirectory. If the exchange file has been was processed correctly by the content server, the barcodes will be are entered in the <WorkingDirectory>\barcode\successful\yyyymmdd.txt file. If barcodes have were not been processed correctly, they will be are entered in the <WorkingDirectory>\barcode\error\yyyymmdd.txt file.

...

In the SAP system, a business process (SAP object) can be assigned to a document. For example, the booking of a payment transaction. During this process, the barcode of a business transaction will be filed together with the SAP object ID in the SAP table BDS_BAR_IN of open internal barcodes.

The document ID is referenced with the barcode in the SAP table for the open external barcodes and the barcode is referenced with an SAP object ID in the table for the open internal barcodes. Thus, the SAP object ID and the document ID can be linked. This is done automatically. Thereby, The SAP object ID and document ID will be included in are added to the SAP link table TOAXX taking into account the repository. Linking an This completes the linking of ayuuvis® Momentum document to an SAP process is thus completed. After linking, the barcode is no longer known to the SAP system and can only be searched in the yuuvis® Momentum system.

...

The following diagram depicts the data flow of when a document is given to the SAP system.

...

Receipts (documents), print lists, and reorg data (data backups) may be stored. In this case, the document ID is transferred to the yuuvis® Momentum system. Barcodes are not transferred here.

ArchiveLink

...

Retention Propagation

If an ILM-Object contains a link to an ArchiveLink object, the REPOSITORYMANAGER service ensures the following rules:

• If a legal hold or an a retention date is apecified specified for the ILM-object, these metadata are propagated to the linked ArchiveLink object itself.
• Same behavior in case of lifting the legal hold.

An ArchiveLink object with an a legal hold and/or with an a retention date lying in the future are prevented from deletion being deleted by ArchiveLink directly.

Requirements

...

Additionally, the service requires:

• ActiveMQ (REPOSITORYMANAGER-MQ service)
• Space for PersistentVolumeClaim, 10 GB recommended

...

This article describes the necessary steps for the installation of the REPOSITORY REPOSITORYMANAGER service. In addition to the docker image deployment, the Kubernetes cluster and a cluster firewall need to be configured accordingly. Furthermore, you can operate multiple instances of the REPOSITORYMANAGER service.

>> Installation of the REPOSITORYMANAGER Service

Configuration

After installing the REPOSITORYMANAGER Service, further configurations of yuuvis® Momentum and the SAP system are required.

>> Configurations for the REPOSITORYMANAGER Service