on 12-17-2013 7:30 AM
Hello everyone,
We are in the process of archiving MM_MATBEL. We have made all the initial settings for the Archival process, but when we run the archive session, the job finishes and says, ' no data available'. We can able to see the data in transaction code MB51.
For the Write job variant, we have mentioned only the posting period.
Is there anything else to be performed before archiving MM_MATBEL?
Kindly clarify,
Thanks,
Regards,
Irfan
My next step would be to run the archive program with a small sample set of data and set a breakpoint at the SELECT statement from MKPF and evaluate the dynamic WHERE clause that was built.
There are also 2 BADIs that are used in the program:
ARC_MM_MATBEL_CHECK - This BADI allows you to program custom archiability
Check if this was previously implemented and if anything was coded there.
There is another BADI used ARC_MM_MATBEL_WRITE which allows custom information to be written to the archive file. I do not think that any code that may exist here will be causing documents to NOT be archived.
Hope this helps.
Mike Arnold
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Make an analysis either with SE16 or with TAANA and find out how many records you have per period.
the period is the financial period, which can be different from calendar year, depending on the setup of fiscal year variants.
E.g. look at the data in SE16 for table MMKPF for your period 2011 and see if the posting date is in the same year
Did you maintain the config table for this archiving object?
This allows you to set document life by plant/transaction type.
Please review tcode OMB9.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@manjunath : No i have performed archiving for other objects and seems no problem with this user id
@Siew: The retention period for the Material documents is 2 years (i.e.need to keep last 2 years of data in the system)
@Michael : Yes i did maintain the config table. In OMB9, doc life for all in 200.
@Jurgen : For Doc life, maintained Tx types WA,WE,WH,WI,WL,WO,WQ,WR,WZ for all plants.
Thanks,
Regards,
Irfan
Hi,
Can you tell me what's the retention period of your article document that you are trying to archive?
bye
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
for MM_MATBEL SAP will not check any dependency, it does not matter if you have stock.
Please tell in which job you get the message ' no data available' . Is it in the write job, or in the delete job?
Maybe the selection criteria does not fit the data or is in conflict with the residence time.
What does the spool file for the job tell you?
the message is talking about a log, if you left the field below the complete log as LIST, then you have to check the spool file, not the log.
Just do SM37, find your jjob and see if it has an icon for spool file, if yes, then select the job and click the spool file button
you get then a list like this:
Message was edited by: Jürgen L
That is very unusual, you should even get a list if not a single document gets archived.
Try it the other way, leave all selection fields empty, just enter one material document number where you are certain that this should be archived.
Are you in a special industry solution?
What is your release?
I think there is not much left what we can do with the discussion here in SCN.
My system works normal, the screen shot from above was from some years ago, but I just did a test run for a single document and I got the expected spool file.
If you dont get the spool file then I recommend to open a ticket at service.sap.com/notes
The spool file is expected to explain why no documents could be found. Once you get the spool then we can further discuss
this last answer was probably to quick. I just did another test and entered "FAKE" as material document number in the selection screen. And in turn SAP did not create any spool file and I have the same error in the job log like you.
And the same situation (no spool) happens if I add a current material document number which is inside the defined residence time
Please tell what settings you have for residence time
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.