Sustainability Discussions
Contribute to SAP sustainability discussions. Share ideas, collaborate on solutions, and join a community driving positive change towards a sustainable future.
cancel
Showing results for 
Search instead for 
Did you mean: 

Error KF_NOT_FOUND for basic custom metrics in SAP SCT

JBrandt
Participant
0 Kudos
560

Hi all :),

I was following the example of creating a basic custom metric in the SCT and created a metric called "FUEL_CONS", like in the demo data available.

After creating the metric, I switched to the CPE environment to upload data for the basic custom metric with the process template "Actuals - create new records for basic custom metrics".
I uploaded the demo data file for custom metrics, but the validation failed with the error:

"KF_NOT_FOUND Key figure ID value FUEL_CONS cannot be found in the Master Data table."

The error is listed here: https://help.sap.com/docs/SAP_SUS_SCT/fb87312681e94455b9f61c3b8fe83404/70b264af6be94f5faebbea8988672...

Why do I get this error? I created the metric with the correct name beforehand, shouldnt that have created the master data for the metric?
If not, where can I create the metric in the master data table myself?

Thanks for any advice or help in advance 🙂

Best regards,
Jonathan

1 ACCEPTED SOLUTION

JBrandt
Participant
0 Kudos
314

After creating a support ticket about this issue, the service pointed me towards the really simple explanation:

When creating the basic metric, I accidentally named it "FUEL_CONS " with a trailing white-space. Therefore the uploaded demo date didn't match the metric ID name...

Creating a new metric with the correct name solved the issue.

View solution in original post

1 REPLY 1

JBrandt
Participant
0 Kudos
315

After creating a support ticket about this issue, the service pointed me towards the really simple explanation:

When creating the basic metric, I accidentally named it "FUEL_CONS " with a trailing white-space. Therefore the uploaded demo date didn't match the metric ID name...

Creating a new metric with the correct name solved the issue.