cancel
Showing results for 
Search instead for 
Did you mean: 

Archiving Documents for DMS Object CV_DVS

Former Member
0 Kudos

Dear Experts,

I am working on DMS Implementation, and during the testing we have created couple of sample documents, and now i wanted to Archive those documents, I have done the following :

  • Mark the DIR for deletion
  • CVAR- Archive administration, created a variant Var_DMS, Start Date = Immediate, Spool = Print device
  • Archive Directory is already showing as =/usr/sap/DEV/SYS/global/  how to change this ??
  • note down the archive session = Archiving session 000021 and archive file: PP_CV_DVS_20150517_120701_0.ARCHIVE
  • CVRE - Read program DVSARCH3 executed and it shows from session 21 that 7 documents are read
  • CVLO- Select Archive session and file 000021,  immediate and print device.

After going through all the above steps, i get the following job log. But the strange thing is all those 7 documents with Deletion Flag still exist .

Job started

Step 001 started (program DVSARCH2, variant DV_TEST1, user ID BASIS)

Archive file 000021-001CV_DVS is being verified

Archive file 000021-001CV_DVS is being processed

Job finished

Please suggest if i m still missing any steps.?

Thanks
Adnan

Accepted Solutions (0)

Answers (2)

Answers (2)

christoph_hopf
Advisor
Advisor
0 Kudos

Hi Adnan,

maybe the information at http://help.sap.com/saphelp_erp60_sp/helpdata/en/f1/04dd5321e8424de10000000a174cb4/content.htm?frame...

could be useful for you.

Best regards,

Christoph

benedikt_wagner_mdt
Active Participant
0 Kudos

Hi Adnan,

your first step (DVSARCH2) only selects the data and writes it to a file. What was the effect of the CVLO transaction? This would delete the data from the database.

I never used the special transactions you mentioned. I always use transaction SARA to have an overview of the environment. Archiving object for DMS is CV_DVS.

From SARA you can access:

  • Customizing: In "Archiving Object-Specific Customizing/Technical Settings"
    • you can set the destination of the file via a logical file name
    • specify the variants for the delete program (test/production); I suppose that your production variant has the test flag set
    • sequence of write/archive/delete: on test systems you could delete without archiving; on production systems I recommend to archive before deleting and read from storage system
  • write job (this is CVAR)
  • delete job (this is CVLO)
  • ...

Regards,

Benedikt