SAP Knowledge Base Article - Preview

2403587 - Default Delete Job does not work even the custom archive job has been deactivated

Symptom

You once scheduled a custom archive job (in addition to "Default Version Archive Job") to archive all expired messages in final state. Now you would like to activate the "Default Delete Job" to directly delete messages in final state from DB when their retention period expires instead of archiving them to archive store. However, you notice that the "Default Delete job" does not work as expected, never delete any message or report any error, even the custom archive job that you created manually has been deactivated. For example,

d1Capture.PNG

  • Data Archiving Job => the custom archive job in this example, created manually and has been deactivated
  • Default Delete job => created by PI system automatically, it is active now but no message is deleted and no error is reported
  • Default Version Archive Job  => created by PI system automatically

Read more...

Environment

  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver 7.5

Product

SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

Default Delete Job, Archive Job, Default Version Archive Job, Background Job Processing Monitor, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, AEX , KBA , BC-XI-IS-WKB , Runtime Workbench / Monitoring , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.