Deleting and Changing Activity Types in SAP
Uploaded by
LiviuDeleting and Changing Activity Types in SAP
Uploaded by
LiviuCommon questions
Powered by AIReport RKPLNC18 is used to delete COKA records, which is part of the cleanup process to remove any lingering data after planned activities for an activity type are reversed. Report RKPLNC29 is specifically created to remove the control records from the CSSL table when planned activities are deleted, as a program error prevents automatic deletion. Both reports facilitate proper updates to the system after changes in activity type categories or cost elements .
Control records in SAP, such as those in the CSSL table, directly impact the fiscal planning and allocation accuracy by providing default values based upon the initial posting data. Failure to update or remove these records after changes lead to planning discrepancies and can perpetuate outdated financial data usage, undermining financial reporting and operational accuracy .
To change the activity type category or allocation cost element effectively, you need to delete all postings related to the activity type, as simply changing the master data via transaction KL02 is insufficient. Planned values must be deleted rather than set to zero, and any COKA records should be removed using report RKPLNC18. Finally, you should run report RKPLNC29 to delete the control record from table CSSL, assuming no further transaction data exists for that cost center/activity type .
The CSSL table maintains a control record based on the first posting data of an activity type to a cost center. This control structure dictates the subsequent application of activity type categories and cost elements during postings. If it remains unchanged or unremoved, it defaults back to using old contexts, affecting consistency and accuracy in planning .
Setting planned values to "0" does not suffice because zero balance records remain in the SAP tables such as COSL, which cannot be deleted using standard tools. To completely clean up the data and ensure no residual records interfere with further activity type updates, full deletion of records is required .
The system uses the old activity type category or cost element during planning due to a program error wherein the control record in table CSSL is not deleted when the planned activity is deleted. As a result, although the master data should serve only as default values, the data from the first posting to a cost center remains controlling, and this requires manual deletion of control records using report RKPLNC29 .
SAP software component releases like SAP_APPL 30A to 46B establish the context under which the described program errors and solutions in the SAP notes are applicable. These releases determine the version-specific behavior and availability of features or corrections, guiding users in implementing the appropriate solutions, like those provided in SAP note 129584 for handling activity type changes and related errors .
If dependent records exist, you cannot change the allocation cost element of the corresponding activity type within a fiscal year. The default behavior of the system prevents this change because dependent records mean the allocation cost element is already transferred to the control table, which is year-dependent. This prevents any updates unless the records are appropriately managed or deleted .
The error AH1 indicates that plan records still exist on cost centers for the activity type, preventing deletion. To address this, you need to ensure that all planned and actual postings are thoroughly deleted rather than reset to zero. This includes clearing any dependent records in relevant SAP tables, typically using designated reports like RKPLNC18 and RKPLNC29 .
Creating the report RKPLNC29 is crucial because it provides a solution to a program error that fails to delete control records in the CSSL table after planned activities are removed. This custom report enables the manual deletion of these records, ensuring that updates to the activity type categories or cost elements are correctly reflected in subsequent planning and postings, thus resolving issues highlighted in SAP note 129584 .