Archiving Deliveries (RV_LIKP)

[former_member431487]

Hello Experts,

I am trying to archive deliveries by using object RV_LIKP. After running archive program when I run deletion program then I am getting error. Does deletion flag have to be set in delivery document before it can be archived and deleted. Can the delivery document be archived if the Accounting document is still not cleared?

Thanks,

Karan

[JL23]

Any part of your questions can be answered by reading the docu.

I only entered RV_LIKP into Google and the very first hit was this docu from help.sap.com :Archiving RV_LIKP

if you click the "checks" in the menu on the left then you wont find anything about deletion indicators, hence they are not a prerequisite. The error in the spool file explain pretty well why a record could not be archived.

Of course you have to make the setting in the archiving variant to create a detailed error log. But as someone without any experience in archiving it is just silly to run it without that setting.

[former_member431487]

Hi Jurgen,

I tried to run archiving program for RV_LIKP. After that when I tried to delete in SARA then I got No data message. I selected my variant based on the selection parameters given in Production system still it did not work. I am new to this and not very sure what needs to be done to archive and delete delivery document correctly. I did try to go thru some docs in Google but still no success. I am wondering if I am missing something in Customising  but even that I checked and entry was maintained for Sales Org and Residence time field. Any idea what else could be missing?

Thanks,

Karan

[JL23]

Before you can delete anything via SARA you need to have archived something.

Do you have evidence from your write job that you archived something?

The logs and spool files are extremely important.

If you do not know anything about archiving, then you should take a class room training. Archiving goes much beyond the technical part. The legal part is even more important and this part can often not be achieved by self-education from help files

SAP press has as well a very good book on archiving.

If you need pictures beside of the documentation, then check SCN for documents, the SARA process is uniform for the common archiving objects. So a document about  could help you further too.

We cannot directly tell what you are missing, SAP has written a book about archiving, so don't expect that we can post all eventualities as a reply to a question. Make screenshots to show what you have done, and what you see in the logs then it is quite easy to explain what is missing.

[former_member431487]

Hi Jurgen,

Thanks for the detailed reply. I am new to Archiving. What I want to understand is that how I can determine the Business Rules for different Archiving objects in SD. What I mean to say is that how can I find out what are the dependencies of Archiving on particular object (like what should be document status before it is archived, impact on tables etc).

Since I am very new to this so I have not yet done anything in the system so unfortunately I cannot share any screenshots. I just wanted to get some understanding before starting in the system.

I hope I have correctly explained what I am trying to understand. Thanks again for your answers and would really appreciate if you can help me understand it further.

Regards,

Karan

[JL23]

in transaction SARA, enter the archiving object, then click the network icon and you will get what SAP has defined on dependencies for their standard process.

As many things in SAP, even this network graphic is subject for customizing. Most people take the default as the only truth and wonder later about issues.

However, the network graphic is not more than an optical help, it does not control any activity.

Important is to have deep knowledge about archiving functionality on one hand, and deep knowledge on your process design on the other hand.

From my personal point of view certainly not an activity for beginners.

We are currently running an archiving project, as I am doing a migration project I couldn't take the lead, so we even hired an experienced external. He did a real good job in talking with the business, explaining archiving in general and collecting requirements and doing documentation. He then came up with an overall archiving sequence which was based on the SAP network graphics and I explained him that this doesn't work that easy. In the network graphic is for example the stock transfer process not included.

If you archive deliveries, then it can happen that purchase orders cannot be closed if there was a difference with the receipt, as an addition receipt or a cancellation checks the delivery and returns for existence. Hence you need to differentiate the dependencies by document type, item category etc. to avoid such situation. Just one example.

[former_member431487]

Hi Jurgen,

Thanks for the detailed explanation.

I tried Archiving Shipments and Delivery documents using SD_VTTK and RV_LIKP objects respectively. I selected 50 Shipments but only 38 were archived and deleted from the system whereas remaining 9 are still in the system. Of the 12 Shipments archived, I selected corresponding Delivery documents and archived but only 3 documents got archived and deleted whereas rest 9 are still in system.

I compared the table entries for archived and non-archived documents and I did not find difference in entries in terms of document type, creation date etc. In standard SAP Archiving objects are there any conditions based on which I can check which documents are getting archived and which are not?

Regards,

Karan

[JL23]

use the object Id to find read the documentation

e.g. drop this in Google:   SD_VTTK site:help.sap.com

here you can find the prerequisites.

Update always your system with the most recent  OSS notes for an archiving object, it is the most important part before starting archiving.

Check further the spool file and the job log of your archiving job, here you find usually the details why something was  not archived.

[former_member431487]

Hi Jurgen,

Thanks for your helpful answers. I have been able to get a hang of archiving and now I am able to archive several documents successfully.

But I have one doubt - I checked in LIPS table that there are many old entries. Based on the conditions given in RV_LIKP object's archiving and deletion program I checked for each delivery in VBUK and they satisfied all the conditions like Overall status C (Completely processed), Billing Status C, Goods Movement status C etc. but still these documents did not get archived.

My question is that even if the delivery document is completely processed but still it is not archived then what could be the reason for that. Does WM Transfer Order also needs to be completed and archived before Delivery can be archived?

I did go thru the SAP help material as suggested by you which helped me understand archiving better. But I am confused regarding the very old entries in LIPS which are not getting archived.

Also, for delivery documents of inactive plants can we run any standard program to clear all the entries from database tables?

Once again, I really appreciate your help.

Regards,

Karan

[JL23]

What does the archiving jobs spool file say about those old documents?

[former_member431487]

Hi Jurgen,

Archiving jobs have been running since a long time in our system yet some old documents are still present. I did not run those jobs earlier and now spool will not be available for those jobs so I am not sure what error message must have been there in the spool.

I am just trying to understand functionally if there is anything missing in those documents (which are completely processed) because of which they are not archived. It can also be possible that for some of those old documents (more than 10 years old) archiving job may not have been run. But before concluding that I just wanted to be sure that functionally there is nothing missing in these documents and if archiving job were to be run now then they should be archived.

Regards,

Karan

[JL23]

Archiving can be executed in test mode, so you can get the error log without having archived anything.