SAP中关于COGI删除记录

如题，相信应用中基本都会遇到类似问题。之前研究过通过权限控制的方法解决。但即使这样，有权用户的COGI删除仍需有记录可查。所以，查阅一下资料，截取如下信息当学习笔记记录一下。

问题：

用户在COGI中删除了一些条目。如何追踪哪些资料已被删除?

我已经尝试在表格AFFW, AFFWPRO，但无法获得信息。

 答复之一：

The other way is to have Table logging of the deleted records for which you need to implement OSS note #309050

Standard SAP does not log the Manually deleted entries of COGI.

If this log is required have a look at the SAP Note:309050, after implementation of the note. You can find the entries in AFFWPRO table with a update indicator as 'D'.

Even if it cleared through background processing the entries will exist in this table with update indicator as U.

另一种方式是有删除记录的表日志，您需要实现OSS注#309050

标准SAP不记录手动删除的COGI条目。

如果需要此日志，请查看SAP备注:309050，在实现该备注之后。您可以在AFFWPRO表中找到更新指示器为“D”的条目。

即使它通过后台处理清除，更新指针为U的表项仍然存在。

Note 309050 - Logging of deleted AFFW records

309050 -记录已删除的AFFW记录
 
Summary总结

Symptom症状
Automatic goods movements are not posted.
There is no material document or a planned change record in tables AFRP1, AFRP2 or AFFW or an error record in table AFFW.
Error records for goods movements deleted manually cannot be identified. You can delete them with transaction COGI, for example.
However, error records can also be deleted by canceling the responsible confirmation.

The system should check whether AFFW records are deleted by processing in the background job without corresponding material documents being posted.

自动货物移动不过账。

表AFRP1、AFRP2或AFFW中没有实质性文件或计划变更记录，表AFFW中没有错误记录。

手动删除的货物移动错误记录无法识别。例如，您可以使用事务COGI删除它们。

但是，通过取消负责任的确认也可以删除错误记录。

系统应检查AFFW记录是否在后台作业中处理删除，而没有发布相应的材料文件。

Reason and Prerequisites
The disappearance of AFFW records cannot be explained.

原因和先决条件

无法解释AFFW记录的消失。

Solution
Make a temporary modification to the goods movements update from the confirmation. You should use the modification to localize the cause of the error. After the removal of the cause, you have to deactivate logging again since it might cause performance to deteriorate.
Logging of all AFFW records which are deleted and for which no material document is created.

解决方案

从确认开始临时修改货物变动。您应该使用修改来定位错误的原因。在消除原因之后，您必须再次禁用日志记录，因为它可能会导致性能下降。

记录所有已删除且未创建任何重要文档的AFFW记录。