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...

Per SAP Note - 2420306, There are no change documents for the transfer order tables LTAK and LTAP. Transactions to create/confirm transfer orders will update tables CDHDR and CDPOS in the event that certain other documents are changed - e.g. if a delivery is changed (CDHDR object class 'LIEFERUNG') or if a batch is changed (object class 'CHARGE') or if a handling unit is involved (object class 'HANDL_UNIT').                                                  This is because deliveries, handling units and batches can have multiple changes and therefore require a change history; whereas a WM transfer order is transactional. A transfer order is simply created then confirmed - there is no editing, therefore the transfer order includes the changes within its own document data.   ...