2445075 - CostingRelevncy Indicator is Copied/Not Copied From Control Key in transaction code CA02 and CEWB

You edit task list operations in transaction code CA02 or CEWB. Following symptoms might be noticed:

• When the control key of an operation is changed in transaction code CA02, CostingRelevancy is not updated according to the costing setting of the new control key. In transaction code CEWB CostingRelevancy is updated properly according to the new control key.
• In transaction code CA02 CostingRelevancy is not set to 'X', when you overwrite the control key of an existing operation with a control key relevant for costing. In transaction code CEWB CostingRelevancy is updated properly according to the new control key.
• In transaction code CEWB CostingRelevancy indicator is updated when the control key of an existing operation is changed. This is unexpected, as transaction code CA02 does not update CostingRelevancy, when the control key of an operation is overwritten.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Read more...

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP S/4HANA Cloud Private Edition all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

PP-BD-RTG , LO-EWB , Routing , Engineering Workbench , CA02 , CEWB , Operation , Vorgang , Control key , Steuerschlüssel , CostingRelevncy , KalkRelevanz , PLPOD-CKSELKZ , OPR_CLASS_DATA-CKSELKZ , Change , ändern , änderung , geändert , Arbeitsplan , Routing , Task List , Kennzeichen , Kennzeichnung , KBA , PP-BD-RTG , Routing , LO-EWB , Engineering Workbench , Problem