SAP Knowledge Base Article - Preview

3810632 - Activity is noted in tables COSP_BAK or COSS_BAK after migration was completed

Symptom

After migrating to SAP S/4HANA, write activity is observed on table COSP_BAK, whenever a production order is saved or released in transaction CO02 for example. This occurs even though COSP and COSS are documented as compatibility views in S/4HANA, and the expectation after migration was that CO data would be stored in the Universal Journal (ACDOCA). Users may question whether this behavior indicates an incomplete or faulty migration.


Read more...

Environment

· Controlling (CO)

· SAP S/4HANA

· SAP S/4HANA Finance

· SAP S/4HANA Cloud Private Edition

Keywords

COSP_BAK, COSS_BAK, planned costs, preliminary costing, migration, S/4HANA conversion, value type 01, value type 04, ACDOCA, compatibility view, OPL8, COR4, write activity, overhead controlling
 
, KBA , FIN-MIG-CO , Data migration for Controlling , CO-OM , Overhead Cost Controlling , Problem

About this page

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

Search for additional results

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