- SAP Community
- Groups
- Interest Groups
- Application Development
- Discussions
- Idoc Archiving
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Idoc Archiving
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2007 12:10 PM
hi,
In the production for writing idocs to archive file , a variant is scheduled every monday, which has mesgtyp and last changed date.
mesgtyp is BOMMAT
the issue is they say that the job is skipping records...can anybody suggest how to check which are the records that are skipped?
points are assured....
regards,
priya.
Message was edited by:
Priya Parvathi Jammalamadaka
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2007 2:59 PM
Hello,
After the delete job has been run, I would use WE02 and display the BOMMAT message type idoc's for the time period of the last archive job to see which idoc's are still in the system. The idoc's that are being "skipped" are probably in a status that does not allow archiving. Use WE47 to see if the status allows archiving or not. Or, depending on what release you are at, you could also try using the "Without success message" option for the Detail Log on the archive write job which should give you information on which idoc's are not archiving.
Hope this helps.
Regards,
Karin Tillotson
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2007 2:59 PM
Hello,
After the delete job has been run, I would use WE02 and display the BOMMAT message type idoc's for the time period of the last archive job to see which idoc's are still in the system. The idoc's that are being "skipped" are probably in a status that does not allow archiving. Use WE47 to see if the status allows archiving or not. Or, depending on what release you are at, you could also try using the "Without success message" option for the Detail Log on the archive write job which should give you information on which idoc's are not archiving.
Hope this helps.
Regards,
Karin Tillotson
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2007 3:57 PM
hi karin,
thanks for the info...
i had done the same checking in WE02 and also suggested that may be the statuses for which the archive flag is not set are the one's that are being skipped, but the client says that its not the problem with the status but with the last changed date, he says that may be that's causing a problem....
but...how can we find out the idocs for which date are not being archived???
regards,
priya.
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2007 4:52 PM
Hello,
Not exactly sure what to say execpt to check out oss note 791185 to see if that helps. Also, the help text on the last change field states:
Date on which control record was last changed
Use
The time of the last change does not match the time of the last generation! The controlrecord therefore always changes if the IDoc is credited a new status record.
You could manually query table EDIDC using the "last change date" field (UPDDAT) to get a list of idoc's that you wish to archive. Then, run the archive job. Use the IDOC Read program to analyze the archive file to see which idoc's were selected and compare that list to the query to find out which idoc's were not selected.
Regards,
Karin Tillotson
- SAP Managed Tags:
- ABAP Development
