SAP Logistics

Output condition records are crucial for business in the case of interfaces. Any changes to it will have an impact on the receiver system not receiving the data. Standard SAP hasn't given any feature to capture records directly but however, SAP has given a provision to do so. Below is the process to be recommended by SAP through SNOTE: 2967998 - No changelog available for OUTPUT condition records Check the indicator for "Log Data Changes" for table NACH in SE11. (-> click button for Technical settings) This can be set. You can develop your own query or Abap to read out the changes made in an output condition record. Use this information as a source: If you create/change an output condition in MN04/MN05, an entry is written into the table B02* (e.g. B026) and into table NACH. The two tables are linked with B026-KNUMH=NACH-KNUMH. Read table CDHDR where OBJECTCLAS = COND_OC and OBJECTID = NACH-KNUMH = B026-KNUMH OBJECTID is stored in this format: 0000000001BEF026NEU where...

NAST table is used to store all output condition records whenever the output is triggered. At times, Business requires to delete the obsolete or Old NAST records which are no longer required.  Archiving of the output records will reduce the load and increase the performance of system during processing of output condition records. To archive obsolete condition records, SAP has provided standard program  RSCLNAST to perform this activity. Ideally, business can schedule a batch job once every month to delete the older records as per the data retention date range or this can be done manually as well.