ArchiveLink Integration

Webflow solutions can store supporting documentation system within your SAP environment and link to the request object (eg vendor, invoice, customer, journal ).

SAP internal storage (SPA Business Document Service) is available out-of-the-box and requires no additional configuration.

SAP ArchiveLink can also be utilised which enables document storage outside the SAP system but still retain links to the SAP objects.

Webflow ArchiveLink Integration

The Archivelink integration is designed to reuse the existing configuration and does not normally need additional configuration.

The Webflow framework will first check the kind of object it is working with (eg a vendor, customer, journal) and check what archivelink configuration is already in place for that object within SAP

The existing configuration will then be used to post documents to archivelink without additional configuration

In summary : Webflow will search the configuration for an entry that supports the current document extension ( xls, doc etc). It will then use the first available entry to post to the archive.

Process flow

The process of searching and selecting the appropriate configuration is described below.

1. Webflow determines the incoming document extension (xls, doc, pdf )

2. Webflow determines the SAP object (vendor, customer, journal) to be linked

3. Webflow checks the available archivelink repositories for this SAP object [Table TOAOM]

4. Webflow checks for configured repositories [Table TOAAR]

5. Webflow searches the configured Archivelink document types for a suitable document type for this extension, SAP object and repository [Table TOADV]

6. Webflow uses the found document type and archive to store the file. ArchiveLink returns the file storage ID

7. Webflow links the uploaded file to the SAP object (vendor, customer, journal) to the file via its storage ID

The result is the file is available in the archivelink server and linked to in the relevant master data transaction (XK02, FB03 etc)

Standard Plugin

If the above logic does not fulfil the customer requirement then Promenta has – in addition – a standard plugin to enable the customer to explicitly configure the Archive Id, document type and archivelink object. The plugin is delivered in the standard install but must be activated by configuration

Decision tree override for /PROMENTA/TM999 – key WEBFORMS / ARCHIVELINK_PLUGIN

Function module name : /PROMENTA/WS_ARCH_UEXIT_OVR

Detail of the Standard Plugin

The standard plugin uses table /PROMENTA/TT052Z to map from promenta webflow to the expected archive information.

The table is non-transportable and must be maintained in each client and system separately. It is maintained via transaction SM30.

Example below shows the mapping for Journal Workflow to an archive (Z1) for XLSX files with documen type (class) Z1FIDOCS

Note : PROC.ID should not be used except for DataFlow solutions.

 

Plugin Technical Info (Promenta use only)

If the above logic does not fulfil the customer requirement then Promenta can produce custom logic. This is a consultancy service and would incur fees.
Promenta does not permit customers to develop their own plugin due to the sensitivity of this functionality.

Technical notes
Table /PROMENTA/TM999 (or decision tree override) – key WEBFORMS / ARCHIVELINK_PLUGIN

Enter function module with same interface as model /PROMENTA/WS_ARCH_UEXIT_MODEL

Note : do NOT change values of object_id or sap_object