Hi all gurus,
we're facing a strange behaviour on the integration we set in place between a SAP backend and an external repository configured by means of Archivelink connectivity.
We did a minimal configuration backend side (customizing) in order to configure the external repo, and now we are experiencing a strange thing: documents uploaded from the original, once deleted, are not marked in TOA01 with the DEL_DATE field.
Briefly:
1- we create a new inforecord by means of transaction CV01N;
2- we upload an original selecting it browsing in the local client;
3- we select the "archive..." button, hence we choose our external repository (Archivelink) "ZG" in the "archive" tab;
4- the file is correctly uploaded into the external repo, and the padlock icon is now closed; we proceed saving the inforecord.
So far, so good.
- we now access by means of the CV02N transaction to the same inforecord created before;
- we select the original, archived file and press the "delete" button; a popup to confirm is shown, we confirm the deletion;
- we proceed by uploading a new file (steps above, from 2 to 4).
Checking the TOA01 table, we were confident to find two entries (the old, deleted file and the new one). We expected to have the DEL_DATE field filled with the deletion date on the first entry.
But this - unfortunately - is not the case; both the entries are in TOA01 without any DEL_DATE filled.
This is a huge problem for us since we are working on a report which retrieves the ARC_DOC_IDs from TOA01, and given the issue described above, we are not able to distinguish between *real* files and obsolete, deleted ones.
Any help or suggestion is really appreciated.
Thanks a lot,
M.