This chapter describes the behavior of the CUD extensions and related aspects in the ImageMaster SAP transfer configurations.
The respective tenant ID has to be provided by the caller of an operation or the front end doing the archiving, deletion or modification (and check-in) of the document.
The functions of SAP CUD extensions extend the functions of ImageMaster with respect to SAP relevant documents. They create, delete or update internal information on documents registered (or going to be registered) in SAP. Finally, if a document is registered in SAP, the SAP system can trigger operations on documents in ImageMaster via the ImageMaster SAP ContentServer.
If a document is registered in SAP, the operations on these documents triggered by the SAP ContentServer will not be interfered by the SAP Messenger CUD extensions. For example, if the deletion of a document is requested, it will be deleted regardless which SAP Messenger extension is configured and active. The processing of the extension is omitted by checking the access role of the operation (role: contentServer) and then leaving the extension. A cleanup of the internal document type (_alis_access) is done by the ContentServer.
If a delete operation is triggered by other ImageMaster front ends, the SAP Messenger delete extension is processed and responsible for the cleanup up of internal tables.
The above also applies to the SAP Messenger create, update, and delete extensions, i.e. if the content server triggers operations, the content server business logic triggers the creation, cleanup or update of the involved data.